RTN 950 Configuration Guide (WebLCT) - (V100R003C00 - 03)

OptiX RTN 950 Radio Transmission System V100R003C00
Configuration Guide (Web LCT)

Issue Date 03 2011-04-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2011-04-10)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT)
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 950 iManager U2000 Web LCT Version V100R003C00 V100R003C00
Intended Audience
This document describes how to configure various services on the equipment. This document describes the basic information and configuration process, and uses configuration examples to show how to set specific parameters. The intended audience of this document are: l l l Installation and commissioning engineer Data configuration engineer System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
Issue 03 (2011-04-10)
iii
About This Document
Symbol
Description Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description 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 (2011-04-10) Based on Product Version V100R003C00

This is the third document issue for the V100R003C00 product version. Compared with the second issue, the updated contents are follows. Section 12 Configuring Auxiliary Ports and Functions Description Added descriptions about the function of monitoring outdoor cabinets, and the configuration procedure and configuration examples of this function. Added descriptions about the operation tasks for monitoring outdoor cabinets.
Issue 03 (2011-04-10)
A.11.6 Monitoring the Outdoor Cabinet
iv
About This Document
Section 11.7 Configuration Example (Clocks for a PSN) A.6.8.9 Activating the AIS
Description Added the examples of configuring clocks on a PSN. Added the operation task for activating AIS in IEEE 802.1ag OAM (packet plane).

This is the second document issue for the V100R003C00 product version. Compared with the first issue, the content updates are as follows. Section 7.1.2 Ethernet Port Numbers B.1.2.10 Parameter Description: Port OSPF Setting Description Added the descriptions of Ethernet port numbers. Added the parameters that are used for setting port OSPF parameters.

This is the first document issue for the V100R003C00 product version.
Issue 03 (2011-04-10)
Contents
Contents
About This Document...................................................................................................................iii 1 Configuration Preparations......................................................................................................1-1
1.1 Preparing Documents and Tools.....................................................................................................................1-2 1.2 Checking Configuration Conditions................................................................................................................1-2
2 Specifying the Configuration Procedure ..............................................................................2-1 3 Common Network Scenarios of Configuration Examples.................................................3-1
3.1 Common Network Scenario of the TDM Radio Network..............................................................................3-2 3.2 Common Network Scenario of the IP Radio Network....................................................................................3-5
4 Configuring the Network Topology.......................................................................................4-1

4.1 Basic Concepts................................................................................................................................................4-2 4.1.1 DCN.......................................................................................................................................................4-2 4.1.2 GNE and Non-GNE...............................................................................................................................4-4 4.1.3 NE ID and NE IP Address......................................................................................................................4-4 4.1.4 Physical Boards and Logical Boards......................................................................................................4-5 4.2 Configuration Procedure.................................................................................................................................4-6 4.3 Configuration Example (TDM Radio Chain Network Topology)................................................................4-11 4.3.1 Networking Diagram............................................................................................................................4-11 4.3.2 Service Planning...................................................................................................................................4-12 4.3.3 Configuration Process..........................................................................................................................4-13 4.4 Configuration Example (TDM Radio Ring Network Topology)..................................................................4-15 4.4.1 Networking Diagram............................................................................................................................4-15 4.4.2 Service Planning...................................................................................................................................4-17 4.4.3 Configuration Process..........................................................................................................................4-17 4.5 Configuration Example (Hybrid Radio Chain Network)..............................................................................4-19 4.5.1 Networking Diagram............................................................................................................................4-19 4.5.2 Service Planning...................................................................................................................................4-20 4.5.3 Configuration Process..........................................................................................................................4-21 4.6 Configuration Example (Hybrid Radio Ring Network)................................................................................4-23 4.6.1 Networking Diagram............................................................................................................................4-23 4.6.2 Service Planning...................................................................................................................................4-24 4.6.3 Configuration Process..........................................................................................................................4-24 4.7 Configuration Example (Packet Network)....................................................................................................4-26 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 4.7.1 Networking Diagram............................................................................................................................4-26 4.7.2 Service Planning...................................................................................................................................4-28 4.7.3 Configuration Process..........................................................................................................................4-29
5 Configuring Radio Links..........................................................................................................5-1

5.1 Basic Concepts................................................................................................................................................5-2 5.1.1 Adaptive Modulation..............................................................................................................................5-2 5.1.2 CCDP and XPIC.....................................................................................................................................5-4 5.1.3 RF Configuration Modes........................................................................................................................5-5 5.2 Configuration Procedure.................................................................................................................................5-6 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network).................................................5-14 5.3.1 Networking Diagram............................................................................................................................5-14 5.3.2 Service Planning...................................................................................................................................5-16 5.3.3 Configuration Process..........................................................................................................................5-19 5.4 Configuration Example (Radio Links on the TDM Radio Ring Network)...................................................5-25 5.4.1 Networking Diagram............................................................................................................................5-25 5.4.2 Service Planning...................................................................................................................................5-27 5.4.3 Configuration Process..........................................................................................................................5-30 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)...............................................5-34 5.5.1 Networking Diagram............................................................................................................................5-34 5.5.2 Service Planning...................................................................................................................................5-37 5.5.3 Configuration Process..........................................................................................................................5-41 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)................................................5-48 5.6.1 Networking Diagram............................................................................................................................5-49 5.6.2 Service Planning...................................................................................................................................5-52 5.6.3 Configuration Process..........................................................................................................................5-55 5.7 Configuration Example (Radio Links on the Packet Network)....................................................................5-60 5.7.1 Networking Diagram............................................................................................................................5-60 5.7.2 Service Planning...................................................................................................................................5-62 5.7.3 Configuration Process..........................................................................................................................5-65
6 Configuring TDM Services......................................................................................................6-1

6.1 Basic Concepts................................................................................................................................................6-2 6.1.1 Protection Modes for TDM Services.....................................................................................................6-2 6.1.2 Timeslots for TDM Services on IF Boards............................................................................................6-5 6.1.3 Numbering Schemes for SDH Timeslots ..............................................................................................6-6 6.1.4 TDM Timeslot Planning Schemes.........................................................................................................6-7 6.2 Configuration Procedure...............................................................................................................................6-10 6.3 Configuration Example (TDM Services on a TDM Radio Chain Network)................................................6-13 6.3.1 Networking Diagram............................................................................................................................6-13 6.3.2 Service Planning...................................................................................................................................6-16 6.3.3 Configuration Process .........................................................................................................................6-17 6.4 Configuration Example (TDM Services on a TDM Radio Ring Network)..................................................6-21 6.4.1 Networking Diagram............................................................................................................................6-21 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
6.4.2 Service Planning...................................................................................................................................6-23 6.4.3 Configuration Process..........................................................................................................................6-24 6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)..............................................6-29 6.5.1 Networking Diagram............................................................................................................................6-29 6.5.2 Service Planning...................................................................................................................................6-31 6.5.3 Configuration Process..........................................................................................................................6-32 6.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network)................................................6-35 6.6.1 Networking Diagram............................................................................................................................6-36 6.6.2 Service Planning...................................................................................................................................6-38 6.6.3 Configuration Process..........................................................................................................................6-39
7 Configuring Native Ethernet Services on the Packet Plane...............................................7-1

7.1 Basic Concepts................................................................................................................................................7-3 7.1.1 What's the Packet Plane..........................................................................................................................7-3 7.1.2 Ethernet Port Numbers...........................................................................................................................7-5 7.1.3 Auto-Negotiation....................................................................................................................................7-5 7.1.4 Flow Control Function...........................................................................................................................7-7 7.1.5 Native Ethernet Service Types Based on the Packet Plane....................................................................7-8 7.1.5.1 Point-to-Point Transparently Transmitted E-Line Service..................................................................7-9 7.1.5.2 VLAN-based E-Line Services...........................................................................................................7-10 7.1.5.3 QinQ-Based E-Line Services............................................................................................................7-11 7.1.5.4 8021D Bridge-based E-LAN Services..............................................................................................7-14 7.1.5.5 802.1Q Bridge-based E-LAN Services.............................................................................................7-15 7.1.5.6 802.1ad Bridge-based E-LAN Services............................................................................................7-16 7.1.6 Typical Mobile Carrier Network Topologies for Ethernet Services....................................................7-18 7.1.6.1 Networking of VLAN-Based E-Line Services..................................................................................7-19 7.1.6.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services...........................................................7-19 7.1.6.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services...........................................................7-20 7.1.6.4 Comparison Between the Three Networking Modes........................................................................7-21 7.1.7 MAC Address Table Management.......................................................................................................7-24 7.1.8 VLAN Forwarding Table.....................................................................................................................7-25 7.1.9 Split Horizon Group.............................................................................................................................7-26 7.1.10 Protection for Native Ethernet Services Based on the Packet Plane..................................................7-27 7.2 Configuration Procedure...............................................................................................................................7-30 7.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services)......................7-31 7.2.2 Configuration Procedure (VLAN-Based E-Line Services)..................................................................7-37 7.2.3 Configuration Procedure (QinQ-Based E-Line Services)....................................................................7-44 7.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services)...........................................7-52 7.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)...........................................7-61 7.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)..........................................7-69 7.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services).................................7-77 7.3.1 Networking Diagram............................................................................................................................7-78 7.3.2 Service Planning...................................................................................................................................7-78 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 7.3.2.1 Service Planning (Ethernet Ports).....................................................................................................7-79 7.3.2.2 Service Planning (Ethernet Protection).............................................................................................7-80 7.3.2.3 Service Planning (Ethernet Services)................................................................................................7-80 7.3.2.4 Service Planning (QoS).....................................................................................................................7-80 7.3.3 Configuration Process..........................................................................................................................7-82 7.3.3.1 Configuration Process (Ethernet Protection).....................................................................................7-83 7.3.3.2 Configuration Process (Service Information)...................................................................................7-83 7.3.3.3 Configuration Process (Ethernet Ports).............................................................................................7-83 7.3.3.4 Configuration Process (QoS)............................................................................................................7-84 7.3.3.5 Configuration Process (Verifying Ethernet Service Configurations)................................................7-86
7.4 Configuration Example (VLAN-Based E-Line Service)..............................................................................7-87 7.4.1 Networking Diagram............................................................................................................................7-88 7.4.2 Service Planning...................................................................................................................................7-90 7.4.2.1 Service Planning (Ethernet Ports).....................................................................................................7-91 7.4.2.2 Service Planning (Ethernet Protection).............................................................................................7-93 7.4.2.3 Service Planning (Ethernet Services)................................................................................................7-93 7.4.2.4 Service Planning (QoS).....................................................................................................................7-96 7.4.3 Configuration Process..........................................................................................................................7-97 7.4.3.1 Configuration Process (Ethernet Protection).....................................................................................7-98 7.4.3.2 Configuration Process (Service Information)...................................................................................7-98 7.4.3.3 Configuration Process (Ethernet Ports)...........................................................................................7-100 7.4.3.4 Configuration Process (QoS)..........................................................................................................7-101 7.4.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-105 7.5 Configuration Example (QinQ-Based E-Line Service)...............................................................................7-108 7.5.1 Networking Diagram..........................................................................................................................7-109 7.5.2 Service Planning.................................................................................................................................7-112 7.5.2.1 Service Planning (Ethernet Ports)...................................................................................................7-112 7.5.2.2 Service Planning (Ethernet Protection)...........................................................................................7-115 7.5.2.3 Service Planning (Ethernet Services)..............................................................................................7-116 7.5.2.4 Service Planning (QoS)...................................................................................................................7-119 7.5.3 Configuration Process........................................................................................................................7-121 7.5.3.1 Configuration Process (Ethernet Protection)...................................................................................7-121 7.5.3.2 Configuration Process (Service Information).................................................................................7-122 7.5.3.3 Configuration Process (QoS)..........................................................................................................7-128 7.5.3.4 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-132 7.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)...............................................................7-136 7.6.1 Networking Diagram..........................................................................................................................7-136 7.6.2 Service Planning.................................................................................................................................7-139 7.6.2.1 Service Planning (Ethernet Ports)...................................................................................................7-139 7.6.2.2 Service Planning (Ethernet Protection)...........................................................................................7-142 7.6.2.3 Service Planning (Ethernet Services)..............................................................................................7-142 7.6.2.4 Service Planning (QoS)...................................................................................................................7-143 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
7.6.3 Configuration Process........................................................................................................................7-145 7.6.3.1 Configuration Process (Ethernet Ports)...........................................................................................7-145 7.6.3.2 Configuration Process (Ethernet Protection)...................................................................................7-148 7.6.3.3 Configuration Process (Service Information).................................................................................7-149 7.6.3.4 Configuration Process (QoS)..........................................................................................................7-151 7.6.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-154 7.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)...............................................................7-157 7.7.1 Networking Diagram..........................................................................................................................7-157 7.7.2 Service Planning.................................................................................................................................7-160 7.7.2.1 Service Planning (Ethernet Ports)...................................................................................................7-161 7.7.2.2 Service Planning (Ethernet Protection)...........................................................................................7-163 7.7.2.3 Service Planning (Ethernet Services)..............................................................................................7-164 7.7.2.4 Service Planning (QoS)...................................................................................................................7-164 7.7.3 Configuration Process........................................................................................................................7-166 7.7.3.1 Configuration Process (Ethernet Ports)...........................................................................................7-166 7.7.3.2 Configuration Process (Ethernet Protection)...................................................................................7-173 7.7.3.3 Configuration Process (Service Information).................................................................................7-173 7.7.3.4 Configuration Process (QoS)..........................................................................................................7-176 7.7.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-180 7.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service)..............................................................7-184 7.8.1 Networking Diagram..........................................................................................................................7-184 7.8.2 Service Planning.................................................................................................................................7-187 7.8.2.1 Service Planning (Ethernet Ports)...................................................................................................7-187 7.8.2.2 Service Planning (Ethernet Protection)...........................................................................................7-190 7.8.2.3 Service Planning (Ethernet Services)..............................................................................................7-191 7.8.2.4 Service Planning (QoS)...................................................................................................................7-192 7.8.3 Configuration Process........................................................................................................................7-194 7.8.3.1 Configuration Process (Ethernet Ports)...........................................................................................7-194 7.8.3.2 Configuration Process (Ethernet Protection)...................................................................................7-199 7.8.3.3 Configuration Process (Service Information).................................................................................7-199 7.8.3.4 Configuration Process (QoS)..........................................................................................................7-203 7.8.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-206 7.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)........................7-210 7.9.1 Networking Diagram..........................................................................................................................7-210 7.9.2 Service Planning.................................................................................................................................7-213 7.9.2.1 Service Planning (Ethernet Ports)...................................................................................................7-213 7.9.2.2 Service Planning (Ethernet Protection)...........................................................................................7-216 7.9.2.3 Service Planning (Ethernet Services)..............................................................................................7-216 7.9.2.4 Service Planning (QoS)...................................................................................................................7-218 7.9.3 Configuration Process........................................................................................................................7-220 7.9.3.1 Configuration Process (Ethernet Ports)...........................................................................................7-220 7.9.3.2 Configuration Process (Ethernet Protection)...................................................................................7-224 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 7.9.3.3 Configuration Process (Service Information).................................................................................7-224 7.9.3.4 Configuration Process (QoS)..........................................................................................................7-228 7.9.3.5 Configuration Process (Verifying Ethernet Service Configurations)..............................................7-231
8 Configuring EoPDH-Based Ethernet Services.....................................................................8-1

8.1 Basic Concepts................................................................................................................................................8-2 8.1.1 What's the EoPDH Plane........................................................................................................................8-2 8.1.2 VCTRUNK.............................................................................................................................................8-3 8.1.3 Transmission Modes of Ethernet Services.............................................................................................8-3 8.1.4 Hub/Spoke..............................................................................................................................................8-4 8.1.5 EoPDH-Based Ethernet Services...........................................................................................................8-4 8.1.5.1 Point-to-Point Transparently Transmitted EPL Services....................................................................8-5 8.1.5.2 EVPL Services Based on the VLAN...................................................................................................8-6 8.1.5.3 QinQ-based EVPL Services................................................................................................................8-7 8.1.5.4 EPLAN Services Based on the 802.1D Bridge.................................................................................8-10 8.1.5.5 EVPLAN Services Based on the 802.1Q Bridge..............................................................................8-11 8.1.5.6 EVPLAN Services Based on 802.1ad Bridge...................................................................................8-13 8.2 Configuration Procedure...............................................................................................................................8-14 8.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services)..........................8-15 8.2.2 Configuration Procedure (VLAN-Based EVPL Services)...................................................................8-20 8.2.3 Configuration Procedure (QinQ-Based EVPL Services).....................................................................8-26 8.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services)...........................................8-32 8.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services)........................................8-38 8.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services)......................................8-45 8.3 Configuration Example (Ethernet Services Based on TDM Radio).............................................................8-52 8.3.1 Networking Diagram............................................................................................................................8-52 8.3.2 Service Planning...................................................................................................................................8-55 8.3.2.1 Service Planning (Ethernet Ports).....................................................................................................8-56 8.3.2.2 Service Planning (Ethernet Protection).............................................................................................8-58 8.3.2.3 Service Planning (Ethernet Services)................................................................................................8-59 8.3.2.4 Service Planning (Ethernet Service Cross-Connections)..................................................................8-60 8.3.2.5 Service Planning (QoS).....................................................................................................................8-64 8.3.3 Configuration Process..........................................................................................................................8-64 8.3.3.1 Configuration Process (Ethernet Ports).............................................................................................8-64 8.3.3.2 Configuration Process (Ethernet Protection).....................................................................................8-67 8.3.3.3 Configuration Process (Ethernet Services).......................................................................................8-68 8.3.3.4 Configuration Process (Cross-Connections) ....................................................................................8-69 8.3.3.5 Configuration Process (QoS)............................................................................................................8-72 8.3.3.6 Configuration Process (Verifying Ethernet Service Configurations)................................................8-72 8.4 Configuration Example (Ethernet Services Traversing a TDM Network)....................................................8-74 8.4.1 Networking Diagram............................................................................................................................8-74 8.4.2 Service Planning...................................................................................................................................8-77 8.4.2.1 Service Planning (Ethernet Ports on the Packet Plane).....................................................................8-78 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
8.4.2.2 Service Planning (Ethernet Services on the Packet Plane)................................................................8-78 8.4.2.3 Service Planning (QoS on the Packet Plane)....................................................................................8-79 8.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)......................................................................8-81 8.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board).............................................................8-83 8.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)................................................................8-84 8.4.2.7 Service Planning (Cross-Connections)..............................................................................................8-85 8.4.2.8 Service Planning (QoS of the EFP8 Board)......................................................................................8-86 8.4.3 Configuration Process..........................................................................................................................8-88 8.4.3.1 Configuration Process (Ethernet Services on the Packet Plane) ......................................................8-89 8.4.3.2 Configuration Process (Ethernet Ports on the Packet Plane) ...........................................................8-89 8.4.3.3 Configuration Process (QoS on the Packet Plane)............................................................................8-90 8.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board).............................................................8-92 8.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board).....................................................8-94 8.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)........................................................8-95 8.4.3.7 Configuration Process (Cross-Connections) ....................................................................................8-96 8.4.3.8 Configuration Process (QoS on the EFP8 Board).............................................................................8-97 8.4.3.9 Configuration Process (Verifying Ethernet Service Configurations)..............................................8-100
9 Configuring MPLS Tunnels.....................................................................................................9-1

9.1 Basic Concept..................................................................................................................................................9-2 9.1.1 MPLS Network Architecture.................................................................................................................9-2 9.1.2 LSP.........................................................................................................................................................9-3 9.1.3 Protection for MPLS Tunnels................................................................................................................9-5 9.2 Configuration Procedure ................................................................................................................................9-6 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)........................................................9-12 9.3.1 Networking Diagram............................................................................................................................9-12 9.3.2 Service Planning...................................................................................................................................9-13 9.3.2.1 Service Planning (MPLS Interfaces).................................................................................................9-13 9.3.2.2 Service Planning (MPLS Tunnel).....................................................................................................9-16 9.3.2.3 Service Planning (MPLS Tunnel APS).............................................................................................9-17 9.3.2.4 Service Planning (QoS).....................................................................................................................9-21 9.3.3 Configuration Process .........................................................................................................................9-23 9.3.3.1 Configuration Process (NNI Ports)...................................................................................................9-23 9.3.3.2 Configuration Process (MPLS Tunnel).............................................................................................9-26 9.3.3.3 Configuration Process (MPLS APS).................................................................................................9-33 9.3.3.4 Configuration Process (QoS)............................................................................................................9-37 9.3.3.5 Configuration Process (Verifying Configured MPLS Tunnels).......................................................9-39 9.4 Configuration Example (MPLS Tunnels with No Protection)......................................................................9-39 9.4.1 Networking Diagram............................................................................................................................9-39 9.4.2 Service Planning...................................................................................................................................9-41 9.4.2.1 Service Planning (MPLS Interfaces).................................................................................................9-41 9.4.2.2 Service Planning (MPLS Tunnel).....................................................................................................9-43 9.4.2.3 Service Planning (QoS).....................................................................................................................9-44 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 9.4.3 Configuration Process .........................................................................................................................9-46 9.4.3.1 Configuration Process (MPLS interfaces).........................................................................................9-46 9.4.3.2 Configuration Process (MPLS Tunnel).............................................................................................9-48 9.4.3.3 Configuration Process (QoS)............................................................................................................ 9-51 9.4.3.4 Configuration Process (Verifying Configured MPLS Tunnels)....................................................... 9-52
10 Configuring PWE3 Services.................................................................................................10-1

10.1 Basic Concept..............................................................................................................................................10-3 10.1.1 Types of PWE3 Services....................................................................................................................10-3 10.1.1.1 CES Services...................................................................................................................................10-3 10.1.1.2 ATM/IMA Services.........................................................................................................................10-6 10.1.1.3 E-Line Services Carried on PWs.....................................................................................................10-7 10.1.2 MS-PW.............................................................................................................................................10-10 10.2 Configuration Procedure...........................................................................................................................10-12 10.2.1 Per-NE Configuration Procedure (CES Services)............................................................................10-12 10.2.2 Per-NE Configuration Procedure (ATM Services)..........................................................................10-16 10.2.3 Configuration Procedure (E-Line Services Carried on PWs)..........................................................10-23 10.3 Configuration Example (Common CES Services)....................................................................................10-31 10.3.1 Networking Diagram........................................................................................................................10-31 10.3.2 Service Planning...............................................................................................................................10-33 10.3.2.1 Service Planning (UNI Ports)........................................................................................................10-33 10.3.2.2 Service Planning (Service Information)........................................................................................10-33 10.3.3 Per-NE Configuration Process.........................................................................................................10-35 10.3.3.1 Configuration Process (Service Information)...............................................................................10-35 10.3.3.2 Configuration Process (Verifying CES Service Configurations)..................................................10-38 10.4 Configuration Example (Fractional CES Services)..................................................................................10-38 10.4.1 Networking Diagram........................................................................................................................10-39 10.4.2 Service Planning...............................................................................................................................10-40 10.4.2.1 Service Planning (UNI Ports)........................................................................................................10-40 10.4.2.2 Service Planning (Service Information)........................................................................................10-41 10.4.3 Per-NE Configuration Process.........................................................................................................10-43 10.4.3.1 Configuration Process (Service Information)...............................................................................10-43 10.4.3.2 Configuration Process (Verifying CES Service Configurations)..................................................10-46 10.5 Configuration Example (MS-PW-based CES Services)...........................................................................10-46 10.5.1 Networking Diagram........................................................................................................................10-46 10.5.2 Service Planning...............................................................................................................................10-47 10.5.2.1 Service Planning (UNI Ports)........................................................................................................10-48 10.5.2.2 Service Planning (Service Information)........................................................................................10-48 10.5.3 Per-NE Configuration Process.........................................................................................................10-50 10.5.3.1 Configuration Process (Service Information)...............................................................................10-50 10.5.3.2 Configuration Process (Verifying CES Service Configurations)..................................................10-54 10.6 Configuration Example (Common ATM Services)..................................................................................10-55 10.6.1 Networking Diagram........................................................................................................................10-55 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
10.6.2 ServicePlanning................................................................................................................................10-56 10.6.2.1 Service Planning (UNI Ports)........................................................................................................10-57 10.6.2.2 Service Planning (ATM/IMA Information)..................................................................................10-57 10.6.2.3 Service Planning (QoS).................................................................................................................10-59 10.6.2.4 Service Planning (Service Information)........................................................................................10-61 10.6.3 Per-NE Configuration Process.........................................................................................................10-64 10.6.3.1 Configuration Process (UNI Ports)...............................................................................................10-64 10.6.3.2 Configuration Process (IMA Information)....................................................................................10-65 10.6.3.3 Configuration Process (QoS)........................................................................................................10-67 10.6.3.4 Configuration Process (Service Information)...............................................................................10-69 10.6.3.5 Configuration Process (Verifying ATM Service Configurations)................................................10-74 10.7 Configuration Example (Fractional ATM Services).................................................................................10-74 10.7.1 Networking Diagram........................................................................................................................10-74 10.7.2 ServicePlanning................................................................................................................................10-76 10.7.2.1 Service Planning (UNI Ports)........................................................................................................10-76 10.7.2.2 Service Planning (ATM/IMA Information)..................................................................................10-77 10.7.2.3 Service Planning (QoS).................................................................................................................10-79 10.7.2.4 Service Planning (Service Information)........................................................................................10-80 10.7.3 Per-NE Configuration Process.........................................................................................................10-83 10.7.3.1 Configuration Process (UNI Ports)...............................................................................................10-83 10.7.3.2 Configuration Process (IMA Information)....................................................................................10-85 10.7.3.3 Configuration Process (QoS)........................................................................................................10-87 10.7.3.4 Configuration Process (Service Information)...............................................................................10-88 10.7.3.5 Configuration Process (Verifying ATM Service Configurations)................................................10-93 10.8 Configuration Example (ATM Services on MS-PWs).............................................................................10-94 10.8.1 Networking Diagram........................................................................................................................10-94 10.8.2 ServicePlanning................................................................................................................................10-95 10.8.2.1 Service Planning (UNI Ports)........................................................................................................10-96 10.8.2.2 Service Planning (ATM/IMA Information)..................................................................................10-96 10.8.2.3 Service Planning (QoS).................................................................................................................10-97 10.8.2.4 Service Planning (Service Information)........................................................................................10-99 10.8.3 Per-NE Configuration Process.......................................................................................................10-105 10.8.3.1 Configuration Process (UNI Ports).............................................................................................10-105 10.8.3.2 Configuration Process (IMA Information)..................................................................................10-106 10.8.3.3 Configuration Process (QoS)......................................................................................................10-108 10.8.3.4 Configuration Process (Service Information).............................................................................10-109 10.8.3.5 Configuration Process (Verifying ATM Service Configurations)..............................................10-119 10.9 Configuration Example (Transparently Transmitted ATM Services).....................................................10-119 10.9.1 Networking Diagram......................................................................................................................10-119 10.9.2 ServicePlanning..............................................................................................................................10-120 10.9.2.1 Service Planning (UNI Ports)......................................................................................................10-121 10.9.2.2 Service Planning (ATM/IMA Information)................................................................................10-122 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 10.9.2.3 Service Planning (QoS)...............................................................................................................10-123 10.9.2.4 Service Planning (Service Information)......................................................................................10-124 10.9.3 Per-NE Configuration Process.......................................................................................................10-125 10.9.3.1 Configuration Process (UNI Ports).............................................................................................10-126 10.9.3.2 Configuration Process (IMA Information)..................................................................................10-127 10.9.3.3 Configuration Process (QoS)......................................................................................................10-129 10.9.3.4 Configuration Process (Service Information).............................................................................10-130 10.9.3.5 Configuration Process (Verifying ATM Service Configurations)..............................................10-134
10.10 Configuration Example (E-Line Services Carried on PWs, a Simple Example)..................................10-134 10.10.1 Networking Diagram....................................................................................................................10-135 10.10.2 Service Planning...........................................................................................................................10-136 10.10.2.1 Service Planning (UNI Ports)....................................................................................................10-136 10.10.2.2 Service Planning (Ethernet Protection).....................................................................................10-137 10.10.2.3 Service Planning (Service Information)....................................................................................10-138 10.10.2.4 Service Planning (QoS).............................................................................................................10-139 10.10.3 Per-NE Configuration Process.....................................................................................................10-140 10.10.3.1 Configuration Process (UNI Ports)...........................................................................................10-141 10.10.3.2 Configuration Process (Ethernet Protection).............................................................................10-142 10.10.3.3 Configuration Process (Service Information)...........................................................................10-143 10.10.3.4 Configuration Process (QoS)....................................................................................................10-145 10.10.3.5 Configuration Process (Verifying Ethernet Service Configurations)........................................10-146 10.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet Services Aggregated from the Hybrid Microwave Network)...........................................................................................................10-148 10.11.1 Networking Diagram....................................................................................................................10-148 10.11.2 Service Planning...........................................................................................................................10-150 10.11.2.1 Service Planning (UNI Ports)....................................................................................................10-150 10.11.2.2 Service Planning (Ethernet Protection).....................................................................................10-152 10.11.2.3 Service Planning (Service Information)....................................................................................10-152 10.11.2.4 Service Planning (QoS).............................................................................................................10-154 10.11.3 Per-NE Configuration Process.....................................................................................................10-155 10.11.3.1 Configuration Process (UNI Ports)...........................................................................................10-156 10.11.3.2 Configuration Process (Ethernet Protection).............................................................................10-157 10.11.3.3 Configuration Process (Service Information)...........................................................................10-158 10.11.3.4 Configuration Process (QoS)....................................................................................................10-162 10.11.3.5 Configuration Process (Verifying Ethernet Service Configurations)........................................10-163 10.12 Configuration Example (E-Line Services Carried on MS-PWs)..........................................................10-166 10.12.1 Networking Diagram....................................................................................................................10-166 10.12.2 Service Planning...........................................................................................................................10-167 10.12.2.1 Service Planning (UNI Ports)....................................................................................................10-168 10.12.2.2 Service Planning (Ethernet Protection).....................................................................................10-169 10.12.2.3 Service Planning (Service Information)....................................................................................10-169 10.12.2.4 Service Planning (QoS).............................................................................................................10-171 10.12.3 Per-NE Configuration Process.....................................................................................................10-173 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
10.12.3.1 Configuration Process (UNI Ports)...........................................................................................10-173 10.12.3.2 Configuration Process (Ethernet Protection).............................................................................10-174 10.12.3.3 Configuration Process (Service Information)...........................................................................10-175 10.12.3.4 Configuration Process (QoS)....................................................................................................10-178 10.12.3.5 Configuration Process (Verifying Ethernet Service Configurations)........................................10-180
11 Configuring the Clock...........................................................................................................11-1

11.1 Basic Concepts............................................................................................................................................11-2 11.1.1 Clock Source......................................................................................................................................11-2 11.1.2 Clock Protection Modes.....................................................................................................................11-2 11.1.3 Clock Synchronization Policy............................................................................................................11-6 11.2 Configuration Procedure...........................................................................................................................11-14 11.3 Configuration Example (Clock for a TDM Radio Chain Network)..........................................................11-17 11.3.1 Networking Diagram........................................................................................................................11-17 11.3.2 Service Planning...............................................................................................................................11-19 11.3.3 Configuration Process......................................................................................................................11-19 11.4 Configuration Example (Clock for a TDM Radio Ring Network)...........................................................11-20 11.4.1 Networking Diagram........................................................................................................................11-20 11.4.2 Service Planning...............................................................................................................................11-22 11.4.3 Configuration Process......................................................................................................................11-23 11.5 Configuration Example (Clock for a Hybrid Radio Chain Network).......................................................11-24 11.5.1 Networking Diagram........................................................................................................................11-25 11.5.2 Service Planning...............................................................................................................................11-26 11.5.3 Configuration Process......................................................................................................................11-27 11.6 Configuration Example (Clock for a Hybrid Radio Ring Network).........................................................11-28 11.6.1 Network Diagram ............................................................................................................................11-28 11.6.2 Service Planning...............................................................................................................................11-30 11.6.3 Configuration Process......................................................................................................................11-31 11.7 Configuration Example (Clocks for a PSN)..............................................................................................11-32 11.7.1 Networking Diagram........................................................................................................................11-32 11.7.2 Service Planning...............................................................................................................................11-34 11.7.3 Configuration Process......................................................................................................................11-35 11.8 Configuration Example (Clocks Across a Third-party TDM Network)...................................................11-36 11.8.1 Networking Diagram........................................................................................................................11-36 11.8.2 Service Planning...............................................................................................................................11-38 11.8.3 Configuration Process......................................................................................................................11-39
12 Configuring Auxiliary Ports and Functions......................................................................12-1

12.1 Auxiliary Ports and Functions.....................................................................................................................12-3 12.2 Environment Monitoring Functions............................................................................................................12-5 12.3 Configuration Procedure (Monitoring the Outdoor Cabinet)......................................................................12-7 12.4 Configuration Example (Orderwire)...........................................................................................................12-9 12.4.1 Networking Diagram..........................................................................................................................12-9 12.4.2 Service Planning...............................................................................................................................12-11 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) 12.4.3 Configuration Process......................................................................................................................12-13
12.5 Configuration Example (Synchronous Data Services)..............................................................................12-13 12.5.1 Networking Diagram........................................................................................................................12-13 12.5.2 Service Planning...............................................................................................................................12-15 12.5.3 Configuration Process......................................................................................................................12-16 12.6 Configuration Example (Asynchronous Data Services)...........................................................................12-16 12.6.1 Networking Diagram........................................................................................................................12-17 12.6.2 Service Planning...............................................................................................................................12-19 12.6.3 Configuration Process......................................................................................................................12-19 12.7 Configuration Example (Wayside E1 Services)........................................................................................12-20 12.7.1 Networking Diagram........................................................................................................................12-20 12.7.2 Service Planning...............................................................................................................................12-21 12.7.3 Configuration Process......................................................................................................................12-21 12.8 Configuration Example (External Alarms)...............................................................................................12-21 12.8.1 Networking Diagram........................................................................................................................12-22 12.8.2 Service Planning...............................................................................................................................12-22 12.8.3 Configuration Process......................................................................................................................12-23 12.9 Configuration Example (Monitoring the Outdoor Cabinet)......................................................................12-24 12.9.1 Network Diagram.............................................................................................................................12-24 12.9.2 Service Planning...............................................................................................................................12-25 12.9.3 Configuration Process......................................................................................................................12-26
13 Adding and Modifying Configuration Data....................................................................13-1

13.1 Common Task Collection (NEs).................................................................................................................13-2 13.2 Common Task Collection (Radio Links)....................................................................................................13-3 13.3 Common Task Collection (TDM Services)................................................................................................13-7 13.4 Common Task Collection (Packet-Plane Ethernet Services)......................................................................13-8 13.5 Task Collection (EoPDH-Plane Ethernet Services)..................................................................................13-10
A Task Collection.........................................................................................................................A-1
A.1 Network Management...................................................................................................................................A-3 A.1.1 Managing NEs......................................................................................................................................A-3 A.1.1.1 Creating NEs by Using the Search Method.......................................................................................A-4 A.1.1.2 Creating NEs by Using the Manual Method.....................................................................................A-5 A.1.1.3 Logging In to an NE..........................................................................................................................A-6 A.1.1.4 Configuring the Logical Board..........................................................................................................A-7 A.1.1.5 Changing the NE ID..........................................................................................................................A-8 A.1.1.6 Changing the NE Name.....................................................................................................................A-9 A.1.1.7 Synchronizing the NE Time............................................................................................................A-10 A.1.1.8 Localizing the NE Time..................................................................................................................A-11 A.1.2 Configuring the Performance Monitoring Status of NEs...................................................................A-12 A.1.3 Suppressing Alarms for Monitored Objects.......................................................................................A-13 A.1.4 Managing Communications................................................................................................................A-14 A.1.4.1 Setting NE Communication Parameters..........................................................................................A-15 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
A.1.4.2 Configuring DCCs...........................................................................................................................A-16 A.1.4.3 Configuring Extended ECC Communication..................................................................................A-17 A.1.4.4 Configuring DCC Transparent Transmission..................................................................................A-19 A.1.4.5 Creating Static IP Routes.................................................................................................................A-20 A.1.4.6 Setting Parameters of the OSPF Protocol........................................................................................A-21 A.1.4.7 Enabling the ARP Proxy.................................................................................................................A-22 A.1.4.8 Configuring the CLNS Role............................................................................................................A-23 A.1.4.9 Configuring the OSI Tunnel............................................................................................................A-23 A.1.4.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN..........................................A-24 A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports..........................................A-25 A.1.4.12 Configuring the Protocol Type of the Inband DCN......................................................................A-26 A.1.4.13 Querying ECC Routes...................................................................................................................A-27 A.1.4.14 Querying IP Routes.......................................................................................................................A-28 A.1.4.15 Querying OSI Routes....................................................................................................................A-28 A.1.4.16 Configuring Access Control..........................................................................................................A-29 A.1.5 Configuring Service Access of NEs ..................................................................................................A-29 A.1.5.1 Configuring LCT Access to NEs.....................................................................................................A-30 A.1.5.2 Configuring Ethernet Access to NEs...............................................................................................A-30 A.1.5.3 Configuring Serial Port Access to NEs...........................................................................................A-31 A.1.6 Configuring an NE User.....................................................................................................................A-32 A.1.6.1 Creating an NE User........................................................................................................................A-32 A.1.6.2 Changing the Password of an NE User...........................................................................................A-33 A.1.6.3 Setting Warning Screen Parameters................................................................................................A-34 A.2 Managing Radio Links................................................................................................................................A-35 A.2.1 Creating an IF 1+1 Protection Group.................................................................................................A-36 A.2.2 Creating an XPIC Workgroup............................................................................................................A-37 A.2.3 Setting the AM Attributes of the XPIC Workgroup...........................................................................A-38 A.2.4 Configuring the IF/ODU Information of a Radio Link......................................................................A-40 A.2.5 Creating an N+1 Protection Group.....................................................................................................A-42 A.2.6 Querying the IF 1+1 Protection Status...............................................................................................A-43 A.2.7 Querying the IF N+1 Protection Status..............................................................................................A-44 A.2.8 IF 1+1 Protection Switching...............................................................................................................A-45 A.2.9 IF N+1 Protection Switching..............................................................................................................A-45 A.2.10 Starting/Stopping the N+1 Protection Protocol................................................................................A-46 A.3 Managing the MSP......................................................................................................................................A-47 A.3.1 Configuring Linear MSP....................................................................................................................A-47 A.3.2 Querying the Status of the Linear MSP..............................................................................................A-48 A.3.3 Performing Linear MSP Switching....................................................................................................A-49 A.3.4 Starting/Stopping the Linear MSP Protocol.......................................................................................A-50 A.4 Managing TDM Services............................................................................................................................A-50 A.4.1 Creating the Cross-Connections of Point-to-Point Services..............................................................A-51 A.4.2 Creating Cross-Connections of SNCP Services.................................................................................A-52 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) A.4.3 Modifying the Priorities of E1 Services.............................................................................................A-53 A.4.4 Inserting E1_AIS upon a TU_AIS Condition....................................................................................A-54 A.4.5 Configuring the Automatic Switching of SNCP Services..................................................................A-55 A.4.6 Deleting Cross-Connections...............................................................................................................A-56 A.4.7 Converting a Normal Service into an SNCP Service.........................................................................A-56 A.4.8 Converting an SNCP Service to a Normal Service............................................................................A-57 A.4.9 Querying TDM Services.....................................................................................................................A-58 A.4.10 Switching SNCP Services................................................................................................................A-59 A.4.11 Querying the Protection Status of SNCP Services...........................................................................A-59
A.5 Managing Ports............................................................................................................................................A-60 A.5.1 Setting the Parameters of SDH Ports..................................................................................................A-61 A.5.2 Setting the Parameters of PDH Ports..................................................................................................A-62 A.5.3 Configuring Overhead Bytes..............................................................................................................A-62 A.5.3.1 Configuring RSOHs........................................................................................................................A-63 A.5.3.2 Configuring VC-4 POHs.................................................................................................................A-64 A.5.3.3 Configuring VC-12 POHs...............................................................................................................A-65 A.5.4 Setting Smart E1 Port Parameters......................................................................................................A-66 A.5.4.1 Setting Basic Attributes of Smart E1 Ports.....................................................................................A-66 A.5.4.2 Setting Advanced Attributes of Smart E1 Ports..............................................................................A-67 A.5.5 Setting Serial Port Parameters............................................................................................................A-68 A.5.5.1 Creating Serial Ports........................................................................................................................A-68 A.5.5.2 Setting Basic Attributes of Serial Ports...........................................................................................A-69 A.5.6 Setting the Parameters of Ethernet Ports............................................................................................A-70 A.5.6.1 Setting the General Attributes of Ethernet Ports.............................................................................A-70 A.5.6.2 Configuring the Traffic Control of Ethernet Ports..........................................................................A-71 A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports.............................................................................A-72 A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports...................................................................................A-73 A.5.6.5 Setting the Advanced Attributes of Ethernet Ports..........................................................................A-74 A.5.7 Setting Parameters of the IF_ETH Port..............................................................................................A-75 A.5.7.1 Setting the General Attributes of the IF_ETH Port.........................................................................A-75 A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port.........................................................................A-76 A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports....................................................................................A-77 A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port.....................................................................A-78 A.5.8 Setting Parameters of IF Ports............................................................................................................A-78 A.5.8.1 Setting IF Attributes........................................................................................................................A-79 A.5.8.2 Configuring the ATPC Attributes...................................................................................................A-81 A.5.8.3 Setting Advanced AM Attributes....................................................................................................A-82 A.5.8.4 Querying the AM Status..................................................................................................................A-82 A.5.8.5 Querying the ATPC Adjustment Records.......................................................................................A-83 A.5.8.6 Modifying the Hybrid/AM Attributes.............................................................................................A-84 A.5.9 Setting the Parameters of ODU Ports.................................................................................................A-86 A.5.9.1 Setting the Transmit Frequency Attribute of the ODU...................................................................A-87 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
A.5.9.2 Querying the ODU Attribute...........................................................................................................A-87 A.5.9.3 Setting the Power Attributes of the ODU........................................................................................A-88 A.5.9.4 Setting the Advanced Attributes of the ODU..................................................................................A-89 A.5.9.5 Setting the State of an ODU Transmitter........................................................................................A-90 A.5.9.6 Querying the History Transmit Power and Receive Power.............................................................A-91 A.6 Configuring Ethernet Services and Features on the Packet Plane...............................................................A-91 A.6.1 Managing the ERPS ..........................................................................................................................A-92 A.6.1.1 Creating Ethernet Ring Protection Instances...................................................................................A-92 A.6.1.2 Setting the Parameters of Ethernet Ring Protocol...........................................................................A-93 A.6.1.3 Querying the Status of the Ethernet Ring Protocol.........................................................................A-94 A.6.2 Managing the LAG.............................................................................................................................A-94 A.6.2.1 Creating a LAG...............................................................................................................................A-95 A.6.2.2 Setting Parameters for LAGs...........................................................................................................A-97 A.6.2.3 Querying the Protocol Information of the LAG..............................................................................A-97 A.6.3 Configuring Ethernet Services...........................................................................................................A-98 A.6.3.1 Configuring the QinQ Link.............................................................................................................A-99 A.6.3.2 Configuring UNI-UNI E-Line Services........................................................................................A-100 A.6.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)................................................A-101 A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)................................................A-103 A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)...........................................................A-105 A.6.3.6 Creating a VLAN Forwarding Table Item....................................................................................A-107 A.6.3.7 Configuring TPID for a Request VLAN.......................................................................................A-108 A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services...........................................................A-108 A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services...........................................................A-110 A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services........................................................A-111 A.6.3.11 Changing Logical Ports Connected to a VB................................................................................A-113 A.6.3.12 Deleting an E-Line Service.........................................................................................................A-113 A.6.3.13 Deleting E-LAN Services............................................................................................................A-114 A.6.4 Managing the MAC Address Table..................................................................................................A-114 A.6.4.1 Creating a Static MAC Address Entry..........................................................................................A-115 A.6.4.2 Creating a Blacklist Entry of MAC Addresses..............................................................................A-116 A.6.4.3 Configuring the Aging Parameters of a MAC Address Table.......................................................A-116 A.6.4.4 Querying or Deleting a Dynamic MAC Address..........................................................................A-117 A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service..................................A-118 A.6.6 Managing the MSTP.........................................................................................................................A-118 A.6.6.1 Creating the MSTP Port Group.....................................................................................................A-119 A.6.6.2 Setting the Bridge Parameters of the MSTP..................................................................................A-120 A.6.6.3 Setting the Parameters of the CIST...............................................................................................A-121 A.6.6.4 Querying the CIST Running Information......................................................................................A-122 A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group....................................................A-123 A.6.6.6 Enabling/Disabling the MSTP Protocol........................................................................................A-123 A.6.6.7 Modifying the Configuration Data of the MSTP Port Group........................................................A-124 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) A.6.7 Managing the QoS............................................................................................................................A-125 A.6.7.1 Creating a DS Domain...................................................................................................................A-126 A.6.7.2 Modifying the Mapping Relationships for the DS Domain..........................................................A-128 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types............................A-129 A.6.7.4 Creating a Port Policy....................................................................................................................A-131 A.6.7.5 Modifying the Port Policy.............................................................................................................A-133 A.6.7.6 Creating the Traffic.......................................................................................................................A-133 A.6.7.7 Setting the Port That Uses the Port Policy....................................................................................A-135 A.6.7.8 Configuring Port Shaping..............................................................................................................A-136 A.6.7.9 Querying the Port Policy...............................................................................................................A-137 A.6.7.10 Querying the DS Domain of a Port.............................................................................................A-138 A.6.8 Using the IEEE 802.1ag OAM.........................................................................................................A-139 A.6.8.1 Creating an MD.............................................................................................................................A-140 A.6.8.2 Creating an MA.............................................................................................................................A-140 A.6.8.3 Creating an MEP Point..................................................................................................................A-141 A.6.8.4 Creating Remote MEPs in an MA.................................................................................................A-142 A.6.8.5 Creating an MIP............................................................................................................................A-143 A.6.8.6 Performing a CC Test....................................................................................................................A-144 A.6.8.7 Performing an LB Test..................................................................................................................A-145 A.6.8.8 Performing an LT Test..................................................................................................................A-146 A.6.8.9 Activating the AIS.........................................................................................................................A-147 A.6.9 Using the IEEE 802.3ah OAM ........................................................................................................A-148 A.6.9.1 Enabling the OAM Auto-Discovery Function..............................................................................A-148 A.6.9.2 Enabling the Remote Alarm Support for Link Event....................................................................A-149 A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold ............................................................A-150 A.6.9.4 Performing Remote Loopback......................................................................................................A-151 A.6.9.5 Enabling Self-Loop Detection ......................................................................................................A-153 A.6.10 LPT Configuration..........................................................................................................................A-153 A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network......................................................A-154 A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network.......................................A-155 A.6.10.3 Configuring Point-to-Multipoint LPT.........................................................................................A-155 A.6.10.4 Configuring Simple LPT.............................................................................................................A-156
A.7 Configuring Ethernet Services and Features on the EoPDH Plane...........................................................A-157 A.7.1 Managing LAGs ..............................................................................................................................A-158 A.7.1.1 Creating a LAG.............................................................................................................................A-158 A.7.1.2 Setting Parameters for LAGs.........................................................................................................A-160 A.7.1.3 Querying the Protocol Information of LAGs................................................................................A-161 A.7.2 Configuring Ethernet Services.........................................................................................................A-161 A.7.2.1 Creating Ethernet Private Line Services........................................................................................A-162 A.7.2.2 Creating Ethernet LAN Services...................................................................................................A-164 A.7.2.3 Changing the Ports Connected to a VB.........................................................................................A-168 A.7.2.4 Creating the VLAN Filtering Table..............................................................................................A-169 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
A.7.2.5 Creating QinQ-Based EVPL Services...........................................................................................A-170 A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services............................................................A-172 A.7.2.7 Deleting an Ethernet Private Line Service....................................................................................A-175 A.7.2.8 Deleting an Ethernet LAN Service................................................................................................A-175 A.7.3 Managing the MAC Address Table..................................................................................................A-176 A.7.3.1 Creating a Static MAC Address Entry..........................................................................................A-177 A.7.3.2 Creating a Blacklist Entry of a MAC Address..............................................................................A-177 A.7.3.3 Setting the Aging Time of a MAC Address Table Entry .............................................................A-178 A.7.3.4 Querying or Deleting a Dynamic MAC Address..........................................................................A-179 A.7.3.5 Querying the Actual Capacity of a MAC Address Table..............................................................A-179 A.7.4 Configuring Ethernet Ports...............................................................................................................A-180 A.7.4.1 Configuring External Ethernet Ports.............................................................................................A-181 A.7.4.2 Configuring VCTRUNKs on an Ethernet Board...........................................................................A-182 A.7.4.3 Modifying the Type Field of QinQ Frames...................................................................................A-184 A.7.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth.................................................A-185 A.7.5 Managing the Spanning Tree Protocol.............................................................................................A-186 A.7.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol....................................A-187 A.7.5.2 Setting the Parameters of Spanning Tree Protocol........................................................................A-187 A.7.5.3 Querying the Running Information About the Spanning Tree Protocol.......................................A-188 A.7.6 Managing the IGMP Snooping Protocol..........................................................................................A-189 A.7.6.1 Configuring the IGMP Snooping Protocol....................................................................................A-189 A.7.6.2 Configuring Static Multicast Entries.............................................................................................A-190 A.7.6.3 Modifying the Aging Time of a Multicast Table Entry................................................................A-191 A.7.6.4 Querying the Running Information of the IGMP Snooping Protocol...........................................A-192 A.7.7 Managing the QoS............................................................................................................................A-193 A.7.7.1 Creating a Flow.............................................................................................................................A-193 A.7.7.2 Creating the CAR..........................................................................................................................A-194 A.7.7.3 Creating the CoS............................................................................................................................A-195 A.7.7.4 Binding the CAR/CoS...................................................................................................................A-197 A.7.7.5 Configuring Traffic Shaping for Egress Queues...........................................................................A-198 A.7.8 Using the IEEE 802.1ag OAM ........................................................................................................A-198 A.7.8.1 Creating MDs................................................................................................................................A-199 A.7.8.2 Creating MAs................................................................................................................................A-200 A.7.8.3 Creating MPs.................................................................................................................................A-201 A.7.8.4 Performing a CC Test....................................................................................................................A-203 A.7.8.5 Performing an LB Test..................................................................................................................A-203 A.7.8.6 Performing an LT Test..................................................................................................................A-205 A.7.8.7 Activating the AIS.........................................................................................................................A-206 A.7.8.8 Performing a Ping Test .................................................................................................................A-206 A.7.8.9 Performing Performance Check....................................................................................................A-207 A.7.9 Using the IEEE 802.3ah OAM.........................................................................................................A-208 A.7.9.1 Enabling the OAM Auto-Discovery Function..............................................................................A-208 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) A.7.9.2 Enabling the Link Event Notification............................................................................................A-209 A.7.9.3 Modifying the OAM Error Frame Monitoring Threshold.............................................................A-210 A.7.9.4 Performing the Remote Loopback.................................................................................................A-211 A.7.10 Configuring LPT............................................................................................................................A-212 A.7.10.1 Configuring LPT for Point-to-Point Services..............................................................................A-212 A.7.10.2 Configuring LPT for Point-to-Multipoint Services.....................................................................A-213
A.8 Managing MPLS/PWE3 Services and Features........................................................................................A-215 A.8.1 Managing Address Resolution.........................................................................................................A-216 A.8.1.1 Creating ARP Static Entries..........................................................................................................A-216 A.8.1.2 Querying ARP Entries...................................................................................................................A-217 A.8.1.3 Converting Dynamic ARP Entries to Static ARP Entries.............................................................A-217 A.8.1.4 Deleting Static ARP Entries..........................................................................................................A-218 A.8.1.5 Setting ARP Aging Time...............................................................................................................A-218 A.8.2 Managing MPLS Tunnels.................................................................................................................A-219 A.8.2.1 Setting Basic MPLS Attributes.....................................................................................................A-220 A.8.2.2 Creating a Unidirectional MPLS Tunnel.......................................................................................A-220 A.8.2.3 Creating a Bidirectional MPLS Tunnel.........................................................................................A-222 A.8.2.4 Querying MPLS Tunnel Information............................................................................................A-223 A.8.2.5 Deleting MPLS Tunnels................................................................................................................A-224 A.8.2.6 Setting MPLS OAM Parameters...................................................................................................A-224 A.8.2.7 Enabling/Disabling FDI.................................................................................................................A-225 A.8.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels............................................................A-226 A.8.2.9 Querying LSP Running Status.......................................................................................................A-226 A.8.2.10 Clearing OAM Configuration Data for MPLS Tunnels..............................................................A-227 A.8.2.11 Performing an LSP Ping Test......................................................................................................A-228 A.8.2.12 Performing an LSP Traceroute Test............................................................................................A-229 A.8.3 Managing MPLS APS Protection Groups........................................................................................A-230 A.8.3.1 Creating an MPLS APS Protection Group....................................................................................A-230 A.8.3.2 Querying MPLS APS Status.........................................................................................................A-231 A.8.3.3 Triggering MPLS APS Switching.................................................................................................A-232 A.8.3.4 Enabling/Disabling MPLS APS Protection...................................................................................A-233 A.8.4 Managing PWs.................................................................................................................................A-234 A.8.4.1 Querying Information and Running Status of PWs.......................................................................A-234 A.8.4.2 Creating an MS-PW......................................................................................................................A-235 A.8.4.3 Setting PW OAM Parameters........................................................................................................A-237 A.8.4.4 Performing a PW Ping Test...........................................................................................................A-237 A.8.4.5 Performing a PW Traceroute Test.................................................................................................A-238 A.8.5 Managing a PW APS Protection Group...........................................................................................A-239 A.8.5.1 Creating a PW APS Protection Group...........................................................................................A-239 A.8.5.2 Configuring Slave Protection Pairs of PW APS............................................................................A-242 A.8.5.3 Querying PW APS Status..............................................................................................................A-243 A.8.5.4 Triggering PW APS Switching.....................................................................................................A-244 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
A.8.5.5 Enabling/Disabling PW APS Protection.......................................................................................A-245 A.8.6 Managing CES Services...................................................................................................................A-246 A.8.6.1 Creating CES Services..................................................................................................................A-246 A.8.6.2 Modifying CES Service Parameters..............................................................................................A-248 A.8.6.3 Querying CES Service Information...............................................................................................A-249 A.8.6.4 Deleting a CES Service.................................................................................................................A-250 A.8.7 Managing ATM/IMA Ports..............................................................................................................A-250 A.8.7.1 Binding ATM TRUNKs................................................................................................................A-250 A.8.7.2 Configuring an IMA group ...........................................................................................................A-252 A.8.7.3 Setting ATM Port Parameters.......................................................................................................A-253 A.8.7.4 Querying Running Status of an IMA Group.................................................................................A-253 A.8.7.5 Querying Link Running Status of an IMA Group.........................................................................A-254 A.8.8 Managing ATM Services.................................................................................................................A-254 A.8.8.1 Creating ATM Services.................................................................................................................A-255 A.8.8.2 Modifying ATM Service Parameters............................................................................................A-257 A.8.8.3 Querying ATM Services................................................................................................................A-258 A.8.8.4 Deleting an ATM Service..............................................................................................................A-258 A.8.9 ATM Traffic Management...............................................................................................................A-259 A.8.9.1 Creating an ATM-DiffServ Domain.............................................................................................A-259 A.8.9.2 Modifying an ATM-Diffserv Domain...........................................................................................A-260 A.8.9.3 Creating an ATM Policy...............................................................................................................A-261 A.8.9.4 Modifying an ATM Policy............................................................................................................A-262 A.8.10 Using ATM OAM..........................................................................................................................A-263 A.8.10.1 Setting Segment and End Attributes of AIS/RDI........................................................................A-263 A.8.10.2 Performing a Continuity Check Test...........................................................................................A-264 A.8.10.3 Querying or Setting LLIDs..........................................................................................................A-264 A.8.10.4 Performing an LB Test................................................................................................................A-265 A.9 Managing the Clock..................................................................................................................................A-266 A.9.1 Managing Clocks at the Physical Layer...........................................................................................A-266 A.9.1.1 Configuring the Clock Sources.....................................................................................................A-267 A.9.1.2 Configuring Clock Subnets...........................................................................................................A-268 A.9.1.3 Self-Defined Clock Quality...........................................................................................................A-269 A.9.1.4 Configuring the SSM Output Status..............................................................................................A-270 A.9.1.5 Configuring the Clock ID Output Status.......................................................................................A-271 A.9.1.6 Modifying the Parameters of the Clock Output............................................................................A-272 A.9.1.7 Configuring Clock Sources for External Clock Output................................................................A-272 A.9.1.8 Changing the Conditions for Clock Source Switching..................................................................A-273 A.9.1.9 Modifying the Recovery Parameter of the Clock Source..............................................................A-274 A.9.1.10 Querying the Clock Synchronization Status................................................................................A-275 A.9.2 Managing CES ACR Clocks............................................................................................................A-275 A.9.2.1 Configuring the Primary Clock for an ACR Clock Domain.........................................................A-275 A.9.2.2 Configuring Ports Using the Clock Domain.................................................................................A-276 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Contents
A.10 Using the RMON.....................................................................................................................................A-278 A.10.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.................................A-278 A.10.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-279 A.10.3 Configuring a History Control Group............................................................................................A-280 A.10.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-281 A.11 Configuring Auxiliary Ports and Functions............................................................................................A-282 A.11.1 Configuring Orderwire...................................................................................................................A-283 A.11.2 Configuring the Synchronous Data Service...................................................................................A-284 A.11.3 Configuring the Asynchronous Data Service.................................................................................A-284 A.11.4 Configuring the Wayside E1 Service.............................................................................................A-285 A.11.5 Configure External Alarms.............................................................................................................A-286 A.11.6 Monitoring the Outdoor Cabinet....................................................................................................A-287 A.11.6.1 Configuring the Function of an Auxiliary Port ..........................................................................A-288 A.11.6.2 Setting the Type of the Outdoor Cabinet.....................................................................................A-289 A.11.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet................A-290 A.11.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet..........A-291 A.11.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet...............................A-292 A.11.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU....................................A-292 A.12 Verifying Services and Features..............................................................................................................A-293 A.12.1 Testing E1 Services Using PRBS...................................................................................................A-294 A.12.2 Testing E1 Services by Using a BER Tester..................................................................................A-295 A.12.3 Testing Ethernet Services...............................................................................................................A-297 A.12.4 Testing ATM Services....................................................................................................................A-301 A.12.5 Testing AM Switching...................................................................................................................A-303 A.12.5.1 Testing AM Switching by Using a BER Tester..........................................................................A-303 A.12.5.2 Testing AM Switching Without a BER Tester............................................................................A-305 A.12.6 Testing Protection Switching.........................................................................................................A-307 A.12.6.1 Testing IF 1+1 Switching............................................................................................................A-307 A.12.6.2 Testing N+1 Protection Switching..............................................................................................A-311 A.12.6.3 Testing SNCP Switching.............................................................................................................A-313 A.12.6.4 Testing ERPS Switching.............................................................................................................A-317 A.12.6.5 Testing MPLS APS Protection Switching...................................................................................A-319 A.12.6.6 Testing Linear MSP Switching...................................................................................................A-321 A.12.6.7 Switching the System Control Unit and the Cross-Connect Unit...............................................A-324
B Parameters Description............................................................................................................B-1
B.1 Parameters for Network Management...........................................................................................................B-2 B.1.1 Parameters for NE Management...........................................................................................................B-2 B.1.1.1 Parameter Description: NE Searching...............................................................................................B-2 B.1.1.2 Parameter Description: NE Creation.................................................................................................B-4 B.1.1.3 Parameter Description: Login to an NE.............................................................................................B-5 B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs..................................................................B-6 B.1.1.5 Parameter Description: NE Time Synchronization............................................................................B-7 xxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
B.1.1.6 Parameter Description: Localization Management of the NE Time................................................B-12 B.1.1.7 Parameter Description: License Management.................................................................................B-13 B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs...........................................B-13 B.1.2 Parameters for Communications Management...................................................................................B-14 B.1.2.1 Parameter Description: NE Communication Parameter Setting......................................................B-15 B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration............................................B-16 B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management...........B-18 B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC......................................B-19 B.1.2.5 Parameter Description: NE ECC Link Management.......................................................................B-21 B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management............................B-22 B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation.............B-24 B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings.......................B-24 B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP...................................................................B-28 B.1.2.10 Parameter Description: Port OSPF Setting....................................................................................B-29 B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter..........................................B-30 B.1.2.12 Parameter Description: OSI Management_Routing Table............................................................B-31 B.1.2.13 Parameter Description: OSI Management_OSI Tunnel.................................................................B-32 B.1.2.14 Parameter Description: DCN Management_Bandwidth Management..........................................B-36 B.1.2.15 Parameter Description: DCN Management_Port Setting..............................................................B-36 B.1.2.16 Parameter Description: DCN Management_Protocol Setting.......................................................B-37 B.1.2.17 Parameter Description: DCN Management_Access Control.........................................................B-38 B.1.2.18 Parameter Description: Access Control.........................................................................................B-38 B.1.3 Parameters for Network Security Management..................................................................................B-40 B.1.3.1 Parameter Description: NE User Management................................................................................B-40 B.1.3.2 Parameter Description: NE User Management_Creation................................................................B-41 B.1.3.3 Parameter Description: LCT Access Control..................................................................................B-43 B.2 Radio Link Parameters.................................................................................................................................B-43 B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation.........................................B-44 B.2.2 Parameter Description: Link Configuration_XPIC............................................................................B-48 B.2.3 Parameter Description: N+1 Protection_Create..................................................................................B-55 B.2.4 Parameter Description: N+1 Protection..............................................................................................B-56 B.2.5 Parameter: IF 1+1 Protection_Create..................................................................................................B-58 B.2.6 Parameter Description: IF 1+1 Protection..........................................................................................B-60 B.2.7 Parameter: Link Configuration_IF/ODU Configuration....................................................................B-63 B.3 Multiplex Section Protection Parameters.....................................................................................................B-73 B.3.1 Parameter Description: Linear MSP_Creation...................................................................................B-73 B.3.2 Parameter Description: Linear MSP...................................................................................................B-77 B.4 SDH/PDH Service Parameters.....................................................................................................................B-81 B.4.1 Parameter Description: SDH Service Configuration_Creation..........................................................B-81 B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation..................................B-84 B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services ......................................................................................................................................................................B-88 B.4.4 Parameter Description: SDH Service Configuration..........................................................................B-91 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) B.4.5 Parameter Description: SNCP Service Control..................................................................................B-93 B.4.6 Parameter Description: TU_AIS Insertion..........................................................................................B-96
B.5 Parameters for Board Interfaces...................................................................................................................B-97 B.5.1 PDH Port Parameters..........................................................................................................................B-97 B.5.1.1 Parameter Description: PDH Ports_Basic Attributes......................................................................B-98 B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes...............................................................B-99 B.5.2 Parameters for the Ports on Ethernet Boards....................................................................................B-103 B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes.........................................................B-103 B.5.2.2 Parameter Description: Ethernet Interface_Flow Control.............................................................B-108 B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes......................................................B-109 B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes.............................................................B-112 B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes..................................................B-114 B.5.3 Serial Port Parameters.......................................................................................................................B-116 B.5.3.1 Parameter Description: Serial Port_Basic Attributes.....................................................................B-117 B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports.........................................................B-118 B.5.4 Microwave Interface Parameters......................................................................................................B-119 B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes....................................................B-119 B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes.................................................B-120 B.5.4.3 Parameter Description: Microwave Interface_Layer 3 Attributes.................................................B-122 B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes.............................................B-124 B.5.5 IF Board Parameters.........................................................................................................................B-127 B.5.5.1 Parameter Description: IF Interface_IF Attribute..........................................................................B-128 B.5.5.2 Parameter Description: IF Interface_ATPC Attribute...................................................................B-135 B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes...................................B-136 B.5.5.4 Parameter Description: ATPC Adjustment Records......................................................................B-137 B.5.5.5 Parameter Description: PRBS Test................................................................................................B-138 B.5.6 ODU Parameters...............................................................................................................................B-139 B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute.............................................B-140 B.5.6.2 Parameter Description: ODU Interface_Power Attributes.............................................................B-141 B.5.6.3 Parameter Description: ODU Interface_Equipment Information..................................................B-145 B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes.......................................................B-147 B.5.7 Parameters for SDH Interface Boards...............................................................................................B-148 B.5.7.1 Parameter Description: SDH Interfaces.........................................................................................B-148 B.5.7.2 Parameter Description: Automatic Laser Shutdown......................................................................B-150 B.5.8 Parameters for PDH Interface Boards...............................................................................................B-150 B.5.8.1 Parameter Description: PDH Interfaces.........................................................................................B-151 B.5.8.2 Parameter Description: PRBS Test................................................................................................B-153 B.5.9 Parameters for Overhead...................................................................................................................B-154 B.5.9.1 Parameter Description: Regenerator Section Overhead.................................................................B-154 B.5.9.2 Parameter Description: VC-4 POHs..............................................................................................B-155 B.5.9.3 Parameter Description: VC-12 POHs............................................................................................B-157 B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane...........................................B-158 xxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Contents
B.6.1 Parameters for Ethernet Services......................................................................................................B-158 B.6.1.1 Parameter Description: E-Line Service_Creation..........................................................................B-159 B.6.1.2 Parameter Description: E-Line Service..........................................................................................B-180 B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation.................................................B-191 B.6.1.4 Parameter Description: E-LAN Service_Creation.........................................................................B-192 B.6.1.5 Parameter Description: E-LAN Service.........................................................................................B-203 B.6.1.6 Parameter Description: QinQ Link_Creation................................................................................B-215 B.6.2 Parameters for Ethernet Protocols....................................................................................................B-216 B.6.2.1 Parameter Description: ERPS Management_Creation..................................................................B-216 B.6.2.2 Parameter Description: ERPS Management..................................................................................B-218 B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation.............................................B-224 B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration....................................B-226 B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters...............................................B-226 B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters..................................................B-232 B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST.................B-234 B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation........................B-242 B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation........................................B-249 B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT..................................................B-250 B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT...................................B-253 B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT.........................................B-253 B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT..........................B-256 B.6.3 Parameters for the Ethernet OAM....................................................................................................B-260 B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation ....................................................................................................................................................................B-261 B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation ....................................................................................................................................................................B-262 B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..............................B-263 B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation................B-265 B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation...............................B-265 B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling................................B-266 B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.................................B-268 B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter................................B-270 B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring.........B-271 B.6.4 QoS Parameters.................................................................................................................................B-273 B.6.4.1 Parameter Description: Diffserv Domain Management.................................................................B-273 B.6.4.2 Parameter Description: DiffServ Domain Management_Create...................................................B-279 B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification.........................................B-286 B.6.4.4 Parameter Description: Policy Management.................................................................................B-288 B.6.4.5 Parameter Description: Port Policy................................................................................................B-293 B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration....................................B-298 B.6.4.7 Parameter Description: Port Shaping Management_Creation.......................................................B-309 B.7 Parameters for Ethernet Services and Ethernet Features on the EoPDH Plane.........................................B-311 B.7.1 Parameters for Ethernet Services......................................................................................................B-311 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) B.7.1.1 Parameter Description: Ethernet Line Service_Creation...............................................................B-312 B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services.....B-315 B.7.1.3 Parameter Description: Ethernet Line Service...............................................................................B-319 B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/802.1q Bridge.................................................................................................................................B-321 B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service........................................................................................................................................................B-325 B.7.1.6 Parameter Description: Ethernet LAN Service..............................................................................B-330 B.7.1.7 Parameter Description: VLAN Filtering Table_Creation..............................................................B-335 B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries...........................................B-337 B.7.2 Parameters for Ethernet Protocols....................................................................................................B-337 B.7.2.1 Parameter Description: Spanning Tree_Protocol Enabling...........................................................B-338 B.7.2.2 Parameter Description: Spanning Tree_Bridge Parameters...........................................................B-339 B.7.2.3 Parameter Description: Spanning Tree_Port Parameters...............................................................B-341 B.7.2.4 Parameter Description: Spanning Tree_Bridge Running Information..........................................B-342 B.7.2.5 Parameter Description: Spanning Tree_Port Running Information...............................................B-343 B.7.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute..................................................B-344 B.7.2.7 Parameter Description: IGMP Snooping Protocol_Enabling........................................................B-345 B.7.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries....B-347 B.7.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries........B-347 B.7.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs......................................B-348 B.7.2.11 Parameter Description: Ethernet Link Aggregation_Link Aggregation......................................B-350 B.7.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT..................B-351 B.7.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT.........B-352 B.7.2.14 Parameter Description: Port Mirroring_Creation........................................................................B-353 B.7.3 Parameters for the Ethernet OAM....................................................................................................B-354 B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs................................................B-355 B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs................................................B-356 B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs................................................B-357 B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB......................................................B-359 B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT......................................................B-360 B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter......................................................B-361 B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring...............................B-362 B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter........................................B-363 B.7.4 QoS Parameters.................................................................................................................................B-364 B.7.4.1 Parameter Description: QoS Management_Creation of Flows......................................................B-365 B.7.4.2 Parameter Description: QoS Management_Creation of CAR.......................................................B-367 B.7.4.3 Parameter Description: QoS Management_Creation of CoS.........................................................B-369 B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS...............................................B-371 B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues...................B-372 B.7.5 Parameters for the Ports on Ethernet Boards....................................................................................B-373 B.7.5.1 Parameter Description: Ethernet Port_External Port.....................................................................B-373 B.7.5.2 Parameter Description: Ethernet Port_Internal Port......................................................................B-379
xxx
Issue 03 (2011-04-10)
Contents
B.7.5.3 Parameter Description: Type Field of QinQ Frames.....................................................................B-385 B.8 RMON Parameters.....................................................................................................................................B-385 B.8.1 Parameter Description: RMON Performance_Statistics Group........................................................B-386 B.8.2 Parameter Description: RMON Performance_History Group..........................................................B-386 B.8.3 Parameter Description: RMON Performance_History Control Group.............................................B-387 B.8.4 Parameter Description: RMON Performance_RMON Setting.........................................................B-388 B.9 Parameters for MPLS/PWE3 Services.......................................................................................................B-389 B.9.1 MPLS Tunnel Parameters.................................................................................................................B-389 B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels..................................................B-390 B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel............................................B-391 B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels.........B-396 B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels...........B-400 B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters.....................................B-405 B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI...........................................................B-410 B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping..................................................B-411 B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute........................................B-414 B.9.1.9 Parameter Description: PW Management_PW Management........................................................B-417 B.9.1.10 Parameter Description: PW Management_MS-PW Creation......................................................B-422 B.9.1.11 Parameter Description: PW Management_PW OAM.................................................................B-433 B.9.1.12 Parameter Description: PW Management_PW Ping...................................................................B-437 B.9.1.13 Parameter Description: PW Management_PW Traceroute.........................................................B-440 B.9.1.14 Parameter Description: MPLS APS Protection Management.....................................................B-443 B.9.1.15 Parameter Description: Tunnel Protection Group_Creation........................................................B-446 B.9.1.16 Parameter Description: PW APS Protection Group_Creation.....................................................B-451 B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation...........B-461 B.9.2 CES Parameters................................................................................................................................B-467 B.9.2.1 Parameter Description: CES Service Management.......................................................................B-467 B.9.2.2 Parameter Description: CES Service Management_Creation........................................................B-476 B.9.3 ATM Parameters...............................................................................................................................B-491 B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management...............................B-492 B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration..............................B-497 B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status..........................................B-499 B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status.............................................B-500 B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management..........................B-501 B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table.............................B-502 B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation.............B-504 B.9.3.8 Parameter Description: ATM Policy Management........................................................................B-506 B.9.3.9 Parameter Description: ATM Policy Management_Creation........................................................B-511 B.9.3.10 Parameter Description: ATM Service Management....................................................................B-516 B.9.3.11 Parameter Description: ATM Service Management_Creation....................................................B-525 B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes.......................B-537 B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status..................................B-540 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Contents
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status.....................B-544 B.9.3.15 Parameter Description: ATM OAM Management_LLID...........................................................B-547
B.10 Clock Parameters.....................................................................................................................................B-548 B.10.1 Physical Clock Parameters..............................................................................................................B-548 B.10.1.1 Parameter Description: Clock Source Priority Table...................................................................B-549 B.10.1.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port ....................................................................................................................................................................B-551 B.10.1.3 Parameter Description: Clock Subnet Setting_Clock Subnet......................................................B-553 B.10.1.4 Parameter Description: Clock Subnet Setting_Clock Quality.....................................................B-556 B.10.1.5 Parameter Description: Clock Subset Setting_SSM Output Control...........................................B-559 B.10.1.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status...................................B-560 B.10.1.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters...........B-562 B.10.1.8 Parameter Description: Clock Source Switching_Clock Source Switching................................B-564 B.10.1.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions.............B-565 B.10.1.10 Parameter Description: Output Phase-Locked Source of the External Clock Source...............B-567 B.10.1.11 Parameter Description: Clock Synchronization Status..............................................................B-569 B.10.2 CES ACR Clock Parameters...........................................................................................................B-571 B.10.2.1 Parameter Description: ACR Clock Source.................................................................................B-571 B.10.2.2 Parameter Description: Clock Domain........................................................................................B-571 B.10.2.3 Parameter Description: Clock Domain_Creation........................................................................B-572 B.10.3 Parameter Description: Auxiliary Ports..........................................................................................B-573 B.11 Parameters for the Orderwire and Auxiliary Interfaces...........................................................................B-573 B.11.1 Parameter Description: Orderwire_General....................................................................................B-574 B.11.2 Parameter Description: Orderwire_Advanced................................................................................B-576 B.11.3 Parameter Description: Orderwire_F1 Data Port............................................................................B-576 B.11.4 Parameter Description: Orderwire_Broadcast Data Port................................................................B-577 B.11.5 Parameter Description: Environment Monitoring Interface...........................................................B-578
C Glossary......................................................................................................................................C-1
C.1 0-9..................................................................................................................................................................C-2 C.2 A-E.................................................................................................................................................................C-2 C.3 F-J................................................................................................................................................................C-11 C.4 K-O..............................................................................................................................................................C-16 C.5 P-T................................................................................................................................................................C-22 C.6 U-Z...............................................................................................................................................................C-31
xxxii
Issue 03 (2011-04-10)
Figures
Figures
Figure 2-1 Configuration flow chart (initial configuration).................................................................................2-2 Figure 3-1 Overall topology of the TDM radio network......................................................................................3-2 Figure 3-2 Topology of a TDM radio chain network...........................................................................................3-3 Figure 3-3 Board configuration of NEs on a TDM radio chain network.............................................................3-3 Figure 3-4 Topology of a TDM radio ring network.............................................................................................3-4 Figure 3-5 Board configuration of NEs on a TDM radio ring network...............................................................3-4 Figure 3-6 Overall topology of the IP radio network...........................................................................................3-5 Figure 3-7 Topology of a packet network............................................................................................................3-6 Figure 3-8 Board configuration of NEs on a packet network..............................................................................3-6 Figure 3-9 Topology of a Hybrid radio chain network .......................................................................................3-7 Figure 3-10 Board configuration of NEs on a Hybrid radio chain network.........................................................3-8 Figure 3-11 Topology of a Hybrid radio ring network .......................................................................................3-8 Figure 3-12 Board configuration of NEs on a Hybrid radio ring network...........................................................3-9 Figure 4-1 HWECC solution................................................................................................................................4-3 Figure 4-2 Inband DCN solution..........................................................................................................................4-3 Figure 4-3 Configuration flow chart (network topology).....................................................................................4-6 Figure 4-4 Networking diagram (TDM radio chain network)............................................................................4-12 Figure 4-5 Allocated IDs and IP addresses (TDM radio chain network)...........................................................4-13 Figure 4-6 Networking diagram (TDM radio ring network)..............................................................................4-16 Figure 4-7 Allocated IDs and IP addresses (TDM radio ring network).............................................................4-17 Figure 4-8 Networking diagram (Hybrid radio chain network).........................................................................4-20 Figure 4-9 Allocated IDs and IP addresses (Hybrid radio chain network)........................................................4-21 Figure 4-10 Networking diagram (Hybrid radio ring network).........................................................................4-23 Figure 4-11 Allocated IDs and IP addresses (Hybrid radio ring network).........................................................4-24 Figure 4-12 Networking diagram (packet network)...........................................................................................4-27 Figure 4-13 Allocated IDs and IP addresses (packet network)..........................................................................4-29 Figure 5-1 Adaptive modulation..........................................................................................................................5-3 Figure 5-2 Single-polarized transmission.............................................................................................................5-4 Figure 5-3 CCDP transmission.............................................................................................................................5-4 Figure 5-4 Configuration flow chart (radio links)................................................................................................5-6 Figure 5-5 Networking diagram (TDM radio chain network)............................................................................5-15 Figure 5-6 Networking diagram (TDM radio ring network)..............................................................................5-26 Figure 5-7 Networking diagram (Hybrid radio chain network).........................................................................5-36 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Figures
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Figure 5-8 Networking diagram (Hybrid radio ring network)...........................................................................5-50 Figure 5-9 Networking diagram (Packet radio chain network)..........................................................................5-61 Figure 6-1 1+1 linear MSP...................................................................................................................................6-3
Figure 6-2 1:N linear MSP...................................................................................................................................6-4 Figure 6-3 SNCP..................................................................................................................................................6-5 Figure 6-4 Numbering VC-12 timeslots by order ...............................................................................................6-6 Figure 6-5 Numbering VC-12 timeslots in the interleaved scheme ....................................................................6-7 Figure 6-6 Timeslot allocation diagram...............................................................................................................6-8 Figure 6-7 Configuration flow chart (TDM services)........................................................................................6-11 Figure 6-8 Networking diagram (TDM services on a TDM radio chain network)............................................6-14 Figure 6-9 Timeslot allocation diagram (TDM services on the TDM radio chain network).............................6-16 Figure 6-10 Networking diagram (TDM services on a TDM radio ring network) ...........................................6-22 Figure 6-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)...............................6-23 Figure 6-12 Networking diagram (TDM services on a Hybrid radio chain network) .......................................6-30 Figure 6-13 Timeslot allocation diagram (TDM services on the Hybrid chain radio network).........................6-32 Figure 6-14 Networking diagram (TDM services on a Hybrid radio ring network) .........................................6-36 Figure 6-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)...........................6-38 Figure 7-1 Packet plane........................................................................................................................................7-5 Figure 7-2 Typical application of service model 1...............................................................................................7-9 Figure 7-3 VLAN-based E-Line service model.................................................................................................7-11 Figure 7-4 Typical application of service model 1.............................................................................................7-13 Figure 7-5 Typical application of service model 2.............................................................................................7-13 Figure 7-6 Typical application of service model 3.............................................................................................7-14 Figure 7-7 Typical application of service model 4.............................................................................................7-14 Figure 7-8 802.1D bridge-based E-LAN service model....................................................................................7-15 Figure 7-9 802.1Q bridge-based E-LAN service model....................................................................................7-16 Figure 7-10 Typical application of the 802.1ad bridge-based E-LAN service model.......................................7-18 Figure 7-11 Networking diagram of VLAN-based E-Line services..................................................................7-19 Figure 7-12 Networking diagram of IEEE 802.1d bridge-based E-LAN services.............................................7-20 Figure 7-13 Networking diagram of IEEE 802.1q bridge-based E-LAN services.............................................7-21 Figure 7-14 Application of the VLAN forwarding table in E-Line services.....................................................7-26 Figure 7-15 Split horizon group.........................................................................................................................7-26 Figure 7-16 Implementation of ERPS................................................................................................................7-28 Figure 7-17 LAG................................................................................................................................................7-29 Figure 7-18 Prevention of network loops on the access side.............................................................................7-30 Figure 7-19 Configuration flow chart (point-to-point transparently transmitted E-Line services)....................7-31 Figure 7-20 Configuration flow chart (VLAN-based E-Line services).............................................................7-38 Figure 7-21 Configuration flow chart (QinQ-based E-Line services)................................................................7-45 Figure 7-22 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)........................................7-53 Figure 7-23 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)........................................7-62 Figure 7-24 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)......................................7-70 Figure 7-25 Networking diagram (point-to-point transparently transmitted E-Line services)..........................7-78 xxxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Figures
Figure 7-26 Networking diagram (VLAN-based E-Line services)....................................................................7-88 Figure 7-27 Networking diagram (QinQ-based E-Line services)....................................................................7-109 Figure 7-28 Networking diagram (IEEE 802.1d bridge-based E-LAN services)............................................7-137 Figure 7-29 Networking diagram (IEEE 802.1q bridge-based E-LAN services)............................................7-158 Figure 7-30 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)..........................................7-185 Figure 7-31 Networking diagram.....................................................................................................................7-211 Figure 8-1 EoPDH plane......................................................................................................................................8-3 Figure 8-2 Hybrid radio........................................................................................................................................8-4 Figure 8-3 Typical application of the service model............................................................................................8-5 Figure 8-4 Typical application of service model 1...............................................................................................8-7 Figure 8-5 Typical application of service model 2...............................................................................................8-7 Figure 8-6 Typical application of service model 1...............................................................................................8-9 Figure 8-7 Typical application of service model 2...............................................................................................8-9 Figure 8-8 Typical application of service model 3.............................................................................................8-10 Figure 8-9 Typical application of service model 4.............................................................................................8-10 Figure 8-10 Model of EPLAN services based on the 802.1D bridge.................................................................8-11 Figure 8-11 Model of EVPLAN services based on the 802.1Q bridge..............................................................8-12 Figure 8-12 Model of EVPLAN services based on 802.1ad bridge...................................................................8-14 Figure 8-13 Configuration flow chart (point-to-point transparently transmitted EPL services)........................8-15 Figure 8-14 Configuration flow chart (VLAN-based EVPL services) .............................................................8-21 Figure 8-15 Configuration flow chart (QinQ-based EVPL services) ................................................................8-27 Figure 8-16 Configuration flow chart (802.1d bridge-based EPLAN services)................................................8-33 Figure 8-17 Configuration flow chart (IEEE 802.1q bridge-based EVPLAN services)....................................8-39 Figure 8-18 Configuration flow chart (IEEE 802.1ad bridge-based EVPLAN services)..................................8-46 Figure 8-19 Networking diagram (Ethernet services based on TDM radio)......................................................8-53 Figure 8-20 Board configuration (Ethernet services based on TDM radio) ......................................................8-53 Figure 8-21 Timeslot allocation diagram (Ethernet services based on TDM radio) .........................................8-61 Figure 8-22 Networking diagram (Ethernet services traversing a TDM network) ...........................................8-75 Figure 8-23 Board configuration (Ethernet services traversing a TDM network).............................................8-76 Figure 9-1 MPLS network architecture................................................................................................................9-2 Figure 9-2 Classification of LSRs on an LSP......................................................................................................9-3 Figure 9-3 MPLS APS.........................................................................................................................................9-6 Figure 9-4 Configuration flow chart (MPLS tunnels)..........................................................................................9-7 Figure 9-5 Networking diagram (packet ring network).....................................................................................9-13 Figure 9-6 MPLS tunnel planning .....................................................................................................................9-17 Figure 9-7 Networking diagram (Packet radio links).........................................................................................9-40 Figure 9-8 Networking diagram (Packet radio links).........................................................................................9-41 Figure 9-9 MPLS tunnel planning .....................................................................................................................9-44 Figure 10-1 Example of CES services...............................................................................................................10-4 Figure 10-2 Compression of idle 64 kbit/s timeslots in TDM E1 signals..........................................................10-5 Figure 10-3 Retiming synchronization mode of CES service clocks.................................................................10-5 Figure 10-4 Adaptive synchronization mode of CES service clocks.................................................................10-6 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Figures
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Figure 10-5 Example of ATM/IMA services ....................................................................................................10-6 Figure 10-6 Typical application of service model 1...........................................................................................10-8 Figure 10-7 Typical application of service model 2...........................................................................................10-9 Figure 10-8 Typical application of service model 3.........................................................................................10-10 Figure 10-9 MS-PW network reference model................................................................................................10-10 Figure 10-10 SS-PW application......................................................................................................................10-11
Figure 10-11 MS-PW application....................................................................................................................10-12 Figure 10-12 Configuration flow chart............................................................................................................10-13 Figure 10-13 Configuration flow chart (ATM services on a per-NE basis).....................................................10-17 Figure 10-14 configuration flow chart (E-Line services carried on PWs).......................................................10-23 Figure 10-15 Networking Diagram..................................................................................................................10-32 Figure 10-16 Networking Diagram..................................................................................................................10-39 Figure 10-17 Networking Diagram..................................................................................................................10-47 Figure 10-18 Networking diagram...................................................................................................................10-55 Figure 10-19 Networking diagram...................................................................................................................10-75 Figure 10-20 Networking diagram...................................................................................................................10-95 Figure 10-21 Networking diagram.................................................................................................................10-120 Figure 10-22 Networking diagram (E-Line services carried on PWs, a simple example).............................10-135 Figure 10-23 Networking diagram (E-Line services carried on PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network)..........................................................................................10-149 Figure 10-24 Networking diagram (E-Line services carried by PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network)..........................................................................................10-167 Figure 11-1 Clock source protection based on priorities....................................................................................11-3 Figure 11-2 SSM protection...............................................................................................................................11-4 Figure 11-3 Extended SSM protection...............................................................................................................11-6 Figure 11-4 Clock synchronization policy for a chain network.........................................................................11-7 Figure 11-5 Clock synchronization policy for a tree network............................................................................11-8 Figure 11-6 Clock synchronization policy for a ring network (on which only the SDH signal is transmitted) .............................................................................................................................................................................11-9 Figure 11-7 Clock synchronization policy for a ring network (on which not only the SDH signal is transmitted) ...........................................................................................................................................................................11-10 Figure 11-8 Clock synchronization policy for a port aggregation network (aggregation only through the tributary port)...................................................................................................................................................................11-11 Figure 11-9 Clock synchronization policy for transmission across TDM network.........................................11-12 Figure 11-10 Tributary retiming.......................................................................................................................11-13 Figure 11-11 Configuration flow chart (clocks)...............................................................................................11-14 Figure 11-12 Networking diagram (clock on a TDM radio chain network)....................................................11-17 Figure 11-13 Clock source information (TDM radio chain network)..............................................................11-19 Figure 11-14 Networking diagram (clocks on a TDM radio ring network).....................................................11-21 Figure 11-15 Clock source information (TDM radio ring network)................................................................11-23 Figure 11-16 Networking diagram (clocks on a Hybrid radio chain network)................................................11-25 Figure 11-17 Networking diagram (clock for a Hybrid radio chain network).................................................11-27 Figure 11-18 Networking diagram (clock on a Hybrid radio ring network)....................................................11-28 Figure 11-19 Information about clock sources (Hybrid radio ring network)...................................................11-30 xxxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Figures
Figure 11-20 Networking diagram (clocks for a PSN)....................................................................................11-32 Figure 11-21 Clock source information (PSN)................................................................................................11-34 Figure 11-22 Networking diagram (clocks across a third-party TDM network).............................................11-37 Figure 11-23 Board configuration (clocks across a third-party TDM network)..............................................11-37 Figure 11-24 Information about clock sources (Hybrid radio chain network) ................................................11-38 Figure 12-1 Interface circuit for external alarm input........................................................................................12-5 Figure 12-2 Configuration flow chart................................................................................................................12-7 Figure 12-3 Networking diagram (orderwire)..................................................................................................12-10 Figure 12-4 Networking diagram (for orderwire)............................................................................................12-11 Figure 12-5 Networking diagram (synchronous data services)........................................................................12-14 Figure 12-6 Networking diagram (asynchronous data services)......................................................................12-17 Figure 12-7 Networking diagram (wayside E1 services).................................................................................12-20 Figure 12-8 Networking diagram (external alarms).........................................................................................12-22 Figure 12-9 Network diagram (outdoor cabinet)..............................................................................................12-25 Figure A-1 Connecting the BER tester............................................................................................................A-296 Figure A-2 Networking diagram for testing Ethernet services........................................................................A-297 Figure A-3 Connection diagram for testing the connectivity of the ATM service..........................................A-302 Figure A-4 Configuration for testing IF 1+1 switching..................................................................................A-308 Figure A-5 Configuration for testing N+1 protection switching.....................................................................A-311 Figure A-6 Configuration for testing SNCP switching...................................................................................A-314 Figure A-7 Configuration for testing ERPS....................................................................................................A-317 Figure A-8 Connection diagram for testing the MPLS APS protection..........................................................A-320 Figure A-9 Configuration for testing linear MSP switching...........................................................................A-322
Issue 03 (2011-04-10)
xxxvii
Tables
Tables
Table 2-1 Initial configuration..............................................................................................................................2-2 Table 2-2 Network adjustment.............................................................................................................................2-3 Table 4-1 Mappings between the physical boards and logical boards.................................................................4-5 Table 4-2 Procedures for creating NEs.................................................................................................................4-7 Table 4-3 Procedures for configuring NE attributes............................................................................................4-7 Table 4-4 Procedures for configuring DCCs........................................................................................................4-8 Table 4-5 Procedures for synchronizing NE time..............................................................................................4-10 Table 4-6 Procedures for setting the performance monitoring status.................................................................4-11 Table 4-7 Connections of DCN links (NE11)....................................................................................................4-12 Table 4-8 Connections of DCN links (NE21)....................................................................................................4-16 Table 4-9 Connections of DCN links (NE31)....................................................................................................4-27 Table 4-10 Connections of DCN links (NE32)..................................................................................................4-27 Table 4-11 Connections of DCN links (NE33)..................................................................................................4-28 Table 4-12 Connections of DCN links (NE34)..................................................................................................4-28 Table 4-13 Connections of DCN links (NE11)..................................................................................................4-28 Table 4-14 Connections of DCN links (NE21)..................................................................................................4-28 Table 5-1 Procedures for Configuring TDM Radio Links (with the XPIC function enabled).............................5-7 Table 5-2 Procedures for configuring TDM radio links (with the XPIC function disabled)...............................5-8 Table 5-3 Procedure for configuring a Integrated IP radio link (with the XPIC function enabled).....................5-9 Table 5-4 Procedure for configuring a Integrated IP radio link (with the XPIC function disabled)..................5-11 Table 5-5 Service capacity accessed by each BTS.............................................................................................5-14 Table 5-6 Connections of radio links (NE11)....................................................................................................5-15 Table 5-7 Connections of radio links (NE12)....................................................................................................5-15 Table 5-8 Connections of radio links (NE13)....................................................................................................5-15 Table 5-9 Connections of radio links (NE14)....................................................................................................5-16 Table 5-10 Connections of radio links (NE15)..................................................................................................5-16 Table 5-11 Connections of radio links (NE16)..................................................................................................5-16 Table 5-12 Basic information about radio links.................................................................................................5-16 Table 5-13 Power and ATPC information..........................................................................................................5-17 Table 5-14 Information of IF boards..................................................................................................................5-18 Table 5-15 Service capacity accessed by each BTS...........................................................................................5-25 Table 5-16 Connections of radio links (NE21)..................................................................................................5-26 Table 5-17 Connections of radio links (NE22)..................................................................................................5-27 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxix
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 5-18 Connections of radio links (NE23)..................................................................................................5-27 Table 5-19 Connections of radio links (NE24)..................................................................................................5-27 Table 5-20 Basic information about radio links.................................................................................................5-28 Table 5-21 Power and ATPC information..........................................................................................................5-28 Table 5-22 Information of IF boards..................................................................................................................5-29 Table 5-23 Service capacity accessed by each BTS...........................................................................................5-35 Table 5-24 Common service priorities...............................................................................................................5-35 Table 5-25 Connections of radio links (NE11)..................................................................................................5-36 Table 5-26 Connections of radio links (NE12)..................................................................................................5-36 Table 5-27 Connections of radio links (NE13)..................................................................................................5-37 Table 5-28 Connections of radio links (NE14)..................................................................................................5-37 Table 5-29 Connections of radio links (NE15)..................................................................................................5-37 Table 5-30 Connections of radio links (NE16)..................................................................................................5-37 Table 5-31 Basic information about radio links.................................................................................................5-38 Table 5-32 Hybrid/AM attribute information.....................................................................................................5-38 Table 5-33 Power and ATPC information..........................................................................................................5-39 Table 5-34 Information about IF boards.............................................................................................................5-40 Table 5-35 Service capacity accessed by each BTS...........................................................................................5-49 Table 5-36 Common service priorities...............................................................................................................5-50 Table 5-37 Connections of radio links (NE21)..................................................................................................5-51 Table 5-38 Connections of radio links (NE22)..................................................................................................5-51 Table 5-39 Connections of radio links (NE23)..................................................................................................5-51 Table 5-40 Connections of radio links (NE24)..................................................................................................5-51 Table 5-41 Basic information about radio links.................................................................................................5-52 Table 5-42 Hybrid/AM attribute information.....................................................................................................5-53 Table 5-43 Power and ATPC information..........................................................................................................5-54 Table 5-44 Information about IF boards.............................................................................................................5-54 Table 5-45 Service capacity accessed by each BTS...........................................................................................5-60 Table 5-46 Common service priorities...............................................................................................................5-61 Table 5-47 Connections of radio links (NE32)..................................................................................................5-62 Table 5-48 Connections of radio links (NE33)..................................................................................................5-62 Table 5-49 Connections of radio links (NE34)..................................................................................................5-62 Table 5-50 Basic information about radio links.................................................................................................5-62 Table 5-51 Hybrid/AM attribute information.....................................................................................................5-63 Table 5-52 Power and ATPC information..........................................................................................................5-64 Table 5-53 Information about IF boards.............................................................................................................5-64 Table 6-1 Procedures for configuring TDM services.........................................................................................6-12 Table 6-2 Connections of TDM links (NE11)....................................................................................................6-14 Table 6-3 Connections of TDM links (NE12)....................................................................................................6-14 Table 6-4 Connections of TDM links (NE13)....................................................................................................6-15 Table 6-5 Connections of TDM links (NE14)....................................................................................................6-15 Table 6-6 Connections of TDM links (NE15)....................................................................................................6-15
xl
Issue 03 (2011-04-10)
Tables
Table 6-7 Connections of TDM links (NE16)....................................................................................................6-15 Table 6-8 Linear MSP........................................................................................................................................6-17 Table 6-9 Connections of TDM links (NE21)....................................................................................................6-22 Table 6-10 Connections of TDM links (NE22)..................................................................................................6-22 Table 6-11 Connections of TDM links (NE23)..................................................................................................6-23 Table 6-12 Connections of TDM links (NE24)..................................................................................................6-23 Table 6-13 SNCP................................................................................................................................................6-24 Table 6-14 Service capacity accessed by each BTS...........................................................................................6-29 Table 6-15 Connections of TDM links (NE11)..................................................................................................6-30 Table 6-16 Connections of TDM links (NE12)..................................................................................................6-30 Table 6-17 Connections of TDM links (NE13)..................................................................................................6-30 Table 6-18 Connections of TDM links (NE14)..................................................................................................6-31 Table 6-19 Connections of TDM links (NE15)..................................................................................................6-31 Table 6-20 Service capacity accessed by each BTS...........................................................................................6-36 Table 6-21 Connections of TDM links (NE21)..................................................................................................6-37 Table 6-22 Connections of TDM links (NE22)..................................................................................................6-37 Table 6-23 Connections of TDM links (NE23)..................................................................................................6-37 Table 6-24 Connections of TDM links (NE24)..................................................................................................6-37 Table 6-25 SNCP................................................................................................................................................6-38 Table 7-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts the auto-negotiation mode).....................................................................................................................................................................7-6 Table 7-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts the autonegotiation mode)..................................................................................................................................................7-6 Table 7-3 Point-to-point transparently transmitted E-Line service model...........................................................7-9 Table 7-4 VLAN-based E-Line service model...................................................................................................7-10 Table 7-5 QinQ-based E-Line service models...................................................................................................7-11 Table 7-6 802.1D bridge-based E-LAN service model......................................................................................7-15 Table 7-7 802.1Q bridge-based E-LAN service model......................................................................................7-16 Table 7-8 802.1ad bridge-based E-LAN service models....................................................................................7-17 Table 7-9 Comparison between the three networking modes............................................................................7-22 Table 7-10 Procedures for configuring a LAG...................................................................................................7-32 Table 7-11 Procedures for configuring point-to-point transparently transmitted E-Line services.....................7-33 Table 7-12 Procedures for configuring Ethernet ports.......................................................................................7-34 Table 7-13 Procedures for configuring QoS.......................................................................................................7-35 Table 7-14 Procedures for verifying Ethernet service configurations................................................................7-36 Table 7-15 Procedures for configuring a LAG...................................................................................................7-39 Table 7-16 Procedures for configuring VLAN-based E-Line services..............................................................7-40 Table 7-17 Procedures for configuring Ethernet ports.......................................................................................7-41 Table 7-18 Procedures for configuring QoS.......................................................................................................7-42 Table 7-19 Procedures for verifying Ethernet service configurations................................................................7-43 Table 7-20 Procedures for configuring Ethernet ports.......................................................................................7-46 Table 7-21 Procedures for configuring a LAG...................................................................................................7-49 Table 7-22 Procedures for configuring QinQ-based E-Line services................................................................7-50 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xli
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 7-23 Procedures for configuring QoS.......................................................................................................7-50 Table 7-24 Procedures for verifying Ethernet service configurations................................................................7-51 Table 7-25 Procedures for configuring Ethernet ports.......................................................................................7-54 Table 7-26 Procedures for configuring a LAG...................................................................................................7-56 Table 7-27 Procedures for configuring ERPS protection...................................................................................7-57 Table 7-28 Procedures for configuring IEEE 802.1d-bridge-based E-LAN services........................................7-58 Table 7-29 Procedures for configuring QoS.......................................................................................................7-59 Table 7-30 Procedures for verifying Ethernet service configurations................................................................7-60 Table 7-31 Procedures for configuring Ethernet ports.......................................................................................7-63 Table 7-32 Procedures for configuring ERPS protection...................................................................................7-64 Table 7-33 Procedures for configuring a LAG...................................................................................................7-65 Table 7-34 Procedures for configuring IEEE 802.1q bridge-based E-LAN services.........................................7-66 Table 7-35 Procedures for configuring QoS.......................................................................................................7-67 Table 7-36 Procedures for verifying Ethernet service configurations................................................................7-68 Table 7-37 Procedures for configuring Ethernet ports.......................................................................................7-71 Table 7-38 Procedures for configuring ERPS protection...................................................................................7-72 Table 7-39 Procedures for configuring a LAG...................................................................................................7-73 Table 7-40 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services.......................................7-74 Table 7-41 Procedures for configuring QoS.......................................................................................................7-75 Table 7-42 Procedures for verifying Ethernet service configurations................................................................7-76 Table 7-43 Connections of Ethernet links (NE1)...............................................................................................7-78 Table 7-44 Ethernet port.....................................................................................................................................7-79 Table 7-45 Ethernet port.....................................................................................................................................7-80 Table 7-46 Point-to-point transparently transmitted E-line service...................................................................7-80 Table 7-47 Service class and PHB service class................................................................................................7-81 Table 7-48 Queue scheduling mode...................................................................................................................7-82 Table 7-49 Connections of Ethernet links (NE12).............................................................................................7-88 Table 7-50 Connections of Ethernet links (NE13).............................................................................................7-89 Table 7-51 Connections of Ethernet links (NE14).............................................................................................7-89 Table 7-52 Connections of Ethernet links (NE15).............................................................................................7-90 Table 7-53 Connections of Ethernet links (NE16).............................................................................................7-90 Table 7-54 Information about Ethernet ports (NE12)........................................................................................7-91 Table 7-55 Information about Ethernet ports (NE13)........................................................................................7-91 Table 7-56 Information about Ethernet ports (NE14)........................................................................................7-91 Table 7-57 Information about Ethernet ports (NE16)........................................................................................7-92 Table 7-58 Information about the IF_ETH port (NE12)....................................................................................7-92 Table 7-59 Information about the IF_ETH port (NE13)....................................................................................7-93 Table 7-60 Information about the IF_ETH port (NE14)....................................................................................7-93 Table 7-61 Information about the IF_ETH port (NE15)....................................................................................7-93 Table 7-62 Information about the IF_ETH port (NE16)....................................................................................7-93 Table 7-63 Information about VLAN-based E-Line services (NE12)...............................................................7-94 Table 7-64 Information about VLAN-based E-Line services (NE13)...............................................................7-94
xlii
Issue 03 (2011-04-10)
Tables
Table 7-65 Information about VLAN-based E-Line services (NE14)...............................................................7-94 Table 7-66 Information about VLAN-based E-Line services (NE15)...............................................................7-95 Table 7-67 Information about VLAN-based E-Line services (NE16)...............................................................7-95 Table 7-68 Service class and PHB service class................................................................................................7-96 Table 7-69 Queue scheduling mode...................................................................................................................7-97 Table 7-70 Connections of Ethernet links (NE11)...........................................................................................7-110 Table 7-71 Connections of Ethernet links (NE12)...........................................................................................7-110 Table 7-72 Connections of Ethernet links (NE13)...........................................................................................7-110 Table 7-73 Connections of Ethernet links (NE14)...........................................................................................7-111 Table 7-74 Connections of Ethernet links (NE15)...........................................................................................7-111 Table 7-75 Connections of Ethernet links (NE16)...........................................................................................7-112 Table 7-76 Information about Ethernet ports (NE11)......................................................................................7-112 Table 7-77 Information about Ethernet ports (NE12)......................................................................................7-113 Table 7-78 Information about Ethernet ports (NE13)......................................................................................7-113 Table 7-79 Information about Ethernet ports (NE14)......................................................................................7-113 Table 7-80 Information about Ethernet ports (NE16)......................................................................................7-114 Table 7-81 Information about the IF_ETH port (NE11)..................................................................................7-114 Table 7-82 Information about the IF_ETH port (NE12)..................................................................................7-114 Table 7-83 Information about the IF_ETH port (NE13)..................................................................................7-115 Table 7-84 Information about the IF_ETH port (NE14)..................................................................................7-115 Table 7-85 Information about the IF_ETH port (NE15)..................................................................................7-115 Table 7-86 Information about the IF_ETH port (NE16)..................................................................................7-115 Table 7-87 LAG information............................................................................................................................7-116 Table 7-88 Information about the QinQ-based E-Line service (NE11)...........................................................7-116 Table 7-89 Information about the QinQ-based E-Line service (NE12)...........................................................7-117 Table 7-90 Information about the QinQ-based E-Line service (NE13)...........................................................7-117 Table 7-91 Information about the QinQ-based E-Line service (NE14)...........................................................7-118 Table 7-92 Information about the QinQ-based E-Line service (NE15)...........................................................7-118 Table 7-93 Information about the QinQ-based E-Line service (NE16)...........................................................7-119 Table 7-94 Service class and PHB service class..............................................................................................7-119 Table 7-95 Queue scheduling mode.................................................................................................................7-120 Table 7-96 Connections of Ethernet links (NE21)...........................................................................................7-137 Table 7-97 Connections of Ethernet links (NE22)...........................................................................................7-138 Table 7-98 Connections of Ethernet links (NE23)...........................................................................................7-138 Table 7-99 Connections of Ethernet links (NE24)...........................................................................................7-138 Table 7-100 Information about Ethernet ports (NE21)....................................................................................7-139 Table 7-101 Information about Ethernet ports (NE22)....................................................................................7-140 Table 7-102 Information about Ethernet ports (NE23)....................................................................................7-140 Table 7-103 Information about Ethernet ports (NE24)....................................................................................7-140 Table 7-104 Information about the IF_ETH port (NE21)................................................................................7-141 Table 7-105 Information about the IF_ETH port (NE22)................................................................................7-141 Table 7-106 Information about the IF_ETH port (NE23)................................................................................7-141 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliii
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 7-107 Information about the IF_ETH port (NE24)................................................................................7-141 Table 7-108 Information about ERPS instances...............................................................................................7-142 Table 7-109 Information about IEEE 802.1d bridge-based E-LAN services...................................................7-143 Table 7-110 Service class and PHB service class............................................................................................7-143 Table 7-111 Queue scheduling mode...............................................................................................................7-144 Table 7-112 Connections of Ethernet links (NE12).........................................................................................7-158 Table 7-113 Connections of Ethernet links (NE13).........................................................................................7-159 Table 7-114 Connections of Ethernet links (NE14).........................................................................................7-159 Table 7-115 Connections of Ethernet links (NE15).........................................................................................7-160 Table 7-116 Connections of Ethernet links (NE16).........................................................................................7-160 Table 7-117 Information about Ethernet ports (NE12)....................................................................................7-161 Table 7-118 Information about Ethernet ports (NE13)....................................................................................7-161 Table 7-119 Information about Ethernet ports (NE14)....................................................................................7-162 Table 7-120 Information about Ethernet ports (NE16)....................................................................................7-162 Table 7-121 Information about the IF_ETH port (NE12)................................................................................7-163 Table 7-122 Information about the IF_ETH port (NE13)................................................................................7-163 Table 7-123 Information about the IF_ETH port (NE14)................................................................................7-163 Table 7-124 Information about the IF_ETH port (NE15)................................................................................7-163 Table 7-125 Information about the IF_ETH port (NE16)................................................................................7-163 Table 7-126 Information about IEEE 802.1q bridge-based E-LAN services...................................................7-164 Table 7-127 Service class and PHB service class............................................................................................7-165 Table 7-128 Queue scheduling mode...............................................................................................................7-165 Table 7-129 Connections of Ethernet links (NE21).........................................................................................7-185 Table 7-130 Connections of Ethernet links (NE22).........................................................................................7-186 Table 7-131 Connections of Ethernet links (NE23).........................................................................................7-186 Table 7-132 Connections of Ethernet links (NE24).........................................................................................7-186 Table 7-133 Information about Ethernet ports (NE21)....................................................................................7-187 Table 7-134 Information about Ethernet ports (NE22)....................................................................................7-188 Table 7-135 Information about Ethernet ports (NE23)....................................................................................7-188 Table 7-136 Information about Ethernet ports (NE24)....................................................................................7-189 Table 7-137 Information about the IF_ETH port (NE21)................................................................................7-189 Table 7-138 Information about the IF_ETH port (NE22)................................................................................7-189 Table 7-139 Information about the IF_ETH port (NE23)................................................................................7-190 Table 7-140 Information about the IF_ETH port (NE24)................................................................................7-190 Table 7-141 Information about ERPS instances...............................................................................................7-190 Table 7-142 Information about IEEE 802.1ad bridge-based E-LAN services.................................................7-191 Table 7-143 Service class and PHB service class............................................................................................7-192 Table 7-144 Queue scheduling mode...............................................................................................................7-193 Table 7-145 Connections of Ethernet links (NE12).........................................................................................7-211 Table 7-146 Connections of Ethernet links (NE13).........................................................................................7-212 Table 7-147 Connections of Ethernet links (NE14).........................................................................................7-212 Table 7-148 Connections of Ethernet links (NE15).........................................................................................7-212
xliv
Issue 03 (2011-04-10)
Tables
Table 7-149 Connections of Ethernet links (NE16).........................................................................................7-213 Table 7-150 Information about Ethernet ports (NE12)....................................................................................7-214 Table 7-151 Information about Ethernet ports (NE13)....................................................................................7-214 Table 7-152 Information about Ethernet ports (NE14)....................................................................................7-214 Table 7-153 Information about Ethernet ports (NE16)....................................................................................7-214 Table 7-154 Information about the IF_ETH port (NE12)................................................................................7-215 Table 7-155 Information about the IF_ETH port (NE13)................................................................................7-215 Table 7-156 Information about the IF_ETH port (NE14)................................................................................7-215 Table 7-157 Information about the IF_ETH port (NE15)................................................................................7-216 Table 7-158 Information about the IF_ETH port (NE16)................................................................................7-216 Table 7-159 Information about point-to-point transparently transmitted E-Line services (NE14)..................7-216 Table 7-160 Information about point-to-point transparently transmitted E-Line services (NE15)..................7-217 Table 7-161 Information about point-to-point transparently transmitted E-Line services (NE16)..................7-217 Table 7-162 Information about IEEE 802.1d bridge-based E-LAN services (NE12)......................................7-218 Table 7-163 Information about IEEE 802.1d bridge-based E-LAN services (NE13)......................................7-218 Table 7-164 Service class and PHB service class............................................................................................7-219 Table 7-165 Queue scheduling mode...............................................................................................................7-219 Table 8-1 Point-to-point transparently transmitted EPL service model...............................................................8-5 Table 8-2 Models of the EVPL service based on the VLAN...............................................................................8-6 Table 8-3 Main service model of QinQ-based EVPL services.............................................................................8-8 Table 8-4 Model of EPLAN services based on the 802.1D bridge....................................................................8-11 Table 8-5 Models of EVPLAN services based on the 802.1Q bridge................................................................8-12 Table 8-6 Models of EVPLAN services based on 802.1ad bridge.....................................................................8-13 Table 8-7 Procedures for configuring Ethernet ports.........................................................................................8-16 Table 8-8 Procedure for configuring a LAG......................................................................................................8-18 Table 8-9 Procedure for configuring point-to-point transparently transmitted EPL services............................8-19 Table 8-10 Procedure for configuring the QoS..................................................................................................8-19 Table 8-11 Procedure for testing Ethernet services............................................................................................8-20 Table 8-12 Procedure for configuring Ethernet ports.........................................................................................8-22 Table 8-13 Procedure for configuring a LAG....................................................................................................8-24 Table 8-14 Procedure for configuring VLAN-based EVPL services ................................................................8-25 Table 8-15 Procedure for configuring the QoS..................................................................................................8-25 Table 8-16 Procedure for testing Ethernet services............................................................................................8-26 Table 8-17 Procedure for configuring Ethernet ports.........................................................................................8-28 Table 8-18 Procedure for configuring a LAG....................................................................................................8-29 Table 8-19 Procedure for configuring QinQ-based EVPL services...................................................................8-30 Table 8-20 Procedure for configuring the QoS..................................................................................................8-30 Table 8-21 Procedure for testing Ethernet services............................................................................................8-31 Table 8-22 Procedure for configuring Ethernet ports.........................................................................................8-34 Table 8-23 Procedure for configuring a LAG....................................................................................................8-35 Table 8-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services.........................................8-36 Table 8-25 Procedure for configuring the QoS..................................................................................................8-37 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlv
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 8-26 Procedure for testing Ethernet services............................................................................................8-37 Table 8-27 Procedure for configuring Ethernet ports.........................................................................................8-40 Table 8-28 Procedure for configuring a LAG....................................................................................................8-42 Table 8-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services......................................8-43 Table 8-30 Procedure for configuring the QoS..................................................................................................8-44 Table 8-31 Procedure for testing Ethernet services............................................................................................8-44 Table 8-32 Procedure for configuring Ethernet ports.........................................................................................8-47 Table 8-33 Procedure for configuring a LAG....................................................................................................8-49 Table 8-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.....................................8-50 Table 8-35 Procedure for configuring the QoS..................................................................................................8-51 Table 8-36 Procedure for testing Ethernet services............................................................................................8-51 Table 8-37 Connections of Ethernet links (NE11).............................................................................................8-54 Table 8-38 Connections of Ethernet links (NE12).............................................................................................8-54 Table 8-39 Connections of Ethernet links (NE13).............................................................................................8-54 Table 8-40 Connections of Ethernet links (NE14).............................................................................................8-55 Table 8-41 Connections of Ethernet links (NE15).............................................................................................8-55 Table 8-42 Information about Ethernet external ports (NE11)..........................................................................8-56 Table 8-43 Information about Ethernet external ports (NE14)..........................................................................8-56 Table 8-44 Information about Ethernet external ports (NE15)..........................................................................8-57 Table 8-45 Information about VCTRUNKs (NE11)..........................................................................................8-57 Table 8-46 Information about VCTRUNKs (NE14)..........................................................................................8-58 Table 8-47 Information about VCTRUNKs (NE15)..........................................................................................8-58 Table 8-48 Information about the LAG..............................................................................................................8-59 Table 8-49 Information about VLAN-based EVPL services (NE11)................................................................8-59 Table 8-50 VLAN-based EVPL services (NE14)..............................................................................................8-60 Table 8-51 VLAN-based EVPL services (NE15)..............................................................................................8-60 Table 8-52 Cross-connections of Ethernet services (NE11)...............................................................................8-62 Table 8-53 Cross-connections of Ethernet services (NE12)...............................................................................8-62 Table 8-54 Cross-connections of Ethernet services (NE13)...............................................................................8-62 Table 8-55 Cross-connections of Ethernet services (NE14)...............................................................................8-63 Table 8-56 Cross-connections of Ethernet services (NE15)...............................................................................8-63 Table 8-57 Connections of Ethernet links (NE11).............................................................................................8-76 Table 8-58 Connections of Ethernet links (NE17).............................................................................................8-77 Table 8-59 Information about Ethernet ports (NE11)........................................................................................8-78 Table 8-60 Information about the IF_ETH port (NE11)....................................................................................8-78 Table 8-61 Information about Ethernet services (NE11)...................................................................................8-79 Table 8-62 Service class and PHB service class................................................................................................8-79 Table 8-63 Queue scheduling mode...................................................................................................................8-80 Table 8-64 Information about Ethernet external ports (NE11)..........................................................................8-81 Table 8-65 Information about Ethernet external ports (NE17)..........................................................................8-81 Table 8-66 Information about VCTRUNKs (NE11)..........................................................................................8-82 Table 8-67 Information about VCTRUNKs (NE17)..........................................................................................8-83
xlvi
Issue 03 (2011-04-10)
Tables
Table 8-68 Information about the LAG (NE11).................................................................................................8-83 Table 8-69 Information about the LAG (NE17).................................................................................................8-83 Table 8-70 Information about Ethernet services (NE11)...................................................................................8-84 Table 8-71 Information about Ethernet services (NE17)...................................................................................8-84 Table 8-72 Cross-connections of Ethernet services (NE11)...............................................................................8-85 Table 8-73 Cross-connections of Ethernet services (NE17)...............................................................................8-85 Table 8-74 Flow parameters (NE11)..................................................................................................................8-86 Table 8-75 Flow parameters (NE17)..................................................................................................................8-86 Table 8-76 CoS attributes of the EFP8 board (NE11 and NE17).......................................................................8-87 Table 8-77 CoS parameters and corresponding BTS service types of the EFP8 board (NE11 and NE17) .............................................................................................................................................................................8-87 Table 9-1 LSP types.............................................................................................................................................9-4 Table 9-2 Procedure for setting UNI port attributes.............................................................................................9-7 Table 9-3 Procedure for configuring an MPLS tunnel.........................................................................................9-9 Table 9-4 Procedure for configuring protection for MPLS tunnels...................................................................9-10 Table 9-5 Configuring QoS................................................................................................................................9-11 Table 9-6 Procedure for verifying created MPLS tunnels..................................................................................9-12 Table 9-7 Information about MPLS interfaces (NE31)......................................................................................9-14 Table 9-8 Information about MPLS interfaces (NE32)......................................................................................9-14 Table 9-9 Information about MPLS interfaces (NE11)......................................................................................9-15 Table 9-10 Information about MPLS interfaces (NE21)....................................................................................9-15 Table 9-11 Basic NE configuration....................................................................................................................9-16 Table 9-12 Basic information about MPLS tunnels...........................................................................................9-17 Table 9-13 Information about MPLS OAM (NE31)..........................................................................................9-18 Table 9-14 Information about MPLS OAM (NE32)..........................................................................................9-18 Table 9-15 Information about MPLS OAM (NE11)..........................................................................................9-18 Table 9-16 Information about MPLS OAM (NE21)..........................................................................................9-19 Table 9-17 Information about MPLS APS protection groups (NE31)...............................................................9-19 Table 9-18 Information about MPLS APS protection groups (NE32)...............................................................9-20 Table 9-19 Information about MPLS APS protection groups (NE11)...............................................................9-20 Table 9-20 Information about MPLS APS protection groups (NE21)...............................................................9-20 Table 9-21 Classes of Service and PHB Service Classes...................................................................................9-21 Table 9-22 Queue scheduling mode...................................................................................................................9-22 Table 9-23 Information about MPLS interfaces (NE32)....................................................................................9-42 Table 9-24 Information about MPLS interfaces (NE33)....................................................................................9-42 Table 9-25 Information about MPLS interfaces (NE34)....................................................................................9-42 Table 9-26 Basic NE configuration....................................................................................................................9-43 Table 9-27 Basic information about MPLS tunnels...........................................................................................9-43 Table 9-28 Classes of Service and PHB Service Classes...................................................................................9-44 Table 9-29 Queue scheduling mode...................................................................................................................9-46 Table 10-1 Model of the E-Line services carried on PWs..................................................................................10-7 Table 10-2 Setting the attributes of UNI ports.................................................................................................10-13 Table 10-3 Configuring CES services..............................................................................................................10-15 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlvii
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 10-4 Verifying CES services..................................................................................................................10-16 Table 10-5 Setting attributes of Smart E1 ports...............................................................................................10-17 Table 10-6 Setting attributes of Smart E1 ports...............................................................................................10-18 Table 10-7 Configuring an IMA group ...........................................................................................................10-19 Table 10-8 Configuring ATM QoS..................................................................................................................10-20 Table 10-9 Procedure for configuring UNI port attributes...............................................................................10-24 Table 10-10 Procedures for configuring a LAG...............................................................................................10-26 Table 10-11 Procedure for configuring UNI-NNI E-Line services carried by PWs........................................10-28 Table 10-12 Procedure for configuring the QoS..............................................................................................10-29 Table 10-13 Procedures for verifying Ethernet service configurations............................................................10-30 Table 10-14 Service port information..............................................................................................................10-32 Table 10-15 UNI port information (NE21)......................................................................................................10-33 Table 10-16 UNI port information (NE31)......................................................................................................10-33 Table 10-17 Service information (CES service 1 of BTS22)...........................................................................10-34 Table 10-18 Service information (CES service 2 of BTS22)...........................................................................10-34 Table 10-19 Default values of advanced attributes of CES services................................................................10-35 Table 10-20 Service port information..............................................................................................................10-39 Table 10-21 UNI Port Information (NE11)......................................................................................................10-40 Table 10-22 UNI Port Information (NE31)......................................................................................................10-40 Table 10-23 Service information (CES service 1 of BTS35)...........................................................................10-41 Table 10-24 Service information (CES service 1 of BTS36)...........................................................................10-42 Table 10-25 Default values of advanced attributes of CES services................................................................10-42 Table 10-26 Service port information..............................................................................................................10-47 Table 10-27 UNI Port Information (NE33)......................................................................................................10-48 Table 10-28 UNI port information (NE31)......................................................................................................10-48 Table 10-29 Service information (CES service 1 of BTS32)...........................................................................10-49 Table 10-30 Default values of advanced attributes of CES services................................................................10-50 Table 10-31 Information about service ports...................................................................................................10-56 Table 10-32 Information about NNI ports (NE11)...........................................................................................10-57 Table 10-33 Information about UNI ports (NE31)...........................................................................................10-57 Table 10-34 ATM/IMA information (NE11)...................................................................................................10-58 Table 10-35 ATM/IMA information (NE31)...................................................................................................10-58 Table 10-36 Mapping information between ATM service types and the ATM service classes.......................10-59 Table 10-37 Information about the 1xE1 ATM policy.....................................................................................10-60 Table 10-38 Information about the 4xE1 ATM policy.....................................................................................10-60 Table 10-39 Service information (ATM services from BTS13 and BTS14)...................................................10-61 Table 10-40 Information about service ports...................................................................................................10-76 Table 10-41 Information about UNI ports (NE21)...........................................................................................10-76 Table 10-42 Serial port information (NE21)....................................................................................................10-77 Table 10-43 Information about UNI ports (NE31)...........................................................................................10-77 Table 10-44 ATM/IMA information (NE21)...................................................................................................10-77 Table 10-45 ATM/IMA information (NE31)...................................................................................................10-78
xlviii
Issue 03 (2011-04-10)
Tables
Table 10-46 Mapping information between ATM service types and the ATM service classes.......................10-79 Table 10-47 Information about the 15-timeslot E1 ATM policy.....................................................................10-80 Table 10-48 Service information (ATM services from BTS37 and BTS38)...................................................10-80 Table 10-49 Information about service ports...................................................................................................10-95 Table 10-50 Information about UNI ports (NE34)...........................................................................................10-96 Table 10-51 Information about UNI ports (NE31)...........................................................................................10-96 Table 10-52 ATM/IMA information (NE34)...................................................................................................10-96 Table 10-53 ATM/IMA information (NE31)...................................................................................................10-97 Table 10-54 Mapping information between ATM service types and the ATM service classes.......................10-98 Table 10-55 Information about the 4xE1 ATM policy.....................................................................................10-98 Table 10-56 Service information (CBR services from BTS34).......................................................................10-99 Table 10-57 Service information (rt-VBR services from BTS34).................................................................10-100 Table 10-58 Service information (nrt-VBR services from BTS34)...............................................................10-102 Table 10-59 Service information (UBR services from BTS34).....................................................................10-103 Table 10-60 Information about service ports.................................................................................................10-120 Table 10-61 Information about UNI ports (NE11).........................................................................................10-121 Table 10-62 Information about UNI ports (NE31).........................................................................................10-121 Table 10-63 ATM/IMA information (NE11).................................................................................................10-122 Table 10-64 ATM/IMA information (NE31).................................................................................................10-122 Table 10-65 Information about the ATM CoS mapping table.......................................................................10-123 Table 10-66 Service information (ATM services from BTS13)....................................................................10-124 Table 10-67 Service information (ATM services from BTS14)....................................................................10-125 Table 10-68 Information about service ports.................................................................................................10-136 Table 10-69 Information about Ethernet ports (NE32)..................................................................................10-136 Table 10-70 Information about Ethernet ports (NE31)..................................................................................10-137 Table 10-71 Information about LAGs............................................................................................................10-137 Table 10-72 Planning information about E-Line services carried on PWs....................................................10-138 Table 10-73 Planning information about PWs...............................................................................................10-138 Table 10-74 Queue scheduling mode.............................................................................................................10-140 Table 10-75 Information about service ports.................................................................................................10-150 Table 10-76 Information about Ethernet ports (NE21)..................................................................................10-151 Table 10-77 Information about Ethernet ports (NE31)..................................................................................10-151 Table 10-78 Information about IF_ETH ports...............................................................................................10-152 Table 10-79 Information about LAGs............................................................................................................10-152 Table 10-80 Planning information about E-Line services carried on PWs....................................................10-153 Table 10-81 Planning information about PWs...............................................................................................10-153 Table 10-82 Queue scheduling mode.............................................................................................................10-155 Table 10-83 Information about service ports.................................................................................................10-167 Table 10-84 Information about Ethernet ports (NE34)..................................................................................10-168 Table 10-85 Information about Ethernet ports (NE31)..................................................................................10-168 Table 10-86 Information about LAGs............................................................................................................10-169 Table 10-87 Planning information about E-Line services carried on PWs....................................................10-170 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlix
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table 10-88 Planning information about PWs...............................................................................................10-170 Table 10-89 Planning information about MS-PWs........................................................................................10-171 Table 10-90 Queue scheduling mode.............................................................................................................10-172 Table 11-1 Procedures for configuring clocks.................................................................................................11-15 Table 11-2 Clock connections (NE11).............................................................................................................11-18 Table 11-3 Clock connections (NE12).............................................................................................................11-18 Table 11-4 Clock connections (NE13).............................................................................................................11-18 Table 11-5 Clock connections (NE14).............................................................................................................11-18 Table 11-6 Clock connections (NE15).............................................................................................................11-18 Table 11-7 Clock connections (NE16).............................................................................................................11-19 Table 11-8 Clock connections (NE21).............................................................................................................11-21 Table 11-9 Clock connections (NE22).............................................................................................................11-21 Table 11-10 Clock connections (NE23)...........................................................................................................11-22 Table 11-11 Clock connections (NE24)...........................................................................................................11-22 Table 11-12 Clock connections (NE1).............................................................................................................11-25 Table 11-13 Clock connections (NE2).............................................................................................................11-25 Table 11-14 Clock connections (NE3).............................................................................................................11-26 Table 11-15 Clock connections (NE4).............................................................................................................11-26 Table 11-16 Clock connections (NE5).............................................................................................................11-26 Table 11-17 Clock connections (NE6).............................................................................................................11-26 Table 11-18 Clock connections (NE22)...........................................................................................................11-29 Table 11-19 Clock connections (NE23)...........................................................................................................11-29 Table 11-20 Clock connections (NE24)...........................................................................................................11-29 Table 11-21 Clock connections (NE11)...........................................................................................................11-33 Table 11-22 Clock connections (NE21)...........................................................................................................11-33 Table 11-23 Clock connections (NE31)...........................................................................................................11-33 Table 11-24 Clock connections (NE32)...........................................................................................................11-33 Table 11-25 Clock connections (NE33)...........................................................................................................11-34 Table 11-26 Clock connections (NE34)...........................................................................................................11-34 Table 11-27 Clock source priority table...........................................................................................................11-35 Table 11-28 Clock link connections (NE1)......................................................................................................11-38 Table 11-29 Clock link connections (NE7)......................................................................................................11-38 Table 12-1 Logical slots for supported outdoor cabinets...................................................................................12-6 Table 12-2 Procedures for configuring the function of monitoring the outdoor cabinet....................................12-7 Table 12-3 Orderwire phone connections (NE1)..............................................................................................12-10 Table 12-4 Orderwire phone connections (NE2)..............................................................................................12-10 Table 12-5 Orderwire phone connections (NE3)..............................................................................................12-10 Table 12-6 Orderwire phone connections (NE4)..............................................................................................12-11 Table 12-7 Orderwire phone connections (NE5)..............................................................................................12-11 Table 12-8 Orderwire phone connections (NE6)..............................................................................................12-11 Table 12-9 Information about orderwire ports.................................................................................................12-12 Table 12-10 Connections of synchronous data services (NE1)........................................................................12-14
Issue 03 (2011-04-10)
Tables
Table 12-11 Connections of synchronous data services (NE2)........................................................................12-14 Table 12-12 Connections of synchronous data services (NE3)........................................................................12-15 Table 12-13 Connections of synchronous data services (NE5)........................................................................12-15 Table 12-14 Connections of synchronous data services (NE6)........................................................................12-15 Table 12-15 Information about the synchronous data service..........................................................................12-16 Table 12-16 Connections of asynchronous data services (NE1)......................................................................12-17 Table 12-17 Connections of asynchronous data services (NE2)......................................................................12-18 Table 12-18 Connections of asynchronous data services (NE3)......................................................................12-18 Table 12-19 Connections of asynchronous data services (NE5)......................................................................12-18 Table 12-20 Connections of asynchronous data services (NE6)......................................................................12-18 Table 12-21 Information about the asynchronous data service........................................................................12-19 Table 12-22 Information about wayside E1 services.......................................................................................12-21 Table 12-23 Information about input alarms....................................................................................................12-23 Table 12-24 Information about output alarms..................................................................................................12-23 Table 12-25 Alarm thresholds for the PMU.....................................................................................................12-25 Table 13-1 Common task collection (NE attributes)..........................................................................................13-2 Table 13-2 Common task collection (radio links)..............................................................................................13-3 Table 13-3 Common task collection (TDM services)........................................................................................13-7 Table 13-4 Common task collection (Packet-plane Ethernet services)..............................................................13-8 Table 13-5 Task Collection (EoPDH-plane Ethernet services)........................................................................13-10 Table B-1 Parameters on the main interface......................................................................................................B-96 Table B-2 Methods used by Ethernet interfaces to process data frames.........................................................B-111 Table B-3 Data frame processing....................................................................................................................B-122 Table B-4 Service direction of UNI-UNI........................................................................................................B-159 Table B-5 Service direction of UNI-NNI (carried by PWs)............................................................................B-163 Table B-6 Service direction of UNI-NNI (carried by QinQ links)..................................................................B-165 Table B-7 Service direction of NNI-NNI........................................................................................................B-167 Table B-8 Parameters on the main interface....................................................................................................B-312 Table B-9 Parameters for port attributes..........................................................................................................B-314 Table B-10 Parameters for bound paths...........................................................................................................B-314 Table B-11 Parameters on the main interface..................................................................................................B-315 Table B-12 Parameters of port attributes.........................................................................................................B-318 Table B-13 Parameters for bound paths...........................................................................................................B-319 Table B-14 Parameters on the main interface (Display QinQ Shared Service is not selected)....................B-320 Table B-15 Parameters on the main interface (Display QinQ Shared Service is selected)...........................B-320 Table B-16 Parameters for port attributes........................................................................................................B-321 Table B-17 Parameters for bound paths...........................................................................................................B-321 Table B-18 Parameters on the main interface..................................................................................................B-322 Table B-19 Parameters for mounting services.................................................................................................B-323 Table B-20 Parameters for mounting configuration........................................................................................B-324 Table B-21 Parameters for bound paths...........................................................................................................B-324 Table B-22 Parameters on the main interface..................................................................................................B-325 Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. li
Tables
OptiX RTN 950 Radio Transmission System Configuration Guide (Web LCT) Table B-23 Parameters of service mounting....................................................................................................B-326 Table B-24 Parameters of service mounting....................................................................................................B-328 Table B-25 Parameters for bound paths...........................................................................................................B-329 Table B-26 Parameters on the main interface..................................................................................................B-330 Table B-27 Parameters for mounting services.................................................................................................B-330 Table B-28 Parameters for VLAN filtering table............................................................................................B-332 Table B-29 Parameters for VLAN unicast.......................................................................................................B-333 Table B-30 Parameters for disabling MAC addresses.....................................................................................B-333 Table B-31 Parameters for bound paths...........................................................................................................B-334 Table B-32 Parameters for self-learned MAC addresses.................................................................................B-334 Table B-33 Parameters for VLAN MAC address table capacity.....................................................................B-335 Table B-34 Parameters for VB port MAC address table capacity...................................................................B-335 Table B-35 Parameters on the main interface..................................................................................................B-336 Table B-36 Parameters on the main interface..................................................................................................B-337 Table B-37 Parameters on the main interface..................................................................................................B-339 Table B-38 Parameters on the main interface..................................................................................................B-339 Table B-39 Parameters on the main interface..................................................................................................B-341 Table B-40 Parameters on the main interface..................................................................................................B-342 Table B-41 Parameters on the main interface..................................................................................................B-343 Table B-42 Parameters on the main interface..................................................................................................B-345 Table B-43 Parameters on the main interface..................................................................................................B-355 Table B-44 Parameters on the main interface..................................................................................................B-356 Table B-45 Parameters on the main interface..................................................................................................B-357 Table B-46 Parameters for advanced attributes...............................................................................................B-358 Table B-47 Parameters on the main interface..................................................................................................B-359 Table B-48 Parameters on the main interface..................................................................................................B-360 Table B-49 Parameters on the main interface..................................................................................................B-361 Table B-50 Parameters on the main interface..................................................................................................B-363 Table B-51 Parameters on the main interface..................................................................................................B-364 Table B-52 Parameters on the main interface..................................................................................................B-366 Table B-53 Parameters on the main interface..................................................................................................B-368 Table B-54 Parameters on the main interface..................................................................................................B-369 Table B-55 Parameters on the main interface..................................................................................................B-371 Table B-56 Parameters on the main interface..................................................................................................B-372 Table B-57 Parameters for the basic attributes................................................................................................B-373 Table B-58 Parameters for flow control..........................................................................................................B-375 Table B-59 Parameters for the tag attributes...................................................................................................B-376 Table B-60 Parameters for the network attributes...........................................................................................B-376 Table B-61 Parameters for the advanced attributes.........................................................................................B-377 Table B-62 Methods used by ports to process data frames.............................................................................B-378 Table B-63 Parameters for the tag attributes...................................................................................................B-379 Table B-64 Parameters for encapsulation or mapping.....................................................................................B-380
lii
Issue 03 (2011-04-10)
Tables
Table B-65 Parameters for the network attributes...........................................................................................B-381 Table B-66 Parameters for the LCAS..............................................................................................................B-381 Table B-67 Parameters for bound paths...........................................................................................................B-383 Table B-68 Methods used by ports to process data frames.............................................................................B-384 Table B-69 Parameters on the main interface..................................................................................................B-385 Table B-70 CES services.................................................................................................................................B-418 Table B-71 E-Line services.............................................................................................................................B-419 Table B-72 ATM services................................................................................................................................B-420 Table B-73 CES services.................................................................................................................................B-420 Table B-74 E-Line services.............................................................................................................................B-421 Table B-75 ATM services................................................................................................................................B-422 Table B-76 ATM services................................................................................................................................B-427 Table B-77 CES services.................................................................................................................................B-452 Table B-78 E-Line services.............................................................................................................................B-452 Table B-79 ATM services................................................................................................................................B-454 Table B-80 CES services.................................................................................................................................B-455 Table B-81 E-Line services.............................................................................................................................B-456 Table B-82 ATM services................................................................................................................................B-456 Table B-83 CES services.................................................................................................................................B-462 Table B-84 E-Line services.............................................................................................................................B-462 Table B-85 ATM services................................................................................................................................B-464 Table B-86 CES services.................................................................................................................................B-465 Table B-87 E-Line services.............................................................................................................................B-466 Table B-88 ATM services................................................................................................................................B-466 Table B-89 Mapping relationship between ATM service types, traffic types, and traffic parameters............B-510 Table B-90 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters. .B-515 Table B-91 ATM services................................................................................................................................B-530
Issue 03 (2011-04-10)
liii
1 Configuration Preparations
1
About This Chapter
Configuration Preparations
Before configuring the NE data, you must make the required preparations. 1.1 Preparing Documents and Tools The relevant documents and tools must be available to ensure the proper configuration of data. 1.2 Checking Configuration Conditions Before the configuration, check whether the configuration conditions meet the requirements.
Issue 03 (2011-04-10)
1-1
1 Configuration Preparations
1.1 Preparing Documents and Tools

The relevant documents and tools must be available to ensure the proper configuration of data.
Documents
l l Network planning documents, such as the XXX Network Planning OptiX RTN 950 Radio Transmission System Configuration Guide
Tools
A computer where the Web LCT software is installed
NOTE
For information about the software and hardware required for the Web LCT and the installation method, see the documents that accompany the Web LCT.
1.2 Checking Configuration Conditions

Before the configuration, check whether the configuration conditions meet the requirements.
Context
Ensure that the following requirements are met: l l l All the NEs on the network must be powered on properly. The DCN communication between the gateway NE and the non-gateway NEs must be normal. The gateway NE must log in to the computer where the Web LCT software is installed.
1-2
Issue 03 (2011-04-10)
2 Specifying the Configuration Procedure
Specifying the Configuration Procedure

You can select the proper configuration procedure according to the actual configuration scenarios.
Initial Configuration
Initial configuration of a radio network refers to configuring the network-wide service data by using the NMS for the first time after the NE commissioning is complete. Figure 2-1 describes the configuration procedure.
Issue 03 (2011-04-10)
2-1
Figure 2-1 Configuration flow chart (initial configuration)

Start
Configuring the network topology
Configuring radio links
Configuring TDM services
Configuring Packet-Based Ethernet services Configuring EoPDH-Based Ethernet services
Configuring MPLS packet services
Configuring the clock
Configuring auxiliary ports and functions End Required Optional
The procedures in the configuration flow chart are described in Table 2-1. Table 2-1 Initial configuration Step 1 2 3 Operation 4 Configuring the Network Topology 5 Configuring Radio Links 6 Configuring TDM Services Description Required. Required. Required when the TDM services need to be transmitted.
2-2
Issue 03 (2011-04-10)
Step 4
Operation 7 Configuring Native Ethernet Services on the Packet Plane
Description Required when Native Ethernet services based on the packet plane need to be transmitted. Required when Ethernet services based on the EoPDH plane need to be transmitted. Required when MPLS packet services need to be transmitted. Required. Required when the orderwire information, wayside E1 service, or synchronous/ asynchronous data service needs to be transmitted or when the external alarm input/output function needs to be enabled.
8 Configuring EoPDH-Based Ethernet Services
Configuring MPLS packet services
9 Configuring MPLS Tunnels 10 Configuring PWE3 Services
7 8
11 Configuring the Clock 12 Configuring Auxiliary Ports and Functions
NOTE
The configuration sequence provided in Table 2-1 is for reference only and needs to be adjusted as required in actual application scenarios.
Network Adjustment
Network adjustment involves adding and adjusting configuration data in the equipment commissioning and operation phases. You can find the corresponding configuration operations according to the actual network adjustment requirements in Table 2-2. Table 2-2 Network adjustment Operation 13.1 Common Task Collection (NEs) Description This common task collection lists configuration operations associated with NE attributes, including changing the ID and IP address of an NE.
2-3
Issue 03 (2011-04-10)
Operation 13.2 Common Task Collection (Radio Links)
Description This common task collection lists configuration operations associated with radio links, including changing the working mode of a TDM radio link and changing the number of E1s on a Hybrid radio link. This common task collection lists configuration operations associated with TDM services, including deleting TDM services and upgrading a normal service to an SNCP service. This common task collection lists configuration operations associated with Native Ethernet services based on the packet plane, including setting or modifying Ethernet port parameters and deleting Ethernet services. This common task collection lists configuration operations associated with Ethernet services based on the EoPDH plane, including setting or modifying Ethernet port parameters and deleting Ethernet services.
13.3 Common Task Collection (TDM Services)
13.4 Common Task Collection (PacketPlane Ethernet Services)
13.5 Task Collection (EoPDH-Plane Ethernet Services)
2-4
Issue 03 (2011-04-10)
3 Common Network Scenarios of Configuration Examples
3
About This Chapter
Common Network Scenarios of Configuration Examples
Initial configuration examples of each section are provided in the same TDM radio network scenario or IP radio network scenario. 3.1 Common Network Scenario of the TDM Radio Network Initial configuration examples are provided in a common network scenario of the TDM radio network where a TDM radio chain network and a TDM radio ring network are interconnected through a third-party SDH network. 3.2 Common Network Scenario of the IP Radio Network Initial configuration examples are provided in a common network scenario of the IP radio network where a Hybrid radio chain network, a Hybrid radio ring network, and a packet network are interconnected. The packet network is a GE packet ring that includes packet radio links.
Issue 03 (2011-04-10)
3-1
3.1 Common Network Scenario of the TDM Radio Network

Initial configuration examples are provided in a common network scenario of the TDM radio network where a TDM radio chain network and a TDM radio ring network are interconnected through a third-party SDH network.
Overall Topology
Figure 3-1 shows the overall topology of the TDM radio network. The base station backhaul services converged from a TDM radio chain network and a TDM radio ring network are transmitted over a third-party SDH network to the BSC. Figure 3-1 Overall topology of the TDM radio network
STM-1 TDM radio chain network Third party SDH network BSC E1 TDM radio ring network
TDM Radio Chain Network

Figure 3-2 shows the topology of a TDM radio chain network. In this topology, all base stations are 2G base stations connected to NEs at E1 ports. The base station backhaul services converged from the TDM radio chain network are transmitted over the third-party SDH network to the BSC. The TDM radio chain network and TDM radio ring network are interconnected through STM-1 fiber links configured with linear MSP.
3-2
Issue 03 (2011-04-10)
Figure 3-2 Topology of a TDM radio chain network

NMS
BTS12 E1 BTS13
E1 STM-1 NE14 NE13 NE12 E1 NE11
DCN Third party SDH network STM-1
E1 NE16 BTS15
E1 NE15 BTS14
BTS11
Figure 3-3 shows the board configuration of each NE on the radio network. Figure 3-3 Board configuration of NEs on a TDM radio chain network
NE13
E1 SP3S E1 CST IF1 NE6 IF1 SL1D STM-1 IF1 IF1
NE12
CST IF1 NE6 IF1 SL1D CST IF1 NE6 IF1 SL1D E1
NE14
CST IF1 NE6 IF1
NE11
BTS12
SP3S
BTS13
BTS11
STM-1
Third party SDH netw ork
CST NE6 IF1 SP3S E1
CST NE6 IF1
IF1 IF1 SP3S E1
NE16 BTS15
NE15
BTS14
TDM Radio Ring Network

Figure 3-4 shows the topology of a TDM radio ring network. In this topology, all base stations are 2G base stations connected to NEs at E1 ports. The TDM radio ring network is interconnected with a third-party SDH network by using E1 cables. Therefore, the base station backhaul services converged from the TDM radio ring network are transmitted over the third-party SDH network to the BSC.
Issue 03 (2011-04-10)
3-3
Figure 3-4 Topology of a TDM radio ring network
NMS DCN Third party SDH network E1 NE21
BTS21 NE22 BTS22 NE24 BTS24
NE23 BTS23
Figure 3-5 shows the board configuration of each NE on the radio network. Figure 3-5 Board configuration of NEs on a TDM radio ring network
NE21
CST IF1 NE6 IF1
Third party SDH netw ork
E1
IF1 SP3S
E1 BTS21
CST
NE22
IF1 SP3S
NE24
CST
NE6 IF1 E1
NE6 IF1
IF1 IF1 SP3S
E1 BTS24
BTS22
NE23
CST
NE6 IF1
IF1 SP3S
E1 BTS23
3-4
Issue 03 (2011-04-10)
3.2 Common Network Scenario of the IP Radio Network

Initial configuration examples are provided in a common network scenario of the IP radio network where a Hybrid radio chain network, a Hybrid radio ring network, and a packet network are interconnected. The packet network is a GE packet ring that includes packet radio links.
Overall Topology
Figure 3-6 shows the overall topology of the IP radio network. The base station backhaul services converged from a Hybrid radio chain network, a Hybrid radio ring network, and a packet radio chain network are transmitted to the BSC/RNC over a GE packet ring. Figure 3-6 Overall topology of the IP radio network
Packet radio chain network
GE packet ring Hybrid radio chain network
NMS
BSC Hybrid radio ring network RNC
Packet Network
Figure 3-7 shows the topology of a packet network. The packet network receives various base station services and the base station backhaul services converged from a Hybrid radio chain network and a Hybrid radio ring network. The base station services transmitted on the network are: l l l 2G base station services (CES services transmitted to the BSC from E1 ports) R99 base station services (ATM PWE3 services transmitted to the RNC from E1 ports) R4 base station services (ETH PWE3 services transmitted to the RNC from GE ports)
Issue 03 (2011-04-10)
3-5
Figure 3-7 Topology of a packet network

BTS33
FE
NE34 NE33 BTS31 BTS32

E1 E1 GE
R4
R4
FE GE
BTS34
R99
NE32 Hybrid radio chain network

E1
NE11
GE
NE31
E1
NMS
NE21
E1
GE
+G E1 E
BTS36
BTS35
Hybrid radio ring network
BSC
R99 BTS37
R99 BTS38 RNC
NOTE
l NE31 is an OptiX PTN NE in an actual network because it does not support any radio links. In this example, NE31 is an IDU. l NE11 receives base station services from BTS35 and BTS36 by using the Fractional E1 function. l NE21 receives base station services from BTS37 and BTS38 by using the Fractional E1 function.
Figure 3-8 provides the board configuration of each NE on the packet network. Figure 3-8 Board configuration of NEs on a packet network
NE34 BTS33
FE CSH NE6 ISU2 EM6T CSH
NE33
NE6 ISU2
ML1 E1 E1
ISU2 ISU2 ML1
R4
BTS31 NE32
CSH ISU2 NE6 ISU2 EM6F GE GE FE
BTS34
R99
BTS32
R4 NE31
CSH NE6 EM6T ML1 E1 E1 GE GE GE
Hybrid radio chain network

CSH ISU2 NE6 ISU2 SP3S E1
NE11
ML1 FE EM6F GE
NE21
CSH ISU2 NE6 ISU2 EM6F E1 GE ML1 GE ISU2 SP3S
EM6F
BTS36
BTS35
R99 BTS38
R99 BTS37 Hybrid radio ring network
BSC
RNC
3-6
Issue 03 (2011-04-10)
NOTE
l The Native E1 services received by the Hybrid radio network are converted to CES services by crossconnecting some E1 ports on the SP3S and ML1 boards of NE11 and NE21. l The Native E-LAN services received by the Hybrid radio network are converted to E-Line services, which can be carried by PWs, by cross-connecting some FE ports on the EM6F board of NE21. NE11 receives Native E-Line services and does not require port cross-connections. l The GE port connected to the RNC is configured into a LAG.
Hybrid Radio Chain Network

Figure 3-9 shows the topology of a Hybrid radio chain network. The Hybrid radio chain network receives various base station services and transmits them to the packet network through NE11. The base station services transmitted on the network are: l l R99 base station services (Native E1 services) R4 base station services (Native ETH services)
Figure 3-9 Topology of a Hybrid radio chain network
R4 BTS12 E1
FE E1+GE+ NE cascade NE14 NE13 NE12 FE NE11 R4 BTS11 Packet network
R99 BTS13
NE16
FE R4 BTS15
E1 NE15 R99 BTS14
NOTE
The cascading ports of NE12 and NE13 are connected by using network cables to achieve DCN communication between NE12 and NE13.
Figure 3-10 shows the board configuration of each NE on the radio network.
Issue 03 (2011-04-10)
3-7
Figure 3-10 Board configuration of NEs on a Hybrid radio chain network
NE14 CSH ISU2 NE6 ISU2 EM6T FE R4 BTS12
SP3S
E1 R99 BTS13
NE13 CSH ISU2 NE6 ISU2 EM6T GE
NE cascade ISU2 ISU2 SP3S E1 FE CSH ISU2 NE6 ISU2 EM6T
NE12 NE11 SP3S
Packet network
R4 BTS11
NE16 CSH NE6 ISU2 EM6T FE
NE15 CSH NE6 ISU2 ISU2 ISU2 SP3S E1
R99 BTS14
R4 BTS15
Hybrid Radio Ring Network

Figure 3-11 shows the topology of a Hybrid radio ring network. The Hybrid radio ring network receives various base station services and transmits them to the packet network through NE21. The base station services transmitted on the network are: l l 2G base station services (Native E1 services) R4 base station services (Native ETH services)
Figure 3-11 Topology of a Hybrid radio ring network
Packet network
NE21
R4 BTS21
FE FE E1 NE22 NE24 R4 BTS24
BTS22 FE NE23 R4 BTS23
3-8
Issue 03 (2011-04-10)
Figure 3-12 shows the board configuration of each NE on the radio network. Figure 3-12 Board configuration of NEs on a Hybrid radio ring network
Packet network
NE21
FE R4 BTS21
CSH
NE22 NE24
ISU2 SP3S CSH
NE6 ISU2 E1
EM6T
NE6 ISU2
EM6T
ISU2 ISU2
BTS22 NE23
CSH
FE
R4 BTS24
NE6 ISU2 FE
EM6T
ISU2
R4 BTS23
Issue 03 (2011-04-10)
3-9
4 Configuring the Network Topology
Configuring the Network Topology
About This Chapter

You can manage a transport network by using the Web LCT only after configuring the network topology on the network. 4.1 Basic Concepts Before configuring the network topology, you need to be familiar with the basic concepts. 4.2 Configuration Procedure This section describes the procedures for configuring NEs, the NE attributes, and the logical boards in the NEs. 4.3 Configuration Example (TDM Radio Chain Network Topology) This section considers a TDM radio chain network as an example to describe how to configure the network topology according to the network planning information. 4.4 Configuration Example (TDM Radio Ring Network Topology) This section considers a TDM radio ring network as an example to describe how to configure the network topology according to the network planning information. 4.5 Configuration Example (Hybrid Radio Chain Network) This topic considers a Hybrid radio chain network as an example and describes how to configure NEs according to the planning information. 4.6 Configuration Example (Hybrid Radio Ring Network) This topic considers a Hybrid radio ring network as an example and describes how to configure NEs according to the planning information. 4.7 Configuration Example (Packet Network) This section considers the NEs on a packet network as examples to describe how to configure NEs according to the network planning information.
Issue 03 (2011-04-10)
4-1
4.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts. 4.1.1 DCN To manage and maintain an NE, the Web LCT needs to communicate with the NE through the data communication network (DCN). 4.1.2 GNE and Non-GNE A gateway NE (GNE) refers to an NE whose application layer communicates directly with the application layer of the NMS. A non-GNE refers to an NE whose application layer communicates with the application layer of the NMS by forwarding data through the application layer of its GNE. 4.1.3 NE ID and NE IP Address The ID and IP address are the unique identifiers of an NE on the DCN. 4.1.4 Physical Boards and Logical Boards The NE software and NMS consider a physical board as one or more logical boards when managing the physical board.
4.1.1 DCN
To manage and maintain an NE, the Web LCT needs to communicate with the NE through the data communication network (DCN). On a DCN, the Web LCT and all the NEs are considered as nodes on the DCN. The DCN between the Web LCT and all the NEs is considered as the external DCN, and the DCN between the NEs is considered as the internal DCN. The OptiX RTN 950 supports several DCN solutions, including HWECC, IP over DCC, and inband DCN. HWECC is the commonest DCN solution. HWECC is the default DCN solution provided by the OptiX RTN 950. In the case of HWECC, the network management (NM) message is encapsulated in the proprietary HWECC protocol stack. Hence, the HWECC solution is easy to configure. As a proprietary protocol stack, however, HWECC can be used only when there is one isolated OptiX RTN 950 NE or when the OptiX RTN 950 NE networks with other OptiX equipment that supports HWECC. Figure 4-1 shows how the NM message is transmitted when HWECC is used. The NM message encapsulated in the HWECC protocol stack can be transmitted on the DCC channels over the optical fiber or microwave, and can also be transmitted over the Ethernet between the Ethernet NM ports or between the NE cascade ports. If there are no fiber connections or radio links between two NEs, ensure that the Ethernet connection is set up between the corresponding Ethernet NM ports or NE cascade ports on the NEs. Otherwise, the communication between the two NEs fails. The Ethernet connection between the corresponding Ethernet NM ports or NE cascade ports functions as the extended channel for transmitting the HWECC protocol stack and is hence considered as the extended ECC. The extended ECC function is enabled by default.
4-2
Issue 03 (2011-04-10)
Figure 4-1 HWECC solution

Message HWECC DCC
Message HWECC DCC
Message HWECC ETH
Message HWECC DCC
NMS
Message HWECC DCC Message HWECC DCC
OptiX optical transmission equipment Radio link Fiber
OptiX radio transmission equipment
Ethernet link
In addition, the inband DCN is enabled by default. In the inband DCN solution, the NM management message occupies part of the Ethernet service bandwidth and is transmitted over Integrated IP radio or through FE/GE ports. The inband DCN solution applies to the scenarios where the OptiX RTN 950 networks OptiX packet switching equipment, as shown in Figure 4-2. Figure 4-2 Inband DCN solution
OptiX Msg IP stack IP radio
NMS
OptiX Msg IP stack ETH
OptiX Msg IP stack Inband DCN
OptiX Msg IP stack FE/GE
OptiX RTN equipment
OptiX PTN equipment
Ethernet link
Issue 03 (2011-04-10)
4-3
In the inband DCN solution, the NM management message occupies part of the Ethernet service bandwidth. Hence, the DCN function of the ports that are not connected to the OptiX packet switching equipment must be disabled.
4.1.2 GNE and Non-GNE

A gateway NE (GNE) refers to an NE whose application layer communicates directly with the application layer of the NMS. A non-GNE refers to an NE whose application layer communicates with the application layer of the NMS by forwarding data through the application layer of its GNE.
GNE
Generally, a GNE is connected to the NMS through a local area network (LAN) or wide area network (WAN). Its application layer can directly communicate with the application layer of the NMS. One set of NMS needs to be connected to one or more GNEs. Disable the extended ECC function for the GNEs, to prevent an oversized DCN that is caused due to the ECC communication between the GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs. It is recommended that fewer than 50 non-GNEs are affiliated to a GNE.
4.1.3 NE ID and NE IP Address

The ID and IP address are the unique identifiers of an NE on the DCN.
NE ID
At the application layer of each DCN solution, an OptiX NE uses its NE ID as the NE address. Therefore, the ID of each NE on the DCN must be unique and all these NE IDs must be planned in a unified manner. The NE ID has 24 bits. The most significant eight bits represent the subnet ID (or the extended ID) and the least significant 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID is 9 and the basic ID is 1.
NE IP Address
An NE uses the IP address as its unique identifier during the TCP/IP communication. In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following scenarios: l l A gateway NE (GNE) communicates with the Web LCT over TCP/IP. The IP address of the GNE must be planned as required by the external DCN. Different NEs communicate with each other over extended ECC channels. In this scenario, NE IP addresses must be on the same network segment. By default, NE IP addresses are on the 129.9.0.0 network segment.
In the DCN solutions (for example, inband DCN) where network management messages are transmitted over TCP/IP, the IP address of an NE is used as the NE address at the network layer.
4-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
Therefore, the IP address of each NE on the DCN must be unique and all these NE IP addresses must be planned in a unified manner. By default (which indicates that the IP address of an NE is not changed manually), the IP address and ID of the NE interlock: When the NE ID is changed, the IP address is automatically changed to 0x81000000 + ID. For example, when the NE ID is changed to 0x090001, the IP address is automatically changed to 129.9.0.1. After the IP address is changed manually, the interlocking relation between the ID and IP address no longer takes effect. It is recommended that the IP address of a GNE be on a different network segment from the IP addresses of its non-GNEs.
4.1.4 Physical Boards and Logical Boards

The NE software and NMS consider a physical board as one or more logical boards when managing the physical board. Table 4-1 provides the mappings between the physical boards and logical boards. Table 4-1 Mappings between the physical boards and logical boards Physical Board CST CSH AUX IF1 IFU2 IFX2 ISU2 ISX2 SL1D EM6T EM6F EFP8 SP3S SP3D ML1 MD1 PIU FAN Logical Board CST in the same slot CSH in the same slot AUX in the same slot IF1 in the same slot IFU2 in the same slot IFX2 in the same slot ISU2 in the same slot ISX2 in the same slot SL1D in the same slot EM6T in the same slot EM6F in the same slot EFP8 in the same slot SP3S in the same slot SP3D in the same slot ML1 in the same slot MD1 in the same slot PIU in the same slot FAN in the same slot
Issue 03 (2011-04-10)
4-5
Physical Board ODU
Logical Board ODU in the slot whose number is 20 plus the slot number of the IF board that is connected to the ODU
4.2 Configuration Procedure

This section describes the procedures for configuring NEs, the NE attributes, and the logical boards in the NEs. Figure 4-3 provides the procedures for configuring the network topology. Figure 4-3 Configuration flow chart (network topology)
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
Setting the performance monitoring status
End
Required Optional
The procedures in the configuration flow chart are described as follows.
4-6
Issue 03 (2011-04-10)
NOTE
l If the NE ID and NE name are changed in the NE commissioning process and if the NE communication parameters, logical boards, VLAN ID and bandwidth of the inband DCN are set during the NE commissioning, the configuration data is automatically synchronized onto the Web LCT in the NE data uploading process. Hence, you need not perform the corresponding operations in the initial configuration process. l The preceding configuration procedure is applicable to the scenarios wherein HWECC is used as the DCN solution. When a DCN solution other than HWECC is used, the DCN-related operations described in the preceding configuration procedure may be inapplicable.
Table 4-2 Procedures for creating NEs Step 1 Operation Creating NEs on the Web LCT A.1.1.2 Creating NEs by Using the Manual Method A.1.1.1 Creating NEs by Using the Search Method Description It is recommended that you perform this operation to add one or more NEs to a large existing network on the Web LCT. It is recommended that you perform this operation to create NEs on the Web LCT in other cases. The following parameters need to be set: Domain: When the IP address of the GNE is known, it is recommended that you set the IP address range of the GNE as the search domain. In the case of initial configuration, it is recommended that you set the 129.9.255.255 network segment as the search domain.
Table 4-3 Procedures for configuring NE attributes Step 1 Operation A.1.1.3 Logging In to an NE A.1.1.5 Changing the NE ID Description Required.
Required. Set the parameters as follows: l Change New ID to be the NE ID specified during the planning of the DCN. l If the extended NE ID is required, change New Extended ID.
A.1.1.6 Changing the NE Name
Optional.
Issue 03 (2011-04-10)
4-7
Step 4
Operation A.1.1.4 Configuring the Logical Board
Description Required.
Table 4-4 Procedures for configuring DCCs Step 1 Operation A.1.4.1 Setting NE Communica tion Parameters Description Required. Set the parameters as follows: l In the case of the GNE, set and Subnet Mask according to the planning of the external DCN. l In the case of the GNE, set Gateway IP if the external DCN requires. l Generally, it is recommended that you set Connection Mode to Common + Security SSL. If you need to set the gateway NE to allow for NMS access only in SSL connection mode, set Connection Mode to Security SSL. l In the case of non-GNEs, it is recommended that you set to 0x81000000 + NE ID. That is, if the NE ID is 0x090001, set to 129.9.0.1. Set Subnet Mask to 255.255.0.0.
NOTE If the IP address of an NE is not changed manually, the IP address changes according to the NE ID and is always 0x81000000 + NE ID. In this case, the IP address of a non-GNE does not need to be changed manually.
A.1.4.2 Configuring DCCs A.1.4.3 Configuring Extended ECC Communica tion A.1.4.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN
When the OptiX RTN equipment is interconnected with thirdparty equipment, the DCCs need to be disabled. For a gateway NE, disable the automatic extended ECC function.
Perform this operation if the OptiX RTN equipment uses the inband DCN solution and if the VLAN ID and bandwidth planned for this inband DCN do not assume their default values (the default VLAN ID is 4094 and the default bandwidth is 512 kbit/s).
4-8
Issue 03 (2011-04-10)
Step 5
Operation A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports
Description Required in the case of the Integrated IP radio network. Set the parameters as follows: l In the case of the Ethernet ports and microwave ports that interconnect with the packet switching equipment, set Enabled Status to Enabled. l In the case of the other ports, set Enabled Status to Disabled.
Issue 03 (2011-04-10)
4-9
Table 4-5 Procedures for synchronizing NE time Step 1 Operation Synchroni zing the NE time A.1.1.7 Synchron izing the NE Time Description Required. l To synchronize the NEs with the NM server, set the relevant parameters as follows: Set Synchronous Mode to NM. Right-click and choose the operation from the shortcut menu to ensure that the NE are synchronized with the NM time immediately. Set the synchronization parameters according to the requirements. It is recommended that the parameters adopt the default values. l To synchronize the NEs with the NTP server, set the relevant parameters as follows: Set Synchronous Mode to Standard NTP. Set Standard NTP Authentication according to the requirements for the NTP server. It is recommended that you set the upper level NTP server that the NEs trace as follows: In the case of the GNE, set the external NTP server to the upper level NTP server. Set Standard NTP Server Flag to NE IP and set Standard NTP Server to the IP address of the external NTP server. In the case of a non-GNE, set the GNE to the upper level NTP server. If the nonGNE needs to communicate with the GNE through the HWECC protocol, set Standard NTP Server Flag to NE ID and set Standard NTP Server to the NE ID of the GNE. If the non-GNE needs to communicate with the GNE through the IP protocol, set Standard NTP Server Flag to NE IP and set Standard NTP Server to the IP address of the GNE. Set Standard NTP Server Key according to the requirements for the NTP server. l The NTP server key needs to be specified if the NE is synchronized with the NTP server and if the NE identification needs to be authenticated on the NTP server. A.1.1.8 Localizin g the NE Time Required if the DST scheme is used at the local area. Set the parameters according to the planning of the DST at the local area.
4-10
Issue 03 (2011-04-10)
Table 4-6 Procedures for setting the performance monitoring status Step 1 Operation A.1.2 Configuring the Performanc e Monitoring Status of NEs Description The 15-minute and 24-hour NE performance monitoring functions are enabled by default and thus do not need to be set manually.
4.3 Configuration Example (TDM Radio Chain Network Topology)

This section considers a TDM radio chain network as an example to describe how to configure the network topology according to the network planning information. 4.3.1 Networking Diagram This section describes the networking information about the NEs. 4.3.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 4.3.3 Configuration Process This section describes the procedures for the data configuration.
4.3.1 Networking Diagram

This section describes the networking information about the NEs. Figure 4-4 shows a TDM radio chain network configured according to the following requirements. l l l l The TDM radio chain network is comprised of the OptiX RTN equipment managed by the standalone Web LCT. The Web LCT is connected to NE11 with a network cable. Therefore, NE11 serves as a GNE and the other NEs are non-GNEs with an access to the Web LCT through NE11. NE12 and NE13 are interconnected by using fibers. The TDM radio chain network is interconnected with a third-party SDH network by using fibers. Therefore, the base station backhaul services converged from the TDM radio chain network are transmitted over the third-party SDH network.
Issue 03 (2011-04-10)
4-11
Figure 4-4 Networking diagram (TDM radio chain network)

NMS
BTS12 E1 BTS13
E1 STM-1 NE14 NE13 NE12 E1 NE11
DCN Third party SDH network STM-1
E1 NE16 BTS15
E1 NE15 BTS14
BTS11
The connections of DCN links shown in Figure 4-4 are described as follows. Table 4-7 Connections of DCN links (NE11) Link Link between NE11 and the third-party SDH network Port 1-SL1D-1 (working unit) 1-SL1D-2 (protection unit) Description l Configure the ports as a 1 +1 linear MSP group. l The base station backhaul services converged from the TDM radio chain network are transmitted over the third-party SDH network to the BSC.
4.3.2 Service Planning

The service planning information contains the information about all the parameters required for configuring the NE data. l In this example, the network is comprised of OptiX RTN equipment only, and therefore HWECC is preferred as the DCN solution. In the HWECC solution, NE12 and NE13 communicate with each other through DCC channels in the SDH optical fibers and the other NEs communicate with each other through the DCC channels over microwave. If no fiber connections are set up between NE12 and NE13, NE12 and NE13 communicate with each other through the extended ECC that is enabled by default. NE11 is the GNE. Hence, the extended ECC function of NE11 needs to be disabled. The TDM radio chain network is connected to the third-party network through STM-1 optical fibers. The TDM radio chain and the third-party network are managed by the Web LCT. Therefore, the DCC channel needs to be disabled over the port on the N11 for connecting to the third-party network.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
l l
4-12
Figure 4-5 shows the ID and IP address that are allocated to each NE according to the uniform DCN planning information.
Figure 4-5 Allocated IDs and IP addresses (TDM radio chain network)
NMS
9-14 129.9.0.14 0.0.0.0
10.0.0.100/16
NE14
9-13 129.9.0.13 0.0.0.0
9-12 129.9.0.12 0.0.0.0
9-11 10.0.0.11 0.0.0.0
Third party SDH network
9-16 129.9.0.16 0.0.0.0
9-15 129.9.0.15 0.0.0.0
NE13
NE12
NE11
NE16
NE15
Extended ID-Basic ID IP address Gateway
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0. l The IP addresses of all the NEs, except NE11, are in the interlocking relations with the NE IDs. Hence, if the IP address of an NE (not NE11) is not changed manually, the NE automatically changes the IP address to be the planned value after the NE ID is changed.
In this example, the policy of synchronizing the NE with the NM server is used. The automatic synchronization period is one day. The daylight saving time (DST) scheme is not used at the local area.
4.3.3 Configuration Process

This section describes the procedures for the data configuration.
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.1.1.1 Creating NEs by Using the Search Method and create the NEs. The values for the related parameters are provided as follows. Parameter Domain Value 129.9.255.255
Issue 03 (2011-04-10)
4-13

NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and is not known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the GNE as the search domain.
Normally, NE11 to NE16 should be added in the NE list. Step 2 See A.1.1.3 Logging In to an NE and log in to the NEs. The values for the relevant parameters are provided as follows. Parameter User Name Password Value lct password
Step 3 See A.1.1.5 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Paramete r New ID New Extended ID Value NE11 11 9 (default value) NE12 12 9 (default value) NE13 13 9 (default value) NE14 14 9 (default value) NE15 15 9 (default value) NE16 16 9 (default value)
Step 4 See A.1.1.4 Configuring the Logical Board and configure the logical boards. Configure the logical boards according to the mapping relations between the physical boards and logical boards. Step 5 See A.1.4.1 Setting NE Communication Parameters and set the NE communication parameters. The values for the related parameters are provided as follows. Parameter Value NE11 IP Gateway IP Subnet Mask Extended ID Connection Mode 10.0.0.11 0.0.0.0 (default value) 255.255.0.0 (default value) 9 Common + Security SSL
4-14
Issue 03 (2011-04-10)
NOTE
The IP addresses of all the NEs, except NE11, are in the interlocking relations with the NE IDs. Hence, you need not change the values of the NE communication parameters manually.
Step 6 See A.1.4.2 Configuring DCCs and configure the DCCs. The values for the relevant parameters of NE11 are provided as follows. Parameter Value 1-SL1D-1 Enabled/Disabled Disabled 1-SL1D-2 Disabled
Step 7 See A.1.4.3 Configuring Extended ECC Communication and disable the automatic extended ECC function for the gateway NE (NE11). Step 8 See A.1.1.7 Synchronizing the NE Time and synchronize the NE time. The values for the related parameters are provided as follows. Parameter Value All the Ports on All the NEs Synchronous Mode Period(days) NM 1
----End
4.4 Configuration Example (TDM Radio Ring Network Topology)

This section considers a TDM radio ring network as an example to describe how to configure the network topology according to the network planning information. 4.4.1 Networking Diagram This section describes the networking information about the NEs. 4.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 4.4.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Figure 4-6 shows a TDM radio ring topology configured according to the following requirements.
Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-15
l l l
The TDM radio ring network is comprised of the OptiX RTN equipment managed by the standalone Web LCT. The Web LCT is connected to NE21 with a network cable. Therefore, NE21 serves as a GNE and the other NEs are non-GNEs with an access to the Web LCT through NE21. The TDM radio ring network is interconnected with a third-party SDH network by using E1 cables. Therefore, the base station backhaul services converged from the TDM radio ring network are transmitted over the third-party SDH network.
Figure 4-6 Networking diagram (TDM radio ring network)
NMS DCN Third party SDH network E1 NE21
BTS21 NE22 BTS22 NE24 BTS24
NE23 BTS23
The connections of DCN links shown in Figure 4-6 are described as follows. Table 4-8 Connections of DCN links (NE21) Link Link between NE21 and the third-party SDH network Port 2-SP3S Description The base station backhaul services converged from the TDM radio ring network are transmitted over the thirdparty SDH network to the BSC.
4-16
Issue 03 (2011-04-10)

The service planning information contains the information about all the parameters required for configuring the NE data. l In this example, the network is comprised of OptiX RTN equipment only, and therefore HWECC is preferred as the DCN solution. In the HWECC solution, the NEs communicate with each other through the DCC channels over microwave. NE21 is the GNE. Hence, the extended ECC function of NE21 should be disabled. The TDM radio ring network is connected to the third-party network through E1 cables and cannot communicate with the third-party network. Therefore, the DCC channels need to be disabled on NE21. Figure 4-7 shows the ID and IP address that are allocated to each NE according to the uniform DCN planning information. Figure 4-7 Allocated IDs and IP addresses (TDM radio ring network)
l l
Third part SDH network
E1 9-21 10.0.0.21 0.0.0.0
10.0.0.101/16
9-22 129.9.0.22 0.0.0.0
NE21
9-24 129.9.0.24 0.0.0.0
NE22
9-23 129.9.0.23 0.0.0.0
NE24
NE23
NOTE

Precautions
Procedure
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the GNE as the search domain.
Normally, NE21 to NE24 should be added in the NE list. Step 2 See A.1.1.3 Logging In to an NE and log in to the NEs. The values for the relevant parameters are provided as follows. Parameter User Name Password Value lct password
Step 3 See A.1.1.5 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Parameter Value NE21 New ID New Extended ID 21 9 (default value) NE22 22 9 (default value) NE23 23 9 (default value) NE24 24 9 (default value)
Step 4 See A.1.1.4 Configuring the Logical Board and configure logical boards. Configure the logical boards according to the mapping relations between the physical boards and logical boards. Step 5 See A.1.4.1 Setting NE Communication Parameters and set the NE communication parameters. The values for the related parameters are provided as follows.
4-18
Issue 03 (2011-04-10)
Parameter
Value NE21
IP Gateway IP Subnet Mask Extended ID Connection Mode
10.0.0.21 0.0.0.0 (default value) 255.255.0.0 (default value) 9 Common + Security SSL
NOTE
The IP addresses of all the NEs, except NE21, are in the interlocking relations with the NE IDs. Hence, you need not change the values of the NE communication parameters manually.
Step 6 See A.1.4.3 Configuring Extended ECC Communication and disable the automatic extended ECC function for the gateway NE (NE21). Step 7 See A.1.1.7 Synchronizing the NE Time and synchronize the NE time. The values for the related parameters are provided as follows. Parameter Value All the Ports on All the NEs Synchronous Mode Period(days) NM 1
----End
4.5 Configuration Example (Hybrid Radio Chain Network)

This topic considers a Hybrid radio chain network as an example and describes how to configure NEs according to the planning information. 4.5.1 Networking Diagram This section describes the networking information about the NEs. 4.5.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 4.5.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs.
Figure 4-8 shows a Hybrid radio chain network configured according to the following requirements. l l l l The Hybrid radio chain network is comprised of the OptiX RTN equipment managed by the Web LCT connected to the packet network. All NEs on the Hybrid radio chain network are non-GNEs with an access to the Web LCT through the packet network. The Hybrid radio chain network receives various base station services and transmits them to the packet network through NE11. NE12 and NE13 are interconnected through cascading ports.
NOTE
For details on configuration of NE11, see 4.7 Configuration Example (Packet Network).
Figure 4-8 Networking diagram (Hybrid radio chain network)
R4 BTS12 E1
FE E1+GE+ NE cascade NE14 NE13 NE12 FE NE11 R4 BTS11 Packet network
R99 BTS13
NE16
FE R4 BTS15
E1 NE15 R99 BTS14

The service planning information contains all the parameters required for configuring the NE data. l All NEs except NE11 adopt HWECC for DCN communication. To be specific, NE12 and NE13 are interconnected through cascading ports and adopt automatic extended ECC (enabled by default) for DCN communication; the other NEs use DCC channels in radio signals for DCN communication. NEs numbered 12 to 16 are not connected to the packet network. Therefore, to improve bandwidth utilization, the inband DCN function is disabled at all ports of these NEs. Figure 4-9 shows the ID and IP address that are allocated to each NE according to the uniform DCN planning information.
l l
4-20
Issue 03 (2011-04-10)
Figure 4-9 Allocated IDs and IP addresses (Hybrid radio chain network)
9-14 129.9.0.14 0.0.0.0
NE14
9-13 129.9.0.13 0.0.0.0
9-12 129.9.0.12 0.0.0.0
9-16 129.9.0.16 0.0.0.0
9-15 129.9.0.15 0.0.0.0
NE13
NE12
Packet network NE11
NE16
NE15
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0. l The IP addresses of all the NEs are in the interlocking relations with the NE IDs. Hence, if the IP address of an NE is not changed manually, the NE automatically changes the IP address to be the planned value after the NE ID is changed.
In this example, the policy of synchronizing the NE with the NM server is used. The automatic synchronization period is one day. The daylight saving time (DST) scheme is not used in the local area.

This section describes the process for the data configuration.
Precautions
Procedure
NOTE
In this configuration example, it is assumed that the IP address of the GNE has not been changed manually and that the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the GNE as the search domain.
Normally, NE12 to NE16 should be added in the NE list. Step 2 See A.1.1.3 Logging In to an NE and log in to the NE. The values for the related parameters are provided as follows.
Parameter User Name Password
Value lct password
Step 3 See A.1.1.5 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Parameter Value NE12 New ID New Extended ID 12 9 (default value) NE13 13 9 (default value) NE14 14 9 (default value) NE15 15 9 (default value) NE16 16 9 (default value)
Step 4 See A.1.1.4 Configuring the Logical Board and configure logical boards. Configure the logical boards according to the mapping relationships between the physical boards and logical boards. Step 5 See A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports and enable/disable the inband DCN at the ports. The values for the related parameters of NE12 to NE16 are provided as follows. Parameter Value All Ports Enabled Status Disabled
Step 6 See A.1.1.7 Synchronizing the NE Time and synchronize the NE time. The values for the related parameters are provided as follows. Parameter Value All the Ports on All the NEs Synchronous Mode Period(days) NM 1
----End
4-22
Issue 03 (2011-04-10)
4.6 Configuration Example (Hybrid Radio Ring Network)

This topic considers a Hybrid radio ring network as an example and describes how to configure NEs according to the planning information. 4.6.1 Networking Diagram This section describes the networking information about the NEs. 4.6.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 4.6.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Figure 4-10 shows a Hybrid radio ring network configured according to the following requirements. l l l The Hybrid radio ring network is comprised of the OptiX RTN equipment managed by the Web LCT connected to the packet network. All NEs on the Hybrid radio ring network are non-GNEs with an access to the Web LCT through the packet network. The Hybrid radio ring network receives various base station services and transmits them to the packet network through NE21.
NOTE
For details on configuration of NE21, see 4.7 Configuration Example (Packet Network).
Figure 4-10 Networking diagram (Hybrid radio ring network)
Packet network
NE21
R4 BTS21
FE FE E1 NE22 NE24 R4 BTS24
BTS22 FE NE23 R4 BTS23
Issue 03 (2011-04-10)
4-23

The service planning information contains all the parameters required for configuring the NE data. l l l All NEs except NE21 adopt HWECC for DCN communication. In HWECC mode, NEs use DCC channels in radio signals for DCN communication. NEs numbered 22 to 24 are not connected to the packet network. Therefore, to improve bandwidth utilization, the inband DCN function is disabled at all ports of these NEs. Figure 4-11 shows the ID and IP address that are allocated to each NE according to the uniform DCN planning information. Figure 4-11 Allocated IDs and IP addresses (Hybrid radio ring network)
Packet network
9-22 129.9.0.22 0.0.0.0
NE21
9-24 129.9.0.24 0.0.0.0
NE22
9-23 129.9.0.23 0.0.0.0
NE24
NE23
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0. l The IP addresses of all the NEs are in the interlocking relations with the NE IDs. Hence, if the IP address of an NE is not changed manually, the NE automatically changes the IP address to be the planned value after the NE ID is changed.
In this example, the policy of synchronizing the NE with the NM server is used. The automatic synchronization period is one day. The daylight saving time (DST) scheme is not used in the local area.

Precautions
4-24
Issue 03 (2011-04-10)
Procedure
NOTE
Normally, NE22 to NE24 should be added in the NE list. Step 2 See A.1.1.3 Logging In to an NE and log in to the NE. The values for the related parameters are provided as follows. Parameter User Name Password Value lct password
Step 3 See A.1.1.5 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Parameter Value NE22 New ID New Extended ID 22 9 (default value) NE23 23 9 (default value) NE24 24 9 (default value)
Step 4 See A.1.1.4 Configuring the Logical Board and configure logical boards. Configure the logical boards according to the mapping relationships between the physical boards and logical boards. Step 5 See A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports. The values for the related parameters of NE22 to NE24 are provided as follows. Parameter Value All Ports Enabled Status
Issue 03 (2011-04-10)
Disabled
4-25
Step 6 See A.1.1.7 Synchronizing the NE Time and synchronize the NE time. The values for the related parameters are provided as follows. Parameter Value All the Ports on All the NEs Synchronous Mode Period(days) NM 1
----End
4.7 Configuration Example (Packet Network)

This section considers the NEs on a packet network as examples to describe how to configure NEs according to the network planning information. 4.7.1 Networking Diagram This section describes the networking information about the NEs. 4.7.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 4.7.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Figure 4-12 shows a packet network configured according to the following requirements. l l The packet network receives various base station services and the base station backhaul services converged from a Hybrid radio chain network and a Hybrid radio ring network. The packet network is comprised of the OptiX RTN equipment managed by the Web LCT.
NOTE
NE31 is an OptiX PTN NE in an actual network because it does not support any radio links. In this example, NE31 is an IDU.
l l
The Web LCT is connected to NE31 by using a network cable. Therefore, NE31 serves as a GNE and the other NEs are non-GNEs with an access to the Web LCT through NE31. The NEs on the packet ring are interconnected through GE fiber links. The NEs on the packet chain are interconnected through Packet radio links.
4-26
Issue 03 (2011-04-10)
Figure 4-12 Networking diagram (packet network)

BTS33
FE

E1 E1 GE
R4
R4
FE GE
BTS34
R99

E1
NE11
GE
NE31
E1
NMS
NE21
E1
GE
+G E1 E
BTS36
BTS35
BSC
R99 BTS37
R99 BTS38 RNC
The connections of DCN links shown in Figure 4-12 are described as follows. Table 4-9 Connections of DCN links (NE31) Link Between NE31 and NE21 Between NE31 and NE32 Port 1-EM6F-2 1-EM6F-1 Description Transmits services on the packet ring.
Table 4-10 Connections of DCN links (NE32) Link Between NE32 and NE31 Between NE32 and NE11 Between NE32 and NE33 Port 2-EM6F-2 2-EM6F-1 3-ISU2-1 (main IF board of a 1+1 HSB protection group) 5-ISU2-1 (standby IF board of a 1+1 HSB protection group) Description Transmits services on the packet ring. Transmits services on the packet chain.
Issue 03 (2011-04-10)
4-27
Table 4-11 Connections of DCN links (NE33) Link Between NE33 and NE32 Port 4-ISU2-1 (main IF board of a 1+1 HSB protection group) 6-ISU2-1 (standby IF board of a 1+1 HSB protection group) Between NE33 and NE34 3-ISU2-1 Description Transmits services on the packet chain.
Table 4-12 Connections of DCN links (NE34) Link Between NE34 and NE33 Port 3-ISU2-1 Description Transmits services on the packet chain.
Table 4-13 Connections of DCN links (NE11) Link Between NE11 and NE32 Between NE11 and NE21 Port 2-EM6F-2 2-EM6F-1 Description Transmits services on the packet ring.
Table 4-14 Connections of DCN links (NE21) Link Between NE21 and NE11 Between NE21 and NE31 Port 1-EM6F-2 1-EM6F-1 Description Transmits services on the packet ring.

The service planning information contains the information about all the parameters required for configuring the NE data. l Service channels are used for communication because NEs on the packet ring are interconnected through GE fiber links. For the convenience of maintenance, inband DCN is adopted on the packet ring and the packet chain. Plan the channel for inband DCN. On the packet ring, the inband DCN function needs to be enabled at Ethernet ports of all NEs and be disabled at other ports.
On the packet chain, the inband DCN function needs to be enabled at microwave ports of all NEs and be disabled at other ports. l Plan the management VLAN ID and bandwidth of inband DCN for each NE. The management VLAN ID takes the default value 4094. If the number of NEs is not greater than 50, set the bandwidth of the inband DCN to 512 kbit/s (default value). l l The extended ECC function needs to be disabled on the GNE, namely, NE31. Figure 4-13 shows the ID and IP address that are allocated to each NE according to the uniform DCN planning information. Figure 4-13 Allocated IDs and IP addresses (packet network)
9-34 129.9.0.34 0.0.0.0 9-33 129.9.0.33 0.0.0.0
Packet radio link

9-32 129.9.0.32 0.0.0.0
NE34
NE33 GE GE
Hybrid Radio Network
NE32
9-11 129.9.0.11 0.0.0.0 NE11 9-31 10.0.0.31 0.0.0.0
NMS
NE11 GE
9-21 129.9.0.21 0.0.0.0
NE31 GE
10.0.0.103/16
NE21
Hybrid Radio Network
NOTE

Precautions
Procedure
NOTE
Normally, NE31 to NE34, NE11, and NE21 should be added in the NE list. Step 2 See A.1.1.3 Logging In to an NE and log in to the NE. The values for the related parameters are provided as follows. Parameter User Name Password Value lct password
Step 3 See A.1.1.5 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Paramete r New ID New Extended ID Value NE31 31 9 (default value) NE32 32 9 (default value) NE33 33 9 (default value) NE34 34 9 (default value) NE11 11 9 (default value) NE21 21 9 (default value)
Step 4 See A.1.1.4 Configuring the Logical Board and configure logical boards. Configure the logical boards according to the mapping relationships between the physical boards and logical boards. Step 5 See A.1.4.1 Setting NE Communication Parameters and set the NE communication parameters.
The values for the related parameters are provided as follows. Parameter Value NE31 IP Gateway IP Subnet Mask Extended ID Connection Mode 10.0.0.31 0.0.0.0 (default value) 255.255.0.0 (default value) 9 Common + Security SSL
NOTE
The IP addresses of all the NEs, except NE31, are in the interlocking relationships with the NE IDs. Hence, you need not change the values of the NE communication parameters manually.
Step 6 See A.1.4.3 Configuring Extended ECC Communication and disable the automatic extended ECC function for the gateway NE (NE31). Step 7 See A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports and configure the extended ECC. The values for the related parameters of NE31 are provided as follows. Parameter Value 1-EM6F-1 Enabled Status Enabled 1-EM6F-2 Enabled Other Ports Disabled
The values for the related parameters of NE32 are provided as follows. Parameter Value 2-EM6F-1 Enabled Status Enabled 2-EM6F-2 Enabled 3-ISU2-1 Enabled 5-ISU2-1 Enabled Other Ports Disabled
The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2-1 Enabled Status Enabled 4-ISU2-1 Enabled 6-ISU2-1 Enabled Other Ports Disabled
Issue 03 (2011-04-10)
4-31
The values for the related parameters of NE34 are provided as follows. Parameter Value 3-ISU2-1 Enabled Status Enabled Other Ports Disabled
The values for the related parameters of NE11 are provided as follows. Parameter Value 2-EM6F-1 Enabled Status Enabled 2-EM6F-2 Enabled Other Ports Disabled
The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6F-1 Enabled Status Enabled 1-EM6F-2 Enabled Other Ports Disabled
Step 8 See A.1.1.7 Synchronizing the NE Time and synchronize the NE time. The values for the related parameters are provided as follows. Parameter Value All Ports on All NEs Synchronous Mode Period(days) NM 1
----End
4-32
Issue 03 (2011-04-10)
5 Configuring Radio Links
5
About This Chapter
Configuring Radio Links
Before configuring services on a radio link, you need to configure the radio link. 5.1 Basic Concepts Before configuring the radio link, you need to be familiar with the basic concepts. 5.2 Configuration Procedure The configuration procedures of different radio link configuration methods are different. 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network) This section considers radio links on a TDM radio chain network as examples to describe how to configure radio links according to the planning information. 5.4 Configuration Example (Radio Links on the TDM Radio Ring Network) This section considers TDM radio links on a TDM radio ring network as examples to describe how to configure radio links according to the network planning information. 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network) This section considers radio links on a Hybrid radio chain network as examples to describe how to configure radio links according to the network planning information. 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network) This section considers radio links on a Hybrid radio ring network as examples to describe how to configure radio links according to the network planning information. 5.7 Configuration Example (Radio Links on the Packet Network) This section considers radio links on a packet network as examples to describe how to configure radio links according to the network planning information.
Issue 03 (2011-04-10)
5-1
5.1 Basic Concepts

Before configuring the radio link, you need to be familiar with the basic concepts. 5.1.1 Adaptive Modulation The adaptive modulation (AM) technology adjusts the modulation scheme automatically based on channel quality. 5.1.2 CCDP and XPIC The CCDP and XPIC are two technologies that are developed based on microwave polarization characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference between the two polarization waves. 5.1.3 RF Configuration Modes The OptiX RTN 950 supports five RF configuration modes, namely, 1+0 non-protection configuration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protection configuration, and cross-polarization interference cancellation (XPIC) configuration.
5.1.1 Adaptive Modulation

The adaptive modulation (AM) technology adjusts the modulation scheme automatically based on channel quality. When the AM technology is used, the microwave service bandwidth varies according to the modulation scheme in the same channel spacing; the higher the modulation efficiency, the higher the bandwidth of the transmitted services. l When the channel quality is good (such as on days when weather conditions are favorable), the equipment adopts a high-efficiency modulation scheme to transmit more user services. This improves transmission efficiency and spectrum utilization of the system. When the channel quality deteriorates (such as on days with adverse weather), the equipment adopts a low-efficiency modulation scheme to transmit only higher-priority services within the available bandwidth and to discard lower-priority services. This improves anti-interference capability of a radio link and therefore ensures the link availability for higher-priority services.
In Hybrid/Packet radio mode, the equipment supports the AM technology. With configurable priorities for E1 services and packet services, the transmission is controlled based on the service bandwidth and QoS policies corresponding to the current modulation scheme. The highestpriority services are transmitted with preference.
NOTE
In Hybrid radio mode, when the equipment transmits STM-1 services and packet services at the same time, STM-1 services have highest priority and their transmission is guaranteed.
Priorities of E1 services The priorities of E1 services are assigned based on the number of E1 services that each modulation scheme can transmit. When modulation scheme switching occurs, only the E1 services whose number is specified in the new modulation scheme can be transmitted and the excess E1 services are discarded.
Priorities of packet services With the QoS technology, packet services are scheduled to queues with different priorities. Then, the services in different queues are transmitted to the microwave port after running
5-2
Issue 03 (2011-04-10)
the queue scheduling algorithm. When modulation scheme switching occurs, certain queues may be congested due to insufficient capacity at the air interface. As a result, certain services or all the services in these queues are discarded. Figure 5-1 shows the change in services brought by the AM technology. The orange part indicates E1 services. The blue part indicates packet services. The closer to the edge, the lower the service priority. Under all channel conditions, the service capacity varies according to the modulation scheme. When the channel is in unfavorable conditions, lower-priority services are discarded. Figure 5-1 Adaptive modulation
256QAM 128QAM 64QAM 32QAM 16QAM
QPSK Channel Capability 16QAM 32QAM 64QAM 128QAM E1 Services Ethernet Services 256QAM
The AM technology used by the OptiX RTN 950 has the following characteristics: l l The AM technology uses the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and 256QAM modulation schemes. The lowest-efficiency modulation scheme (also called reference scheme or modulation scheme of guaranteed capacity) and the highest-efficiency modulation scheme (also called nominal scheme or modulation scheme of full capacity) used by the AM can be configured. In AM, when modulation schemes are switched, the transmit frequency, receive frequency, and channel spacing remain unchanged. In AM, modulation schemes are switched step-by-step. In AM, modulation scheme switching is hitless. When the modulation scheme is downshifted, high-priority services will not be affected when low-priority services are discarded. The switching is successful even when 100 dB/s channel fast fading occurs.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-3
l l l
Issue 03 (2011-04-10)
5.1.2 CCDP and XPIC

The CCDP and XPIC are two technologies that are developed based on microwave polarization characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference between the two polarization waves. Microwave transmission can be classified into single-polarized transmission and CCDP transmission by polarization transmission mode. l In the case of the single-polarized transmission, a signal is transmitted over the horizontally polarized wave or the vertically polarized wave on the same channel, as shown in Figure 5-2. In the case of the CCDP transmission, two signals are transmitted over the horizontally polarized wave and the vertically polarized wave on the same channel, as shown in Figure 5-3.
Therefore, the capacity in CCDP transmission mode is double the capacity in single-polarized transmission mode. Figure 5-2 Single-polarized transmission
Figure 5-3 CCDP transmission
The ideal situation of CCDP transmission is that no interference exists between the two orthogonal signals that operate at the same frequency, and then the receiver can easily recover the two signals. In actual engineering conditions, however, regardless of the orthogonality of the two signals, certain interference between the signals exists, due to cross-polarization discrimination (XPD) of the antenna and channel degradation. To cancel the interference, the XPIC technology is adopted. In the XPIC technology, the signals in the horizontal and vertical directions are received and then processed. In this manner, the original signals are recovered. The characteristics of the XPIC function supported by the OptiX RTN 950 are as follows: l
5-4
The XPD tolerance is increased, and the notch performance is improved.

l l
The maximum difference between the IF cables in two polarization directions of an XPIC workgroup cannot exceed 12 meters in length. The XPIC function is realized completely through hardware.
5.1.3 RF Configuration Modes

The OptiX RTN 950 supports five RF configuration modes, namely, 1+0 non-protection configuration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protection configuration, and cross-polarization interference cancellation (XPIC) configuration.
1+0 Non-Protection Configuration

The 1+0 non-protection configuration indicates that the radio link has one working channel and no protection channel.
N+0 Non-Protection Configuration

The N+0 non-protection configuration indicates that the radio link has N working channels and no protection channel. The OptiX RTN 950 supports N+0 protection (1 < N 5).
1+1 Protection Configuration

The 1+1 protection configuration indicates that the radio link has one working channel and one protection channel. The 1+1 protection configuration is classified into 1+1 HSB, 1+1 FD, and 1+1 SD. l In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF boards and ODUs at both ends of each hop of radio link, thus realizing the protection. In the 1+1 FD protection mode, the system uses two channels with a specific frequency interval to transmit and receive the same service signal. The opposite end selects from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection also supports the 1+1 HSB protection. l In the 1+1 SD protection mode, the system uses two antennas with a space distance to receive the same RF signal. The equipment selects from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 SD protection also supports the 1+1 HSB protection.
N+1 Protection Configuration

The N+1 protection configuration indicates that the radio link has N working channels and one protection channel. The OptiX RTN 950 supports N+1 protection only in the case of STM-1 radio and Integrated IP radio. The N+1 protection is implemented through the N+1 MSP similar to l:N linear MSP. The OptiX RTN 950 supports N+1 protection (1 N 4).
XPIC Configuration
The XPIC adopts both the horizontally polarized wave and the vertically polarized wave over one channel to transmit two channels of signals. The radio link capacity in the case of XPIC configuration is double the radio link capacity in the case of 1+0 configuration. The OptiX RTN 950 supports only the XPIC configuration for the Integrated IP radio link.

The configuration procedures of different radio link configuration methods are different. Figure 5-4 provides the procedures for configuring radio links. Figure 5-4 Configuration flow chart (radio links)
Configure TDM radio links (with XPIC function) Start Configure TDM radio links (without XPIC function) Start Configure IP radio links (with XPIC function) Start Configure IP radio links (without XPIC function) Start
Create XPIC working groups
Configure IF IF 1+1 1+1 Configure protection protection
Create XPIC working groups
Configure IF 1+1 protection
Configure IF/ODU information for radio links
Configure AM attributes for XPIC function
Configure ATPC function
Configure ATPC function
Configure ODU power attributes
Configure AM advanced attributes
End
Configure N+1 protection
Configure AM advanced attributes
End
Configure N+1 protection
Compulsory End Optional End
5-6
Issue 03 (2011-04-10)
Procedures for Configuring TDM Radio Links (with the XPIC function enabled)
Table 5-1 Procedures for Configuring TDM Radio Links (with the XPIC function enabled) Step 1 Operation A.2.2 Creating an XPIC Workgroup A.2.1 Creating an IF 1+1 Protection Group Description Required when the radio links are configured with 1+1 protection. Set the parameters according to the network planning information. Required when two XPIC workgroups need to form two 1+1 protection groups. Set the parameters according to the network planning information.
NOTE One XPIC workgroup cannot form a 1+1 protection group. The radio link in the horizontal/vertical polarization direction of the XPIC workgroup can form a 1+1 protection group with the radio link in the horizontal/vertical polarization direction of the other XPIC workgroup.
A.2.4 Configuring the IF/ODU Information of a Radio Link
Required. Set Power to Be Received(dBm) to the received signal level specified in the network planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna nonalignment indication function. Optional. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect only the performance events associated with ATPC. Therefore, determine whether to set these parameters according to the actual requirements.
A.5.9.3 Setting the Power Attributes of the ODU
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links. l The preceding parameters need to set to the same values, separately for the radio links in the vertical and horizontal polarization directions. l n the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link.
Issue 03 (2011-04-10)
5-7
Procedures for Configuring TDM Radio Links (with the XPIC function disabled)
Table 5-2 Procedures for configuring TDM radio links (with the XPIC function disabled) Step 1 Operation A.2.1 Creating an IF 1+1 Protection Groupa A.2.4 Configuring the IF/ODU Information of a Radio Linka Description Required when the radio links are configured with 1+1 protection. Set the parameters according to the network planning information. Required. Set the parameters as follows: l Set Working Mode and Link ID according to the network planning information. l Set TX Frequency(MHz), T/R Spacing(MHz), and TX Power(dBm) according to the network planning information. l Set TX Status to unmute. l Set Power to Be Received(dBm) to the received signal level specified in the network planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. 3 A.5.8.2 Configuring the ATPC Attributesa Required when the ATPC function needs to be used. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
5-8
Issue 03 (2011-04-10)
Step 4
Operation A.5.9.3 Setting the Power Attributes of the ODUa
Description Optional. l To set the maximum transmit power that is supported by the ATPC adjustment, you need to set Maximum Transmit Power(dBm) according to the actual requirements. l TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold (dBm) affect only the performance events associated with ATPC. Therefore, determine whether to set these parameters according to the actual requirements.
A.2.5 Creating an N+1 Protection Group
Required when the radio links are configured with N+1 protection. Set the attributes of the N+1 protection group to the same values for the equipment at both ends. Set the parameters according to the network planning information.
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning, however, you need to reset ATPC Enable Status. l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link. l In the case of TDM radio links configured with N+1 protection, you need to configure the IF and ODU information on each link. Working Mode must be configured as 7, STM-1, 28MHz, 128QAM.
Configuration Procedure of Integrated IP radio Link (with the XPIC function enabled)
Table 5-3 Procedure for configuring a Integrated IP radio link (with the XPIC function enabled) Step 1 Operation A.2.2 Creating an XPIC Workgroup A.2.3 Setting the AM Attributes of the XPIC Workgroup Description Required. Set the parameters according to the network planning information. Required. Set the parameters according to the network planning information. The parameters in both polarization directions need to take the same values.
Issue 03 (2011-04-10)
5-9
Step 3
Operation A.2.1 Creating an IF 1+1 Protection Group
Description Required when two XPIC workgroups need to form two 1+1 protection groups. Set the parameters according to the network planning information.
NOTE One XPIC workgroup cannot form a 1+1 protection group. The radio link in the horizontal/vertical polarization direction of the XPIC workgroup can form a 1+1 protection group with the radio link in the horizontal/vertical polarization direction of the other XPIC workgroup.
Required. l Set Power to Be Received(dBm) to the received signal level specified in the network planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. l To enable the E1 priority function, set Enable E1 Priority to Enabled. In addition, set Guarantee E1 Capacity and Full E1 Capacity according to the network planning information.
A.5.8.3 Setting Advanced AM Attributes
Optional. To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. Generally, it is recommended that you use the default values. Optional. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect only the performance events associated with ATPC. Therefore, determine whether to set these parameters according to the actual requirements.
5-10
Issue 03 (2011-04-10)
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links according to Table 5-4. l The preceding parameters need to set to the same values, separately for the radio links in the vertical and horizontal polarization directions. l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link. l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot enabled status, modulation mode, or STM-1 count is set inconsistently for both ends of a Integrated IP radio link. This alarm should be cleared immediately. Otherwise, services may be configured unsuccessfully or interrupted.
Procedure for configuring a Integrated IP radio link (with the XPIC function disabled)
Table 5-4 Procedure for configuring a Integrated IP radio link (with the XPIC function disabled) Step 1 Operation A.2.1 Creating an IF 1+1 Protection Groupa Description Required when the radio links are configured with 1+1 protection. Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
5-11
Step 2
Operation A.2.4 Configuring the IF/ODU Information of a Radio Linka
Description Required. Set the parameters as follows: l Set AM Status and IF Channel Bandwidth according to the network planning information. l When the AM function is enabled on the radio links, set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity according to the network planning information. l When the AM function is disabled on the radio links, set Manual Modulation Mode according to the network planning information. l During site commissioning, set AM Status to Disabled. In addition, set Manual Modulation Mode to Modulation Mode of the Guarantee AM Capacity that is planned. l Set Full E1 Capacity and Link ID according to the network planning information. l Set TX Frequency(MHz), T/R Spacing(MHz), and TX Power(dBm) according to the network planning information. l Set TX Status to unmute. l Set Power to Be Received(dBm) to the received signal level specified in the network planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. l To enable the E1 priority function, set Enable E1 Priority to Enabled. In addition, set Guarantee E1 Capacity and Full E1 Capacity according to the network planning information.
5-12
Issue 03 (2011-04-10)
Step 3
Operation A.5.8.2 Configuring the ATPC Attributesa
Description Required when the ATPC function needs to be used. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
A.5.8.3 Setting Advanced AM Attributesa A.5.9.3 Setting the Power Attributes of the ODUa
Optional. To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. Generally, it is recommended that you use the default values. Optional. l To set the maximum transmit power that is supported by the ATPC adjustment function, you need to set Maximum Transmit Power(dBm) according to the actual requirements. l TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold (dBm) affect only the performance events associated with ATPC. Therefore, determine whether to set these parameters according to the actual requirements.
Required when the radio links are configured with N+1 protection. Set the attributes of the N+1 protection group to the same values for the equipment at both ends. Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
5-13

NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning, however, you need to reset AM Status and ATPC Enable Status. l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link. l To configure Integrated IP radio links with N+1 protection, you need to configure the IF and ODU information on each link. l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot enabled status, modulation mode, or STM-1 count is set inconsistently for both ends of a Integrated IP radio link. This alarm should be cleared immediately. Otherwise, services may be configured unsuccessfully or interrupted.
5.3 Configuration Example (Radio Links on the TDM Radio Chain Network)
This section considers radio links on a TDM radio chain network as examples to describe how to configure radio links according to the planning information. 5.3.1 Networking Diagram This section describes the networking information about the NEs. 5.3.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 5.3.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 4.3 Configuration Example (TDM Radio Chain Network Topology), configure the TDM radio links according to the following network planning information (as shown in Figure 5-5): l The service capacity accessed by each BTS is provided in Table 5-5. Table 5-5 Service capacity accessed by each BTS BTS Number of E1 services BTS11 16 BTS12 8 BTS13 8 BTS14 14 BTS15 8
To improve transmission reliability of important services, the radio links between NE11 and NE12, between NE13 and NE14, and between NE13 and NE15 are configured with 1 +1 HSB protection. The ATPC function is enabled to reduce inter-site interference.
l
5-14
Figure 5-5 Networking diagram (TDM radio chain network)

BTS12
102 14952M 14532M 16E1,14M,16QAM 1+1 HSB H-polarization Tx high 101 14930M 14510M STM-1,28M,128QAM 1+1 HSB V-polarzation
BTS13
104 14930M 14510M 8E1,7M,16QAM 1+0 H-polarzation
NE13
Tx low Tx low 103 14967M 14547M 22E1,14M,32QAM 1+1 HSB V-polarization
NE12
Tx low Tx high
NE11 Third party SDH network
NE14
Tx high
Tx high Tx low
BTS11
Link ID Tx high station Tx Freq. Tx low station Tx Freq. Radio work mode RF configuarion Polarization
NE15
NE16 BTS15
BTS14
The connections of radio links shown in Figure 5-5 are described as follows. Table 5-6 Connections of radio links (NE11) Link Between NE11 and NE12 Port 3-IF1 (main IF board) 5-IF1 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
Table 5-7 Connections of radio links (NE12) Link Between NE12 and NE11 Port 3-IF1 (main IF board) 5-IF1 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
Table 5-8 Connections of radio links (NE13) Link Between NE13 and NE14 Port 3-IF1 (main IF board) 5-IF1 (standby IF board) Between NE13 and NE15 4-IF1 (main IF board) 6-IF1 (standby IF board) Description Configure the ports as a 1+1 HSB protection group. Configure the ports as a 1+1 HSB protection group.
Issue 03 (2011-04-10)
5-15
Table 5-9 Connections of radio links (NE14) Link Between NE14 and NE13 Port 3-IF1 (main IF board) 5-IF1 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
Table 5-10 Connections of radio links (NE15) Link Between NE15 and NE13 Port 4-IF1 (main IF board) 6-IF1 (standby IF board) Between NE15 and NE16 3-IF1 Description Configure the ports as a 1+1 HSB protection group. Configure this port to receive and transmit radio service signals.
Table 5-11 Connections of radio links (NE16) Link Between NE16 and NE15 Port 3-IF1 Description Configure this port to receive and transmit radio service signals.

The service planning information contains the information about all the parameters required for configuring the NE data.
Basic Information About Radio Links

According to the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about the radio links, as provided in Table 5-12. Table 5-12 Basic information about radio links Parameter Link ID Tx high site Tx low site Link 1 101 NE11 NE12 Link 2 102 NE14 NE13 Link 3 103 NE15 NE13 Link 4 104 NE15 NE16
5-16
Issue 03 (2011-04-10)
Parameter Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Radio working mode RF configuration mode Polarization direction
Link 1 14930
Link 2 14952
Link 3 14967
Link 4 14930
14510
14532
14547
14510
420 STM-1, 28MHz, 128QAM 1+1 HSB
420 16E1, 14MHz, 16QAM 1+1 HSB
420 22E1, 14MHz, 32QAM 1+1 HSB
420 8E1, 7MHz, 16QAM 1+0
V (vertical polarization)
H (horizontal polarization)
NOTE
l To prevent interference on a microwave site, it is recommended that you plan the microwave site as only a TX high site or a TX low site at a time. l To prevent interference between two radio links on a microwave site that use transmit frequencies with a small spacing between, it is recommended that you set the two radio links to operate in different polarization directions. l The planning information that is not related to the configuration of the IDU (except for the polarization direction) is not provided in this example.
Power and ATPC Information

By using the radio network planning software such as the Pathloss, you can analyze and compute the availability of services and parameters of radio links. Then, you can obtain the power and ATPC information of the radio links as provided in Table 5-13. Table 5-13 Power and ATPC information Parameter Transmit power (dBm) Receive power (dBm) ATPC enabling Link 1 5 (NE11) 5 (NE12) -42 (NE11) -42 (NE12) Enabled Link 2 10 (NE13) 10 (NE14) -44 (NE13) -44 (NE14) Enabled Link 3 10 (NE13) 10 (NE15) -43 (NE13) -43 (NE15) Enabled Link 4 15 (NE15) 15 (NE16) -48 (NE15) -48 (NE16) Enabled
Issue 03 (2011-04-10)
5-17
Parameter ATPC automatic threshold enabling Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Maximum transmit power (dBm)
Link 1 Disabled
Link 2 Disabled
Link 3 Disabled
Link 4 Disabled
-32 (NE11) -32 (NE12)
-34 (NE13) -34 (NE14)
-33 (NE13) -33 (NE15)
-38 (NE15) -38 (NE16)
-52 (NE11) -52 (NE12)
-54 (NE13) -54 (NE14)
-53 (NE13) -53 (NE15)
-58 (NE15) -58 (NE16)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if there is no such a requirement. l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value between the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper threshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power. l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled. When this parameter is not specified, the value of the parameter is the rated maximum transmit power of the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with the spectrum configuration profile. Hence, this parameter is not set generally.
Information of IF Boards
According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1 protection, you can obtain the information of IF boards as provided in Table 5-14. Table 5-14 Information of IF boards Parameter Main IF board Link 1 3-IF1 (NE11) 3-IF1 (NE12) Standby IF board RF configuration mode
5-18
Link 2 3-IF1 (NE13) 3-IF1 (NE14) 5-IF1 (NE13) 5-IF1 (NE14) 1+1 HSB
Link 3 4-IF1 (NE13) 4-IF1 (NE15) 6-IF1 (NE13) 6-IF1 (NE15) 1+1 HSB
Link 4 3-IF1 (NE15) 3-IF1 (NE16) -
5-IF1 (NE11) 5-IF1 (NE12) 1+1 HSB
1+0
Issue 03 (2011-04-10)
Parameter Revertive mode WTR time(s) Reverse switching enabling
Link 1 Revertive (default value) 600 (default value) Disabled
Link 4 -
NOTE
l It is recommended that you configure the two IF boards that construct the 1+1 HSB protection group in slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main IF board in the slot with the smaller slot number. l It is recommended that you configure the two IF boards that construct the 1+1 FD/SD protection group in slot 3 and slot 5, slot 4 and slot 6, or slot 1 and slot 2. In addition, it is recommended that you configure the main IF board in the slot with the smaller slot number. l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD configuration, it is recommended that you enable the reverse switching function. l If there are no special requirements, the other parameters of the 1+1 HSB/FD/SD all take default values.

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for NE11 to NE15. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value NE11 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-IF1 5-IF1
l The values for the relevant parameters of NE12 are provided as follows.
Issue 03 (2011-04-10)
5-19
Parameter
Value NE12
Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board
HSB Revertive mode 600 Disabled 3-IF1 5-IF1
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value NE13 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-IF1 5-IF1 HSB Revertive mode 600 Disabled 4-IF1 6-IF1
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value NE14 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-IF1 5-IF1
5-20
Issue 03 (2011-04-10)
Parameter
Value NE15
HSB Revertive mode 600 Disabled 4-IF1 6-IF1
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 7,STM-1,28MHz,128QAM 101 14930 420 5 -42 unmute
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status
Issue 03 (2011-04-10)
7,STM-1,28MHz,128QAM 101 14510 420 5 -42 unmute
5-21
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 6,16E1,14MHz,16QAM 102 14532 420 10 -44 unmute 4-IF1 and 24-ODU 8,22E1,14MHz,32QAM 103 14547 420 10 -43 unmute
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 6,16E1,14MHz,16QAM 102 14952 420 10 -44 unmute
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) 4,8E1,7MHz,16QAM 104 14930 420 15 4-IF1 and 24-ODU 8,22E1,14MHz,32QAM 103 14967 420 10
5-22
Issue 03 (2011-04-10)
Parameter
Value 3-IF1 and 23-ODU 4-IF1 and 24-ODU -43 unmute
Power to Be Received (dBm) TX Status
-48 unmute
l The values for the relevant parameters of NE16 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 4,8E1,7MHz,16QAM 104 14510 420 15 -48 unmute
Step 3 See A.5.8.2 Configuring the ATPC Attributes and configure the ATPC function. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Status Enabled -32 -52 Disabled
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm)
Issue 03 (2011-04-10)
Enabled -32 -52

5-23
Parameter
Value 3-IF1 and 23-ODU
ATPC Automatic Threshold Enable Status
Disabled
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) ATPC Automatic Threshold Enable Status Enabled -34 -54 Disabled 4-IF1 and 24-ODU Enabled -33 -53 Disabled
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Status Enabled -34 -54 Disabled
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) ATPC Automatic Threshold Enable Status
5-24
4-IF1 and 24-ODU Enabled -33 -53 Disabled
Enabled -38 -58 Disabled
Issue 03 (2011-04-10)
l The values for the relevant parameters of NE16 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Status Enabled -38 -58 Disabled
----End
5.4 Configuration Example (Radio Links on the TDM Radio Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe how to configure radio links according to the network planning information. 5.4.1 Networking Diagram This section describes the networking information about the NEs. 5.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 5.4.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 4.4 Configuration Example (TDM Radio Ring Network Topology), configure the TDM radio links according to the network planning information (as shown in Figure 5-6): l The service capacity accessed by each BTS is provided in Table 5-15. Table 5-15 Service capacity accessed by each BTS BTS Number of E1 services BTS21 4 BTS22 4 BTS23 4 BTS24 4
To improve transmission reliability of important services, the radio links between NE21 and NE24 are configured with 1+1 SD protection.
Issue 03 (2011-04-10)
The ATPC function is enabled to reduce inter-site interference.
Figure 5-6 Networking diagram (TDM radio ring network)

Third party SDH network
201 14930M 14510M 16E1,14M,16QAM 1+0 V-polarzation Tx high 204 14958M 14538M 16E1,14M,16QAM 1+1 V-polarization Tx low Tx low Tx high Tx high 203 14930M 14510M 16E1,14M,16QAM 1+0 H-polarzation
NE21
Tx high
BTS21 NE22 BTS22
Tx low Tx low
NE24
BTS24
202 14958M 14538M 16E1,14M,16QAM 1+0 H-polarization
4E1 NE23 BTS23

Link ID Tx high station Tx Freq. Tx low station Tx Freq. Radio work mode RF configuarion Polarization
The connections of radio links shown in Figure 5-6 are described as follows. Table 5-16 Connections of radio links (NE21) Link Between NE21 and NE22 Port 4-IF1 Description Configure this port to receive and transmit radio service signals. Configure the ports as a 1+1 SD protection group.
Between NE21 and NE24
3-IF1 (main IF board) 5-IF1 (standby IF board)
5-26
Issue 03 (2011-04-10)
Table 5-17 Connections of radio links (NE22) Link Between NE22 and NE21 Port 3-IF1 Description Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
4-IF1
Table 5-18 Connections of radio links (NE23) Link Between NE23 and NE22 Port 3-IF1 Description Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
4-IF1
Table 5-19 Connections of radio links (NE24) Link Between NE24 and NE21 Port 4-IF1 (main IF board) 6-IF1 (standby IF board) Between NE24 and NE23 3-IF1 Description Configure the ports as a 1+1 HSB protection group. Configure this port to receive and transmit radio service signals.


According to the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about the radio links as provided in Table 5-20.
Issue 03 (2011-04-10)
5-27
Table 5-20 Basic information about radio links Parameter Link ID Tx high site Tx low site Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Radio working mode RF configuration mode Polarization direction Link 1 201 NE21 NE22 14930 Link 2 202 NE23 NE22 14958 Link 3 203 NE23 NE24 14930 Link 4 204 NE21 NE24 14958
14510
14538
14510
14538
420 16E1, 14MHz, 16QAM 1+0
420 16E1, 14MHz, 16QAM 1+0
420 16E1, 14MHz, 16QAM 1+0
420 16E1, 14MHz, 16QAM 1+1 SD
NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization direction) is not provided in this example.

By using the radio network planning software such as the Pathloss, you can analyze and compute the availability of services and parameters of radio links. Then, you can obtain the power and ATPC information about the radio links, as provided in Table 5-21. Table 5-21 Power and ATPC information Parameter Transmit power (dBm) Receive power (dBm) ATPC enabling Link 1 9 (NE21) 9 (NE22) -46 (NE21) -46 (NE22) Enabled Link 2 10 (NE23) 10 (NE22) -44 (NE23) -44 (NE22) Enabled Link 3 10 (NE23) 10 (NE24) -43 (NE23) -43 (NE24) Enabled Link 4 8 (NE21) 8 (NE24) -47 (NE21) -47 (NE24) Enabled
5-28
Issue 03 (2011-04-10)
Parameter ATPC automatic threshold enabling Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Maximum transmit power (dBm)
Link 1 Disabled
Link 2 Disabled
Link 3 Disabled
Link 4 Disabled
-36 (NE21) -36 (NE22)
-34 (NE23) -34 (NE22)
-33 (NE23) -33 (NE24)
-37 (NE21) -37 (NE24)
-56 (NE21) -56 (NE22)
-54 (NE23) -54 (NE22)
-53 (NE23) -53 (NE24)
-57 (NE21) -57 (NE24)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if there is no such a requirement. l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value of the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper threshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power. l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled. When this parameter is not specified, the value of the parameter is the rated maximum transmit power of the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with the spectrum configuration profile. Hence, this parameter is not set generally.
Information About IF Boards

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1 protection, you can obtain the information about IF boards as provided in Table 5-22. Table 5-22 Information of IF boards Parameter Main IF board Link 1 4-IF1 (NE21) 3-IF1 (NE22) Standby IF board RF configuration mode Link 2 4-IF1 (NE22) 3-IF1 (NE23) Link 3 4-IF1 (NE23) 3-IF1 (NE24) Link 4 4-IF1 (NE24) 3-IF1 (NE21) 6-IF1 (NE24) 5-IF1 (NE21) 1+0 1+0 1+0 1+1 SD
Issue 03 (2011-04-10)
5-29
Parameter Revertive mode WTR time(s) Reverse switching enabling
Link 1 -
Link 2 -
Link 3 -
Link 4 Revertive (default value) 600 (default value) Enabled
NOTE

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and configure the 1+1 protection groups for NE21 and NE24. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value NE21 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board SD Revertive mode 600 Enabled 3-IF1 5-IF1
5-30
Issue 03 (2011-04-10)
Parameter
Value NE24
SD Revertive mode 600 Enabled 4-IF1 6-IF1
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 6,16E1,14MHz,16QAM 204 14958 420 8 -47 unmute 4-IF1 and 24-ODU 6,16E1,14MHz,16QAM 201 14930 420 9 -46 unmute
l The values for the relevant parameters of NE22 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm)
Issue 03 (2011-04-10)
4-IF1 and 24-ODU 6, 16E1, 14MHz, 16QAM 202 14538 420 10 -44
6, 16E1,14MHz, 16QAM 201 14510 420 9 -46
5-31
Parameter
Value 3-IF1 and 23-ODU 4-IF1 and 24-ODU unmute
TX Status
unmute
l The values for the relevant parameters of NE23 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 6, 16E1, 14MHz, 16QAM 202 14958 420 10 -44 unmute 4-IF1 and 24-ODU 6, 16E1, 14MHz, 16QAM 203 14930 420 10 -43 unmute
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value 3-IF1 and 23-ODU Working Mode Link ID TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 6, 16E1, 14MHz, 16QAM 203 14510 420 10 -43 unmute 4-IF1 and 24-ODU 6, 16E1, 14MHz, 16QAM 204 14538 420 8 -47 unmute
Step 3 See A.5.8.2 Configuring the ATPC Attributes and configure the ATPC function. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status
5-32
4-IF1 and 24-ODU Enabled

Issue 03 (2011-04-10)
Enabled
Parameter
Value 3-IF1 and 23-ODU 4-IF1 and 24-ODU -36 -56 Disabled
ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) ATPC Automatic Threshold Enable Status
-37 -57 Disabled
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value 3-IF1 and 23-ODU ATPC Enable Status Enabled 4-IF1 and 24-ODU Enabled
Issue 03 (2011-04-10)
5-33
Parameter
Value 3-IF1 and 23-ODU 4-IF1 and 24-ODU -37 -57 Disabled
ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) ATPC Automatic Threshold Enable Status
-33 -53 Disabled
----End
5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how to configure radio links according to the network planning information. 5.5.1 Networking Diagram This section describes the networking information about the NEs. 5.5.2 Service Planning This section provides the information about all the parameters required for configuring the NE data. 5.5.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 4.5 Configuration Example (Hybrid Radio Chain Network), configure the Hybrid radio links according to the following network planning information (as shown in Figure 5-7): l l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is enabled on each link. To improve transmission reliability of important services, the radio links between NE11 and NE12, between NE13 and NE14, and between NE13 and NE15 are configured with 1 +1 HSB protection. The service capacity accessed by each BTS is provided in Table 5-23.
5-34
Issue 03 (2011-04-10)
Table 5-23 Service capacity accessed by each BTS BTS Number of highpriority E1s Number of low-priority E1s Capacity of highpriority Ethernet services (Mbit/s) Capacity of low-priority Ethernet services (Mbit/s) BTS11 0 BTS12 0 BTS13 1 BTS14 2 BTS15 0
10
35
15
24
20
19
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources and may be discarded in the case of an AM switch. The common service priorities are provided in Table 5-24.
Table 5-24 Common service priorities Service Type TDM E1s that transmit 2G base station services ATM E1s (IMA E1s are not used) that transmit 3G base station services E1s (of a bandwidth not lower than the high-priority service bandwidth) in the IMA E1 group that transmits 3G base station services Other E1s in the IMA E1 group that transmits 3G base station services Voice, signaling, and OM Ethernet services Service Class High-priority services High-priority services High-priority service
Low-priority services High-priority services
Issue 03 (2011-04-10)
5-35
Service Type Streaming media, background, and interactive Ethernet services, for example, Internet services
Service Class Low-priority services
Figure 5-7 Networking diagram (Hybrid radio chain network)

BTS12
102 14952M 14532M 14M 1+1 HSB H-polarization Tx high 101 14930M 14510M 28M 1+1 HSB V-polarzation
BTS13
104 14930M 14510M 7M 1+0 H-polarzation
NE13
Tx low Tx low 103 14967M 14547M 14M 1+1 HSB V-polarization
NE12
Tx low Tx high
NE11 Packet network
NE14
Tx high
Tx high Tx low
BTS11
Link ID Tx high station Tx Freq. Tx low station Tx Freq. Channel spacing RF configuarion Polarization
NE15
NE16 BTS15
BTS14
The connections of radio links shown in Figure 5-7 are described as follows. Table 5-25 Connections of radio links (NE11) Link Between NE11 and NE12 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
Table 5-26 Connections of radio links (NE12) Link Between NE12 and NE11 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
5-36
Issue 03 (2011-04-10)
Table 5-27 Connections of radio links (NE13) Link Between NE13 and NE14 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Between NE13 and NE15 4-ISU2 (main IF board) 6-ISU2 (standby IF board) Description Configure the ports as a 1+1 HSB protection group. Configure the ports as a 1+1 HSB protection group.
Table 5-28 Connections of radio links (NE14) Link Between NE14 and NE13 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports as a 1+1 HSB protection group.
Table 5-29 Connections of radio links (NE15) Link Between NE15 and NE13 Port 4-ISU2 (main IF board) 6-ISU2 (standby IF board) Between NE15 and NE16 3-ISU2 Description Configure the ports as a 1+1 HSB protection group. Configure this port to receive and transmit radio service signals.
Table 5-30 Connections of radio links (NE16) Link Between NE16 and NE15 Port 3-ISU2 Description Configure this port to receive and transmit radio service signals.

This section provides the information about all the parameters required for configuring the NE data.

According to the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information of the radio links, as provided in Table 5-31.
Table 5-31 Basic information about radio links Parameter Link ID Tx high site Tx low site Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Channel spacing (MHz) RF configuration mode Polarization direction Link 1 101 NE11 NE12 14930 Link 2 102 NE14 NE13 14952 Link 3 103 NE15 NE13 14967 Link 4 104 NE15 NE16 14930
14510
14532
14547
14510
420 28 1+1 HSB
420 14 1+1 HSB
420 14 1+1 HSB
420 7 1+0
NOTE
Hybrid/AM Attribute Information

According to the capacity of E1 and Ethernet services and the availability requirement, you can calculate the Hybrid/AM attribute information, as provided in Table 5-32. Table 5-32 Hybrid/AM attribute information Parameter Number of E1s in AM guaranteed capacity mode Number of E1s in AM full capacity mode Link 1 3 Link 2 1 Link 3 2 Link 4 0
5-38
Issue 03 (2011-04-10)
Parameter Capacity of high-priority Ethernet services (Mbit/ s) Capacity of lowpriority Ethernet services (Mbit/ s) AM enabling AM guaranteed capacity mode AM full capacity mode E1 priority enabling
Link 1 24
Link 2 8
Link 3 6
Link 4 5
113
39
39
19
Enabled QPSK 128QAM Enabled
Enabled QPSK 32QAM Disabled
Enabled QPSK 64QAM Enabled
Enabled QPSK 32QAM Disabled
NOTE
The Hybrid radio capacity and the AM function require the proper license file.

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the power and ATPC information of the radio links, as provided in Table 5-33. Table 5-33 Power and ATPC information Parameter Transmit power (dBm) Receive power (dBm) ATPC enabling ATPC automatic threshold enabling Link 1 16.5 (NE11) 16.5 (NE12) -46 (NE11) -46 (NE12) Disabled Link 2 16.5 (NE13) 16.5 (NE14) -44 (NE13) -44 (NE14) Disabled Link 3 16 (NE13) 16 (NE15) -43 (NE13) -43 (NE15) Disabled Link 4 20 (NE15) 20 (NE16) -48 (NE15) -48 (NE16) Disabled -
Issue 03 (2011-04-10)
5-39
Parameter Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Maximum transmit power (dBm)
Link 1 -
Link 2 -
Link 3 -
Link 4 -
NOTE
l The transmit power is calculated in AM guaranteed capacity mode. l The receive power is calculated in AM guaranteed capacity mode. l In this example, the ATPC function is disabled.

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1 protection, you can obtain the information about IF boards, as provided in Table 5-34. Table 5-34 Information about IF boards Parameter Main IF board Link 1 3-ISU2 (NE11) 3-ISU2 (NE12) Standby IF board RF configuration mode Revertive mode WTR time(s) Reverse switching enabling 5-ISU2 (NE11) 5-ISU2 (NE12) 1+1 HSB Link 2 3-ISU2 (NE13) 3-ISU2 (NE14) 5-ISU2 (NE13) 5-ISU2(NE14) 1+1 HSB Link 3 4-ISU2 (NE13) 4-ISU2 (NE15) 6-ISU2 (NE13) 6-ISU2 (NE15) 1+1 HSB 1+0 Link 4 3-ISU2 (NE15) 3-ISU2 (NE16) -
Revertive (default value) 600 (default value) Disabled
5-40
Issue 03 (2011-04-10)
NOTE

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for NE11 to NE15. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value NE11 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-ISU2 5-ISU2
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value NE12 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-ISU2 5-ISU2
Issue 03 (2011-04-10)
5-41
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value NE13 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-ISU2 5-ISU2 HSB Revertive mode 600 Disabled 4-ISU2 6-ISU2
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. l The values for the relevant parameters of NE11 are provided as follows.
Parameter
Value 3-ISU2 and 23-ODU
Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status
101 Hybrid(Native E1+ETH) 28M Enabled QPSK 128QAM Enabled 3 5 14930 420 16.5 -46 unmute
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity 101 Hybrid(Native E1+ETH) 28M Enabled QPSK 128QAM Enabled 3 5
Issue 03 (2011-04-10)
5-43
Parameter
TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status
14510 420 16.5 -46 unmute
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 102 Hybrid(Native E1+ETH) 14M Enabled QPSK 32QAM Enabled 1 1 14532 420 16.5 -44 unmute 4-ISU2 and 24-ODU 103 Hybrid(Native E1+ETH) 14M Enabled QPSK 64QAM Enabled 2 4 14547 420 16 -43 unmute
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID
5-44
102
Parameter
IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status
Hybrid(Native E1+ETH) 14M Enabled QPSK 32QAM Disabled 1 14952 420 16.5 -44 unmute
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) 104 Hybrid(Native E1+ETH) 7M Enabled QPSK 32QAM Disabled 0 14930 4-ISU2 and 24-ODU 103 Hybrid(Native E1+ETH) 14M Enabled QPSK 64QAM Enabled 2 4 14967
Issue 03 (2011-04-10)
5-45
Parameter
Value 3-ISU2 and 23-ODU 4-ISU2 and 24-ODU 420 16 -43 unmute
T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status
420 20 -48 unmute
l The values for the relevant parameters of NE16 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 104 Hybrid(Native E1+ETH) 7M Enabled QPSK 32QAM Disabled 0 14510 420 20 -48 unmute
Step 3 See A.5.8.1 Setting IF Attributes and set the IF attributes. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot
5-46
Disabled
Issue 03 (2011-04-10)
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot Disabled
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot Disabled 4-ISU2 and 24-ODU Disabled
Step 4 See A.5.8.2 Configuring the ATPC Attributes and configure the ATPC function. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled
Issue 03 (2011-04-10)
5-47
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled 4-ISU2 and 24-ODU Disabled
----End
5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how to configure radio links according to the network planning information. 5.6.1 Networking Diagram This section describes the networking information about the NEs. 5.6.2 Service Planning
This section provides the information about all the parameters required for configuring the NE data. 5.6.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 4.6 Configuration Example (Hybrid Radio Ring Network), configure the Hybrid radio links according to the network planning information (as shown in Figure 5-8): l l l Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is enabled on each link. To improve transmission reliability of important services, the radio links between NE21 and NE24 are configured with 1+1 SD protection. The service capacity accessed by each BTS is provided in Table 5-35. Table 5-35 Service capacity accessed by each BTS BTS Number of high-priority E1s Number of low-priority E1s Capacity of high-priority Ethernet services (Mbit/ s) Capacity of low-priority Ethernet services (Mbit/ s) BTS21 0 BTS22 2 BTS23 0 BTS24 0
10
10
10
10
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources and may be discarded in the case of an AM switch. The common service priorities are provided in Table 5-36.
Issue 03 (2011-04-10)
5-49
Table 5-36 Common service priorities Service Type TDM E1s that transmit 2G base station services ATM E1s (IMA E1s are not used) that transmit 3G base station services E1s (of a bandwidth not lower than the high-priority service bandwidth) in the IMA E1 group that transmits 3G base station services Other E1s in the IMA E1 group that transmits 3G base station services Voice, signaling, and OM Ethernet services Streaming media, background, and interactive Ethernet services, for example, Internet services Service Class High-priority services High-priority services High-priority service
Low-priority services High-priority services Low-priority services
Figure 5-8 Networking diagram (Hybrid radio ring network)

Packet network
201 14930M 14510M 14M 1+0 V-polarzation Tx high 204 14958M 14538M 14M 1+1 V-polarization Tx low Tx low Tx high Tx high 203 14930M 14510M 14M 1+0 H-polarzation
NE21
Tx high
BTS21 NE22 BTS22
Tx low Tx low
NE24
BTS24
202 14958M 14538M 14M 1+0 H-polarization
4E1 NE23 BTS23

5-50
Issue 03 (2011-04-10)
The connections of radio links shown in Figure 5-8 are described as follows. Table 5-37 Connections of radio links (NE21) Link Between NE21 and NE22 Port 4-ISU2 Description Configure this port to receive and transmit radio service signals. Configure the ports as a 1+1 SD protection group.
3-ISU2 (main IF board) 5-ISU2 (standby IF board)
Table 5-38 Connections of radio links (NE22) Link Between NE22 and NE21 Port 3-ISU2 Description Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
4-ISU2
Table 5-39 Connections of radio links (NE23) Link Between NE23 and NE22 Port 3-ISU2 Description Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
4-ISU2
Table 5-40 Connections of radio links (NE24) Link Between NE24 and NE21 Port 4-ISU2 (main IF board) 6-ISU2 (standby IF board) Between NE24 and NE23 3-ISU2 Description Configure the ports as a 1+1 SD protection group. Configure this port to receive and transmit radio service signals.
Issue 03 (2011-04-10)
5-51


According to the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about the radio links, as provided in Table 5-41. Table 5-41 Basic information about radio links Parameter Link ID Tx high site Tx low site Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Channel spacing (MHz) RF configuration mode Polarization direction Link 1 201 NE21 NE22 14930 Link 2 202 NE23 NE22 14958 Link 3 203 NE23 NE24 14930 Link 4 204 NE21 NE24 14958
14510
14538
14510
14538
420 14 1+0
420 14 1+0
420 14 1+0
420 14 1+1 SD
NOTE

According to the capacity of E1 and Ethernet services and the availability requirement, you can calculate the Hybrid/AM attribute information as provided in Table 5-42.
5-52
Issue 03 (2011-04-10)
Table 5-42 Hybrid/AM attribute information Parameter Number of E1s in guaranteed capacity mode Number of E1s in AM full capacity mode Capacity of high-priority Ethernet services (Mbit/ s) Capacity of lowpriority Ethernet services (Mbit/ s) AM enabling AM guarantee capacity mode AM full capacity mode E1 priority enabling Link 1 2 Link 2 2 Link 3 2 Link 4 2
28
28
28
28
40
40
40
40
Enabled 16QAM 128QAM Disabled
NOTE
l In this example, E1 services are high-priority services and therefore the E1 service priority function does not need to be enabled. l According to the Hybrid ring protection scheme, each Hybrid radio link must carry all the services on the ring. l The Hybrid radio capacity and the AM function require the appropriate license file.

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the power and ATPC information of the radio links, as provided in Table 5-43.
Issue 03 (2011-04-10)
5-53
Table 5-43 Power and ATPC information Parameter Transmit power (dBm) Receive power (dBm) ATPC enabling ATPC automatic threshold enabling Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Maximum transmit power (dBm) Link 1 16.5 (NE21) 16.5 (NE22) -42 (NE21) -42 (NE22) Disabled Link 2 16.5 (NE23) 16.5 (NE22) -44 (NE23) -44 (NE22) Disabled Link 3 16 (NE23) 16 (NE24) -43 (NE23) -43 (NE24) Disabled Link 4 15 (NE21) 15 (NE24) -45 (NE21) -45 (NE24) Disabled -
NOTE

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1 protection, you can obtain the information about IF boards, as provided in Table 5-44. Table 5-44 Information about IF boards Parameter Main IF board Link 1 4-ISU2 (NE21) 3-ISU2 (NE22) Standby IF board Link 2 4-ISU2 (NE22) 3-ISU2 (NE23) Link 3 4-ISU2 (NE23) 3-ISU2 (NE24) Link 4 4-ISU2 (NE24) 3-ISU2 (NE21) 6-ISU2 (NE24) 5-ISU2 (NE21)
5-54
Issue 03 (2011-04-10)
Parameter RF configuration mode Revertive mode WTR time(s) Reverse switching enabling
Link 1 1+0
Link 2 1+0
Link 3 1+0
Link 4 1+1 SD
Revertive (default value) 600 (default value) Enabled
NOTE

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for NE21and NE24. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value NE21 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board SD Revertive mode 600 Enabled 3-ISU2 5-ISU2
Issue 03 (2011-04-10)
5-55
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value NE24 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board SD Revertive mode 600 Enabled 4-ISU2 6-ISU2
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 204 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14958 420 15 -45 unmute 4-ISU2 and 24-ODU 201 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14930 420 16.5 -42 unmute
5-56
Issue 03 (2011-04-10)
Parameter
Value 3-ISU2 and 23-ODU 4-ISU2 and 24-ODU 202 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14538 420 16.5 -44 unmute
Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status
201 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14510 420 16.5 -42 unmute
l The values for the relevant parameters of NE23 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity TX Frequency(MHz) 202 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14958 4-ISU2 and 24-ODU 203 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14930
Issue 03 (2011-04-10)
5-57
Parameter
Value 3-ISU2 and 23-ODU 4-ISU2 and 24-ODU 420 16 -43 unmute
T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status
420 16.5 -44 unmute
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value 4-ISU2 and 24-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 204 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14538 420 15 -45 unmute 3-ISU2 and 23-ODU 203 Hybrid(Native E1+ETH) 14M Enabled 16QAM 128QAM Disabled 2 14510 420 16 -43 unmute
Step 3 See A.5.8.1 Setting IF Attributes and set the IF attributes l The values for the relevant parameters of NE21 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot
5-58
4-ISU2 and 24-ODU Disabled
Disabled
Issue 03 (2011-04-10)
Step 4 See A.5.8.2 Configuring the ATPC Attributes and configure the ATPC function. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled 4-ISU2 and 24-ODU Disabled
l The values for the relevant parameters of NE23 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status
Issue 03 (2011-04-10)
4-ISU2 and 24-ODU Disabled

5-59
Disabled
----End
5.7 Configuration Example (Radio Links on the Packet Network)

This section considers radio links on a packet network as examples to describe how to configure radio links according to the network planning information. 5.7.1 Networking Diagram This section describes the networking information about the NEs. 5.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 5.7.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Based on 4.7 Configuration Example (Packet Network), configure radio links according to the network planning information (as shown in Figure 5-9). l l l The AM function is enabled for each radio link. To improve transmission reliability of important services, the radio links between NE32 and NE33 are configured as a 1+1 HSB protection group. The service capacity accessed by each BTS is provided in Table 5-45. Table 5-45 Service capacity accessed by each BTS BTS Capacity of highpriority services (Mbit/s) Capacity of lowpriority services (Mbit/s) BTS32 5 BTS33 1 BTS34 4
24
15
5-60
Issue 03 (2011-04-10)
NOTE
High-priority services are services that require transmission guarantees. High-priority services cannot be discarded in modulation scheme shifts. Low-priority services are services that do not require transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. Table 5-46 lists common high-priority services.
Table 5-46 Common service priorities Service Type TDM E1s that transmit 2G base station services ATM E1s (IMA E1s are not used) that transmit 3G base station services E1s (of a bandwidth not lower than the high-priority service bandwidth) in the IMA E1 group that transmits 3G base station services Other E1s in the IMA E1 group that transmits 3G base station services Voice, signaling, and OM Ethernet services Streaming media, background, and interactive Ethernet services, for example, Internet services Service Class High-priority services High-priority services High-priority service
Low-priority services High-priority services Low-priority services
Figure 5-9 Networking diagram (Packet radio chain network)

302 14930M 14510M 7M 1+0 H-polarzation Tx low Tx high Tx high 301 14967M 14547M 14M 1+1 V-polarization Tx low
BTS33 NE34 BTS34 BTS32 NE32

NE33
Issue 03 (2011-04-10)
5-61
The connections of radio links shown in Figure 5-9 are described as follows. Table 5-47 Connections of radio links (NE32) Link Between NE32 and NE33 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configures a 1+1 HSB protection group.
Table 5-48 Connections of radio links (NE33) Link Between NE33 and NE32 Port 4-ISU2 (main IF board) 6-ISU2 (standby IF board) Between NE33 and NE34 3-ISU2 Description Configures a 1+1 HSB protection group. Receives and transmits Packet radio services.
Table 5-49 Connections of radio links (NE34) Link Between NE34 and NE33 Port 3-ISU2 Description Receives and transmits Packet radio services.

The service planning information contains all the parameters required for configuring the NE data.

Based on the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about radio links as shown in Table 5-50. Table 5-50 Basic information about radio links Parameter Link ID Tx high site Tx low site
5-62
Link 1 301 NE33 NE32

Link 2 302 NE33 NE34

Issue 03 (2011-04-10)
Parameter Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Channel spacing (MHz) RF configuration mode Polarization direction
Link 1 14967 14547 420 14 1+1 HSB V (vertical polarization)
Link 2 14930 14510 420 7 1+0 H (horizontal polarization)
NOTE
The link planning information that is not associated with the configuration of IDU (except for the polarization direction) is not provided in this example.

According to the capacity of E1 and Ethernet services and the availability requirement, you can calculate the Hybrid/AM attribute information, as provided in Table 5-51. Table 5-51 Hybrid/AM attribute information Parameter Capacity of high-priority services (Mbit/s) Capacity of low-priority services (Mbit/s) AM enable status Modulation mode of the guarantee AM capacity Modulation mode of the full AM capacity Link 1 10 43 Enabled QPSK 64QAM Link 2 5 19 Enabled QPSK 32QAM
NOTE
The Hybrid radio capacity and the AM function are available only if the corresponding license files are configured.

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the radio link power and ATPC information as shown in Table 5-52.
Table 5-52 Power and ATPC information Parameter Transmit power (dBm) Link 1 16 (NE32) 16 (NE33) Receive power (dBm) -43 (NE32) -43 (NE33) ATPC enabling Automatic ATPC threshold setting Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Maximum transmit power (dBm) Disabled Link 2 20 (NE33) 20 (NE34) -48 (NE33) -48 (NE34) Disabled -
NOTE
Information About IF boards

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1 protection, you can obtain the information about IF boards as provided in Table 5-53. Table 5-53 Information about IF boards Parameter Main IF board Link 1 3-ISU2 (NE32) 4-ISU2 (NE33) Standby IF board 5-ISU2 (NE32) 6-ISU2 (NE33) RF configuration mode Revertive Mode WTR time Enable reverse switching 1+1 HSB Revertive (default value) 600s (default value) Disabled 1+0 Link 2 3-ISU2 (NE33) 3-ISU2 (NE34) -
5-64
Issue 03 (2011-04-10)
NOTE

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection group on NE32 and NE33. l The values for the related parameters of NE32 are provided as follows. Parameter Value NE32 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 3-ISU2 5-ISU2
l The values for the related parameters of NE33 are provided as follows. Parameter Value NE33 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode 600 Disabled 4-ISU2 6-ISU2
Issue 03 (2011-04-10)
5-65
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information for radio links. l The values for the related parameters of NE32 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 301 Hybrid(Native E1+ETH) 14M Enabled QPSK 64QAM Disabled 0 14547 420 16 -43 unmute
l The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority
5-66
4-ISU2 and 24-ODU 301 Hybrid(Native E1+ETH) 14M Enabled QPSK 64QAM Disabled
Issue 03 (2011-04-10)
302 Hybrid(Native E1+ETH) 7M Enabled QPSK 32QAM Disabled
Parameter
Value 3-ISU2 and 23-ODU 4-ISU2 and 24-ODU 0 14967 420 16 -43 unmute
Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status
0 14930 420 20 -48 unmute
l The values for the related parameters of NE34 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Link ID IF Service Type IF Channel Bandwidth AM Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Full E1 Capacity TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received(dBm) TX Status 302 Hybrid(Native E1+ETH) 7M Enabled QPSK 32QAM Disabled 0 14510 420 20 -48 unmute
Step 3 See A.5.8.1 Setting IF Attributes and configure IF attributes. l The values for the related parameters of NE32 are provided as follows.
Parameter
Enable IEEE-1588 Timeslot
Enabled
l The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot Enabled 4-ISU2 and 24-ODU Enabled
l The values for the related parameters of NE34 are provided as follows. Parameter Value 3-ISU2 and 23-ODU Enable IEEE-1588 Timeslot Enabled
Step 4 See A.5.8.2 Configuring the ATPC Attributes and set the ATPC function. l The values for the related parameters of NE32 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled
l The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled 4-ISU2 and 24-ODU Disabled
l The values for the related parameters of NE34 are provided as follows. Parameter Value 3-ISU2 and 23-ODU ATPC Enable Status Disabled
----End
5-68
Issue 03 (2011-04-10)
6 Configuring TDM Services
6
About This Chapter
Configuring TDM Services
The key to configuring TDM services is configuring the corresponding service crossconnections. 6.1 Basic Concepts Before configuring the TDM service, you need to be familiar with the basic concepts. 6.2 Configuration Procedure This section describes the procedures for configuring the cross-connections and protection of a TDM service and the procedures for setting the SDH/PDH port parameters. 6.3 Configuration Example (TDM Services on a TDM Radio Chain Network) This section considers a TDM radio chain network as an example to describe how to configure TDM services according to the network planning information. 6.4 Configuration Example (TDM Services on a TDM Radio Ring Network) This section considers a TDM radio ring network as an example to describe how to configure TDM services according to the network planning information. 6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network) This section considers a Hybrid radio chain network as an example to describe how to configure TDM services according to the network planning information. 6.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network) This section considers a Hybrid radio ring network as an example to describe how to configure TDM services according to the network planning information.
Issue 03 (2011-04-10)
6-1
6.1 Basic Concepts

Before configuring the TDM service, you need to be familiar with the basic concepts. 6.1.1 Protection Modes for TDM Services The OptiX RTN 950 supports linear MSP and SNCP for TDM services. 6.1.2 Timeslots for TDM Services on IF Boards When TDM services need to be transmitted on a radio link, you need to configure the corresponding cross-connections between the service timeslots on the service board and the service timeslots on the IF board. The timeslots for the TDM services on the IF board are closely related to the type of the radio services transmitted by the IF board and the radio capacity. 6.1.3 Numbering Schemes for SDH Timeslots Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or SDH radio links. 6.1.4 TDM Timeslot Planning Schemes The timeslot allocation diagram illustrates the TDM timeslot planning scheme.
6.1.1 Protection Modes for TDM Services

The OptiX RTN 950 supports linear MSP and SNCP for TDM services.
Linear MSP
Linear MSP applies to point-to-point physical networks. Linear MSP provides protection for the services between two multiplex section termination (MST) modules. That is, when a linear MSP switching occurs, the services are switched from the working section to the protection section. In the case of the OptiX RTN 950, linear MSP provides protection for TDM services that are transmitted over SDH fibers. Linear MSP is classified into 1+1 linear MSP and 1:N linear MSP. l 1+1 linear MSP To realize the 1+1 linear MSP, one working channel and one protection channel are required. The protection channel does not transmit extra services. When the working channel becomes unavailable, services are switched to the protection channel for transmission. Figure 6-1 shows the application of 1+1 linear MSP. According to the revertive mode, 1+1 linear MSP is classified into dual-ended revertive, dual-ended nonrevertive, single-ended revertive, and single-ended non-revertive modes. The single-ended non-revertive mode is the most common linear MSP mode.
6-2
Issue 03 (2011-04-10)
Figure 6-1 1+1 linear MSP

NE A Working channel NE B
Protection channel
Protection switching NE A Working channel NE B
Protection channel
1:N linear MSP To realize the 1:N linear MSP, N working channels and one protection channel are required. The working channels transmit normal services and the protection channel transmits extra services. When a working channel becomes unavailable, the services on this channel are switched to the protection channel for transmission. As a result, the extra services previously transmitted on this protection channel are interrupted. Figure 6-2 shows the application of the 1:N linear MSP. The 1:N linear MSP is available only in dual-ended revertive mode.
Issue 03 (2011-04-10)
6-3
Figure 6-2 1:N linear MSP

NE A Normal service 1 Working channel 1 NE B Normal service1
...
Normal service N Extra service
Working channel N Protection channel
...
Protection switching NE A Normal service 1 Working channel 1 NE B Normal service1
...
Working channel N Protection channel
...
SNCP
In the case of subnetwork connection protection (SNCP), the protection subnetwork connection takes over when the working subnetwork connection fails or deteriorates. In the case of the OptiX RTN 950, SNCP provides protection for TDM services that are transmitted on STM-1 fiber ring networks, TDM radio ring networks, Hybrid radio ring networks, or hybrid ring networks that comprise optical network equipment and Hybrid radio equipment. The SNCP protection scheme, which requires one working subnetwork and one protection subnetwork, selects one service from the dually transmitted services. In the case of SNCP, the services are switched to the protection subnetwork for transmission when the working subnetwork connection fails or deteriorates. Figure 6-3 shows the application of SNCP.
6-4
Issue 03 (2011-04-10)
Figure 6-3 SNCP

Working SNC Trail source Trail sink
NE A Protection SNC
NE B
Protection switching
Working SNC Trail source Trail sink
NE A Protection SNC
NE B
The OptiX RTN 950 supports the coexistence of SNCP and the 1+1 protection or N+1 protection. In the case of coexistence of the SNCP and the 1+1 protection or N+1 protection, you can set the hold-off time for SNCP so that the protection switching for the radio link can be performed first, thus preventing circular switchings.
6.1.2 Timeslots for TDM Services on IF Boards

When TDM services need to be transmitted on a radio link, you need to configure the corresponding cross-connections between the service timeslots on the service board and the service timeslots on the IF board. The timeslots for the TDM services on the IF board are closely related to the type of the radio services transmitted by the IF board and the radio capacity.
TDM Radio
When the IF board works in PDH radio mode and when the radio capacity is nxE1, the first to nth VC-12 timeslots on the IF board are available and correspond to first to nth E1s that are transmitted over microwave. For example, if the radio capacity is 4xE1, only the first to fourth VC-12 timeslots in VC4-1 on the IF board are available. If a cross-connection is configured between the E1 port of a service board and the second VC-12 in VC4-1 on the IF board, the E1 services that are accessed from the E1 port are sent to the second E1 timeslot that is transmitted over radio. If the radio capacity is E3, only the first VC-3 timeslot in VC4-1 on the IF board is available and corresponds to the E3 timeslot that is transmitted over microwave.
When the IF board works in STM-1 radio mode, all the timeslots in VC4-1 on the IF board are available and correspond to the timeslots in the VC-4 that is transmitted on microwave.
Hybrid Radio
When the IF board works in Hybrid radio mode and when the Guarantee E1 Capacity is set to n in Hybrid/AM Configuration, the first to nth VC-12 timeslots on the IF board are available and correspond to the first to nth E1 timeslots that are transmitted over microwave. For example, if the E1 capacity is 75xE1, only the first to sixty-third VC-12 timeslots in VC4-1 and the first to twelfth VC-12 timeslots in VC4-2 on the IF board are available. If a cross-connection is configured between the E1 port of a service board and the second VC-12 in VC4-2 on the IF board, the E1 services that are accessed from the E1 port are sent to the sixty-fifth E1 timeslot that is transmitted over microwave.
6.1.3 Numbering Schemes for SDH Timeslots

Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or SDH radio links.
VC-12 Timeslot Numbering

Two numbering schemes are applicable to SDH optical/electrical lines or SDH radio links when you create cross-connections. l By order This timeslot numbering scheme is also considered as timeslot scheme. The numbering formula is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number -1) x 21. This scheme is the numbering scheme recommended by ITU-T G.707 and is the default scheme adopted by the OptiX equipment. l Interleaved scheme This timeslot numbering scheme is also considered as line scheme. The numbering formula is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1) x 3 + TU-12 number. The OptiX equipment can adopt this scheme when it interconnects with the equipment that adopts the interleaved scheme or when a specific timeslot numbering scheme is required. Figure 6-4 Numbering VC-12 timeslots by order
TUG-2 1 1 2 4 25 46 5 26 47 6 27 48 3 7 28 49 8 29 50 9 30 51 4 10 31 52 11 32 53 12 33 54 5 13 34 55 14 35 56 15 36 57 6 16 37 58 17 38 59 18 39 60 7 19 40 61 20 41 62 21 42 63 1 2 3 1 2 3 1 2 3 TU-12
TUG-3
{ { {
1 22 43 2 23 44 3 24 45
6-6
Issue 03 (2011-04-10)
Figure 6-5 Numbering VC-12 timeslots in the interleaved scheme

1 2 4 5 6 25 26 27 46 47 48 3 7 8 9 28 29 30 49 50 51 TUG-2 4 10 11 12 31 32 33 52 53 54 5 13 14 15 34 35 36 55 56 57 6 16 17 18 37 38 39 58 59 60 7 19 20 21 40 41 42 61 62 63 1 2 3 1 2 3 1 2 3 TU-12
TUG-3
{ { {
1 2 3 22 23 24 43 44 45
VC-3 Timeslot Numbering

A VC-3 timeslot number corresponds to a TUG-3 number. If you need to configure crossconnections of VC-3s and VC-12s in the same VC-4, note that the timeslots in the TUG-3 that are occupied by the VC-3 cross-connections cannot be configured for VC-12 cross-connections.
6.1.4 TDM Timeslot Planning Schemes

The timeslot allocation diagram illustrates the TDM timeslot planning scheme.
Timeslot Allocation Diagram

The timeslot allocation diagram provides significant references for configuring TDM services. Before planning TDM timeslots, you need to be familiar with the meanings shown in the timeslot allocation diagram.
Issue 03 (2011-04-10)
6-7
Figure 6-6 Timeslot allocation diagram

Site Timeslot NE1 Interface board 1 Tributary board: port No. Tributary board: port No. NE2 Interface Interface board 2 board 3 Timeslot 1 Timeslot 2 Timeslot 3 Timeslot 4 Tributary board: port No. Tributary board: port No. Timeslot 5 Tributary board: port No. NE3 Interface board 5 NE4 Interface board 6
Interface board 4
VC4-1
Tributary board: Tributary board: Tributary board: port No. port No. port No.
VC4-2
......
......
Site area Timeslot area Timeslot allocation area
Add/Drop Foward Pass-through Add/Drop (SNCP path)
As shown in Figure 6-6, the timeslot allocation diagram contains three areas, namely, site area, timeslot area, and timeslot allocation area. The site area contains the NE icons and interface boards that carry radio links. l The start and end NEs each have only one interface board, which is located under the NE icon. The intermediate NEs each have two interface boards, which are located at the two sides of the vertical line under the NE icon. The interface boards may be IF boards or line boards. The interface board on the left side of the vertical line under an NE icon is connected to the interface board on the right side of the vertical line under its upstream NE icon. The interface board on the right side of the vertical line under an NE icon is connected to the interface board on the left side of the vertical line under its downstream NE icon. In the case of a ring radio link, before planning the site area, you need to divide the ring radio link into a chain radio link and ensure that the start and end NEs are the same one.
The timeslot area represents the VC-4 timeslot resources. For example, in the case of radio links, timeslots occupied by an STM-1 service are all in the first VC-4. In the timeslot allocation area, each straight line represents a service and the numeric above the straight line represents the timeslot occupied by this service. l A black dot indicates that services are added to or dropped from the NE. The board under a black dot indicates the board and corresponding ports on the board that are used for adding or dropping services. An arrow indicates that services are transferred on the NE. If a straight line passes a vertical line without any arrow or black dot, it indicates that services pass through the NE. In the case of protection configuration (for example, 1+1 HSB protection) wherein the working service and protection service have the uniform route, you only need to draw a continuous line to represent the working service. In the case of protection configuration
l l l
6-8
(for example, SNCP) wherein the working service and protection service have different routes, you need to draw a continuous line to represent the working service and a dotted line to represent the protection service.
TDM Timeslot Planning Scheme for Chain Networks

On the backhaul network for a mobile BTS, the services are accessed from different nodes and then aggregated to the same node for transmission. In this case, allocate the timeslots on the chain radio network as follows: 1. Select the chain that contains the maximum of hops as the main chain. Then, divide the chain network into several sub-chains by considering the main chain as the reference. Consider the E1 channels or fiber connections that are used for transferring services between NEs as links. Allocate the timeslots for the add/drop or pass-through services on the NEs of the main chain one after another, in the descending order of the NE distance. Repeat the previous step to configure the timeslots for the services on all the sub-chains.
2. 3.
This timeslot allocation method ensures that only the numbers of the timeslots that the services on the nodes of the aggregation sub-chain occupy may change. The principles for obtaining the timeslot cross-connection configurations from the non-SNCP service timeslot allocation diagram are as follows: l l The vertical line under the NE name is considered as the reference. If a straight line representing a pass-through service crosses the vertical line, it indicates that cross-connections are configured between the boards on both sides of the vertical line. The corresponding cross-connected timeslots are marked over the straight line. If there is a straight line with one dot on one side of the vertical line, it indicates that crossconnections are configured between the board on this side of the vertical line and the board under the straight line with one dot. The corresponding cross-connected timeslots are marked over the straight line with one dot. If there is a straight line with an arrow on both sides of the vertical line, it indicates that cross-connections are configured between the two boards on both sides of the vertical line. The corresponding cross-connected timeslots on each board are marked over the straight line with an arrow on the side of this board.
For details, see 6.3 Configuration Example (TDM Services on a TDM Radio Chain Network) and 6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network).
TDM Timeslot Planning Scheme for Ring Networks

On a backhaul network for a mobile BTS, the services are accessed from different nodes and then aggregated to the same node for transmission. Hence, you can perform the following operations to allocate the timeslots on the SNCP radio ring network: 1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate the minimum VC-12 timeslot number to the service on the nearest NE. The number of the timeslot each service occupies does not change on the ring network. Repeat the previous step to configure the timeslots for the services on all the sub-chains.
2.
This timeslot allocation method ensures that only the timeslots that the services on the nodes of the aggregation sub-chain occupy change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service timeslot allocation diagram are as follows: l l The vertical line under the NE name is considered as the reference. If a straight line representing a pass-through service crosses the vertical line, it indicates that cross-connections are configured between the boards on both sides of the vertical line. The corresponding cross-connected timeslots are marked over the straight line. If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP cross-connections are configured between the board on this side of the vertical line and the board under the straight line with one dot. The corresponding cross-connected timeslots are marked over the straight line with one dot.
For details, see 6.4 Configuration Example (TDM Services on a TDM Radio Ring Network) and 6.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network).

This section describes the procedures for configuring the cross-connections and protection of a TDM service and the procedures for setting the SDH/PDH port parameters. Figure 6-7 provides the procedures for configuring TDM services.
6-10
Issue 03 (2011-04-10)
Figure 6-7 Configuration flow chart (TDM services)

Required Start
Optional Configuring MSP
Creating TDM service crossconnections
Configuring the automatic switching conditions of SNCP services
Modifying the priorities of E1 services
Configuring the overhead bytes
Setting parameters of SDH port
Setting parameters of PDH ports
Performing PRBS tests for E1 services
End
Issue 03 (2011-04-10)
6-11
Table 6-1 Procedures for configuring TDM services Step 1 Operation A.3.1 Configuring Linear MSP Description Required when linear MSP is configured for the optical transmission line. The parameters need to be set according to the service planning. 2 Configuri ng the crossconnectio ns of the TDM servicea A.4.1 Creating the CrossConnectio ns of Point-toPoint Services A.4.2 Creating CrossConnectio ns of SNCP Services 3 A.4.5 Configuring the Automatic Switching of SNCP Services A.4.3 Modifying the Priorities of E1 Services Required when the TDM service is a point-to-point service. The parameters need to be set according to the service planning.
Required when the TDM service is an SNCP service. The parameters need to be set according to the service planning.
Optional when the TDM service is an SNCP service.
Required when the working source, protection source, or sink of an SNCP service is a link where the AM function and the E1 priority function are enabled or when the E1 priority of a crossconnection needs to be changed. E1 Priority needs to be modified according to the service planning information.
NOTE When the radio link on which the AM function is enabled is configured with the E1 priority, note the following: l If the cross-connection is configured for a point-topoint service, the E1 priority is configured when the cross-connection is created. l If the cross-connection is configured for an SNCP service, the E1 priority is modified after the crossconnection is created. l If the service priority is not configured when the crossconnection is created (that is, E1 Priority is set to None), E1 Priority of each service must be set to a specific value after the cross-connection is configured.
Configuri ng the overhead bytes
A.5.3.1 Configuri ng RSOHs
Required when the J0_MM alarm is generated on the local or remote equipment.
6-12
Issue 03 (2011-04-10)
Step
Operation A.5.3.2 Configuri ng VC-4 POHs A.5.3.3 Configuri ng VC-12 POHs
Description Required when the TIM or SLM alarm is generated on the local or remote equipment.
Required when the TIM or SLM alarm is generated on the local or remote equipment.
A.5.1 Setting the Parameters of SDH Ports A.5.2 Setting the Parameters of PDH Ports A.12.1 Testing E1 Services Using PRBS
Optional.
Optional.
The test results should show that each E1 service contains no bit errors.
NOTE
a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure the TDM service on the working channel only. In the case of N+1 protection configuration or 1:N linear MSP configuration, you need to configure TDM services on the working channels and the extra service (if any) on the protection channel.
6.3 Configuration Example (TDM Services on a TDM Radio Chain Network)

This section considers a TDM radio chain network as an example to describe how to configure TDM services according to the network planning information. 6.3.1 Networking Diagram This section describes the networking information about the NEs. 6.3.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 6.3.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Based on 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network), configure the TDM services according to the following network planning information (as shown in Figure 6-8):
l l
To ensure reliable transmission of the services between NE11 and the third-party network, linear MSP is configured for the optical transmission line. Services are transferred between NE12 and NE13 through STM-1 optical ports.
Figure 6-8 Networking diagram (TDM services on a TDM radio chain network)
8xE1 BTS12 8xE1 BTS13 NE13 14xE1 NE15 BTS14 NE12 BTS11 STM-1 NE14 16xE1 NE11 STM-1 Third party network
8xE1 NE16 BTS15
The connections of TDM links shown in Figure 6-8 are described as follows. Table 6-2 Connections of TDM links (NE11) Link Between NE11 and the thirdparty network Between NE11 and NE12 Port 1-SL1D-1 (working port) 1-SL1D-2 (protection port) 3-IF1 (main IF board) 5-IF1 (standby IF board) Description Configure the ports as a 1+1 linear MSP group. Configure the ports as a 1+1 HSB protection group.
Table 6-3 Connections of TDM links (NE12) Link Between NE12 and BTS11 Between NE12 and NE11 Port 2-SP3S (1-16) 3-IF1 (main IF board) 5-IF1 (standby IF board) Between NE12 and NE13 1-SL1D-1 Description Configure the ports to access services from BTS11. Configure the ports as a 1+1 HSB protection group. Configure this port to transmit TDM services.
6-14
Issue 03 (2011-04-10)
Table 6-4 Connections of TDM links (NE13) Link Between NE13 and NE12 Between NE13 and NE14 Port 1-SL1D-1 3-IF1 (main IF board) 5-IF1 (standby IF board) Between NE13 and NE15 4-IF1 (main IF board) 6-IF1 (standby IF board) Description Configure this port to transmit TDM services. Configure the ports as a 1+1 HSB protection group. Configure the ports as a 1+1 HSB protection group.
Table 6-5 Connections of TDM links (NE14) Link Between NE14 and BTS12 Between NE14 and BTS13 Between NE14 and NE13 3-IF1 (main IF board) 5-IF1 (standby IF board) Port 2-SP3S (1-16) Description Configure the ports to access services from BTS12 and BTS13. Configure the ports as a 1+1 HSB protection group.
Table 6-6 Connections of TDM links (NE15) Link Between NE15 and BTS14 Between NE15 and NE13 Port 2-SP3S (1-14) 4-IF1 (main IF board) 6-IF1 (standby IF board) Between NE15 and NE16 3-IF1 Description Configure the ports to access services from BTS14. Configure the ports as a 1+1 HSB protection group. Configure this port to receive and transmit radio service signals.
Table 6-7 Connections of TDM links (NE16) Link Between NE16 and BTS15 Port 2-SP3S (1-8) Description Configure the ports to access services from BTS15.
Issue 03 (2011-04-10)
6-15
Link Between NE16 and NE15
Port 3-IF1
Description Configure this port to receive and transmit radio service signals.


Figure 6-9 shows the timeslots that are allocated for the TDM services according to the service planning information. Figure 6-9 Timeslot allocation diagram (TDM services on the TDM radio chain network)
Links-1: NE11 - NE12 - NE13 -NE15 -NE16 Station BSC Timeslot NE11 NE12 3-IF1 1-SL1D-1 NE13 1-SL1D-1 4-IF1 NE15 4-IF1 3-IF1 NE16 3-IF1 2-SP3S:1-8 2-SP3S:1-14
1-SL1D-1 3-IF1 VC12: 1-8 VC12: 9-22
VC4-1
VC12: 23-38 VC12: 39-54 2-SP3S:1-16
Links-2: NE13-NE14 Station Timeslot VC4-1 NE13 1-SL1D-1 3-IF1 VC12: 23-38 VC12: 1-16 2-SP3S:1-16 NE14 3-IF1
Pass through Add/Drop Foward
As shown in Figure 6-9, the information about the timeslots that the TDM services occupy on each NE is as follows: l E1 services on NE16: The E1 services are added to or dropped from the first to eighth ports on the SP3S board in slot 2 of NE16. The E1 services occupy the first to eighth VC-12 timeslots on the link between the first optical port on the SL1D board in slot 1 of NE11 and the IF1 board in slot 3 of NE16. l E1 services on NE15: The E1 services are added to or dropped from the first to fourteenth ports on the SP3S board in slot 2 of NE15.
The E1 services occupy the ninth to twenty-second VC-12 timeslots on the link between the first optical port on the SL1D board in slot 1 of NE11 and the IF1 board in slot 3 of NE15. l E1 services on NE14: The E1 services are added to or dropped from the first to sixteenth ports on the SP3S board in slot 2 of NE14. The E1 services occupy the twenty-third to thirty-eighth VC-12 timeslots on the link between the first optical port on the SL1D board in slot 1 of NE11 and the SL1D board in slot 1 of NE13. The E1 services occupy the first to sixteenth VC-12 timeslots on the link between the IF1 board in slot 3 of NE13 and the IF1 board in slot 3 of NE14. l E1 services on NE12: The E1 services are added to or dropped from the first to sixteenth ports on the SP3S board in slot 2 of NE12. The E1 services occupy the thirty-ninth to fifty-fourth VC-12 timeslots on the link between the first optical port on the SL1D board in slot 1 of NE11 and the IF1 board in slot 3 of NE12.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended non-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE11 and the third-party network. Table 6-8 provides the related planning information. Table 6-8 Linear MSP Parameter Protection Type Switching Mode Revertive Mode SD Switching Protocol Type West Working Unit West Protection Unit NE11 1+1 Linear MSP Single-Ended Switching Non-Revertive Enabled (default value) New Protocol (default value) 1-SL1D-1 1-SL1D-2
NOTE
Unless otherwise specified, SD Switching, Protocol Type take the default values.

Issue 03 (2011-04-10)
6-17
Procedure
Step 1 See A.3.1 Configuring Linear MSP and configure 1+1 linear MSP. The values for the related parameters are provided as follows. Parameter Value NE11 Protection Type Switching Mode Revertive Mode WTR Time(s) SD Switching Protocol Type Mapped Boards 1+1 Linear MSP Single-Ended Switching Non-Revertive 600 Enabled New Protocol l West Working Unit: 1-SL1D-1 l West Protection Unit: 1-SL1D-2
Step 2 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and create the pointto-point service cross-connections. l The values for the related parameters of NE11 are provided as follows. Parameter Value NE11 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 Bidirectional 1-SL1D 1 VC4-1 1-54 3-IF1 1 VC4-1 1-54
l The values for the related parameters of NE12 are provided as follows.
6-18
Issue 03 (2011-04-10)
Parameter
Value NE12
Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6)
VC-12 Bidirectional 3-IF1 1 VC4-1 1-38 1-SL1D 1 VC4-1 1-38
VC-12 Bidirectional 3-IF1 1 VC4-1 39-54 2-SP3S 1-16
l The values for the related parameters of NE13 are provided as follows. Parameter Value NE13 Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) VC-12 Bidirectional 1-SL1D 1 VC4-1 1-22 4-IF1 1 VC4-1 1-22 VC-12 Bidirectional 1-SL1D 1 VC4-1 23-38 3-IF1 1 VC4-1 1-16
Issue 03 (2011-04-10)
6-19
Parameter
Value NE14
Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
l The values for the related parameters of NE15 are provided as follows. Parameter Value NE15 Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) VC-12 Bidirectional 4-IF1 1 VC4-1 1-8 3-IF1 1 VC4-1 1-8 VC-12 Bidirectional 4-IF1 1 VC4-1 9-22 2-SP3S 1-14
6-20
Issue 03 (2011-04-10)
Parameter
Value NE16
Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
Step 3 See A.12.1 Testing E1 Services Using PRBS and test the E1 services. Test two E1 services on each BTS. The test results should show that the E1 services contain no bit errors. ----End
6.4 Configuration Example (TDM Services on a TDM Radio Ring Network)

This section considers a TDM radio ring network as an example to describe how to configure TDM services according to the network planning information. 6.4.1 Networking Diagram This section describes the networking information about the NEs. 6.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 6.4.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Based on 5.4 Configuration Example (Radio Links on the TDM Radio Ring Network), configure the TDM services according to the service requirements. To ensure reliable transmission of the services between the BTSs and the third-party network, SNCP is configured to provide protection for TDM services on the ring network. See Figure 6-10.
Figure 6-10 Networking diagram (TDM services on a TDM radio ring network)
Third party SDH network 16E1
NE21
4E1 BTS21 4E1 NE22 BTS22 4E1 NE23 BTS23 NE24 4E1 BTS24
The connections of TDM links shown in Figure 6-10 are described as follows. Table 6-9 Connections of TDM links (NE21) Link Between NE21 and the thirdparty network Between NE21 and NE22 Between NE21 and NE24 Port 2-SP3S (1-16) 4-IF1 3-IF1 (main IF board of a 1+1 SD protection group) 5-IF1 (standby IF board of a 1+1 SD protection group) Description Configure the ports to transmit TDM services. Configure the ports as east ports. Configure the ports as west ports.
Table 6-10 Connections of TDM links (NE22) Link Between NE22 and BTS21 Between NE22 and BTS22 Between NE22 and NE21 Between NE22 and NE23 3-IF1 4-IF1 Port 2-SP3S (1-8) Description Configure the ports to access services from BTS21 and BTS22. Configure the ports as west ports. Configure this port as an east port.
6-22
Issue 03 (2011-04-10)
Table 6-11 Connections of TDM links (NE23) Link Between NE23 and BTS23 Between NE23 and NE22 Between NE23 and NE24 Port 2-SP3S (1-4) 3-IF1 4-IF1 Description Configure the ports to access services from BTS23. Configure this port as a west port. Configure this port as an east port.
Table 6-12 Connections of TDM links (NE24) Link Between NE24 and BTS24 Between NE24 and NE21 Port 2-SP3S (1-4) 4-IF1 (main IF board of a 1+1 SD protection group) 6-IF1 (standby IF board of a 1+1 SD protection group) Between NE24 and NE23 3-IF1 Configure this port as a west port. Description Configure the ports to access services from BTS24. Configure the ports as east ports.


Figure 6-11 shows the timeslots that are allocated for the TDM services according to the service planning information. Figure 6-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)
Station Timeslot NE21 4-IF1 VC12: 1-8 2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8 VC12: 9-12 VC4-1 2-SP3S:9-12 2-SP3S:13-16 Pass through (SNCP working path) Pass through (SNCP protection path) Add/Drop (SNCP working path) Add/Drop (SNCP protection path) NE22 3-IF1 4-IF1 NE23 3-IF1 4-IF1 VC12: 1-8 2-SP3S:1-8 VC12: 9-12 2-SP3S:9-12 VC12: 13-16 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:13-16 NE24 3-IF1 4-IF1 NE21 3-IF1
2-SP3S:1-4 2-SP3S:1-4 VC12: 13-16
Issue 03 (2011-04-10)
6-23
As shown in Figure 6-11, the information about the timeslots that the TDM services occupy on each NE is as follows: l E1 services on NE22: The E1 services are added to or dropped from the first to eighth ports on the SP3S board in slot 2 of NE22. The E1 services are added to or dropped from the first to eighth ports on the SP3S board in slot 2 of NE21. The E1 services occupy the first to eighth VC-12 timeslots on the ring. l E1 services on NE23: The E1 services are added to or dropped from the first to fourth ports on the SP3S board in slot 2 of NE23. The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S board in slot 2 of NE21. The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring. l E1 services on NE24: The E1 services are added to or dropped from the first to fourth ports on the SP3S board in slot 2 of NE24. The E1 services are added to or dropped from the thirteenth to sixteenth ports on the SP3S board in slot 2 of NE21. The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 6-13 provides the information about SNCP. Table 6-13 SNCP Parameter Working Source Protection Source Revertive Mode WTR Time Hold-Off Time Switching Condition Value See the timeslot allocation diagram. See the timeslot allocation diagram. Revertive 600s (default value) 0 (default value) Necessary conditions for an SNCP switching (default values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.4.2 Creating Cross-Connections of SNCP Services and configure the SNCP service cross-connections. l The values for the related parameters of NE21 are provided as follows. Parameter Value NE21 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Bidirectional VC-12 0 Revertive 600 4-IF1 (working service) 3-IF1 (protection service) Source Port Source VC4 1 VC4-1 (working service) VC4-1 (protection service) Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) 1-12 2-SP3S 1-12 Bidirectional VC-12 0 Revertive 600 3-IF1 (working service) 4-IF1 (protection service) 1 VC4-1 (working service) VC4-1 (protection service) 13-16 2-SP3S 13-16
l The values for the related parameters of NE22 are provided as follows. Parameter Value NE22 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Bidirectional VC-12 0 Revertive 600
Issue 03 (2011-04-10)
6-25
Parameter
Value NE22
Source
3-IF1 (working service) 4-IF1 (protection service)
Source Port Source VC4
1 VC4-1 (working service) VC4-1 (protection service)
Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
1-8 2-SP3S 1-8
l The values for the related parameters of NE23 are provided as follows. Parameter Value NE23 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Bidirectional VC-12 0 Revertive 600 3-IF1 (working service) 4-IF1 (protection service) Source Port Source VC4 1 VC4-1 (working service) VC4-1 (protection service) Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) 9-12 2-SP3S 1-4
Parameter
Value NE24
Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source
Bidirectional VC-12 0 Revertive 600 4-IF1 (working service) 3-IF1 (protection service)
Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
13-16 2-SP3S 1-4
Step 2 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and configure the service cross-connections on NE22, NE23, and NE24. l The values for the related parameters of NE22 are provided as follows. Parameter Value NE22 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 VC-12 Bidirectional 3-IF1 1 VC4-1 9-16 4-IF1 1 VC4-1
Issue 03 (2011-04-10)
6-27
Parameter
Value NE22
Sink Timeslot Range(e.g.1,3-6)
9-16
l The values for the related parameters of NE23 are provided as follows. Parameter Value NE23 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 Bidirectional 3-IF1 1 VC4-1 1-8,13-16 4-IF1 1 VC4-1 1-8,13-16
l The values for the related parameters of NE24 are provided as follows. Parameter Value NE24 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 Bidirectional 3-IF1 1 VC4-1 1-12 4-IF1 1 VC4-1 1-12
6-28
Issue 03 (2011-04-10)
Step 3 See A.12.1 Testing E1 Services Using PRBS and test the E1 services. Test two E1 services on each BTS. The test results should show that the E1 services contain no bit errors. ----End
6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)

This section considers a Hybrid radio chain network as an example to describe how to configure TDM services according to the network planning information. 6.5.1 Networking Diagram This section describes the networking information about the NEs. 6.5.2 Service Planning This section provides the information about all the parameters required for configuring the NE data. 6.5.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure the TDM services according to the following network planning information (as shown in Figure 6-12): l l Services are transferred between NE12 and NE13 through E1 channels. The service capacity accessed by each BTS is provided in Table 6-14. Table 6-14 Service capacity accessed by each BTS BTS Number of high-priority E1 services Number of low-priority E1 services BTS13 1 0 BTS14 2 2
Issue 03 (2011-04-10)
6-29
Figure 6-12 Networking diagram (TDM services on a Hybrid radio chain network)
Packet network
1xE1 BTS13
E1 NE14 NE13 4xE1 NE12
NE11
NE16
NE15 BTS14
The connections of TDM links shown in Figure 6-12 are described as follows. Table 6-15 Connections of TDM links (NE11) Link Between NE11 and the PSN Between NE11 and NE12 Port 1-SP3S-1 (1-5) 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports to transmit TDM services. Configure the ports as a 1+1 HSB protection group.
Table 6-16 Connections of TDM links (NE12) Link Between NE12 and NE11 Port 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Between NE12 and NE13 2-SP3S (1-5) Description Configure the ports as a 1+1 HSB protection group. Configure the ports to transmit TDM services.
Table 6-17 Connections of TDM links (NE13) Link Between NE13 and NE12 Between NE13 and NE14 Port 2-SP3S (1-5) 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports to transmit TDM services. Configure the ports as a 1+1 HSB protection group.
6-30
Issue 03 (2011-04-10)
Port 4-ISU2 (main IF board) 6-ISU2 (standby IF board)
Description Configure the ports as a 1+1 HSB protection group.
Table 6-18 Connections of TDM links (NE14) Link Between NE14 and BTS13 Between NE14 and NE13 Port 2-SP3S (1) 3-ISU2 (main IF board) 5-ISU2 (standby IF board) Description Configure the ports to access services from BTS13. Configure the ports as a 1+1 HSB protection group.
Table 6-19 Connections of TDM links (NE15) Link Between NE15 and BTS14 Between NE15 and NE13 Port 2-SP3S (1-4) 4-ISU2 (main IF board) 6-ISU2 (standby IF board) Description Configure the ports to access services from BTS14. Configure the ports as a 1+1 HSB protection group.


Figure 6-13 shows the timeslots that are allocated for the TDM services according to the network planning information.
Issue 03 (2011-04-10)
6-31
Figure 6-13 Timeslot allocation diagram (TDM services on the Hybrid chain radio network)
Links-1: NE11 - NE12 - NE13 -NE5 Station Timeslot RNC NE11 1-SP3S 3-ISU2 VC12: 1-2 VC12: 3-4 VC4-1 VC12: 5 2-SP3S:1-2 2-SP3S:3-4 NE12 3-ISU2 2-SP3S NE13 2-SP3S 4-ISU2 NE15 4-ISU2
Links-2: NE13-NE14 Station Timeslot VC4-1 NE13 2-SP3S 3-ISU2 VC12: 5 VC12: 1 2-SP3S:1 NE14 3-ISU2
/ / /
Pass through(low/high) Add/Drop(low/high) Foward(low/high)
As shown in Figure 6-13, the information about the timeslots that the TDM services occupy on each NE is as follows: l E1 services on NE15 The E1 services are added to or dropped from ports 1-4 of the SP3S board in slot 2 on NE15.Ports 1 and 2 add and drop high-priority services and ports 3 and 4 add and drop low-priority services. The E1 services occupy the first to fourth VC-12 timeslots on the link between the SP3S board in slot 1 of NE11 and the ISU2 board in slot 4 of NE15. Ports 1 and 2 transmit high-priority services and ports 3 and 4 transmit low-priority services. l E1 services on NE14 The E1 services are added to or dropped from the first port on the SP3S board in slot 2 of NE14. The E1 services received by NE14 are high-priority services by default, because the E1 service priority function is disabled on the radio link to which NE14 belongs. The E1 services occupy the fifth VC-12 timeslot on the link between the SP3S board in slot 1 of NE11 and the SP3S board in slot 2 of NE13. The E1 services occupy the first VC-12 timeslot on the link between the ISU2 board in slot 3 of NE13 and the ISU2 board in slot 3 of NE14.

Procedure
Step 1 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and create point-topoint service cross-connections. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value NE11 Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) E1 Priority VC12 Bidirectional 1-SP3S 1-2,5 3-ISU2 1 VC4-1 1-2,5 High VC12 Bidirectional 1-SP3S 3-4 3-ISU2 1 VC4-1 3-4 Low
l The values for the relevant parameters of NE12 are provided as follows. Parameter Value NE12 Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 VC12 Bidirectional 3-ISU2 1 VC4-1 1-2,5 2-SP3S VC12 Bidirectional 3-ISU2 1 VC4-1 3-4 2-SP3S -
Issue 03 (2011-04-10)
6-33
Parameter
Value NE12
Sink Timeslot Range(e.g. 1,3-6) E1 Priority
1-2,5 High
3-4 Low
l The values for the relevant parameters of NE13 are provided as follows. Parameter Value NE13 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority VC12 Bidirectional 2-SP3S 1-2 4-ISU2 1 VC4-1 1-2 High VC12 Bidirectional 2-SP3S 3-4 4-ISU2 1 VC4-1 3-4 Low VC12 Bidirectional 2-SP3S 5 3-ISU2 1 VC4-1 1 -
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value NE14 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink
6-34
VC12 Bidirectional 3-ISU2 1 VC4-1 1 2-SP3S

Parameter
Value NE14
Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority
1 -
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value NE15 Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) E1 Priority VC12 Bidirectional 4-ISU2 1 VC4-1 1-2 2-SP3S 1-2 High VC12 Bidirectional 4-ISU2 1 VC4-1 3-4 2-SP3S 3-4 Low
Step 2 See A.12.1 Testing E1 Services Using PRBS and test the E1 services. Test one E1 service on BTS13 and BTS14. The test results should show that the E1 services contain no bit errors. ----End
6.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network)

This section considers a Hybrid radio ring network as an example to describe how to configure TDM services according to the network planning information. 6.6.1 Networking Diagram
This section describes the networking information about the NEs. 6.6.2 Service Planning This section provides the information about all the parameters required for configuring the NE data. 6.6.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about the NEs. Based on 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network), configure the TDM services according to the service requirements. To ensure reliable transmission of the services between the BTSs and the PSN, SNCP is configured to provide protection for TDM services on the ring network. See Figure 6-14.The service capacity accessed by each BTS is provided in Table 6-20. Table 6-20 Service capacity accessed by each BTS BTS Number of E1s BTS22 2
Figure 6-14 Networking diagram (TDM services on a Hybrid radio ring network)
Packet network BSC 2E1
NE21
BTS21 2E1 NE22 BTS22 NE24 BTS24
NE23 BTS23
The connections of TDM links shown in Figure 6-14 are described as follows.
6-36
Issue 03 (2011-04-10)
Table 6-21 Connections of TDM links (NE21) Link Between NE21 and the PSN Between NE21 and NE22 Between NE21 and NE24 Port 2-SP3S (1-2) 4-ISU2 3-ISU2 (main IF board of a 1 +1 SD protection group) 5-ISU2 (standby IF board of a 1+1 SD protection group) Description Configure the ports to transmit TDM services. Configure the ports as east ports. Configure the ports as west ports.
Table 6-22 Connections of TDM links (NE22) Link Between NE22 and BTS22 Between NE22 and NE21 Between NE22 and NE23 Port 2-SP3S (1-2) 3-ISU2 4-ISU2 Description Configure the ports to access services from BTS22. Configure the ports as west ports. Configure this port as an east port.
Table 6-23 Connections of TDM links (NE23) Link Between NE23 and NE22 Between NE23 and NE24 Port 3-ISU2 4-ISU2 Description Configure this port as a west port. Configure this port as an east port.
Table 6-24 Connections of TDM links (NE24) Link Between NE24 and NE21 Port 4-ISU2 (main IF board of a 1 +1 SD protection group) 6-ISU2 (standby IF board of a 1+1 SD protection group) Between NE24 and NE23 3-ISU2 Configure this port as a west port.
6-37
Description Configure the ports as east ports.
Issue 03 (2011-04-10)


Figure 6-15 shows the timeslots that are allocated for the TDM services according to the network planning information. Figure 6-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station Timeslot NE21 4-ISU2 VC12: 1-2 2-SP3S:1-2 2-SP3S:1-2 2-SP3S:1-2 NE22 3-ISU2 4-ISU2 NE23 3-ISU2 4-ISU2 VC12: 1-2 2-SP3S:1-2 NE24 3-ISU2 4-ISU2 NE21 3-ISU2
Pass through (SNCP working path) Pass through (SNCP protection path) Add/Drop (SNCP working path) Add/Drop (SNCP protection path)
As shown in Figure 6-15, the information about the timeslots that the TDM services occupy on each NE is as follows: E1 services on NE22: l l l The E1 services are added to or dropped from the first to second ports on the SP3S board in slot 2 of NE22. The E1 services are added to or dropped from the first to second ports on the SP3S board in slot 2 of NE21. The E1 services occupy the first to second VC-12 timeslots on the ring.
SNCP
Table 6-25 provides the information about SNCP. Table 6-25 SNCP Parameter Working Source Protection Source Revertive Mode WTR Time Hold-Off Time
6-38
Value See the timeslot allocation diagram. See the timeslot allocation diagram. Revertive 600s (default value) 0 (default value)
Parameter Switching Condition
Value Necessary conditions for an SNCP switching (default values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.4.2 Creating Cross-Connections of SNCP Services and configure the SNCP service cross-connections. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value NE21 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Bidirectional VC-12 0 Revertive 600 4-ISU2 (working service) 3-ISU2 (protection service) Source Port Source VC4 1 VC4-1 (working service) VC4-1 (protection service) Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority 1-2 2-SP3S 1-2 -
Parameter
Value NE22
Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source
Bidirectional VC-12 0 Revertive 600 3-ISU2 (working service) 4-ISU2 (protection service)
Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority
1-2 2-SP3S 1-2 -
Step 2 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and configure the service cross-connections on NE23 and NE24. l The values for the relevant parameters of NE23 are provided as follows. Parameter Value NE23 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port VC-12 Bidirectional 3-ISU2 1 VC4-1 1-2 4-ISU2 1
6-40
Issue 03 (2011-04-10)
Parameter
Value NE23
Sink VC4 Sink Timeslot Range(e.g.1,3-6) Priority
VC4-1 1-2 -
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value NE24 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) Priority VC-12 Bidirectional 3-ISU2 1 VC4-1 1-2 4-ISU2 1 VC4-1 1-2 -
Step 3 See A.12.1 Testing E1 Services Using PRBS and test the E1 services. Test one E1 service on BTS22. The test results should show that the E1 services contain no bit error. ----End
Issue 03 (2011-04-10)
6-41
7 Configuring Native Ethernet Services on the Packet Plane
Configuring Native Ethernet Services on the Packet Plane
About This Chapter

Native Ethernet services on the packet plane include Native E-Line services and Native E-LAN services. 7.1 Basic Concepts Before configuring the Ethernet services, you need to be familiar with the basic concepts. 7.2 Configuration Procedure The service configuration procedure differs according to the specific service type. 7.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services) This section considers a point-to-point transparently transmitted E-Line service as an example to describe how to configure the Ethernet service according to the network planning information. 7.4 Configuration Example (VLAN-Based E-Line Service) This section considers a VLAN-based E-line service as an example to describe how to configure the Ethernet service according to the network planning information. 7.5 Configuration Example (QinQ-Based E-Line Service) This section considers a QinQ-based E-line service as an example to describe how to configure the Ethernet service according to the network planning information. 7.6 Configuration Example (802.1d-Bridge-Based E-LAN Service) This section considers an 802.1d-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.7 Configuration Example (802.1q-Bridge-Based E-LAN Service) This section considers an 802.1q-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service) This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)
This section describes how to configure a radio network that transmits E-Line services and ELAN services at the same time according to the network planning information.
7-2
Issue 03 (2011-04-10)
7.1 Basic Concepts

Before configuring the Ethernet services, you need to be familiar with the basic concepts. 7.1.1 What's the Packet Plane The packet plane refers to the switching plane provided by the packet switching unit on a system control, switching, and timing board. The packet plane provides a wide range of services and features based on Native Ethernet, as well as a wide range of services and features based on MPLS/PWE3. 7.1.2 Ethernet Port Numbers On the NMS, Ethernet ports are represented by PORTs. 7.1.3 Auto-Negotiation The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network and to receive the corresponding information that the opposite end may transfer. 7.1.4 Flow Control Function When the equipment fails to handle the flow received at the port due to poor data processing/ transferring capability, congestion occurs on the line. To reduce the number of discarded packets caused by buffer overflow, proper flow control measures must be taken. 7.1.5 Native Ethernet Service Types Based on the Packet Plane Based on the packet plane, Native Ethernet services are classified into six types. 7.1.6 Typical Mobile Carrier Network Topologies for Ethernet Services Generally, Ethernet services are transmitted in three network topologies on a mobile carrier network. 7.1.7 MAC Address Table Management The entries in a MAC address table indicate the mappings between MAC addresses and ports. A MAC address table contains dynamic entries, static entries, and blacklist entries. 7.1.8 VLAN Forwarding Table Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If changing VLAN IDs is required, configure a VLAN forwarding table. 7.1.9 Split Horizon Group To separate services that are converged and to prevent broadcast storm resulting from a service loop, you can configure a split horizon group for the E-LAN services at the specified nodes. After the configuration, the logical ports in one split horizon group cannot forward packets to each other. 7.1.10 Protection for Native Ethernet Services Based on the Packet Plane The OptiX RTN 950 supports three protection modes for Native Ethernet services, namely, Ethernet ring protection switching (ERPS), link aggregation group (LAG), and multiple spanning tree protocol (MSTP).
7.1.1 What's the Packet Plane

The packet plane refers to the switching plane provided by the packet switching unit on a system control, switching, and timing board. The packet plane provides a wide range of services and features based on Native Ethernet, as well as a wide range of services and features based on MPLS/PWE3.
As shown in Figure 7-1, the ports connecting to the packet plane are classified into the following types: l FE/GE ports on an Ethernet interface board In the receive direction, the Ethernet switching unit on an Ethernet interface board adds port tags to the packets received from its internal FE/GE ports. Then, the packets are converged to the GE ports on the board, and then transmitted to the packet switching unit. The packet switching unit processes the packets of each port based on the port tags. In the transmit direction, the packet switching unit adds the port tags to the packets. Then, the packets are transmitted to the Ethernet switching unit through the internal GE ports on the board. The Ethernet switching unit transmits the packets to the ports based on the port tags. Therefore, the FE/GE ports on the Ethernet interface board can be regarded as being directly connected to the packet switching unit. l IF_ETH ports on a general IF board or general XPIC IF board IF_ETH ports are internal GE ports on a general IF board or general XPIC IF board. Ethernet packets are transmitted to the local IF board through its IF_ETH ports, and then mapped into Integrated IP radio frames. Ethernet packets demapped from Integrated IP radio frames are transmitted to the packet switching unit through IF_ETH ports. The main differences between an IF_ETH port and a GE/FE port are as follows: An IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and does not have PHY-layer functions. The bandwidth at an IF_ETH port is equal to the Ethernet service bandwidth that Integrated IP radio supports. Therefore, when the AM function is enabled in the case of Integrated IP radio, the bandwidth at an IF_ETH port changes according to the modulation scheme.
NOTE
Since an IF port corresponds to an IF_ETH port. the IF ports or the microwave ports corresponding to IF ports can be regarded as being directly connected to the packet plane.
Bridging port (PORT10) connecting to the packet plane on the EFP8 board The EFP8 board has two bridging ports: PORT9 and PORT10. PORT9 and PORT10 are two back-to-back internal GE ports, not having PHY-layer functions. PORT10 is connected to the packet plane. The Ethernet services on the packet plane are transmitted to the EoPDH plane through PORT10. PORT9 is connected to the EoPDH plane. The Ethernet services on the packet plane are transmitted to the FE port or VCTRUNK port on the EFP8 board through PORT9.
7-4
Issue 03 (2011-04-10)
Figure 7-1 Packet plane

Packet plane Ethernet interface board PORT1 Ethernet switching unit System control, switching, and timing board General IF board or general XPIC IF board IF unit GE
FE/GE
IF_ETH GE
IF
FE/GE
PORTn
FE/GE
Ethernet interface board PORT1 Ethernet switching unit
Packet switching unit GE GE
IF_ETH
General IF board or general XPIC IF board IF unit
IF
FE/GE
PORTn
PORT10 GE
PORT9
EFP8 Ethernet switching unit
GE EoPDH plane
7.1.2 Ethernet Port Numbers

On the NMS, Ethernet ports are represented by PORTs. l l For the EM6F, GE1 and GE2 correspond to PORT1 and PORT2 respectively; FE1 to FE4 correspond to PORT3 to PORT6 respectively. For the EM6T, GE1 and GE2 correspond to PORT1 and PORT2 respectively; FE1 to FE4 correspond to PORT3 to PORT6 respectively.
7.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network and to receive the corresponding information that the opposite end may transfer.
Auto-Negotiation Function of FE Electrical Ports

In the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10M full-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of the local FE electrical port does not match the working mode of the opposite FE electrical port, the two ports cannot communicate with each other. With the auto-negotiation function, however, the two ports can communicate with each other. The auto-negotiation function uses fast link pulses and normal link pulses to transfer the negotiation information of the working mode so that the working mode of the local FE electrical port matches the working mode of the opposite FE electrical port. Table 7-1 lists the FE auto-negotiation rules.
Issue 03 (2011-04-10)
7-5
Table 7-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts the auto-negotiation mode) Working Mode of the Opposite FE Electrical Port Auto-negotiation 10M half-duplex 10M full-duplex 100M half-duplex 100M full-duplex Auto-Negotiation Result 100M full-duplex 10M half-duplex 10M half-duplex 100M half-duplex 100M half-duplex
NOTE
As provided in Table 7-1, when the working mode of the opposite FE electrical port is 10M full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the FE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the opposite FE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the local FE electrical port to 10M full-duplex or 100M full-duplex.
When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at both ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Electrical Ports

In the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M fullduplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiation function of GE electrical ports is similar to the auto-negotiation function of FE electrical ports. Table 7-2 lists the auto-negotiation rules of GE electrical ports.
Table 7-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts the auto-negotiation mode) Working Mode of the Opposite GE Electrical Port Auto-negotiation (GE electrical port) Auto-negotiation (FE electrical port) 10M half-duplex 10M full-duplex 100M half-duplex 100M full-duplex 1000M full-duplex Auto-Negotiation Result 1000M full-duplex 100M full-duplex 10M half-duplex 10M half-duplex 100M half-duplex 100M half-duplex 1000M full-duplex
7-6
Issue 03 (2011-04-10)
NOTE
As provided in Table 7-2, when the working mode of the opposite GE electrical port is 10M full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of the GE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the opposite GE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the local GE electrical port to 10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both ends can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Optical Ports

GE optical ports support only the 1000M full-duplex working mode. The auto-negotiation function of GE optical ports is used only for negotiating the flow control function.
7.1.4 Flow Control Function

When the equipment fails to handle the flow received at the port due to poor data processing/ transferring capability, congestion occurs on the line. To reduce the number of discarded packets caused by buffer overflow, proper flow control measures must be taken. The half-duplex Ethernet port applies the back-pressure mechanism to control the flow. The fullduplex Ethernet port applies PAUSE frames to control the flow. Currently, the half-duplex Ethernet function is not widely applied. Hence, the flow control function realized by Ethernet service boards is used for the full-duplex Ethernet ports. The flow control function realized by Ethernet service boards is classified into two types: autonegotiation flow control and non-auto-negotiation flow control.
Auto-Negotiation Flow Control

When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiation flow control function. The auto-negotiation flow control modes include the following: l Asymmetric PAUSE toward the link partner The port can transmit PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l l Symmetric PAUSE The port can transmit PAUSE frames and process the received PAUSE frames. Both asymmetric and symmetric PAUSE The port has the following capabilities: Transmits and processes PAUSE frames. Transmits PAUSE frames but cannot process the received PAUSE frames. Processes the received PAUSE frames but cannot transmit PAUSE frames. l Disabled The port does not transmit or process PAUSE frames.
NOTE
On the NMS, the OptiX RTN 950 supports only two auto-negotiation flow control modes, namely, the Disabled mode and the Enable Symmetric Flow Control(symmetric PAUSE) mode.
Issue 03 (2011-04-10)
7-7
Non-Auto-Negotiation Flow Control

When the Ethernet port works in a fixed working mode, you can adopt the non-auto-negotiation flow control function. The non-auto-negotiation flow control modes include the following: l Send only The port can transmit PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l Receive only The port can process the received PAUSE frames but cannot transmit PAUSE frames in the case of congestion. l l Symmetric The port can transmit PAUSE frames and can also process received PAUSE frames. Disabled The port does not transmit or process PAUSE frames.
NOTE
On the NMS, the OptiX RTN 950 supports only two non-auto-negotiation flow control modes, namely, the Disabled mode and the Enable Symmetric Flow Control (symmetric) mode.
7.1.5 Native Ethernet Service Types Based on the Packet Plane

Based on the packet plane, Native Ethernet services are classified into six types. 7.1.5.1 Point-to-Point Transparently Transmitted E-Line Service The point-to-point transparently transmitted E-Line service are the basic E-Line model. Pointto-point transmission does not involve service bandwidth sharing, service isolation, or service distinguishing; instead, Ethernet services are transparently transmitted between two service access points. 7.1.5.2 VLAN-based E-Line Services VLANs can be used to separate several E-Line services so that these services share one physical channel for transmission. These E-Line services are called VLAN-based E-Line services. 7.1.5.3 QinQ-Based E-Line Services S-VLAN tags can be used to separate several E-Line services so that these services share one physical channel for transmission. These services are called QinQ-based E-Line services. 7.1.5.4 8021D Bridge-based E-LAN Services If packets of E-LAN services are forwarded only based on the MAC address table, these E-LAN services are called 802.1D bridge-based E-LAN services. 7.1.5.5 802.1Q Bridge-based E-LAN Services VLANs can be used to separate several E-LAN services, and then an 802.1Q bridge is divided into multiple independent sub-switching domains. These E-LAN services are called 802.1Q bridge-based E-LAN services. 7.1.5.6 802.1ad Bridge-based E-LAN Services S-VLAN tags can be used to separate several E-LAN services, and then a bridge is divided into multiple independent sub-switching domains. These services are called 802.1ad bridge-based E-LAN services.
7-8
Issue 03 (2011-04-10)
7.1.5.1 Point-to-Point Transparently Transmitted E-Line Service

The point-to-point transparently transmitted E-Line service are the basic E-Line model. Pointto-point transmission does not involve service bandwidth sharing, service isolation, or service distinguishing; instead, Ethernet services are transparently transmitted between two service access points.
Service Model
Table 7-3 describes the point-to-point transparently transmitted E-Line service model. Table 7-3 Point-to-point transparently transmitted E-Line service model Service Model Model 1 Traffic Flow PORT (source) PORT (sink) Service Direction UNI-UNI Encapsulation Type Null (source) Null (sink) Description The source port transparently transmits all the received Ethernet frames to the sink port. The source port processes the incoming Ethernet frames based on its TAG attribute, and then sends the processed Ethernet frames to the sink port. The sink port processes the Ethernet frames based on its TAG attribute, and then exports the processed Ethernet frames.
Model 2
NOTE In service model 2, ports process the received Ethernet frames according to their TAG attributes. Therefore, service model 2 is not a real transparent transmission model and is not recommended.
PORT (source) PORT (sink)
UNI-UNI
802.1Q (source) 802.1Q (sink)
Typical Application
Figure 7-2 shows the typical application of service model 1. Figure 7-2 Typical application of service model 1
NE 1 Port 1 Service 1 Service 2 Port 2 E-Line E-Line Port 4 Port 3 Transmission Network Port 3 NE 2 E-Line E-Line Port 4 Port 2 Port 1 Service 1 Service 2
Issue 03 (2011-04-10)
7-9
In service model 1, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and port 2 transparently transmit Ethernet service 1 and Ethernet service 2 to port 3 and port 4, respectively. Port 3 and port 4 then transmit Ethernet service 1 and Ethernet service 2 to NE2. Service processing on NE2 is the same as on NE1. In service model 2, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and Port 2 process the incoming packets based on their own TAG attributes. Then, Port 1 and Port 2 send Ethernet service 1 and Ethernet service 2 to Port 3 and Port 4 respectively. Port 3 and Port 4 process the incoming packets based on their own TAG attributes. Then, Port 3 and Port 4 send Ethernet service 1 and Ethernet service 2 to NE2. Service processing on NE2 is the same as on NE1.
7.1.5.2 VLAN-based E-Line Services

VLANs can be used to separate several E-Line services so that these services share one physical channel for transmission. These E-Line services are called VLAN-based E-Line services.
Service Model
Table 7-4 shows the VLAN-based E-Line service model. Table 7-4 VLAN-based E-Line service model Service Type Service Flow Service Direction Port Encapsulation Mode 802.1Q (source) 802.1Q (sink) Service Description The source port processes the incoming Ethernet frames based on its TAG attribute, and then sends the Ethernet frames with a specific VLAN ID to the sink port. The sink port processes the Ethernet frames based on its TAG attribute, and then exports the processed Ethernet frames.
VLAN-based ELine service
PORT+VLAN (source) PORT+VLAN (sink)

NOTE The VLAN ID of the source must be the same as that of the sink.
UNI-UNI
Typical Application
Figure 7-3 shows the typical application of the VLAN-based E-Line service model. Service 1 and service 2 carry different VLAN IDs. After the two Ethernet services are received at NE1 through port 1 and port 2 respectively, they share the same transmission channel at port 3.
On NE1, port 1 and port 2 process the incoming packets based on their own TAG attributes; then, port 1 and port 2 send service 1 and service 2 to port 3. Port 3 processes all the outgoing packets based on its TAG attribute, and then sends service 1 and service 2 to NE2. Due to the different VLAN IDs, service 1 and service 2 can be transmitted through port 3 at the same time. NE2 processes service 1 and service 2 in the same manner as NE1. Figure 7-3 VLAN-based E-Line service model
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1 NE 2 Port 3 Transmission Network Port 3 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
E-Line
E-Line
e E-Lin
Port 1
Service 1 VLAN ID: 100
Port 2
Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
E-Lin e
Service 2 Port 2 VLAN ID: 200
7.1.5.3 QinQ-Based E-Line Services

S-VLAN tags can be used to separate several E-Line services so that these services share one physical channel for transmission. These services are called QinQ-based E-Line services.
NOTE
10.1.1.3 E-Line Services Carried on PWs describes QinQ-based E-Line services carried by PWs.
Service Model
Table 7-5 shows the QinQ-based E-Line service models. Table 7-5 QinQ-based E-Line service models Service Model Service Flow Service Direction Port Encapsulation Mode Null (source) QinQ (sink) Service Description The source port adds the S-VLAN tag that corresponds to the QinQ link to all the received Ethernet frames, and then transmits the Ethernet frames to the sink port to which the QinQ link is connected.
Model 1
PORT (source) QinQ link (sink)
UNI-NNI
Issue 03 (2011-04-10)
7-11
Service Model
Service Flow
Service Direction
Port Encapsulation Mode 802.1Q (source)a QinQ (sink)
Service Description After the source port receives the Ethernet frames that carry C-VLAN tags, it adds the S-VLAN tag that corresponds to the QinQ link to all the Ethernet frames and then transmits the Ethernet frames to the sink port to which the QinQ link is connected. The source port adds the S-VLAN tag that corresponds to the QinQ link to all the Ethernet frames that carry specific CVLAN tags and then transmits the Ethernet frames to the sink port to which the QinQ link is connected. The source port transmits the Ethernet frames that carry a specific SVLAN tag (corresponding to the source QinQ link) to the sink port to which the sink QinQ link is connected. If the source and sink QinQ links have different S-VLAN tags, S-VLAN tag swapping occurs.
Model 2
PORT (source) QinQ link (sink)
UNI-NNI
Model 3
PORT+C-VLAN (source) QinQ link (sink)
UNI-NNI
802.1Q (source)a QinQ (sink)
Model 4
QinQ link (source) QinQ link (sink)
NNI-NNI
QinQ (source) QinQ (sink)
NOTE
a: Set Tag to Tag Aware.
7-12
Issue 03 (2011-04-10)
Typical Application
Figure 7-4 shows the typical application of service model 1. Service 1 and service 2 contain tagged frames and untagged frames. Service 1 is transmitted to NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted to Port 3. Port 3 transmits service 1 and service 2 to NE2. NE2 processes service 1 and service 2 in the same manner as NE1. Figure 7-4 Typical application of service model 1
NE 1 Port 1 Service 1 Service 2 Port 2
Strip S-VLAN Label Data( 1) Data(2)
NE 2 Port 3 Transmission Network Port 3

E-Line
E-Line
e E-Lin
Port 1 Service 1 Service 2 Port 2
E-Lin e
Add S-VLAN Label S-VLAN(300) S-VLAN(400) Data(1) Data(2)
Strip S-VLAN Label Data(1) Data(2)
Figure 7-5 shows the typical application of service model 2. Service 1 and service 2 carry different unknown C-VLAN tags. Service 1 is transmitted to NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted to port 3. Port 3 transmits service 1 and service 2 to NE2. NE2 processes service 1 and service 2 in the same manner as NE1. Figure 7-5 Typical application of service model 2
Strip S-VLAN Label C-VLAN C-VLAN Data( 1) Data(2) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN C-VLAN Data(1) Data(2)
NE 1 Service 1 Unknown CVLAN Service 2 Unknown CVLAN Port 1

E-Line
E-Line
e E-Lin
Port 1
Service 1 Unknown CVLAN Service 2 Unknown CVLAN
Port 2
E-Lin e
Port 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN C-VLAN Data(1) Data(2)
Strip S-VLAN Label C-VLAN C-VLAN Data( 1) Data(2)
Figure 7-6 shows the typical application of service model 3. Service 1 and service 2 carry different C-VLAN tags. Service 1 is transmitted to NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service
1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted to port 3. Port 3 transmits service 1 and service 2 to NE2. NE2 processes service 1 and service 2 in the same manner as NE1. Figure 7-6 Typical application of service model 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1

E-Line
E-Line
e E-Lin
Port 1
Port 2
E-Lin e

Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
Figure 7-7 shows the typical application of service model 4. Service 1 and service 2 carry the same S-VLAN tag. Service 1 is transmitted to NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 changes the S-VLAN tag carried in service 1 and port 2 changes the S-VLAN tag carried in service 2 so that the service 1 and service carry different S-VLAN tags. Port 3 transmits service 1 and service 2 to NE2. NE2 processes service 1 and service 2 in the same manner as NE1. Figure 7-7 Typical application of service model 4
Switching S-VLAN Label S-VLAN(100) S-VLAN(100) Data( 1) Data(2) S-VLAN(300) S-VLAN(400) Data(1) Data(2)
NE 1 Service 1 S-VLAN ID: 100 Service 2 S-VLAN ID: 100 Port 1

E-Line
E-Line
e E-Lin
Port 1
Service 1 S-VLAN ID: 100
Port 2
E-Lin e
Service 2 Port 2 S-VLAN ID: 100
7.1.5.4 8021D Bridge-based E-LAN Services

If packets of E-LAN services are forwarded only based on the MAC address table, these E-LAN services are called 802.1D bridge-based E-LAN services.
Service Model
Table 7-6 shows the 802.1D bridge-based E-LAN service model. Table 7-6 802.1D bridge-based E-LAN service model Service Type Tag Attribute Port Encapsulation Mode Null Logical Port Type PORT Learning Mode SVL SubSwitching Domain No division of sub-switching domains
802.1D bridgebased E-LAN service
TagTransparent
Typical Application
Figure 7-8 shows the typical application of the 802.1D bridge-based E-LAN service model. NE2 and NE3 receive A services, and the A services are transmitted over the transmission network. The two A services are converged at the convergence node NE1. The services do not need to be separated. Therefore, an 802.1D bridge is used at NE1 to groom services. Figure 7-8 802.1D bridge-based E-LAN service model
NE 2
Port 2 NE 1 Transmission Network Port 2 Port 3 802.1d bridge Transmission Network NE 3
Port 1 User A2
Port 1 User A1
Port 2
Port 1 User A3
7.1.5.5 802.1Q Bridge-based E-LAN Services

VLANs can be used to separate several E-LAN services, and then an 802.1Q bridge is divided into multiple independent sub-switching domains. These E-LAN services are called 802.1Q bridge-based E-LAN services.
Service Model
Table 7-7 shows the 802.1Q bridge-based E-LAN service model.
Table 7-7 802.1Q bridge-based E-LAN service model Service Type TAG Attribute C-Awared Port Encapsulation Mode 802.1Q Logical Port Type PORT+VLAN Learning Mode IVL SubSwitching Domain Sub-switching domains are divided based on VLANs.
802.1Q bridgebased E-LAN service
Typical Application
Figure 7-9 shows the typical application of the 802.1Q bridge-based E-LAN service model. Services G and H are received at NE2 and NE3, and then are transmitted over the transmission network. These services finally are converged and switched at NE1. As services G and H use different VLAN planning, 802.1Q bridges are configured on NEs and sub-switching domains are divided based on VLANs, differentiating and separating the two services. Figure 7-9 802.1Q bridge-based E-LAN service model
NE 2
VLAN 100
Port 1 User G2
NE 1 Port 1 User G1
VLAN 100
Port 3
VLAN 200
Transmission Network Port 3 802.1q bridge NE 3

VLAN 100
Port 2 User H2
Port 2 User H1
VLAN 200
Port 4 Transmission Network
802.1q bridge
VLAN 200
Port 1 User G3 Port 2 User H3
Port 3
802.1q bridge
NOTE
You can configure 7.1.5.2 VLAN-based E-Line Services on NE2 and NE3 for receiving services.
7.1.5.6 802.1ad Bridge-based E-LAN Services

S-VLAN tags can be used to separate several E-LAN services, and then a bridge is divided into multiple independent sub-switching domains. These services are called 802.1ad bridge-based E-LAN services.
Service Model
Table 7-8 shows the 802.1ad bridge-based E-LAN service models. Table 7-8 802.1ad bridge-based E-LAN service models Service Type Tag Attribute Port Encapsulation Mode Null or 802.1Q (UNI port)a QinQ (NNI port) Logical Port Type PORT (The encapsulation mode of the UNI port is Null.) PORT or PORT +C-VLAN (The encapsulation mode of the UNI port is 802.1Q.)
a
Learning Mode IVL
SubSwitching Domain Sub-switching domains are divided based on S-VLAN tags.
E-LAN services based on 802.1ad bridge
S-Awared
PORT+SVLAN (NNI port)
NOTE
a: When the encapsulation mode of port is 802.1Q, set Tag to Tag Aware.
Typical Application
Figure 7-10 shows the typical application of the 802.1ad bridge-based E-LAN service model. Services G and H are received at NE2 and NE3, and then are transmitted over the transmission network. These services finally are converged and switched at NE1. As services G and H use the same C-VLAN planning, extra S-VLAN tags are configured on NEs, differentiating and separating the two services.
Issue 03 (2011-04-10)
7-17
Figure 7-10 Typical application of the 802.1ad bridge-based E-LAN service model
NE 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H) Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
NE 2
SVLAN 300
Port 1 User G2 Port 3 NE 1

SVLAN 300 SVLAN 400 CVLAN 100
Transmission Network Port 3 802.1ad bridge
Port 2 User H2
CVLAN 100
Port 1 User G1
CVLAN 100 SVLAN 400
User H1
Port 2 Port 4 802.1ad bridge Transmission Network
NE 3
SVLAN 300
CVLAN 100
Port 1 User G3
CVLAN 100 SVLAN 400
NE 1
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
Port 3
Port 2 User H3
CVLAN 100
802.1ad bridge NE 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
NOTE
You can configure 7.1.5.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
7.1.6 Typical Mobile Carrier Network Topologies for Ethernet Services

Generally, Ethernet services are transmitted in three network topologies on a mobile carrier network. 7.1.6.1 Networking of VLAN-Based E-Line Services VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line services can share one physical channel. 7.1.6.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services In the case of IEEE 802.1d bridge-based E-LAN service networking, data is forwarded based on MAC addresses instead of VLAN IDs. 7.1.6.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services
In the case of IEEE 802.1q bridge-based E-LAN service networking, services are isolated by means of VLAN IDs. That is, the IEEE 802.1q bridge is divided into multiple sub-switching domains, which are isolated from each other. 7.1.6.4 Comparison Between the Three Networking Modes The three networking modes differ from each other.
7.1.6.1 Networking of VLAN-Based E-Line Services

VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line services can share one physical channel. On the mobile carrier network shown in Figure 7-11, the VLAN IDs that received BTS services carry are planned in a unified manner and are unique globally. The BTS services share the Ethernet service bandwidth on the Hybrid radio network (NE1 to NE5) and are isolated from each other by means of VLAN IDs. The BTS services are aggregated at NE1 and then transmitted through the regional backhaul network to the BSC. Therefore, in this example, services on the Hybrid radio network of the mobile carrier network are configured as VLAN-based E-Line services. Figure 7-11 Networking diagram of VLAN-based E-Line services
FE BTS VLAN 1 FE BTS VLAN 2 FE BTS VLAN 3 FE BTS VLAN 4 NE4 NE3 NE2 Hybrid microwave transmission network Regional Backhaul Network NE1
GE BSC
NE5
7.1.6.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services

In the case of IEEE 802.1d bridge-based E-LAN service networking, data is forwarded based on MAC addresses instead of VLAN IDs. As shown in Figure 7-12, the mobile carrier network need not sense whether the received BTS services carry any VLAN IDs. Services from each BTS are aggregated at NE1 and then transmitted through the regional backhaul network to the BSC. Therefore, in this example, the services on the Hybrid radio network (NE1 to NE6) of the mobile carrier network are configured as IEEE 802.1d bridge-based E-LAN services. The Hybrid radio network checks the destination ports in the MAC address table according to the destination MAC addresses carried by the BTS services and then forwards BTS services to the ports.
Issue 03 (2011-04-10)
7-19

NOTE
IEEE 802.1d bridge-based E-LAN service packets are forwarded based on MAC addresses and may be broadcast among all ports connected to the IEEE 802.1d bridge. Therefore, isolate the ports that need not communicate with each other by adding the ports into a split horizon group.
Figure 7-12 Networking diagram of IEEE 802.1d bridge-based E-LAN services

FE BTS FE BTS NE3 NE2 Hybrid microwave transmission network Regional backhaul network NE1 FE BTS FE BTS NE6 NE5 NE4
GE BSC
Split horizon group
7.1.6.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services

In the case of IEEE 802.1q bridge-based E-LAN service networking, services are isolated by means of VLAN IDs. That is, the IEEE 802.1q bridge is divided into multiple sub-switching domains, which are isolated from each other. On the mobile carrier network shown in Figure 7-13, the VLAN IDs that received BTS services carry are planned in a unified manner and are unique within each domain. BTS services in different domains are isolated from each other by means of VLAN IDs and BTSs in the same domain can communicate with each other. The BTS services are aggregated at NE1 and then transmitted through the regional backhaul network to the BSC. Therefore, in this example, the services on the Hybrid radio network of the mobile carrier network are configured as IEEE 802.1q bridge-based E-LAN services. The Hybrid radio network checks the destination ports in the MAC address table according to the destination MAC addresses and VLAN IDs carried by the BTS services and then forwards BTS services to the ports.
NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the ports that need not communicate with each other by adding the ports into a split horizon group.
7-20
Issue 03 (2011-04-10)
Figure 7-13 Networking diagram of IEEE 802.1q bridge-based E-LAN services
FE BTS VLAN 1 FE BTS VLAN 1 Hybrid radio network FE BTS VLAN 2 FE BTS VLAN 2 NE6 NE5 NE4 NE2 Domain 1 VLAN 1 Domain 2 VLAN 2 NE1 Regional backhaul network NE3
GE BSC
Split horizon group
7.1.6.4 Comparison Between the Three Networking Modes

The three networking modes differ from each other. Table 7-9 compares the three networking modes.
Issue 03 (2011-04-10)
7-21
Table 7-9 Comparison between the three networking modes Networkin g Mode Application Scenario Applicable Network Size This networking mode is applicable to all network sizes. Applicable VLAN ID Allocation l The VLAN IDs that received BTS services carry are planned in a unified manner and are unique globally. l BTS services share Ethernet service bandwidt hs and are isolated by means of VLAN IDs. Service Stability Service Security Configurati on Complexity Network Scalability
Networking of VLANbased E-Line services
High
l Very high l Services from different BTSs are isolated from each other.
l The configurat ion operations are complex. l Only point-topoint configurat ion is supported .
l The network is difficult to expand. l To add the new VLAN ID after a BTS is added, you need to change the E-Line configurat ions on all the NEs that the new service path traverses.
7-22
Issue 03 (2011-04-10)
Networkin g Mode
Application Scenario Applicable Network Size It is recommende d that the network contains less than 50 BTSs. Applicable VLAN ID Allocation l The network need not sense whether the received BTS services carry any VLAN IDs. l Services need not be isolated between different ports connected to the same bridge.a
Service Stability
Service Security
Configurati on Complexity
Network Scalability
Networking of IEEE 802.1d bridge-based E-LAN services
Medium
l Low l The service packets can be broadcast on the entire network.
l The configurat ion operations are simple. l Point-tomultipoint configurat ion is supported .
l The network is easy to expand. l After a BTS is added, you need not change the configurat ions of other NEs on the network. Instead, you only need to change the mounted ports on the NE connected to the base station.
Issue 03 (2011-04-10)
7-23
Networkin g Mode
Application Scenario Applicable Network Size This networking mode is applicable to all network sizes, especially to a network that is divided into several domains. Applicable VLAN ID Allocation l The VLAN IDs that received BTS services carry are planned in a unified manner and are unique within each domain. l The BTS services from different domains are isolated from each other by means of VLAN IDs. l BTS services within a domain need not be isolated from each other.a
Service Stability
Service Security
Configurati on Complexity
Network Scalability
Networking of IEEE 802.1q bridge-based E-LAN services
Medium
l High l The service packets are broadcast within each domain and are isolated between different domains.
l The configurat ion operations are simple. l Point-tomultipoint configurat ion is supported .
l The network is easy to expand. l After a BTS is added in a domain, you need not change the configurat ions of the other NEs in the domain or the configurat ions of NEs in the other domains. Instead, you only need to change the mounted ports and VLAN IDs on the NE connected to the base station.
NOTE
a: To block communication between certain ports connected to a bridge, you need to add the ports into a split horizon group.
7.1.7 MAC Address Table Management

The entries in a MAC address table indicate the mappings between MAC addresses and ports. A MAC address table contains dynamic entries, static entries, and blacklist entries.
Dynamic entry A dynamic entry is obtained by learning of a bridge through the SVL/IVL mode. The dynamic entry will be aged.
Static entry A static entry is manually added by a network administrator to the MAC address table by using the NMS. The static entry will not be aged. Generally, the static entry is configured when a port corresponds to a device with its MAC address known and this device transmits large traffic for a long time.
Blacklist entry A blacklist entry, that is, the MAC disabled entry, is used to discard the data frame that contains the specified MAC address (source MAC address or destination MAC address). A blacklist entry is also called a blackhole entry. The blacklist entry is configured by the network administrator. The blacklist entry does not age, and is not lost after the Ethernet processing board is reset.
NOTE
If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time.
7.1.8 VLAN Forwarding Table

Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If changing VLAN IDs is required, configure a VLAN forwarding table. For VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are usually set to the same value. If packets carry different VLAN IDs on the source and sink nodes, these VLAN IDs need to be set for the source and sink nodes of the E-Line services. In addition, you need to configure a VLAN forwarding table to achieve the switch of VLAN IDs at the source and sink nodes. Figure 7-14 shows an application of the VLAN forwarding table. In this figure, service 1 carries a VLAN ID of 100, and it is transmitted to NE1 through port 1. On a transmission network, the VLAN ID of service 1 may be in conflict with the VLAN IDs of other services. To avoid this situation, the VLAN ID of service 1 must be changed to another value before it is transmitted on the transmission network and then be changed to the original value after it is transmitted out of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and NE2, so that the VLAN IDs of services between port 1 and port 3 can be changed as required. For service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and then changes back to 100 again at NE2.
Issue 03 (2011-04-10)
7-25
Figure 7-14 Application of the VLAN forwarding table in E-Line services

NE 1 Service 1 VLAN ID: 100 Port 1 Transmission Network NE 2 Port 1 Port 3 Port 3 Service 1 VLAN ID: 100
E-Lin e
e E-Lin
Service 1 VLAN ID: 200 VLAN Forwarding Table Source Interface Port 1 Port 3 Source VLAN ID 100 200 Sink Sink Interface VLAN ID 200 Port 3 Port 1 100
VLAN Forwarding Table Source Interface Port 1 Port 3 Source VLAN ID 100 200 Sink Sink Interface VLAN ID 200 Port 3 Port 1 100
E-Line Service Information Table Source Interface Port 1 Source VLAN ID 100, 200 Sink Sink Interface VLAN ID Port 3 100, 200 Source Interface Port 1
E-Line Service Information Table Source VLAN ID 100, 200 Sink Sink Interface VLAN ID Port 3 100, 200
7.1.9 Split Horizon Group

To separate services that are converged and to prevent broadcast storm resulting from a service loop, you can configure a split horizon group for the E-LAN services at the specified nodes. After the configuration, the logical ports in one split horizon group cannot forward packets to each other. Figure 7-15 shows a typical application of the split horizon group. NEs on the network are configured with E-LAN services, and the east and west 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, broadcast storm occurs due to a network loop as the east and west ports can forward packets to each other. If a split horizon group is created at NE1 and the east and west ports are configured as members of the split horizon group, the east and west ports do not forward packets to each other. Therefore, a service loop is prevented. Figure 7-15 Split horizon group
NE1 BSC Split horizon group
BTS NE2 BTS NE4 BTS
NE3 BTS
7-26
Issue 03 (2011-04-10)
NOTE
l ERPS can prevent a service loop on a ring network. Therefore, if ERPS is already enabled for a ring network, a split horizon group is not needed as it may affect normal operation of ERPS. l On the OptiX RTN 950, only the configuration of a split horizon group based on physical ports is supported. Therefore, if a physical port is mapped into several logical ports and one of these logical ports is a member of a split horizon group, the other logical ports are added to the split horizon group automatically.
7.1.10 Protection for Native Ethernet Services Based on the Packet Plane
The OptiX RTN 950 supports three protection modes for Native Ethernet services, namely, Ethernet ring protection switching (ERPS), link aggregation group (LAG), and multiple spanning tree protocol (MSTP).
ERPS
ERPS is applicable to ring physical networks and can provide protection for the E-LAN services between all the nodes on the ring network. Generally, when a ring network is configured with ERPS, the RPL node blocks the RPL port on one side so that all the services are transmitted through the ports on the other side. In this manner, service loops are prevented. If a section of link fails or an NE becomes faulty, the RPL node unblocks its RPL port so that the services are switched from the faulty point to the RPL port for transmission. In this manner, protection for the ring network is realized. The Ethernet ring network shown in Figure 7-16 is configured with ERPS. Generally, the RPL node (NE D) blocks its RPL port that is connected to NE A, and all the services are transmitted over the link NE A <-> NE B <-> NE C <-> NE D. When the link between NE A <-> NE B becomes faulty, NE D unblocks the blocked port so that the services can be transmitted over the link NE A <-> NE D <-> NE C <-> NE B.
Issue 03 (2011-04-10)
7-27
Figure 7-16 Implementation of ERPS
NE A
NE B
NE D
NE C
Protection switching
Failure
NE A
NE B
NE D
NE C Link Ethernet service direction Blocked port
LAG
Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link. As shown in Figure 7-17, the LAG provides the following functions: l
7-28
Increases the link capacity.

The LAG provides the telecom operators with a cost-effective method of increasing the link bandwidth. The operators obtain data links with higher bandwidths by combining multiple physical links into one logical link without upgrading the existing equipment. The bandwidth of the logical link is equal to the sum of the bandwidths of the physical links. The aggregation module distributes the traffic to different members by using the load sharing algorithm, thus realizing the load sharing function at the link level. l Improves the link availability. The links in a LAG provide backup to each other dynamically. When a link fails, another link in the LAG quickly takes over. The process in which link aggregation starts the backup link is related only to the links in the same LAG and is not related to the links that are not in the LAG. Figure 7-17 LAG
Link 1 Link 2 Ethernet packet Link 3 Link aggregation group Ethernet packet
MSTP
The OptiX RTN 950 supports only the MSTP protocol that uses the common and internal spanning tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree protocol (RSTP). The RSTP is applicable in the case of a network loop. This protocol adopts certain algorithms to reconstruct a loop network into a loop-free tree network and thus prevents Ethernet frames from increasing and cycling in an endless manner on the loop network. In the case of the OptiX RTN 950, the MSTP is used to prevent a network loop on the access side. See Figure 7-18. When the user equipment accesses the OptiX RTN 950 through two different trails, you can configure the ports on the OptiX RTN 950 that are connected to the user network into a port group. This port group, together with the switch on the user network, can run the MSTP. Hence, if a service access link becomes faulty, the MSTP enables a re-configuration to generate the spanning tree topology, thus providing protection for the user network that is configured with multiple access points.
Issue 03 (2011-04-10)
7-29
Figure 7-18 Prevention of network loops on the access side

Root Root
Port group CIST Blocked Port

The service configuration procedure differs according to the specific service type. 7.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services) This section describes how to perform parameter settings and other relevant operations as required in the procedures for configuring point-to-point transparently transmitted E-Line services. 7.2.2 Configuration Procedure (VLAN-Based E-Line Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an VLAN-based E-Line service and the procedure for verifying the service configurations. 7.2.3 Configuration Procedure (QinQ-Based E-Line Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of a QinQ-based E-Line service and the procedure for verifying the service configurations. 7.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service and the procedure for verifying the service configurations. 7.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations. 7.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service and the procedure for verifying the service configurations.
7.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedures for configuring point-to-point transparently transmitted E-Line services.
Configuration Flow Chart

Figure 7-19 provides the procedures for configuring point-to-point transparently transmitted ELine services. Figure 7-19 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Required Optional Configuring LAGs Start
Configuring E-Line services
Configuring Ethernet ports
Configuring IF_ETH ports
Configuring QoS
Verifying Ethernet service configurations
End
Issue 03 (2011-04-10)
7-31
Procedures for Configuring a LAG

Table 7-10 Procedures for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if LAG protection is configured for FE/GE ports or for the Integrated IP radio that works in N+0/XPIC mode. Set the parameters as follows: l Set LAG Type to the same value as the opposite equipment. Generally, set LAG Type to Static for the equipment at both ends. l The Hybrid/AM attributes must be set to the same value for the IF ports in a LAG. l In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to provide protection, it is recommended that you set Load Sharing to NonSharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the Integrated IP radio works in N+0/XPIC mode and uses LAG protection, set Load Sharing to Sharing for the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive for the equipment at both ends. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l It is recommended that you set this parameter to the same value for the main and slave ports of the LAGs at both ends. In this case, you can set System Priority according to the actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l For air interface LAG, to enable microwave signal degrade to trigger LAG switching, set Switch LAG upon Air Interface SD to Enabled. l Set Main Board, Main Port, and Selected Standby Ports according to the planning information. It is recommended that you set this parameter to the same value for the main and slave ports of the LAGs at both ends.
NOTE The members of a 1+1 XPIC workgroup cannot be used to construct any LAG.
7-32
Issue 03 (2011-04-10)
Operation A.6.2.2 Setting Parameters for LAGs
Description Required in these following scenarios: l Required if Load Sharing is Sharing. Set System Load Sharing Hash Algorithm to the same value as the opposite equipment. Unless otherwise specified, this parameter adopts the default value. This parameter is valid to the sharing LAG only. l Required if Load Sharing is Non-Sharing, and the non-sharing LAG has multiple slave ports and the sequence in which the slave pots take over the main port needs to be specified. Set Port Priority to a smaller value for the slave port that first takes over the main port in the case of protection. Set Port Priority to larger values for the other slave ports. The highest value indicates the last slave port to take over the main port.
Procedures for Configuring Point-to-Point Transparently Transmitted E-Line Services

Table 7-11 Procedures for configuring point-to-point transparently transmitted E-Line services Operation A.6.3.2 Configuring UNI-UNI ELine Services Description Required. Set the parameters as follows: l Set Direction to UNI-UNI. l Set Source Interface and Sink Interface according to the planning information. l Source VLAN ID and Sink VLAN ID remain null. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is autonegotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l Set Port Mode to Layer 2 and set Encapsulation Type to Null. A.6.3.6 Creating a VLAN Forwarding Table Item Required when the VLAN tags of the Ethernet service need to be swapped at the source and sink. Set the parameters according to the network planning information.
NOTE The corresponding VLAN forwarding table entries need to be configured for the source port and sink port.
Issue 03 (2011-04-10)
7-33
Procedures for Configuring Ethernet Ports

Table 7-12 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable Symmetric Flow Control. l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to Enable Symmetric Flow Control. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port Optional.
A.5.6.2 Configuring the Traffic Control of Ethernet Ports
Optional.
Optional.
NOTE l For the ISU2/ISX2, it is recommended that you set Speed Air Interface Transmission at L2 and Speed Air Interface Transmission at L3 to Enabled, if the corresponding permission to enable the two functions is already obtained. l When Speed Air Interface Transmission at L3 is set to Enabled, Encapsulation Type of the ISU2 and ISX2 boards cannot be set to Null. l Set Speed Air Interface Transmission at L2 and Speed Air Interface Transmission at L3 consistently for both ends of a radio link.
7-34
Issue 03 (2011-04-10)
Procedures for Configuring QoS

Table 7-13 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required when the new port policy is created. Set the parameters according to the network planning information.
Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
7-35
Procedures for Verifying Ethernet Service Configurations

Table 7-14 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.6.8.2 Creating an MA Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s. A.6.8.3 Creating an MEP Point Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Board and Port to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
7-36
Issue 03 (2011-04-10)
Operation A.6.8.4 Creating Remote MEPs in an MA
Description Required in the case of the NE where the Ethernet ports involved in the OAM operation are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
Perform an LB test to test the Ethernet service configurations
Required. The LB test result should show that no packet loss occurs.
7.2.2 Configuration Procedure (VLAN-Based E-Line Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an VLAN-based E-Line service and the procedure for verifying the service configurations.

Figure 7-20 provides the procedures for configuring VLAN-based E-Line services.
Issue 03 (2011-04-10)
7-37
Figure 7-20 Configuration flow chart (VLAN-based E-Line services)

Required Optional Configuring LAGs Start
Configuring Ethernet ports
Configuring QoS
End
7-38
Issue 03 (2011-04-10)

Issue 03 (2011-04-10)
7-39
Procedures for Configuring VLAN-Based E-Line Services

Table 7-16 Procedures for configuring VLAN-based E-Line services Operation A.6.3.2 Configuring UNI-UNI ELine Services Description Required. Set the parameters as follows: l Set Direction to UNI-UNI. l Set Source Interface and Sink Interface according to the network planning information. l Set Source VLAN ID and Sink VLAN ID according to the network planning information. The two parameters should be set to the same value. l Set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. A.6.3.6 Creating a VLAN Forwarding Table Item Required when the VLAN tags of the Ethernet service need to be switched at the source and sink. The parameters need to be set according to the network planning information.
NOTE The corresponding VLAN forwarding table items need to be configured for the source port and sink port.
7-40
Issue 03 (2011-04-10)

Table 7-17 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable Symmetric Flow Control. l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to Enable Symmetric Flow Control. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port Optional.
Optional.
Issue 03 (2011-04-10)
7-41
Operation A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port
Description Optional.

Table 7-18 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information.
7-42
Issue 03 (2011-04-10)
Operation A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when the new port policy is created. Set the parameters according to the network planning information.

Table 7-19 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.6.8.2 Creating an MA Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s.
Issue 03 (2011-04-10)
7-43
Operation A.6.8.3 Creating an MEP Point
Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Board and Port to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
A.6.8.4 Creating Remote MEPs in an MA
Required in the case of the NE where the Ethernet ports involved in the OAM operation are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
7.2.3 Configuration Procedure (QinQ-Based E-Line Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of a QinQ-based E-Line service and the procedure for verifying the service configurations.

Figure 7-21 provides the procedures for configuring QinQ-based E-Line services.
7-44
Issue 03 (2011-04-10)
Figure 7-21 Configuration flow chart (QinQ-based E-Line services)

Required Optional Configuring Ethernet ports Start
Configuring LAGs
Configuring QoS
End
Issue 03 (2011-04-10)
7-45

Table 7-20 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports Description A.5.6.1 Setting the General Attributes of Ethernet Ports Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l If a UNI can access untagged frames, set Port Mode to Layer 2 and set Encapsulation Type to Null. If a UNI can access tagged frames only, set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of an NNI, set Port Mode to Layer 2 and set Encapsulation Type to QinQ. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length (byte) to 1536.
7-46
Issue 03 (2011-04-10)
Operation
Description A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: l When the external equipment uses the nonauto-negotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable Symmetric Flow Control. l When the external equipment uses the autonegotiation flow control function, set AutoNegotiation Flow Control Mode to Enable Symmetric Flow Control. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the S-VLAN that is supported by the external equipment. In the case of NNIs within the network, QinQ Type Domain takes the default value. Optional.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port
Required. Set Port Mode to Layer 2 and set Encapsulation Type to QinQ.
Issue 03 (2011-04-10)
7-47
Operation
Description A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port Optional. In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the S-VLAN that is supported by the external equipment. In the case of NNIs within the network, QinQ Type Domain takes the default value. Optional.
A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port
7-48
Issue 03 (2011-04-10)

Issue 03 (2011-04-10)
7-49
Procedures for Configuring QinQ-Based E-Line Services

Table 7-22 Procedures for configuring QinQ-based E-Line services Operation A.6.3.1 Configuring the QinQ Link A.6.3.4 Configuring UNI-NNI ELine Services (Carried by QinQ Links) Description Required. Set the parameters according to the network planning information. Required. Set the parameters according to the network planning information.

Table 7-23 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port.
7-50
Issue 03 (2011-04-10)
Operation A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.

Table 7-24 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.
Issue 03 (2011-04-10)
7-51
Operation A.6.8.2 Creating an MA
Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s.
A.6.8.3 Creating an MEP Point
Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Board and Port to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
7.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service and the procedure for verifying the service configurations.
7-52
Issue 03 (2011-04-10)

Figure 7-22 provides the procedures for configuring IEEE 802.1d-bridge-based E-LAN services. Figure 7-22 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)
Configuring LAGs
Configuring ERPS protection
Configuring E-LAN services
Configuring QoS
End
Issue 03 (2011-04-10)
7-53

Table 7-25 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Port Mode to Layer 2 and set Encapsulation Type to Null. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the actual requirements. Required. Set Port Mode to Layer 2 and set Encapsulation Type to Null.
Setting the parameters of IF_ETH ports
A.5.7.1 Setting the General Attributes of the IF_ETH Port
7-54
Issue 03 (2011-04-10)
Operation A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port
Description Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.
Issue 03 (2011-04-10)
7-55

7-56
Issue 03 (2011-04-10)
Procedures for Configuring ERPS Protection

Table 7-27 Procedures for configuring ERPS protection Operation A.6.1.1 Creating Ethernet Ring Protection Instances A.6.1.2 Setting the Parameters of Ethernet Ring Protocol Description Required when an Ethernet ring needs to be protected and service loops need to be avoided on the Ethernet ring.
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and Packet Transmit Interval(s) according to the actual requirements. Set these parameters to the same values for all the NEs on the network.
Issue 03 (2011-04-10)
7-57
Procedures for Configuring IEEE 802.1d-Bridge-Based E-LAN Services

Table 7-28 Procedures for configuring IEEE 802.1d-bridge-based E-LAN services Operation A.6.3.8 Configuring IEEE 802.1d Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to Tag-Transparent. l Set Self-Learning MAC Address to Enabled according to the planning information. l In Get UNI Port, set Port according to the planning information and set and VLAN (e.g. 1,3-5) to null. l Set Port Mode to Layer 2 and set Encapsulation Type to Null. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if the aging function needs to be disabled or if the default aging time (five minutes) needs to be changed. Set the parameters according to the network planning information.
Optional.
7-58
Issue 03 (2011-04-10)

Table 7-29 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
7-59

7-60
Issue 03 (2011-04-10)
7.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations.

Figure 7-23 provides the procedures for configuring IEEE 802.1q bridge-based E-LAN services.
Issue 03 (2011-04-10)
7-61
Figure 7-23 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
The detailed information about the procedures in the flow chart is provided as follows.
7-62
Issue 03 (2011-04-10)

Table 7-31 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements. Required. Set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q.
Issue 03 (2011-04-10)
7-63
Operation A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Description Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set Tag to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set Tag to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set Tag to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information. A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.

7-64
Issue 03 (2011-04-10)

Issue 03 (2011-04-10)
7-65
Procedures for Configuring IEEE 802.1q Bridge-Based E-LAN Services

Table 7-34 Procedures for configuring IEEE 802.1q bridge-based E-LAN services Operation A.6.3.9 Configuring IEEE 802.1q Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to C-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In Get UNI Port, set Port and VLAN (e.g. 1,3-5) according to the planning information. l Set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
7-66
Issue 03 (2011-04-10)
Operation A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
Description Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if the aging function needs to be disabled or if the default aging time (five minutes) needs to be changed. Set the parameters according to the network planning information.
Optional.

Table 7-35 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
7-67
Operation A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required when the new port policy is created. Set the parameters according to the network planning information.

7-68
Issue 03 (2011-04-10)
7.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service and the procedure for verifying the service configurations.

Figure 7-24 provides the procedures for configuring IEEE 802.1ad bridge-based E-LAN services.
Issue 03 (2011-04-10)
7-69
Figure 7-24 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
The detailed information about the procedures in the flow chart is provided as follows.
7-70
Issue 03 (2011-04-10)

Table 7-37 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l If a UNI can access untagged frames, set Port Mode to Layer 2, and set Encapsulation Type to Null. If a UNI can access tagged frames only, set Encapsulation Type to 802.1Q. l In the case of an NNI, set Port Mode to Layer 2, and set Encapsulation Type to QinQ. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set TAG to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. In the case of an NNI within the network, QinQ Type Domain takes the default value. Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements. Required. l If a UNI can access untagged frames, set Port Mode to Layer 2, and set Encapsulation Type to Null. If a UNI can access tagged frames only, set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of an NNI, set Port Mode to Layer 2 and set Encapsulation Type to QinQ.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port
Issue 03 (2011-04-10)
7-71
Operation A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Description Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set Tag to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. In the case of an NNI within the network, QinQ Type Domain takes the default value. Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.

7-72
Issue 03 (2011-04-10)

Issue 03 (2011-04-10)
7-73
Procedures for Configuring IEEE 802.1ad Bridge-Based E-LAN Services

Table 7-40 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services Operation A.6.3.10 Configuring IEEE 802.1ad Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to S-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In Get UNI Port and Get NNI Port, set the parameters according to the planning information. l If a UNI can access untagged frames, set Port Mode to Layer 2, and set Encapsulation Type to Null. If a UNI can access tagged frames only, set Port Mode to Layer 2 and set Encapsulation Type to 802.1Q. l In the case of an NNI, set Port Mode to Layer 2 and set Encapsulation Type to QinQ. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member.
7-74
Issue 03 (2011-04-10)
Operation Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
Description Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if the aging function needs to be disabled or if the default aging time (five minutes) needs to be changed. Set the parameters according to the network planning information.
Optional.

Table 7-41 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain
Issue 03 (2011-04-10)
Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information.
7-75
Operation A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required when the new port policy is created. Set the parameters according to the network planning information.

7-76
Issue 03 (2011-04-10)
7.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)

This section considers a point-to-point transparently transmitted E-Line service as an example to describe how to configure the Ethernet service according to the network planning information. 7.3.1 Networking Diagram This section describes the networking information about the NEs. 7.3.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service. 7.3.3 Configuration Process This section describes the process for data configuration.
Issue 03 (2011-04-10)
7-77

This section describes the networking information about the NEs. As shown in Figure 7-25, NE1 is a terminal station of a backhaul network. The service requirements are as follows: l l NE1 transparently transmits the Ethernet services from the BTS to NE2 in point-to-point manner. DSCP flags are used to identify the priorities of the Ethernet services from the BTS.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are configured; in addition, corresponding QoS processing is configured. Figure 7-25 Networking diagram (point-to-point transparently transmitted E-Line services)
Tranparent transmitted E-Line service
Backhaul network
NE1 BTS
NE2
BSC
The connections of Ethernet links shown in Figure 7-25 are described as follows. Table 7-43 Connections of Ethernet links (NE1) Link Between NE1 and the BTS Between NE1 and NE2 Port 1-EM6T-3 3-IFU2-1 Description Configure this port to access services from the BTS. Configure this port to transmit backhaul services from a BTS. The Hybrid radio link between NE1 and NE2 adopts the 1+0 nonprotection configuration. In addition, the AM function is enabled for the Hybrid radio link.

You need to plan the corresponding parameter information before configuring an Ethernet service.
7.3.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.3.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.3.2.3 Service Planning (Ethernet Services) The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.3.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.
7.3.2.1 Service Planning (Ethernet Ports)

The service planning information contains the information about all the parameters required for configuring Ethernet ports.
Ethernet Port
Table 7-44 provides the information about the Ethernet port involved in the service. Table 7-44 Ethernet port Parameter Encapsulation Type Working Mode Maximum Frame Length (byte) Flow Control 1-EM6T-3 Null Auto-Negotiation 1536 Disabled
NOTE
l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the GE port that accesses the BTS must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its default value of 1522. l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends.
Information About the IF_ETH Ports

Table 7-45 provides the information about the IF_ETH ports that carry services.
Table 7-45 Ethernet port Parameter Encapsulation Type 3-IFU2-1 Null
7.3.2.2 Service Planning (Ethernet Protection)

The service planning information contains the information about all the parameters required for configuring Ethernet protection. In this example, Ethernet protection is not used.
7.3.2.3 Service Planning (Ethernet Services)

The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-46 provides the detailed service planning information. Table 7-46 Point-to-point transparently transmitted E-line service Parameter Service ID Service Name Direction BPDU Source Port Source C-VLANs Sink Port Sink C-VLANs NE1 1 BTStoNE2_Tline UNI-UNI Not Transparently Transmitted 1-EM6T-3 Blank 3-IFU2-1 Blank
7.3.2.4 Service Planning (QoS)

The service planning information contains the information about all the parameters required for configuring QoS.
QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated according to the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding DSCP values according to the service type, and the NEs allocate the PHB service classes according to the DSCP value, as shown in Table 7-47. Each Ethernet port involved in the service uses the same DS configuration. Table 7-47 Service class and PHB service class PHB Service Class CS7 CS6 EF DSCP 56 48 40 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF4 AF3
32 24
AF2
16
AF1 BE
8 0
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 7-48 lists the queue scheduling mode used by each Ethernet port involved in the service in this example.
Issue 03 (2011-04-10)
7-81
Table 7-48 Queue scheduling mode PHB Service Class CS7 CS6 EF AF4 AF3 AF2 AF1 BE Queue Scheduling Mode SP SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP
QoS (CAR or Shaping for a Specified Service Flow)

Normally, flow control is already performed on 2G/3G base stations and BSCs/RNCs and therefore CAR or shaping processing does not need to be performed again on the microwave backhaul network.
QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the aggregation services, you can perform port shaping at the edge node to limit the Ethernet service traffic that travels to the aggregation node, thus preventing congestion at the aggregation node. In this example, you do not need to perform port shaping.

This section describes the process for data configuration. 7.3.3.1 Configuration Process (Ethernet Protection) In this example, Ethernet protection is not used. 7.3.3.2 Configuration Process (Service Information) This section describes the process for configuring service information. 7.3.3.3 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.3.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.3.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.
7-82
Issue 03 (2011-04-10)
7.3.3.1 Configuration Process (Ethernet Protection)

In this example, Ethernet protection is not used.
7.3.3.2 Configuration Process (Service Information)

This section describes the process for configuring service information.
Procedure
Step 1 See A.6.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services. The values for the relevant parameters are provided as follows. Parameter Service ID Service Name Direction Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Port Mode Working Mode Encapsulation Type Value 1 BTStoNE2_Tline UNI-UNI 1-EM6T-3 Blank 3-IFU2-1 Blank 1-EM6T-3 Enabled Layer 2 Auto-Negotiation Null 3-IFU2-1 Layer 2 Null
----End
7.3.3.3 Configuration Process (Ethernet Ports)

This section describes the process for configuring Ethernet ports.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes of the Ethernet port. The values for the relevant parameters are provided as follows. Parameter Value 1-EM6T-3 Max Frame Length(byte)
Issue 03 (2011-04-10)
1536
7-83
----End
7.3.3.4 Configuration Process (QoS)

This section describes the procedures for configuring QoS.
Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and change the mapping relationships for the DS domain. The values for the relevant parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
The values for the relevant parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN Default value SVLAN Default value IP DSCP Default value MPLS EXP Default value PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
The values for the relevant parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11
CVLAN Default value
SVLAN Default value
IP DSCP Default value
MPLS EXP Default value
PHB AF21 AF31 AF41 EF CS6 CS7
CVLAN
SVLAN
IP DSCP
MPLS EXP
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified.
Step 2 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet types. Port 1-EM6T-3 3-IFU2-1 Packet Type ip-dscp
NOTE
The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Step 3 See A.6.7.4 Creating a Port Policy to create the port policy. The values for the related parameters are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4-AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Parameter Bandwidth Limit
Value Disabled (for all PHB service classes)
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the related parameters are provided as follows. Parameter Value Port_Comm Port 1-EM6T-3 3-IFU2-1
----End
7.3.3.5 Configuration Process (Verifying Ethernet Service Configurations)

This section describes the process for verifying Ethernet service configurations.
Procedure
Step 1 See A.6.8.1 Creating an MD and create an MD. The values for the related parameters are provided as follows. Parameter Value NE1 Maintenance Domain Name Maintenance Domain Level InterNE 3
Step 2 See A.6.8.2 Creating an MA and create an MA. The values for the related parameters are provided as follows. Parameter Value NE1 Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period InterNE BTS_Tline 1-BTStoNE2_Tline 1s
7-86
Issue 03 (2011-04-10)
Step 3 See A.6.8.3 Creating an MEP Point and create MEP points. The values for the related parameters are provided as follows. Parameter Value NE1 Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status InterNE BTS_Tline 1-EM6T 1-EM6T-3 101 Ingress Active Active InterNE BTS_Tline 3-IFU2 3-IFU2-1 102 Ingress Active Active
Step 4 A.6.8.4 Creating Remote MEPs in an MA. Parameter Value NE1 Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) InterNE BTS_Tline 102
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line service. Use MEP ID 101 as the source maintenance point and MEP ID 102 as the sink maintenance point to perform the LB test. No packet loss occurs. ----End
7.4 Configuration Example (VLAN-Based E-Line Service)

This section considers a VLAN-based E-line service as an example to describe how to configure the Ethernet service according to the network planning information. 7.4.1 Networking Diagram The section describes the networking information about the NEs.
7.4.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service. 7.4.3 Configuration Process This section describes the process for data configuration.

The section describes the networking information about the NEs. Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure Ethernet services according to the following requirements: l l l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s. Services transmitted by each BTS carry VLAN IDs, and VLAN IDs on the entire network are planned in a unified manner. VLAN priorities are configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for service transmission on each NE; in addition, corresponding QoS processing is configured. Figure 7-26 Networking diagram (VLAN-based E-Line services)
BTS12 VLAN 110 FE R4 GE NE14 FE NE13 NE12 R4 NE15 R4 BTS15 VLAN 120 BTS11 VLAN 100 NE11 Packet network
FE NE16
The connections of Ethernet links shown in Figure 7-26 are described as follows. Table 7-49 Connections of Ethernet links (NE12) Link Between NE12 and NE13 Port 1-EM6T-1 Port Description Description Configure these ports to transmit backhaul services from BTSs.
7-88
Issue 03 (2011-04-10)
Port 3-ISU2-1
Port Description Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group -
Description Configure this port to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
Between NE12 and BTS11
1-EM6T-3
Configure these ports to access services from BTS11.
Table 7-50 Connections of Ethernet links (NE13) Link Between NE13 and NE14 Port 3-ISU2-1 Port Description Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group Description Configure this port to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
4-ISU2-1
6-ISU2-1
Configure this port to transmit Native Ethernet services on Hybrid radio.
1-EM6T-1
Configure this port to transmit backhaul services from BTSs.
Table 7-51 Connections of Ethernet links (NE14) Link Between NE14 and NE13 Port 3-ISU2-1 Port Description Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group Description Configure this port to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
Issue 03 (2011-04-10)
7-89
Link Between NE14 and BTS12
Port 1-EM6T-3
Port Description -
Description Configure this port to access services from BTS12.
Table 7-52 Connections of Ethernet links (NE15) Link Between NE15 and NE16 Port 3-ISU2-1 Port Description Description Configure this port to transmit Native Ethernet services on Hybrid radio. Configure this port to transmit Native Ethernet services on Hybrid radio.
4-ISU2-1
Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group
6-ISU2-1
Table 7-53 Connections of Ethernet links (NE16) Link Between NE16 and NE15 Port 3-ISU2-1 Port Description Description Configure this port to transmit Ethernet services on Hybrid radio. Configure these ports to access services from BTS15.
1-EM6T-3

You need to plan the corresponding parameter information before configuring an Ethernet service. 7.4.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.4.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.4.2.3 Service Planning (Ethernet Services)
The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.4.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.

Information About Ethernet Ports

Table 7-54 to Table 7-57 provide the information about the Ethernet ports that transmit the Ethernet services. Table 7-54 Information about Ethernet ports (NE12) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute 1-EM6T-1 802.1q Auto-negotiation 1536 Disabled Tag aware 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled Tag aware
Table 7-55 Information about Ethernet ports (NE13) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute 1-EM6T-1 802.1q Auto-negotiation 1536 Disabled Tag aware
Table 7-56 Information about Ethernet ports (NE14) Parameter Encapsulation type Port working mode
Issue 03 (2011-04-10)
1-EM6T-3 802.1Q Auto-negotiation

7-91
Parameter Maximum frame length (byte) Flow control Tag attribute
1-EM6T-3 1536 Disabled Tag aware
Table 7-57 Information about Ethernet ports (NE16) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled Tag aware
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its default value of 1522. l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends. l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.

Table 7-58 to Table 7-62 provide the information about the IF_ETH ports that carry the Ethernet services. Table 7-58 Information about the IF_ETH port (NE12) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 5-ISU2-1 802.1q Tag aware
7-92
Issue 03 (2011-04-10)
Table 7-59 Information about the IF_ETH port (NE13) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 5-ISU2-1 802.1q Tag aware 4-ISU2-1 802.1q Tag aware 6-ISU2-1 802.1q Tag aware
Table 7-60 Information about the IF_ETH port (NE14) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1Q Tag aware 5-ISU2-1 802.1Q Tag aware
Table 7-61 Information about the IF_ETH port (NE15) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 4-ISU2-1 802.1q Tag aware 6-ISU2-1 802.1q Tag aware
Table 7-62 Information about the IF_ETH port (NE16) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1Q Tag aware


The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-63 to Table 7-67 provide the planning information of the VLAN-based E-Line services.
Issue 03 (2011-04-10)
7-93
Table 7-63 Information about VLAN-based E-Line services (NE12) Parameter NE12 NE13 to NE11 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 NE13toNE11_Vline UNI-UNI Not transparently transmitted 1-EM6F-1 110,120 3-ISU2-1 110, 120 BTS11 to NE11 2 BTS11toNE11_Vline UNI-UNI Not transparently transmitted 1-EM6T-3 100 3-ISU2-1 100
Table 7-64 Information about VLAN-based E-Line services (NE13) Parameter NE13 NE14 to NE12 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 NE14toNE12_Vline UNI-UNI Not transparently transmitted 3-ISU2-1 110 1-EM6T-1 110 NE15 to NE12 2 NE15toNE12_Vline UNI-UNI Not transparently transmitted 4-ISU2-1 120 1-EM6T-1 120
Table 7-65 Information about VLAN-based E-Line services (NE14) Parameter NE4 BTS12 to NE13 Service ID Service name Service direction 1 BTS12toNE13_Vline UNI-UNI
7-94
Issue 03 (2011-04-10)
Parameter
NE4 BTS12 to NE13
BPDU Source port Source C-VLANs Sink port Sink C-VLANs
Not transparently transmitted 1-EM6T-3 110 3-ISU2-1 110
Table 7-66 Information about VLAN-based E-Line services (NE15) Parameter NE15 NE16 to NE13 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 NE16toNE13_Vline UNI-UNI Not transparently transmitted 3-ISU2-1 120 4-ISU2-1 120
Table 7-67 Information about VLAN-based E-Line services (NE16) Parameter NE16 BTS15 to NE15 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port 1 BTS15toNE15_Vline UNI-UNI Not transparently transmitted 1-EM6T-3 120 3-ISU2-1
Issue 03 (2011-04-10)
7-95
Parameter
NE16 BTS15 to NE15
Sink C-VLANs
120

QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 7-68. Each Ethernet port involved in the service uses the same DS configuration. Table 7-68 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF4 AF3
4 3
AF2
AF1 BE
1 0
7-96
Issue 03 (2011-04-10)
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority and therefore does not need to be modified.

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 7-69 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 7-69 Queue scheduling mode PHB Service Class CS7 CS6 EF AF4 AF3 AF2 AF1 BE Queue Scheduling Mode SP SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP

QoS (Port Shaping)


This section describes the process for data configuration.
Issue 03 (2011-04-10)
7-97
7.4.3.1 Configuration Process (Ethernet Protection) In this example, Ethernet protection is not used. 7.4.3.2 Configuration Process (Service Information) This section describes the process for configuring service information. 7.4.3.3 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.4.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.4.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.


Procedure
Step 1 See A.6.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services. l The values for the related parameters of NE12 are provided as follows. Parameter Value NE13 to NE11 Service ID Service Name Direction Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Port Mode Working Mode 1 NE13toNE11_Vline UNI-UNI 1-EM6F-1 110, 120 3-ISU2-1 110, 120 1-EM6F-1 Enabled Layer 2 AutoNegotiation 3-ISU2-1 Layer 2 BTS11 to NE11 2 BTS11toNE11_Vline UNI-UNI 1-EM6T-3 100 3-ISU2-1 100 1-EM6T-3 Enabled Layer 2 AutoNegotiation 3-ISU2-1 Layer 2 -
7-98
Issue 03 (2011-04-10)
Parameter
Value NE13 to NE11 BTS11 to NE11 802.1Q Tag Aware 802.1Q Tag Aware 802.1Q Tag Aware
Encapsulation Type Tag
802.1Q Tag Aware
l The values for the related parameters of NE13 are provided as follows. Parameter Value NE14 to NE12 Service ID Service Name Direction Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Port Mode Working Mode Encapsulation Type Tag 1 NE14toNE12_Vline UNI-UNI 3-ISU2-1 110 1-EM6T-1 110 3-ISU2-1 Layer 2 802.1Q Tag Aware 1-EM6T-1 Enabled Layer 2 AutoNegotiation 802.1Q Tag Aware NE15 to NE12 2 NE15toNE12_Vline UNI-UNI 4-ISU2-1 120 1-EM6T-1 120 4-ISU2-1 Layer 2 802.1Q Tag Aware 1-EM6T-1 Enabled Layer 2 AutoNegotiation 802.1Q Tag Aware
l The values for the related parameters of NE14 are provided as follows. Parameter Value BTS12 to NE13 Service ID Service Name Direction Source Interface
Issue 03 (2011-04-10)
1 BTS12toNE13_Vline UNI-UNI 1-EM6T-3

7-99
Parameter
Value BTS12 to NE13
Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Port Mode Working Mode Encapsulation Type Tag
110 3-ISU2-1 110 1-EM6T-3 Enabled Layer 2 Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 Layer 2 802.1Q Tag Aware
l The values for the related parameters of NE16 are provided as follows. Parameter Value BTS15 to NE15 Service ID Service Name Direction Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Port Mode Working Mode Encapsulation Type Tag 1 BTS5toNE5_Vline UNI-UNI 1-EM6T-3 120 3-ISU2-1 120 1-EM6T-3 Enabled Layer 2 Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 Layer 2 802.1Q Tag Aware
----End

Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 1-EM6T-1 Max Frame Length(byte) 1536 1-EM6T-3 1536
l The values for the related parameters of NE13 are provided as follows. Parameter Value 1-EM6T-1 Max Frame Length(byte) 1536
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and modify the mapping relationships for the DS domain.
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information. Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as follows.
Parameter Mapping Relation ID Mapping Relation Name
Value 1 Default Map
The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN 0 1 2 3 4 5 6 7 SVLAN Default value IP DSCP Default value MPLS EXP Default value PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7 CVLAN 0 1 2 3 4 5 6 7 SVLAN Default value IP DSCP Default value MPLS EXP Default value
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
7-102
Issue 03 (2011-04-10)
Step 2 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network planning information. Therefore, you can skip this step.
l The values for the related parameters of NE12 are provided as follows. Port 1-EM6T-1 1-EM6T-3 3-ISU2-1 l The values for the related parameters of NE13 are provided as follows. Port 3-ISU2-1 4-ISU2-1 1-EM6T-1 l The values for the related parameters of NE14 are provided as follows. Port 3-ISU2-1 1-EM6T-3 l The values for the related parameters of NE15 are provided as follows. Port 3-ISU2-1 4-ISU2-1 l The values for the related parameters of NE16 are provided as follows. Port 1-EM6T-3 3-ISU2-1 Packet Type CVLAN Packet Type CVLAN Packet Type CVLAN Packet Type CVLAN Packet Type CVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. l The values for the related parameters of NE12 to NE16 are provided as follows. Parameter Policy ID
Issue 03 (2011-04-10)
Value 1
7-103
Parameter Policy Name Grooming Police After Reloading
Value Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Policy Weight(%)
5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Disabled (for all PHB service classes)
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. l The values for the related parameters of NE12 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-1 1-EM6T-3 3-ISU2-1 l The values for the related parameters of NE13 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1 1-EM6T-1 l The values for the related parameters of NE14 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1
7-104
Issue 03 (2011-04-10)
Parameter
Value Port_Comm (Policy ID=1)
Port
3-ISU2-1 4-ISU2-1
l The values for the related parameters of NE16 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and configure the MD for NE12, NE14, and NE16. The values for the related parameters are provided as follows. Parameter Value NE12 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE14 EdgeNE 4 NE16 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create the maintenance association (MA) for NE12, NE14, and NE16. l The values for the relevant parameters of NE12 are provided as follows. l Parameter Maintenance Domain Name Maintenance Association Name Value EdgeNE BTS11_Vline EdgeNE BTS11_Vline EdgeNE BTS12_Vline EdgeNE BTS15_Vline
Issue 03 (2011-04-10)
7-105
Parameter Relevant Service CC Test Transmit Period
Value 1BTS11toNE11 _Vline 1s 1NE13toNE11_ Vline 1s 1NE13toNE11_ Vline 1s 1NE13toNE11_ Vline 1s
l The values for the relevant parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS12_Vline 1-BTS12toNE13_Vline 1s
l The values for the relevant parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS15_Vline 1-BTS15toNE15_Vline 1s
Step 3 See A.6.8.3 Creating an MEP Point and create the MEP for NE12, NE14, and NE16. l The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction
7-106
Value EdgeNE BTS11_Vline EdgeNE BTS11_Vline EdgeNE BTS12_Vline EdgeNE BTS15_Vline
1-EM6T 1-EM6T-3 100 201 Ingress
3-ISU2 3-ISU2-1 100 200 Ingress

Issue 03 (2011-04-10)
Parameter CC Status AIS Active Status
Value Active Active Active Active Active Active Active Active
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS12_Vline 1-EM6T-3 1-EM6T-3 110 401 Ingress Active Active
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS15_Vline 1-EM6T 1-EM6T-3 120 601 Ingress Active Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEP points for NE12, NE14, and NE16. The values for the related parameters of NE12 are provided as follows.
Issue 03 (2011-04-10)
7-107
Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6)
Value EdgeNE BTS11_Vline 201 EdgeNE BTS12_Vline 401 EdgeNE BTS15_Vline 601
The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS12_Vline 202
The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS15_Vline 205
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services on NE12. l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 202 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 205 as the source MEP and the MEP whose MEP ID is 601 as the sink MEP. There should be no packets lost during the LB tests. ----End
7.5 Configuration Example (QinQ-Based E-Line Service)

This section considers a QinQ-based E-line service as an example to describe how to configure the Ethernet service according to the network planning information.
7.5.1 Networking Diagram This section describes the networking information about the NEs. 7.5.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service. 7.5.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure Ethernet services according to the following requirements: l l l BTS11 to BTS15 provide FE ports whose port rate is 100 Mbit/s. GE links to the RNC are configured with LAG protection. The VLAN ID used by the services on a BTS is allocated by the RNC that controls the BTS. Therefore, the VLAN IDs of services on BTSs that are controlled by different RNCs may be the same. To solve this problem, an RNC allocates an S-VLAN ID for each BTS, and the S-VLAN IDs on the entire network are planned in a unified manner. VLAN priorities are configured on each BTS according to service types.
To meet the preceding requirements, QinQ-based E-Line services are configured for service transmission on each NE; in addition, corresponding QoS processing is configured. Figure 7-27 Networking diagram (QinQ-based E-Line services)
BTS12 SVLAN 201
FE R4 GE NE14 FE NE13 NE12 NE11 R4 BTS11 SVLAN 200 RNC GE
FE NE16 R4 BTS15 SVLAN 202
NE15
The connections of Ethernet links shown in Figure 7-27 are described as follows.
Issue 03 (2011-04-10)
7-109
Table 7-70 Connections of Ethernet links (NE11) Link Between NE11 and the RNC Between NE11 and NE12 Port 1-EM6T-1 1-EM6T-2 3-ISU2-1 Port Description Main port of a LAG Slave port of a LAG Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group Description Configure these ports to transmit backhaul services from BTSs. Configure these ports to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
Table 7-71 Connections of Ethernet links (NE12) Link Between NE12 and NE13 Between NE12 and NE11 Port 1-EM6T-1 Port Description Description Configure these ports to transmit backhaul services from BTSs. Configure this port to transmit Native Ethernet services on Hybrid radio.
3-ISU2-1
Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group -
5-ISU2-1
1-EM6T-3
Table 7-72 Connections of Ethernet links (NE13) Link Between NE13 and NE14 Port 3-ISU2-1 Port Description Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group Main IF board of a 1 +1 HSB protection group Description Configure this port to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
4-ISU2-1

Issue 03 (2011-04-10)
7-110
Link
Port 6-ISU2-1
Port Description Standby IF board of a 1+1 HSB protection group -
Description
1-EM6T-1
5-ISU2-1
1-EM6T-3
Configure this port to access services from BTS12.
4-ISU2-1
6-ISU2-1
Issue 03 (2011-04-10)
7-111
1-EM6T-3

You need to plan the corresponding parameter information before configuring an Ethernet service. 7.5.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.5.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.5.2.3 Service Planning (Ethernet Services) The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.5.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.


Table 7-76 to Table 7-80 provide the information about the Ethernet ports that transmit the Ethernet services. Table 7-76 Information about Ethernet ports (NE11) Parameter Encapsulation type Port working mode 1-EM6T-1 802.1q Auto-negotiation 1-EM6T-2 802.1q Auto-negotiation
7-112
Issue 03 (2011-04-10)
Parameter Maximum frame length (byte) Flow control Tag attribute
Table 7-77 Information about Ethernet ports (NE12) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute QinQ type domain 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled Tag aware 1-EM6T-1 QinQ Auto-negotiation 1536 Disabled Tag aware 0x88a8
Table 7-78 Information about Ethernet ports (NE13) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control QinQ type domain 1-EM6T-1 QinQ Auto-negotiation 1536 Disabled 0x88a8
Table 7-79 Information about Ethernet ports (NE14) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled
Issue 03 (2011-04-10)
7-113
Table 7-80 Information about Ethernet ports (NE16) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends. l In this example, all the NNI ports are connected to Huawei equipment. Therefore, the QinQ type domain of the NNI ports assumes the default value of 0x88a8.

Table 7-81 to Table 7-86 provide the information about the IF_ETH ports that carry the Ethernet services. Table 7-81 Information about the IF_ETH port (NE11) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8 5-ISU2-1 QinQ 0x88a8
Table 7-82 Information about the IF_ETH port (NE12) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8 5-ISU2-1 QinQ 0x88a8
7-114
Issue 03 (2011-04-10)
Table 7-83 Information about the IF_ETH port (NE13) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8 5-ISU2-1 QinQ 0x88a8 4-ISU2-1 QinQ 0x88a8 6-ISU2-1 QinQ 0x88a8
Table 7-85 Information about the IF_ETH port (NE15) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8 4-ISU2-1 QinQ 0x88a8 6-ISU2-1 QinQ 0x88a8
Table 7-86 Information about the IF_ETH port (NE16) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8
NOTE
All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you need to set the QinQ type domain to 0x88a8 for the IF_ETH ports.

The service planning information contains the information about all the parameters required for configuring Ethernet protection. To improve the reliability of service transmission, NE11 and the RNC are interconnected through the LAG formed by two GE links. Table 7-87 provides the planning information.
Issue 03 (2011-04-10)
7-115
Table 7-87 LAG information Parameter LAG type Revertive mode Load sharing mode System priority Main port Slave port NE11 Static (default value) Non-revertive Non-sharing (default value) 32768 (default value) 1-EM6T-1 1-EM6T-2
NOTE
In this example, the bandwidth of the Ethernet services is much lower than the bandwidth of a GE port. Therefore, you need not configure the LAG to the load-sharing mode for increasing the bandwidth.

The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-88 to Table 7-93 provide the planning information of the QinQ-based E-Line services. Table 7-88 Information about the QinQ-based E-Line service (NE11) Parameter NE11 BTS12 to the RNC Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) QinQ link (sink) 1 BTS12toRNC_Qline UNI-NNI Not transparently transmitted 1-EM6T-1 ID: 1 Port: 3-ISU2-1 S-VLAN: 201 BTS11 to the RNC 2 BTS11toRNC_Qline UNI-NNI Not transparently transmitted 1-EM6T-1 ID: 2 Port: 3-ISU2-1 S-VLAN: 200 BTS15 to the RNC 3 BTS15toRNC2_Qli ne UNI-NNI Not transparently transmitted 1-EM6T-1 ID: 3 Port: 3-ISU2-1 S-VLAN: 202
7-116
Issue 03 (2011-04-10)
Table 7-89 Information about the QinQ-based E-Line service (NE12) Parameter NE12 BTS11 to NE11 Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) 1 BTS11toNE11_Qlin e UNI-NNI Not transparently transmitted 1-EM6T-3 BTS12 to NE11 2 BTS12toNE11_Qlin e NNI-NNI Not transparently transmitted ID: 2 Port: 1-EM6T-1 S-VLAN: 201 QinQ link (sink) ID: 1 Port: 3-ISU2-1 S-VLAN: 200 ID: 3 Port: 3-ISU2-1 S-VLAN: 201 BTS15 to NE11 3 BTS15toNE11_Qlin e NNI-NNI Not transparently transmitted ID: 4 Port: 1-EM6T-1 S-VLAN: 202 ID: 5 Port: 3-ISU2-1 S-VLAN: 202
Table 7-90 Information about the QinQ-based E-Line service (NE13) Parameter NE13 BTS12 to NE12 Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) 1 BTS12toNE12_Qline NNI-NNI Not transparently transmitted ID: 1 Port: 1-EM6T-1 S-VLAN: 201 QinQ link (sink) ID: 2 Port: 3-ISU2-1 S-VLAN: 201 BTS15 to NE12 2 BTS15toNE12_Qline NNI-NNI Not transparently transmitted ID: 3 Port: 1-EM6T-1 S-VLAN: 202 ID: 4 Port: 4-ISU2-1 S-VLAN: 202
Issue 03 (2011-04-10)
7-117
Table 7-91 Information about the QinQ-based E-Line service (NE14) Parameter NE14 BTS12 to NE13 Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) QinQ link (sink) 1 BTS12toNE13_Qline UNI-NNI Not transparently transmitted 1-EM6T-3 ID: 1 Port: 3-ISU2-1 S-VLAN: 201
Table 7-92 Information about the QinQ-based E-Line service (NE15) Parameter NE15 BTS15 to NE13 Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) 1 BTS15toNE13_Qline NNI-NNI Not transparently transmitted ID: 1 Port: 3-ISU2-1 SVLAN: 202 QinQ link (sink) ID: 2 Port: 4-ISU2-1 S-VLAN: 202
7-118
Issue 03 (2011-04-10)
Table 7-93 Information about the QinQ-based E-Line service (NE16) Parameter NE16 BTS15 to NE15 Service ID Service name Service direction BPDU Source port Source C-VLANs QinQ link (source) QinQ link (sink) 1 BTS15toNE15_Qline UNI-NNI Not transparently transmitted 1-EM6T-3 ID: 1 Port: 3-ISU2-1 S-VLAN: 202

QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 7-94. Each Ethernet port involved in the service uses the same DS configuration. Table 7-94 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services)
7-119
Issue 03 (2011-04-10)
PHB Service Class AF4 AF3
VLAN Priority 4 3
Corresponding Service Type Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF2
AF1 BE
1 0
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority and therefore needs to be modified as required.

7-120
Issue 03 (2011-04-10)

QoS (Port Shaping)


This section describes the process for data configuration. 7.5.3.1 Configuration Process (Ethernet Protection) This section describes the procedures for configuring LAG. 7.5.3.2 Configuration Process (Service Information) This section describes the process for configuring service information. 7.5.3.3 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.5.3.4 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

This section describes the procedures for configuring LAG.
Procedure
Step 1 See A.6.2.1 Creating a LAG and create the LAG for NE11. The values for the required parameters that are set in the main interface are as follows. Parameter LAG No. LAG Name LAG Type Revertive Mode Load Sharing System Priority Value Automatically Assign ToBSC Static Non-Revertive Non-Sharing 32768
Issue 03 (2011-04-10)
7-121
The values for the related parameters that need to be set in Port Setting are as follows. Parameter Main Board Main Port Selected Standby Ports Value 1-EM6T 1 (PORT-1) 1-EM6T-2
----End

Procedure
Step 1 See A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) and configure the E-Line services. l The values for the related parameters of NE11 are provided as follows. The values for the required parameters that are set in the main interface are as follows. Parameter Value BTS12 to the RNC1 Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type 1 BTS12toRNC1_Qline UNI-NNI Not Transparently Transmitted 1-EM6T-1 QinQ Link BTS11 to RNC2 2 BTS11&15toRNC2 _Qline UNI-NNI Not Transparently Transmitted 1-EM6T-1 QinQ Link BTS15 to RNC2 3 BTS11&15toRNC2 _Qline UNI-NNI Not Transparently Transmitted 1-EM6T-1 QinQ Link
The values for QinQ link parameters are provided as follows. Parameter Value BTS12 to the RNC1 QinQ Link ID
7-122
BTS11 to RNC2 2
BTS15 to RNC2 3
Issue 03 (2011-04-10)
Parameter
Value BTS12 to the RNC1 BTS11 to RNC2 3-ISU2-1 200 BTS15 to RNC2 3-ISU2-1 200
Port S-Vlan ID
3-ISU2-1 201
The values for Ethernet port attributes are provided as follows. Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag Value 1-EM6T-1 Enabled Layer 2 802.1Q Auto-Negotiation Tag Aware 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware
l The values for the related parameters of NE12 are provided as follows. The values for the required parameters that are set in the main interface are as follows. Parameter Value BTS11 to NE11 Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type 1 BTS11toNE11_Qli ne UNI-NNI Not Transparently Transmitted 1-EM6T-3 QinQ Link BTS12 to NE11 2 BTS12toNE11_Qli ne NNI-NNI Not Transparently Transmitted QinQ Link BTS15 to NE11 3 BTS15toNE11_Qli ne NNI-NNI Not Transparently Transmitted QinQ Link
The values for QinQ link parameters are provided as follows.
Issue 03 (2011-04-10)
7-123
Parameter
Value BTS11 to NE11 BTS12 to NE11 2 1-EM6T-1 201 3 3-ISU2-1 201 BTS15 to NE11 4 1-EM6T-1 202 5 3-ISU2-1 202
QinQ Link ID Port S-Vlan ID
1 3-ISU2-1 200
The values for Ethernet port attributes are provided as follows. Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag Value 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware 1-EM6T-3 Enabled Layer 2 802.1Q Auto-Negotiation Tag Aware 1-EM6T-1 Enabled Layer 2 QinQ Auto-Negotiation Tag Aware
l The values for the related parameters of NE13 are provided as follows. The values for the required parameters that are set in the main interface are as follows. Parameter Value BTS12 to NE12 Service ID Service Name Direction BPDU Bearer Type 1 BTS12toNE12_Qline NNI-NNI Not Transparently Transmitted QinQ Link BTS15 to NE12 2 BTS15toNE12_Qline NNI-NNI Not Transparently Transmitted QinQ Link
7-124
Issue 03 (2011-04-10)
Parameter
Value BTS12 to NE12 BTS15 to NE12 2 3-ISU2-1 201 3 1-EM6T-1 202 4 4-ISU2-1 202
1 1-EM6T-1 201
The values for Ethernet port attributes are provided as follows. Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag Value 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware 1-EM6T-1 Enabled Layer 2 QinQ Auto-Negotiation Tag Aware
l The values for the related parameters of NE14 are provided as follows. The values for the required parameters that are set in the main interface are as follows. Parameter Value BTS12 to NE13 Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type 1 BTS12toNE13_Qline UNI-NNI Not Transparently Transmitted 1-EM6T-3 QinQ Link
Issue 03 (2011-04-10)
7-125
Parameter
Value BTS12 to NE12
1 3-ISU2-1 201
The values for Ethernet port attributes are provided as follows. Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag Value 1-EM6T-3 Enabled Layer 2 802.1Q Auto-Negotiation Tag Aware 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware
l The values for the related parameters of NE15 are provided as follows. The values for the required parameters that are set in the main interface are as follows. Parameter Value BTS15 to NE13 Service ID Service Name Direction BPDU Bearer Type 1 BTS15toNE13_Qline NNI-NNI Not Transparently Transmitted QinQ Link
The values for QinQ link parameters are provided as follows. Parameter Value BTS12 to NE12 QinQ Link ID Port 1 3-ISU2-1 2 4-ISU2-1
7-126
Issue 03 (2011-04-10)
Parameter
Value BTS12 to NE12
S-Vlan ID
202
202
The values for Ethernet port attributes are provided as follows. Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag Value 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware 4-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware
l The values for the related parameters of NE16 are provided as follows. Parameter Value BTS15 to NE15 Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type 1 BTS15toNE15_Qline UNI-NNI Not Transparently Transmitted 1-EM6T-3 QinQ Link
The values for QinQ link parameters are provided as follows. Parameter QinQ Link ID Port S-Vlan ID Value 1 3-ISU2-1 202
The values for Ethernet port attributes are provided as follows.

Parameter Port Enable Port Port Mode Encapsulation Type Working Mode Tag
Value 1-EM6T-3 Enabled Layer 2 802.1Q Auto-Negotiation Tag Aware 3-ISU2-1 Layer 2 QinQ Auto-Negotiation Tag Aware
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and change the mapping relationships for the DS domain. The values for the required parameters that are set in the main interface are as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN 0 1 2 3 4 5 6 7 SVLAN 0 1 2 3 4 5 6 7 IP DSCP Default value MPLS EXP Default value PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
7-128
Issue 03 (2011-04-10)
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7 CVLAN 0 1 2 3 4 5 6 7 SVLAN 0 1 2 3 4 5 6 7 IP DSCP Default value MPLS EXP Default value
NOTE
Step 2 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet type. l The values for the related parameters of NE11 are provided as follows. Port 3-ISU2-1 1-EM6F-1 Packet Type SVLAN CVLAN
l The values for the related parameters of NE12 are provided as follows. Port 1-EM6T-3 1-EM6T-1 3-ISU2-1 Packet Type CVLAN SVLAN SVLAN
l The values for the related parameters of NE13 are provided as follows. Port 3-ISU2-1 4-ISU2-1
Issue 03 (2011-04-10)
Packet Type SVLAN SVLAN

Port 1-EM6T-1
Packet Type SVLAN
l The values for the related parameters of NE14 are provided as follows. Port 1-EM6T-3 3-ISU2-1 Packet Type CVLAN SVLAN
l The values for the related parameters of NE15 are provided as follows. Port 3-ISU2-1 4-ISU2-1 Packet Type SVLAN SVLAN
l The values for the related parameters of NE16 are provided as follows. Port 3-ISU2-1 1-EM6T-3 Packet Type SVLAN CVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the related parameters of NE11 to NE16 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes)
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy.
l The values for the related parameters of NE11 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 1-EM6T-1 l The values for the related parameters of NE12 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-1
l The values for the related parameters of NE13 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1 1-EM6T-1 l The values for the related parameters of NE14 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and configure the MD for NE11, NE12, NE14, and NE16. The values for the required parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE12 EdgeNE 4 NE14 EdgeNE 4 NE16 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and configure the MA for NE11, NE12, NE14, and NE16. l The values for the related parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS11_Qline 1-BTS11_Qline 1s EdgeNE BTS12_Qline 2-BTS12_Qline 1s EdgeNE BTS15_Qline 5-BTS15_Qline 1s
l The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS11_Qline 1-BTS11_Qline 1s
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name
7-132
Value EdgeNE
Issue 03 (2011-04-10)
Parameter Maintenance Association Name Relevant Service CC Test Transmit Period
Value BTS12_Qline 1-BTS12_Qline 1s
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS15_Qline 1-BTS15_Qline 1s
Step 3 See A.6.8.3 Creating an MEP Point and create the MEPs. l The values for the related parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status EdgeNE BTS11_Qline 1-EM6T 1-EM6T-1 100 101 Ingress Active Active EdgeNE BTS12_Qline 1-EM6T 1-EM6T-1 110 102 Ingress Active Active EdgeNE BTS15_Qline 1-EM6T 1-EM6T-1 140 105 Ingress Active Active
l The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port
Issue 03 (2011-04-10)
Value EdgeNE BTS11_Qline 1-EM6T 1-EM6T-3
7-133
Parameter VLAN MP ID Direction CC Status AIS Active Status
Value 201 Ingress Active Active
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS12_Qline 1-EM6T 1-EM6T-3 401 Ingress Active Active
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS15_Qline 1-EM6T 1-EM6T-3 601 Ingress Active Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs of the MA for NE11, NE12, NE14, and NE16.
The values for the related parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS11_Qline 201 EdgeNE BTS12_Qline 401 EdgeNE BTS15_Qline 601
The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS11_Qline 101
Step 5 On NE1, perform LB tests to test the Ethernet service configurations. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP.
l Perform the LB test by considering the MEP whose MEP ID is 102 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 105 as the source MEP and the MEP whose MEP ID is 601 as the sink MEP. There should be no packet lost during the LB tests. ----End
7.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)

This section considers an 802.1d-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.6.1 Networking Diagram This section describes the networking information about the NEs. 7.6.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service. 7.6.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network), configure Ethernet services according to the following requirements: l l l l l BTS21 to BTS23 provide FE ports whose port rate is 100 Mbit/s. The Ethernet services on the ring network are protected. The BTS services are transparently transmitted. VLAN priorities are configured on each BTS according to service types. The functions of detecting looped services and suppressing broadcast packets need to be provided on the network.
To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured to implement transmission of the BTS services; in addition, the functions of detecting looped services and suppressing broadcast packets, ERPS protection, and QoS processing are configured. See Figure 7-28.
7-136
Issue 03 (2011-04-10)
Figure 7-28 Networking diagram (IEEE 802.1d bridge-based E-LAN services)
Packet network NE21
FE ERPS R4 NE22 BTS21 802.1d bridge NE24
FE R4 BTS24 802.1d bridge
FE NE23 802.1d bridge R4 BTS23
The connections of Ethernet links shown in Figure 7-28 are described as follows. Table 7-96 Connections of Ethernet links (NE21) Link Between NE21 and the PSN Port 1-EM6F-3 Port Description Description Configure this port to drop the Native ELAN services from the Hybrid radio ring network. Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to transmit Ethernet services on Hybrid radio.
4-ISU2-1
East port of an ERPS ring node
3-ISU2-1
West port of an ERPS ring node Main IF board of a 1 +1 SD protection group
5-ISU2-1
Standby IF board of a 1+1 SD protection group
Issue 03 (2011-04-10)
7-137
Table 7-97 Connections of Ethernet links (NE22) Link Between NE22 and NE23 Port 4-ISU2-1 Port Description East port of an ERPS ring node Description Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to access services from BTS21. Configure this port to transmit Ethernet services on Hybrid radio.
Between NE22 and BTS21 Between NE22 and NE21
1-EM6T-3
3-ISU2-1
West port of an ERPS ring node
Table 7-98 Connections of Ethernet links (NE23) Link Between NE23 and NE24 Port 4-ISU2-1 Port Description l East port of an ERPS ring node l RPL port Between NE23 and BTS23 Between NE23 and NE22 1-EM6T-3 Description Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to access services from BTS23. Configure this port to transmit Ethernet services on Hybrid radio.
3-ISU2-1
Table 7-99 Connections of Ethernet links (NE24) Link Between NE24 and NE21 Port 4-ISU2-1 Port Description East port of an ERPS ring node Main IF board of a 1 +1 SD protection group 6-ISU2-1 Standby IF board of a 1+1 SD protection group Description Configure these ports to transmit Ethernet services on Hybrid radio.
7-138
Issue 03 (2011-04-10)
Link Between NE24 and BTS24 Between NE24 and NE23
Port 1-EM6T-3
Port Description -
Description Configure this port to access services from BTS24. Configure this port to transmit Ethernet services on Hybrid radio.
3-ISU2-1

You need to plan the corresponding parameter information before configuring an Ethernet service. 7.6.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.6.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.6.2.3 Service Planning (Ethernet Services) The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.6.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.


Table 7-103 and Table 7-100 provide the information about the Ethernet ports that transmit the Ethernet services. Table 7-100 Information about Ethernet ports (NE21) Parameter Encapsulation type Port working mode Maximum frame length (byte)
Issue 03 (2011-04-10)
1-EM6F-3 Null Auto-negotiation 1536

7-139
Parameter Flow control Enabling broadcast packet suppression Broadcast packet suppression threshold
1-EM6F-3 Disabled Enabled 30
Table 7-101 Information about Ethernet ports (NE22) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Enabling broadcast packet suppression Broadcast packet suppression threshold 1-EM6T-3 Null Auto-negotiation 1536 Disabled Enabled 30
Table 7-103 Information about Ethernet ports (NE24) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control 1-EM6T-3 Null Auto-negotiation 1536 Disabled
7-140
Issue 03 (2011-04-10)
Parameter Enabling broadcast packet suppression Broadcast packet suppression threshold
1-EM6T-3 Enabled 30
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its default value of 1522.

Table 7-104 to Table 7-107 provide the information about the IF_ETH ports that carry the Ethernet services. Table 7-104 Information about the IF_ETH port (NE21) Parameter Encapsulation type 3-ISU2-1 Null 5-ISU2-1 Null 4-ISU2-1 Null
Table 7-105 Information about the IF_ETH port (NE22) Parameter Encapsulation type 3-ISU2-1 Null 4-ISU2-1 Null
Table 7-107 Information about the IF_ETH port (NE24) Parameter Encapsulation type 3-ISU2-1 Null 4-ISU2-1 Null 6-ISU2-1 Null
Issue 03 (2011-04-10)
7-141

The service planning information contains the information about all the parameters required for configuring Ethernet protection.
Information About ERPS Instances

Table 7-108 provides the planning information about ERPS instances. Table 7-108 Information about ERPS instances Parameter ERPS ID East port West port RPL owner ring node flag RPL port Control VLAN Packet transmit interval Entity level WTR time Guard time Hold-off time NE21 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value) 500 ms (default value) 0s (default value) NE22 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value) 500 ms (default value) 0s (default value) NE23 1 4-ISU2-1 3-ISU2-1 Yes 4-ISU2-1 4093 5s (default value) 4 (default value) 5 minutes (default value) 500 ms (default value) 0s (default value) NE24 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value) 500 ms (default value) 0s (default value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link is relatively even. l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control VLAN use VLAN 4093. l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their default values.

The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-109 provides the planning information of IEEE 802.1a bridge-based E-LAN services.
Table 7-109 Information about IEEE 802.1d bridge-based E-LAN services Parameter Service ID Service name TAG type Self-learning MAC address MAC address learning mode Mounted UNI port NE21 1 Dlan TagTransparent Enabled SVL 1-EM6F-3 3-ISU2-1 4-ISU2-1 NE22 1 Dlan TagTransparent Enabled SVL 1-EM6T-3 3-ISU2-1 4-ISU2-1 NE23 1 Dlan TagTransparent Enabled SVL 1-EM6T-3 3-ISU2-1 4-ISU2-1 NE24 1 Dlan TagTransparent Enabled SVL 1-EM6T-3 3-ISU2-1 4-ISU2-1

QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 7-110. Each Ethernet port involved in the service uses the same DS configuration. Table 7-110 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) 7-143
AF4
Issue 03 (2011-04-10)
4
PHB Service Class AF3
VLAN Priority 3
AF2
AF1 BE
1 0
NOTE

7-144
Issue 03 (2011-04-10)

QoS (Port Shaping)


This section describes the process for data configuration. 7.6.3.1 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.6.3.2 Configuration Process (Ethernet Protection) This section describes the process for configuring Ethernet protection. 7.6.3.3 Configuration Process (Service Information) This section describes the process for configuring service information. 7.6.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.6.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of Ethernet ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6F-3 Enable Port Port Mode Encapsulation Type Working Mode
Issue 03 (2011-04-10)
Enabled Layer 2 Null Auto-Negotiation

7-145
Parameter
Value 1-EM6F-3
Max Frame Length(byte)
1536
l The values for the related parameters of NE22 and NE24 are provided as follows. Parameter Value 1-EM6T-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 Null Auto-Negotiation 1536
l The values for the related parameters of NE23 are provided as follows. Parameter Value 1-EM6T-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 Null Auto-Negotiation 1536
Step 2 See A.5.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes of Ethernet ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6F-3 Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled Enabled 30
l The values for the related parameters of NE22 and NE24 are provided as follows.
Parameter
Value 1-EM6T-3
Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold
Enabled Enabled 30
l The values for the related parameters of NE23 are provided as follows. Parameter Value 1-EM6T-3 Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled Enabled 30
Step 3 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes of the IF_ETH ports. l The values for the related parameters of NE22 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null 4-ISU2-1 Layer 2 Null 5-ISU2-1 Layer 2 Null
l The values for the related parameters of NE23 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null 4-ISU2-1 Layer 2 Null
l The values for the related parameters of NE24 are provided as follows. Parameter Value 3-ISU2-1 Port Mode
Issue 03 (2011-04-10)
4-ISU2-1 Layer 2
6-ISU2-1 Layer 2
7-147
Layer 2
Parameter
Value 3-ISU2-1 4-ISU2-1 Null 6-ISU2-1 Null
Encapsulation Type
Null
Step 4 See A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port and set the advanced attributes of the IF_ETH ports. l The values for the related parameters of NE22 and NE23 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 30 4-ISU2-1 Enabled 30
l The values for the related parameters of NE24 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 4-ISU2-1 Enabled 6-ISU2-1 Enabled
30
30
30
----End

This section describes the process for configuring Ethernet protection.
Procedure
Step 1 See A.6.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance. The values for the required parameters are provided as follows. Parameter Value NE21 ERPS ID
7-148
NE22 1
NE23 1
NE24 1
Issue 03 (2011-04-10)
Parameter
Value NE21 NE22 4-ISU2-1 3-ISU2-1 No 4093 NE23 4-ISU2-1 3-ISU2-1 Yes 4-ISU2-1 4093 NE24 4-ISU2-1 3-ISU2-1 No 4093
East Port West Port RPL Owner Ring Node Flag RPL Port Control VLAN
4-ISU2-1 3-ISU2-1 No 4093
----End

Procedure
Step 1 See A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the ELAN services. l Parameters of NE21 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Dlan Tag-Transparent Enabled 1-EM6F-3 UNI Blank Enabled Auto-Negotiation Null Tag Aware 3-ISU2-1 UNI Blank Null Tag Aware 4-ISU2-1 UNI Blank Null Tag Aware
Issue 03 (2011-04-10)
7-149
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6F-3 3-ISU2-1 4-ISU2-1 l Parameters of NE22 and NE24 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Dlan Tag-Transparent Enabled 1-EM6T-3 UNI Blank Enabled Auto-Negotiation Null Tag Aware 3-ISU2-1 UNI Blank Null Tag Aware 4-ISU2-1 UNI Blank Null Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 3-ISU2-1 4-ISU2-1 l Parameters of NE23 The values for the related parameters that need to be set in the main interface are provided as follows.
Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag
Value 1 Dlan Tag-Transparent Enabled 1-EM6T-3 UNI Blank Enabled Auto-Negotiation Null Tag Aware 3-ISU2-1 UNI Blank Null Tag Aware 4-ISU2-1 UNI Blank Null Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 3-ISU2-1 4-ISU2-1
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and change the mapping relationships for the DS domain.
NOTE
The values for the related parameters that need to be set in the main interface are provided as follows.
Parameter Mapping Relation ID Mapping Relation Name
Value 1 Default Map
NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
7-152
Issue 03 (2011-04-10)
NOTE
l The values for the related parameters of NE21 are provided as follows. Port 1-EM6F-3 3-ISU2-1 4-ISU2-1 Packet Type CVLAN
l The values for the related parameters of NE22 are provided as follows. Port 1-EM6T-3 3-ISU2-1 4-ISU2-1 Packet Type CVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the related parameters of each NE are provided as follows. Parameter Policy ID Policy Name Value 1 Port_Comm
Issue 03 (2011-04-10)
7-153
Parameter Grooming Police After Reloading
Value SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Policy Weight(%)
5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. l The values for the related parameters of NE21 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6F-3 3-ISU2-1 4-ISU2-1 l The values for the related parameters of NE22 and NE24 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-3 3-ISU2-1 4-ISU2-1 l The values for the related parameters of NE23 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-3 3-ISU2-1 4-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs. The values for the required parameters are provided as follows. Parameter Value NE21 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE22 EdgeNE 4 NE23 EdgeNE 4 NE24 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create the MA. The values for the required parameters are provided as follows. Parameter Value NE21 Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period EdgeNE Dlan NE22 EdgeNE Dlan NE23 EdgeNE Dlan NE24 EdgeNE Dlan
1-Dlan 1s
1-Dlan 1s
1-Dlan 1s
1-Dlan 1s
Step 3 See A.6.8.3 Creating an MEP Point and create the MEPs. The values for the required parameters are provided as follows. Parameter Value NE21 Maintenance Domain Name Maintenance Association Name Board
Issue 03 (2011-04-10)
NE22 EdgeNE Dlan
NE23 EdgeNE Dlan
NE24 EdgeNE Dlan
EdgeNE Dlan
1-EM6F
1-EM6T
1-EM6T
1-EM6T
7-155
Parameter
Value NE21 NE22 1-EM6T-3 201 Ingress Active Active NE23 1-EM6T-3 301 Ingress Active Active NE24 1-EM6T-3 401 Ingress Active Active
Port VLAN MP ID Direction CC Status AIS Active Status
1-EM6F-3 101 Ingress Active Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEP points. The values for the related parameters of NE21 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g: 1,3-6) Value EdgeNE Dlan EdgeNE Dlan EdgeNE Dlan EdgeNE Dlan
201
202
302
401
The values for the related parameters of NE22 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE Dlan 101
The values for the related parameters of NE23 are provided as follows. Parameter Maintenance Domain Name Value EdgeNE
7-156
Issue 03 (2011-04-10)
Parameter Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6)
Value Dlan 101
The values for the related parameters of NE24 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE Dlan 101
Step 5 Perform an LB test to verify Ethernet service configurations. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 202 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 301 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. There should be no packet lost during the LB tests. ----End
7.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)

This section considers an 802.1q-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.7.1 Networking Diagram This section describes the networking information about the NEs. 7.7.2 Service Planning You need to plan the corresponding parameter information before service configuration. 7.7.3 Configuration Process This section describes the process for data configuration.

Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure Ethernet services according to the following requirements: l l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s. BTS11 and BTS12 belong to domain 1; BTS15 belongs to domain 2. The BTSs in a domain have the same VLAN ID and the data from different domains is isolated from each other by using the VLAN IDs. VLAN priorities are configured on each BTS according to service types. The functions of detecting looped services and suppressing broadcast packets need to be provided on the network.
l l
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured for service transmission on each NE; in addition, the functions of detecting looped services and suppressing broadcast packets, and QoS processing are configured. Figure 7-29 Networking diagram (IEEE 802.1q bridge-based E-LAN services)
BTS12 VLAN 100 FE R4 NE14 1 VLAN 100
BTS11 VLAN 100
FE GE
R4
Packet network NE13 2 VLAN 110 FE NE16 R4 BTS15 VLAN 110 NE15 NE12 NE11
The connections of Ethernet links shown in Figure 7-29 are described as follows. Table 7-112 Connections of Ethernet links (NE12) Link Between NE12 and NE13 Port 1-EM6T-1 Port Description Description Configure these ports to transmit backhaul services from BTSs.
7-158
Issue 03 (2011-04-10)
Port 3-ISU2-1
Port Description Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group -
Description Configure this port to transmit Native Ethernet services on Hybrid radio.
5-ISU2-1
1-EM6T-3
5-ISU2-1
4-ISU2-1
6-ISU2-1
1-EM6T-1
5-ISU2-1
Issue 03 (2011-04-10)
7-159
Link Between NE14 and BTS12
Port 1-EM6T-3
Port Description -
Description Configure this port to access services from BTS12.
4-ISU2-1
6-ISU2-1
1-EM6T-3

You need to plan the corresponding parameter information before service configuration. 7.7.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.7.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.7.2.3 Service Planning (Ethernet Services)
The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.7.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.


Table 7-117 to Table 7-120 provide the information about the Ethernet ports that transmit the Ethernet services. Table 7-117 Information about Ethernet ports (NE12) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute Enabling broadcast packet suppression Broadcast packet suppression threshold 1-EM6T-1 802.1q Auto-negotiation 1536 Disabled Tag aware Enabled 30 1-EM6T-3 802.1q Auto-negotiation 1536 Disabled Tag aware Enabled 30
Table 7-118 Information about Ethernet ports (NE13) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute Enabling broadcast packet suppression Broadcast packet suppression threshold 1-EM6T-1 802.1q Auto-negotiation 1536 Disabled Tag aware Enabled 30
Issue 03 (2011-04-10)
7-161
Table 7-119 Information about Ethernet ports (NE14) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Tag attribute Enabling broadcast packet suppression Broadcast packet suppression threshold 1-EM6T-3 802.1Q Auto-negotiation 1536 Disabled Tag aware Enabled 30
NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its default value of 1522. l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.

Table 7-121 to Table 7-125 provide the information about the IF_ETH ports that carry the Ethernet services.
7-162
Issue 03 (2011-04-10)
Table 7-121 Information about the IF_ETH port (NE12) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 5-ISU2-1 802.1q Tag aware
Table 7-122 Information about the IF_ETH port (NE13) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 5-ISU2-1 802.1q Tag aware 4-ISU2-1 802.1q Tag aware 6-ISU2-1 802.1q Tag aware
Table 7-123 Information about the IF_ETH port (NE14) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 5-ISU2-1 802.1q Tag aware
Table 7-124 Information about the IF_ETH port (NE15) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1q Tag aware 4-ISU2-1 802.1q Tag aware 6-ISU2-1 802.1q Tag aware
Table 7-125 Information about the IF_ETH port (NE16) Parameter Encapsulation type Tag attribute 3-ISU2-1 802.1Q Tag aware


The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-126 provides the planning information of IEEE 802.1q bridge-based E-LAN services. Table 7-126 Information about IEEE 802.1q bridge-based E-LAN services Parameter Service ID Service name Tag type Self-learning MAC address MAC address learning mode Mounted UNI port NE12 1 Qlan C-Awared Enabled NE13 1 Qlan C-Awared Enabled NE14 1 Qlan C-Awared Enabled NE15 1 Qlan C-Awared Enabled NE16 1 Qlan C-Awared Enabled
IVL
IVL
IVL
IVL
IVL
1-EM6T-1 (VLAN ID: 100, 110) 1-EM6T-3 (VLAN ID: 100) 3-ISU2-1 (VLAN ID: 100, 110)
3-ISU2-1 (VLAN ID: 100) 4-ISU2-1 (VLAN ID: 110) 1-EM6T-1 (VLAN ID: 100, 110)
3-ISU2-1 (VLAN ID: 100) 1-EM6T-3 (VLAN ID: 100)
3-ISU2-1 (VLAN ID: 110) 4-ISU2-1 (VLAN ID: 110)
3-ISU2-1 (VLAN ID: 110) 1-EM6T-3 (VLAN ID: 110)
NOTE
In this example, the split horizon group is not used.

QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 7-127. Each Ethernet port involved in the service uses the same DS configuration. Table 7-127 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF4 AF3
4 3
AF2
AF1 BE
1 0
NOTE

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 7-128 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 7-128 Queue scheduling mode PHB Service Class CS7
Issue 03 (2011-04-10)
Queue Scheduling Mode SP
7-165
PHB Service Class CS6 EF AF4 AF3 AF2 AF1 BE
Queue Scheduling Mode SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP

QoS (Port Shaping)


This section describes the process for data configuration. 7.7.3.1 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.7.3.2 Configuration Process (Ethernet Protection) In this example, Ethernet protection is not used. 7.7.3.3 Configuration Process (Service Information) This section describes the process for configuring service information. 7.7.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.7.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 1-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536 1-EM6T-3 Enabled Layer 2 802.1Q Auto-Negotiation 1536
l The values for the related parameters of NE13 are provided as follows. Parameter Value 1-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536
Issue 03 (2011-04-10)
7-167
Parameter
Value 1-EM6T-3
Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte)
Enabled Layer 2 802.1Q Auto-Negotiation 1536
Step 2 See A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 1-EM6T-1 TAG Tag Aware 1-EM6T-3 Tag Aware
l The values for the related parameters of NE13 are provided as follows. Parameter Value 1-EM6T-1 TAG Tag Aware
Step 3 See A.5.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows.
Parameter
Value 1-EM6T-1 1-EM6T-3 Enabled Enabled 30
Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold
Enabled Enabled 30
Step 4 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes of IF_ETH ports. l The values for the related parameters of NE12 are provided as follows.
Parameter
Value 3-ISU2-1 5-ISU2-1 Layer 2 802.1Q
Port Mode Encapsulation Type
Layer 2 802.1Q
l The values for the related parameters of NE13 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q 5-ISU2-1 Layer 2 802.1Q 4-ISU2-1 Layer 2 802.1Q 6-ISU2-1 Layer 2 802.1Q
l The values for the related parameters of NE14 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q 5-ISU2-1 Layer 2 802.1Q
l The values for the related parameters of NE15 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q 4-ISU2-1 Layer 2 802.1Q 6-ISU2-1 Layer 2 802.1Q
l The values for the related parameters of NE16 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q
Step 5 See A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributes of IF_ETH ports. l The values for the related parameters of NE12 are provided as follows.
Parameter
Value 3-ISU2-1 5-ISU2-1 Tag Aware
Tag
Tag Aware
l The values for the related parameters of NE13 are provided as follows. Parameter Value 3-ISU2-1 Tag Tag Aware 5-ISU2-1 Tag Aware 4-ISU2-1 Tag Aware 6-ISU2-1 Tag Aware
l The values for the related parameters of NE14 are provided as follows. Parameter Value 3-ISU2-1 Tag Tag Aware 5-ISU2-1 Tag Aware
l The values for the related parameters of NE15 are provided as follows. Parameter Value 3-ISU2-1 Tag Tag Aware 4-ISU2-1 Tag Aware 6-ISU2-1 Tag Aware
l The values for the related parameters of NE16 are provided as follows. Parameter Value 3-ISU2-1 Tag Tag Aware
Step 6 See A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port and set the advanced attributes of the IF_ETH ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 30 5-ISU2-1 Enabled 30
Issue 03 (2011-04-10)
7-171
l The values for the related parameters of NE13 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 5-ISU2-1 Enabled 4-ISU2-1 Enabled 6-ISU2-1 Enabled
30
30
30
30
l The values for the related parameters of NE14 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 30 5-ISU2-1 Enabled 30
30
30
30
l The values for the related parameters of NE16 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 30
----End


Procedure
Step 1 See A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services and configure the ELAN services. l Parameters of NE12 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Qlan C-Awared Enabled 1-EM6T-1 UNI 100, 110 Enabled Auto-Negotiation 802.1Q Tag Aware 1-EM6T-3 UNI 100 Enabled Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 UNI 100, 110 802.1Q Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-1 1-EM6T-3 3-ISU2-1 VLAN (1, 3-5) 100, 110 100 100, 110
Issue 03 (2011-04-10)
7-173
l Parameters of NE13 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Qlan C-Awared Enabled 1-EM6T-1 UNI 100, 110 Enabled Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 UNI 100 802.1Q Tag Aware 4-ISU2-1 UNI 110 802.1Q Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-1 3-ISU2-1 4-ISU2-1 VLAN (1, 3-5) 100, 110 100 110
l Parameters of NE14 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address
7-174
Value 1 Qlan C-Awared Enabled
Issue 03 (2011-04-10)
Parameter Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag
Value 1-EM6T-3 UNI 100 Enabled Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 UNI 100 802.1Q Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 3-ISU2-1 l Parameters of NE15 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Qlan C-Awared Enabled 3-ISU2-1 UNI 110 802.1Q Tag Aware 4-ISU2-1 UNI 110 802.1Q Tag Aware VLAN (1, 3-5) 100 100
Issue 03 (2011-04-10)
7-175
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 3-ISU2-1 4-ISU2-1 VLAN (1, 3-5) 110 110
l Parameters of NE16 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type VLAN Enable Port Working Mode Encapsulation Type Tag Value 1 Qlan C-Awared Enabled 1-EM6T-3 UNI 110 Enabled Auto-Negotiation 802.1Q Tag Aware 3-ISU2-1 UNI 110 802.1Q Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 3-ISU2-1 VLAN (1, 3-5) 110 110
----End

7-176
Issue 03 (2011-04-10)
Procedure
NOTE
The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11 AF21 AF31 AF41
Issue 03 (2011-04-10)
CVLAN 0 1 2 3 4
SVLAN Default value
IP DSCP Default value
7-177
PHB EF CS6 CS7
CVLAN 5 6 7
SVLAN
IP DSCP
MPLS EXP
NOTE
NOTE
l The values for the related parameters of NE12 are provided as follows. Port 1-EM6T-1 1-EM6T-3 3-ISU2-1 Packet Type CVLAN
l The values for the related parameters of NE13 are provided as follows. Port 3-ISU2-1 4-ISU2-1 1-EM6T-1 Packet Type CVLAN
l The values for the related parameters of NE14 are provided as follows. Port 3-ISU2-1 1-EM6T-3 Packet Type CVLAN
l The values for the related parameters of NE15 are provided as follows. Port 3-ISU2-1 4-ISU2-1 Packet Type CVLAN
7-178
Issue 03 (2011-04-10)
l The values for the related parameters of NE16 are provided as follows. Port 1-EM6T-3 3-ISU2-1 Packet Type CVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. l The values for the related parameters of NE12 to NE16 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes)
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. l The values for the related parameters of NE12 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-1 1-EM6T-3 3-ISU2-1
l The values for the related parameters of NE13 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1 1-EM6T-1
Parameter
Port
3-ISU2-1
l The values for the related parameters of NE15 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs for NE12, NE14, and NE16. The values for the required parameters are provided as follows. Parameter Value NE12 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE14 EdgeNE 4 NE16 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create the MAs for NE12, NE14, and NE16. l The values for the related parameters of NE12 are provided as follows.
7-180
Issue 03 (2011-04-10)
Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period
Value EdgeNE BTS11_Qlan 1-Qlan 1s EdgeNE BTS12_Qlan 1-Qlan 1s EdgeNE BTS15_Qlan 1-Qlan 1s
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS12_Qlan 1-Qlan 1s
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE BTS15_Qlan 1-Qlan 1s
Step 3 See A.6.8.3 Creating an MEP Point and create the MEPs for NE12, NE14, and NE16. l The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN Value EdgeNE BTS11_Qlan EdgeNE BTS11_Qlan EdgeNE BTS12_Qlan EdgeNE BTS15_Qlan
1-EM6T 1-EM6T-3 100
3-ISU2 3-ISU2-1 100
3-ISU2 3-ISU2-1 100
3-ISU2 3-ISU2-1 110
Issue 03 (2011-04-10)
7-181
Parameter MP ID Direction CC Status AIS Active Status
Value 201 Ingress Active Active 200 Ingress Active Active 202 Ingress Active Active 205 Ingress Active Active
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS12_Qlan 1-EM6T-3 1-EM6T-3 110 401 Ingress Active Active
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE BTS15_Qlan 1-EM6T 1-EM6T-3 120 601 Ingress Active Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE12, NE14, and NE16.
The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS11_Qlan 201 EdgeNE BTS12_Qlan 401 EdgeNE BTS15_Qlan 601
The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS12_Qlan 202
The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE BTS15_Qlan 205
Step 5 On NE12, perform LB tests to test the Ethernet service configurations. l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 202 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 205 as the source MEP and the MEP whose MEP ID is 601 as the sink MEP. There should be no packet lost during the LB tests. ----End
Issue 03 (2011-04-10)
7-183
7.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service)

This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how to configure the Ethernet service according to the network planning information. 7.8.1 Networking Diagram This section describes the networking information about the NEs. 7.8.2 Service Planning You need to plan the corresponding parameter information before service configuration. 7.8.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network), configure Ethernet services according to the following requirements: l l l l BTS11 to BTS14 provide FE ports whose port rate is 100 Mbit/s. The RNC provides GE ports whose port rate is 1000 Mbit/s. The VLAN ID used by the services on a BTS is allocated by the RNC that controls the BTS. The VLAN IDs of services on BTSs that are controlled by different RNCs may be the same. Therefore, the transport network allocates an S-VLAN ID for services from the BTSs controlled by the same RNC, and the S-VLAN IDs on the entire network are planned in a unified manner. The Ethernet services on the ring network are protected. VLAN priorities are configured on each BTS according to service types. The functions of detecting looped services and suppressing broadcast packets need to be provided on the network.
l l l
To meet the preceding requirements, IEEE 802.1ad bridge based E-LAN services are configured to implement transmission of the BTS services; in addition, the functions of detecting looped services and suppressing broadcast packets, ERPS protection, and QoS processing are configured. See Figure 7-30.
7-184
Issue 03 (2011-04-10)
Figure 7-30 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)

RNC1 BTS11 CVLAN 100 SVLAN 200 FE R4 NE22 802.1ad bridge ERPS NE24 802.1ad bridge NE21 802.1ad bridge GE GE BTS14 CVLAN 100 SVLAN 201 FE R4 RNC2
FE NE23 802.1ad bridge R4 BTS13 CVLAN 110 SVLAN 200
The connections of Ethernet links shown in Figure 7-30 are described as follows. Table 7-129 Connections of Ethernet links (NE21) Link Between NE21 and RNC1 Between NE21 and RNC2 Between NE21 and NE22 Port 1-EM6T-1 Port Description Description Configure this port to transmit backhaul services from BTSs. Configure this port to transmit backhaul services from BTSs. Configure this port to transmit Native Ethernet services on Hybrid radio. Configure these ports to transmit Native Ethernet services on Hybrid radio.
1-EM6T-2
4-ISU2-1
East port of an ERPS ring node
3-ISU2-1
Main IF board of a 1 +1 SD protection group West port of an ERPS ring node Standby IF board of a 1+1 SD protection group
5-ISU2-1
Issue 03 (2011-04-10)
7-185
Table 7-130 Connections of Ethernet links (NE22) Link Between NE22 and NE23 Port 4-ISU2-1 Port Description East port of an ERPS ring node Description Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to access services from BTS21. Configure this port to transmit Ethernet services on Hybrid radio.
Between NE22 and BTS21 Between NE22 and NE21
1-EM6T-3
3-ISU2-1
Table 7-131 Connections of Ethernet links (NE23) Link Between NE23 and NE24 Port 4-ISU2-1 Port Description l East port of an ERPS ring node l RPL port Between NE23 and BTS23 Between NE23 and NE22 1-EM6T-3 Description Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to access services from BTS23. Configure this port to transmit Ethernet services on Hybrid radio.
3-ISU2-1
Table 7-132 Connections of Ethernet links (NE24) Link Between NE24 and NE21 Port 4-ISU2-1 Port Description East port of an ERPS ring node Main IF board of a 1 +1 SD protection group 6-ISU2-1 Standby IF board of a 1+1 SD protection group Description Configure these ports to transmit Ethernet services on Hybrid radio.
7-186
Issue 03 (2011-04-10)
Link Between NE24 and BTS24 Between NE24 and NE23
Port 1-EM6T-3
Port Description -
Description Configure this port to access services from BTS24. Configure this port to transmit Ethernet services on Hybrid radio.
3-ISU2-1

You need to plan the corresponding parameter information before service configuration. 7.8.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.8.2.2 Service Planning (Ethernet Protection) The service planning information contains the information about all the parameters required for configuring Ethernet protection. 7.8.2.3 Service Planning (Ethernet Services) The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.8.2.4 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring QoS.


Table 7-133 to Table 7-136 provide the information about the Ethernet ports that transmit the Ethernet services. Table 7-133 Information about Ethernet ports (NE21) Parameter Encapsulation type Port working mode Maximum frame length (byte)
Issue 03 (2011-04-10)
1-EM6T-1 802.1q Auto-negotiation 1536
1-EM6T-2 802.1q Auto-negotiation 1536
7-187
Parameter Flow control Tag attribute Enabling broadcast packet suppression Broadcast packet suppression threshold
1-EM6T-1 Disabled Tag aware Enabled 30
1-EM6T-2 Disabled Tag aware Enabled 30
7-188
Issue 03 (2011-04-10)
NOTE
l In this example, the FE/GE ports on all the BTSs/RNC work in auto-negotiation mode. Therefore, the FE/ GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame.

Table 7-137 to Table 7-140 provide the information about the IF_ETH ports that carry the Ethernet services. Table 7-137 Information about the IF_ETH port (NE21) Parameter Encapsulation type QinQ type domain 3-ISU2-1 QinQ 0x88a8 5-ISU2-1 QinQ 0x88a8 4-ISU2-1 QinQ 0x88a8
Issue 03 (2011-04-10)
7-189
Table 7-140 Information about the IF_ETH port (NE24) Parameter Encapsulation type QinQ type domain 3-ISU2-1 802.1q 0x88a8 4-ISU2-1 802.1q 0x88a8 6-ISU2-1 802.1q 0x88a8
NOTE
All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you set the QinQ type domain to 0x88a8 for the IF_ETH ports.

The service planning information contains the information about all the parameters required for configuring Ethernet protection.
Information about ERPS Instances

Table 7-141 provides the planning information about ERPS instances. Table 7-141 Information about ERPS instances Parameter ERPS ID East port West port RPL owner ring node flag RPL port Control VLAN Packet transmit interval Entity level NE21 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value) NE22 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value) NE23 1 4-ISU2-1 3-ISU2-1 Yes 4-ISU2-1 4093 5s (default value) 4 (default value) NE24 1 4-ISU2-1 3-ISU2-1 No 4093 5s (default value) 4 (default value)
7-190
Issue 03 (2011-04-10)
Parameter WTR time Guard time Hold-off time
NE21 500 ms (default value) 0s (default value)
NE23 5 minutes (default value) 500 ms (default value) 0s (default value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link is relatively even. l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control VLAN use VLAN 4093. l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their default values.

The service planning information contains the information about all the parameters required for configuring Ethernet services. Table 7-142 provides the planning information of IEEE 802.1ad bridge-based E-LAN services. Table 7-142 Information about IEEE 802.1ad bridge-based E-LAN services Parameter Service ID Service name Tag type Self-learning MAC address MAC address learning mode Mounted UNI port NE21 1 ADlan S-Awared Enabled IVL 1-EM6T-3 (CVLAN ID: 100, 110) (S-VLAN ID: 200) 1-EM6T-4 (CVLAN ID: 100) (S-VLAN ID: 201) NE22 1 ADlan S-Awared Enabled IVL 1-EM6T-3 (CVLAN ID: 100) (S-VLAN ID: 200) NE23 1 ADlan S-Awared Enabled IVL 1-EM6T-3 (CVLAN ID: 110) (S-VLAN ID: 200) NE24 1 ADlan S-Awared Enabled IVL 1-EM6T-3 (CVLAN ID: 100) (S-VLAN ID: 201)
Issue 03 (2011-04-10)
7-191
Parameter Mounted NNI port
NE21 3-ISU2-1 (SVLAN ID: 200, 201) 4-ISU2-1 (SVLAN ID: 200, 201)

QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 7-143. Each Ethernet port involved in the service uses the same DS configuration. Table 7-143 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) -
AF4 AF3
4 3
AF2
AF1
7-192
Issue 03 (2011-04-10)
PHB Service Class BE
VLAN Priority 0
Corresponding Service Type HSDPA data service (HSPA interactive and background services)
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority and therefore needs to be modified as required.


QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the aggregation services, you can perform port shaping at the edge node to limit the Ethernet
service traffic that travels to the aggregation node, thus preventing congestion at the aggregation node. In this example, you do not need to perform port shaping.

This section describes the process for data configuration. 7.8.3.1 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.8.3.2 Configuration Process (Ethernet Protection) This section describes the process for configuring Ethernet protection. 7.8.3.3 Configuration Process (Service Information) This section describes the process for configuring service information. 7.8.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.8.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of Ethernet ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536 1-EM6T-2 Enabled Layer 2 802.1Q Auto-Negotiation 1536
l The values for the related parameters of NE22 are provided as follows. Parameter Value 1-EM6T-3 Enable Port
7-194
Enabled
Issue 03 (2011-04-10)
Parameter
Value 1-EM6T-3
Port Mode Encapsulation Type Working Mode Max Frame Length(byte)
Layer 2 802.1Q Auto-Negotiation 1536
Step 2 See A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of Ethernet ports. The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6T-1 TAG Tag Aware 1-EM6T-2 Tag Aware
Issue 03 (2011-04-10)
7-195
The values for the related parameters of NE22 are provided as follows. Parameter Value 1-EM6T-3 TAG Tag Aware
Step 3 See A.5.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes of Ethernet ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6T-1 Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled Enabled 30 1-EM6T-2 Enabled Enabled 30
l The values for the related parameters of NE22 and NE24 are provided as follows. Parameter Value 1-EM6T-3 Loopback Check Enabling Broadcast Packet Suppression Enabled Enabled
7-196
Issue 03 (2011-04-10)
Parameter
Value 1-EM6T-3
Broadcast Packet Suppression Threshold
30
Step 4 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the attributes of the IF_ETH ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 QinQ 4-ISU2-1 Layer 2 QinQ 5-ISU2-1 Layer 2 QinQ
l The values for the related parameters of NE22 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 QinQ 4-ISU2-1 Layer 2 QinQ
l The values for the related parameters of NE23 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 QinQ 4-ISU2-1 Layer 2 QinQ
Issue 03 (2011-04-10)
7-197
l The values for the related parameters of NE24 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 QinQ 4-ISU2-1 Layer 2 QinQ 6-ISU2-1 Layer 2 QinQ
Step 5 See A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port and set the advanced attributes of the IF_ETH ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 4-ISU2-1 Enabled 5-ISU2-1 Enabled
30
30
30
l The values for the related parameters of NE22 and NE23 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 30 4-ISU2-1 Enabled 30
30
30
30
----End

Procedure
Step 1 See A.6.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance. The values for the required parameters are provided as follows. Parameter Value NE21 ERPS ID East Port West Port RPL Owner Ring Node Flag RPL Port Control VLAN 1 4-ISU2-1 3-ISU2-1 No 4093 NE22 1 4-ISU2-1 3-ISU2-1 No 4093 NE23 1 4-ISU2-1 3-ISU2-1 Yes 4-ISU2-1 4093 NE24 1 4-ISU2-1 3-ISU2-1 No 4093
----End

Procedure
Step 1 See A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services and configure the E-LAN services. l Parameters of NE21 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type
Issue 03 (2011-04-10)
Value 1 ADlan S-Awared Enabled 3-ISU2-1 NNI 4-ISU2-1 NNI 1-EM6T-1 UNI 1-EM6T-1 UNI
7-199
Parameter C-VLAN S-VLAN Enable Port Working Mode Encapsulation Type Tag
Value Blank 200, 201 QinQ Tag Aware Blank 200, 201 QinQ Tag Aware 100, 110 200 Enabled Autonegotiation 802.1Q Tag Aware 100 201 Enabled Autonegotiation 802.1Q Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-1 1-EM6T-2 Port Type UNI (Port+CVLAN+S-VLAN) UNI (Port+CVLAN+S-VLAN) C-VLAN 100, 110 100 S-VLAN 200 201
The values for the related parameters that need to be set in the Get NNI Port tab page are provided as follows. Port 3-ISU2-1 4-ISU2-1 Port Type NNI NNI C-VLAN S-VLAN 200, 201 200, 201
l Parameters of NE22 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port
7-200
Value 1 ADlan S-Awared Enabled 1-EM6T-3 3-ISU2-1 4-ISU2-1

Issue 03 (2011-04-10)
Parameter Port Type C-VLAN S-VLAN Enable Port Working Mode Encapsulation Type Tag
Value UNI 100 200 Enabled Auto-Negotiation 802.1Q Tag Aware NNI Blank 200, 201 QinQ Tag Aware NNI Blank 200, 201 QinQ Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 Port Type UNI (Port+CVLAN+S-VLAN) C-VLAN 100 S-VLAN 200
l Parameters of NE23 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type
Issue 03 (2011-04-10)
Value 1 ADlan S-Awared Enabled 1-EM6T-3 UNI 3-ISU2-1 NNI 4-ISU2-1 NNI
7-201
Parameter C-VLAN S-VLAN Enable Port Working Mode Encapsulation Type Tag
Value 110 200 Enabled Auto-Negotiation 802.1Q Tag Aware Blank 200, 201 QinQ Tag Aware Blank 200, 201 QinQ Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 Port Type UNI (Port+CVLAN+S-VLAN) C-VLAN S-VLAN 120
l Parameters of NE24 The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type C-VLAN
7-202
Value 1 ADlan S-Awared Enabled 1-EM6T-3 UNI 100 3-ISU2-1 NNI Blank 4-ISU2-1 NNI Blank
Issue 03 (2011-04-10)
Parameter S-VLAN Enable Port Working Mode Encapsulation Type Tag
Value 201 Enabled Auto-Negotiation 802.1Q Tag Aware 200, 201 QinQ Tag Aware 200, 201 QinQ Tag Aware
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-3 Port Type UNI (Port+CVLAN+S-VLAN) C-VLAN 100 S-VLAN 201
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and change the mapping relationships for the DS domain. The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
Issue 03 (2011-04-10)
7-203
The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN 0 1 2 3 4 5 6 7 SVLAN 0 1 2 3 4 5 6 7 IP DSCP Default value MPLS EXP Default value PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7 CVLAN 0 1 2 3 4 5 6 7 SVLAN 0 1 2 3 4 5 6 7 IP DSCP Default value MPLS EXP Default value
NOTE
Step 2 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet types. l The values for the related parameters of NE21 are provided as follows.
7-204
Issue 03 (2011-04-10)
Port 3-ISU2-1 4-ISU2-1 1-EM6T-1 1-EM6T-2
Packet Type SVLAN SVLAN CVLAN
l The values for the related parameters of NE22 are provided as follows. Port 1-EM6T-3 3-ISU2-1 4-ISU2-1 Packet Type CVLAN SVLAN SVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. l Parameters of NE21 to NE23 The values for the related parameters that need to be set in the main interface are as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Parameter Policy Weight(%)
Value 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the related parameters of NE21 to NE24 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs. The values for the required parameters are provided as follows. Parameter Value NE21 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE22 EdgeNE 4 NE23 EdgeNE 4 NE24 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create an MA. The values for the required parameters are provided as follows.
7-206
Issue 03 (2011-04-10)
Parameter
Value NE21 NE22 EdgeNE ADlan NE23 EdgeNE ADlan NE24 EdgeNE ADlan
Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period
EdgeNE ADlan
1-ADlan 1s
1-ADlan 1s
1-ADlan 1s
1-ADlan 1s
Step 3 See A.6.8.3 Creating an MEP Point and create MEPs. l The values for the related parameters of NE21 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE ADlan 1-EM6T 1-EM6T-1 100 101 Ingress Active Active EdgeNE ADlan 1-EM6T 1-EM6T-1 110 103 Ingress Active Active EdgeNE ADlan 1-EM6T 1-EM6T-2 100 104 Ingress Active Active
l The values for the related parameters of NE22 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN
Issue 03 (2011-04-10)
Value EdgeNE ADlan 1-EM6T 1-EM6T-3 100
7-207
l The values for the related parameters of NE23 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE ADlan 1-EM6T 1-EM6T-3 110 301 Ingress Active Active
l The values for the related parameters of NE24 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE ADlan 1-EM6T 1-EM6T-3 100 401 Ingress Active Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs. The values for the related parameters of NE21 are provided as follows.
Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6)
Value EdgeNE ADlan 201 EdgeNE ADlan 301 EdgeNE ADlan 401
The values for the related parameters of NE22 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE ADlan 101
Step 5 Perform LB tests to verify Ethernet service configurations. l Perform the LB test by considering the MEP whose MEP ID is 101 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 103 as the source MEP and the MEP whose MEP ID is 301 as the sink MEP.
l Perform the LB test by considering the MEP whose MEP ID is 104 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. There should be no packet lost during the LB tests. ----End
7.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)
This section describes how to configure a radio network that transmits E-Line services and ELAN services at the same time according to the network planning information. 7.9.1 Networking Diagram This section describes the networking information about the NEs. 7.9.2 Service Planning You need to plan the corresponding parameter information before service configuration. 7.9.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure Ethernet services according to the following requirements: l l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s. It is unknown whether the Ethernet services on each BTS carry a VLAN ID or whether the carried VLAN IDs conflict. Therefore, in this example, the point-to-point transparently transmitted E-Line services are configured to implement point-to-point transparent service transmission, and the IEEE 802.1d bridge-based E-LAN services are configured to implement service convergence. DSCP values are configured on each BTS according to service types. The BTSs need not communicate with each other.
l l
7-210
Issue 03 (2011-04-10)
Figure 7-31 Networking diagram

BTS12 FE R4 GE NE14 NE13 NE12 FE NE11 R4 FE NE15 R4 BTS15 Point-to-point transparently transmitted E-Line service IEEE 802.1d bridge Split horizon group BTS11 PSN
NE16
The connections of Ethernet links shown in Figure 7-31 are described as follows. Table 7-145 Connections of Ethernet links (NE12) Link Between NE12 and NE13 Between NE12 and NE11 Port 1-EM6T-1 Port Description Description Configure these ports to transmit backhaul services from BTSs. Configure this port to transmit Native Ethernet services on Hybrid radio.
3-ISU2-1
Main IF board of a 1 +1 HSB protection group Standby IF board of a 1+1 HSB protection group -
5-ISU2-1
1-EM6T-3
Issue 03 (2011-04-10)
7-211
5-ISU2-1
4-ISU2-1
6-ISU2-1
1-EM6T-1
5-ISU2-1
1-EM6T-3
Configure this port to access services from BTS12.
Table 7-148 Connections of Ethernet links (NE15) Link Between NE15 and NE16 Port 3-ISU2-1 Port Description Description Configure this port to transmit Native Ethernet services on Hybrid radio. Configure this port to transmit Native
4-ISU2-1
Main IF board of a 1 +1 HSB protection group
7-212
Issue 03 (2011-04-10)
Link
Port 6-ISU2-1
Port Description Standby IF board of a 1+1 HSB protection group
Description Ethernet services on Hybrid radio.
1-EM6T-3

You need to plan the corresponding parameter information before service configuration. 7.9.2.1 Service Planning (Ethernet Ports) The service planning information contains the information about all the parameters required for configuring Ethernet ports. 7.9.2.2 Service Planning (Ethernet Protection) In this example, Ethernet protection is not used. 7.9.2.3 Service Planning (Ethernet Services) The service planning information contains the information about all the parameters required for configuring Ethernet services. 7.9.2.4 Service Planning (QoS) This section provides the information about all the parameters required for configuring QoS.


Table 7-150 to Table 7-153 provide the information about the Ethernet ports that transmit the Ethernet services.
Issue 03 (2011-04-10)
7-213
Table 7-150 Information about Ethernet ports (NE12) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control Enabling broadcast packet suppression Broadcast packet suppression threshold 1-EM6T-3 Null Auto-negotiation 1536 Disabled Enabled 30 1-EM6T-1 Null Auto-negotiation 1536 Disabled Enabled 30
Table 7-152 Information about Ethernet ports (NE14) Parameter Encapsulation type Port working mode Maximum frame length (byte) Flow control 1-EM6T-3 Null Auto-negotiation 1536 Disabled
Table 7-153 Information about Ethernet ports (NE16) Parameter Encapsulation type
7-214
1-EM6T-3 Null
Issue 03 (2011-04-10)
Parameter Port working mode Maximum frame length (byte) Flow control
1-EM6T-3 Auto-negotiation 1536 Disabled
NOTE
l In this example, the planned encapsulation type is null because whether the Ethernet services on each BTS carry a VLAN ID or whether the carried VLAN IDs conflict is unknown. l In this example, the FE/GE ports on all the BTSs/BSC work in the auto-negotiation mode. Therefore, the FE/GE port of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are planned as auto-negotiation. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its default value of 1522. l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.

Table 7-154 to Table 7-158 provide the information about the IF_ETH ports that carry the Ethernet services. Table 7-154 Information about the IF_ETH port (NE12) Parameter Encapsulation type 3-ISU2-1 Null 5-ISU2-1 Null
Table 7-155 Information about the IF_ETH port (NE13) Parameter Encapsulation type 3-ISU2-1 Null 5-ISU2-1 Null 4-ISU2-1 Null 6-ISU2-1 Null
Issue 03 (2011-04-10)
7-215
Table 7-157 Information about the IF_ETH port (NE15) Parameter Encapsulation type 3-ISU2-1 Null 4-ISU2-1 Null 6-ISU2-1 Null
Table 7-158 Information about the IF_ETH port (NE16) Parameter Encapsulation type 3-ISU2-1 Null


The service planning information contains the information about all the parameters required for configuring Ethernet services.
Information About Point-to-Point Transparently Transmitted E-Line Services

Point-to-point transparently transmitted E-Line services need to be configured on NE14, NE15, and NE16. Table 7-159 to Table 7-161 provide the planning information of the E-Line services. Table 7-159 Information about point-to-point transparently transmitted E-Line services (NE14) Parameter NE14 BTS12 to NE13 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 BTS12toNE13_Tline UNI-UNI Not transparently transmitted 3-ISU2-1 1-EM6F-3 -
7-216
Issue 03 (2011-04-10)
Table 7-160 Information about point-to-point transparently transmitted E-Line services (NE15) Parameter NE15 NE16 to NE13 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 NE16toNE13_Tline UNI-UNI Not transparently transmitted 3-ISU2-1 4-ISU2-1 -
Table 7-161 Information about point-to-point transparently transmitted E-Line services (NE16) Parameter NE16 BTS15 to NE15 Service ID Service name Service direction BPDU Source port Source C-VLANs Sink port Sink C-VLANs 1 BTS15toNE15_Tline UNI-UNI Not transparently transmitted 1-EM6F-3 3-ISU2-1 -
Information About IEEE 802.1d Bridge-Based E-LAN Services

IEEE 802.1d bridge-based E-LAN services need to be configured on NE12 and NE13, where VLAN IDs may conflict. In addition, the split horizon group needs to be configured for preventing the BTSs from communicating with each other. Table 7-162 and Table 7-163 provide the planning information of the IEEE 802.1d bridge-based E-LAN services.
Issue 03 (2011-04-10)
7-217
Table 7-162 Information about IEEE 802.1d bridge-based E-LAN services (NE12) Parameter Service ID Service name Tag type Self-learning MAC address Mounted UNI port NE12 1 Dlan Tag-Transparent Enabled 1-EM6T-1 1-EM6T-3 3-ISU2-1 Split horizon group 1-EM6T-1 1-EM6T-3
Table 7-163 Information about IEEE 802.1d bridge-based E-LAN services (NE13) Parameter Service ID Service name Tag type Self-learning MAC address Mounted UNI port NE3 1 Dlan Tag-Transparent Enabled 1-EM6T-1 3-ISU2-1 4-ISU2-1 Split horizon group 3-ISU2-1 4-ISU2-1

This section provides the information about all the parameters required for configuring QoS.
QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated according to the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding DSCP values according to the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 7-164. Each Ethernet port involved in the service uses the same DS configuration. Table 7-164 Service class and PHB service class PHB Service Class CS7 CS6 EF DSCP 56 48 40 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF4 AF3
32 24
AF2
16
AF1 BE
8 0
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. l The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type needs to be modified for service-associated Ethernet ports applied in the default DS domain.

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 7-165 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 7-165 Queue scheduling mode PHB Service Class CS7
Issue 03 (2011-04-10)
Queue Scheduling Mode SP
7-219
PHB Service Class CS6 EF AF4 AF3 AF2 AF1 BE
Queue Scheduling Mode SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP

QoS (Port Shaping)


This section describes the process for data configuration. 7.9.3.1 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 7.9.3.2 Configuration Process (Ethernet Protection) In this example, Ethernet protection is not used. 7.9.3.3 Configuration Process (Service Information) This section describes the process for configuring service information. 7.9.3.4 Configuration Process (QoS) This section describes the procedures for configuring QoS. 7.9.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 1-EM6T-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 Null Auto-Negotiation 1536 1-EM6T-1 Enabled Layer 2 Null Auto-Negotiation 1536
Issue 03 (2011-04-10)
7-221
Parameter
Value 1-EM6T-3
Enabled Layer 2 Null Auto-Negotiation 1536
Step 2 See A.5.6.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes of Ethernet ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 1-EM6T-3 Loopback Check Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled Enabled 30 1-EM6T-1 Enabled Enabled 30
Step 3 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes of IF_ETH ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type
7-222
5-ISU2-1 Layer 2 Null

Issue 03 (2011-04-10)
Layer 2 Null
l The values for the related parameters of NE13 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null 5-ISU2-1 Layer 2 Null 4-ISU2-1 Layer 2 Null 6-ISU2-1 Layer 2 Null
l The values for the related parameters of NE14 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null 5-ISU2-1 Layer 2 Null
l The values for the related parameters of NE15 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null 4-ISU2-1 Layer 2 Null 6-ISU2-1 Layer 2 Null
l The values for the related parameters of NE16 are provided as follows. Parameter Value 3-ISU2-1 Port Mode Encapsulation Type Layer 2 Null
Step 4 See A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port and set the advanced attributes of the IF_ETH ports. l The values for the related parameters of NE12 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression
Issue 03 (2011-04-10)
5-ISU2-1 Enabled
Enabled
7-223
Parameter
Value 3-ISU2-1 5-ISU2-1 30
30
l The values for the related parameters of NE13 are provided as follows. Parameter Value 3-ISU2-1 Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Enabled 5-ISU2-1 Enabled 4-ISU2-1 Enabled 6-ISU2-1 Enabled
30
30
30
30
----End


Procedure
Step 1 See A.6.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services on NE14 to NE16. l The values for the related parameters of NE14 are provided as follows. Parameter Value BTS12 to NE13 Service ID Service Name Direction Source Interface Source VLAN ID
7-224
1 BTS12toNE13_Tline UNI-UNI 3-ISU2-1 Issue 03 (2011-04-10)
Parameter
Value BTS12 to NE13
Sink Interface Sink VLAN ID Port Name Enable Port Working Mode Encapsulation Type
1-EM6F-3 1-EM6F-3 Enabled Auto-Negotiation Null 3-ISU2-1 Null
l The values for the related parameters of NE15 are provided as follows. Parameter Value NE16 to NE13 Service ID Service Name Direction Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Working Mode Encapsulation Type 1 NE16toNE13_Tline UNI-UNI 3-ISU2-1 4-ISU2-1 3-ISU2-1 Null 4-ISU2-1 Null
l The values for the related parameters of NE16 are provided as follows. Parameter Value BTS15 to NE15 Service ID Service Name Direction Source Interface 1 BTS15toNE15_Tline UNI-UNI 1-EM6F-3
Issue 03 (2011-04-10)
7-225
Parameter
Value BTS15 to NE15
Source VLAN ID Sink Interface Sink VLAN ID Port Name Enable Port Working Mode Encapsulation Type
3-ISU2-1 1-EM6F-3 Enabled Auto-Negotiation Null 3-ISU2-1 Null
Step 2 See A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the ELAN services on NE12 and NE13. The values for the related parameters of NE12 that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type Enable Port Working Mode Encapsulation Type Value 1 Dlan Tag-Transparent Enabled 1-EM6T-1 UNI Enabled Auto-Negotiation Null 1-EM6T-3 UNI Enabled Auto-Negotiation Null 3-ISU2-1 UNI Null
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-1 1-EM6T-3
7-226
Issue 03 (2011-04-10)
Port 3-ISU2-1
The values for the related parameters that need to be set in the Split Horizon Group tab page are provided as follows. Split Horizon Group ID 1 Split Horizon Group Member 1-EM6T-1, 1-EM6T-3
The values for the related parameters of NE13 that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Tag Type Self-Learning MAC Address Port Port Type Enable Port Working Mode Encapsulation Type Value 1 Dlan Tag-Transparent Enabled 1-EM6T-1 UNI Enabled Auto-Negotiation Null 3-ISU2-1 UNI Null 4-ISU2-1 UNI Null
The values for the related parameters that need to be set in the Get UNI Port tab page are provided as follows. Port 1-EM6T-1 3-ISU2-1 4-ISU2-1
The values for the related parameters that need to be set in the Split Horizon Group tab page are provided as follows.
Split Horizon Group ID 1
Split Horizon Group Member 3-ISU2-1, 4-ISU2-1
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and change the mapping relationships for the DS domain. The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN Default value SVLAN Default value IP DSCP 0 8 16 24 32 40 48 56 MPLS EXP Default value PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows.
7-228
Issue 03 (2011-04-10)
PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
CVLAN Default value
SVLAN Default value
IP DSCP 0 8 16 24 32 40 48 56
NOTE
Step 2 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet types. l The values for the related parameters of NE12 are provided as follows. Port 1-EM6T-3 1-EM6T-1 3-IFU2-1 Packet Type ip-dscp
l The values for the related parameters of NE13 are provided as follows. Port 3-IFU2-1 4-IFU2-1 1-EM6T-1 Packet Type ip-dscp
l The values for the related parameters of NE14 are provided as follows. Port 3-IFU2-1 1-EM6T-3 Packet Type ip-dscp
Port 3-IFU2-1 4-IFU2-1
Packet Type ip-dscp
l The values for the related parameters of NE16 are provided as follows. Port 1-EM6T-3 3-IFU2-1 Packet Type ip-dscp
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. l The values for the related parameters of NE12 to NE16 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes)
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. l The values for the related parameters of NE12 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6T-1 1-EM6T-3 3-ISU2-1 l The values for the related parameters of NE13 are provided as follows.
7-230
Issue 03 (2011-04-10)
Parameter
Port
3-ISU2-1 4-ISU2-1 1-EM6T-1
l The values for the related parameters of NE15 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-ISU2-1
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and configure the MD for NE12, NE14, and NE16. The values for the related parameters are provided as follows. Parameter Value NE12 Maintenance Domain Name
Issue 03 (2011-04-10)
NE14 EdgeNE
NE16 EdgeNE
EdgeNE
7-231
Parameter
Value NE12 NE14 4 NE16 4
Maintenance Domain Level
Step 2 See A.6.8.2 Creating an MA and create the MAs for NE12, NE14, and NE16. l The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE DlantoBTS 1-Dlan 1s EdgeNE DlantoBTS 1-Dlan 1s EdgeNE DlantoBTS 1-Dlan 1s
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE DlantoBTS 1-BTS12toNE13_Tline 1s
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period Value EdgeNE DlantoBTS 1-BTS15toNE15_Tline 1s
Step 3 See A.6.8.3 Creating an MEP Point and configure the MEPs for NE12, NE14, and NE16. l The values for the related parameters of NE12 are provided as follows.
7-232
Issue 03 (2011-04-10)
Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status
Value EdgeNE DlantoBTS 1-EM6T-3 1-EM6T-3 201 Ingress Active Active EdgeNE DlantoBTS 3-ISU2 3-ISU2-1 200 Ingress Active Active
l The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status AIS Active Status Value EdgeNE DlantoBTS 1-EM6T-3 1-EM6T-3 401 Ingress Active Active
l The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Board Port VLAN Value EdgeNE DlantoBTS 1-EM6T 1-EM6T-3 -
Issue 03 (2011-04-10)
7-233
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEP points for NE12, NE14, and NE16. The values for the related parameters of NE12 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE DlantoBTS 201 EdgeNE DlantoBTS 401 EdgeNE DlantoBTS 601
The values for the related parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE DlantoBTS 200
The values for the related parameters of NE16 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value EdgeNE DlantoBTS 200
Step 5 On NE12, perform LB tests to test the Ethernet service configurations.
7-234
Issue 03 (2011-04-10)
l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and the MEP whose MEP ID is 201 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and the MEP whose MEP ID is 401 as the sink MEP. l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and the MEP whose MEP ID is 601 as the sink MEP. There should be no packet lost during the LB tests. ----End
Issue 03 (2011-04-10)
7-235
Configuring EoPDH-Based Ethernet Services
About This Chapter

EoPDH-based Ethernet services are classified into EPL services, EVPL services, EPLAN services, and EVPLAN services. 8.1 Basic Concepts This section describes the basic concepts that are related to EoPDH services. 8.2 Configuration Procedure The service configuration procedure differs according to the specific service type. 8.3 Configuration Example (Ethernet Services Based on TDM Radio) This section considers an Ethernet service based on TDM radio as an example to describe how to configure Ethernet services according to the service planning information. 8.4 Configuration Example (Ethernet Services Traversing a TDM Network) This section considers an Ethernet service traversing a TDM network as an example to describe how to configure Ethernet services according to the service planning information.
Issue 03 (2011-04-10)
8-1
8.1 Basic Concepts

This section describes the basic concepts that are related to EoPDH services. 8.1.1 What's the EoPDH Plane The EoPDH plane refers to the switching plane provided by the Ethernet switching unit on the EFP8 board. The EoPDH plane provides a wide range of services and features based on Native Ethernet. 8.1.2 VCTRUNK When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards. 8.1.3 Transmission Modes of Ethernet Services The OptiX RTN 950 supports two transmission modes of Ethernet services in EoPDH mode, namely, EoPDH and Hybrid radio. 8.1.4 Hub/Spoke In the case of convergence services, mutual access between non-central stations and central stations is needed but mutual access between non-central stations is not needed. Therefore, you need to specify a mounted port as a Hub port or a Spoke port. 8.1.5 EoPDH-Based Ethernet Services Based on the EoPDH mode, Ethernet services can be classified into six types.
8.1.1 What's the EoPDH Plane

The EoPDH plane refers to the switching plane provided by the Ethernet switching unit on the EFP8 board. The EoPDH plane provides a wide range of services and features based on Native Ethernet. As shown in Figure 8-1, the ports connecting to the EoPDH plane are classified into the following types: l l PORT on the EFP8 board, that is, the FE port on the EFP8 board VCTRUNK port on the EFP8 board, that is, the internal port on the EFP8 board The Ethernet packets on the EoPDH plane can be transmitted to the EoPDH encapsulating/ mapping module. Then, the packets are encapsulated into E1 services for transmission. l Bridging port (PORT9) connecting to the EoPDH plane on the EFP8 board The EFP8 board has two bridging ports: PORT9 and PORT10. PORT9 and PORT10 are two back-to-back internal GE ports, not having PHY-layer functions. PORT9 is connected to the EoPDH plane. The Ethernet services on the packet plane are transmitted to the FE port or VCTRUNK port on the EFP8 board through PORT9. PORT10 is connected to the packet plane. The Ethernet services on the packet plane are transmitted to the EoPDH plane through PORT10.
8-2
Issue 03 (2011-04-10)
Figure 8-1 EoPDH plane

FE PORT1 EFP8 EoPDH plane Packet plane System control, switching, and timing board
FE
PORT8
Ethernet switching unit GE
PORT9 PORT10
Packet switching unit
VCTRUNK1
GE
VCTRUNK16 VC-4 Crossconnect unit TDM plane
Encapsulating /Mapping unit
8.1.2 VCTRUNK
When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards. A VCTRUNK is a path that comprises virtual containers (VCs) and is also the internal port on an Ethernet board. In the case of EoPDH, multiple individual E1 channels are concatenated into a bigger virtual path for service transmission. The EFP8 is an EoPDH Ethernet board and provides VCTRUNKs binding E1 channelsa.
NOTE
a: On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
8.1.3 Transmission Modes of Ethernet Services

The OptiX RTN 950 supports two transmission modes of Ethernet services in EoPDH mode, namely, EoPDH and Hybrid radio.
EoPDH
In EoPDH mode, Ethernet services are encapsulated and mapped into E1 channels according to a corresponding encapsulation and mapping protocol, and are then transmitted over the SDH/ PDH network. The configurations for EoPDH transmission are similar to the configurations for EoS transmission. The OptiX RTN 950 provides the following transmission lines to implement EoPDH transmission: SDH optical line, E1 line, TDM radio link constructed by the IF1 boards, and E1 line constructed by the IFU2/IFX2 boards in Hybrid radio mode.
Hybrid Radio
The OptiX RTN 950 embeds the MADM and the packet processing platform. The MADM transmits E1 services that are received locally or extracted from the SDH services to the microwave port. The packet processing platform processes the received Ethernet services in a
unified manner and then transmits the Ethernet services to the microwave port. The microwave port maps the E1 services and the Ethernet services into Hybrid microwave frames and then transmits the Hybrid microwave frames. Figure 8-2 Hybrid radio
IDU E1 TDM cross-connect matrix Packet switching Native E1 and native Ethernet ODU Hybrid radio
Ethernet
8.1.4 Hub/Spoke
In the case of convergence services, mutual access between non-central stations and central stations is needed but mutual access between non-central stations is not needed. Therefore, you need to specify a mounted port as a Hub port or a Spoke port. l Hub port Hub ports can mutually access each other. Hub ports and Spoke ports can mutually access each other. l Spoke port Spoke ports cannot mutually access each other. Spoke ports and Hub ports can mutually access each other.
NOTE
A mounted port is a Hub port by default. During configuration, you can configure the mounted port of a central station to a Hub port, and configure the mounted port of a non-central station to a Spoke port. This can ensure that a central station can communicate with any non-central station, but non-central stations cannot communicate with each other.
8.1.5 EoPDH-Based Ethernet Services

Based on the EoPDH mode, Ethernet services can be classified into six types. 8.1.5.1 Point-to-Point Transparently Transmitted EPL Services In the case of EPL services, the source port transparently transmits all the received Ethernet packets to the sink port, and the services occupy the bandwidth exclusively. These services are point-to-point transparently transmitted EPL services. 8.1.5.2 EVPL Services Based on the VLAN VLANs can be used to separate EVPL services. With the VLAN technology, multiple EVPL services can share one physical channel. This type of EVPL services is called the EVPL service based on the VLAN. 8.1.5.3 QinQ-based EVPL Services
S-VLAN tags can be used to separate EVPL services. Thus, multiple EVPL services can share one physical channel. Such services are called QinQ-based EVPL services. 8.1.5.4 EPLAN Services Based on the 802.1D Bridge In the case of EPLAN services, packets can be forwarded only based on the MAC address table. This type of EPLAN services is called the EPLAN service based on the 802.1D bridge. 8.1.5.5 EVPLAN Services Based on the 802.1Q Bridge EVPLAN services can be separated by setting VLANs, and then a bridge is divided into multiple sub-switching domains. This type of EVPLAN services is called the EVPLAN service based on 802.1Q bridge. 8.1.5.6 EVPLAN Services Based on 802.1ad Bridge S-VLAN tags can be used to separate EVPLAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. Such services are called EVPLAN services based on 802.1ad bridge.
8.1.5.1 Point-to-Point Transparently Transmitted EPL Services

In the case of EPL services, the source port transparently transmits all the received Ethernet packets to the sink port, and the services occupy the bandwidth exclusively. These services are point-to-point transparently transmitted EPL services.
Service Model
Table 8-1 describes the point-to-point transparently transmitted EPL service model. Table 8-1 Point-to-point transparently transmitted EPL service model Traffic Flow PORT (source) PORT (sink) Network Attribute UNI (source) UNI (sink) Entry Detection Disabled (source) Disabled (sink) Description The source port transparently transmits all the received Ethernet frames to the sink port, and the sink port processes the Ethernet frames and sends out the Ethernet frames.
Typical Application
Figure 8-3 shows the typical application scenarios of the point-to-point transparently transmitted EPL service model. Ethernet service 1 gains access to NE1 through port 1, regardless of whether the Ethernet service carries an unknown VLAN ID or does not carry a VLAN ID. Port 1 processes the received packets and transparently transmits Ethernet service 1 to port 3. Port 3 then processes the received packets and transmits Ethernet service 1 to NE2. Service processing on NE2 is the same as on NE1. Figure 8-3 Typical application of the service model
NE 1 Port 1 Service 1 Port 3 Transmission network Port 3 NE 2 Port 1 Service 1
EPL
EPL
Issue 03 (2011-04-10)
8-5
8.1.5.2 EVPL Services Based on the VLAN

VLANs can be used to separate EVPL services. With the VLAN technology, multiple EVPL services can share one physical channel. This type of EVPL services is called the EVPL service based on the VLAN.
Service Model
Table 8-2 shows the models of the EVPL service based on the VLAN. Table 8-2 Models of the EVPL service based on the VLAN Service Model Model 1 Service Flow PORT (source) PORT (sink) Network Attribute UNI (source) UNI (sink) Ingress Check Enabled (source) Enabled (sink) Service Description The source port processes the incoming Ethernet frames based on its TAG attribute, and then sends the processed Ethernet frames to the sink port. The sink port processes the Ethernet frames based on its TAG attribute, and then sends the processed Ethernet frames. The source port processes the incoming Ethernet frames based on its TAG attribute, and then sends the Ethernet frames with a specific VLAN ID to the sink port. The sink port processes the Ethernet frames based on its TAG attribute, and then sends the processed Ethernet frames.
Model 2
PORT+VLAN (source) PORT+VLAN (sink)
UNI (source) UNI (sink)
Enabled (source) Enabled (sink)
Typical Applications
Figure 8-4 shows the typical application of service model 1. Ethernet Service 1 and Service 2 carry unknown VLAN IDs. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE2 through Port 2. Port 1 and Port 2, based on
their own TAG attributes, process the incoming packets. Then, Port 1 sends Service 1 to Port 3, and Port 2 sends Service 2 to Port 4. Port 3 and Port 4, based on their own TAG attributes, process the incoming packets. Then, Port 3 sends Service 1 to NE2, and Port 4 sends Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-4 Typical application of service model 1
NE 1 Port 1 Service 1 Service 2 Port 2 EVPL EVPL Port 4 Port 3 Transmission Network Port 3 NE 2 EVPL EVPL Port 4 Port 2 Port 1 Service 1 Service 2
NOTE
The application of service model 1 is similar to point-to-point transparent transmission of Ethernet services. The difference lies in that ports need to process packets based on their TAG attributes in the application of service model 1.
Figure 8-5 shows the typical application of service model 2. Service 1 and Service 2 carry different VLAN IDs. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. They share the transmission channel at Port 3 and are isolated by using VLANs. On NE1, Port 1 and Port 2, based on their own TAG attributes, process the incoming packets. Then, Port 1 sends Service 1 to Port 3, and Port 2 sends Service 2 to Port 3. Port 3, based on their own TAG attributes, processes the incoming packets, and then sends Service 1 and Service 2 to NE2. Service 1 and Service 2 carry different VLAN IDs, so they can be transmitted through Port 3 with separated from each other. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-5 Typical application of service model 2
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1 NE 2 Port 3 Transmission Network Port 3 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
EVPL
EVPL
EVP L
Port 1
Port 2
Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
EVP L
8.1.5.3 QinQ-based EVPL Services

S-VLAN tags can be used to separate EVPL services. Thus, multiple EVPL services can share one physical channel. Such services are called QinQ-based EVPL services.
Service Model
Table 8-3 shows a main service model of QinQ-based EVPL services.
Table 8-3 Main service model of QinQ-based EVPL services Service Model Model 1 Service Flow (Bidirectional) PORT (source) PORT+S-VLAN (sink) Network Attribute C-Aware (Source) S-Aware (Sink) Operation of Tag Adding S-VLAN tags (C-Aware port) Description of Service The source port adds S-VLAN tags to all the received Ethernet packets, and then transmits the packets to the sink port. The source port adds S-VLAN tags to all the received Ethernet packets that carry the specified C-VLAN tags, and then transmits the packets to the sink port. The source port transparently transmits the Ethernet packets that carry the specified S-VLAN tags to the sink port. The source port transmits the Ethernet packets that carry the specified S-VLAN tags to the sink port. If the source and sink QinQ links correspond to different S-VLAN tags, the S-VLAN tags carried in the Ethernet frames are switched.
Model 2
PORT+C-VLAN (source) PORT+C-VLAN +S-VLAN (sink)
C-Aware (Source) S-Aware (Sink)
Adding S-VLAN tags (C-Aware port)
Model 3
PORT+S-VLAN (source) PORT+S-VLAN (sink)
S-Aware (source) S-Aware (sink)
Transparently transmitting SVLAN tags (SAware port)
Model 4
PORT+S-VLAN (source) PORT+S-VLAN (sink)
S-Aware (source) S-Aware (sink)
Switching S-VLAN tags (S-Aware port)
Figure 8-6 shows the typical application of service model 1. Ethernet Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds
the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-6 Typical application of service model 1
NE 1 Port 1 Service 1 Service 2 Port 2
Strip S-VLAN Label Data( 1) Data(2)

EVPL
EVPL
EVP L
Port 1 Service 1 Service 2 Port 2
EVP L
Strip S-VLAN Label Data(1) Data(2)
Figure 8-7 shows the typical application of service model 2. Service 1 and Service 2 carry different VLAN IDs. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE 1 through Port 2. Port 1 adds the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-7 Typical application of service model 2
Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1

EVPL
EVPL
EVP L
Port 1
EVP
Port 2

Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
Figure 8-8 shows the typical application of service model 3. Service 1 and Service 2 carry different VLAN IDs. After Service 1 is accessed to NE1 through Port 1 and Service 2 is accessed to NE1 through Port 2, they share the same transmission channel
at Port 3 and are separated from each other through S-VLAN tags. On NE1, Port 1 and Port 2 transparently transmit Service 1 and Service 2 respectively to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. With the different S-VLAN tags, Service 1 and Service 2 can be transmitted through Port 3 at the same time. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-8 Typical application of service model 3
NE 1 Service 1 S-VLAN ID: 100 Service 2 S-VLAN ID: 200 Port 1 NE 2 Port 3 Transmission Network Port 3
EVPL
EVPL
EVP L
Port 1
Service 1 S-VLAN ID: 100 Service 2 S-VLAN ID: 200
Port 2
EVP
Port 2
Figure 8-9 shows the typical application of service model 4. Service 1 and Service 2 carry a same S-VLAN tag. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 changes the S-VLAN tag carried in Service 1 and Port 2 changes the S-VLAN tag carried in Service 2 so that the S-VLAN tags carried in Service 1 and Service 2 are different. Then, Port 1 and Port 2 transmit Service 1 and Service 2 to Port 3 respectively. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 8-9 Typical application of service model 4
NE 1 Service 1 S-VLAN ID: 100 Service 2 S-VLAN ID: 100 Port 1

E-Line
E-Line
e E-Lin
Port 1
Service 1 S-VLAN ID: 100
Port 2
E-Lin e
Service 2 Port 2 S-VLAN ID: 100
8.1.5.4 EPLAN Services Based on the 802.1D Bridge

In the case of EPLAN services, packets can be forwarded only based on the MAC address table. This type of EPLAN services is called the EPLAN service based on the 802.1D bridge.
Service Model
Table 8-4 shows the model of EPLAN services based on the 802.1D bridge. Table 8-4 Model of EPLAN services based on the 802.1D bridge Type of Service Service Flow Learning/ Switching Mode of a Bridge SVL/Ingress filter disable Attribute of a Mounted Port UNI Sub-Switching Domain No classification of sub-switching domains
EPLAN services based on the 802.1D bridge
PORT
Figure 8-10 shows a typical application based on the model of service. The transmission network needs to carry the A services accessed from NE2 and NE3. The two A services are aggregated at the convergence node NE1. The services need not be isolated. Therefore, an 802.1D bridge is used at NE1 to groom services. Figure 8-10 Model of EPLAN services based on the 802.1D bridge
NE 2
Port 2 NE 1 Transmission Network Port 2 Port 3 802.1d bridge Transmission Network NE 3
Port 1 User A2
Port 1 User A1
Port 2
Port 1 User A3
8.1.5.5 EVPLAN Services Based on the 802.1Q Bridge

EVPLAN services can be separated by setting VLANs, and then a bridge is divided into multiple sub-switching domains. This type of EVPLAN services is called the EVPLAN service based on 802.1Q bridge.
Service Model
Table 8-5 shows the models of EVPLAN services based on the 802.1Q bridge.
Table 8-5 Models of EVPLAN services based on the 802.1Q bridge Type of Service Service Flow Attribute of a Mounted Port UNI Learning/ Switching Mode of a Bridge IVL/Ingress filter enablea Sub-Switching Domain Division of subswitching domains based on VLANs
EVPLAN service based on the 802.1Q bridge
PORT+VLAN
NOTE
a: A VLAN filter table must be configured to check the VLAN tag. If a packet carries a VLAN ID different from the VLAN ID of the port specified in the VLAN filter table, the packet is discarded.
Figure 8-11 shows the typical application of the model of the EVPLAN service based on the 802.1Q bridge. The transmission network needs to carry G and H services accessed from NE2 and NE3. Both types of services are aggregated and switched on NE1. G and H services adopt different VLAN planning. Therefore, a 802.1Q bridge is used on NEs and sub-switching domains are divided based on VLANs, differentiating and separating the two types of services. Figure 8-11 Model of EVPLAN services based on the 802.1Q bridge
NE 2
VLAN 100
Port 1 User G2
NE 1 Port 1 User G1
VLAN 100
Port 3
VLAN 200
Transmission Network Port 3 802.1q bridge NE 3

VLAN 100
Port 2 User H2
Port 2 User H1
VLAN 200
Port 4 Transmission Network
802.1q bridge
VLAN 200
Port 1 User G3 Port 2 User H3
Port 3
802.1q bridge
NOTE
You can also configure 8.1.5.2 EVPL Services Based on the VLAN on NE2 and NE3 for service access.
8-12
Issue 03 (2011-04-10)
8.1.5.6 EVPLAN Services Based on 802.1ad Bridge

S-VLAN tags can be used to separate EVPLAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. Such services are called EVPLAN services based on 802.1ad bridge.
Model of Service
Table 8-6 lists the models of EVPLAN services based on 802.1ad bridge. Table 8-6 Models of EVPLAN services based on 802.1ad bridge Type of Service Model of Service Learning/ Switching Mode of a Bridge IVL/Ingress filter enable
a
Mount Port Attribute
Operation of Tag
SubSwitching Domain Division of subswitching domains based on S-VLAN tags
EVPLAN services based on 802.1ad bridge
Model 1
C-Aware port
Adding SVLAN tags based on PORT Adding SVLAN tags based on PORT and C-VLAN
S-Aware port
Mount Port and base for PORT and S-VLAN Adding SVLAN tags based on PORT Mount port No division of sub-switching domains
Model 2
SVL/Ingress filter disable
C-Aware port
S-Aware port
NOTE
a: When Bridge Learning Mode is set to IVL, the VLAN filtering table must be configured so that the bridge can check the contents of the VLAN tags. If the VLAN ID is not defined in the VLAN filtering table, the packet is discarded.
The 802.1ad bridge normally adopts Model 1. Figure 8-12 shows the typical application of the model of service. The transport network needs to carry G and H services accessed from NE2 and NE3. The two types of services are aggregated and switched on NE1. Since G and H services have a same C-VLAN tag, you need to add different S-VLAN tags to G and H services for service isolation.
Issue 03 (2011-04-10)
8-13
Figure 8-12 Model of EVPLAN services based on 802.1ad bridge

NE 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H) Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
NE 2
SVLAN 300
Port 1 User G2 Port 3 NE 1

SVLAN 300 SVLAN 400 CVLAN 100
Transmission Network Port 3 802.1ad bridge
Port 2 User H2
CVLAN 100
Port 1 User G1
CVLAN 100 SVLAN 400
User H1
Port 2 Port 4 802.1ad bridge Transmission Network
NE 3
SVLAN 300
CVLAN 100
Port 1 User G3
CVLAN 100 SVLAN 400
NE 1
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
Port 3
Port 2 User H3
CVLAN 100
802.1ad bridge NE 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
NOTE
You can configure 8.1.5.3 QinQ-based EVPL Services on NE2 and NE3 for service access.

The service configuration procedure differs according to the specific service type. 8.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring point-to-point transparently transmitted EPL services. 8.2.2 Configuration Procedure (VLAN-Based EVPL Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring VLAN-based EVPL services. 8.2.3 Configuration Procedure (QinQ-Based EVPL Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring QinQ-based EVPL services.
8.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1d bridge-based EPLAN services. 8.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1q bridge-based EVPLAN services. 8.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services) This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.
8.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring point-to-point transparently transmitted EPL services.

Figure 8-13 provides the procedures for configuring point-to-point transparently transmitted EPL services. Figure 8-13 Configuration flow chart (point-to-point transparently transmitted EPL services)
Required Optional Configuring Ethernet Ports Start
Configuring LAGs
Configuring Ethernet Line Services
Configuring QoS
Verifying Ethernet Service Configurations
End
Issue 03 (2011-04-10)
8-15

Table 8-7 Procedures for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l You need to set TAG Attributes. In the case of a point-to-point transparently transmitted EPL service, set Entry Detection to Disabled. l In the case of a point-to-point transparently transmitted EPL service, set Port Attributes in the Network Attributes tag page to UNI. l Determine whether to set Advanced Attributes according to actual requirements.
8-16
Issue 03 (2011-04-10)
Operation A.7.4.2 Configuring VCTRUNKs on an Ethernet Board
Description Required when internal ports need to be used. l You need to set TAG Attributes. In the case of a point-to-point transparently transmitted EPL service, set Entry Detection to Disabled. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of a point-to-point transparently transmitted EPL service, set Port Attributes in the Network Attributes tag page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.
NOTE The EFP8 of the OptiX RTN 950 is an EoPDH Ethernet board, which supports VCTRUNKs that bind E1 channels. On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
Issue 03 (2011-04-10)
8-17
Procedure for Configuring a LAG

Table 8-8 Procedure for configuring a LAG Operation A.7.1.1 Creating a LAG Description Required when a LAG needs to be configured. Set the major parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive for the equipment at both ends. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l Set Main Port and Selected Standby Ports according to the network planning information. It is recommended that the main and slave ports at both ends adopt the same settings. A.7.1.2 Setting Parameters for LAGs Optional.
8-18
Issue 03 (2011-04-10)
Procedure for Configuring Point-to-Point Transparently Transmitted EPL Services

Table 8-9 Procedure for configuring point-to-point transparently transmitted EPL services Operation A.7.2.1 Creating Ethernet Private Line Services Description Required. Set the parameters as follows: l Set Service Type to EPL. l Set Direction to Bidirectional. l Set Source Port and Sink Port according to the network planning information. l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) to null. l If any VCTRUNK to which no paths are bound is used as Source Port or Sink Port, configure corresponding bound channels according to the network planning information.
NOTE The EFP8 is an EoPDH Ethernet board, which supports VCTRUNKs that bind E1 channels. On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
Procedure for Configuring the QoS

Table 8-10 Procedure for configuring the QoS Operation A.7.7.1 Creating a Flow A.7.7.2 Creating the CAR A.7.7.3 Creating the CoS A.7.7.4 Binding the CAR/CoS A.7.7.5 Configuring Traffic Shaping for Egress Queues Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Description Required when you need to perform CAR or CoS operations. Before performing any CAR or CoS operations, you need to create flows. Set the relevant parameters according to the network planning information. Required if you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CARs or CoSs to the corresponding flows according to the network planning information.
Issue 03 (2011-04-10)
8-19
Procedure for Testing Ethernet Services

NOTE
It is recommended that you use standard MPs for testing Ethernet services. The following table only provides the description about standard MPs.
Table 8-11 Procedure for testing Ethernet services Operation A.7.8.1 Creating MDs Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.7.8.2 Creating MAs Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs. A.7.8.3 Creating MPs Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the major parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Node to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the Ethernet switching unit on the EFP8 board, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l If the MP ID is used to identify an MEP, set CC Status to Active. l It is recommended that you set CCM Sending Period(ms) to 1000 ms. perform an LB test to test the Ethernet service configurations Required. The LB test result should show that the test is successful.
8.2.2 Configuration Procedure (VLAN-Based EVPL Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring VLAN-based EVPL services.

Figure 8-14 provides the procedures for configuring VLAN-based EVPL services. Figure 8-14 Configuration flow chart (VLAN-based EVPL services)
Configuring LAGs
Configuring QoS
End
Issue 03 (2011-04-10)
8-21
Procedure for Configuring Ethernet Ports

Table 8-12 Procedure for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l You need to set TAG Attributes. In the case of a VLAN-based EVPL service, set Entry Detection to Enabled. Set TAG, Default VLAN ID, and VLAN Priority as planned. Default VLAN ID and VLAN Priority are valid only when TAG is Access or Hybrid. l In the case of a VLAN-based EVPL service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to set Advanced Attributes according to actual requirements.
8-22
Issue 03 (2011-04-10)
Description Required when internal ports need to be used. l You need to set TAG Attributes. In the case of a VLAN-based EVPL service, set Entry Detection to Enabled. Set TAG, Default VLAN ID, and VLAN Priority as planned. Default VLAN ID and VLAN Priority are valid only when TAG is Access or Hybrid. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of a VLAN-based EVPL service, it is recommended that you set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.
Issue 03 (2011-04-10)
8-23

8-24
Issue 03 (2011-04-10)
Procedure for Configuring VLAN-Based EVPL Services

Table 8-14 Procedure for configuring VLAN-based EVPL services Operation A.7.2.1 Creating Ethernet Private Line Services Description Required. Set the major parameters as follows: l Set Service Type to EPL. l Set Direction to Bidirectional. l Set Source Port and Sink Port according to the network planning information. l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) according to the network planning information. l If any VCTRUNK to which no paths are bound is used as Source Port or Sink Port, configure corresponding bound channels according to the network planning information.

Issue 03 (2011-04-10)
8-25

NOTE
Table 8-16 Procedure for testing Ethernet services Operation A.7.8.1 Creating MDs Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.7.8.2 Creating MAs Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs. A.7.8.3 Creating MPs Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the major parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Node to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the Ethernet switching unit on the EFP8 board, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l If the MP ID is used to identify an MEP, set CC Status to Active. l It is recommended that you set CCM Sending Period(ms) to 1000 ms. perform an LB test to test the Ethernet service configurations Required. The LB test result should show that the test is successful.
8.2.3 Configuration Procedure (QinQ-Based EVPL Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring QinQ-based EVPL services.

Figure 8-15 provides the procedures for configuring QinQ-based EVPL services. Figure 8-15 Configuration flow chart (QinQ-based EVPL services)
Configuring LAGs
Configuring QoS
End
Issue 03 (2011-04-10)
8-27

Table 8-17 Procedure for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l In the case of a QinQ-based EVPL service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l Determine whether to set Advanced Attributes according to actual requirements.
8-28
Issue 03 (2011-04-10)
Description Required when internal ports need to be used. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of a QinQ-based EVPL service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.

Table 8-18 Procedure for configuring a LAG Operation A.7.1.1 Creating a LAG Description Required when a LAG needs to be configured. Set the major parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive for the equipment at both ends. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l Set Main Port and Selected Standby Ports according to the network planning information. It is recommended that the main and slave ports at both ends adopt the same settings.
Procedure for Configuring QinQ-Based EVPL Services

Table 8-19 Procedure for configuring QinQ-based EVPL services Operation A.7.2.5 Creating QinQ-Based EVPL Services Description Required. Set the major parameters as follows:
NOTE Before setting the parameters, select Display QinQ Shared Service.
l Set Service Type to EVPL (QinQ). l Set Direction to Bidirectional. l Set Operation Type, Source Port, Source C-VLAN (e.g. 1, 3-6), Source S-VLAN, Sink Port, Sink C-VLAN(e.g. 1, 3-6), Sink SVLAN, C-VLAN Priority, and S-VLAN Priority according to the network planning information. l If any VCTRUNK to which no paths are bound is used as Source Port or Sink Port, configure corresponding bound channels according to the network planning information.

Table 8-20 Procedure for configuring the QoS Operation A.7.7.1 Creating a Flow A.7.7.2 Creating the CAR A.7.7.3 Creating the CoS Description Required when you need to perform CAR or CoS operations. Before performing any CAR or CoS operations, you need to create flows. Set the relevant parameters according to the network planning information. Required if you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CARs or CoSs to the corresponding flows according to the network planning information.
8-30
Issue 03 (2011-04-10)
Operation A.7.7.4 Binding the CAR/CoS A.7.7.5 Configuring Traffic Shaping for Egress Queues
Description
Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information.

NOTE
Table 8-21 Procedure for testing Ethernet services Operation A.7.8.1 Creating MDs Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.7.8.2 Creating MAs Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs.
Issue 03 (2011-04-10)
8-31
Operation A.7.8.3 Creating MPs
Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the major parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Node to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the Ethernet switching unit on the EFP8 board, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l If the MP ID is used to identify an MEP, set CC Status to Active. l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
perform an LB test to test the Ethernet service configurations
Required. The LB test result should show that the test is successful.
8.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1d bridge-based EPLAN services.

Figure 8-16 provides the procedures for configuring IEEE 802.1d bridge-based EPLAN services.
8-32
Issue 03 (2011-04-10)
Figure 8-16 Configuration flow chart (802.1d bridge-based EPLAN services)

Configuring LAGs
Configuring Ethernet LAN Services
Configuring QoS
End
Issue 03 (2011-04-10)
8-33

Table 8-22 Procedure for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l To enable the broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.
8-34
Issue 03 (2011-04-10)
Description Required when internal ports need to be used. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.

Table 8-23 Procedure for configuring a LAG Operation A.7.1.1 Creating a LAG Description Required when a LAG needs to be configured. Set the major parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive for the equipment at both ends. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l Set Main Port and Selected Standby Ports according to the network planning information. It is recommended that the main and slave ports at both ends adopt the same settings.
Procedure for Configuring IEEE 802.1d Bridge-Based EPLAN Services

Table 8-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services Operation A.7.2.2 Creating Ethernet LAN Services Description Required. Set the major parameters as follows: l Set VB name according to the network planning information. l Set Bridge Type to 802.1d. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the network planning information.
Managing the MAC address table
A.7.3.2 Creating a Blacklist Entry of a MAC Address A.7.3.1 Creating a Static MAC Address Entry A.7.3.3 Setting the Aging Time of a MAC Address Table Entry
Required when usage of EPLAN services needs to be disabled on certain MAC address hosts. The parameters need to be set according to network planning.
Required if you need to set certain MAC address entries not to age. The parameters need to be set according to network planning.
Required if you need to disable the aging function or change the aging time (five minutes by default). The parameters need to be set according to network planning.
A.7.2.3 Changing the Ports Connected to a VB
Required if you need to change a port connected to a VB, enabled status of a port connected to a VB, or Hub/Spoke attribute of a port connected to a VB.
8-36
Issue 03 (2011-04-10)


NOTE
Table 8-26 Procedure for testing Ethernet services Operation A.7.8.1 Creating MDs Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.
Issue 03 (2011-04-10)
8-37
Operation A.7.8.2 Creating MAs
Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs.
A.7.8.3 Creating MPs
Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the major parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Node to the Ethernet ports that are involved in the service test. l Set MP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the Ethernet switching unit on the EFP8 board, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l If the MP ID is used to identify an MEP, set CC Status to Active. l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
8.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1q bridge-based EVPLAN services.

Figure 8-17 provides the procedures for configuring IEEE 802.1q bridge-based EVPLAN services.
8-38
Issue 03 (2011-04-10)
Figure 8-17 Configuration flow chart (IEEE 802.1q bridge-based EVPLAN services)
Configuring LAGs
Configuring QoS
End
Issue 03 (2011-04-10)
8-39

Table 8-27 Procedure for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l TAG Attributes is mandatory. Set TAG, Default VLAN ID, and VLAN Priority as required. Default VLAN ID and VLAN Priority are valid only when TAG is Access or Hybrid. l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l To enable the broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.
8-40
Issue 03 (2011-04-10)
Description Required when internal ports need to be used. l TAG is mandatory. Set TAG, Default VLAN ID, and VLAN Priority. Default VLAN ID and VLAN Priority are valid only when TAG is Access or Hybrid. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.
Issue 03 (2011-04-10)
8-41

8-42
Issue 03 (2011-04-10)
Procedure for Configuring IEEE 802.1q Bridge-Based EVPLAN Services

Table 8-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services Operation A.7.2.2 Creating Ethernet LAN Services Description Required. Set the major parameters as follows: l Set VB name according to the network planning information. l Set Bridge Type to 802.1q. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the network planning information.
A.7.2.4 Creating the VLAN Filtering Table
Required. Set VLAN ID(e.g.1,3-6) and Selected forwarding ports according to the network planning information. Required when usage of EVPLAN services needs to be disabled on certain MAC address hosts. Set the parameters according to the network planning information.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if you need to disable the aging function or change the aging time (five minutes by default). Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
8-43


NOTE
8-44
Issue 03 (2011-04-10)
8.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services)

This section describes how to perform parameter settings and other relevant operations as required in the procedure for configuring IEEE 802.1ad bridge-based EVPLAN services.

Figure 8-18 provides the procedures for configuring IEEE 802.1ad bridge-based EVPLAN services.
Issue 03 (2011-04-10)
8-45
Figure 8-18 Configuration flow chart (IEEE 802.1ad bridge-based EVPLAN services)
Configuring LAGs
Configuring QoS
End
8-46
Issue 03 (2011-04-10)

Table 8-32 Procedure for configuring Ethernet ports Operation A.7.4.1 Configuring External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used ports, set Enabled/Disabled to Enabled. In the case of unused ports, set Enabled/Disabled to Disabled. In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: When the external equipment uses the non-auto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the auto-negotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric/Dissymmetric Flow Control. l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l To enable the broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.
Issue 03 (2011-04-10)
8-47
Description Required when internal ports need to be used. l Determine whether to set Encapsulation/Mapping according to actual requirements. It is recommended that the parameters take the default values and are the same for both ends of a link. l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Mode according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameter settings are consistent at both ends of a link. l You need to set Bound Path. Configure bound channels according to the network planning information.
8-48
Issue 03 (2011-04-10)

Issue 03 (2011-04-10)
8-49
Procedure for Configuring IEEE 802.1ad Bridge-Based EVPLAN Services

Table 8-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services Operation A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services Description Required. Set the parameters as follows: l Set VB name according to the network planning information. l Set Bridge Type to 802.1ad. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the network planning information.
Required if you set Bridge Switch Mode to IVL/Ingress Filter Enable. Set VLAN ID(e.g.1,3-6) and Selected forwarding ports according to the network planning information.
Required when usage of EVPLAN services needs to be disabled on certain MAC address hosts. The parameters need to be set according to network planning.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if you need to disable the aging function or change the aging time (five minutes by default). Set the parameters according to the network planning information.
8-50
Issue 03 (2011-04-10)


NOTE
Issue 03 (2011-04-10)
8-51
8.3 Configuration Example (Ethernet Services Based on TDM Radio)

This section considers an Ethernet service based on TDM radio as an example to describe how to configure Ethernet services according to the service planning information. 8.3.1 Networking Diagram This section describes the networking information about the NEs. 8.3.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service based on TDM radio. 8.3.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network), configure the Ethernet services on the TDM radio chain network shown in Figure 8-19, according to the following requirements:
In this example, few Ethernet services are transmitted only on BTS13 and BTS14. To meet the service requirements, the radio network need not be upgraded and the EoPDH mode is adopted to transmit Ethernet services. The Ethernet services on BTS13 occupy a 4 Mbit/s bandwidth and the Ethernet services on BTS14 occupy a 10 Mbit/s bandwidth. Ethernet services transmitted by BTS13 and BTS14 carry VLAN tags, and VLAN IDs on the entire network are planned in a unified manner. FE links to the BSC are configured with LAG protection. QoS processing is not required. Figure 8-20 shows the board configuration of each NE on the radio network.
l l l l l
Figure 8-19 Networking diagram (Ethernet services based on TDM radio)

E1 BTS12 FE+E1 STM-1 NE14 E1 NE13 FE+E1 E1 NE16 BTS15 NE15 BTS14 10 Mbit/s VLAN 130 NE12 BTS11 NE11 BSC FE+STM-1
BTS13 4 Mbit/s VLAN 120
Figure 8-20 Board configuration (Ethernet services based on TDM radio)

NE13 E1 BTS12 FE E1 BTS13
CST IF1 NE6 IF1 SL1D IF1 IF1
NE12
CST IF1 NE6 IF1 SL1D CST IF1 NE6 IF1 SL1D
NE11
NE14
CST IF1 NE6 IF1
EFP8
EFP8 SP3S
SP3S
STM-1 BTS11
E1 STM-1 BSC FE
CST NE6 IF1 SP3S
CST NE6 IF1 EFP8 IF1 IF1 SP3S
NE16 E1 BTS15
NE15
FE
E1 BTS14
The connections of Ethernet links are described as follows.

Table 8-37 Connections of Ethernet links (NE11) Link Between NE11 and the BSC Port 4-EFP8-PORT1 (main port of a LAG) 4-EFP8-PORT2 (slave port of a LAG) Description l Configure these ports to aggregate the Ethernet services backhauled from BTS13 and BTS14 to the BSC. l Configure these ports into a load non-sharing LAG, therefore improving link reliability. Configure these ports to transmit Ethernet services encapsulated in E1s.
3-IF1 (main IF board of a 1+1 HSB protection group) 5-IF1 (standby IF board of a 1+1 HSB protection group)
Table 8-38 Connections of Ethernet links (NE12) Link Between NE12 and NE11 Port 3-IF1 (main IF board of a 1+1 HSB protection group) 5-IF1 (standby IF board of a 1+1 HSB protection group) Between NE12 and NE13 1-SL1D-1 Description Configure these ports to transmit Ethernet services encapsulated in E1s.
Configure these ports to transmit Ethernet services encapsulated in E1s.
Table 8-39 Connections of Ethernet links (NE13) Link Between NE13 and NE12 Port 1-SL1D-1 Description Configure these ports to transmit Ethernet services encapsulated in E1s. Configure these ports to transmit Ethernet services encapsulated in E1s.
4-IF1 (main IF board of a 1+1 HSB protection group)
Configure these ports to transmit Ethernet services encapsulated in E1s.
8-54
Issue 03 (2011-04-10)
Link
Port 6-IF1 (standby IF board of a 1+1 HSB protection group)
Description
Table 8-40 Connections of Ethernet links (NE14) Link Between NE14 and BTS13 Port 4-EFP8-PORT1 Description Configure this port to support access of services from BTS13 and transmit the services in EoPDH mode. Configure these ports to transmit Ethernet services encapsulated in E1s.
Table 8-41 Connections of Ethernet links (NE15) Link Between NE15 and BTS14 Port 1-EFP8-PORT1 Description Configure this port to support access of services from BTS14 and transmit the services in EoPDH mode. Configure these ports to transmit Ethernet services encapsulated in E1s.

You need to plan the corresponding parameter information before configuring an Ethernet service based on TDM radio. 8.3.2.1 Service Planning (Ethernet Ports) This section provides the information about all the parameters required for configuring Ethernet ports. 8.3.2.2 Service Planning (Ethernet Protection) This section provides the information about all the parameters required for configuring Ethernet protection. 8.3.2.3 Service Planning (Ethernet Services)
This section provides the information about all the parameters required for configuring Ethernet services. 8.3.2.4 Service Planning (Ethernet Service Cross-Connections) This section provides the information about all the parameters required for configuring Ethernet service cross-connections. 8.3.2.5 Service Planning (QoS) In this example, the QoS function is not used.

This section provides the information about all the parameters required for configuring Ethernet ports.
Information About Ethernet External Ports

Table 8-42 to Table 8-44 provide the information about the Ethernet ports that transmit the Ethernet services. Table 8-42 Information about Ethernet external ports (NE11) Parameter Port enabled Port working mode Maximum frame length Flow control TAG attribute Entry detection Network attribute 4-EFP8-PORT1 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI 4-EFP8-PORT2 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI
Table 8-43 Information about Ethernet external ports (NE14) Parameter Port enabled Port working mode Maximum frame length Flow control TAG attribute Entry detection Network attribute 4-EFP8-PORT1 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI
8-56
Issue 03 (2011-04-10)
Table 8-44 Information about Ethernet external ports (NE15) Parameter Port enabled Port working mode Maximum frame length Flow control TAG attribute Entry detection Network attribute 1-EFP8-PORT1 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI
NOTE
l In this example, the FE ports on all the BTSes/BSC work in auto-negotiation mode. Therefore, the FE ports on the NEs that receive services from and transmit services to the BTSes/BSC must also work in auto-negotiation mode. If the peer Ethernet ports work in a mode other than the auto-negotiation mode, plan the local Ethernet ports to work in the same mode as the peer Ethernet ports. In the case of Ethernet ports within a network, plan the Ethernet ports to work in auto-negotiation mode. l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends. l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag Aware. l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

Table 8-45 to Table 8-47 provide the information about the VCTRUNKs that are configured to transmit the Ethernet services. Table 8-45 Information about VCTRUNKs (NE11) Parameter 4-EFP8-VCTRUNK1 (Receiving and Transmitting Ethernet Services Between BTS14 and the BSC) Tag Aware Enabled UNI 4-EFP8-VCTRUNK2 (Receiving and Transmitting Ethernet Services Between BTS13 and the BSC) Tag Aware Enabled UNI
TAG attribute Entry detection Network attribute
Issue 03 (2011-04-10)
8-57
Parameter
4-EFP8-VCTRUNK1 (Receiving and Transmitting Ethernet Services Between BTS14 and the BSC) GFP Enabled VC4-1-VC12(1-5)
4-EFP8-VCTRUNK2 (Receiving and Transmitting Ethernet Services Between BTS13 and the BSC) GFP Enabled VC4-1-VC12(6-7)
Mapping protocol LCAS Bound paths
Table 8-46 Information about VCTRUNKs (NE14) Parameter 4-EFP8-VCTRUNK1 (Receiving and Transmitting Ethernet Services Between BTS13 and the BSC) Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(1-2)
TAG attribute Entry detection Network attribute Mapping protocol LCAS Bound paths
Table 8-47 Information about VCTRUNKs (NE15) Parameter 1-EFP8-VCTRUNK1 (Receiving and Transmitting Ethernet Services Between BTS14 and the BSC) Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(1-5)
TAG attribute Entry detection Network attribute Mapping protocol LCAS Bound paths

This section provides the information about all the parameters required for configuring Ethernet protection.
To improve reliability of service transmission, NE11 and the BSC are interconnected through the LAG formed by two FE links. Table 8-48 provides the planning information. Table 8-48 Information about the LAG Parameter LAG type Revertive mode Load sharing System priority Main port Slave port NE11 Static Non-Revertive Non-Sharing 32768 4-EFP8-PORT1 4-EFP8-PORT2
NOTE
In this example, the bandwidth of the Ethernet services to be transmitted is 14 Mbit/s, which is much lower than the bandwidth of an FE port. Therefore, you need not configure the LAG to the load-sharing mode to increase the bandwidth.

This section provides the information about all the parameters required for configuring Ethernet services. Ethernet services received by each BTS carry the specific VLAN ID. Therefore, you need to configure VLAN-based EVPL services in this example. Table 8-49 to Table 8-51 provide the service planning information. Table 8-49 Information about VLAN-based EVPL services (NE11) Parameter Board Service type Service direction Source port Source VLAN Sink port Sink VLAN Between BTS14 and the BSC 4-EFP8 EPL Bidirectional VCTRUNK1 130 PORT1 130 Between BTS13 and the BSC 4-EFP8 EPL Bidirectional VCTRUNK2 120 PORT1 120
Issue 03 (2011-04-10)
8-59
Table 8-50 VLAN-based EVPL services (NE14) Parameter Board Service type Service direction Source port Source VLAN Sink port Sink VLAN Between BTS13 and the BSC 4-EFP8 EPL Bidirectional PORT1 120 VCTRUNK1 120
Table 8-51 VLAN-based EVPL services (NE15) Parameter Board Service type Service direction Source port Source VLAN Sink port Sink VLAN Between BTS14 and the BSC 1-EFP8 EPL Bidirectional PORT1 130 VCTRUNK1 130
8.3.2.4 Service Planning (Ethernet Service Cross-Connections)

This section provides the information about all the parameters required for configuring Ethernet service cross-connections.
Timeslot Allocation
Figure 8-21 shows the timeslots that are allocated to the TDM radio-based Ethernet services according to the service planning information. 6.1.4 TDM Timeslot Planning Schemes describes the meanings of the timeslot allocation diagram and how to plan the timeslot allocation diagram.
8-60
Issue 03 (2011-04-10)
Figure 8-21 Timeslot allocation diagram (Ethernet services based on TDM radio)
Links-1: NE11 - NE12 - NE13 -NE15-NE16 Station Timeslot NE11 3-IF1 3-IF1 VC12:1-5 4-EFP8-1 (VCTRUNK1) VC4-1:VC12:1-5 VC4-1 4-EFP8-1(VCTRUNK2) VC4-1:VC12:6-7 VC12:6-7 1-EFP8-1 (VCTRUNK1) VC4-1:VC12:1-5 NE12 1-SL1D-1 NE13 1-SL1D-1 4-IF1 4-IF1 NE15 3-IF1 NE16 3-IF1
Links-2: NE13-NE14 Station Timeslot VC4-1 VC12:6-7 NE13 1-SL1D-1 3-IF1 VC12:1-2 4-EFP8 -1(VCTRUNK1) VC4-1:VC12:1-2 NE14 3-IF1
Pass through Add/Drop Foward
As shown in Figure 8-21, the information about the timeslots that the TDM radio-based Ethernet services occupy on each NE is as follows: l Ethernet services on NE15: The Ethernet services are added to or dropped from the first to fifth VC-12 timeslots in the first VC-4 of VCTRUNK1 on the EFP8 board in slot 1 of NE15. The Ethernet services are added to or dropped from the first to fifth VC-12 timeslots in the first VC-4 of VCTRUNK1 on the EFP8 board in slot 4 of NE11. The Ethernet services occupy the first to fifth VC-12 timeslots on the link between the IF1 board in slot 3 of NE11 and the IF1 board in slot 4 of NE15. l Ethernet services on NE14: The Ethernet services are added to or dropped from the first and second VC-12 timeslots in the first VC-4 of VCTRUNK1 on the EFP8 board in slot 4 of NE14. The Ethernet services are added to or dropped from the sixth and seventh VC-12 timeslots in the first VC-4 of VCTRUNK2 on the EFP8 board in slot 4 of NE11. The Ethernet services occupy the sixth and seventh VC-12 timeslots on the link between the IF1 board in slot 3 of NE11 and the first optical port on the SL1D board in slot 1 of NE13. The Ethernet services occupy the first and second VC-12 timeslots on the link from the IF1 board in slot 3 of NE13 to the IF1 board in slot 3 of NE14.
Information About Cross-Connections of Ethernet Services

Based on the timeslot allocation information shown in Figure 8-21, you can plan the Ethernet service cross-connections. Table 8-52 to Table 8-56 provide the information about crossconnections of the Ethernet services.
Table 8-52 Cross-connections of Ethernet services (NE11) Parameter Service level Service direction Source slot Source port Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range Value VC12 Bidirectional 4-EFP8 1 VC4-1 1-7 3-IF1 1 VC4-1 1-7
Table 8-53 Cross-connections of Ethernet services (NE12) Parameter Service level Service direction Source slot Source port Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range Value VC12 Bidirectional 3-IF1 1 VC4-1 1-7 1-SL1D 1 VC4-1 1-7
Table 8-54 Cross-connections of Ethernet services (NE13) Parameter Service level Service direction Value VC-12 Bidirectional VC-12 Bidirectional
8-62
Issue 03 (2011-04-10)
Parameter Source slot Source port Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range
Value 1-SL1D 1 VC4-1 1-5 4-IF1 1 VC4-1 1-5 1-SL1D 1 VC4-1 6-7 3-IF1 1 VC4-1 1-2
Table 8-55 Cross-connections of Ethernet services (NE14) Parameter Service level Service direction Source slot Source port Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range Value VC12 Bidirectional 4-EFP8 1 VC4-1 1-2 3-IF1 1 VC4-1 1-2
Table 8-56 Cross-connections of Ethernet services (NE15) Parameter Service level Service direction Source slot Source port Source VC4 Value VC12 Bidirectional 1-EFP8 1 VC4-1
Issue 03 (2011-04-10)
8-63
Parameter Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range
Value 1-5 4-IF1 1 VC4-1 1-5

In this example, the QoS function is not used.

This section describes the process for data configuration. 8.3.3.1 Configuration Process (Ethernet Ports) This section describes the process for configuring Ethernet ports. 8.3.3.2 Configuration Process (Ethernet Protection) This section describes the process for configuring Ethernet protection. 8.3.3.3 Configuration Process (Ethernet Services) This section describes the process for configuring the Ethernet service information. 8.3.3.4 Configuration Process (Cross-Connections) This section describes the process for configuring the cross-connections. 8.3.3.5 Configuration Process (QoS) In this example, the QoS function is not used. 8.3.3.6 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

Procedure
Step 1 See A.7.4.1 Configuring External Ethernet Ports and configure the Ethernet external ports. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8-PORT1 Enabled/Disabled Working Mode
8-64
4-EFP8-PORT2 Enabled Auto-Negotiation

Issue 03 (2011-04-10)
Enabled Auto-Negotiation
Parameter
Value 4-EFP8-PORT1 4-EFP8-PORT2 1522 Disabled Disabled Tag Aware Enabled UNI
Maximum Frame Length Non-Autonegotiation Flow Control Mode Autonegotiation Flow Control Mode TAG Entry Detection Port Attributes
1522 Disabled Disabled Tag Aware Enabled UNI
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value 4-EFP8-PORT1 Enabled/Disabled Working Mode Maximum Frame Length Non-Autonegotiation Flow Control Mode Autonegotiation Flow Control Mode TAG Entry Detection Port Attributes Enabled Auto-Negotiation 1522 Disabled Disabled Tag Aware Enabled UNI
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value 1-EFP8-PORT1 Enabled/Disabled Working Mode Maximum Frame Length Non-Autonegotiation Flow Control Mode Autonegotiation Flow Control Mode Enabled Auto-Negotiation 1522 Disabled Disabled
Issue 03 (2011-04-10)
8-65
Parameter
Value 1-EFP8-PORT1
TAG Entry Detection Port Attributes
Tag Aware Enabled UNI
Step 2 See A.7.4.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8-VCTRUNK1 TAG Entry Detection Mapping Protocol Port Attributes Enabling LCAS Level Direction Bound Path Tag Aware Enabled GFP UNI Enabled VC-12-Xv Bidirectional VC4-1-VC12(1-5) 4-EFP8-VCTRUNK2 Tag Aware Enabled GFP UNI Enabled VC-12-Xv Bidirectional VC4-1-VC12(6-7)
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value 4-EFP8-VCTRUNK1 TAG Entry Detection Mapping Protocol Port Attributes Enabling LCAS Level Direction Bound Path Tag Aware Enabled GFP UNI Enabled VC-12-Xv Bidirectional VC4-1-VC12(1-2)
Parameter
Value 1-EFP8-VCTRUNK1
TAG Entry Detection Mapping Protocol Port Attributes Enabling LCAS Level Direction Bound Path
Tag Aware Enabled GFP UNI Enabled VC-12-Xv Bidirectional VC4-1-VC12(1-5)
----End

Procedure
Step 1 See A.7.1.1 Creating a LAG and create the LAG. The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8 LAG No LAG Name LAG Type Load Sharing Revertive Mode Main Port Selected Standby Ports 1 ToBSC Static Non-Sharing Non-Revertive PORT1 PORT2
Step 2 See A.7.1.2 Setting Parameters for LAGs and set the parameters for LAGs. The values for the relevant parameters of NE11 are provided as follows.
Issue 03 (2011-04-10)
8-67
Parameter
Value 4-EFP8
LAG No LAG Name System Priority
1 ToBSC 32768
----End
8.3.3.3 Configuration Process (Ethernet Services)

This section describes the process for configuring the Ethernet service information.
Procedure
Step 1 See A.7.2.1 Creating Ethernet Private Line Services and create the Ethernet private line service. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value Between BTS14 and the BSC Board Service Type Direction Source Port Source VLAN(e.g. 1,3-6) Sink Port Sink VLAN(e.g. 1,3-6) 4-EFP8 EPL Bidirectional VCTRUNK1 130 PORT1 130 Between BTS13 and the BSC 4-EFP8 EPL Bidirectional VCTRUNK2 120 PORT1 120
l The values for the relevant parameters of NE14 are provided as follows. Parameter Value Between BTS13 and the BSC Board Service Type Direction Source Port
8-68
4-EFP8 EPL Bidirectional PORT1

Issue 03 (2011-04-10)
Parameter
Value Between BTS13 and the BSC
Source VLAN(e.g. 1,3-6) Sink Port Sink VLAN(e.g. 1,3-6)
120 VCTRUNK1 120
l The values for the relevant parameters of NE15 are provided as follows. Parameter Value Between BTS14 and the BSC Board Service Type Direction Source Port Source VLAN(e.g. 1,3-6) Sink Port Sink VLAN(e.g. 1,3-6) 1-EFP8 EPL Bidirectional PORT1 130 VCTRUNK1 130
----End
8.3.3.4 Configuration Process (Cross-Connections)

This section describes the process for configuring the cross-connections.
Procedure
Step 1 On NE11, NE14, and NE15, see A.4.1 Creating the Cross-Connections of Point-to-Point Services and create the service cross-connections. l The values for the relevant parameters of NE11 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6)
Issue 03 (2011-04-10)
Value VC12 Bidirectional 4-EFP8 1 VC4-1 1-7

8-69
Parameter Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
Value 3-IF1 1 VC4-1 1-7
l The values for the relevant parameters of NE12 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) Value VC12 Bidirectional 3-IF1 1 VC4-1 1-7 1-SL1D 1 VC4-1 1-7
l The values for the relevant parameters of NE13 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Value VC12 Bidirectional 1-SL1D 1 VC4-1 1-5 4-IF1 1 VC4-1 VC12 Bidirectional 1-SL1D 1 VC4-1 6-7 3-IF1 1 VC4-1
8-70
Issue 03 (2011-04-10)
Parameter Sink Timeslot Range(e.g. 1,3-6)
Value 1-5 1-2
l The values for the relevant parameters of NE14 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) Value VC12 Bidirectional 4-EFP8 1 VC4-1 1-2 3-IF1 1 VC4-1 1-2
l The values for the relevant parameters of NE15 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) Value VC12 Bidirectional 1-EFP8 1 VC4-1 1-5 4-IF1 1 VC4-1 1-5
----End
Issue 03 (2011-04-10)
8-71

In this example, the QoS function is not used.

Procedure
Step 1 On NE11, NE14, and NE15, see A.7.8.1 Creating MDs and create the maintenance domain. The values for the required parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE14 EdgeNE 4 NE15 EdgeNE 4
Step 2 On NE11, NE14, and NE15, see A.7.8.2 Creating MAs and create the maintenance association. l The values for the relevant parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Value EdgeNE BTS13_Vline EdgeNE BTS14_Vline
l The values for the relevant parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Value EdgeNE BTS13_Vline
l The values for the relevant parameters of NE15 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Value EdgeNE BTS14_Vline
Step 3 On NE11, NE14, and NE15, see A.7.8.3 Creating MPs and create the maintenance points.
l The values for the relevant parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status CCM Sending Period(ms) Value EdgeNE BTS13_Vline 4-EFP8-PORT1 120 103 MEP Ingress Activate 1000 EdgeNE BTS14_Vline 4-EFP8-PORT1 130 104 MEP Ingress Activate 1000
l The values for the relevant parameters of NE14 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status CCM Sending Period(ms) Value EdgeNE BTS13_Vline 4-EFP8-PORT1 120 401 MEP Ingress Activate 1000
l The values for the relevant parameters of NE15 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID
Issue 03 (2011-04-10)
Value EdgeNE BTS14_Vline 1-EFP8-PORT1 130 501
8-73
Parameter Type Direction CC Status CCM Sending Period(ms)
Value MEP Ingress Activate 1000
Step 4 On NE11, perform LB tests to test the Ethernet service configurations. l Perform the LB test by considering the maintenance point whose MP ID is 103 as the source maintenance point and considering the maintenance point whose MP ID is 401 as the sink maintenance point. l Perform the LB test by considering the maintenance point whose MP ID is 104 as the source maintenance point and considering the maintenance point whose MP ID is 501 as the sink maintenance point. All LB tests should show that the tests are successful. ----End
8.4 Configuration Example (Ethernet Services Traversing a TDM Network)

This section considers an Ethernet service traversing a TDM network as an example to describe how to configure Ethernet services according to the service planning information. 8.4.1 Networking Diagram This section describes the networking information about the NEs. 8.4.2 Service Planning You need to plan the corresponding parameter information before configuring an Ethernet service traversing a TDM network. 8.4.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. On the network shown in Figure 8-22, all the Ethernet services from BTS11-BTS15 are aggregated through Hybrid radio links to NE11, traverse the leased TDM network, and then are transmitted to the BSC. Based on 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network), configure the Ethernet services according to the following requirements: l l NE11 uses the EFP8 board to receive Ethernet services from and transmit Ethernet services to BTS16. NE11 and NE17 use the EoPDH technology, wherein Ethernet services are encapsulated into E1 services so that Ethernet services traverse the TDM network successfully.
8-74
NOTE
To facilitate description of service configurations in this example, NE17 is an IDU that supports the EoPDH function. In actual networking scenarios, NE17 can also be OptiX MSTP equipment that supports the EoPDH function.
l l
Each BTS is allocated with a specific Ethernet bandwidth and a total of 40 Mbit/s bandwidth is required. Therefore, 20 E1 lines need to be leased. The services transmitted by each BTS carry VLAN tags, and VLAN IDs on the entire network are planned in a unified manner. Therefore, the VLAN-based E-Line services are configured for service transmission in this example. VLAN priorities are configured on each BTS according to service types and QoS processing is required. Figure 8-23 shows the board configuration of each NE on the radio network.
NOTE
l l
This section describes only how to configure Ethernet services on NE11 and NE17. For details on how to configure Ethernet services on NE12 to NE16, see 7.4 Configuration Example (VLAN-Based E-Line Service).
Figure 8-22 Networking diagram (Ethernet services traversing a TDM network)

BTS12 10 Mbit/s VLAN 110 FE
BTS16 10 Mbit/s VLAN 150 FE FE NE13 NE12 BTS11 10 Mbti/s VLAN 100 NE11 TDM network E1 FE NE17 BSC
GE NE14
E1
FE NE16 BTS15 10 Mbit/s VLAN 120
NE15
Issue 03 (2011-04-10)
8-75
Figure 8-23 Board configuration (Ethernet services traversing a TDM network)

NE13 NE cascade
ISU2 ISU2 SP3S CSH ISU2 NE6 ISU2 EM6T
NE14
CSH ISU2 NE6 ISU2 EM6T
FE E1 BTS12
SP3S
NE12
NE11
CSH ISU2 NE6 ISU2 EFP8 SP3D
FE
SP3D
GE
E1 E1 E1 FE BTS11 TDM network E1 BTS16
CSH
CSH
CSH ISU2 ISU2 SP3S
NE6 ISU2
EM6T SP3S
NE6 ISU2
EM6T
NE6
EFP8 SP3D
NE16 FE BTS15
NE15 E1
NE17 FE
BSC
The connections of Ethernet links are described as follows. Table 8-57 Connections of Ethernet links (NE11) Link Between NE11 and the leased TDM network Between NE11 and BTS16 Port 2-SP3D(1-20) Description Configure these ports to be connected to the leased E1 lines. Configure this port to receive Ethernet services from and transmit Ethernet service to BTS16. PORT9 and PORT10 bridge between the EoPDH plane and the packet plane. PORT9 bridges the EoPDH plane and PORT10 bridges the packet plane. Configure this port to receive Ethernet services from and transmit Ethernet services to NE12.
4-EFP8-PORT1
4-EFP8-PORT9 4-EFP8-PORT10
3-ISU2 (main IF board of a 1 +1 HSB protection group) 5-ISU2 (standby IF board of a 1+1 HSB protection group)
8-76
Issue 03 (2011-04-10)
Table 8-58 Connections of Ethernet links (NE17) Link Between NE17 and the leased TDM network Between NE17 and the BSC Port 2-SP3D(1-20) Description Configure these ports to be connected to the leased E1 lines. Configure this port to aggregate the Ethernet services backhauled from the BTSs to the BSC.
4-EFP8-PORT1
NOTE
In this example, 20 E1 lines are used to transmit Ethernet services only. In actual networking scenarios, extra E1 lines need to be leased for transmitting E1 services.

You need to plan the corresponding parameter information before configuring an Ethernet service traversing a TDM network. 8.4.2.1 Service Planning (Ethernet Ports on the Packet Plane) This section provides the information about all the parameters required for configuring Ethernet ports on the packet plane. 8.4.2.2 Service Planning (Ethernet Services on the Packet Plane) This section provides the information about all the parameters required for configuring Ethernet services on the packet plane. 8.4.2.3 Service Planning (QoS on the Packet Plane) This section provides the information about all the parameters required for configuring QoS on the packet plane. 8.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board) This section provides the information about all the parameters required for configuring Ethernet ports on the EFP8 board. 8.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board) This section provides the information about all the parameters required for configuring Ethernet protection for the EFP8 board. 8.4.2.6 Service Planning (Ethernet Services on the EFP8 Board) This section provides the information about all the parameters required for configuring Ethernet services on the EFP8 board. 8.4.2.7 Service Planning (Cross-Connections) This section provides the information about all the parameters required for configuring Ethernet services. 8.4.2.8 Service Planning (QoS of the EFP8 Board) This section provides the information about all the parameters required for configuring QoS of the EFP8 board.
8.4.2.1 Service Planning (Ethernet Ports on the Packet Plane)

This section provides the information about all the parameters required for configuring Ethernet ports on the packet plane.

Table 8-59 provides the information about the Ethernet ports that transmit the Ethernet service. Table 8-59 Information about Ethernet ports (NE11) Parameter Encapsulation type Maximum frame length Flow control TAG attribute 4-EFP8-PORT10 802.1Q 1522 Disabled Tag Aware
NOTE
l In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag Aware. l In the case of the EFP8 board, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends. l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the maximum frame length according to the requirements of the specific BTS.

Table 8-60 provides the information about the IF_ETH ports that carry the Ethernet service. Table 8-60 Information about the IF_ETH port (NE11) Parameter Encapsulation type TAG attribute 3-ISU2 802.1Q Tag Aware 5-ISU2 802.1Q Tag Aware
8.4.2.2 Service Planning (Ethernet Services on the Packet Plane)

This section provides the information about all the parameters required for configuring Ethernet services on the packet plane. Table 8-61 provides the planning information about the Ethernet service.
8-78
Issue 03 (2011-04-10)
Table 8-61 Information about Ethernet services (NE11) Parameter Service ID Service name Service direction BPDU Source port Source C-VLAN Sink port Sink C-VLAN Between NE12 and the TDM Network 1 NE12toTDM_Vline UNI-UNI No transparent transmission 4-EFP8-PORT10 100, 110, 120 3-ISU2 100, 110, 120
8.4.2.3 Service Planning (QoS on the Packet Plane)

This section provides the information about all the parameters required for configuring QoS on the packet plane.
QoS (Diffserv)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 8-62. Each Ethernet port involved in the service uses the same DS configuration. Table 8-62 Service class and PHB service class PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) -
AF4
Issue 03 (2011-04-10)
8-79
VLAN Priority 3
AF2
AF1 BE
1 0
NOTE

8-80
Issue 03 (2011-04-10)

QoS (Port Shaping)

8.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)

This section provides the information about all the parameters required for configuring Ethernet ports on the EFP8 board.
Information About Ethernet External Ports

Table 8-64 and Table 8-65 provide the information about the Ethernet ports that transmit the Ethernet services. Table 8-64 Information about Ethernet external ports (NE11) Parameter Port enabled Port working mode Maximum frame length Flow control TAG attribute Entry detection Network attribute 4-EFP8-PORT1 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI 4-EFP8-PORT9 Enabled Auto-negotiation 1522 Disabled Tag Aware Enabled UNI
Table 8-65 Information about Ethernet external ports (NE17) Parameter Port enabled Port working mode Maximum frame length Flow control
Issue 03 (2011-04-10)
4-EFP8-PORT1 Enabled Auto-negotiation 1522 Disabled

Parameter TAG attribute Entry detection Network attribute
4-EFP8-PORT1 Tag Aware Enabled UNI
NOTE
l In this example, the FE ports on all the BTSes/BSC work in auto-negotiation mode. Therefore, the FE ports on the NEs that receive services from and transmit services to the BTSes/BSC must also work in auto-negotiation mode. If the peer Ethernet ports work in a mode other than the auto-negotiation mode, plan the local Ethernet ports to work in the same mode as the peer Ethernet ports. In the case of Ethernet ports within a network, plan the Ethernet ports to work in auto-negotiation mode. l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends. l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag Aware. l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

In EoPDH mode, a VCTRUNK can bind a maximum of 16 VC-12 channels. In this example, a total of 40 Mbit/s Ethernet bandwidth is required, that is, 20 VC-12 channels are occupied. Therefore, you need to configure two VCTRUNKs. In this example, configure the two VCTRUNKs with the same number of VC-12 channels and then create the two VCTRUNKs into a load-sharing LAG. Table 8-66 and Table 8-67 provide the information about the VCTRUNKs that are configured to transmit the Ethernet services. Table 8-66 Information about VCTRUNKs (NE11) Parameter TAG attribute Entry detection Network attribute Mapping protocol LCAS Bound paths 4-EFP8-VCTRUNK1 Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(1-10) 4-EFP8-VCTRUNK2 Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(11-20)
8-82
Issue 03 (2011-04-10)
Table 8-67 Information about VCTRUNKs (NE17) Parameter TAG attribute Entry detection Network attribute Mapping protocol LCAS Bound paths 4-EFP8-VCTRUNK1 Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(1-10) 4-EFP8-VCTRUNK2 Tag Aware Enabled UNI GFP Enabled VC4-1-VC12(11-20)
8.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board)

This section provides the information about all the parameters required for configuring Ethernet protection for the EFP8 board. According to the information about the VCTRUNKs in this example, you need to configure the two VCTRUNKs into a load-sharing LAG to increase the bandwidth. Table 8-68 and Table 8-69 provide the planning information of LAGs. Table 8-68 Information about the LAG (NE11) Parameter LAG type Revertive mode Load sharing type Load sharing mode System priority Main port Slave port NE11 Static aggregation Load sharing Load sharing based on IP 32768 4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
Table 8-69 Information about the LAG (NE17) Parameter LAG type Revertive mode Load sharing type Load sharing mode
Issue 03 (2011-04-10)
NE17 Static aggregation Load sharing Load sharing based on IP

8-83
Parameter System priority Main port Slave port
NE17 32768 4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2
8.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)

This section provides the information about all the parameters required for configuring Ethernet services on the EFP8 board. LAGs are created on NE1 and NE7 in this example. Therefore, you need to configure services only on the main ports. Table 8-70 and Table 8-71 provide the service planning information. Table 8-70 Information about Ethernet services (NE11) Parameter NE11 Between BTS16 and the TDM Network Board Service type Service direction Source port Source VLAN Sink port Sink VLAN 4-EFP8 EPL Bidirectional VCTRUNK1 150 PORT1 150 Between NE12 and the TDM Network 4-EFP8 EPL Bidirectional VCTRUNK1 100, 110, 120 PORT9 100, 110, 120
Table 8-71 Information about Ethernet services (NE17) Parameter NE17 Between the TDM Network and the BSC Board Service type Service direction Source port Source VLAN 4-EFP8 EPL Bidirectional VCTRUNK1 100, 110, 120, 150
8-84
Issue 03 (2011-04-10)
Parameter
NE17 Between the TDM Network and the BSC
Sink port Sink VLAN
PORT1 100, 110, 120, 150
8.4.2.7 Service Planning (Cross-Connections)

This section provides the information about all the parameters required for configuring Ethernet services. In this example, VC-12 timeslot cross-connections are set up between the first to twentieth VC-12 timeslots (bound with VCTRUNKs) in VC4-1 on the 4-EFP8 board and the first to twentieth ports on the 2-SP3D board. Table 8-72 and Table 8-73 provide the information about cross-connections of the Ethernet services. Table 8-72 Cross-connections of Ethernet services (NE11) Parameter Service level Service direction Source slot Source port Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range Value VC12 Bidirectional 4-EFP8 1 VC4-1 1-20 2-SP3D 1-20
Table 8-73 Cross-connections of Ethernet services (NE17) Parameter Service level Service direction Source slot Source port
Issue 03 (2011-04-10)
Value VC-12 Bidirectional 4-EFP8 1

Parameter Source VC4 Source timeslot range Sink slot Sink port Sink VC4 Sink timeslot range
Value VC4-1 1-20 2-SP3D 1-20
8.4.2.8 Service Planning (QoS of the EFP8 Board)

This section provides the information about all the parameters required for configuring QoS of the EFP8 board.
QoS (Flow)
Traffic classification is the prerequisite for configuring QoS of the EFP8 board. In this example, VLAN-based EVPL services are created. Therefore, you need to create PORT+VLAN-based flows. Table 8-74 and Table 8-75 provide the planning information of flows. Table 8-74 Flow parameters (NE11) Parameter Flow type Port VLAN ID Bound CAR ID Bound CoS ID Value PORT+VLANbased flow 4-EFP8-PORT1 150 1 PORT+VLANbased flow 4-EFP8-PORT9 100 1 PORT+VLANbased flow 4-EFP8-PORT9 110 1 PORT+VLANbased flow 4-EFP8-PORT9 120 1
Table 8-75 Flow parameters (NE17) Parameter Flow type Port VLAN ID Bound CAR ID
8-86
Value PORT+VLANbased flow 4-EFP8-PORT1 100 PORT+VLANbased flow 4-EFP8-PORT1 110 PORT+VLANbased flow 4-EFP8-PORT1 120 PORT+VLANbased flow 4-EFP8-PORT1 150 Issue 03 (2011-04-10)
Parameter Bound CoS ID
Value 1 1 1 1
NOTE
According to the service classes of the BTS services, CoS with the ID of 1 schedules BTS services with different VLAN priorities into egress queues with different forwarding priorities.
QoS (CAR)
In this example, CAR need not be configured.
QoS (CoS)
In this example, the BTS services are configured with corresponding VLAN priorities or DSCPs based on the service types. The EFP8 board performs CoS processing for a BTS service according to its VLAN priority or DSCP. In this example, BTSs allocate VLAN priorities to services according to the service types. Therefore, you need to configure CoS on Ethernet ports that receive services from and transmit services to the BTSs, according to the service types. Table 8-76 and Table 8-77 provide the CoS planning information. Table 8-76 CoS attributes of the EFP8 board (NE11 and NE17) Parameter CoS ID CoS type Value 1 VLAN priority
Table 8-77 CoS parameters and corresponding BTS service types of the EFP8 board (NE11 and NE17) CoS Parameter User priority 0 in the VLAN tag User priority 1 in the VLAN tag User priority 2 in the VLAN tag CoS Priority 0 Corresponding BTS Service Type HSDPA data services (HSPA interactive and HSPA background services) R99 non-real-time services (R99 interactive and R99 background services)
3 4
Issue 03 (2011-04-10)
8-87
CoS Parameter User priority 3 in the VLAN tag User priority 4 in the VLAN tag User priority 5 in the VLAN tag
CoS Priority 5
Corresponding BTS Service Type OM and HSDPA real-time services (OM streaming and HSPA streaming services) Real-time voice service and signaling service (R99 conversational and R99 streaming services) -
6 7
User priority 6 in the VLAN tag User priority 7 in the VLAN tag
7 7
NOTE
Queue 8 (namely, CoS priority 7) is the SP queue and queues 1 to 7 (namely, CoS priorities 0 to 6) are WRR queues. Therefore, you need to map all high-priority services into queue 8 so that high-priority services can be scheduled in time.
QoS (Shaping Based on the Egress Queues)

In this example, you need not configure traffic shaping based on the egress queues.

This section describes the process for data configuration. 8.4.3.1 Configuration Process (Ethernet Services on the Packet Plane) This section describes the process for configuring Ethernet services on the packet plane. 8.4.3.2 Configuration Process (Ethernet Ports on the Packet Plane) This section describes the process for configuring Ethernet ports on the packet plane. 8.4.3.3 Configuration Process (QoS on the Packet Plane) This section describes the procedure for configuring QoS on the packet plane. 8.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board) This section describes the process for configuring Ethernet ports on the EFP8 board. 8.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board) This section describes the process for configuring Ethernet protection on the EFP8 board. 8.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board) This section describes the process for configuring Ethernet services on the EFP8 board. 8.4.3.7 Configuration Process (Cross-Connections) This section describes the process for configuring the cross-connections.
8.4.3.8 Configuration Process (QoS on the EFP8 Board) This section describes the procedures for configuring QoS on the EFP8 board. 8.4.3.9 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.
8.4.3.1 Configuration Process (Ethernet Services on the Packet Plane)

This section describes the process for configuring Ethernet services on the packet plane.
Procedure
Step 1 See A.6.3.2 Configuring UNI-UNI E-Line Services and create the E-Line services. The values for the relevant parameters of NE11 are provided as follows. Parameter Value Between NE12 and the TDM Network Service ID Service Name Direction BPDU Source Interface Source VLAN ID Sink Interface Sink VLAN ID Port Name Encapsulation Type Tag 1 NE12toTDM_Vline UNI-UNI Not Transparently Transmitted 4-EFP8-PORT10 100, 110, 120 3-ISU2-1 100, 110, 120 4-EFP8-PORT10 802.1Q Tag Aware 3-ISU2-1 802.1Q Tag Aware
----End
8.4.3.2 Configuration Process (Ethernet Ports on the Packet Plane)

This section describes the process for configuring Ethernet ports on the packet plane.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic attributes of Ethernet ports. The values for the relevant parameters of NE11 are provided as follows.
Parameter
Value 4-EFP8-PORT10
Max Frame Length(byte)
1522
----End
8.4.3.3 Configuration Process (QoS on the Packet Plane)

This section describes the procedure for configuring QoS on the packet plane.
Procedure
NOTE
The mapping relationship defined in the default DS domain is the same as the mapping relationship defined in the DS domain that is created in this step. Therefore, you can skip this step.
The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Value 1 Default Map
8-90
Issue 03 (2011-04-10)
NOTE
NOTE
The values for the related parameters of NE12 are provided as follows. Port 3-ISU2-1 4-EFP8-PORT10 Packet Type CVLAN
Step 3 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the relevant parameters of NE11 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Parameter Policy Weight(%)
Value 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Step 4 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the relevant parameters of NE11 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2-1 4-EFP8-PORT10
----End
8.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board)

This section describes the process for configuring Ethernet ports on the EFP8 board.
Procedure
Step 1 See A.7.4.1 Configuring External Ethernet Ports and configure the Ethernet external ports. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8-PORT1 Enabled/Disabled Working Mode Maximum Frame Length Non-Autonegotiation Flow Control Mode Autonegotiation Flow Control Mode TAG Entry Detection Port Attributes
8-92
4-EFP8-PORT9 Enabled Auto-Negotiation 1522 Disabled Disabled Tag Aware Enabled UNI
Issue 03 (2011-04-10)
Enabled Auto-Negotiation 1522 Disabled Disabled Tag Aware Enabled UNI
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8-PORT1 Enabled/Disabled Working Mode Maximum Frame Length Non-Autonegotiation Flow Control Mode Autonegotiation Flow Control Mode TAG Entry Detection Port Attributes Enabled Auto-Negotiation 1522 Disabled Disabled Tag Aware Enabled UNI
Step 2 See A.7.4.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8-VCTRUNK1 TAG Entry Detection Mapping Protocol Port Attributes Enabling LCAS Level Direction Bound Path Tag Aware Enabled UNI GFP Enabled VC-12-Xv Bidirectional VC4-1-VC12(1-10) 4-EFP8-VCTRUNK2 Tag Aware Enabled UNI GFP Enabled VC-12-Xv Bidirectional VC4-1-VC12(11-20)
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8-VCTRUNK1 TAG Entry Detection Tag Aware Enabled 4-EFP8-VCTRUNK2 Tag Aware Enabled
Issue 03 (2011-04-10)
8-93
Parameter
Value 4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK2 UNI GFP Enabled VC-12-Xv Bidirectional VC4-1-VC12(11-20)
Mapping Protocol Port Attributes Enabling LCAS Level Direction Bound Path
UNI GFP Enabled VC-12-Xv Bidirectional VC4-1-VC12(1-10)
----End
8.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board)

This section describes the process for configuring Ethernet protection on the EFP8 board.
Procedure
Step 1 See A.7.1.1 Creating a LAG and create the LAGs. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8 LAG No LAG Name LAG Type Load Sharing Sharing Mode Main Port Selected Standby Ports 1 ToTDM Static Sharing IP Sharing Mode VCTRUNK1 VCTRUNK2
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8 LAG No LAG Name LAG Type
8-94
1 ToBSC Static
Issue 03 (2011-04-10)
Parameter
Value 4-EFP8
Load Sharing Sharing Mode Main Port Selected Standby Ports
Sharing IP Sharing Mode VCTRUNK1 VCTRUNK2
Step 2 See A.7.1.2 Setting Parameters for LAGs and set the parameters for LAGs. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8 LAG No LAG Name System Priority 1 ToTDM 32768
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8 LAG No LAG Name System Priority 1 ToBSC 32768
----End
8.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)

This section describes the process for configuring Ethernet services on the EFP8 board.
Procedure
Step 1 See A.7.2.1 Creating Ethernet Private Line Services and create the Ethernet private line services. l The values for the relevant parameters of NE11 are provided as follows.
Issue 03 (2011-04-10)
8-95
Parameter
Value Between BTS16 and the TDM Network Between NE12 and the TDM Network 4-EFP8 EPL Bidirectional VCTRUNK1 100, 110, 120 PORT9 100, 110, 120
Board Service Type Direction Source Port Source VLAN(e.g. 1,3-6) Sink Port Sink VLAN(e.g. 1,3-6)
4-EFP8 EPL Bidirectional VCTRUNK1 150 PORT1 150
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value Between the TDM Network and the BSC Board Service Type Direction Source Port Source VLAN(e.g. 1,3-6) Sink Port Sink VLAN(e.g. 1,3-6) 4-EFP8 EPL Bidirectional VCTRUNK1 100, 110, 120, 150 PORT1 100, 110, 120, 150
----End
8.4.3.7 Configuration Process (Cross-Connections)

This section describes the process for configuring the cross-connections.
Procedure
Step 1 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and create the service cross-connections. l The values for the relevant parameters of NE11 are provided as follows. Parameter Level
8-96
Value VC12
Issue 03 (2011-04-10)
Parameter Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
Value Bidirectional 4-EFP8 1 VC4-1 1-20 2-SP3D 1-20
l The values for the relevant parameters of NE17 are provided as follows. Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) Value VC-12 Bidirectional 4-EFP8 1 VC4-1 1-20 2-SP3D 1-20
----End
8.4.3.8 Configuration Process (QoS on the EFP8 Board)

This section describes the procedures for configuring QoS on the EFP8 board.
Procedure
Step 1 See A.7.7.1 Creating a Flow and create the flows. l The values for the relevant parameters of NE11 are provided as follows.
Issue 03 (2011-04-10)
8-97
Parameter
Value 4-EFP8
Flow Type Port VLAN ID
Port+VLAN Flow PORT1 150
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8 Flow Type Port VLAN ID Port+VLAN Flow PORT1 100 Port+VLAN Flow PORT1 110 Port+VLAN Flow PORT1 120 Port+VLAN Flow PORT1 150
Step 2 See A.7.7.3 Creating the CoS and create the CoS. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8 CoS ID CoS Type 1 VLAN priority
CoS Parameter User Priority 0 in the VLAN Tag User Priority 1 in the VLAN Tag User Priority 2 in the VLAN Tag User Priority 3 in the VLAN Tag User Priority 4 in the VLAN Tag User Priority 5 in the VLAN Tag User Priority 6 in the VLAN Tag User Priority 7 in the VLAN Tag
CoS Priority 0 3 4 5 6 7 7 7
8-98
Issue 03 (2011-04-10)
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8 CoS ID CoS Type 1 VLAN priority
CoS Parameter User Priority 0 in the VLAN Tag User Priority 1 in the VLAN Tag User Priority 2 in the VLAN Tag User Priority 3 in the VLAN Tag User Priority 4 in the VLAN Tag User Priority 5 in the VLAN Tag User Priority 6 in the VLAN Tag User Priority 7 in the VLAN Tag
CoS Priority 0 3 4 5 6 7 7 7
Step 3 See A.7.7.4 Binding the CAR/CoS and bind the CAR/CoS. l The values for the relevant parameters of NE11 are provided as follows. Parameter Value 4-EFP8 Flow Type Port C-VLAN Bound CAR Bound CoS Port+VLAN Flow PORT1 150 1 Port+VLAN Flow PORT9 100 1 Port+VLAN Flow PORT9 110 1 Port+VLAN Flow PORT9 120 1
l The values for the relevant parameters of NE17 are provided as follows. Parameter Value 4-EFP8 Flow Type Port+VLAN Flow Port+VLAN Flow Port+VLAN Flow Port+VLAN Flow
8-99
Issue 03 (2011-04-10)
Parameter
Value 4-EFP8
Port C-VLAN Bound CAR Bound CoS
PORT1 150 1
PORT1 100 1
PORT1 110 1
PORT1 120 1
----End

Procedure
Step 1 See A.7.8.1 Creating MDs and create the maintenance domain on NE11 and NE17. The values for the required parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE17 EdgeNE 4
Step 2 See A.7.8.2 Creating MAs and create the maintenance domain on NE11 and NE17. l The values for the relevant parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Value EdgeNE BTS16_Vline
l The values for the relevant parameters of NE17 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name
8-100
Value EdgeNE BTS11_Vline EdgeNE BTS12_Vline EdgeNE BTS15_Vline EdgeNE BTS16_Vline
Issue 03 (2011-04-10)
Step 3 See A.7.8.3 Creating MPs and create the maintenance domain on NE11 and NE17. l The values for the relevant parameters of NE11 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status CCM Sending Period(ms) Value EdgeNE BTS16_Vline 4-EFP8-PORT1 150 101 MEP Ingress Activate 1000
l The values for the relevant parameters of NE17 are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status CCM Sending Period(ms) Value EdgeNE BTS11_Vline EdgeNE BTS12_Vline EdgeNE BTS15_Vline EdgeNE BTS16_Vline
4-EFP8PORT1 100 701 MEP Ingress Activate 1000
Step 4 On NE17, perform an LB test to test the Ethernet service configurations. l Perform the LB test by considering the maintenance point whose MP ID is 706 as the source maintenance point and the maintenance point whose MP ID is 101 as the sink maintenance point.
l Perform the LB test by considering the maintenance point whose MP ID is 701 as the source maintenance point and the maintenance point whose MP ID is 201 as the sink maintenance point. l Perform the LB test by considering the maintenance point whose MP ID is 702 as the source MEP and the maintenance point whose MP ID is 401 as the sink MEP. l Perform the LB test by considering the maintenance point whose MP ID is 705 as the source MEP and the maintenance point whose MP ID is 601 as the sink MEP.
NOTE
The sink maintenance points whose MP IDs are 201, 401, and 601 need to be created on NE12 to NE16 respectively. The process for creating these sink maintenance points is not described in this section.
All LB tests should show that the tests are successful. ----End
8-102
Issue 03 (2011-04-10)
9 Configuring MPLS Tunnels
9
About This Chapter
Configuring MPLS Tunnels
Configuring MPLS tunnels is the prerequisite for configuring PWE3 services. 9.1 Basic Concept Before configuring MPLS tunnels, you need to be familiar with the basic concepts. 9.2 Configuration Procedure This section describes the procedures for configuring MPLS tunnels, MPLS OAM, MPLS APS, QoS, and the procedure for verifying the configurations. 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) This section uses an example to describe how to configure MPLS tunnels with MPLS APS protection on a PSN. 9.4 Configuration Example (MPLS Tunnels with No Protection) This section uses an example to describe how to configure MPLS tunnels with no protection on a PSN.
Issue 03 (2011-04-10)
9-1
9.1 Basic Concept

Before configuring MPLS tunnels, you need to be familiar with the basic concepts. 9.1.1 MPLS Network Architecture An MPLS network, also called an MPLS domain, is a network area that consists of interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network device that performs MPLS label switching and packet forwarding. 9.1.2 LSP Label switched paths (LSPs), also called MPLS tunnels, are classified into various types depending on different classification criteria. 9.1.3 Protection for MPLS Tunnels The OptiX RTN 950 supports 1:1 MPLS APS.
9.1.1 MPLS Network Architecture

An MPLS network, also called an MPLS domain, is a network area that consists of interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network device that performs MPLS label switching and packet forwarding. Figure 9-1 shows the MPLS network architecture. On an MPLS network, LSRs on the network edge are called label edge routers (LERs), and LSRs within the network range are called core LSRs. An LER may have one or more adjacent non-LSR nodes, but all the adjacent nodes of a core LSR are LSRs. Figure 9-1 MPLS network architecture
LER Other MPLS network
MPLS network
Other MPLS network LER
LER
LSR
Core LSR
LSR
LER
Other MPLS network
Packet transmission equipment
On an MPLS network, each LSR has a unique identifier; that is, a 16-byte LSR ID. An LSR ID can be based on the IPv4 address or IPv6 address.
NOTE
Currently, the OptiX RTN 950 supports only LSR IDs based on the IPv4 address.
9-2
Issue 03 (2011-04-10)
9.1.2 LSP
Label switched paths (LSPs), also called MPLS tunnels, are classified into various types depending on different classification criteria.
Basic Concepts of LSPs

On an MPLS network, an LSR adopts the same label switching mechanism to forward packets with the same characteristics. The packets with the same characteristics are called a forwarding equivalence class (FEC). The path along which an FEC travels through the MPLS network is called an LSP, or an MPLS tunnel. To provide a unified interface for upper-level applications of an LSP, the system needs to assign an ID to the LSP. This ID is called an LSP ID or tunnel ID. An LSP ID is 4-byte long, and is only valid for the local LSR. An LSP is unidirectional. As shown in Figure 9-2, LSRs on an LSP can be classified into the following types: l Ingress An LSP ingress node pushes a label onto the packet for MPLS packet encapsulation and forwarding. One LSP has only one ingress node. l Transit An LSP transit node swaps labels and forwards MPLS packets according to the label forwarding table. One LSP may have one or more transits nodes. l Egress An LSP egress node pops the label and recovers the packet for forwarding. One LSP has only one egress node. Figure 9-2 Classification of LSRs on an LSP
MPLS network
Other MPLS network Other MPLS network
Ingress
Transit
Transit
Egress
LSP
LSP Types
LSPs are classified into various types depending on different classification criteria. For details, see Table 9-1.
Table 9-1 LSP types Aspect Setup mode LSP Type Static tunnel Definition A static tunnel is set up according to the data configurations. A dynamic tunnel is set up by running the Label Distribution Protocol (LDP). A unidirectional tunnel is an LSP with one specific direction. A bidirectional tunnel is actually a pair of LSPs that have the same path but different directions. An E-LSP uses the EXP field for prioritizing packet scheduling. One ELSP supports PWs belonging to up to eight scheduling types. An L-LSP uses the MPLS label value for prioritizing packet scheduling priority. One L-LSP supports PWs belonging to one scheduling type. The TE tunnel has the preset bandwidth. The bandwidth is unlimited. When an egress node pops the MPLS tunnel label, it renews the packet scheduling priority according to the EXP field in the label. The OptiX RTN 950 supports the Pipe mode only. The OptiX RTN 950 supports both types. The OptiX RTN 950 supports both types. However, the OptiX RTN 950 does not support prioritizing packet discarding. The OptiX RTN 950 supports both types. Support Capability The OptiX RTN 950 supports static tunnels.
Dynamic tunnel
Direction
Unidirectional tunnel
Bidirectional tunnel
DiffServ identification mode
E-LSP
L-LSP
Bandwidth limit
TE tunnel Bandwidthunlimited tunnel
LSP mode
Uniform
9-4
Issue 03 (2011-04-10)
Aspect
LSP Type Pipe
Definition When an egress pops the MPLS tunnel label, it does not renew the packet scheduling priority.
Support Capability
9.1.3 Protection for MPLS Tunnels

The OptiX RTN 950 supports 1:1 MPLS APS. MPLS APS is a function that protects MPLS tunnels based on the APS protocol. MPLS APS improves reliability for service transmission in tunnels. With this function, when the working tunnel is faulty, the service can be switched to the preconfigured protection tunnel. The MPLS APS function supported by the OptiX RTN 950 has the following characteristics: l l l MPLS APS provides end-to-end protection for tunnels. The working tunnel and protection tunnel have the same ingress and egress nodes. The protection tunnel in an MPLS APS protection group does not carry extra traffic.
In MPLS APS, the MPLS OAM mechanism is used to detect faults in tunnels, and the ingress and egress nodes exchange APS protocol packets to achieve protection switching. As shown in Figure 9-3, when the MPLS OAM mechanism detects a fault in the working tunnel, the service is switched to the protection tunnel for transmission.
Issue 03 (2011-04-10)
9-5
Figure 9-3 MPLS APS

Transit
Working Tunnel Ingress Egress Protection Tunnel
Transit Protect switching Transit
Working Tunnel Ingress Egress Protection Tunnel
Transit Service Packet transmission equipment

This section describes the procedures for configuring MPLS tunnels, MPLS OAM, MPLS APS, QoS, and the procedure for verifying the configurations. Figure 9-4 provides the procedures for configuring MPLS tunnels.
9-6
Issue 03 (2011-04-10)
Figure 9-4 Configuration flow chart (MPLS tunnels)

Required Optional Set NNI port attributes Start
Create MPLS tunnels
Create MPLS protection groups
Set the QoS policy for NNI ports Verify configured MPLS tunnels End
The procedures in the configuration flow chart are described as follows. Table 9-2 Procedure for setting UNI port attributes Operation Setting attributes of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the major parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Port Mode to Layer 3. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is autonegotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. l Set Max Frame Length(byte) according to the service packet length. It is recommended that you set Max Frame Length(byte) to 1620.
Issue 03 (2011-04-10)
9-7
Operation A.5.6.2 Configuring the Traffic Control of Ethernet Ports
Description Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the major parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enabled . l When the external equipment uses the autonegotiation flow control function, set AutoNegotiation Flow Control Mode to Enabled. A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports Required. Set the major parameters as follows: l In the case of used ports, set Enable Tunnel to Enabled. l Set Specify IP Address to Manually. Set IP Address for each port according to planning information. The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment. Optional.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting attributes of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports
Required. Set the major parameters as follows: Set Port Mode to Layer 3.
l In the case of used ports, set Enable Tunnel to Enabled. l Set Specify IP Address to Manually. Set IP Address for each port according to planning information. The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment. Optional. The parameters need to be modified mainly in the following scenarios: l If the service at the MPLS interface is allowed to have bit errors, set Error Frame Discard Enabled to Disabled. l If the ISU2/ISX2 board has the licenses to enable Speed Air Interface Transmission at L2 and Speed Air Interface Transmission at L3, set the two parameters to Enabled. The two parameters must be set to same values at the two ends of a radio link.
9-8
Issue 03 (2011-04-10)
Procedure for Configuring an MPLS Tunnel

Table 9-3 Procedure for configuring an MPLS tunnel Operation A.8.2.1 Setting Basic MPLS Attributes Description Required. Set the major parameters as follows: l Set LSR ID according to planning information and ensure that the value is unique on the entire network. l Set Start of Global Label Space according to planning information. On an MPLS-enabled network, global label spaces of NEs are recommended to overlap each other if possible. Configuring an MPLS tunnel A.8.2.2 Creating a Unidirectional MPLS Tunnel Required if you need to configure a unidirectional MPLS tunnel. Set this parameter according to network planning information. Required if you need to configure a bidirectional MPLS tunnel. Set this parameter according to network planning information. Required when the dynamic ARP protocol cannot obtain the next-hop MAC address. Set the parameters as follows: l ARP List IP Address: Specifies the IP address of the next-hop port. l ARP List MAC: Specifies the MAC address of the next-hop port.
A.8.2.3 Creating a Bidirectional MPLS Tunnel
A.8.1.1 Creating ARP Static Entries
Issue 03 (2011-04-10)
9-9
Procedure for Configuring Protection for MPLS Tunnels

Table 9-4 Procedure for configuring protection for MPLS tunnels Operation A.8.2.6 Setting MPLS OAM Parameters Description Required when you need to configure an MPLS APS protection group. l For a bidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. It is recommended that you set Detection Mode to Auto-Sensing. When you need to create an MPLS APS protection group, set Detection Packet Type to FFD and set Detection Packet Period(ms) to 3.3. This ensures that the switching time is less than 100 ms. Set SD Threshold and SF Threshold as required. l For the ingress node of a unidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. When you need to create an MPLS APS protection group, set Detection Packet Type to FFD and set Detection Packet Period(ms) to 3.3. This ensures that the switching time is less than 100 ms. Select the corresponding reverse tunnel. l For the egress node of a unidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. Set Detection Mode to Auto-Sensing. Select the corresponding reverse tunnel. Set SD Threshold and SF Threshold as required.
9-10
Issue 03 (2011-04-10)
Operation A.8.3.1 Creating an MPLS APS Protection Group
Description Required when you need to configure protection for services carried on an MPLS tunnel. l The protection tunnel must be created. l When creating an APS protection group, set Protocol Status to Disabled. Start the protocol only when the APS protection group is successfully created on nodes at both ends. l Set the parameters of the protection group according to network planning information.
Procedure for Configuring QoS at an MPLS Interface

Table 9-5 Configuring QoS Operation Configuring Diffserv A.6.7.2 Modifying the Mapping Relationshi ps for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types Configuring the port policy A.6.7.4 Creating a Port Policy Description When the default mapping between the DS domain and the PHB service classes does not meet network requirements, perform this operation to change the mapping.
Required. Set Packet Type at each MPLS interface to MPLS-EXP.
Required when the queue scheduling algorithm needs to be changed or the shaping function needs to be enabled for the egress queues at an MPLS interface. The parameters need to be set according to the network planning information.
A.6.7.7 Setting the Port That Uses the Port Policy
Required after a new port policy is created. The parameters need to be set according to the network planning information.
Issue 03 (2011-04-10)
9-11
Operation A.6.7.8 Configuring Port Shaping
Description Required when the shaping function needs to enabled for egress queues. The parameters need to be set according to the network planning information.
Procedure for Verifying Created MPLS Tunnels

Table 9-6 Procedure for verifying created MPLS tunnels Operation A.8.2.6 Setting MPLS OAM Parameters Description Required. Before you create an MPLS APS protection group, you need to enable the MPLS OAM function to detect the tunnel status. When you need to check availability of MPLS tunnels, it is recommended that you set Detection Packet Type to CV. A.8.2.9 Querying LSP Running Status Required.
9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)

This section uses an example to describe how to configure MPLS tunnels with MPLS APS protection on a PSN. 9.3.1 Networking Diagram The section describes the networking information about the NEs. 9.3.2 Service Planning You need to plan the corresponding parameter information before service configuration. 9.3.3 Configuration Process This section describes how to set parameters of MPLS tunnel.

The section describes the networking information about the NEs. All base station services need to be transmitted through a PSN to the BSC and RNC. Based on 5.7 Configuration Example (Radio Links on the Packet Network), configure MPLS tunnels on the packet ring according to the following actual requirements: l Bidirectional MPLS tunnels are configured between NE31 and NE11, between NE31 and NE21, and between NE31 and NE32.
9-12
l l
MPLS APS protection is configured for each tunnel on the packet ring to ensure service availability upon a tunnel fault. MPLS interfaces used on the packet ring are shown in Figure 9-5.
Figure 9-5 Networking diagram (packet ring network)

NE34 NE33
2-EM6F-1(to NE11) 2-EM6F-2(to NE31) GE NE32 NE11 2-EM6F-1(to NE21) 2-EM6F-2(to NE32) 1-EM6F-1(to NE31) 1-EM6F-2(to NE11) GE NE21 NE31 GE 1-EM6F-2(to NE21) GE 1-EM6F-1(to NE32)

You need to plan the corresponding parameter information before service configuration. 9.3.2.1 Service Planning (MPLS Interfaces) This section provides the information about all the parameters required for configuring MPLS interfaces. 9.3.2.2 Service Planning (MPLS Tunnel) The service planning information contains the information about all the parameters required for configuring MPLS tunnels. 9.3.2.3 Service Planning (MPLS Tunnel APS) The service planning information contains the information about all the parameters required for configuring MPLS tunnel APS. 9.3.2.4 Service Planning (QoS) This section provides the information about all the parameters required for configuring QoS for MPLS interface.
9.3.2.1 Service Planning (MPLS Interfaces)

This section provides the information about all the parameters required for configuring MPLS interfaces. Table 9-7 to Table 9-10 provide the information about each NNI port involved in the service.
Table 9-7 Information about MPLS interfaces (NE31) Parameter Port name Port enabled Port mode Port working mode Maximum frame length (byte) Flow control Enable tunnel Specify IP address Port IP address IP mask Loopback check Loopback port shutdown Enabling broadcast packet suppression 1-EM6F-1 conn_NE32 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.1 255.255.255.252 Disabled Disabled Disabled 1-EM6F-2 conn_NE21 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.14 255.255.255.252 Disabled Disabled Disabled
Table 9-8 Information about MPLS interfaces (NE32) Parameter Port name Port enabled Port mode Port working mode Maximum frame length (byte) Flow control Enable tunnel Specify IP address Port IP address IP mask Loopback check 2-EM6F-1 conn_NE11 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.5 255.255.255.252 Disabled 2-EM6F-2 conn_NE31 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.2 255.255.255.252 Disabled
9-14
Issue 03 (2011-04-10)
Parameter Loopback port shutdown Enabling broadcast packet suppression
2-EM6F-1 Disabled Disabled
2-EM6F-2 Disabled Disabled
Table 9-9 Information about MPLS interfaces (NE11) Parameter Port name Port enabled Port mode Port working mode Maximum frame length (byte) Flow control Enable tunnel Specify IP address Port IP address IP mask Loopback check Loopback port shutdown Enabling broadcast packet suppression 2-EM6F-1 conn_NE21 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.9 255.255.255.252 Disabled Disabled Disabled 2-EM6F-2 conn_NE32 Enabled Layer 3 Auto-negotiation 1620 Disabled Enabled Manually 46.1.64.6 255.255.255.252 Disabled Disabled Disabled
Table 9-10 Information about MPLS interfaces (NE21) Parameter Port name Port enabled Port mode Port working mode Maximum frame length (byte) Flow control
Issue 03 (2011-04-10)
1-EM6F-1 conn_NE31 Enabled Layer 3 Auto-negotiation 1620 Disabled

1-EM6F-2 conn_NE11 Enabled Layer 3 Auto-negotiation 1620 Disabled

9-15
Parameter Enable tunnel Specify IP address Port IP address IP mask Loopback check Loopback port shutdown Enabling broadcast packet suppression
1-EM6F-1 Enabled Manually 46.1.64.13 255.255.255.252 Disabled Disabled Disabled
1-EM6F-2 Enabled Manually 46.1.64.10 255.255.255.252 Disabled Disabled Disabled
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire network in a unified manner. l In this example, all GE ports on the packet network are set to the auto-negotiation mode. l The maximum frame length for each MPLS interface is set to 1620, because an Ethernet frame carrying MPLS packet is longer than a Native Ethernet frame. l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient QoS capabilities. The planning information of flow control must be the same for the equipment at both ends. l An MPLS interface does not carry E-LAN services, so the loopback check, loopback port shutdown, and broadcast packet suppression functions do not need to be enabled for Ethernet ports.
9.3.2.2 Service Planning (MPLS Tunnel)

The service planning information contains the information about all the parameters required for configuring MPLS tunnels.
Basic NE Configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE as its unique ID on the network. See Table 9-11. Table 9-11 Basic NE configuration Parameter LSR ID Start of global label space NE31 130.0.0.1 0 NE32 130.0.0.2 0 NE11 130.0.0.3 0 NE21 130.0.0.4 0
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 9.4 Configuration Example (MPLS Tunnels with No Protection).
9-16
Issue 03 (2011-04-10)
Information About MPLS Tunnels

Table 9-12 provides basic information about the working and protection tunnels between NE31 and NE32, between NE31 and NE11, and between NE31 and NE21. Table 9-12 Basic information about MPLS tunnels Parameter Working tunnel Protection tunnel Tunnel name Tunnel ID Tunnel name Tunnel ID Between NE31 and NE32 NE31-NE32-W 1501 NE31-NE32-P 1507 NE31 Between NE31 and NE11 NE31-NE11-W 1503 NE31-NE11-P 1509 NE31 Between NE31 and NE21 NE31-NE21-W 1505 NE31-NE21-P 1511 NE31
Ingress node of the forward working tunnel
Figure 9-6 shows the specific tunnel information. Figure 9-6 MPLS tunnel planning
Links-1: NE31 - NE32 - NE11 -NE21 -NE31 NE31 (46.1.4.1) 1-EM6F-1 (46.1.64.1) L:1501 L:1502 L:1505 L:1506 L:1503 L:1504 ID:1511 ID:1503 ID:1501 NE32 (46.1.4.2) 2-EM6F-2 2-EM6F-1 (46.1.64.2) (46.1.64.5) L:1501 L:1507 L:1502 L:1508 L:1505 L:1509 L:1506 L:1510 L:1503 L:1511 L:1504 L:1512 NE11 (46.1.4.3) 2-EM6F-2 2-EM6F-1 (46.1.64.6) (46.1.64.9) L:1507 L:1501 L:1508 L:1502 L:1509 L:1503 L:1510 L:1504 L:1511 L:1505 L:1512 L:1506 NE21 (46.1.4.4) 1-EM6F-2 1-EM6F-1 (46.1.64.10) (46.1.64.13) L:1501 L:1507 L:1502 L:1508 L:1503 L:1509 L:1504 L:1510 L:1505 L:1511 L:1506 L:1512 ID:1507 NE31 (46.1.4.1) 1-EM6F-2 (46.1.64.14) L:1507 L:1508 ID:1509 ID:1505 L:1509 L:1510 L:1511 L:1512
Ingress/Egress L: Label Working tunnel Protection tunnel
NOTE
l Next Hop Address represents the port IP address of the next-hop node. In Figure 9-6, the IP addresses under board names are port IP addresses. l Generally, it is recommended that you set Bandwidth(kbit/s) to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth.
9.3.2.3 Service Planning (MPLS Tunnel APS)

The service planning information contains the information about all the parameters required for configuring MPLS tunnel APS.
Information About MPLS OAM

MPLS APS is configured on the packet ring network to improve service reliability. Before creating an MPLS APS protection group, you need to enable the MPLS OAM function. Table 9-13 to Table 9-16 provide the planning information about MPLS OAM. Table 9-13 Information about MPLS OAM (NE31) Paramete r Tunnel ID OAM status Detection mode Detection packet type Detection packet period (ms) Between NE31 and NE32 1501 Enabled Autosensing FFD 1507 Enabled Autosensing FFD Between NE31 and NE11 1503 Enabled Autosensing FFD 1509 Enabled Autosensing FFD Between NE31 and NE21 1505 Enabled Autosensing FFD 1511 Enabled Autosensing FFD
3.3
3.3
3.3
3.3
3.3
3.3
Table 9-14 Information about MPLS OAM (NE32) Parameter Tunnel ID OAM status Detection mode Detection packet type Detection packet period (ms) Between NE31 and NE32 1501 Enabled Auto-sensing FFD 3.3 1507 Enabled Auto-sensing FFD 3.3
Table 9-15 Information about MPLS OAM (NE11) Parameter Tunnel ID Node type OAM status Detection mode
9-18
Between NE31 and NE11 1503 Egress Enabled Auto-sensing 1509 Egress Enabled Auto-sensing
Issue 03 (2011-04-10)
Parameter Detection packet type Detection packet period (ms)
Between NE31 and NE11 FFD 3.3 FFD 3.3
Table 9-16 Information about MPLS OAM (NE21) Parameter Tunnel ID OAM status Detection mode Detection packet type Detection packet period (ms) Between NE31 and NE21 1505 Enabled Auto-sensing FFD 3.3 1511 Enabled Auto-sensing FFD 3.3
Information About MPLS APS Protection Groups

Based on the planning MPLS tunnel information, MPLS APS protection groups are planned as shown Table 9-17 to Table 9-20. Table 9-17 Information about MPLS APS protection groups (NE31) Parameter Tunnel type Working ingress tunnel ID Working egress tunnel ID Protection ingress tunnel ID Protection egress tunnel ID Protection type WTR time (m) Hold-off time Protocol status Between NE31 and NE32 MPLS tunnel 1501 1501 1507 1507 1:1 dual-ended revertive mode 5 0 Disabled Between NE31 and NE11 MPLS tunnel 1503 1503 1509 1509 1:1 dual-ended revertive mode 5 0 Disabled Between NE31 and NE21 MPLS tunnel 1505 1505 1511 1511 1:1 dual-ended revertive mode 5 0 Disabled
Issue 03 (2011-04-10)
9-19
Table 9-18 Information about MPLS APS protection groups (NE32) Parameter Tunnel type Working ingress tunnel ID Working egress tunnel ID Protection ingress tunnel ID Protection egress tunnel ID Protection type WTR time (m) Hold-off time Protocol status Between NE31 and NE32 MPLS tunnel 1501 1501 1507 1507 1:1 dual-ended revertive mode 5 0 Disabled
Table 9-19 Information about MPLS APS protection groups (NE11) Parameter Tunnel type Working ingress tunnel ID Working egress tunnel ID Protection ingress tunnel ID Protection egress tunnel ID Protection type WTR time (m) Hold-off time Protocol status Between NE31 and NE11 MPLS tunnel 1503 1503 1509 1509 1:1 dual-ended revertive mode 5 0 Disabled
Table 9-20 Information about MPLS APS protection groups (NE21) Parameter Tunnel type Working ingress tunnel ID Working egress tunnel ID Protection ingress tunnel ID Between NE31 and NE21 MPLS tunnel 1505 1505 1511
9-20
Issue 03 (2011-04-10)
Parameter Protection egress tunnel ID Protection type WTR time (m) Hold-off time Protocol status
Between NE31 and NE21 1511 1:1 dual-ended revertive mode 5 0 Disabled
NOTE
In this example, MPLS APS is configured as the only protection scheme on the packet ring network. Therefore, set Hold-Time(100ms) to 0.

This section provides the information about all the parameters required for configuring QoS for MPLS interface.
NOTE
The NEs in this example and in 9.4 Configuration Example (MPLS Tunnels with No Protection) are on the same MPLS network, so the QoS planning for the NEs is the same.
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX RTN 950, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ information is planned in a unified manner. Table 9-21 lists the mapping between the DS domain and PHB service classes. Table 9-21 Classes of Service and PHB Service Classes PHB Service Class CS7 CS6 EF VLAN Priority 7 6 5 DSCP MPLS EXP Priority 7 6 5 Correspondin g Service Category Real-time voice service and signaling service (R99 conversational and R99 streaming services) 9-21
56 48 40
AF4
Issue 03 (2011-04-10)
32
VLAN Priority 3
DSCP
MPLS EXP Priority 3
Correspondin g Service Category OM, real-time HSDPA services (OM, HSPA streaming) R99 non-realtime services (R99 interactive and R99 background services) HSDPA data services (HSPA interactive and HSPA background services)
24
AF2
16
AF1 BE
1 0
8 0
1 0
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 9-22 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 9-22 Queue scheduling mode PHB Service Class CS7 CS6 EF AF4 AF3
9-22
Queue Scheduling Mode SP SP SP WRR (weight = 5) WRR (weight = 60)
Issue 03 (2011-04-10)
PHB Service Class AF2 AF1 BE
Queue Scheduling Mode WRR (weight = 30) WRR (weight = 5) SP

This section describes how to set parameters of MPLS tunnel. 9.3.3.1 Configuration Process (NNI Ports) This section describes the process for configuring NNI port information. 9.3.3.2 Configuration Process (MPLS Tunnel) This section describes the process for configuring MPLS tunnels. 9.3.3.3 Configuration Process (MPLS APS) This section describes the process for configuring MPLS APS protection groups. 9.3.3.4 Configuration Process (QoS) This section describes the process for configuring QoS information for MPLS interfaces. 9.3.3.5 Configuration Process (Verifying Configured MPLS Tunnels) This section describes the process for verifying configured MPLS tunnels.
9.3.3.1 Configuration Process (NNI Ports)

This section describes the process for configuring NNI port information.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the basic port attributes. l The values for the related parameters of NE31 are provided as follows. Parameter Value 1-EM6F-1 Name Enable Port Port Mode Working Mode Max Frame Length(byte) conn_NE32 Enabled Layer 3 Auto-Sensing 1620 1-EM6F-2 conn_NE21 Enabled Layer 3 Auto-Sensing 1620
Issue 03 (2011-04-10)
9-23
Parameter
Value 2-EM6F-1 2-EM6F-2 conn_NE31 Enabled Layer 3 Auto-Sensing 1620
Name Enable Port Port Mode Working Mode Max Frame Length(byte)
conn_NE11 Enabled Layer 3 Auto-Sensing 1620
l The values for the related parameters of NE11 are provided as follows. Parameter Value 2-EM6F-1 Name Enable Port Port Mode Working Mode Max Frame Length(byte) conn_NE21 Enabled Layer 3 Auto-Sensing 1620 2-EM6F-2 conn_NE32 Enabled Layer 3 Auto-Sensing 1620
l The values for the related parameters of NE21 are provided as follows. Parameter Value 1-EM6F-1 Name Enable Port Port Mode Working Mode Max Frame Length(byte) conn_NE31 Enabled Layer 3 Auto-Sensing 1620 1-EM6F-2 conn_NE11 Enabled Layer 3 Auto-Sensing 1620
Step 2 See A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports and set the Layer 3 attributes of the ports. l The values for the related parameters of NE31 are provided as follows. Parameter Value 1-EM6F-1 Enable Tunnel Enabled 1-EM6F-2 Enabled
9-24
Issue 03 (2011-04-10)
Parameter
Value 1-EM6F-1 1-EM6F-2 Manually 46.1.64.14 255.255.255.252
Specify IP Address IP Address IP Mask
Manually 46.1.64.1 255.255.255.252
l The values for the related parameters of NE32 are provided as follows. Parameter Value 2-EM6F-1 Enable Tunnel Specify IP Address IP Address IP Mask Enabled Manually 46.1.64.5 255.255.255.252 2-EM6F-2 Enabled Manually 46.1.64.2 255.255.255.252
----End
Issue 03 (2011-04-10)
9-25
9.3.3.2 Configuration Process (MPLS Tunnel)

This section describes the process for configuring MPLS tunnels.
Procedure
Step 1 See A.8.2.1 Setting Basic MPLS Attributes and set the LSR ID for each NE. The values for the related parameters of each NE are provided as follows. Parameter Value NE31 LSR ID Start of Global Label Space 130.0.0.1 0 NE32 130.0.0.2 0 NE11 130.0.0.3 0 NE21 130.0.0.4 0
Step 2 See A.8.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels. 1. Create the working MPLS tunnels. l The values for the related parameters of NE31 are provided as follows. Parameter Value Between NE31 and NE32 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label 1501 NE31-NE32-W Ingress No Limit 1-EM6F 1 1501 1502 Between NE31 and NE11 1503 NE31-NE11-W Ingress No Limit 1-EM6F 1 1503 1504 Between NE31 and NE21 1505 NE31-NE21-W Ingress No Limit 1-EM6F 2 1505 1506
9-26
Issue 03 (2011-04-10)
Parameter
Value Between NE31 and NE32 Between NE31 and NE11 46.1.64.2 130.0.0.3 E-LSP None Pipe Between NE31 and NE21 46.1.64.13 130.0.0.4 E-LSP None Pipe
Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
46.1.64.2 130.0.0.2 E-LSP None Pipe
l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE31 and NE32 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address
Issue 03 (2011-04-10)
Between NE31 and NE11 1503 NE31-NE11-W Transit No Limit 2-EM6F 2 1503 1504 2-EM6F 1 1509 1510 46.1.64.6 46.1.64.1
1501 NE31-NE32-W Egress No Limit 2-EM6F 2 1501 1502 46.1.64.1
9-27
Parameter
Value Between NE31 and NE32 Between NE31 and NE11 130.0.0.1 130.0.0.3 E-LSP -
Source Node Sink Node Tunnel Type EXP LSP Mode
130.0.0.1 E-LSP None Pipe
l The values for the related parameters of NE11 are provided as follows. Parameter Value Between NE31 and NE11 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode 1503 NE31-NE11-W Egress No Limit 2-EM6F 2 1503 1504 46.1.64.5 130.0.0.1 E-LSP None Pipe
9-28
Issue 03 (2011-04-10)
l The values for the related parameters of NE21 are provided as follows. Parameter Value Between NE31 and NE21 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode 2. Create the protection MPLS tunnels. l The values for the related parameters of NE31 are provided as follows. Parameter Value Between NE31 and NE32 Tunnel ID Tunnel Name Node Type CIR(kbit/s) 1507 NE31-NE32-P Ingress No Limit Between NE31 and NE11 1509 NE31-NE11-P Ingress No Limit Between NE31 and NE21 1511 NE31-NE21-P Ingress No Limit 1505 NE31-NE21-W Egress No Limit 1-EM6F 1 1505 1506 46.1.64.14 130.0.0.1 E-LSP None Pipe
Issue 03 (2011-04-10)
9-29
Parameter
Value Between NE31 and NE32 Between NE31 and NE11 1-EM6F 2 1509 1510 46.1.64.13 130.0.0.3 E-LSP None Pipe Between NE31 and NE21 1-EM6F 1 1511 1512 46.1.64.2 130.0.0.4 E-LSP None Pipe
In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
1-EM6F 2 1507 1508 46.1.64.13 130.0.0.2 E-LSP None Pipe
l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE31 and NE32 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type 1507 NE31-NE32-P Egress No Limit 2-EM6F Between NE31 and NE21 1511 NE31-NE21-P Transit No Limit 2-EM6F
9-30
Issue 03 (2011-04-10)
Parameter
Value Between NE31 and NE32 Between NE31 and NE21 2 1511 1512 2-EM6F 1 1511 1512 46.1.64.6 46.1.64.1 130.0.0.1 130.0.0.4 E-LSP -
In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
1 1507 1508 46.1.64.6 130.0.0.1 E-LSP None Pipe
l The values for the related parameters of NE11 are provided as follows. Parameter Value Between NE31 and NE11 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label 1509 NE31-NE11-P Egress No Limit 2-EM6F 1 1509 Between NE31 and NE32 1507 NE31-NE32-P Transit No Limit 2-EM6F 1 1507 Between NE31 and NE21 1511 NE31-NE21-P Transit No Limit 2-EM6F 2 1511
Issue 03 (2011-04-10)
9-31
Parameter
Value Between NE31 and NE11 Between NE31 and NE32 1508 2-EM6F 2 1507 1508 46.1.64.5 46.1.64.10 130.0.0.1 130.0.0.2 E-LSP Between NE31 and NE21 1512 2-EM6F 1 1511 1512 46.1.64.10 46.1.64.5 130.0.0.1 130.0.0.4 E-LSP -
Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
1510 46.1.64.10 130.0.0.1 E-LSP None Pipe
l The values for the related parameters of NE21 are provided as follows. Parameter Value Between NE31 and NE21 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label 1511 NE31-NE21-P Egress No Limit 1-EM6F 2 1511 1512 Between NE31 and NE32 1507 NE31-NE32-P Transit No Limit 1-EM6F 1 1507 1508
9-32
Issue 03 (2011-04-10)
Parameter
Value Between NE31 and NE21 Between NE31 and NE32 1-EM6F 2 1507 1508 46.1.64.9 46.1.64.14 130.0.0.1 130.0.0.2 E-LSP -
Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
46.1.64.9 130.0.0.1 E-LSP None Pipe
----End
9.3.3.3 Configuration Process (MPLS APS)

This section describes the process for configuring MPLS APS protection groups.
Procedure
Step 1 See A.8.2.6 Setting MPLS OAM Parameters and set MPLS OAM parameters. l The values for the related parameters of NE31 are provided as follows. Paramet er Value Between NE31 and NE32 1501 Enabled AutoSensing 1507 Enabled AutoSensing Between NE31 and NE11 1503 Enabled AutoSensing 1509 Enabled AutoSensing Between NE31 and NE21 1505 Enabled AutoSensing 1511 Enabled AutoSensing
Tunnel ID OAM Status Detection Mode
Issue 03 (2011-04-10)
9-33
Paramet er
Value Between NE31 and NE32 FFD FFD Between NE31 and NE11 FFD FFD Between NE31 and NE21 FFD FFD
Detection Packet Type Detection Packet Period (ms)
3.3
3.3
3.3
3.3
3.3
3.3
l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE31 and NE32 Tunnel ID OAM Status Detection Mode Detection Packet Type Detection Packet Period (ms) 1501 Enabled Auto-Sensing FFD 3.3 1507 Enabled Auto-Sensing FFD 3.3
l The values for the related parameters of NE11 are provided as follows. Parameter Value Between NE31 and NE11 Tunnel ID OAM Status Detection Mode Detection Packet Type Detection Packet Period (ms) 1503 Enabled Auto-Sensing FFD 3.3 1509 Enabled Auto-Sensing FFD 3.3
l The values for the related parameters of NE21 are provided as follows. Parameter Tunnel ID OAM Status
9-34
Between NE31 and NE21 1505 Enabled 1511 Enabled

Issue 03 (2011-04-10)
Parameter Detection Mode Detection Packet Type Detection Packet Period (ms)
Between NE31 and NE21 Auto-Sensing FFD 3.3 Auto-Sensing FFD 3.3
Step 2 See A.8.3.1 Creating an MPLS APS Protection Group and create the MPLS APS protection group. l The values for the related parameters of NE31 are provided as follows. Parameter Value Between NE31 and NE32 Protection Type Switching Mode Working Tunnel Type Working Ingress Tunnel ID Working Egress Tunnel ID Protection Tunnel Type Protection Ingress Tunnel ID Protection Egress Tunnel ID Revertive Mode WTR Time(m) Hold-Time(100ms) Protocol Status 1:1 Dual-Ended MPLS Tunnel 1501 1501 MPLS Tunnel 1507 1507 Non-Revertive 5 0 Disabled Between NE31 and NE11 1:1 Dual-Ended MPLS Tunnel 1503 1503 MPLS Tunnel 1509 1509 Non-Revertive 5 0 Disabled Between NE31 and NE21 1:1 Dual-Ended MPLS Tunnel 1505 1505 MPLS Tunnel 1511 1511 Non-Revertive 5 0 Disabled
l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE31 and NE32 Protection Type 1:1
Issue 03 (2011-04-10)
9-35
Parameter
Value Between NE31 and NE32
Switching Mode Working Tunnel Type Working Ingress Tunnel ID Working Egress Tunnel ID Protection Tunnel Type Protection Ingress Tunnel ID Protection Egress Tunnel ID Revertive Mode WTR Time(m) Hold-Time(100ms) Protocol Status
Dual-Ended MPLS Tunnel 1501 1501 MPLS Tunnel 1507 1507 Non-Revertive 5 0 Disabled
l The values for the related parameters of NE11 are provided as follows. Parameter Value Between NE31 and NE11 Protection Type Switching Mode Working Tunnel Type Working Ingress Tunnel ID Working Egress Tunnel ID Protection Tunnel Type Protection Ingress Tunnel ID Protection Egress Tunnel ID Revertive Mode WTR Time(m) Hold-Time(100ms) Protocol Status 1:1 Dual-Ended MPLS Tunnel 1503 1503 MPLS Tunnel 1509 1509 Non-Revertive 5 0 Disabled
9-36
Issue 03 (2011-04-10)
Parameter
Protection Type Switching Mode Working Tunnel Type Working Ingress Tunnel ID Working Egress Tunnel ID Protection Tunnel Type Protection Ingress Tunnel ID Protection Egress Tunnel ID Revertive Mode WTR Time(m) Hold-Time(100ms) Protocol Status
1:1 Dual-Ended MPLS Tunnel 1505 1505 MPLS Tunnel 1511 1511 Non-Revertive 5 0 Disabled
Step 3 See A.8.3.4 Enabling/Disabling MPLS APS Protection and start/stop the MPLS APS protocol. If Protocol Status is Enabled, the MPLS APS protocol is enabled for the NE where the MPLS APS protection group is configured. ----End

This section describes the process for configuring QoS information for MPLS interfaces.
Procedure
Step 1 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet type. The values for the related parameters that need to be set are provided as follows. Parameter Value NE31 Port 1-EM6F-1 1-EM6F-2 Packet Type mpls-exp NE32 2-EM6F-1 2-EM6F-2 mpls-exp NE11 2-EM6F-1 2-EM6F-2 mpls-exp NE21 1-EM6F-1 1-EM6F-2 mpls-exp
Step 2 See A.6.7.4 Creating a Port Policy and create the port policy.
l The values for the related parameters of each NE are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and specify the ports that use the port policy. l The values for the related parameters of NE31 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 1-EM6F-1 1-EM6F-2
l The values for the related parameters of NE32 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 2-EM6F-1 2-EM6F-2
l The values for the related parameters of NE11 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 2-EM6F-1 2-EM6F-2
9-38
Issue 03 (2011-04-10)
Parameter
Port
1-EM6F-1 1-EM6F-2
----End
9.3.3.5 Configuration Process (Verifying Configured MPLS Tunnels)

This section describes the process for verifying configured MPLS tunnels.
Procedure
Step 1 For MPLS tunnels configured in an MPLS APS protection group, see A.8.2.9 Querying LSP Running Status and query the LSP running status. Normally, each MPLS tunnel is available. ----End
9.4 Configuration Example (MPLS Tunnels with No Protection)

This section uses an example to describe how to configure MPLS tunnels with no protection on a PSN. 9.4.1 Networking Diagram This section describes the networking information about the NEs. 9.4.2 Service Planning You need to plan the corresponding parameter information before service configuration. 9.4.3 Configuration Process This section describes how to set parameters of MPLS tunnel.

This section describes the networking information about the NEs. All base station services need to be transmitted through a PSN to the BSC and RNC. Based on 5.7 Configuration Example (Radio Links on the Packet Network), configure MPLS tunnels on Packet radio links according to the following actual requirements: l l l Bidirectional MPLS tunnels need to be configured between NE32 and NE33 and between NE32 and NE34. MPLS APS is not configured for any tunnel on Packet radio links. MPLS interfaces used on the Packet radio links are shown in Figure 9-7. 1+1 HSB protection is configured for the radio links between NE32 and NE33. In the 1+1 HSB
Issue 03 (2011-04-10)
protection group, the IF board in the slot with the smaller slot number functions as the main IF board. Figure 9-7 Networking diagram (Packet radio links)
3-ISU2-1(to NE34) 4-ISU2-1(to NE32) 6-ISU2-1(to NE32) NE34 NE33 3-ISU2-1(to NE33) 3-ISU2-1(to NE33) 5-ISU2-1(to NE33) GE NE32 NE11 GE NE21 NE31 GE GE
NOTE
To save tunnel resources, MPLS tunnels are created only between NE33 and NE32 and between NE34 and NE32 in this example. NE32 is the S-PE. The MPLS tunnels on the chain and the MPLS tunnels on the packet ring are created segment by segment through this example and 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). See Figure 9-8. In actual application scenarios, you can also create MPLS tunnels between NE34 and NE31 and between NE33 and NE31 to transmit corresponding base station services to NE31; in addition, you can configure MPLS APS for the MPLS tunnels.
9-40
Issue 03 (2011-04-10)
Figure 9-8 Networking diagram (Packet radio links)

NE34 NE33
GE NE32 NE11 GE NE21
GE
NE31 GE
Working Tunnel Protection Tunnel

You need to plan the corresponding parameter information before service configuration. 9.4.2.1 Service Planning (MPLS Interfaces) This section provides the information about all the parameters required for configuring MPLS interfaces. 9.4.2.2 Service Planning (MPLS Tunnel) The service planning information contains the information about all the parameters required for configuring MPLS tunnels. 9.4.2.3 Service Planning (QoS) This section provides the information about all the parameters required for configuring QoS for MPLS interfaces.
9.4.2.1 Service Planning (MPLS Interfaces)

This section provides the information about all the parameters required for configuring MPLS interfaces. Table 9-23 to Table 9-25 provide the information about each NNI port on the Packet radio links that are used for configuring the MPLS tunnel.
NOTE
In this example, 1+1 HSB protection is configured for the radio links between NE32 and NE33. Therefore, you need to configure IF_ETH port information only for the main radio link.
Issue 03 (2011-04-10)
9-41
Table 9-23 Information about MPLS interfaces (NE32) Parameter Port name Port mode Enable tunnel Specify IP address Port IP address IP mask Error frame discard enabled 3-ISU2 conn_NE33 Layer 3 Enabled Manually 46.1.64.17 255.255.255.252 Enabled
Table 9-24 Information about MPLS interfaces (NE33) Parameter Port name Port mode Enable tunnel Specify IP address Port IP address IP mask Error frame discard enabled 3-ISU2 conn_NE34 Layer 3 Enabled Manually 46.1.64.21 255.255.255.252 Enabled 4-ISU2 conn_NE32 Layer 3 Enabled Manually 46.1.64.18 255.255.255.252 Enabled
Table 9-25 Information about MPLS interfaces (NE34) Parameter Port name Port mode Enable tunnel Specify IP address Port IP address IP mask Error frame discard enabled 3-ISU2 conn_NE33 Layer 3 Enabled Manually 46.1.64.22 255.255.255.252 Enabled
9-42
Issue 03 (2011-04-10)
9.4.2.2 Service Planning (MPLS Tunnel)

The service planning information contains the information about all the parameters required for configuring MPLS tunnels.
Basic NE configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE as its unique ID on the network. See Table 9-26. Table 9-26 Basic NE configuration Parameter LSR ID Start of global label space NE32 130.0.0.2 0 NE33 130.0.0.5 0 NE34 130.0.0.6 0
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
Information About MPLS Tunnels

Table 9-27 provides basic information about the bidirectional MPLS tunnels between NE32 and NE33 and between NE32 and NE34. Table 9-27 Basic information about MPLS tunnels Parameter Tunnel name Tunnel ID Ingress node of the forward working tunnel Between NE32 and NE33 NE32-NE33-W 1513 NE32 Between NE32 and NE34 NE32-NE34-W 1515 NE32
Figure 9-9 shows the specific tunnel information.
Issue 03 (2011-04-10)
9-43
Figure 9-9 MPLS tunnel planning

Links: NE32-NE33-NE34
NE32 (46.1.4.2) 3-ISU2-1 (46.1.64.17) L:1513 L:1514 L:1515 L:1516 ID:1515 ID:1513
NE33 (46.1.4.5) 4-ISU2-1 3-ISU2-1 (46.1.64.18) (46.1.64.21) L:1513 L:1514 L:1515 L:1501 L:1516 L:1502
NE34 (46.1.4.6) 3-ISU2-1 (46.1.64.22)
L:1501 L:1502
Ingress/Egress L: Label Working tunnel

This section provides the information about all the parameters required for configuring QoS for MPLS interfaces.
NOTE
The NEs in this example and the NEs in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) belong to the same MPLS network. Therefore, the QoS planning in this example is the same as that in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX RTN 950, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ information is planned in a unified manner. Table 9-28 lists the mapping between the DS domain and PHB service classes. Table 9-28 Classes of Service and PHB Service Classes PHB Service Class CS7 CS6 VLAN Priority 7 6 DSCP MPLS EXP Priority 7 6 Correspondin g Service Category -
56 48
9-44
Issue 03 (2011-04-10)
PHB Service Class EF
VLAN Priority 5
DSCP
MPLS EXP Priority 5
Correspondin g Service Category Real-time voice service and signaling service (R99 conversational and R99 streaming services) OM, real-time HSDPA services (OM, HSPA streaming) R99 non-realtime services (R99 interactive and R99 background services) HSDPA data services (HSPA interactive and HSPA background services)
40
AF4 AF3
4 3
32 24
4 3
AF2
16
AF1 BE
1 0
8 0
1 0
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE. The default mapping relationships for the DS domain comply with the network planning requirements and therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.

Issue 03 (2011-04-10)
9-45

This section describes how to set parameters of MPLS tunnel. 9.4.3.1 Configuration Process (MPLS interfaces) This section describes the process for configuring MPLS interfaces. 9.4.3.2 Configuration Process (MPLS Tunnel) This section describes the process for configuring MPLS tunnels. 9.4.3.3 Configuration Process (QoS) This section describes the process for configuring QoS information for MPLS interfaces. 9.4.3.4 Configuration Process (Verifying Configured MPLS Tunnels) This section describes the process for verifying configured MPLS tunnels.
9.4.3.1 Configuration Process (MPLS interfaces)

This section describes the process for configuring MPLS interfaces.
Procedure
Step 1 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes of IF_ETH ports. l The values for the related parameters of NE32 are provided as follows. Parameter Value 3-ISU2-1 Name Port Mode conn_NE33 Layer 3
9-46
Issue 03 (2011-04-10)
l The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2-1 Name Port Mode conn_NE34 Layer 3 4-ISU2-1 conn_NE32 Layer 3
l The values for the related parameters of NE34 are provided as follows. Parameter Value 3-ISU2-1 Name Port Mode conn_NE33 Layer 3
Step 2 See A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports and set the Layer 3 attributes of IF_ETH ports. l The values for the related parameters of NE32 are provided as follows. Parameter Value 3-ISU2-1 Enable Tunnel Specify IP Address IP Address IP Mask Enabled Manually 46.1.64.17 255.255.255.252
l The values for the related parameters of NE33 are provided as follows. Parameter Value 3-ISU2-1 Enable Tunnel Specify IP Address IP Address IP Mask Enabled Manually 46.1.64.21 255.255.255.252 4-ISU2-1 Enabled Manually 46.1.64.18 255.255.255.252
Issue 03 (2011-04-10)
9-47
Parameter
Value 3-ISU2-1
Enable Tunnel Specify IP Address IP Address IP Mask
Enabled Manually 46.1.64.22 255.255.255.252
----End
9.4.3.2 Configuration Process (MPLS Tunnel)

This section describes the process for configuring MPLS tunnels.
Procedure
Step 1 See A.8.2.1 Setting Basic MPLS Attributes and set the LSR ID for each NE. The values for the related parameters of each NE are provided as follows. Parameter Value NE32 LSR ID Start of Global Label Space 130.0.0.2 0 NE33 130.0.0.5 0 NE34 130.0.0.6 0
Step 2 See A.8.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels. l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE32 and NE33 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label
9-48
Between NE32 and NE34 1515 NE32-NE34-W Ingress No Limit Issue 03 (2011-04-10)
1513 NE32-NE33-W Ingress No Limit -
Parameter
Value Between NE32 and NE33 Between NE32 and NE34 3-ISU2 1 1515 1516 46.1.64.18 130.0.0.6 E-LSP None Pipe
Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
3-ISU2 1 1513 1514 46.1.64.18 130.0.0.5 E-LSP None Pipe
l The values for the related parameters of NE33 are provided as follows. Parameter Value Between NE32 and NE33 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port 1513 NE32-NE33-W Egress No Limit 4-ISU2 1 1513 1514 Between NE32 and NE34 1515 NE32-NE34-W Transit No Limit 4-ISU2 1 1515 1516 3-ISU2 1
Issue 03 (2011-04-10)
9-49
Parameter
Value Between NE32 and NE33 Between NE32 and NE34 1515 1516 46.1.64.22 46.1.64.17 130.0.0.2 130.0.0.6 E-LSP -
Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type EXP LSP Mode
46.1.64.17 130.0.0.2 E-LSP None Pipe
l The values for the related parameters of NE34 are provided as follows. Parameter Value Between NE34 and NE32 Tunnel ID Tunnel Name Node Type CIR(kbit/s) In Board/Logic Interface Type In Port Forward In Label Reverse Out Label Out Board/Logic Interface Type Out Port Forward Out Label Reverse In Label Forward Next Hop Address Reverse Next Hop Address Source Node 1515 NE34-NE32-W-F Egress No Limit 3-ISU2 1 1515 1516 46.1.64.21 130.0.0.2
9-50
Issue 03 (2011-04-10)
Parameter
Sink Node Tunnel Type EXP LSP Mode
E-LSP None Pipe
----End

This section describes the process for configuring QoS information for MPLS interfaces.
Procedure
Step 1 See A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and change the ports that are applied to the DS domain and their trusted packet type. The values for the related parameters that need to be set are provided as follows. Parameter Value NE32 Port 3-ISU2 NE33 3-ISU2 4-ISU2 Packet Type mpls-exp mpls-exp mpls-exp NE34 3-ISU2
Step 2 See A.6.7.4 Creating a Port Policy and create the port policy. l The values for the related parameters of each NE are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Value Disabled (for all PHB service classes)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and specify the ports that use the port policy. l The values for the related parameters of NE32 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2
l The values for the related parameters of NE33 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2 4-ISU2 l The values for the related parameters of NE34 are provided as follows. Parameter Value Port_Comm (Policy ID=1) Port 3-ISU2
----End
9.4.3.4 Configuration Process (Verifying Configured MPLS Tunnels)

This section describes the process for verifying configured MPLS tunnels.
Procedure
Step 1 If MPLS APS protection is not configured for MPLS tunnels on the Packet radio links, the MPLS OAM function needs to be enabled to detect the tunnel status. See A.8.2.6 Setting MPLS OAM Parameters. l The values for the related parameters of NE32 are provided as follows. Parameter Value Between NE32 and NE33 Tunnel ID OAM Status
9-52
Between NE32 and NE34 1515 Enabled

Issue 03 (2011-04-10)
1513 Enabled
Parameter
Value Between NE32 and NE33 Between NE32 and NE34 Auto-Sensing CV
Detection Mode Detection Packet Type
Auto-Sensing CV
l The values for the related parameters of NE33 are provided as follows. Parameter Value Between NE32 and NE33 Tunnel ID OAM Status Detection Mode Detection Packet Type 1513 Enabled Auto-Sensing CV
l The values for the related parameters of NE34 are provided as follows. Parameter Value Between NE32 and NE34 Tunnel ID OAM Status Detection Mode Detection Packet Type 1515 Enabled Auto-Sensing CV
Step 2 See A.8.2.9 Querying LSP Running Status and query the LSP running status. Normally, each MPLS tunnel is available. ----End
Issue 03 (2011-04-10)
9-53
10 Configuring PWE3 Services
10
About This Chapter
Configuring PWE3 Services
The procedure and method of configuring PWE3 services vary with types of PWE3 services. 10.1 Basic Concept Before configuring PWE3, you need to be familiar with the basic concepts. 10.2 Configuration Procedure The service configuration procedure differs according to the specific service type. 10.3 Configuration Example (Common CES Services) This section considers a common CES service on a packet network as an example to describe how to configure CES services according to network planning information. Each CES service is encapsulated in SAToP mode. 10.4 Configuration Example (Fractional CES Services) This section considers a Fractional CES service on a packet network as an example to describe how to configure CES services according to the network planning information. Each service is encapsulated in CESoPSN mode. 10.5 Configuration Example (MS-PW-based CES Services) This section considers an MS-PW-based CES service on a packet network as an example to describe how to configure CES services according to the network planning information. This sample service is encapsulated in CESoPSN mode. 10.6 Configuration Example (Common ATM Services) This section uses a common ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in n-to-1 VCC mode. 10.7 Configuration Example (Fractional ATM Services) This section uses a Fractional ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in n-to-1 VCC mode. 10.8 Configuration Example (ATM Services on MS-PWs) This section uses an ATM service carried on MS-PWs of a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in 1-to-1 VCC mode.
10.9 Configuration Example (Transparently Transmitted ATM Services) This section uses a transparently transmitted ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. 10.10 Configuration Example (E-Line Services Carried on PWs, a Simple Example) This section considers E-Line services carried on PWs as an example to describe how to configure E-Line services. 10.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet Services Aggregated from the Hybrid Microwave Network) This section considers E-Line services carried on PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network as an example to describe how to configure ELine services carried on PWs. 10.12 Configuration Example (E-Line Services Carried on MS-PWs) This section considers E-Line services carried on MS-PWs as an example to describe how to configure E-Line services carried on PWs.
10-2
Issue 03 (2011-04-10)
10.1 Basic Concept

Before configuring PWE3, you need to be familiar with the basic concepts. 10.1.1 Types of PWE3 Services The OptiX RTN 950 supports the following types of PWE3 services: CES services, ATM services, and E-Line services carried by PWs. 10.1.2 MS-PW A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW).
10.1.1 Types of PWE3 Services

The OptiX RTN 950 supports the following types of PWE3 services: CES services, ATM services, and E-Line services carried by PWs. 10.1.1.1 CES Services On the OptiX RTN 950, CES services are constructed using the TDM PWE3 technology. That is, TDM E1 services are encapsulated into PW packets, and the PW packets are transmitted through a PW on the PSN. 10.1.1.2 ATM/IMA Services The OptiX RTN 950 supports ATM PWE3 services. The IMA E1 technology is used to transmit ATM services to the OptiX RTN equipment, and then the ATM cells are encapsulated into PW packets. Then, the packets are transmitted in the MPLS tunnel on the PSN. 10.1.1.3 E-Line Services Carried on PWs For the E-Line service category, a PW can be used to carry Ethernet services on an Ethernet port. In this scenario, this type of Ethernet service is called the E-Line service carried on PWs.
10.1.1.1 CES Services

On the OptiX RTN 950, CES services are constructed using the TDM PWE3 technology. That is, TDM E1 services are encapsulated into PW packets, and the PW packets are transmitted through a PW on the PSN. Circuit emulation service (CES) is a technology wherein adaptation is performed on TDM services and the basic behaviors and characteristics of TDM services are emulated so that TDM services can be transparently transmitted on the packet switching network (PSN).
Application Example
CES is mainly used to transmit mobile backhauled services and enterprise private line services. As shown in Figure 10-1, a 2G base station or an enterprise private line connects to the OptiX RTN 950 through a TDM line. The OptiX RTN 950 encapsulates the TDM signals into packets, and then transmits the packets to the opposite end through a PW on the PSN.
Issue 03 (2011-04-10)
10-3
Figure 10-1 Example of CES services

Backebone layer IP/MPLS Backebone Network
Convergence BSC layer
BSC
Access layer
BTS
BTS
Corporation
BTS
BTS
Corporation
CES services
OptiX RTN 900
OptiX packet transmission product
Emulation Modes
The OptiX RTN 950 supports the CES services in structured emulation mode and non-structured emulation mode. l l The structured emulation mode is the CESoPSN mode. The equipment is aware of the frame structure, framing mode, and timeslot information in the TDM circuit. The non-structured emulation mode is the SAToP mode. The equipment is not aware of the frame structure. Instead, the equipment considers the TDM signals as consecutive bit streams, and then emulates and transparently transmits the TDM signals.
As shown in Figure 10-2, the OptiX RTN 950 in CESoPSN mode supports the compression of idle 64 kbit/s timeslots in TDM E1 signals to save transmission bandwidth.
10-4
Issue 03 (2011-04-10)
Figure 10-2 Compression of idle 64 kbit/s timeslots in TDM E1 signals

0 1 2 3 ... 2 9 30 31
BTS
PW 1 2 29
0 1 2 3 ... 29 30 31 0 1 2 3 ... 29 30 31
BTS
29 30 3 ... 2 0 1
31
PW 1 3 30 31
0 1 2 3 ... 29 30 31
BSC PW 1 2 3
0 1 2 3 ... 29 30 31 BTS 0 1 2 3 ... 29 30 31
Timeslots in the E1 frame
Service Clocks
Clock information is an important feature of TDM services. The OptiX RTN 950 supports the retiming clocks and CES ACR clocks of CES services. In retiming synchronization mode, the system clocks of all PEs on the network are synchronized. The system clock of a PE is considered as the service transmit clock (retiming). As shown in Figure 10-3, the system clock of BTS synchronizes itself with the service clock of PE. In this manner, all PEs and CEs are synchronous, and the transmit clocks of the TDM services on all CEs and PEs are synchronous. Figure 10-3 Retiming synchronization mode of CES service clocks
Transmitting E1 signals according to the system clock Synchronized with the radio link clock Synchronized with the E1 signal clock
E1 BTS PE CES Clock synchronization PE
E1 BSC
In ACR mode, the clock is extracted from the TDM interface on the PE on the ingress side. On the PE on the egress side, the clock of the emulated TDM service is recovered based on the clock information in the CES service. Figure 10-4 shows the retiming synchronization mode of CES service clocks.
Issue 03 (2011-04-10)
10-5
Figure 10-4 Adaptive synchronization mode of CES service clocks

Recover the E1 signal clock from the CES service Extract the clock from the E1 signal and add the clock information to the CES service
E1 BTS PE CES PE
E1 BSC
Clock synchronization
10.1.1.2 ATM/IMA Services

The OptiX RTN 950 supports ATM PWE3 services. The IMA E1 technology is used to transmit ATM services to the OptiX RTN equipment, and then the ATM cells are encapsulated into PW packets. Then, the packets are transmitted in the MPLS tunnel on the PSN.
Application Example
ATM/IMA services are mainly backhauled services of base stations. With the IMA E1 technology, the ATM services from NodeB are transmitted to the OptiX RTN 950. On the OptiX RTN 950, PWE3 emulation is performed for the ATM services. Then, the services are transmitted over PWs in MPLS tunnels across the PSN towards the RNC. Before being sent to the RNC, the services are decapsulated on the OptiX PTN/RTN equipment. Figure 10-5 shows the application example. Figure 10-5 Example of ATM/IMA services
IMA E1 IMA E1/ c-STM-1 RTN
NodeB
PSN
PTN
RNC
MPLS tunnel
PW (ATM PWE3)
ATM/IMA Services on the UNI Side

On the UNI side, the OptiX RTN 950 supports the following ATM/IMA functions: l l Supports the IMA E1 technology, wherein an IMA group comprises E1 links. Supports the fractional IMA technology, wherein an IMA group comprises fractional E1 links.
10-6
ATM PWE3 Services on the NNI Side

On the NNI side, the OptiX RTN 950 supports the following ATM PWE3 functions: l l l l l l One-to-one VCC mapping scheme: One VCC is mapped into one PW. N-to-one VCC mapping scheme: N (N32) VCCs are mapped into one PW. One-to-one VPC mapping scheme: One VPC is mapped into one PW. N-to-one VPC mapping scheme: N (N32) VPCs are mapped into one PW. On one PW, a maximum of 31 ATM cells can be concatenated. ATM transparent service.
10.1.1.3 E-Line Services Carried on PWs

For the E-Line service category, a PW can be used to carry Ethernet services on an Ethernet port. In this scenario, this type of Ethernet service is called the E-Line service carried on PWs.
Service Mode
Table 10-1 defines the model of the E-Line services carried on PWs. Table 10-1 Model of the E-Line services carried on PWs Service Model Model 1 Service Flow PORT+CVLAN (source) PW (sink) Service Direction UNI-NNI Port Mode Layer 2 (source) Layer 3 (sink) Encapsulation Mode of Port IEEE 802.1q (source) - (sink) Service Description A UNI port processes the packets carrying a specific CVLAN ID based on its tag attribute, and then sends the packets to the NNI side for transmission on PWs. A UNI port processes the packets carrying a specific SVLAN ID based on its QinQ attribute, and then sends the packets to the NNI side for transmission on PWs.
Model 2
PORT+SVLAN (source) PW (sink)
UNI-NNI
Layer 2 (source) Layer 3 (sink)
QinQ (source) - (sink)
Issue 03 (2011-04-10)
10-7
Service Model Model 3
Service Flow PORT (source) PW (sink)
Service Direction UNI-NNI
Port Mode Layer 2 (source) Layer 3 (sink)
Encapsulation Mode of Port 802.1Q or QinQ (source) - (sink)
Service Description A UNI port processes the packets carrying a specific CVLAN ID based on its tag attribute or QinQ type domain, and then sends the packets to the NNI side for transmission on PWs.
Typical Application
Figure 10-6 shows the typical application of service model 1. Service 1 is present between the NodeB 1 and the RNC, and service 2 is present between the NodeB 2 and the RNC. The two services have different VLAN IDs and need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1. Figure 10-6 Typical application of service model 1
Service 1 Port: 1(802.1Q) VLAN ID: 100 Service 1 Port: 1(802.1Q) VLAN ID: 100
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(802.1Q) VLAN ID: 200 Packet transmission equipment NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(802.1Q) VLAN ID: 200 AC AC RNC
Figure 10-7 shows the typical application of service model 2. Service 1 (QinQ service) is present between NodeB 1 and the RNC, and service 2 (QinQ service) is present between the NodeB 2
and the RNC. The two services have different S-VLAN IDs and need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1. Figure 10-7 Typical application of service model 2
Service 1 Port: 1(QinQ) S-VLAN ID: 100 Service 1 Port: 1(QinQ) S-VLAN ID: 100
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(QinQ) S-VLAN ID: 200 Packet transmission equipment NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(QinQ) S-VLAN ID: 200 AC AC RNC
Figure 10-8 shows the typical application of service model 3. Service 1 (Ethernet service) is present between the NodeB 1 and the RNC, and service 2 (Ethernet service) is present between the NodeB 2 and the RNC. Service 1 carries various C-VLAN IDs, and service 2 carries various S-VLAN IDs. The two services need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1.
Issue 03 (2011-04-10)
10-9
Figure 10-8 Typical application of service model 3

Service 1 Port: 1 (802.1Q) Service 1 Port: 1 (802.1Q)
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(QinQ) NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(QinQ) AC AC RNC
10.1.2 MS-PW
A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW).
NOTE
For the SS-PW network reference model, see PWE3 Network Reference Model.
MS-PW Network Reference Model

Figure 10-9 shows the MS-PW network reference model. Figure 10-9 MS-PW network reference model
Emulated service MS-PW Native service T-PE1 CE1 PW2 PW4 PSN tunnel 1 PW1 S-PE1 PSN tunnel 2 PW3 T-PE2 CE2 Native service
AC PW switching point T-PE: terminating provider edge S-PE: switching provider edge
AC
10-10
Issue 03 (2011-04-10)
NOTE
PSN tunnels are available in several types, but the OptiX RTN 950 supports only MPLS tunnels. In this document, PWE3 is based on MPLS tunnels (LSPs), unless otherwise specified.
In the preceding network reference model, T-PE1 and T-PE2 provide PWE3 services to CE1 and CE2. The PWs are carried in two PSN tunnels, and constitute the MS-PW. The two tunnels (PSN tunnel 1 and PSN tunnel 2) that are used to carry PWs reside in different PSN domains. PSN tunnel 1 extends from T-PE1 to S-PE1, and PSN tunnel 2 extends from SPE1 to T-PE2. Labels of PW1 carried in PSN tunnel 1 and PW3 carried in PSN tunnel 2 are swapped at S-PE1. Similarly, labels of PW2 carried in PSN tunnel 1 and PW4 carried in PSN tunnel 2 are swapped at S-PE1.
MS-PW Application
Compared with the SS-PW, the MS-PW has the following characteristics: l l l Reduces required tunnel resources. Traverses different PSNs. Provides segment-based protection for tunnels.
The following paragraphs and figures compare the application scenarios of the SS-PW and MSPW to show that it is easier for the MS-PW to implement segment-based protection for tunnels. Figure 10-10 shows the SS-PW networking mode. The services between PE1 and PE2 are transmitted on PW1 carried in MPLS tunnel 1. Both MPLS tunnel 1 and MPLS tunnel 2 are configured with 1:1 protection. Protection, however, fails to be provided if disconnection faults occur on different sides of the operator device (called the P device). Figure 10-10 SS-PW application
SS-PW
PW1
MPLS tunnel 1
PW1
PE1
PW1
P MPLS tunnel 2
PE2
PW1
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
Figure 10-11 shows the MS-PW networking mode. The services between T-PE1 and T-PE2 are transmitted on PW1 carried in MPLS tunnel 1 and PW2 carried on MPLS tunnel 2. The paired tunnels (MPLS tunnel 1 and MPLS tunnel 3; MPLS tunnel 2 and MPLS tunnel 4) are configured with 1:1 protection. In this configuration, protection can still be provided even when disconnection faults occur on different sides of the S-PE1 device.
Figure 10-11 MS-PW application

MS-PW MPLS tunnel 1
PW1
MPLS tunnel 2
PW2
PW1
PW2
T-PE1
MPLS tunnel 3
S-PE1
MPLS tunnel 4
T-PE2

The service configuration procedure differs according to the specific service type. 10.2.1 Per-NE Configuration Procedure (CES Services) This section describes how to configure CES services, configure UNI ports, and verify CES services. 10.2.2 Per-NE Configuration Procedure (ATM Services) This section describes the procedures for configuring the service information, UNI port information, IMA information, and QoS information of an ATM service and the procedure for verifying the service configurations. 10.2.3 Configuration Procedure (E-Line Services Carried on PWs) describes how to configure the information about E-Line services carried by PWs, UNI port attributes, link aggregation groups (LAGs), QoS policies, PW protection, and service verification.
10.2.1 Per-NE Configuration Procedure (CES Services)

This section describes how to configure CES services, configure UNI ports, and verify CES services.

Figure 10-12 provides the procedures for configuring CES services on a single NE.
10-12
Issue 03 (2011-04-10)
Figure 10-12 Configuration flow chart

Mandatory Optional Configure UNI ports Start
Configure CES services
Configure PW APS
Verify CES services
End
NOTE
By default, CES services use the retiming mode to transmit clock. Therefore, it is unnecessary to describe the retiming mode in this topic. If CES services need to use the CES ACR mode to transmit clock, configure the mode according to Configuration Procedure in the OptiX RTN 950 V100R003C00 Radio Transmission System Feature Description.
Setting the Attributes of UNI Ports

Setting the attributes of UNI ports carrying CES services mainly involves setting the attributes of Smart E1 ports. Table 10-2 Setting the attributes of UNI ports Operation Setting the attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports Remarks Required. Set the parameters as follows: Set Port Mode to Layer 1.
Issue 03 (2011-04-10)
10-13
Operation A.5.4.2 Setting Advanced Attributes of Smart E1 Ports
Remarks Optional. Set the parameters as follows: l When PW Type is CESoPSN, set Frame Format to CRC-4 Multiframe or Double Frame as planned. The value CRC-4 Multiframe is recommended for securing transmission quality. When PW Type is SAToP, set Frame Format to Unframe. l Set Frame Mode to 31. If Frame Mode of the opposite end is 30, the source 64 kbit/s timeslots at the local end must include the 16th timeslot. l Generally, Retiming Mode is set to Master Mode.
10-14
Issue 03 (2011-04-10)
Configuring CES Services

Table 10-3 Configuring CES services Operation A.8.6.1 Creating CES Services Setting the general attributes of services Remarks Required. Set the parameters as follows: l Set Service ID(e.g.1,3-6), Service name, Source Board, Source Low Channel(e.g.1,3-6), and Source 64K Timeslot(e.g.1,3-6) according to service planning information. Source 64K Timeslot(e.g.1,3-6) is valid only for the CESoPSN mode. If the Frame Mode at the opposite end is set to 30, the source 64 kbit/ s timeslots at the local end must include the 16th timeslot. l Set Pri. Pri indicates the PHB service class for CES services. The default PHB service class for CES services is EF. If CES services are transmitted on the ISU2/ISX2, set the PHB service class to CS7 to decrease the CES service transmission delay and jitters. l Set Mode to UNI-NNI. l Set Protection Type for a PW according to network planning information. l Optional. When creating a CES service, you can set UNI port parameters.
Issue 03 (2011-04-10)
10-15
Operation Configuring PWs
Remarks l Required. Set the basic attributes of PWs. Set PW ID according to planning information. Set PW Type according to planning information. If PCM timeslots are used for service access, select CESoPSN; otherwise, select SAToP. For Fractional E1, select CESoPSN. Set PW Ingress Label/Source Port and PW Egress Label/ Sink Port according to planning information. Select the Ingress Tunnel according to planning information. For a unidirectional tunnel, select or create an egress tunnel. l Optional. Set advanced attributes of PWs. Advanced attributes of PWs take their default values.
Procedure for Configuring PW Protection

For details about how to configure PW protection, see Configuration Procedure in PW APS of the Feature Description.
Verifying CES Services

Table 10-4 Verifying CES services Operation A.12.2 Testing E1 Services by Using a BER Tester Remarks Test CES services at each E1 port by using BER testers. The BER testers that support Nx64 kbit/s are required to test CES services in CESoPSN mode.
10.2.2 Per-NE Configuration Procedure (ATM Services)

This section describes the procedures for configuring the service information, UNI port information, IMA information, and QoS information of an ATM service and the procedure for verifying the service configurations.

The procedure for configuring ATM/IMA E1 services is different from the procedure for configuring Fractional ATM/IMA services. See Figure 10-13. Figure 10-13 Configuration flow chart (ATM services on a per-NE basis)
Flow chart for configuring ATM/IMA E1 services Required Optional Start Flow chart for configuring Fractional ATM/IMA services Start
Set UNI port attributes of ATM/IMA E1 services
Set UNI port attributes of Fractional E1 services
Configure IMA group information
Configure IMA group information
Configure ATM QoS
Configure ATM QoS
Configure ATM services
Configure ATM services
Configure PW APS
Configure PW APS
Verify ATM service configurations
Verify ATM service configurations
End
End
Setting UNI Port Attributes for ATM/IMA E1 Services

Table 10-5 Setting attributes of Smart E1 ports Operation Setting attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports Description Required. Set the parameters as follows: l Set Name according to service planning information. l Set Port Mode to Layer 2.
Issue 03 (2011-04-10)
10-17
Operation A.5.4.2 Setting Advanced Attributes of Smart E1 Ports
Description Optional. Set the parameters as follows: l Set Frame Format and Frame Mode according to service planning information. Ensure that the same frame mode is used at both ends. Normally, the port that transmits ATM/IMA services uses the CRC-4 multi-frame format and the PCM30 frame mode.
Setting UNI Port Attributes for Fractional E1 Services

Setting the UNI port attributes for Fractional E1 services involves setting Smart E1 port attributes, creating serial ports, and configuring serial ports. Table 10-6 Setting attributes of Smart E1 ports Operation Setting attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports A.5.4.2 Setting Advanced Attributes of Smart E1 Ports Description Required. Set the parameters as follows: l Set Name according to service planning information. l Set Port Mode to Layer 1. Optional. Set the parameters as follows: Set Frame Format and Frame Mode according to service planning information. Ensure that the same frame mode is used at both ends. Normally, the port that transmits Fractional ATM services uses the CRC-4 multi-frame format and the PCM31 frame mode. Creating and configuring serial ports A.5.5.1 Creating Serial Ports Required. Set the parameters as follows: l Set the parameters according to service planning information. Port Number(e.g:1,3-6) and Name specifies the ID and name of a serial port. Used Board and Used Port specifies the board and port where the serial port exists. 64K Timeslot(e.g:1,3-6) specifies the IDs of the 64 kbit/s timeslots that are used as a serial port. l The default value of Level is 64K Timeslot.
NOTE When the E1 frame mode is PCM30, timeslot 0 and timeslot 16 cannot be used to carry services. When the E1 frame mode is PCM31, timeslot 0 cannot be used to carry services.
10-18
Issue 03 (2011-04-10)
Operation A.5.5.2 Setting Basic Attributes of Serial Ports
Description Required. Set Port Mode to Layer 2.
Setting IMA Group Information

Configuring IMA group information involves binding ATM trunks, configuring an IMA group, and configuring ATM ports. Table 10-7 Configuring an IMA group Operation A.8.7.1 Binding ATM TRUNKs Description Required. l For ATM/IMA services, set Level to E1. For Fractional E1 services, set Level to Fractional E1. l Set the other parameters according to service planning information.
NOTE When the E1 frame mode is PCM30, timeslot 16 cannot be bound to an ATM trunk.
A.8.7.2 Configuring an IMA group
Required. Set the parameters as follows: l Set IMA Protocol Enable Status. For ATM E1 and Fractional ATM, set IMA Protocol Enable Status to Disabled in most cases. For IMA E1 and Fractional IMA, set IMA Protocol Enable Status to Enabled. l Set Clock Mode of the local NE and the NE at the opposite end of the IMA trunk to be the same as Clock Mode of the interconnected BTS. l The other parameters are valid only for IMA E1 and Fractional IMA. Parameters must be set to the same values for equipment at both ends of an IMA link. It is recommended that the parameters take their default values.
Issue 03 (2011-04-10)
10-19
Operation A.8.7.3 Setting ATM Port Parameters
Description Optional. l Set Port Type and ATM Cell Payload Scrambling according to the type of access equipment. It is recommended that the parameters take their default values. The parameter values must be the same for both ends of a link. l The other parameters take their default values.
Configuring ATM QoS

Configuring ATM QoS involves configuring the ATM policy and configuring the CoS mapping table. For transparently transmitted ATM services, you do not need to configure the ATM traffic management policy. For ATM connection-based services, the ATM traffic management policy must be configured. Table 10-8 Configuring ATM QoS Operation A.8.9.3 Creating an ATM Policy Description Required for services that are not transparently transmitted ATM services. Set parameters according to the type of the ATM service access equipment. l Set Policy ID. Alternatively, you can select Automatically Assign so that the policy ID is automatically assigned. l Select or assign a value for Policy Name. l Set Service Type according to service planning information. l Set Traffic Type and corresponding traffic parameters based on Service Type. l Set the enabled status of Discard Traffic Frame and UPC/NPC according to planning information. A.8.9.1 Creating an ATM-DiffServ Domain Required if "DefaultAtmCosMap" does not meet requirements. Set parameters according to service planning information.
10-20
Issue 03 (2011-04-10)
Configuring an ATM Service

Operation A.8.8.1 Creating ATM Services Setting service attributes Description Set the basic attributes for ATM services. Required. Set the parameters as follows: l Set Service ID and Service Name. l Set Direction to UNIs-NNI. l Set Connection Type. If services are transmitted based on VP connections, set Connection Type to PVP. If services are transmitted based on VC connections, set Connection Type to PVC. If services are transparently transmitted over ports, set Connection Type to Port Transparent. Configuring ATM connections Creating ATM connections Required. Set connection parameters according to service planning information. l For ATM connection-based services, the connection parameters need to be configured. Uplink Policy and Down link Policy are specified for ATM connections during configuration of ATM policies. l For services transparently transmitted through ATM ports, only Source Port, and PW ID need to be configured.
Issue 03 (2011-04-10)
10-21
Operation Configuring PWs
Description l Setting basic attributes of PWs Required. Set PW ID, PW Ingress Label / Source Port, and PW Egress Label / Sink Port according to service planning information. Set PW Type according to planning information. Select a value for Tunnel according to service planning information. For unidirectional tunnels, you also need to set Egress Tunnel. l Setting advanced attributes of PWs Optional. If Control Word is No Use, set Control Channel Type to Alert Label. Other advanced attributes generally take their default values. Advanced attributes of PWs take their default values. l Optional. Configure the QoS. The QoS parameters take their default values. Configuring CoS mapping Required if "DefaultAtmCosMap" does not meet requirements. Set CoS Mapping according to planning information. Set the mapping between PW ID and CoS Mapping. Select the policy for mapping different ATM service levels to CoS priorities. In this way, different quality levels are provided for different ATM services.

10-22
Issue 03 (2011-04-10)
Verifying ATM Service Configurations

Operation A.12.4 Testing ATM Services Description Use the ATM OAM function to test ATM service connectivity.
NOTE For transparently transmitted ATM services, service verification needs to be conducted on the ATM service access equipment.
10.2.3 Configuration Procedure (E-Line Services Carried on PWs)

describes how to configure the information about E-Line services carried by PWs, UNI port attributes, link aggregation groups (LAGs), QoS policies, PW protection, and service verification.

Figure 10-14 provides the procedures for configuring E-Line services carried PWs. Figure 10-14 configuration flow chart (E-Line services carried on PWs)
Required Optional Configuring UNI Port Attributes Start
Configuring LAGs of UNI Ports
Configuring UNI-NNI E-Line Services Carried on PWs
Configuring PW Protection Groups
Configuring Affiliation Protection Pairs of PWs
Configurig QoS Policies
Verifying E-Line Service Configurations
End
Issue 03 (2011-04-10)
10-23
Procedure for Configuring UNI Port Attributes

Table 10-9 Procedure for configuring UNI port attributes Operation Setting attributes of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required when an Ethernet port is enabled to access Ethernet services. In the case of used UNI ports, set the major parameters as follows: l Set Enable Port to Enabled. l Set Port Mode to Layer 2. l Set Encapsulation Type to 802.1Q. l In the case of an Ethernet port that is connected to external equipment (BTS or RNC), set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is autonegotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the major parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enabled. l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to Enabled. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the major parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
10-24
Issue 03 (2011-04-10)
Operation A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting attributes of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Required when an IF_ETH port is enabled to access Ethernet services. Set the major parameters as follows: l Set Port Mode to Layer 2. l Set Encapsulation Type to 802.1Q.
Required. Set the major parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set Tag to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set Tag to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set Tag to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.
Issue 03 (2011-04-10)
10-25

10-26
Issue 03 (2011-04-10)
Issue 03 (2011-04-10)
10-27
Procedure for Configuring UNI-NNI E-Line Services Carried by PWs

Table 10-11 Procedure for configuring UNI-NNI E-Line services carried by PWs Operation A.6.3.5 Configuring UNI-NNI ELine Services (Carried by PWs) Description Required. Set the major parameters of E-Line services as follows: l Set Direction to UNI-NNI. l Set BPDU to Not Transparently transmitted. l Set Source Interface and Source VLAN ID according to the network planning information. l Set Bearer Type to PW. l It is recommended that you set Protection Type to No Protection. Although a PW protection scheme needs to be created, it is recommended that you create it after creating E-Line services carried by PWs. Set the major parameters for a PW in the General Attributes tab as follows: l Set PW ID according to the service planning information. l Set PW Signaling Type to Static. l PW Type indicates whether to add P-TAG when Ethernet frames are encapsulated on a PW. When no request is proposed to add VLAN IDs, set this parameter to Ethernet. When a request is proposed to add VLAN IDs, set this parameter to Ethernet Tagged Mode. In the Advanced Attributes tab page, set Request VLAN to be added. l Set PW Ingress Label/Source Port and PW Egress Label/Sink Port according to the service planning information. l Set Tunnel Type to MPLS. l Select the Tunnel that carries PWs according to the service planning information. Set the major parameters for a PW in the Advanced Attributes tab as follows: l The control word is not supported during ETH PWE3 packet encapsulation on the OptiX RTN 950. Therefore, set Control Word to No Use. l Set Control Channel Type to Alert Label. l Set VCCV Verification Mode to Ping. Set the major parameters for a PW in the QoS tab as follows: l Set Bandwidth Limit for a PW according to the service planning information. Its default value is Disabled. l To enable Bandwidth Limit to take effect for a PW, first configure a maximum bandwidth for the tunnel that carries the PW.
10-28
Issue 03 (2011-04-10)


Table 10-12 Procedure for configuring the QoS Operation Using the default DS domain for OptiX RTN equipment Description Required. 1. If the mappings that are planned between the packet priority and PHB service classes for base stations or interconnected equipment are different from the mappings that are configured for the default DS domain of the OptiX RTN equipment, change the mappings of the OptiX RTN equipment to be the same as the mappings planned for the base stations or interconnected equipment. 2. If the packet priority type (namely, the trusted packet type) supported by base stations or interconnected equipment is different from the trusted packet type (C-VLAN priority, by default) for the default DS domain of the OptiX RTN equipment, change the trusted packet type of the UNI port in the DS domain that receives the Ethernet service packets to be the same as the trusted packet type of the base stations or interconnected equipment. 3. When transmitting the PW-carried UNI-NNI E-Line service packets, an NNI port supports only packets with the MPLS EXP priority. Therefore, you need to change the trusted packet type of the NNI port in the default DS domain to MPLS EXP. A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping Required when you need to apply QoS policies other than Diffserv and port shaping for a specific port. Set the relevant parameters according to the network planning information. Required when you need to perform the CAR or shaping operation for a specific flow over the port. Set the relevant parameters according to the network planning information. Required when a port policy is created. Set the relevant parameters according to the network planning information.
Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information.
Issue 03 (2011-04-10)
10-29

10-30
Issue 03 (2011-04-10)
10.3 Configuration Example (Common CES Services)

This section considers a common CES service on a packet network as an example to describe how to configure CES services according to network planning information. Each CES service is encapsulated in SAToP mode. 10.3.1 Networking Diagram This section describes the networking information about the NEs. 10.3.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 10.3.3 Per-NE Configuration Process This section describes the process for configuring CES services on a single NE.

This section describes the networking information about the NEs. Based on 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection), configure CES services according to the following requirements for BTS22 shown in Figure 10-15. l l Table 10-14 provides the port information of CES services. There is a bidirectional working tunnel between NE21 and NE31. Protection schemes are configured for this tunnel and its tunnel ID is 1505. 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) describes the configuration of this tunnel. There are no requirements for transmitting services with some of the timeslots.
Issue 03 (2011-04-10)
10-31
Figure 10-15 Networking Diagram
GE
GE
NE32 NE11
GE E1 loop
NE31 NE21
GE
E1
BSC Working tunnel (ID=1505)

E1
BTS22
Table 10-14 Service port information NE NE21 Service Port 2-SP3S(1-2) Description Receives base station services from BTS22 over the Hybrid radio network. For the configuration process of these services, see 6.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network). Switches the E1 services of BTS22 from the TDM domain to the packet domain by forming cross-connect loops with and 2-SP3S-(1-2) ports. Transmits base station services from BTS22 to the BSC.
6-ML1(1-2)
NE31
2-ML1(1-2)
NOTE
If E1 services are locally accessed, they can be received by Smart E1 ports. Therefore, the cross-connect loop between PDH ports and Smart E1 ports is not required.
10-32
Issue 03 (2011-04-10)

The service planning information contains the information about all the parameters required for configuring the NE data. 10.3.2.1 Service Planning (UNI Ports) The service planning information contains the information about all the parameters required for configuring UNI ports. 10.3.2.2 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring CES services.
10.3.2.1 Service Planning (UNI Ports)

The service planning information contains the information about all the parameters required for configuring UNI ports. Table 10-15 to Table 10-16 provide UNI port information. Table 10-15 UNI port information (NE21) Parameter Port name E1 frame format 6-ML1-1 conn_bts22_ces1 Unframe 6-ML1-2 conn_bts22_ces2 Unframe
Table 10-16 UNI port information (NE31) Parameter Port name E1 frame format 2-ML1-1 conn_bsc_ces1 Unframe 2-ML1-2 conn_bsc_ces2 Unframe
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port names. l If customers have no requirements for transmitting services with some of the timeslots, CES services adopt the SAToP mode and the E1 frame format always adopts the unframe mode.
10.3.2.2 Service Planning (Service Information)

The service planning information contains the information about all the parameters required for configuring CES services.
Service Information Planning

Table 10-17 to Table 10-18 provide the service planning information.
Table 10-17 Service information (CES service 1 of BTS22) Parameter CES Service 1 of BTS22 Source NE (NE21) Service ID Service name Service port Encapsulation mode 64 kbit/s timeslot Priority Protection scheme PW ID PW In/Out label ID of working tunnel 201 bts22_ces_service_01 6-ML1-1 SAToP EF Non-protection 201 201/201 1505 EF 2-ML1-1 Sink NE (NE31)
Table 10-18 Service information (CES service 2 of BTS22) Parameter CES Service 2 of BTS22 Source NE (NE21) Service ID Service name Service port Emulation mode 64 kbit/s timeslot Priority Protection scheme PW ID PW In/Out label Working tunnel ID 202 bts22_ces_service_02 6-ML1-2 SAToP EF Non-protection 202 202/202 1505 EF 2-ML1-2 Sink NE (NE31)
10-34
Issue 03 (2011-04-10)
NOTE
l OptiX RTN 950 supports point-to-point CES services only. That is, one PW cannot carry services from multiple E1 ports. l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots.
Planning of Advanced Attributes of CES Services

NOTE
The advanced attributes of CES services take default values on both PEs if CES services are transmitted only on Huawei equipment. If Huawei equipment communicates CES services with third-party equipment, the advanced attributes of CES services need to be negotiated according to the default values listed in Table 10-19. Ensure that the parameters take the same values on both PEs.
Table 10-19 Default values of advanced attributes of CES services Parameter RTP header encapsulation enabling Jitter buffer time Packet loading time VCCV verification mode Sequence number mode Value Range Disabled 8000 us 1000 us VCCV using CW Huawei mode
10.3.3 Per-NE Configuration Process

This section describes the process for configuring CES services on a single NE. 10.3.3.1 Configuration Process (Service Information) This section describes the process for configuring CES services. 10.3.3.2 Configuration Process (Verifying CES Service Configurations) This section describes the process for verifying CES service configurations.

This section describes the process for configuring CES services.
Procedure
Step 1 See A.8.6.1 Creating CES Services and create CES services. l Parameters of NE21 The values for the related parameters that need to be set in the main interface are as follows.
Issue 03 (2011-04-10)
10-35
Parameter
NE21 CES Service 1 of BTS22 CES Service 2 of BTS22 202 bts22_ces_service_02 UNI-NNI 6-ML1 2 EF SAToP No Protection
Service ID(e.g.1,3-6) Service name Mode Source Board Source Low Channel(e.g. 1,3-6) Source 64K Timeslot(e.g. 1,3-6) Pri PW Type Protection Type
201 bts22_ces_service_01 UNI-NNI 6-ML1 1 EF SAToP No Protection
The values for the related parameters that need to be set in Port Attribute are as follows. Parameter NE21 6-ML1-1 Port Mode Frame Format Layer 1 Unframe 6-ML1-2 Layer 1 Unframe
The values for the basic PW attributes that need to be set in the PW tab are as follows. Parameter NE21 CES Service 1 of BTS22 PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
10-36
CES Service 2 of BTS22 202 Static MPLS 202 202 MPLS 1505
Issue 03 (2011-04-10)
201 Static MPLS 201 201 MPLS 1505
The values for the Advanced Attributes that need to be set in the PW tab are as follows. Parameter NE21 CES Service 1 of BTS22 Control Channel Type VCCV Verification Mode Sequence Number Mode CW Ping Huawei Mode CES Service 2 of BTS22 CW Ping Huawei Mode
l Parameters of NE31 The values for the related parameters that need to be set in the main interface are as follows. Parameter NE31 CES Service 1 of BTS22 Service ID(e.g.1,3-6) Service name Mode Source Board Source Low Channel(e.g. 1,3-6) Source 64K Timeslot(e.g. 1,3-6) Pri PW Type Protection Type 201 bts22_ces_service_01 UNI-NNI 2-ML1 1 EF SAToP No Protection CES Service 2 of BTS22 202 bts22_ces_service_02 UNI-NNI 2-ML1 2 EF SAToP No Protection
The values for the related parameters that need to be set in Port Attribute are as follows. Parameter NE31 2-ML1-1 Port Mode Frame Format Layer 1 Unframe 6-ML1-2 Layer 1 Unframe
The values for the basic PW attributes that need to be set in the PW tab are as follows.
Parameter
NE31 CES Service 1 of BTS22 CES Service 2 of BTS22 202 Static MPLS 202 202 MPLS 1505
PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
The values for the Advanced Attributes that need to be set in the PW tab are as follows. Parameter NE31 CES Service 1 of BTS22 Control Channel Type VCCV Verification Mode Sequence Number Mode CW Ping Huawei Mode CES Service 2 of BTS22 CW Ping Huawei Mode
----End
10.3.3.2 Configuration Process (Verifying CES Service Configurations)

This section describes the process for verifying CES service configurations.
Procedure
Step 1 See A.12.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER testers. It is recommended that you connect BER testers to NE31 and perform loopbacks on NE21. The test results should be no bit errors. ----End
10.4 Configuration Example (Fractional CES Services)

This section considers a Fractional CES service on a packet network as an example to describe how to configure CES services according to the network planning information. Each service is encapsulated in CESoPSN mode.
10.4.1 Networking Diagram This section describes the networking information about the NEs. 10.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 10.4.3 Per-NE Configuration Process This section describes the process for configuring CES services on a single NE.

This section describes the networking information about the NEs. Based on 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection), configure the CES services according to the following requirements for BTS35 and BTS36 shown in Figure 10-16. l l Table 10-20 provides the CES service port information. There is a bidirectional working tunnel between NE11 and NE31. Protection schemes are configured for this tunnel and its tunnel ID is 1509. 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) describes the configuration of this tunnel.

Working tunnel (ID=1509)
GE GE
NE32 NE11
GE E1
NE31
E1
NE21
GE
BSC
BTS36
BTS35
Table 10-20 Service port information NE NE11 Service Port 4-ML1-1 Description Receives base station services from BTS35 and BTS36 in Fractional CES mode. The services from BTS35 occupy the first to 15th timeslots and those from BTS36 occupy the 17th to 31st timeslots.
10-39
Issue 03 (2011-04-10)
NE NE31
Service Port 2-ML1-3
Description Transmits base station services from BTS35 to the BSC. These services occupy the first to 15th timeslots. Transmits base station services from BTS36 to the BSC. These services occupy the first to 15th timeslots.
2-ML1-4

The service planning information contains the information about all the parameters required for configuring the NE data. 10.4.2.1 Service Planning (UNI Ports) The service planning information contains the information about all the parameters required for configuring UNI ports. 10.4.2.2 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring CES services.

The service planning information contains the information about all the parameters required for configuring UNI ports. Table 10-21 to Table 10-22 provide UNI port information. Table 10-21 UNI Port Information (NE11) Parameter Port name E1 frame format E1 frame mode 4-ML1-1 conn_bts35_bts36_ces1 CRC-4 multiframe PCM31
Table 10-22 UNI Port Information (NE31) Parameter Port name E1 frame format E1 frame mode
10-40
2-ML1-3 conn_bsc_ces3 CRC-4 multiframe PCM31
2-ML1-4 conn_bsc_ces4 CRC-4 multiframe PCM31

Issue 03 (2011-04-10)
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port names. l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types. During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual E1 frame format is double, the E1 port will report the LMFA alarm. l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid radio network.


Table 10-23 to Table 10-24 provide the service planning information. Table 10-23 Service information (CES service 1 of BTS35) Parameter CES Service 1 of BTS35 Source NE (NE11) Service ID Service name Service port Encapsulation mode 64 kbit/s timeslot Priority Protection scheme PW ID PW In/Out label Working tunnel ID 203 bts35_ces_service_01 4-ML1-1 CESoPSN 1-15 EF Non-protection 203 203/203 1509 1-15 EF 2-ML1-3 Sink NE (NE31)
Issue 03 (2011-04-10)
10-41
Table 10-24 Service information (CES service 1 of BTS36) Parameter CES Service 1 of BTS36 Source NE (NE11) Service ID Service name Service port Emulation type 64 kbit/s timeslot Priority Protection scheme PW ID PW In/Out label ID of working tunnel 204 bts36_ces_service_01 4-ML1-1 CESoPSN 17-31 EF Non-protection 204 204/204 1509 1-15 EF 2-ML1-4 Sink NE (NE31)
NOTE
l Fractional CES services must adopt the CESoPSN mode. Therefore, you need to know the allocation of E1 timeslots in advance. l If the allocation of E1 timeslots is the same on the BSC side and the BTS side, as in this example, the E1 that transmits the services of BTS35 and BTS36 with the same timeslot allocation on the BSC side can be considered a common CES service.

NOTE
10-42
Issue 03 (2011-04-10)


Procedure
Step 1 See A.8.6.1 Creating CES Services and create CES services. l Parameters of NE11 The values for the related parameters that need to be set in the main interface are as follows. Parameter NE11 CES Service of BTS35 Service ID(e.g.1,3-6) Service name Mode Source Board Source Low Channel(e.g. 1,3-6) Source 64K Timeslot(e.g. 1,3-6) Pri PW Type Protection Type 203 bts35_ces_service_01 UNI-NNI 4-ML1 1 1-15 EF CESoPSN No Protection CES Service of BTS36 204 bts36_ces_service_01 UNI-NNI 4-ML1 1 17-31 EF CESoPSN No Protection
The values for the related parameters that need to be set in the Port Attributes tab page are as follows. Parameter NE11 4-ML1-1 Port Mode Frame Format
Issue 03 (2011-04-10)
Layer 1 CRC-4 Multiframe

10-43
Parameter
NE11 4-ML1-1
Frame Mode
31
The values for the basic PW attributes that need to be set in the PW tab are as follows. Parameter NE11 CES Service of BTS35 PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel 203 Static MPLS 203 203 MPLS 1509 CES Service of BTS36 204 Static MPLS 204 204 MPLS 1509
The values for the Advanced Attributes that need to be set in the PW tab are as follows. Parameter NE11 CES Service of BTS35 Control Channel Type VCCV Verification Mode Sequence Number Mode l Parameters of NE31 The values for the related parameters that need to be set in the main interface are as follows. Parameter NE31 CES Service of BTS35 Service ID(e.g.1,3-6) Service name Mode 203 bts35_ces_service_01 UNI-NNI CES Service of BTS36 204 bts36_ces_service_01 UNI-NNI CW Ping Huawei Mode CES Service of BTS36 CW Ping Huawei Mode
10-44
Issue 03 (2011-04-10)
Parameter
NE31 CES Service of BTS35 CES Service of BTS36 2-ML1 4 1-15 EF CESoPSN No Protection
Source Board Source Low Channel(e.g. 1,3-6) Source 64K Timeslot(e.g. 1,3-6) Pri PW Type Protection Type
2-ML1 3 1-15 EF CESoPSN No Protection
The values for the related parameters that need to be set in Port Attributes are as follows. Parameter NE31 2-ML1-3 Port Mode Frame Format Frame Mode Layer 1 CRC-4 Multiframe 31 2-ML1-4 Layer 1 CRC-4 Multiframe 31
The values for the basic PW attributes that need to be set in the PW tab are as follows. Parameter NE31 CES Service of BTS35 PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel 203 Static MPLS 203 203 MPLS 1509 CES Service of BTS36 204 Static MPLS 204 204 MPLS 1509
The values for the Advanced Attributes that need to be set in the PW tab are as follows.
Parameter
NE31 CES Service of BTS35 CES Service of BTS36 CW Ping Huawei Mode
Control Channel Type VCCV Verification Mode Sequence Number Mode
CW Ping Huawei Mode
----End

Procedure
Step 1 See A.12.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER testers. l Because the CES services under test adopt the CESoPSN mode, BER testers must be used for testing nx64 kbit/s services according to timeslot allocation. l It is recommended that you connect BER testers to NE31 and perform loopbacks on NE11. The test results should be no bit errors. ----End
10.5 Configuration Example (MS-PW-based CES Services)

This section considers an MS-PW-based CES service on a packet network as an example to describe how to configure CES services according to the network planning information. This sample service is encapsulated in CESoPSN mode. 10.5.1 Networking Diagram This section describes the networking information about the NEs. 10.5.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 10.5.3 Per-NE Configuration Process This section describes the process for configuring CES services on a single NE.

This section describes the networking information about the NEs. Based on 9.4 Configuration Example (MPLS Tunnels with No Protection), configure CES services according to the following requirements for BTS32 shown in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). l
10-46
Table 10-26 provides the port information of CES services.

The information about the working tunnels between NE33 and NE31 is as follows: There is a bidirectional working tunnel between NE33 and NE32. Protection schemes are configured for this tunnel and its tunnel ID is 1513. 9.4 Configuration Example (MPLS Tunnels with No Protection) describes the configuration of this tunnel. There is a bidirectional working tunnel between NE32 and NE31. Protection schemes are configured for this tunnel and its tunnel ID is 1501. 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) describes the configuration of this tunnel.

NE33 BTS32
E1 GE GE
NE32 NE11
GE
NE31 NE21
GE
E1
BSC
Table 10-26 Service port information NE NE33 Service Port 2-ML1-1 Description Receives base station services from BTS32. These services occupy the first to 21st timeslots. Transmits base station services from BTS32 to the BSC. These services occupy the first to 21st timeslots.
NE31
2-ML1-5

The service planning information contains the information about all the parameters required for configuring the NE data. 10.5.2.1 Service Planning (UNI Ports) The service planning information contains the information about all the parameters required for configuring UNI ports. 10.5.2.2 Service Planning (Service Information)

The service planning information contains the information about all the parameters required for configuring UNI ports. Table 10-27 to Table 10-28 provide UNI port information. Table 10-27 UNI Port Information (NE33) Parameter Port name E1 frame format E1 frame mode 2-ML1-1 conn_bts32_ces1 CRC-4 multiframe PCM31
Table 10-28 UNI port information (NE31) Parameter Port name E1 frame format E1 frame mode 2-ML1-5 conn_bsc_ces5 CRC-4 multiframe PCM31
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port names. l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types. During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual E1 frame format is double, the E1 port will report the LMFA alarm. l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid radio network.


Table 10-29 provides the the service planning information.
Table 10-29 Service information (CES service 1 of BTS32) Parameter CES Service 1 of BTS32 Source NE (NE33) Service ID Service name Service port Encapsulation mode 64 kbit/s timeslot Priority Protection scheme PW ID PW In/Out label ID of working tunnel PW switch node PW switch service ID PW switch service name 205 bts32_ces_service_01_1stp w 2-ML1-1 CESoPSN 1-21 CS7 Non-protection 205 205\205 1513 NE32 901 bts32_ces_service_mspw 206 206\206 1501 1-21 CS7 Sink NE (NE31) 206 bts32_ces_service_01_2ndc pw 2-ML1-5
NOTE
l OptiX RTN 950 supports point-to-point CES services only. That is, one PW cannot carry services from multiple E1 ports. l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots. In this example, the CESoPSN mode is adopted because the allocation of 64 kbit/s timeslots is specified, PWs are carried on radio links, and the radio bandwidth is better utilized. l The default PHB service class for CES services is EF. If CES services are transmitted on the ISU2/ISX2, set the PHB service class to CS7 to decrease the CES service transmission delay and jitters. l If an MS-PW is used, the label values of the first segment and the last segment must be different.

NOTE
Issue 03 (2011-04-10)
10-49


Procedure
Step 1 See A.8.6.1 Creating CES Services and create CES services. l Parameters of NE33 The values for the related parameters that need to be set in the main interface are as follows. Parameter NE33 CES Service of BTS32 (First Segment of PW) Service ID(e.g.1,3-6) Service name Mode Source Board Source Low Channel(e.g.1,3-6) Source 64K Timeslot(e.g.1,3-6) Pri PW Type
10-50
205 bts32_ces_service_01_1stpw UNI-NNI 2-ML1 1 1-21 CS7 CESoPSN
Issue 03 (2011-04-10)
Parameter
NE33 CES Service of BTS32 (First Segment of PW)
Protection Type
No Protection
The values for the related parameters that need to be set in the Port Attributes tab page are as follows. Parameter NE33 2-ML1-1 Port Mode Frame Format Frame Mode Layer 1 CRC-4 Multiframe 31
The values for the basic PW attributes that need to be set in the PW tab are as follows. Parameter NE33 CES Service of BTS32 (First Segment of PW) PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel 205 Static MPLS 205 205 MPLS 1513
The values for the Advanced Attributes that need to be set in the PW tab are as follows. Parameter NE33 CES Service of BTS32 (First Segment of PW) Control Channel Type VCCV Verification Mode CW Ping
Issue 03 (2011-04-10)
10-51
Parameter
NE33 CES Service of BTS32 (First Segment of PW)
Sequence Number Mode l Parameters of NE31
Huawei Mode
The values for the related parameters that need to be set in the main interface are as follows. Parameter NE31 CES Service of BTS32 (Last Segment of PW) Service ID(e.g.1,3-6) Service name Mode Source Board Source Low Channel(e.g.1,3-6) Source 64K Timeslot(e.g.1,3-6) Pri PW Type Protection Type 206 bts32_ces_service_01_2ndpw UNI-NNI 2-ML1 5 1-21 CS7 CESoPSN No Protection
The values for the related parameters that need to be set in the Port Attributes tab page are as follows. Parameter NE31 2-ML1-1 Port Mode Frame Format Frame Mode Layer 1 CRC-4 Multiframe 31
The values for the basic PW attributes that need to be set in the PW tab are as follows.
10-52
Issue 03 (2011-04-10)
Parameter
NE31 CES Service of BTS32 (Last Segment of PW)
PW ID PW Signaling Type PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
The values for the Advanced Attributes that need to be set in the PW tab are as follows. Parameter NE31 CES Service of BTS32 (Last Segment of PW) Control Channel Type VCCV Verification Mode Sequence Number Mode CW Ping Huawei Mode
Step 2 See A.8.4.2 Creating an MS-PW and create an MS-PW on NE32. The values for the related parameters that need to be set in the main interface are as follows. Parameter ID Name Service Type NE32 901 bts32_ces_service_mspw CES Service
Parameter
NE32 CES Service of BTS32 (First Segment of PW) CES Service of BTS32 (Last Segment of PW) 206 Static
10-53
PW ID PW Signaling Type
Issue 03 (2011-04-10)
205 Static
Parameter
NE32 CES Service of BTS32 (First Segment of PW) CES Service of BTS32 (Last Segment of PW) CESoPSN 206 206 Manually MPLS 1501
PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel
CESoPSN 205 205 Manually MPLS 1513
The values for related parameters that need to be set in Advanced Attributes are as follows. The other parameters take their default values. Parameter NE32 CES Service of BTS32 (First Segment of PW) Control Channel Type VCCV Verification Mode 64K Timeslot Number CW Ping 21 CES Service of BTS32 (Last Segment of PW) CW Ping 21
----End

Procedure
Step 1 See A.12.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER testers. l Because the CES services under test adopt the CESoPSN mode, BER testers must be used for testing nx64 kbit/s services according to timeslot allocation. l It is recommended that you connect BER testers to NE31 and perform loopbacks on NE11. The test results should be no bit errors. ----End
10-54
Issue 03 (2011-04-10)
10.6 Configuration Example (Common ATM Services)

This section uses a common ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in n-to-1 VCC mode. 10.6.1 Networking Diagram This section describes the networking information about the NEs. 10.6.2 ServicePlanning You need to plan the corresponding parameter information before service configuration. 10.6.3 Per-NE Configuration Process This section describes the process for configuring ATM services.

This section describes the networking information about the NEs. Based on 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection), configure information about ATM services transmitted from BTS13 and BTS14 according to the following network planning information (as shown in Figure 10-18): l l Information about ATM service ports is provided in Table 10-31. A bidirectional tunnel (ID: 1503), which has a protection tunnel, is available between NE11 and NE31. This tunnel and its corresponding information have been configured in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). None of the services accessed from BTSs occupies only part of an E1 timeslot. Each BTS has real-time voice services, signaling services (CBR services), HSDPA data services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99 non-real-time services (nrt-VBR services).
l l

G E G E

E1
NE11
G E
NE31 NE21
G E
E1 RNC
E1
E1 loo p
R99 BTS13
R99 BTS14
Issue 03 (2011-04-10)
10-55
Table 10-31 Information about service ports NE NE11 Service Port 1-SP3S-1 Description Configure this port to receive BTS13 services through a Hybrid radio chain network. For the service configuration process, see 6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network). Configure these ports to receive BTS14 services through a Hybrid radio chain network. For the service configuration process, see 6.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network). Use an E1 cable to connect this port to port 1-SP3S-1 so that the E1 services from BTS13 are switched from the TDM plane to the packet plane. Use E1 cables to connect these ports to ports 1-SP3S-2 to 1-SP3S-5 so that the E1 services from BTS14 are switched from the TDM plane to the packet plane. Configure these ports to transmit BTS13 and BTS14 services to the RNC.
1-SP3S-2 to 1-SP3S-5
4-ML1-2
4-ML1-3 to 4-ML1-6
NE31
2-ML1-6 to 2-ML1-13
NOTE
If E1 services are received directly from Smart E1 ports, you need not connect the Smart E1 ports with corresponding PDH ports with E1 cables.
10.6.2 ServicePlanning
You need to plan the corresponding parameter information before service configuration. 10.6.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.6.2.2 Service Planning (ATM/IMA Information)
The service planning information contains the information about all the parameters required for configuring ATM/IMA services. 10.6.2.3 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies. 10.6.2.4 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring ATM services.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-32 and Table 10-33 provide planning information about UNI ports. Table 10-32 Information about NNI ports (NE11) Parameter Port name Frame format Frame mode 4-ML1-2 conn_bts13_atm1 CRC-4 multiframe PCM30 4-ML1-3 to 4-ML1-6 conn_bts14_ima1 to conn_bts14_ima4 CRC-4 multiframe PCM30
Table 10-33 Information about UNI ports (NE31) Parameter Port name Frame format Frame mode 2-ML1-6 to 2-ML1-13 conn_rnc_ima1 to conn_rnc_ima8 CRC-4 multiframe PCM30
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire network in a unified manner. l As specified in ITU-T G.804, ATM service ports use the CRC-4 multiframe format and PCM30 frame mode by default. The E1 frame format and frame mode must be the same as those at the opposite end. l ATM services are converged from a Hybrid radio chain network. On the Hybrid radio chain network, E1 services are transmitted in Native E1 mode. Therefore, set the information about the UNI ports based on BTS configurations.
10.6.2.2 Service Planning (ATM/IMA Information)

The service planning information contains the information about all the parameters required for configuring ATM/IMA services.
Table 10-34 and Table 10-35 provide ATM/IMA information. Table 10-34 ATM/IMA information (NE11) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Minimum number of activated links Differential delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling 4-ML1-1 (TRUNK1) 4-ML1-2 Disabled 4-ML1-2 (TRUNK2) 4-ML1-3 to 4-ML1-6 Enabled 1.1 128 Symmetrical mode and symmetrical operation 1
conn_bts13_trunk1 UNI Enabled
25 ITC conn_bts14_trunk2 UNI Enabled
Table 10-35 ATM/IMA information (NE31) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Differential delay tolerance Clock mode ATM port name 2-ML1-1 (TRUNK1) 2-ML1-6 to 2-ML1-13 Enabled 1.1 128 Symmetrical mode and symmetrical operation 25 ITC conn_rnc_trunk1
10-58
Issue 03 (2011-04-10)
Parameter Port type ATM cell payload scrambling
2-ML1-1 (TRUNK1) UNI Enabled
NOTE
l If carried over a single E1, ATM services from a BTS are generally transmitted and received through a single UNI port. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from a BTS are transmitted and received through IMA trunks. l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected equipment. Normally, the BTS/RNC configurations are as follows: l IMA protocol version: 1.1 l IMA frame length: 128 l IMA symmetric mode: symmetrical mode and symmetrical operation l The differentiated delay tolerance: 25 l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the NE at the opposite end of the IMA link.

The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies.
Mapping Information Between ATM Service Types and ATM Service Classes
Table 10-36 provides the mapping information between ATM service types and the ATM service classes. Table 10-36 Mapping information between ATM service types and the ATM service classes Parameter CBR rt-VBR nrt-VBR UBR PHB Service Class EF AF3 AF2 BE
This mapping table is consistent with "DefaultAtmCosMap". Therefore, you can use the default CoS mapping table during service configuration.
Information about ATM policies

The parameter values of the ATM policy differ with the E1 quantity and service type.
NE11 uses one E1 to receive and transmit BTS13 services and use four E1s to receive and transmit BTS14 services. Both BTS13 services and BTS14 services contain CBR, UBR, rt-VBR, and ntr-VBR services. An ATM policy needs to be configured for each type of service; therefore, up to eight ATM policies need to be configured on NE11. Eight ATM policies also need to be configured on NE31. Table 10-37 Information about the 1xE1 ATM policy Parameter Service Type CBR Service Policy ID Policy name Service type Traffic type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Clp01Mcr(cell/ s) MBS (cell) CDVT (us) Discard Traffic Frame UPC/NPC 1 1e1_cbr CBR ClpTransparent NoScr 175 102400 Disabled Disabled rt-VBR Service 2 1e1_rtvbr RT-VBR ClpTransparentScr 1859 1685 1000 10240 Disabled Disabled nrt-VBR Service 3 1e1_nrtvbr NRT-VBR NoClpScr 1859 1685 1000 Disabled Disabled UBR Service 4 1e1_ubr UBR NoClpNoScr 1859 Disabled Disabled
Table 10-38 Information about the 4xE1 ATM policy Parameter Service Type CBR Service Policy ID Policy name Service type
10-60
rt-VBR Service 6 4e1_rtvbr RT-VBR
nrt-VBR Service 7 4e1_nrtvbr NRT-VBR
UBR Service 8 4e1_ubr UBR

Issue 03 (2011-04-10)
5 4e1_cbr CBR
Parameter
Service Type CBR Service rt-VBR Service ClpTransparentScr 2252 2048 1000 10240 Disabled Disabled nrt-VBR Service NoClpScr 9295 8799 1000 Disabled Disabled UBR Service NoClpNoScr 9295 Disabled Disabled
Traffic type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Clp01Mcr(cell/ s) MBS (cell) CDVT (us) Discard Traffic Frame UPC/NPC
ClpTransparent NoScr 500 102400 Disabled Disabled

The service planning information contains the information about all the parameters required for configuring ATM services. Table 10-39 provides the service planning information. Table 10-39 Service information (ATM services from BTS13 and BTS14) Parame ter Service name Service ID Service type Connect ion type ATM Services from BTS13 and BTS14 Source NE (NE11) bts13_bts14_atmservice 101 UNIs-NNI PVC Sink NE (NE31)
Issue 03 (2011-04-10)
10-61
Parame ter Protecti on type
ATM Services from BTS13 and BTS14 Source NE (NE11) No protection Sink NE (NE31)
ATM connection information (source NE) Connect ion name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstrea m QoS Policy Downst ream QoS policy bts13_cb r_atm 4-ML1 TRUNK1 13 33 13 33 1 (1e1_cbr ) 1 (1e1_cbr ) 13 34 13 34 2 (1e1_rt vbr) 2 (1e1_rt vbr) 13 35 13 35 3 (1e1_n rtvbr) 3 (1e1_n rtvbr) 13 36 13 36 4 (1e1_u br) 4 (1e1_u br) TRUNK2 14 33 14 33 5 (4e1_c br) 5 (4e1_c br) 14 34 14 34 6 (4e1_rt vbr) 6 (4e1_rt vbr) 14 35 14 35 7 (4e1_n rtvbr) 7 (4e1_n rtvbr) 14 36 14 36 8 (4e1_u br) 8 (4e1_u br) bts13_r tvbr_at m bts13_ nrtvbr_ atm bts13_ ubr_at m bts14_ cbr_at m bts14_r tvbr_at m bts14_ nrtvbr_ atm bts14_ ubr_at m
ATM connection information (sink NE) Connect ion name Service board Service port Source VPI Source VCI bts13_cb r_atm 2-ML1 TRUNK1 13 33 13 34 13 35 13 36 14 33 14 34 14 35 14 36 bts13_r tvbr_at m bts13_ nrtvbr_ atm bts13_ ubr_at m bts14_ cbr_at m bts14_r tvbr_at m bts14_ nrtvbr_ atm bts14_ ubr_at m
10-62
Issue 03 (2011-04-10)
Parame ter Sink VPI Sink VCI Upstrea m QoS policy Downst ream QoS policy
ATM Services from BTS13 and BTS14 Source NE (NE11) 13 33 1 (1e1_cbr ) 1 (1e1_cbr ) 13 34 2 (1e1_rt vbr) 2 (1e1_rt vbr) 13 35 3 (1e1_n rtvbr) 3 (1e1_n rtvbr) 13 36 4 (1e1_u br) 4 (1e1_u br) Sink NE (NE31) 14 33 5 (4e1_c br) 5 (4e1_c br) 14 34 6 (4e1_rt vbr) 6 (4e1_rt vbr) 14 35 7 (4e1_n rtvbr) 7 (4e1_n rtvbr) 14 36 8 (4e1_u br) 8 (4e1_u br)
PW information PW ID PW ingress/ egress label Encapsu lation Tunnel Control Word Control Channel Type VCCV Verifica tion Mode 101 101/101
ATM n-to-one VCC 1503 No Use Alert Label
Ping
CoS mapping information CoS mappin g DefaultAtmCosMap
Issue 03 (2011-04-10)
10-63

NOTE
l In this example, the n-to-one VCC encapsulation mode is used due to the following reasons: l The PSN between NE11 and NE31 has GE links, which provide much higher bandwidth than required for the planned packet services. Therefore, there is a very low possibility that ATM service congestion occur on the PSN; multiple ATM connections can be carried by one PW. l On the ATM trunks at UNI ports, service congestion may occur. Therefore, ATM traffic management needs to be performed for different types of services.

This section describes the process for configuring ATM services. 10.6.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port information. 10.6.3.2 Configuration Process (IMA Information) This section describes the procedure for configuring IMA information. 10.6.3.3 Configuration Process (QoS) This section describes the process for configuring QoS information for ATM services. 10.6.3.4 Configuration Process (Service Information) This section describes the process for configuring service information. 10.6.3.5 Configuration Process (Verifying ATM Service Configurations) This section describes the process for verifying ATM service configurations.
10.6.3.1 Configuration Process (UNI Ports)

This section describes the process for configuring UNI port information.
Procedure
Step 1 See A.5.4.1 Setting Basic Attributes of Smart E1 Ports and set the general attributes of Smart E1 ports. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-2 Name Port Mode conn_bts13_atm_1 Layer 2 4-ML1-3 to 4-ML1-6 conn_bts14_ima_1 to conn_bts14_ima_4 Layer 2
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 to 2-ML1-13 Name
10-64
conn_rnc_ima_1 to conn_rnc_ima_8
Parameter
NE31 2-ML1-6 to 2-ML1-13
Port Mode
Layer 2
Step 2 See A.5.4.2 Setting Advanced Attributes of Smart E1 Ports and set the advanced attributes of Smart E1 ports. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-2 Frame Format Frame Mode CRC-4 Multiframe 30 4-ML1-3 to 4-ML1-6 CRC-4 Multiframe 30
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 to 2-ML1-13 Frame Format Frame Mode CRC-4 Multiframe 30
----End
10.6.3.2 Configuration Process (IMA Information)

This section describes the procedure for configuring IMA information.
Procedure
Step 1 See A.8.7.1 Binding ATM TRUNKs and bind the ATM trunk. l The values for the related parameters for NE11 are provided as follows. Parameter NE11 Trunk1 (Connecting BTS13 Services) Available Boards Configurable Ports Level 4-ML1 4-ML1-1 (Trunk1) E1 Trunk2 (Connecting BTS14 Services) 4-ML1 4-ML1-2 (Trunk2) E1
Issue 03 (2011-04-10)
10-65
Parameter
NE11 Trunk1 (Connecting BTS13 Services) Trunk2 (Connecting BTS14 Services) 4-ML1-3 (conn_bts14_ima_1) to 4ML1-6 (conn_bts14_ima_4)
Available Resources
4-ML1-2 (conn_bts13_atm_1)
l The values for the related parameters for NE31 are provided as follows. Parameter NE31 Trunk1 (Connecting the RNC) Available Boards Configurable Ports Level Available Resources 2-ML1 2-ML1-1 (Trunk1) E1 2-ML1-6 (conn_rnc_ima_1) to 2-ML1-13 (conn_rnc_ima_8)
Step 2 See A.8.7.2 Configuring an IMA group and create an IMA group. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-1 (Trunk1) (Connecting BTS13 Services) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Disabled 4-ML1-2 (Trunk2) (Connecting BTS14 Services) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operation 25
10-66
Issue 03 (2011-04-10)
Parameter
NE31 2-ML1-1 (Trunk1) (Connecting the RNC)
IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms)
Enabled 1.1 128 Symmetrical Mode and Symmetrical Operation 25
Step 3 See A.8.7.3 Setting ATM Port Parameters and set ATM port parameters. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-1 (Trunk1) (Connecting BTS13 Services) Name Port Type ATM Cell Payload Scrambling conn_bts13_trunk1 UNI Enabled 4-ML1-2 (Trunk2) (Connecting BTS14 Services) conn_bts14_trunk2 UNI Enabled
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-1 (Trunk1) (Connecting the RNC) Name Port Type ATM Cell Payload Scrambling conn_rnc_trunk1 UNI Enabled
----End

This section describes the process for configuring QoS information for ATM services.
Issue 03 (2011-04-10)
10-67
Procedure
Step 1 See A.8.9.3 Creating an ATM Policy and create ATM policies. Parameters for NE11 and NE31: Parameter NE11 and NE31 CBR Service (1xE1) Policy ID Policy Name Service Type Traffic Type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame UPC/NPC 1 1e1_cbr CBR ClpTransparent NoScr 175 102400 rt-VBR Service (1xE1) 2 1e1_rtvbr RT-VBR ClpTransparentScr 1859 1685 1000 10240 nrt-VBR Service (1xE1) 3 1e1_nrtvbr NRT-VBR NoClpScr 1859 1685 1000 UBR Service (1xE1) 4 1e1_ubr UBR NoClpNoScr 1859 -
Disabled Disabled
Disabled Disabled
Disabled Disabled
Disabled Disabled
Parameter
NE11 and NE31 (Continued) CBR Service rt-VBR Service 6 4e1_rtvbr RT-VBR ClpTransparentScr 2252 nrt-VBR Service 7 4e1_nrtvbr NRT-VBR NoClpScr 9295 UBR Service 8 4e1_ubr UBR NoClpNoScr 9295
Policy ID Policy Name Service Type Traffic Type Clp01Pcr(cell/ s)
5 4e1_cbr CBR ClpTransparent NoScr 500
10-68
Issue 03 (2011-04-10)
Parameter
NE11 and NE31 (Continued) CBR Service rt-VBR Service 2048 1000 10240 nrt-VBR Service 8799 1000 UBR Service -
Clp01Scr(cell/ s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame UPC/NPC
102400
Disabled Disabled
Disabled Disabled
Disabled Disabled
Disabled Disabled
----End

Procedure
Step 1 See A.8.8.1 Creating ATM Services and create ATM services. l Parameters of NE11: The values for the related parameters that need to be set in the main interface are as follows. Parameter NE11 ATM Services from BTS13 and BTS14 Service Name Service ID Direction Connection Type Protection Type bts13_bts14_atmservice 101 UNIs-NNI PVC No Protection
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows.
Issue 03 (2011-04-10)
10-69
Param eter Conne ction Name Source Port
NE11 ATM Services from BTS13 and BTS14 bts13_ cbr_at m 4ML1-1 (TRU NK1) 4ML1(2) 13 bts13_r tvbr_at m 4ML1-1 (TRU NK1) 4ML1(2) 13 bts13_ nrtvbr_ atm 4ML1-1 (TRU NK1) 4ML1(2) 13 bts13_ ubr_at m 4ML1-1 (TRU NK1) 4ML1(2) 13 bts14_ cbr_at m 4ML1-2 (TRU NK2) 4ML1(3-6) 14 bts14_r tvbr_at m 4ML1-2 (TRU NK2) 4ML1(3-6) 14 bts14_ nrtvbr_ atm 4ML1-2 (TRU NK2) 4ML1(3-6) 14 bts14_ ubr_at m 4ML1-2 (TRU NK2) 4ML1(3-6) 14
Source Bind Path Source VPI (eg. 35,3639) Source VCI (eg. 35,3639) PW ID Sink VPI (eg. 35,3639) Sink VCI (eg. 35,3639) Uplink Policy Down link Policy
33
34
35
36
33
34
35
36
101 13
101 13
101 13
101 13
101 14
101 14
101 14
101 14
33
34
35
36
33
34
35
36
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
In the Configure PW dialog box, the values for the related parameters that need to be set in the General Attributes tab page are provided as follows.
10-70
Issue 03 (2011-04-10)
Parameter
NE11 ATM Services from BTS13 and BTS14
PW ID PW Signaling Type PW Type PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel
101 Static ATM n-to-one VCC cell transport 101
101 1503
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE11 ATM Services from BTS13 and BTS14 Control Word Control Channel Type VCCV Verification Mode NO use Alert Label Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are provided as follows. Parameter NE11 ATM Services from BTS13 and BTS14 PW ID CoS Mapping l Parameters of NE31: The values for the related parameters that need to be set in the main interface are as follows. 101 DefaultAtmCosMap
Issue 03 (2011-04-10)
10-71
Parameter
Service Name Service ID Direction Connection Type Protection Type
bts13_bts14_atmservice 101 UNIs-NNI PVC No protection
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows. Param eter Conne ction Name Source Port NE31 ATM Services from BTS13 and BTS14 bts13_ cbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 13 bts13_r tvbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 13 bts13_ nrtvbr_ atm 2ML1-1 (TRU NK1) 2ML1(6-13) 13 bts13_ ubr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 13 bts14_ cbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 14 bts14_r tvbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 14 bts14_ nrtvbr_ atm 2ML1-1 (TRU NK1) 2ML1(6-13) 14 bts14_ ubr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 14
Source Bind Path Source VPI (eg. 35,3639) Source VCI (eg. 35,3639) PW ID Sink VPI (eg. 35,3639)
33
34
35
36
33
34
35
36
101 13
101 13
101 13
101 13
101 14
101 14
101 14
101 14
10-72
Issue 03 (2011-04-10)
Param eter Sink VCI (eg. 35,3639) Uplink Policy Down link Policy
NE31 ATM Services from BTS13 and BTS14 33 34 35 36 33 34 35 36
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parameter NE31 ATM Services from BTS13 and BTS14 PW ID PW Signaling Type PW Type PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel 101 Static ATM n-to-one VCC cell transport 101
101
1503
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE31 ATM Services from BTS13 and BTS14 Control Word Control Channel Type NO use Alert Label
Issue 03 (2011-04-10)
10-73
Parameter
VCCV Verification Mode
Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are provided as follows. Parameter NE31 ATM Services from BTS13 and BTS14 PW ID CoS Mapping 101 DefaultAtmCosMap
----End
10.6.3.5 Configuration Process (Verifying ATM Service Configurations)

This section describes the process for verifying ATM service configurations.
Procedure
Step 1 See A.12.4 Testing ATM Services and verify the ATM service configurations. The "success" verification result should be displayed. ----End
10.7 Configuration Example (Fractional ATM Services)

This section uses a Fractional ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in n-to-1 VCC mode. 10.7.1 Networking Diagram This section describes the networking information about the NEs. 10.7.2 ServicePlanning You need to plan the corresponding parameter information before service configuration. 10.7.3 Per-NE Configuration Process This section describes the process for configuring ATM services on a per-NE basis.

Based on 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection), configure information about ATM services transmitted from BTS37 and BTS38 according to the following network planning information (as shown in Figure 10-19): l l Information about ATM service ports is provided in Table 10-40. A bidirectional tunnel (ID: 1505), which has a protection tunnel, is available between NE21 and NE31. This tunnel and its corresponding information have been configured in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). NE21 uses a Fractional E1 to receive and transmit BTS37 and BTS38 services. The BTS37 services occupy the 1st to 15th timeslots of the E1 port and the BTS38 services occupy the 17th to 31st timeslots of the E1 port. Each BTS has real-time voice services, signaling services (CBR services), HSDPA data services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99 non-real-time services (nrt-VBR services).
G E
G E
NE32 NE11
G E
NE31 NE21
G E
E1
E1
l ne n tu g 0 5) n 5 ki o r D=1 W (I
RNC
R99 BTS37
R99 BTS38
Issue 03 (2011-04-10)
10-75
Table 10-40 Information about service ports NE NE21 Service Port 6-ML1-3 Description BTS37 and BTS38 services occupy different timeslots of the same E1 port. The BTS37 services occupy the 1st to 15th timeslots of the E1 port and the BTS38 services occupy the 17th to 31st timeslots of the E1 port. Configure these ports to transmit BTS37 and BTS38 services to the RNC.
NE31
2-ML1-6 to 2-ML1-13
You need to plan the corresponding parameter information before service configuration. 10.7.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.7.2.2 Service Planning (ATM/IMA Information) The service planning information contains the information about all the parameters required for configuring ATM/IMA information. 10.7.2.3 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies. 10.7.2.4 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring ATM services.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-41 to Table 10-43 provide the planning information. Table 10-41 Information about UNI ports (NE21) Parameter Port name Frame format Frame mode 6-ML1-3 conn_bts37_bts38_frac CRC-4 multiframe PCM31
10-76
Issue 03 (2011-04-10)
A UNI port that transmits the fractional ATM service is described as a serial port.Table 10-42 provides the planning information about serial ports. Table 10-42 Serial port information (NE21) Paramete r Port name Level Port 64K timeslot Port mode Serial Port Where BTS37 Services Are Located conn_bts37_sp01 64K timeslot 6-ML1-3 Timeslots 1 to 15 Layer 2 Serial Port Where BTS38 Services Are Located conn_bts38_sp02 64K timeslot 6-ML1-3 Timeslots 17 to 31 Layer 2
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire network in a unified manner. l The E1 frame format and frame mode must be the same as those of service access equipment. l For an E1 port that transmits Fractional ATM services, set the E1 frame mode to PCM31.

The service planning information contains the information about all the parameters required for configuring ATM/IMA information. Table 10-44 and Table 10-45 provide ATM/IMA information. Table 10-44 ATM/IMA information (NE21) Parameter Bound port IMA protocol enabled status
Issue 03 (2011-04-10)
6-ML1-1 (TRUNK1) 6-ML1-3 (conn_bts37_sp01) Disabled
6-ML1-2 (TRUNK2) 6-ML1-3 (conn_bts38_sp02) Disabled
10-77
Parameter IMA protocol version IMA frame length IMA symmetric mode Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling
6-ML1-1 (TRUNK1) conn_bts37_trunk1 UNI Enabled
6-ML1-2 (TRUNK2) conn_bts38_trunk2 UNI Enabled
Table 10-45 ATM/IMA information (NE31) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling 2-ML1-1 (TRUNK1) 2-ML1-6 to 2-ML1-13 Enabled 1.1 128 Symmetrical mode and symmetrical operation 25 ITC conn_rnc_trunk1 UNI Enabled
10-78
Issue 03 (2011-04-10)
NOTE
l If one E1 is divided into several timeslots to transmit ATM services from BTSs, the Fractional ATM mode is used and the IMA protocol is disabled in most cases. l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected equipment. Normally, the BTS/RNC configurations are as follows: l IMA protocol version: 1.1 l IMA frame length: 128 l IMA symmetric mode: symmetrical mode and symmetrical operation l The differentiated delay tolerance: 25 l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the NE at the opposite end of the IMA link.


The parameter values of the ATM policy differ with the E1 quantity and service type. NE21 uses timeslots 1 to 15 of one E1 port to receive and transmit BTS37 services and timeslots 17 to 31 to receive and transmit BTS38 services. Both BTS37 services and BTS38 services contain CBR, UBR, rt-VBR, and ntr-VBR services. An ATM policy needs to be configured for each type of service; therefore, up to four ATM policies need to be configured. Table 10-47 shows the planning information about the ATM policy.
Issue 03 (2011-04-10)
10-79
Table 10-47 Information about the 15-timeslot E1 ATM policy Parameter Service Type CBR Service Policy ID Policy name Service type Traffic type Clp01Pcr (cell/ s) Clp01Scr (cell/ s) Clp0Pcr (cell/s) Clp0Scr (cell/s) Clp01Mcr (cell/ s) MBS (cell) CDVT (us) Discard Traffic Frame UPC/NPC 9 15ts_cbr CBR ClpTransparent NoScr 105 102400 Disabled Disabled rt-VBR Service 10 15ts_rtvbr RT-VBR ClpTransparentScr 960 858 1000 10240 Disabled Disabled nrt-VBR Service 11 15ts_nrtvbr NRT-VBR NoClpScr 960 858 1000 Disabled Disabled UBR Service 12 15ts_ubr UBR NoClpNoScr 960 Disabled Disabled

The service planning information contains the information about all the parameters required for configuring ATM services. Table 10-48 provides the service planning information. Table 10-48 Service information (ATM services from BTS37 and BTS38) Parame ter Service name Service ID
10-80
ATM Services from BTS37 and BTS38 Source NE (NE21) bts37_bts38_fracatmservice 102 Sink NE (NE31)
Issue 03 (2011-04-10)
Parame ter Service type Connect ion type Protecti on type Source NE
ATM Services from BTS37 and BTS38 Source NE (NE21) UNIs-NNI PVC No protection NE21 Sink NE (NE31)
ATM connection information (source NE) Connect ion name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstrea m QoS policy Downstr eam QoS policy bts37_cb r_atm 6-ML1 TRUNK1 37 33 37 33 9 37 34 37 34 10 37 35 37 35 11 37 36 37 36 12 TRUNK2 38 33 38 33 9 38 34 38 34 10 38 35 38 35 11 38 36 38 36 12 bts37_r tvbr_at m bts37_ nrtvbr_ atmM bts37_ ubr_at m bts38_ cbr_at m bts38_r tvbr_at m bts38_ nrtvbr_ atmM bts38_ ubr_at m
10
11
12
10
11
12
ATM connection information (sink NE) Connect ion name Service board bts37_cb r_atm 2-ML1 bts37_r tvbr_at m bts37_ nrtvbr_ atmM bts37_ ubr_at m bts38_ cbr_at m bts38_r tvbr_at m bts38_ nrtvbr_ atmM bts38_ ubr_at m
Issue 03 (2011-04-10)
10-81
Parame ter Service port Source VPI Source VCI Sink VPI Sink VCI Upstrea m QoS policy Downstr eam QoS policy
ATM Services from BTS37 and BTS38 Source NE (NE21) TRUNK1 37 33 37 33 9 37 34 37 34 10 37 35 37 35 11 37 36 37 36 12 Sink NE (NE31) TRUNK2 38 33 38 33 9 38 34 38 34 10 38 35 38 35 11 38 36 38 36 12
10
11
12
10
11
12
PW information PW ID PW ingress/ egress label Encapsu lation type Tunnel Control Word Control Channel Type VCCV Verifica tion Mode 102 102/102
ATM n-to-one VCC
1505 No Use Alert Label
Ping
CoS mapping information
10-82
Issue 03 (2011-04-10)
Parame ter CoS mappin g
ATM Services from BTS37 and BTS38 Source NE (NE21) DefaultAtmCosMap Sink NE (NE31)
NOTE
l In this example, the n-to-one VCC encapsulation mode is used due to the following reasons: l The PSN between NE21 and NE31 has GE links, which provide much higher bandwidth than required for the planned packet services. Therefore, there is a very low possibility that ATM service congestion occur on the PSN; various types of ATM services can be transmitted over the same PW. l On the ATM trunks at UNI ports, service congestion may occur. Therefore, ATM traffic management needs to be performed for different types of services.

This section describes the process for configuring ATM services on a per-NE basis. 10.7.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port information. 10.7.3.2 Configuration Process (IMA Information) This section describes the process for configuring IMA information. 10.7.3.3 Configuration Process (QoS) This section describes the process for configuring QoS information of ATM services. 10.7.3.4 Configuration Process (Service Information) This section describes the process for configuring service information. 10.7.3.5 Configuration Process (Verifying ATM Service Configurations) This section describes the process for verifying ATM service configurations.

Procedure
Step 1 See A.5.4.1 Setting Basic Attributes of Smart E1 Ports and set the general attributes of Smart E1 ports. l The values for the related parameters of NE21 are provided as follows. Parameter NE21 6-ML1-3 Name Port Mode
Issue 03 (2011-04-10)
conn_bts37_bts38_frac Layer 1
10-83
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 to 2-ML1-13 Name Port Mode conn_rnc_ima_1 to conn_rnc_ima_8 Layer 2
Step 2 See A.5.4.2 Setting Advanced Attributes of Smart E1 Ports and set the advanced attributes of Smart E1 ports. l The values for the related parameters of NE21 are provided as follows. Parameter Value 6-ML1-3 Frame Format Frame Mode CRC-4 Multiframe 31
Step 3 See A.5.5.1 Creating Serial Ports and configure serial ports on NE21. The values for the serial port parameters are provided as follows. Parameter NE21 Serial Port Where BTS37 Services Are Located Port Name Level Used Board Used Port 64K Timeslot 1 conn_bts37_sp01 64K Timeslot 6-ML1 6-ML1-3 1-15 Serial Port Where BTS38 Services Are Located 2 conn_bts38_sp02 64K Timeslot 6-ML1 6-ML1-3 17-31
10-84
Issue 03 (2011-04-10)
Step 4 See A.5.5.2 Setting Basic Attributes of Serial Ports and set the basic attributes of serial ports on NE21. The values for basic attributes of serial ports that need to be set are as follows. Parameter NE21 conn_bts37_sp01 Port Mode Encapsulation Type Layer 2 ATM conn_bts38_sp02 Layer 2 ATM
----End

This section describes the process for configuring IMA information.
Procedure
Step 1 See A.8.7.1 Binding ATM TRUNKs and bind the ATM trunk. l The values for the related parameters of NE21 are provided as follows. Parameter Value Trunk1 (Connecting BTS37 Services) Available Boards Configurable Ports Level Available Resources 6-ML1 6-ML1-1 (Trunk1) Fractional E1 6-ML1-1 (conn_bts37_sp01) Trunk2 (Connecting BTS38 Services) 6-ML1 6-ML1-2 (Trunk2) Fractional E1 6-ML1-2 (conn_bts38_sp02)
Step 2 See A.8.7.2 Configuring an IMA group and create an IMA group.
l The values for the IMA group parameters of NE21 are provided as follows. Parameter NE21 6-ML1-1 (Trunk1) (Connecting BTS37 Services) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Disabled 6-ML1-2 (Trunk2) (Connecting BTS38 Services) Disabled -
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-1 (Trunk1) (Connecting the RNC) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operational 25
Step 3 See A.8.7.3 Setting ATM Port Parameters and set the ATM port parameters. l The values for the ATM port parameters of NE21 are provided as follows. Parameter NE21 6-ML1-1 (Trunk1) (Connecting BTS37 Services) Name Port Type ATM Cell Payload Scrambling conn_bts37_trunk1 UNI Enabled 6-ML1-2 (Trunk2) (Connecting BTS38 Services) conn_bts38_trunk2 UNI Enabled
10-86
Issue 03 (2011-04-10)
----End

This section describes the process for configuring QoS information of ATM services.
Procedure
Step 1 See A.8.9.3 Creating an ATM Policy and create the ATM policy. The values for the related parameters of NE21 and NE31 are provided as follows. Parameter NE21 and NE31 CBR Service (15 Timeslots in an E1) Policy ID Policy Name Service Type Traffic Type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
Issue 03 (2011-04-10)
rt-VBR Service (15 Timeslots in an E1) 10 15ts_rtvbr RT-VBR ClpTransparentScr 960 858 1000 10240
nrt-VBR Service (15 Timeslots in an E1) 11 15ts_nrtvbr NRT-VBR NoClpScr 960 858 1000 -
UBR Service (15 Timeslots in an E1) 12 15ts_ubr UBR NoClpNoScr 960 -
9 15ts_cbr CBR ClpTransparent NoScr 105 102400
Disabled
Disabled
Disabled
Disabled
10-87
Parameter
NE21 and NE31 CBR Service (15 Timeslots in an E1) rt-VBR Service (15 Timeslots in an E1) Disabled nrt-VBR Service (15 Timeslots in an E1) Disabled UBR Service (15 Timeslots in an E1) Disabled
UPC/NPC
Disabled
----End

Procedure
Step 1 See A.8.8.1 Creating ATM Services and create ATM services. l Parameters of NE21: The values for the related parameters that need to be set in the main interface are as follows. Parameter NE21 ATM Services from BTS37 and BTS38 Service Name Service ID Direction Connection Type Protection Type bts37_bts38_fracatmservice 102 UNIs-NNI PVC No Protection
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows. Param eter Conne ction Name Source Port NE21 ATM Services from BTS37 and BTS38 bts37_ cbr_at m 6ML1-1 (TRU NK1) bts37_r tvbr_at m 6ML1-1 (TRUN K1) bts37_ nrtvbr_ atmM 6ML1-1 (TRU NK1) bts37_ ubr_at m 6ML1-1 (TRU NK1) bts38_ cbr_at m 6ML1-2 (TRU NK2) bts38_r tvbr_at m 6ML1-2 (TRUN K2) bts38_ nrtvbr_ atmM 6ML1-2 (TRU NK2) bts38_ ubr_at m 6ML1-2 (TRU NK2)
10-88
Issue 03 (2011-04-10)
Param eter Source Bind Path Source VPI (eg. 35,3639) Source VCI (eg. 35,3639)
NE21 ATM Services from BTS37 and BTS38 6ML1(1) 37 6ML1(1) 37 6ML1(1) 37 6ML1(1) 37 6ML1(2) 38 6ML1(2) 38 6ML1(2) 38 6ML1(2) 38
33
34
35
36
33
34
35
36
PW ID 102 Sink VPI (eg. 35,3639) Sink VCI (eg. 35,3639) Uplin k Policy Down link Policy 37
102 37
102 37
102 37
102 38
102 38
102 38
102 38
33
34
35
36
33
34
35
36
10
11
12
10
11
12
10
11
12
10
11
12
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Param eter PW ID NE21 ATM Services from BTS37 and BTS38 102
Issue 03 (2011-04-10)
10-89
Param eter PW Signali ng Type PW Type PW Ingres s Label / Source Port PW Egress Label / Sink Port Ingres s Tunne l
NE21 ATM Services from BTS37 and BTS38 Static
ATM n-to-one VCC cell transport 102
102
1505
The values for the relevant parameters that need to be set in the CoS Mapping tab page are provided as follows.
10-90
Issue 03 (2011-04-10)
Param eter PW ID CoS Mappi ng
NE21 ATM Services from BTS37 and BTS38 102 DefaultAtmCosMap
l Parameters of NE31: The values for the related parameters that need to be set in the main interface are as follows. Parameter NE31 ATM Services from BTS37 and BTS38 Service Name Service ID Direction Connection Type Protection Type bts37_bts38_fracatmservice 102 UNIs-NNI PVC No Protection
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows. Param eter Conne ction Name Source Port NE31 ATM Services from BTS37 and BTS38 bts37_ cbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 37 bts37_r tvbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 37 bts37_ nrtvbr_ atmM 2ML1-1 (TRU NK1) 2ML1(6-13) 37 bts37_ ubr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 37 bts38_ cbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 38 bts38_r tvbr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 38 bts38_ nrtvbr_ atmM 2ML1-1 (TRU NK1) 2ML1(6-13) 38 bts38_ ubr_at m 2ML1-1 (TRU NK1) 2ML1(6-13) 38
Source Bind Path Source VPI (eg. 35,3639)
Issue 03 (2011-04-10)
10-91
Param eter Source VCI (eg. 35,3639) PW ID Sink VPI (eg. 35,3639) Sink VCI (eg. 35,3639) Uplink Policy Down link Policy
NE31 ATM Services from BTS37 and BTS38 33 34 35 36 33 34 35 36
102 37
102 37
102 37
102 37
102 38
102 38
102 38
102 38
33
34
35
36
33
34
35
36
9 9
10 10
11 11
12 12
9 9
10 10
11 11
12 12
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Param eter PW ID PW Signali ng Type PW Type PW Ingres s Label / Source Port NE31 ATM Services from BTS37 and BTS38 102 Static
ATM n-to-one VCC cell transport 102
10-92
Issue 03 (2011-04-10)
Param eter PW Egress Label / Sink Port Ingres s Tunne l
NE31 ATM Services from BTS37 and BTS38 102
1505
The values for the relevant parameters that need to be set in the CoS Mapping tab page are provided as follows. Param eter PW ID CoS Mappi ng NE31 ATM Services from BTS37 and BTS38 102 DefaultAtmCosMap
----End

Issue 03 (2011-04-10)
10-93
Procedure
Step 1 See A.12.4 Testing ATM Services and verify the ATM service configurations. The verification result should be "success". ----End
10.8 Configuration Example (ATM Services on MS-PWs)

This section uses an ATM service carried on MS-PWs of a PSN as an example to describe how to configure ATM services according to service planning information. In this example, services are encapsulated in 1-to-1 VCC mode. 10.8.1 Networking Diagram This section describes the networking information about the NEs. 10.8.2 ServicePlanning You need to plan the corresponding parameter information before service configuration. 10.8.3 Per-NE Configuration Process This section describes the process for configuring ATM services on a per-NE basis.

This section describes the networking information about the NEs. Based on 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) and 9.4 Configuration Example (MPLS Tunnels with No Protection), configure information about ATM services transmitted from BTS34 according to the following network planning information (as shown in Figure 10-20): l l Information about ATM service ports is provided in Table 10-49. The information about the tunnel between NE34 and NE31 is as follows: A bidirectional tunnel (ID: 1515), which has no protection tunnel, is available between NE34 and NE32. This tunnel and its corresponding information have been configured in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between NE32 and NE31. This tunnel and its corresponding information have been configured in 9.4 Configuration Example (MPLS Tunnels with No Protection). l Each BTS has real-time voice services, signaling services (CBR services), HSDPA data services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99 non-real-time services (nrt-VBR services).
10-94
Issue 03 (2011-04-10)

Wo rki n (ID g tu n =1 5 n 1 5) el
NE34
E1
NE33
G E
R99 BTS34
W or ki ID ng t =1 u n 50 ne l 1
G E
NE32 NE11
G E
NE31 NE21
G E
E1
RNC
Table 10-49 Information about service ports NE NE34 Service Port 2-ML1-1 to 2-ML1-5 Description Configure these ports to receive and transmit BTS34 services. Configure these ports to transmit BTS34 services to the RNC.
NE31
2-ML1-6 to 2-ML1-13
You need to plan the corresponding parameter information before service configuration. 10.8.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.8.2.2 Service Planning (ATM/IMA Information) The service planning information contains the information about all the parameters required for configuring ATM/IMA information. 10.8.2.3 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies. 10.8.2.4 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring ATM services.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-50 and Table 10-51 provide planning information about UNI ports. Table 10-50 Information about UNI ports (NE34) Parameter Port name Frame format Frame mode 2-ML1-1 to 2-ML1-4 conn_bts34_ima1 to conn_bts34_ima4 CRC-4 multiframe PCM30

The service planning information contains the information about all the parameters required for configuring ATM/IMA information. Table 10-52 and Table 10-53 provide ATM/IMA information. Table 10-52 ATM/IMA information (NE34) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Differentiated delay tolerance Clock mode ATM port name
10-96
2-ML1-1 (TRUNK1) 2-ML1-1 to 2-ML1-4 Enabled 1.1 128 Symmetrical mode and symmetrical operation 25 ITC conn_bts34_trunk1
Issue 03 (2011-04-10)
Parameter Port type ATM cell payload scrambling
2-ML1-1 (TRUNK1) UNI Enabled
Table 10-53 ATM/IMA information (NE31) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling 2-ML1-1 (TRUNK1) 2-ML1-6 to 2-ML1-13 Enabled 1.1 128 Symmetrical mode and symmetrical operation 25 ITC conn_rnc_trunk1 UNI Enabled
NOTE
l If carried over a single E1, ATM services from a NodeB are transmitted and received through UNI ports. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from a NodeB are transmitted and received through IMA trunks. l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected equipment. Normally, the BTS/RNC configurations are as follows: l IMA protocol version: 1.1 l IMA frame length: 128 l IMA symmetric mode: symmetrical mode and symmetrical operation l The differentiated delay tolerance: 25 l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the NE at the opposite end of the IMA link.


The parameter values of the ATM policy differ with the E1 quantity and service type. NE34 uses four E1 ports to receive and transmit BTS34 services, which contain CBR, UBR, rt-VBR, and nrt-VBR services. Therefore, up to four ATM policies need to be configured. Table 10-55 shows the planning information about the ATM policy. Table 10-55 Information about the 4xE1 ATM policy Parameter Service Type CBR Service Policy ID Policy name Service type Traffic type Clp01Pcr (cell/ s) Clp01Scr (cell/ s) Clp0Pcr (cell/s) Clp0Scr (cell/s) Clp01Mcr (cell/ s)
10-98
rt-VBR Service 6 4e1_rtvbr RT-VBR ClpTransparentScr 2252 2048 -
nrt-VBR Service 7 4e1_nrtvbr NRT-VBR NoClpScr 9295 8799 -
UBR Service 8 4e1_ubr UBR NoClpNoScr 9295 -
5 4e1_cbr CBR ClpTransparent NoScr 500 -
Issue 03 (2011-04-10)
Parameter
Service Type CBR Service rt-VBR Service 1000 10240 Disabled Disabled nrt-VBR Service 1000 Disabled Disabled UBR Service Disabled Disabled
MBS (cell) CDVT (us) Discard Traffic Frame UPC/NPC
102400 Disabled Disabled

The service planning information contains the information about all the parameters required for configuring ATM services. Table 10-56 to Table 10-59 provide the service planning information. Table 10-56 Service information (CBR services from BTS34) Parameter CBR Services from BTS34 Source NE (NE34) Service name Service ID Service type Connection type Protection type bts34_cbrservice_1stpw 103 UNIs-NNI PVC No protection Sink NE (NE31) bts34_cbrservice_2ndpw 104
ATM connection information (source NE) Connection name Source board Source port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy bts34_cbr_atm 2-ML1 TRUNK1 34 33 34 33 5 (4e1_cbr) 5 (4e1_cbr)
Issue 03 (2011-04-10)
10-99
Parameter
CBR Services from BTS34 Source NE (NE34) Sink NE (NE31)
ATM connection information (sink NE) Connection name Source board Source port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy PW information PW ID PW ingress/egress label Encapsulation type Tunnel Control Word Control Channel Type VCCV Verification Mode CoS mapping information CoS mapping PW switching node PW switching service ID PW switching service name DefaultAtmCosMap NE32 902 bts34_cbrservice_mspw 103 103/103 ATM one-to-one VCC 1515 Must Use CW Ping 1501 104 104/104 bts34_cbr_atm 2-ML1 TRUNK1 34 33 34 33 5 (4e1_cbr) 5 (4e1_cbr)
Table 10-57 Service information (rt-VBR services from BTS34) Parameter rt-VBR Services from BTS34 Source NE (NE34) Service name bts34_rtvbrservice_1stpw Sink NE (NE31) bts34_rtvbrservice_2ndpw
10-100
Issue 03 (2011-04-10)
Parameter
rt-VBR Services from BTS34 Source NE (NE34) Sink NE (NE31) 106
Service ID Service type Connection type Protection type
105 UNIs-NNI PVC No protection
ATM connection information (source NE) Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy bts34_rtvbr_atm 2-ML1 TRUNK1 34 34 34 34 6 (4e1_rtvbr) 6 (4e1_rtvbr)
ATM connection information (sink NE) Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy PW information PW ID PW ingress/egress label Encapsulation type Tunnel 105 105/105 ATM one-to-one VCC 1515 1501 106 106/106 bts34_rtvbr_atm 2-ML1 TRUNK1 34 34 34 34 6 (4e1_rtvbr) 6 (4e1_rtvbr)
Issue 03 (2011-04-10)
10-101
Parameter
rt-VBR Services from BTS34 Source NE (NE34) Sink NE (NE31)
Control Word Control Channel Type VCCV Verification Mode CoS mapping information CoS mapping PW switching node PW switching ervice ID PW switching service name
Must Use CW Ping
DefaultAtmCosMap NE32 903 bts34_rtvbrservice_mspw
Table 10-58 Service information (nrt-VBR services from BTS34) Parameter nrt-VBR Services from BTS34 Source NE (NE34) Service name Service ID Service type Connection type Protection type bts34_nrtvbrservice_1stpw 107 UNIs-NNI PVC No protection Sink NE (NE31) bts34_nrtvbrservice_2ndpw 108
ATM connection information (source NE) Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy bts34_nrtvbr_atm 2-ML1 TRUNK1 34 35 34 35 7 (4e1_nrtvbr) 7 (4e1_nrtvbr)
ATM connection information (sink NE)
10-102
Issue 03 (2011-04-10)
Parameter
nrt-VBR Services from BTS34 Source NE (NE34) Sink NE (NE31)
Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy PW information PW ID PW ingress/egress label Encapsulation type Tunnel Control Word Control Channel Type VCCV Verification Mode CoS mapping information CoS mapping PW switching node PW switching service ID PW switching service name
bts34_nrtvbr_atm 2-ML1 TRUNK1 34 35 34 35 7 (4e1_nrtvbr) 7 (4e1_nrtvbr)
107 107/107 ATM one-to-one VCC 1515 Must Use CW Ping
108 108/108
1501
DefaultAtmCosMap NE32 904 bts34_nrtvbrservice_mspw
Table 10-59 Service information (UBR services from BTS34) Parameter UBR Services from BTS34 Source NE (NE34) Service name Service ID bts34_ubrservice_1stpw 109 Sink NE (NE31) bts34_ubrservice_2ndpw 110
Issue 03 (2011-04-10)
10-103
Parameter
UBR Services from BTS34 Source NE (NE34) Sink NE (NE31)
Service type Connection type Protection type
UNIs-NNI PVC No protection
ATM connection information (source NE) Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy bts_ubr_atm 2-ML1 TRUNK1 34 36 34 36 8 (4e1_ubr) 8 (4e1_ubr)
ATM connection information (sink NE) Connection name Service board Service port Source VPI Source VCI Sink VPI Sink VCI Upstream QoS policy Downstream QoS policy PW information PW ID PW ingress/egress label Encapsulation type Tunnel Control Word 109 109/109 ATM one-to-one VCC 1515 Must Use 1501 110 110/110 bts_ubr_atm 2-ML1 TRUNK1 34 36 34 36 8 (4e1_ubr) 8 (4e1_ubr)
10-104
Issue 03 (2011-04-10)
Parameter
UBR Services from BTS34 Source NE (NE34) Sink NE (NE31)
Control Channel Type VCCV Verification Mode CoS mapping information CoS mapping PW switching node PW switching service ID PW switching service name
CW Ping
DefaultAtmCosMap NE32 905 bts34_ubrservice_mspw
NOTE
l In this example, the 1-to-1 VCC encapsulation mode is used due to the following reasons: l The PSN between NE34 and NE31 has AM radio links. When the AM radio link capacity decreases, ATM services may be congested. Therefore, different PWs need to be configured to carry different ATM services. l On the ATM trunks at UNI ports, service congestion may occur. Therefore, ATM traffic management needs to be performed for different types of services. l When MS-PWs are used, the label values of the forward PW and the backward PW must be different.

This section describes the process for configuring ATM services on a per-NE basis. 10.8.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port information. 10.8.3.2 Configuration Process (IMA Information) This section describes the process for configuring IMA information. 10.8.3.3 Configuration Process (QoS) This section describes the process for configuring QoS information. 10.8.3.4 Configuration Process (Service Information) This section describes the process for configuring service information. 10.8.3.5 Configuration Process (Verifying ATM Service Configurations) This section describes the process for verifying ATM service configurations.

Procedure
Step 1 See A.5.4.1 Setting Basic Attributes of Smart E1 Ports and set general attributes of Smart E1 ports.
l The values for the related parameters of NE34 are provided as follows. Parameter NE34 2-ML1-1 to 2-ML1-4 Name Port Mode conn_bts34_ima1 to conn_bts34_ima4 Layer 2
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 to 2-ML1-13 Name Port Mode conn_rnc_ima1 to conn_rnc_ima8 Layer 2
Step 2 See A.5.4.2 Setting Advanced Attributes of Smart E1 Ports and set advanced attributes of Smart E1 ports. l The values for the related parameters of NE34 are provided as follows. Parameter NE34 2-ML1-1 to 2-ML1-4 Frame Format Frame Mode CRC-4 Multiframe 30
----End

Procedure
Step 1 See A.8.7.1 Binding ATM TRUNKs and bind ATM trunks. l The values for the related parameters of NE34 are provided as follows.
Parameter
NE34 Trunk1 (Connecting BTS34 Services)
Available Boards Configurable Ports Level Available Resources
2-ML1 2-ML1-1 to 2-ML1-4 E1 2-ML1-1 (conn_bts34_ima1) to 2-ML1-4 (conn_bts34_ima4)
Step 2 See A.8.7.2 Configuring an IMA group and configure an IMA group. l The values for the related parameters of NE34 are provided as follows. Parameter NE34 2-ML1-1 (TRUNK1) (Connecting BTS34 Services) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operational 25
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-1 (Trunk1) (Connecting the RNC) IMA Protocol Enable Status
Issue 03 (2011-04-10)
Enabled
10-107
Parameter
NE31 2-ML1-1 (Trunk1) (Connecting the RNC)
IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms)
1.1 128 Symmetrical Mode and Symmetrical Operational 25
Step 3 See A.8.7.3 Setting ATM Port Parameters and set ATM port parameters. l The values for the related parameters of NE34 are provided as follows. Parameter NE34 2-ML1-1 (TRUNK1) (Connecting BTS34 Services) Name Port Type ATM Cell Payload Scrambling conn_bts34_trunk1 UNI Enabled
----End

This section describes the process for configuring QoS information.
Procedure
Step 1 See A.8.9.3 Creating an ATM Policy and create ATM policies. The values for the related parameters of NE34 and NE31 are provided as follows,
Parameter
NE34 and NE31 CBR Service rt-VBR Service 6 4e1_rtvbr RT-VBR ClpTransparentScr 2252 2048 1000 10240 nrt-VBR Service 7 4e1_nrtvbr NRT-VBR NoClpScr 9295 8799 1000 UBR Service 8 4e1_ubr UBR NoClpNoScr 9295 -
Policy ID Policy Name Service Type Traffic Type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame UPC/NPC
5 4e1_cbr CBR ClpTransparent NoScr 500 102400
Disabled Disabled
Disabled Disabled
Disabled Disabled
Disabled Disabled
----End

Procedure
Step 1 See A.8.8.1 Creating ATM Services and create ATM services. l Parameters of NE34: The values for the related parameters that need to be set in the main interface are as follows.
Issue 03 (2011-04-10)
10-109
Pa ra m ete r Se rvi ce Na me Se rvi ce ID Di rec tio n Co nn ect ion Ty pe Pr ote cti on Ty pe
NE34 CBR Services from BTS34 bts34_cbrservice_ 1stpw rt-VBR Services from BTS34 bts34_rtvbrservice _1stpw nrt-VBR Services from BTS34 bts34_nrtvbrservi ce_1stpw UBR Services from BTS34 bts34_ubrservice_ 1stpw
103
105
107
109
UNIs-NNI
UNIs-NNI
UNIs-NNI
UNIs-NNI
PVC
PVC
PVC
PVC
No Protection
No Protection
No Protection
No Protection
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows. Parameter NE34 CBR Services from BTS34 Connection Name Source Port Source Bind Path bts34_cbr_atm 2-ML1-1 (TRUNK1) 2-ML1-(1-4) rt-VBR Services from BTS34 bts34_rtvbr_at m 2-ML1-1 (TRUNK1) 2-ML1-(1-4) nrt-VBR Services from BTS34 bts34_nrtvbr_a tm 2-ML1-1 (TRUNK1) 2-ML1-(1-4) UBR Services from BTS34 bts34_ubr_atm 2-ML1-1 (TRUNK1) 2-ML1-(1-4)
10-110
Issue 03 (2011-04-10)
Parameter
NE34 CBR Services from BTS34 rt-VBR Services from BTS34 34 34 105 34 34 6 6 nrt-VBR Services from BTS34 34 35 107 34 35 7 7 UBR Services from BTS34 34 36 109 34 36 8 8
Source VPI (eg.35,36-39) Source VCI (eg.35,36-39) PW ID Sink VPI(eg. 35,36-39) Sink VCI(eg. 35,36-39) Uplink Policy Down link Policy
34 33 103 34 33 5 5
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parameter NE34 CBR Services from BTS34 PW ID PW Signaling Type PW Type 103 Static ATM one to one VCC cell transport 103 rt-VBR Services from BTS34 105 Static ATM one to one VCC cell transport 105 nrt-VBR Services from BTS34 107 Static ATM one to one VCC cell transport 107 UBR Services from BTS34 109 Static ATM one to one VCC cell transport 109
PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel
103
105
107
109
1515
1515
1515
1515
Issue 03 (2011-04-10)
10-111
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE34 CBR Services from BTS34 Control Word Control Channel Type VCCV Verification Mode Must use CW Ping rt-VBR Services from BTS34 Must use CW Ping nrt-VBR Services from BTS34 Must use CW Ping UBR Services from BTS34 Must use CW Ping
The values for the relevant parameters that need to be set in the CoS Mapping tab page are provided as follows. Parameter NE34 CBR Services from BTS34 PW ID CoS Mapping 103 DefaultAtmCo sMap rt-VBR Services from BTS34 105 DefaultAtmCo sMap nrt-VBR Services from BTS34 107 DefaultAtmCo sMap UBR Services from BTS34 109 DefaultAtmCo sMap
l Parameters of NE31: The values for the related parameters that need to be set in the main interface are as follows. Parameter NE31 CBR Services from BTS34 Service Name Service ID Direction Connection Type Protection Type bts34_cbrservi ce_2ndpw 104 UNIs-NNI PVC No Protection rt-VBR Services from BTS34 bts34_rtvbrser vice_2ndpw 106 UNIs-NNI PVC No Protection nrt-VBR Services from BTS34 bts34_nrtvbrse rvice_2ndpw 108 UNIs-NNI PVC No Protection UBR Services from BTS34 bts34_ubrservi ce_2ndpw 110 UNIs-NNI PVC No Protection
10-112
Issue 03 (2011-04-10)
The values for the related parameters that need to be set in the Configure Connection tab page are provided as follows. Parameter NE31 CBR Services from BTS34 Connection Name Source Port Source Bind Path Source VPI (eg.35,36-39) Source VCI (eg.35,36-39) PW ID Sink VPI(eg. 35,36-39) Sink VCI(eg. 35,36-39) Uplink Policy Down link Policy bts34_cbr_atm 2-ML1-1 (TRUNK1) 2-ML1-(6-13) 34 33 104 34 33 5 5 rt-VBR Services from BTS34 bts34_rtvbr_at m 2-ML1-1 (TRUNK1) 2-ML1-(6-13) 34 34 106 34 34 6 6 nrt-VBR Services from BTS34 bts34_nrtvbr_a tm 2-ML1-1 (TRUNK1) 2-ML1-(6-13) 34 35 108 34 35 7 7 UBR Services from BTS34 bts34_ubr_atm 2-ML1-1 (TRUNK1) 2-ML1-(6-13) 34 36 110 34 36 8 8
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parameter NE31 CBR Services from BTS34 PW ID PW Signaling Type PW Type 104 Static ATM one to one VCC cell transport rt-VBR Services from BTS34 106 Static ATM one to one VCC cell transport nrt-VBR Services from BTS34 108 Static ATM one to one VCC cell transport UBR Services from BTS34 110 Static ATM one to one VCC cell transport
Issue 03 (2011-04-10)
10-113
Parameter
NE31 CBR Services from BTS34 rt-VBR Services from BTS34 106 nrt-VBR Services from BTS34 108 UBR Services from BTS34 110
PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel
104
104
106
108
110
1501
1501
1501
1501
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE31 CBR Services from BTS34 Control Word Control Channel Type VCCV Verification Mode Must use CW Ping rt-VBR Services from BTS34 Must use CW Ping nrt-VBR Services from BTS34 Must use CW Ping UBR Services from BTS34 Must use CW Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are provided as follows. Parameter NE31 CBR Services from BTS34 PW ID CoS Mapping 104 DefaultAtmCo sMap rt-VBR Services from BTS34 106 DefaultAtmCo sMap nrt-VBR Services from BTS34 108 DefaultAtmCo sMap UBR Services from BTS34 110 DefaultAtmCo sMap
Step 2 See A.8.4.2 Creating an MS-PW and create an MS-PW on NE32. l MS-PW parameters for CBR services: The values for the required parameters that are set in the main interface are as follows.
Parameter
NE32 CBR Services from BTS34
ID Name Service Type Connection Type
902 bts34_cbrservice_mspw ATM Service PVC
The values for the related parameters that need to be set in the PW Basic Attributes tab page are provided as follows. Parameter NE32 CBR Services from BTS34 (Forward PW) PW ID PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel 103 Static ATM one to one VCC cell transport 103 103 Manually MPLS 1515 CBR Services from BTS34 (Backward PW) 104 Static ATM one to one VCC cell transport 104 104 Manually MPLS 1501
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE32 CBR Services from BTS34 (Forward PW) Control Word Control Channel Type VCCV Verification Mode Must use CW Ping CBR Services from BTS34 (Backward PW) Must use CW Ping
Issue 03 (2011-04-10)
10-115
l MS-PW parameters for rt-VBR services: The values for the required parameters that are set in the main interface are as follows. Parameter NE32 rt-VBR Services from BTS34 ID Name Service Type Connection Type 903 bts34_rtvbrservice_mspw ATM Service PVC
The values for the related parameters that need to be set in the PW Basic Attributes tab page are provided as follows. Parameter NE32 rt-VBR Services from BTS34 (Forward PW) PW ID PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel 105 Static ATM one to one VCC cell transport 105 105 Manually MPLS 1515 rt-VBR Services from BTS34 (Backward PW) 106 Static ATM one to one VCC cell transport 106 106 Manually MPLS 1501
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE32 rt-VBR Services from BTS34 (Forward PW) Control Word Control Channel Type Must use CW rt-VBR Services from BTS34 (Backward PW) Must use CW
10-116
Issue 03 (2011-04-10)
Parameter
NE32 rt-VBR Services from BTS34 (Forward PW) rt-VBR Services from BTS34 (Backward PW) Ping
Ping
l MS-PW parameters for nrt-VBR services: The values for the required parameters that are set in the main interface are as follows. Parameter NE32 nrt-VBR Services from BTS34 ID Name Service Type Connection Type 904 bts34_nrtvbrservice_mspw ATM Service PVC
The values for the related parameters that need to be set in the PW Basic Attributes tab page are provided as follows. Parameter NE32 nrt-VBR Services from BTS34 (Forward PW) PW ID PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel 107 Static ATM one to one VCC cell transport 107 107 Manually MPLS 1515 nrt-VBR Services from BTS34 (Backward PW) 108 Static ATM one to one VCC cell transport 108 108 Manually MPLS 1501
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows.
Issue 03 (2011-04-10)
10-117
Parameter
NE32 nrt-VBR Services from BTS34 (Forward PW) nrt-VBR Services from BTS34 (Backward PW) Must use CW Ping
Control Word Control Channel Type VCCV Verification Mode
Must use CW Ping
l MS-PW parameters for UBR services: The values for the required parameters that are set in the main interface are as follows. Parameter NE32 UBR Services from BTS34 ID Name Service Type Connection Type 905 bts34_ubrservice_mspw ATM Service PVC
The values for the related parameters that need to be set in the PW Basic Attributes tab page are provided as follows. Parameter NE32 UBR Services from BTS34 (Forward PW) PW ID PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel 109 Static ATM one to one VCC cell transport 109 109 Manually MPLS 1515 UBR Services from BTS34 (Backward PW) 110 Static ATM one to one VCC cell transport 110 110 Manually MPLS 1501
10-118
Issue 03 (2011-04-10)
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parameter NE32 UBR Services from BTS34 (Forward PW) Control Word Control Channel Type VCCV Verification Mode Must use CW Ping UBR Services from BTS34 (Backward PW) Must use CW Ping
----End

Procedure
Step 1 See A.12.4 Testing ATM Services and verify ATM service configurations. The verification result should be "success". ----End
10.9 Configuration Example (Transparently Transmitted ATM Services)

This section uses a transparently transmitted ATM service on a PSN as an example to describe how to configure ATM services according to service planning information. 10.9.1 Networking Diagram The section describes the networking information about the NEs. 10.9.2 ServicePlanning You need to plan the corresponding parameter information before service configuration. 10.9.3 Per-NE Configuration Process This section describes the process for configuring transparently transmitted ATM services on a per-NE basis.

The section describes the networking information about the NEs. Compared with service requirements in 10.6 Configuration Example (Common ATM Services), this configuration example has the following different service requirements:
Issue 03 (2011-04-10)
10-119
Services from BTS13 and BTS14 are directly transmitted to NE11. The RNC uses different E1 ports to receive services from different BTSs. For specific ATM service port information, see Table 10-60. A bidirectional tunnel (ID: 1503), which has a protection tunnel, is available between NE11 and NE31. This tunnel and its corresponding information have been configured in 9.3 Configuration Example (MPLS Tunnels with MPLS APS Protection). The NEs need not perform traffic management for ATM services.

GE GE
NE32 NE11
E1 GE E1
NE31 NE21
GE
E1 RNC
R99 BTS13
R99 BTS14
Table 10-60 Information about service ports NE NE11 Service Port 4-ML1-2 4-ML1-3 to 4-ML1-6 NE31 2-ML1-6 Description Configure this port to receive BTS13 services. Configure these ports to receive BTS14 services. Configure this port to transmit BTS13 services to the RNC. Configure these ports to transmit BTS14 services to the RNC.
2-ML1-7 to 2-ML1-10
You need to plan the corresponding parameter information before service configuration. 10.9.2.1 Service Planning (UNI Ports)
This section provides the information about all the parameters required for configuring UNI ports. 10.9.2.2 Service Planning (ATM/IMA Information) The service planning information contains the information about all the parameters required for configuring ATM/IMA information. 10.9.2.3 Service Planning (QoS) The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies. 10.9.2.4 Service Planning (Service Information) The service planning information contains the information about all the parameters required for configuring ATM services.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-61 and Table 10-62 provide planning information about UNI ports. Table 10-61 Information about UNI ports (NE11) Parameter Port name Frame format Frame mode 4-ML1-2 conn_bts13_atm1 CRC-4 multiframe PCM30 4-ML1-3 to 4-ML1-6 conn_bts14_ima1 to conn_bts14_ima4 CRC-4 multiframe PCM30
Table 10-62 Information about UNI ports (NE31) Parameter Port name Frame format Frame mode 2-ML1-6 conn_rnc_atm1 CRC-4 multiframe PCM30 2-ML1-7 to 2-ML1-10 conn_rnc_ima1 to conn_rnc_ima4 CRC-4 multiframe PCM30
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire network in a unified manner. l The E1 frame format and frame mode must be the same as those of service access equipment. As specified in ITU-T G.804, ATM service ports use the default CRC-4 multiframe format and the PCM30 frame mode.
Issue 03 (2011-04-10)
10-121

The service planning information contains the information about all the parameters required for configuring ATM/IMA information. Table 10-63 and Table 10-64 provide ATM/IMA information. Table 10-63 ATM/IMA information (NE11) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Minimum number of activated links Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling 4-ML1-1 (TRUNK1) 4-ML1-2 Disabled 4-ML1-2 (TRUNK2) 4-ML1-3 to 4-ML1-6 Enabled 1.1 128 Symmetric mode and symmetric operation 1
conn_bts13_trunk1 UNI Enabled
25 ITC conn_bts14_trunk2 UNI Enabled
Table 10-64 ATM/IMA information (NE31) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length
10-122
2-ML1-1 (TRUNK1) 2-ML1-6 Disabled -
2-ML1-2 (TRUNK2) 2-ML1-7 to 2-ML1-10 Enabled 1.1 128
Issue 03 (2011-04-10)
Parameter IMA symmetric mode Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling
2-ML1-1 (TRUNK1) conn_rnc_trunk1 UNI Enabled
2-ML1-2 (TRUNK2) Symmetric mode and symmetric operation 25 ITC conn_rnc_trunk2 UNI Enabled
NOTE
l If carried over a single E1, ATM services from a BTS are transmitted and received through UNI ports. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from a BTS are transmitted and received through IMA trunks. l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected equipment. Normally, the BTS/RNC configurations are as follows: l IMA protocol version: 1.1 l IMA frame length: 128 l IMA symmetric mode: symmetrical mode and symmetrical operation l The differentiated delay tolerance: 25 l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the NE at the opposite end of the IMA link.

The service planning information contains the information about all the parameters required for configuring ATM service classes and ATM policies. In this example, the PHB service class is set to EF for transparently transmitted ATM services to ensure reliable transmission of medium- and high-priority services. The PHB service class for transparently transmitted ATM services, however, is defined as BE in the default ATM CoS mapping table. Therefore, a new ATM CoS mapping table needs to be created. Table 10-65 Information about the ATM CoS mapping table Parameter Value NE11 Mapping table ID Mapping table name
Issue 03 (2011-04-10)
NE31
2 Port-transparent
10-123
Parameter
Value NE11 NE31
PHB service class for transparently transmitted ATM services
EF

The service planning information contains the information about all the parameters required for configuring ATM services. Table 10-66 provides the service planning information. Table 10-66 Service information (ATM services from BTS13) Parameter ATM Services from BTS13 Source NE (NE11) Service name Service ID Service type Connection type Protection type Service board Service port PW information PW ID PW ingress/ egress label PW type Tunnel Control Word Control Channel Type VCCV Verification Mode 101 101/101 ATM transparent cell transport 1503 No Use Alert Label Ping bts13_atmservice 101 UNIs-NNI Port Transparent No protection 4-ML1 TRUNK1 2-ML1 TRUNK1 Sink NE (NE31)
CoS mapping information

Parameter
ATM Services from BTS13 Source NE (NE11) Sink NE (NE31)
CoS mapping
2 (Port Transparent)
Table 10-67 Service information (ATM services from BTS14) Parameter ATM Services from BTS14 Source NE (NE11) Service name Service ID Service type Connection type Protection type Service board Service port PW information PW ID PW ingress/ egress label PW type Tunnel Control Word Control Channel Type VCCV Verification Mode 112 112/112 ATM transparent cell transport 1503 No Use Alert Label Ping bts14_imaservice 112 UNIs-NNI Port Transparent No protection 4-ML1 TRUNK2 2-ML1 TRUNK2 Sink NE (NE31)
CoS mapping information CoS mapping 2 (Port Transparent)

This section describes the process for configuring transparently transmitted ATM services on a per-NE basis.
Issue 03 (2011-04-10)
10-125
10.9.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port information. 10.9.3.2 Configuration Process (IMA Information) This section describes the process for configuring IMA information. 10.9.3.3 Configuration Process (QoS) This section describes the process for configuring QoS information for ATM services. 10.9.3.4 Configuration Process (Service Information) This section describes the process for configuring service information. 10.9.3.5 Configuration Process (Verifying ATM Service Configurations) This section describes the process for verifying ATM service configurations.

Procedure
Step 1 See A.5.4.1 Setting Basic Attributes of Smart E1 Ports and set general attributes of Smart E1 ports. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-2 Name Port Mode conn_bts13_atm1 Layer 2 4-ML1-3 to 4-ML1-6 conn_bts14_ima1 to conn_bts14_ima4 Layer 2
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 Name Port Mode conn_rnc_atm1 Layer 2 2-ML1-7 to 2-ML1-10 conn_rnc_ima1 to conn_rnc_ima4 Layer 2
Step 2 See A.5.4.2 Setting Advanced Attributes of Smart E1 Ports and set advanced attributes of Smart E1 ports. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-2 Frame Format
10-126
4-ML1-3 to 4-ML1-6 CRC-4 Multiframe

Issue 03 (2011-04-10)
CRC-4 Multiframe
Parameter
NE11 4-ML1-2 4-ML1-3 to 4-ML1-6 30
Frame Mode
30
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-6 Frame Format Frame Mode CRC-4 Multiframe 30 2-ML1-7 to 2-ML1-10 CRC-4 Multiframe 30
----End

Procedure
Step 1 See A.8.7.1 Binding ATM TRUNKs and bind the ATM trunk. l The values for the related parameters for NE11 are provided as follows. Parameter NE11 Trunk1 (Connecting BTS13 Services) Available Boards Configurable Ports Level Available Resources 4-ML1 4-ML1-1 (Trunk1) E1 4-ML1-2 (conn_bts13_atm_1) Trunk2 (Connecting BTS14 Services) 4-ML1 4-ML1-2 (Trunk2) E1 4-ML1-3 (conn_bts14_ima1) to 4ML1-6 (conn_bts14_ima4)
l The values for the related parameters for NE31 are provided as follows. Parameter NE31 Trunk1 (Transmitting BTS13 Services to the RNC) Available Boards Configurable Ports
Issue 03 (2011-04-10)
Trunk2 (Transmitting BTS14 Services to the RNC) 2-ML1 2-ML1-2 (Trunk2)

10-127
2-ML1 2-ML1-1 (Trunk1)
Parameter
NE31 Trunk1 (Transmitting BTS13 Services to the RNC) Trunk2 (Transmitting BTS14 Services to the RNC) E1 2-ML1-7 (conn_rnc_ima1) to 2-ML1-10 (conn_rnc_ima4)
Level Available Resources
E1 2-ML1-6 (conn_rnc_atm1)
Step 2 See A.8.7.2 Configuring an IMA group and create an IMA group. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-1 (Trunk1) (Connecting BTS13 Services) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Disabled 4-ML1-2 (Trunk2) (Connecting BTS14 Services) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operational 25
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-1 (Trunk1) (Transmitting BTS13 Services to the RNC) IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Disabled 2-ML1-2 (Trunk2) (Transmitting BTS14 Services to the RNC) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operational
10-128
Issue 03 (2011-04-10)
Parameter
NE31 2-ML1-1 (Trunk1) (Transmitting BTS13 Services to the RNC) 2-ML1-2 (Trunk2) (Transmitting BTS14 Services to the RNC) 25
Maximum Delay Between Links (ms)
Step 3 See A.8.7.3 Setting ATM Port Parameters and set ATM port parameters. l The values for the related parameters of NE11 are provided as follows. Parameter NE11 4-ML1-1 (Trunk1) (Connecting BTS13 Services) Name Port Type ATM Cell Payload Scrambling conn_bts13_trunk1 UNI Enabled 4-ML1-2 (Trunk2) (Connecting BTS14 Services) conn_bts14_trunk2 UNI Enabled
l The values for the related parameters of NE31 are provided as follows. Parameter NE31 2-ML1-1 (Trunk1) (Transmitting BTS13 Services to the RNC) Name Port Type ATM Cell Payload Scrambling conn_rnc_trunk1 UNI Enabled 2-ML1-2 (Trunk2) (Transmitting BTS14 Services to the RNC) conn_rnc_trunk2 UNI Enabled
----End

This section describes the process for configuring QoS information for ATM services.
Procedure
Step 1 See A.8.9.1 Creating an ATM-DiffServ Domain and create the ATM DS domain. Parameters for NE11 and NE31:
Parameter
Value NE11 and NE31
Mapping Relation ID Mapping Relation Name PORT-TRANS
2 Port-transparent EF
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is recommended that a transparently transmitted ATM service takes its default PHB service class.
----End

Procedure
Step 1 See A.8.8.1 Creating ATM Services and create ATM services. l Parameters of NE11: The values for the related parameters that need to be set in the main interface are as follows. Parame ter Service Name Service ID Directio n Connec tion Type Protecti on Type NE11 ATM Services from BTS13 bts13_atmservice 101 UNIs-NNI Port Transparent ATM Services from BTS14 bts14_imaservice 112 UNIs-NNI Port Transparent
No Protection
No Protection
10-130
Issue 03 (2011-04-10)
Parameter
NE11 ATM Services from BTS13 ATM Services from BTS14 4-ML1 2 (TRUNK2)
Source Board Source Port
4-ML1 1 (TRUNK1)
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parame ter PW ID PW Signalin g Type PW Type PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel NE11 ATM Services from BTS13 101 Static ATM Services from BTS14 112 Static
ATM transparent cell transport 101
101
112
1503
1503
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parame ter Control Word NE11 ATM Services from BTS13 NO use ATM Services from BTS14 NO use
Issue 03 (2011-04-10)
10-131
Parame ter Control Channe l Type VCCV Verifica tion Mode
NE11 ATM Services from BTS13 Alert Label ATM Services from BTS14 Alert Label
Ping
Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are provided as follows. Parame ter PW ID CoS Mappin g NE11 ATM Services from BTS13 101 2 (Port-transparent) ATM Services from BTS14 112 2 (Port-transparent)
l Parameters of NE31: The values for the related parameters that need to be set in the main interface are as follows. Parame ter Service Name Service ID Directio n Connec tion Type Protecti on Type NE31 ATM Services from BTS13 bts13_atmservice 101 UNIs-NNI Port Transparent ATM Services from BTS14 bts14_imaservice 112 UNIs-NNI Port Transparent
No protection
No protection
Parameter
NE31 ATM Services from BTS13 ATM Services from BTS14 2-ML1 2 (TRUNK2)
Source Board Source Port
2-ML1 1 (TRUNK1)
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parame ter PW ID PW Signali ng Type PW Type PW Ingress Label / Source Port PW Egress Label / Sink Port Ingress Tunnel NE31 ATM Services from BTS13 101 Static ATM Services from BTS14 112 Static
101
112
1503
1503
In the Configure PW dialog box, the values for the related parameters that need to be set in the Advanced Attributes tab page are provided as follows. Parame ter Control Word NE31 ATM Services from BTS13 NO use ATM Services from BTS14 NO use
Issue 03 (2011-04-10)
10-133
Parame ter Control Channe l Type VCCV Verifica tion Mode
NE31 ATM Services from BTS13 Alert Label ATM Services from BTS14 Alert Label
Ping
Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are provided as follows. Parame ter PW ID CoS Mappin g NE31 ATM Services from BTS13 101 2 (Port-transparent) ATM Services from BTS14 112 2 (Port-transparent)
----End

Procedure
Step 1 Transparently transmitted ATM services do not support the ATM OAM function. Therefore, it is recommended you use the ATM OAM function on the BTS and the RNC to test ATM service connectivity. ----End
10.10 Configuration Example (E-Line Services Carried on PWs, a Simple Example)

This section considers E-Line services carried on PWs as an example to describe how to configure E-Line services. 10.10.1 Networking Diagram The section describes the networking information about the NEs. 10.10.2 Service Planning
You need to plan the corresponding parameter information before service configuration. 10.10.3 Per-NE Configuration Process This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode.

The section describes the networking information about the NEs. After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the RNC by means of PWs. The service requirements are as follows: l Ethernet services (VLAN ID: 310) at BTS31, which are received by NE32, need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1501), which has a protection tunnel, is available between NE32 and NE31. Ethernet services carried on PWs connected to BTS31 are transparently transmitted over the tunnel. Ethernet services at all preceding BTSs have already been configured with corresponding VLAN priorities based on service types (real-time voice services, HSDPA real-time services, R99 non-real-time services, and HSDPA data services), and the transmission network is required to provide end-to-end QoS control based on the VLAN priorities specified at the BTSs. GE ports on NE31, which are connected to the RNC, need to be protected in link aggregation group (LAG) mode.
Figure 10-22 Networking diagram (E-Line services carried on PWs, a simple example)
BTS33
FE
NE34 NE33 BTS31
R4
FE
R4 Working Tunnel (ID=1501)
GE
NE32
GE
Hybrid radio chain network
NE11
GE
NE31 NE21
GE
GE
RNC
Table 10-68 provides the information about UNI ports of E-Line services carried on PWs.
Table 10-68 Information about service ports NE NE32 NE31 Service Port 2-EM6F-3 4-EM6T-1 4-EM6T-2 Description Receives the Ethernet services from BTS31. Ports 4-EM6T-1 and 4EM6T-2 form a LAG.

You need to plan the corresponding parameter information before service configuration. 10.10.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.10.2.2 Service Planning (Ethernet Protection) This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. 10.10.2.3 Service Planning (Service Information) This section provides the information about all the parameters required for creating E-Line services carried on PWs. 10.10.2.4 Service Planning (QoS) The section provides the information about all the parameters required for configuring QoS.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-69 provides the information about the Ethernet ports on NE32. Table 10-69 Information about Ethernet ports (NE32) Parameter NE32 2-EM6F-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Flow Control Enabled Layer 2 802.1Q Auto-Negotiation 1536 Disabled
10-136
Issue 03 (2011-04-10)
Table 10-70 provides the information about the Ethernet ports on NE31. Table 10-70 Information about Ethernet ports (NE31) Parameter NE31 4-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Flow Control Enabled Layer 2 802.1Q Auto-Negotiation 1536 Disabled 4-EM6T-2 Enabled Layer 2 802.1Q Auto-Negotiation 1536 Disabled
NOTE
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work in the corresponding modes. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient QoS capabilities. The planning information of flow control must be the same for the equipment at both ends. l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is enabled.

This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. To improve the reliability of service transmission, NE31 and the RNC are interconnected through the LAG formed by two GE links.Table 10-71 provides the planning information. Table 10-71 Information about LAGs Parameter LAG type Revertive mode Load sharing System priority Main port
Issue 03 (2011-04-10)
NE31 Static Non-Revertive Non-Sharing 32768 4-EM6T-1

Parameter Slave port
NE31 4-EM6T-2
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore, you need not configure the LAG to the load-sharing mode for increase of the bandwidth utilization.

This section provides the information about all the parameters required for creating E-Line services carried on PWs. Table 10-72 provides the planning information about E-Line services carried on PWs. Table 10-72 Planning information about E-Line services carried on PWs Parameter E-Line Services Carried on PWs Connected to BTS 31 Source NE (NE32) Service ID Service Name Direction BPDU Source Port Source VLANs Bearer Type Protection Type 303 BTS31-RNC_E-Line UNI-NNI Not Transparently Transmitted 2-EM6F-3 310 PW No Protection Sink NE (NE31) 303 BTS31-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 310 PW No Protection
Table 10-73 provides the planning information about PWs. Table 10-73 Planning information about PWs Parameter E-Line Services Carried on PWs Connected to BTS31 Source NE (NE32) PW ID PW Signaling Type PW Type
10-138
Sink NE (NE31) 303 Static Ethernet

Issue 03 (2011-04-10)
303 Static Ethernet

Parameter
E-Line Services Carried on PWs Connected to BTS31 Source NE (NE32) Sink NE (NE31) Bidirectional MPLS 40 40 MPLS 1501 46.1.4.2 No Use Alert Label Ping
Direction PW Encapsulation Type PW Ingress Labs/Source Port PW Egress Labs/Sink Port Tunnel selection mode Tunnel Opposite LSR ID Control Word Control Channel Type VCCV Verification Mode
Bidirectional MPLS 40 40 MPLS 1501 46.1.4.1 No Use Alert Label Ping
NOTE
In this example, the tunnel has already been planned when you plan MPLS tunnels. Therefore, you need to select only the tunnel that carries the PWs.

The section provides the information about all the parameters required for configuring QoS.
QoS (DiffServ)
Diffserv is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding Diffserv domain according to the allocated VLAN priority, DSCP value, or MPLS EXP value. Each Ethernet port involved in the service must use the same Diffserv configuration. In this example, the BTS services are allocated corresponding C-VLAN priorities by service type, and PW-carried UNI-NNI E-Line services are configured on the transmission network. DiffServ planning has been completed for the transmission network during MPLS tunnel planning. In this example, you only need to set the trusted packet types of the UNI and NNI ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of the transmission network, therefore achieving end-to-end QoS control on the transmission network.


QoS (Port Shaping)

QoS (PW Bandwidth Control)

In this example, PW bandwidth does not need to be controlled.

This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode. 10.10.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port attributes. 10.10.3.2 Configuration Process (Ethernet Protection) This section describes how to create a LAG of the GE port of NE31 connected to the RNC. 10.10.3.3 Configuration Process (Service Information) This section describes the process for configuring E-Line services carried on PWs. 10.10.3.4 Configuration Process (QoS) This section describes the process for configuring QoS of E-Line services carried on PWs.
10.10.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

This section describes the process for configuring UNI port attributes.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes of the UNI ports. l The values for the general attribute parameters of the UNI port of NE32 are provided as follows. Parameter NE32 2-EM6F-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536
l The values for the general attribute parameters of the UNI port of NE31 are provided as follows. Parameter NE31 4-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536 4-EM6T-2 Enabled Layer 2 802.1Q Auto-Negotiation 1536
Step 2 See A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of the UNI ports. l The values for the Layer 2 attribute parameters of the UNI port of NE32 are provided as follows. Parameter NE32 2-EM6F-3 TAG
Issue 03 (2011-04-10)
Tag Aware
l The values for the Layer 2 attribute parameters of the UNI port of NE31 are provided as follows. Parameter NE31 4-EM6T-1 TAG Tag Aware 4-EM6T-2 Tag Aware
----End

This section describes how to create a LAG of the GE port of NE31 connected to the RNC.
Procedure
Step 1 See A.6.2.1 Creating a LAG and create a LAG. The values for the relevant parameters that need to be set in the main interface are provided as follows. Parameter LAG No. LAG Name LAG Type Revertive Mode Load Sharing System Priority Value Select Automatically Assign. ToRNC Static Non-Revertive Non-Sharing 32768
The values for the relevant parameters that need to be set in the Port Setting tab page are as follows. Parameter Main Board Main Port Selected Standby Ports Value 4-EM6T 1 2
----End
10-142
Issue 03 (2011-04-10)

This section describes the process for configuring E-Line services carried on PWs.
Procedure
Step 1 See A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the ELine services. l Parameters of NE32 The values for the relevant parameters that need to be set in the main interface are as follows. Parameter Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type Protection Type NE32 303 BTS31-RNC_E-Line UNI-NNI Not Transparently Transmitted 2-EM6F-3 310 PW No Protection
The values for the relevant parameters that need to be set in the PW tab page are provided as follows. Parameter PW ID PW Signaling Type PW Type PW Direction PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel Peer LSR ID NE32 303 Static Ethernet Bidirectional MPLS 40 40 MPLS 1501 46.1.4.1
Issue 03 (2011-04-10)
10-143
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode l Parameters of NE31 The values for the relevant parameters that need to be set in the main interface are as follows. Parameter Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type Protection Type NE31 303 BTS31-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 310 PW No Protection NE32 No Use Alert Label Ping
In the Configure PW dialog box, the values for the relevant parameters that need to be set in the General Attributes tab page are provided as follows. Parameter PW ID PW Signaling Type PW Type PW Direction PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel Peer LSR ID NE31 303 Static Ethernet Bidirectional MPLS 40 40 MPLS 1501 46.1.4.2
10-144
Issue 03 (2011-04-10)
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode NE31 No Use Alert Label Ping
----End

This section describes the process for configuring QoS of E-Line services carried on PWs.
Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and set the trusted packet types of the UNI and NNI ports on NE32 and NE31 that transmit the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively. 1. Select the default DS domain for the OptiX RTN equipment.
NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN equipment. Therefore, the default DS domain settings are used.
Parameter Mapping Relation ID Mapping Relation Name 2.
Value 1 DefaultMap
Set the trusted packet type of the UNI ports on NE32 and NE31 to C-VLAN. Parameter Value NE32 Port 2-EM6F-3 NE31 4-EM6T-1 4-EM6T-2 Packet Type CVLAN CVLAN
NOTE
For an NNI port that transmits a PW-carried E-Line service, set Packet Type trusted by the NNI port to MPLS EXP.
Step 2 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the related parameters of UNI ports of NE32 and NE31 are provided as follows.
Parameter Policy ID Policy Name Grooming Police After Reloading
Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Policy Weight(%)
5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Disabled (for all PHB service levels)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the related parameters of UNI ports of NE32 and NE31 are provided as follows. Parameter Value NE32 Port_Comm (Policy ID=1) Port 2-EM6F-3 NE31 Port_Comm (Policy ID=1) 4-EM6T-1 4-EM6T-2
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs for NE31 and NE32. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Domain Level
10-146
NE32 EdgeNE 4
EdgeNE 4
Issue 03 (2011-04-10)
Step 2 See A.6.8.2 Creating an MA and create an MA for NE31 and NE32. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period EdgeNE BTS31-RNC_E-Line BTS31-RNC_E-Line 1s NE32 EdgeNE BTS31-RNC_E-Line BTS31-RNC_E-Line 1s
Step 3 See A.6.8.3 Creating an MEP Point and create MEPs for NE31 and NE32. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status EdgeNE BTS31-RNC_E-Line 4-EM6T 4-EM6T-1 310 310 Ingress Active NE32 EdgeNE BTS31-RNC_E-Line 2-EM6F 2-EM6F-3 310 320 Ingress Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and NE32. The values for the relevant parameters are provided as follows.
Issue 03 (2011-04-10)
10-147
Parameter
Value NE31 NE32 EdgeNE BTS31-RNC_E-Line 310
Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6)
EdgeNE BTS31-RNC_E-Line 320
Step 5 On NE31, perform LB tests to verify the Ethernet service configurations. Perform the LB test by considering the MEP whose MP ID is 310 as the source MEP and the MEP whose MP ID is 320 as the sink MEP to check the connectivity of the E-Line services carried on the PWs between NE31 and NE32. The LB test result shows that no packet loss occurs. ----End
10.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet Services Aggregated from the Hybrid Microwave Network)
This section considers E-Line services carried on PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network as an example to describe how to configure ELine services carried on PWs. 10.11.1 Networking Diagram The section describes the networking information about the NEs. 10.11.2 Service Planning You need to plan the corresponding parameter information before service configuration. 10.11.3 Per-NE Configuration Process This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode.

The section describes the networking information about the NEs. After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the RNC by means of PWs. The service requirements are as follows: l On the Hybrid microwave chain network connected to NE11, Ethernet services at BTS11, BTS12, and BTS13 respectively carry VLAN ID 100, VLAN ID 110, and VLAN ID 120, and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1503),
10-148
which has a protection tunnel, is available between NE11 and NE31. Ethernet services carried on PWs at BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel. l On the Hybrid microwave ring network connected to NE21, Ethernet services at BTS21, BTS22, and BTS23 respectively carry VLAN ID 200, VLAN ID 210, and VLAN ID 220, and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1505), which has a protection tunnel, is available between NE21 and NE31. Ethernet services carried on PWs at BTS21, BTS22, and BTS23 are transparently transmitted over the tunnel. Ethernet services at all preceding BTSs have already been configured with corresponding VLAN priorities based on service types (real-time voice services, HSDPA real-time services, R99 non-real-time services, and HSDPA data services), and the transmission network is required to provide end-to-end QoS control based on the VLAN priorities specified at the BTSs. GE ports on NE31, which are connected to the RNC, need to be protected in link aggregation group (LAG) mode.
Figure 10-23 Networking diagram (E-Line services carried on PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network)
BTS33
FE
NE34 NE33 BTS31
R4
FE
BTS11
Working Tunnel (ID=1503)

GE
R4
GE
R4 BTS12 Hybrid radio chain network
NE32
NE31
GE
NE11
GE
NE21
GE
R4
RNC Working Tunnel (ID=1505)
BTS13 BTS21 R4 R4 BTS22 BTS23 Hybrid radio ring network
R4
R4
Table 10-75 provides the information about UNI service ports of E-Line services carried on PWs.
Issue 03 (2011-04-10)
10-149
Table 10-75 Information about service ports NE NE11 Service Port 3-ISU2-1 Description Receive Ethernet services at BTS11, BTS12, and BTS13 connected to the Hybrid microwave chain network. NE21 cross-connects and loops back the 1-EM6F-3 port to the 1-EM6F-4 port by means of a network cable to convert Native E-LAN services (at BTS21, BTS22, and BTS23) received by the 1-EM6F-3 port on the Hybrid microwave ring network to E-Line services carried on PWs. Ports 4-EM6T-1 and 4EM6T-2 form a LAG.
NE21
1-EM6F-4
NE31
4-EM6T-1 4-EM6T-2

You need to plan the corresponding parameter information before service configuration. 10.11.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.11.2.2 Service Planning (Ethernet Protection) This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. 10.11.2.3 Service Planning (Service Information) This section provides the information about all the parameters required for E-Line services carried on PWs. 10.11.2.4 Service Planning (QoS) The section provides the information about all the parameters required for configuring QoS.

This section provides the information about all the parameters required for configuring UNI ports.

Table 10-76 provides the information about the Ethernet ports on NE21.
Table 10-76 Information about Ethernet ports (NE21) Parameter NE21 1-EM6F-4 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Flow Control Enabled Layer 2 802.1Q Auto-Negotiation 1536 Disabled
NOTE
l NE21 cross-connects and loops back the 1-EM6F-3 port to the 1-EM6F-4 port by means of a network cable to convert Native E-LAN services received by the 1-EM6F-3 port on the Hybrid microwave ring network to E-Line services carried on PWs. l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work in the corresponding modes. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient QoS capabilities. The planning information of flow control must be the same for the equipment at both ends. l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is enabled for Ethernet ports.
Issue 03 (2011-04-10)
10-151
Information About IF_ETH Ports

Table 10-78 provides the information about IF_ETH ports on NE11, which receive Ethernet services from BTSs on the Hybrid microwave chain network. Table 10-78 Information about IF_ETH ports Parameter NE11 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q

This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. To improve the reliability of service transmission, NE31 and the RNC are interconnected through the LAG formed by two GE links.Table 10-79 provides the planning information. Table 10-79 Information about LAGs Parameter LAG type Revertive mode Load sharing System priority Main port Slave port NE31 Static Non-Revertive Non-Sharing 32768 4-EM6T-1 4-EM6T-2
NOTE

This section provides the information about all the parameters required for E-Line services carried on PWs. Table 10-80 provides the planning information about E-Line services carried on PWs.
10-152
Issue 03 (2011-04-10)
Table 10-80 Planning information about E-Line services carried on PWs Parameter E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 Source NE (NE11) Service ID Service Name Direction BPDU 301 BTS11/12/13RNC_E-Line UNI-NNI Not Transparently Transmitted 3-ISU2-1 100,110,120 PW No Protection Sink NE (NE31) 301 BTS11/12/13RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 100,110,120 PW No Protection E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 Source NE (NE21) 302 BTS21/22/23RNC_E-Line UNI-NNI Not Transparently Transmitted 1-EM6F-4 200,210,220 PW No Protection Sink NE (NE31) 302 BTS21/22/23RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 200,210,220 PW No Protection
Source Port Source VLANs Bearer Type Protection Type
Table 10-81 provides the planning information about PWs. Table 10-81 Planning information about PWs Parameter E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 Source NE (NE11) PW ID PW Signaling Type PW Type Direction PW Encapsulation Type PW Ingress Labs/Source Port 301 Static Ethernet Bidirectional MPLS Sink NE (NE31) 301 Static Ethernet Bidirectional MPLS E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 Source NE (NE21) 302 Static Ethernet Bidirectional MPLS Sink NE (NE31) 302 Static Ethernet Bidirectional MPLS
60
60
50
50
Issue 03 (2011-04-10)
10-153
Parameter
E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 Source NE (NE11) Sink NE (NE31) 60 MPLS 1503 46.1.4.3 No Use Alert Label Ping
E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 Source NE (NE21) 50 MPLS 1505 46.1.4.1 No Use Alert Label Ping Sink NE (NE31) 50 MPLS 1505 46.1.4.4 No Use Alert Label Ping
PW Egress Labs/Sink Port Tunnel selection mode Tunnel Opposite LSR ID Control Word Control Channel Type VCCV Verification Mode
60 MPLS 1503 46.1.4.1 No Use Alert Label Ping
NOTE

QoS (DiffServ)
Diffserv is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding Diffserv domain according to the allocated VLAN priority, DSCP value, or MPLS EXP value. Each Ethernet port involved in the service must use the same Diffserv configuration. In this example, the BTS services are allocated corresponding C-VLAN priorities by service type, and PW-carried UNI-NNI E-Line services are configured on the transmission network. DiffServ planning has been completed for the transmission network during MPLS tunnel planning. In this example, you only need to set the trusted packet types of the UNI and NNI ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of the transmission network, therefore achieving end-to-end QoS control on the transmission network.

Generally, each Ethernet port involved in the service uses the same queue scheduling mode.
Table 10-82 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 10-82 Queue scheduling mode PHB Service Class CS7 CS6 EF AF4 AF3 AF2 AF1 BE Queue Scheduling Mode SP SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP

QoS (Port Shaping)



This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode. 10.11.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI ports. 10.11.3.2 Configuration Process (Ethernet Protection) This section describes how to create a LAG of the GE port of NE31 connected to the RNC. 10.11.3.3 Configuration Process (Service Information) This section describes the process for configuring E-Line services carried on PWs.
10.11.3.4 Configuration Process (QoS) This section describes the process for configuring QoS of E-Line services carried on PWs. 10.11.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

This section describes the process for configuring UNI ports.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes of the UNI ports. l The values for the general attribute parameters of the UNI port of NE21 are provided as follows. Parameter NE21 1-EM6F-4 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536
l The values for the general attribute parameters of the UNI port of NE31 are provided as follows. Parameter NE31 4-EM6T-1 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536 4-EM6T-2 Enabled Layer 2 802.1Q Auto-Negotiation 1536
Step 2 See A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of the UNI ports. l The values for the Layer 2 attribute parameters of the UNI port of NE21 are provided as follows.
10-156
Issue 03 (2011-04-10)
Parameter
NE21 1-EM6F-4
TAG
Tag Aware
Step 3 See A.5.7.1 Setting the General Attributes of the IF_ETH Port and set the general attributes of the UNI ports. The values for the general attribute parameters of the UNI port of NE11 are provided as follows. Parameter NE11 3-ISU2-1 Port Mode Encapsulation Type Layer 2 802.1Q
Step 4 See A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributes of the UNI ports. The values for the Layer 2 attribute parameters of the UNI port of NE11 are provided as follows. Parameter NE11 3-ISU2-1 Tag Tag Aware
----End

Procedure
Step 1 See A.6.2.1 Creating a LAG and create a LAG. The values for the relevant parameters that need to be set in the main interface are provided as follows.
Parameter LAG No. LAG Name LAG Type Revertive Mode Load Sharing System Priority
Value Select Automatically Assign. ToRNC Static Non-Revertive Non-Sharing 32768
----End

Procedure
Step 1 See A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the ELine services. l Parameters of NE11 The values for the relevant parameters that need to be set in the main interface are as follows. Parameter Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type
10-158
NE11 301 BTS11/12/13-RNC_E-Line UNI-NNI Not Transparently Transmitted 3-ISU2-1 100,110,120 PW

Issue 03 (2011-04-10)
Parameter Protection Type
NE11 No Protection
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode l Parameters of NE21 The values for the relevant parameters that need to be set in the main interface are as follows. Parameter Service ID Service Name Direction BPDU NE21 302 BTS21/22/23-RNC_E-Line UNI-NNI Not Transparently Transmitted NE11 No Use Alert Label Ping
Issue 03 (2011-04-10)
10-159
Parameter Source Interface Source VLAN ID Bearer Type Protection Type
NE21 1-EM6F-4 200,210,220 PW No Protection
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode l Parameters of NE31 The values for the relevant parameters that need to be set in the main interface are as follows. NE21 No Use Alert Label Ping
10-160
Issue 03 (2011-04-10)
Parameter
NE31 E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 302 BTS21/22/23-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 200,210,220 PW No Protection
Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type Protection Type
301 BTS11/12/13-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 100,110,120 PW No Protection
The values for the relevant parameters that need to be set in the PW tab page are provided as follows. Parameter NE31 E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 PW ID PW Signaling Type PW Type PW Direction PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel Peer LSR ID 301 Static Ethernet Bidirectional MPLS 60 60 MPLS 1503 46.1.4.3 E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 302 Static Ethernet Bidirectional MPLS 50 50 MPLS 1505 46.1.4.4
Issue 03 (2011-04-10)
10-161
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter NE31 E-Line Services Carried on PWs Connected to BTS11, BTS12, or BTS13 Control Word Control Channel Type VCCV Verification Mode No Use Alert Label Ping E-Line Services Carried on PWs Connected to BTS21, BTS22, or BTS23 No Use Alert Label Ping
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and set the trusted packet types of the UNI and NNI ports on NE11, NE21, and NE31 that transmit the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively. 1. Select the default DS domain for the OptiX RTN equipment.
NOTE
Value 1 DefaultMap
Set the trusted packet type of the UNI ports on NE11, NE21, and NE31 to C-VLAN. Parameter Value NE11 Port 3-ISU2-1 NE21 1-EM6F-4 NE31 4-EM6T-1 4-EM6T-2 Packet Type CVLAN CVLAN CVLAN
10-162
Issue 03 (2011-04-10)
NOTE
Step 2 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the relevant parameters of UNI ports of NE11, NE21, and NE31 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service levels)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the relevant parameters of UNI ports of NE11, NE21, and NE31 are provided as follows. Parameter Value NE11 Port_Comm (Policy ID=1) Port 3-ISU2-1 NE21 Port_Comm (Policy ID=1) 1-EM6F-4 NE31 Port_Comm (Policy ID=1) 4-EM6T-1 4-EM6T-2
----End

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs for NE11, NE21, and NE31. The values for the relevant parameters are provided as follows.
Parameter
Value NE11 NE21 EdgeNE 4 NE31 EdgeNE 4
Maintenance Domain Name Maintenance Domain Level
EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create an MA for NE11, NE21, and NE31. The values for the relevant parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period EdgeNE BTS11/12/13RNC_E-Line BTS11/12/13RNC_E-Line 1s NE21 EdgeNE BTS21/22/23RNC_E-Line BTS21/22/23RNC_E-Line 1s EdgeNE BTS11/12/13RNC_E-Line BTS11/12/13RNC_E-Line 1s NE31 EdgeNE BTS21/22/23RNC_E-Line BTS21/22/23RNC_E-Line 1s
Step 3 See A.6.8.3 Creating an MEP Point and create MEPs for NE11, NE21, and NE31. The values for the relevant parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID
10-164
NE21 EdgeNE BTS21/22/23RNC_E-Line 1-EM6F 1-EM6F-4 200 210 EdgeNE BTS11/12/13RNC_E-Line 4-EM6T 4-EM6T-1 100 311
NE31 EdgeNE BTS21/22/23RNC_E-Line 4-EM6T 4-EM6T-1 200 312

Issue 03 (2011-04-10)
EdgeNE BTS11/12/13RNC_E-Line 3-ISU2 3-ISU2-1 100 110
Parameter
Value NE11 NE21 Ingress Active Ingress Active NE31 Ingress Active
Direction CC Status
Ingress Active
NOTE
l On NE11, when performing the connectivity check on the E-Line services carried on PWs, use the BTS service (VLAN ID: 100) received by NE11 as an example. l On NE21, when performing the connectivity check on the E-Line services carried on PWs, use the BTS service (VLAN ID: 200) received by NE21 as an example.
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE11, NE21, and NE31. The values for the relevant parameters are provided as follows. Parameter Value NE11 Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g: 1,3-6) EdgeNE BTS11/12/13RNC_E-Line 311 NE21 EdgeNE BTS21/22/23RNC_E-Line 312 NE31 EdgeNE BTS11/12/13RNC_E-Line 110 EdgeNE BTS21/22/23RNC_E-Line 210
Step 5 On NE31, perform LB tests to verify the Ethernet service configurations. Perform the LB test by considering the MEP whose MP ID is 311 as the source MEP and the MEP whose MP ID is 110 as the sink MEP to check the connectivity of the E-Line services carried on the PWs between NE31 and NE11. Perform the LB test by considering the MEP whose MP ID is 310 as the source MEP and the MEP whose MP ID is 210 as the sink MEP to check the connectivity of the E-Line services carried on the PWs between NE31 and NE21. The LB test results show that no packet loss occurs. ----End
Issue 03 (2011-04-10)
10-165
10.12 Configuration Example (E-Line Services Carried on MS-PWs)

This section considers E-Line services carried on MS-PWs as an example to describe how to configure E-Line services carried on PWs. 10.12.1 Networking Diagram The section describes the networking information about the NEs. 10.12.2 Service Planning You need to plan the corresponding parameter information before service configuration. 10.12.3 Per-NE Configuration Process This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode.

The section describes the networking information about the NEs. After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the RNC by means of PWs. The service requirements are as follows: l l Ethernet services (VLAN ID: 330) at BTS33, which are received by NE34, need to be transmitted to the RNC. The information about the tunnel between NE34 and NE31 is as follows: A bidirectional tunnel (ID: 1515), which does not have a protection tunnel, is available between NE34 and NE32. A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between NE32 and NE31. Ethernet services at BTSs are carried by PWs on the two tunnels, and exchange PW labels and tunnel labels on NE32. l Ethernet services at all preceding BTSs have already been configured with corresponding VLAN priorities based on service types (real-time voice services, HSDPA real-time services, R99 non-real-time services, and HSDPA data services), and the transmission network is required to provide end-to-end QoS control based on the VLAN priorities specified at the BTSs. GE ports on NE31, which are connected to the RNC, need to be protected in link aggregation group (LAG) mode.
10-166
Issue 03 (2011-04-10)
Figure 10-24 Networking diagram (E-Line services carried by PWs and transmitting the Ethernet services aggregated from the Hybrid microwave network)
BTS33
FE
NE34 NE33 BTS31 Tunnel (ID=1515)

FE GE
R4
R4 Working Tunnel (ID=1501)
NE32 Hybrid radio chain network NE11

GE
GE
NE31 NE21
GE
GE
RNC
Table 10-83 provides the information about UNI ports of E-Line services carried by PWs. Table 10-83 Information about service ports NE NE34 NE31 Service Port 1-EM6T-3 4-EM6T-1 4-EM6T-2 Description Receives the Ethernet services from BTS33. Ports 4-EM6T-1 and 4EM6T-2 form a LAG.

You need to plan the corresponding parameter information before service configuration. 10.12.2.1 Service Planning (UNI Ports) This section provides the information about all the parameters required for configuring UNI ports. 10.12.2.2 Service Planning (Ethernet Protection) This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. 10.12.2.3 Service Planning (Service Information) This section provides the information about all the parameters required for E-Line services carried on PWs.
10.12.2.4 Service Planning (QoS) The section provides the information about all the parameters required for configuring QoS.

This section provides the information about all the parameters required for configuring UNI ports. Table 10-84 provides the information about the Ethernet ports on NE34. Table 10-84 Information about Ethernet ports (NE34) Parameter NE34 1-EM6T-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Flow Control Enabled Layer 2 802.1Q Auto-Negotiation 1536 Disabled
10-168
Issue 03 (2011-04-10)
NOTE
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work in the corresponding modes. l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traverse the equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit jumbo frames with a greater length, set the maximum frame length according to the actual length of a jumbo frame. l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient QoS capabilities. The planning information of flow control must be the same for the equipment at both ends. l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is enabled.

This section provides the information about all the Ethernet protection parameters required for GE ports of NE31 connected to the RNC. To improve the reliability of service transmission, NE31 and the RNC are interconnected through the LAG formed by two GE links.Table 10-86 provides the planning information. Table 10-86 Information about LAGs Parameter LAG type Revertive mode Load sharing System priority Main port Slave port NE31 Static Non-Revertive Non-Sharing 32768 4-EM6T-1 4-EM6T-2
NOTE

This section provides the information about all the parameters required for E-Line services carried on PWs. Table 10-87 provides the planning information about E-Line services carried on PWs.
Issue 03 (2011-04-10)
10-169
Table 10-87 Planning information about E-Line services carried on PWs Parameter E-Line Services Carried on PWs Connected to BTS33 Source NE (NE34) Service ID Service Name Direction BPDU Source Port Source VLANs Bearer Type Protection Type 304 BTS33-RNC_E-Line UNI-NNI Not Transparently Transmitted 1-EM6T-3 330 PW No Protection Sink NE (NE31) 305 BTS33-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 330 PW No Protection
Table 10-88 provides the planning information about PWs. Table 10-88 Planning information about PWs Parameter E-Line Services Carried on PWs Connected to BTS33 Source NE (NE34) PW ID PW Signaling Type PW Type Direction PW Encapsulation Type PW Ingress Labs/Source Port PW Egress Labs/Sink Port Tunnel selection mode Tunnel Opposite LSR ID Control Word Control Channel Type VCCV Verification Mode 304 Static Ethernet Bidirectional MPLS 20 20 MPLS 1515 46.1.4.2 No Use Alert Label Ping Sink NE (NE31) 305 Static Ethernet Bidirectional MPLS 30 30 MPLS 1501 46.1.4.2 No Use Alert Label Ping
10-170
Issue 03 (2011-04-10)
NOTE
Table 10-89 provides the planning information about MS-PWs connected to NE32. Table 10-89 Planning information about MS-PWs Parameter ID Name MTU (byte) Service Type PW ID PW Signaling Type PW Type Direction PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Tunnel Opposite LSR ID 903 bts33_e-line_service_mspw 9000 Ethernet Service Forward PW: 305 Forward PW: Static Forward PW: Ethernet Forward PW: Bidirectional Forward PW: MPLS Forward PW: 30 Forward PW: 30 Forward PW: MPLS Forward PW: 1501 Forward PW: 46.1.4.1 Backward PW: 304 Backward PW: Static Backward PW: Ethernet Backward PW: Bidirectional Backward PW: MPLS Backward PW: 20 Backward PW: 20 Backward PW: MPLS Backward PW: 1515 Backward PW: 46.1.4.6 NE32
NOTE
l When MS-PWs are used, the label values of Forward PW and Backward PW cannot be the same. l In end-to-end configuration mode, PW ID, PW Ingress Label, and PW Egress Label can be automatically allocated and therefore they do not need to be planned. l In end-to-end configuration mode, MS-PW service ID and PW switching service ID are automatically allocated and invisible.

QoS (DiffServ)
Diffserv is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the
corresponding Diffserv domain according to the allocated VLAN priority, DSCP value, or MPLS EXP value. Each Ethernet port involved in the service must use the same Diffserv configuration. In this example, the BTS services are allocated corresponding C-VLAN priorities by service type, and PW-carried UNI-NNI E-Line services are configured on the transmission network. DiffServ planning has been completed for the transmission network during MPLS tunnel planning. In this example, you only need to set the trusted packet types of the UNI and NNI ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of the transmission network, therefore achieving end-to-end QoS control on the transmission network.


QoS (Port Shaping)



This section describes the process for configuring E-Line services carried on PWs in Per-NE configuration mode. 10.12.3.1 Configuration Process (UNI Ports) This section describes the process for configuring UNI port attributes. 10.12.3.2 Configuration Process (Ethernet Protection) This section describes how to create a LAG of the GE port of NE31 connected to the RNC. 10.12.3.3 Configuration Process (Service Information) This section describes the process for configuring E-Line services carried on PWs. 10.12.3.4 Configuration Process (QoS) This section describes the process for configuring QoS of E-Line services carried on PWs. 10.12.3.5 Configuration Process (Verifying Ethernet Service Configurations) This section describes the process for verifying Ethernet service configurations.

This section describes the process for configuring UNI port attributes.
Procedure
Step 1 See A.5.6.1 Setting the General Attributes of Ethernet Ports and set the general attributes of the UNI ports. l The values for the general attribute parameters of the UNI port of NE34 are provided as follows. Parameter NE34 1-EM6T-3 Enable Port Port Mode Encapsulation Type Working Mode Max Frame Length(byte) Enabled Layer 2 802.1Q Auto-Negotiation 1536
l The values for the general attribute parameters of the UNI port of NE31 are provided as follows.
Issue 03 (2011-04-10)
10-173
Parameter
NE31 4-EM6T-1 4-EM6T-2 Enabled Layer 2 802.1Q Auto-Negotiation 1536
Enabled Layer 2 802.1Q Auto-Negotiation 1536
Step 2 See A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of the UNI ports. l The values for the Layer 2 attribute parameters of the UNI port of NE34 are provided as follows. Parameter NE34 1-EM6T-3 TAG Tag Aware
----End

Procedure
Step 1 See A.6.2.1 Creating a LAG and create a LAG. The values for the relevant parameters that need to be set in the main interface are provided as follows. Parameter LAG No. LAG Name
10-174
Value Select Automatically Assign. ToRNC

Parameter LAG Type Revertive Mode Load Sharing System Priority
Value Static Non-Revertive Non-Sharing 32768
----End

Procedure
Step 1 See A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the ELine services. l Parameters of NE34 The values for the relevant parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type Protection Type NE34 304 BTS34-RNC_E-Line UNI-NNI Not Transparently Transmitted 1-EM6T-3 330 PW No Protection
Issue 03 (2011-04-10)
10-175
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode l Parameters of NE31 The values for the relevant parameters that need to be set in the main interface are provided as follows. Parameter Service ID Service Name Direction BPDU Source Interface Source VLAN ID Bearer Type NE31 305 BTS33-RNC_E-Line UNI-NNI Not Transparently Transmitted 4-EM6T-1 330 PW NE34 No Use Alert Label Ping
10-176
Issue 03 (2011-04-10)
NE31 No Protection
The values for the relevant parameters that need to be set in the Advanced Attributes dialog box are provided as follows. Parameter Control Word Control Channel Type VCCV Verification Mode NE31 No Use Alert Label Ping
Step 2 See A.8.4.2 Creating an MS-PW and configure the E-Line services. The values for the relevant parameters that need to be set for creating an MS-PW on NE32 are provided as follows. Parameter ID Name MTU(bytes)
Issue 03 (2011-04-10)
NE32 903 bts33_e-line_service_mspw 9000

Parameter Service Type PW ID PW Signaling Type PW Type PW Direction PW Encapsulation Type PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel Peer LSR ID Ethernet Service Forward PW: 305 Forward PW: Static Forward PW: Ethernet
NE32
Backward PW: 304 Backward PW: Static Backward PW: Ethernet Backward PW: Bidirectional Backward PW: MPLS Backward PW: 20 Backward PW: 20 Backward PW: MPLS Backward PW: 1515 Backward PW: 46.1.4.6
Forward PW: Bidirectional Forward PW: MPLS Forward PW: 30 Forward PW: 30 Forward PW: MPLS Forward PW: 1501 Forward PW: 46.1.4.1
----End

Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain and set the trusted packet types of the UNI and NNI ports on NE34 and NE31 that transmit the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively. 1. Select the default DS domain for the OptiX RTN equipment.
NOTE
Value 1 DefaultMap
Set the trusted packet type of the UNI ports on NE34 and NE31 to C-VLAN.
10-178
Issue 03 (2011-04-10)
Parameter
Value NE34 NE31 4-EM6T-1 4-EM6T-2
Port
1-EM6T-3
Packet Type
CVLAN
CVLAN
NOTE
Step 2 See A.6.7.4 Creating a Port Policy and create the port policy. The values for the relevant parameters of UNI ports of NE34 and NE31 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service levels)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy. The values for the relevant parameters of UNI ports of NE34 and NE31 are provided as follows. Parameter Value NE34 Port_Comm (Policy ID=1) Port 1-EM6T-3 NE31 Port_Comm (Policy ID=1) 4-EM6T-1 4-EM6T-2
----End
Issue 03 (2011-04-10)
10-179

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs For NE31 and NE34. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Domain Level EdgeNE 4 NE34 EdgeNE 4
Step 2 See A.6.8.2 Creating an MA and create an MA for NE31 and NE34. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period EdgeNE BTS33-RNC_E-Line BTS33-RNC_E-Line 1s NE34 EdgeNE BTS33-RNC_E-Line BTS33-RNC_E-Line 1s
Step 3 See A.6.8.3 Creating an MEP Point and create MEPs for NE31 and NE34. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Association Name Board Port
10-180
NE34 EdgeNE BTS33-RNC_E-Line 1-EM6T 1-EM6T-3

Issue 03 (2011-04-10)
EdgeNE BTS33-RNC_E-Line 4-EM6T 4-EM6T-1
Parameter
Value NE31 NE34 330 340 Ingress Active
VLAN MP ID Direction CC Status
330 313 Ingress Active
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and NE34. The values for the relevant parameters are provided as follows. Parameter Value NE31 Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) EdgeNE BTS33-RNC_E-Line 340 NE34 EdgeNE BTS33-RNC_E-Line 313
Step 5 On NE31, perform LB tests to verify the Ethernet service configurations. Perform the LB test by considering the MEP whose MP ID is 313 as the source MEP and the MEP whose MP ID is 340 as the sink MEP to check the connectivity of the E-Line services carried on the PWs between NE31 and NE34. The LB test result shows that no packet loss occurs. ----End
Issue 03 (2011-04-10)
10-181
11 Configuring the Clock
11
About This Chapter
Configuring the Clock
To ensure that clocks of all the nodes on the transmission network are synchronized, configure the clocks for these nodes according to a unified clock synchronization policy. 11.1 Basic Concepts Before configuring the clock, you need to be familiar with the basic concepts. 11.2 Configuration Procedure This section describes the procedures for configuring the clock source, clock protection, and output clock. 11.3 Configuration Example (Clock for a TDM Radio Chain Network) This section considers a TDM radio chain network as an example to describe how to configure the clock according to the network planning information. 11.4 Configuration Example (Clock for a TDM Radio Ring Network) This section considers a TDM radio ring network as an example to describe how to configure the clock according to the network planning information. 11.5 Configuration Example (Clock for a Hybrid Radio Chain Network) This section considers a Hybrid radio chain network as an example to describe how to configure clocks according to the network planning information. 11.6 Configuration Example (Clock for a Hybrid Radio Ring Network) This section considers a Hybrid radio ring network as an example to describe how to configure the clock according to the network planning information. 11.7 Configuration Example (Clocks for a PSN) This section uses clocks for a packet convergence ring and a Packet radio chain as examples to describe how to configure clocks according to the network planning information. 11.8 Configuration Example (Clocks Across a Third-party TDM Network) This section considers Ethernet services transmitted across a third-party TDM network as an example and describes how to configure clocks according to the planning information.
Issue 03 (2011-04-10)
11-1
11.1 Basic Concepts

Before configuring the clock, you need to be familiar with the basic concepts. 11.1.1 Clock Source A clock source is a signal source that carries the timing reference information. An NE implements clock synchronization, by using its phase locked loop (PLL) to lock the timing information of the clock source. 11.1.2 Clock Protection Modes The OptiX RTN 950 supports clock source protection based on priorities, synchronization status message (SSM) protection, and extended SSM protection. 11.1.3 Clock Synchronization Policy Users should plan a proper clock synchronization policy according to the network topology.
11.1.1 Clock Source

A clock source is a signal source that carries the timing reference information. An NE implements clock synchronization, by using its phase locked loop (PLL) to lock the timing information of the clock source. The OptiX RTN 950 supports the following clock sources: l l l l Line clock source Refers to a clock source that is extracted from the received SDH signal. Radio clock source Refers to a clock source that is extracted from the received radio signal. Tributary clock source Refers to a clock source that is extracted from the received PDH signal. Ethernet clock source Refers to a clock source that is extracted from the FE/GE signal by using the synchronous Ethernet function. l External clock source Refers to a clock source that is extracted from the 2 Mbit/s or 2 MHz signal that is received at the external clock port. l Internal clock source Refers to a clock source that is generated through the free-run oscillation of the built-in clock of an NE. The internal clock source has the lowest priority.
11.1.2 Clock Protection Modes

The OptiX RTN 950 supports clock source protection based on priorities, synchronization status message (SSM) protection, and extended SSM protection.
Clock Source Protection Based on Priorities

Clock source protection is provided based on the priorities specified in the clock source priority list. When the clock source of a higher priority fails, the clock source of a lower priority is used.
As shown in Figure 11-1, the radio links between NE1 and NE2 adopt the 1+1 HSB protection. NE2 needs to trace the clock on the radio links to keep synchronous with NE1. In this case, the clock sources extracted by the main and standby IF boards can be configured in the clock source priority list. The clock source extracted by the main IF board, however, has a higher priority. Therefore, if the 1+1 HSB protection switching occurs on the radio links, the clock can be switched at the same time. Figure 11-1 Clock source protection based on priorities
1+1 HSB configuration
BITS Clock
NE1
NE2
SSM Protection
The SSM protection uses the SSM protocol specified in ITU-T G.781 to realize the clock protection. According to the SSM protocol, the SDH NE transmits the SSM protocol through bits 5-8 of the S1 byte, realizes the automatic protection switching of clock sources, and prevents the timing loop. The OptiX RTN 950 supports SSM protection on SDH optical transmission lines, FE/GE links, and radio links. After SSM protection is enabled on an NE, automatic protection switching of clock sources conforms to the following rules: l l l According to the clock source priority list, the NE selects the clock source of the best quality as the synchronization source. If multiple clock sources have the best quality, the NE selects the one of the highest priority as the synchronization source. The NE broadcasts the quality information of the synchronization clock source to its downstream NEs, and also notifies its upstream NE that its own clock source cannot be used for synchronization.
Figure 11-2 is an radio ring where the SSM protection is enabled. When the network operates normally, the NEs on the ring select the clock source as follows: 1. 2. 3. NE1 selects the external clock source as the synchronization source and notifies NE2 and NE4 of the external clock quality. NE2 and NE4 select the clock source from NE1 as the synchronization source and notify NE1 that the clock sources from NE2 and NE4 are unusable. NE3 detects that the clock sources from NE2 and NE4 have the same quality and selects the clock source of a higher priority (the clock source from NE2) as the synchronization source. In addition, NE3 transmits the information of the synchronization source quality to NE4 and notifies NE2 that the clock source from NE3 is unusable. NE4 detects that the clock sources from NE1 and NE3 have the same quality and selects the clock source of a higher priority (the clock source from NE3) as the synchronization
4.
Issue 03 (2011-04-10)
source. In addition, NE4 transmits the quality information of the synchronization clock source to NE1 and notifies NE3 that the clock source from NE4 is unusable. 5. According to the clock quality in west and east directions and the configured clock source priorities, NE2, NE3, and NE4 determine that the synchronization source requires no modifications. Therefore, the clock source selection is finished.
When the radio links between NE1 and NE2 become faulty, the NEs on the ring select the clock source as follows: 1. 2. 3. NE2 selects the internal source as the synchronization source and transmits the information of the synchronization source quality to NE1 and NE3. NE3 selects NE2 as the clock source and informs NE4 of the clock quality. After detecting that the quality of the clock from NE1 is higher than the quality of the clock from NE3, NE4 transmits the clock quality information to NE3 and informs NE1 that the clock from NE4 is unavailable. After detecting that the quality of the clock from NE4 is higher than the quality of the clock from NE2, NE3 selects the clock source from NE4 as the synchronization source, transmits the information of the synchronization source quality to NE2, and notifies NE4 that the clock source from NE3 is unusable. After detecting that the quality of the clock from NE3 is higher than the quality of the internal clock source, NE2 selects the clock source from NE3 as the synchronization source, transmits the information of the synchronization source quality to NE1, and notifies NE3 that the clock source from NE2 is unusable. According to the clock quality in west and east directions and the configured clock source priorities, NE2, NE3, and NE4 determine that the synchronization source requires no modifications. Therefore, the clock source selection is completed.
NOTE
4.
5.
6.
The SSM protection does not provide a complete solution to the timing loop. Therefore, when you configure clock sources, the clocks cannot form a loop as on NE1 in this example.
Figure 11-2 SSM protection

BITS NE1 Extenal/ Internal
West/East/ Internal NE2
W E NE4 West/East/ Internal
W W E
Master clock NE3
West/East/ Internal
11-4
Issue 03 (2011-04-10)
Extended SSM Protection

The extended SSM protection uses the extended SSM protocol to provide the clock protection. The extended SSM protocol, developed by Huawei on the basis of the SSM protocol, introduces the concept of clock ID. Through the extended SSM protocol, you can define a clock ID for any clock source. The clock ID of the synchronization source can be transmitted together with the SSM protocol and be used for the automatic clock switching.OptiX RTN 950 supports extended SSM protection on SDH optical transmission lines, FE/GE links and radio links. After the extended SSM protection is enabled on an NE, the automatic clock switching conforms to the following rules: l l l l According to the clock source priority list, the NE selects the clock source of the best quality as the synchronization source. If the clock ID of a certain clock source indicates that the clock source is from the NE itself, the clock source is not processed. If multiple clock sources have the best quality, the NE selects the one of the highest priority as the synchronization source. The NE broadcasts the quality information and the clock ID of the synchronization clock source to its downstream NEs, and also notifies its upstream NE that its own clock source cannot be used for synchronization.
The clock ID takes a value from 0 to 15. 0 is the default value, indicating that the clock ID is invalid. After the extended SSM protocol is enabled on the NE, the NE does not select clock source 0 as the current clock source. Clock IDs are allocated as follows: l l l l l l When the extended SSM is used, the clock ID of an external clock source cannot be automatically extracted and needs to be allocated. At all the nodes that access external clock sources, the internal clock sources should have a clock ID. At all the intersection nodes of a ring/chain and a ring, the internal clock sources should have a clock ID. At all the intersection nodes of a ring/chain and a ring, the clock sources that are accessed into the ring should have a clock ID. The clock sources other than the preceding types always use their default clock ID of 0. Clock IDs are used for timing reference only. They do not indicate any priority difference.
Figure 11-3 is an radio ring where the extended SSM protection is enabled. On the ring, the following clock sources require a clock ID: l l l l External clock source 1 on NE1 External clock source 2 on NE3 Internal clock source on NE1 Internal clock source on NE3
Issue 03 (2011-04-10)
11-5
Figure 11-3 Extended SSM protection

Master BITS NE1 Extenal 1 / West / East / Internal
West / East / Internal NE2
E West / East / Internal
E W E West / East / Extenal 2 / Internal
NE4
Master clock Slave BITS
NE3
NOTE
l The extended SSM protection provides a complete solution to the timing loop. Therefore, when you configure clock sources, the clocks can form a loop. l The extended SSM protection is advantageous in the complex networking of clock protection, for example, the dual external clocks. Hence, the extended SSM protection is used in only a few cases.
11.1.3 Clock Synchronization Policy

Users should plan a proper clock synchronization policy according to the network topology.
Clock Synchronization Policy for a Chain Network

In the case of a chain network consisting of radio links, the clock synchronization policy should be planned according to the following principles: l l l The master (source) node accesses one clock source (which can be an external clock, a line clock, or an Ethernet clock). On this node, the accessed clock source should be configured. In the case of the other nodes, the clock sources for their upper level radio links should be configured. If the upper level radio link is configured with 1+1 protection, a node should be configured with two radio clock sources, and the clock source for the main radio link should have a higher priority than the clock source for the standby radio link. If a node has multiple upper level radio links (for example, the upper level radio links are configured with XPIC or N+1 protection), each radio link should be configured with one radio clock source on this node. In addition, these radio clock sources should be configured with different priorities according to the actual condition. The SSM or extended SSM protection need not be configured.
Figure 11-4 shows the clock synchronization policy for a chain network.
The master node (NE1) accesses one external clock source. In this case, the clock source priorities for NE1 in a descending order are as follows: external clock source > internal clock source. The ISU2 boards in slots 3 and 5 on NE2 form a 1+1 IF protection group, where the ISU2 board in slot 3 functions as the main board. In addition, the radio links between NE1 and NE2 comprise the two ISU2 boards. Hence, the clock source priorities for NE2 in a descending order are as follows: 3-ISU2-1 > 5-ISU2-1 > internal clock source. The radio link between NE3 and NE2 comprises the ISU2 board in slot 3 on NE3, and thus the clock source priorities for NE3 in a descending order are as follows: 3-ISU2-1 > internal clock source. The SSM or extended SSM protection need not be configured.
Figure 11-4 Clock synchronization policy for a chain network

NE1 NE2 NE3
BITS
Extenal/ Internal Clock
3-IF1-1/ 5-IF1-1/ Internal
3-IF1-1/ Internal
Clock Synchronization Policy for a Tree Network

A tree network can be considered the derivation of a chain network. Hence, a tree network can adopt the same clock synchronization policy as a chain network. Figure 11-5 shows the clock synchronization policy for a tree network. l In the case of the master node (NE1), the port 1 on the EM6T board in slot 2 accesses the Ethernet link, which functions as a clock source. Hence, the clock source priorities for NE1 in a descending order are as follows: 2-EMT6-1 > internal clock source. The ISX2 boards in slots 3 and 5 on NE2 form an XPIC working group, where the ISX2 board in slot 3 uses the vertical polarization mode and the ISX2 board in slot 5 uses the horizontal polarization mode. In addition, the radio links between NE1 and NE2 comprise the two ISX2 boards. Hence, the clock source priorities for NE2 in a descending order are as follows: 3-ISX2-1 > 5-ISX2-1 > internal clock source. The radio link between NE3 and NE2 comprises the ISU2 board in slot 3 on NE3, and thus the clock source priorities for NE3 in a descending order are as follows: 3-ISU2-1 > internal clock source. The radio link between NE4 and NE2 comprises the ISU2 board in slot 3 on NE4, and thus the clock source priorities for NE4 in a descending order are as follows: 3-ISU2-1 > internal clock source.
Issue 03 (2011-04-10)
11-7
The radio link between NE5 and NE4 comprises the ISU2 board in slot 3 on NE5, and thus the clock source priorities for NE5 in a descending order are as follows: 3-ISU2-1 > internal clock source. The SSM or extended SSM protection need not be configured.
Figure 11-5 Clock synchronization policy for a tree network

NE3
NE1
NE2
3-ISU2-1/ Internal
NE4 BSC 3-ISX2-1/ 5-ISX2-1/ Internal
NE5
2-EM6T-1/ Internal Clock
3-ISU2-1/ Internal
3-ISU2-1/ Internal
Clock Synchronization Policy for a Ring Network

If a ring network comprises only radio links or comprises radio links and optical transmission lines, plan the clock synchronization policy according to the following principles: l If only the SDH signal is transmitted on the ring, configure SSM or extended SSM protection according to the clock synchronization policy for an optical transmission network. If the PDH radio or Integrated IP radio is used on certain segments of the ring, equally divide the ring into two chains, and then plan the clock synchronization policy according to the related policy for a chain network.
Figure 11-6 shows the clock synchronization policy for a ring on which only the SDH signal is transmitted. l l Configure the SSM or extended SSM protection for all the nodes on the ring. The master node (NE1) accesses one external clock source. In this case, the clock source priorities in a descending order for NE1 are as follows: external clock source > internal clock source. The clock source priorities for the other nodes in a descending order are as follows: west clock source > east clock source > internal clock source.
11-8
Issue 03 (2011-04-10)
Figure 11-6 Clock synchronization policy for a ring network (on which only the SDH signal is transmitted)
BITS NE2 West/East/ Internal E E NE1
NE6 West/East/ Internal W
Extenal/ W Internal
W West/East/ Internal NE3 NE4 Master clock West/East/ Internal E W E
E West/East/ Internal NE5
Figure 11-7 shows the clock synchronization policy for a ring network on which not only the SDH signal is transmitted. l l The ring uses the Integrated IP radio for transmission. Thus, divide the ring into the following chains at the master node (NE1): NE1-NE2-NE3 and NE1-NE4. In the case of the master node (NE1), the port 1 on the EM6T board in slot 3 accesses the Ethernet link, which functions as a clock source. Hence, the clock source priorities for NE1 in a descending order are as follows: 3-EMT6-1 > internal clock source. NE2 traces the clock of the master node, and thus the clock source priorities for NE2 in a descending order are as follows: west clock source > internal clock source. NE3 traces the clock of NE2, and thus the clock source priorities for NE3 in a descending order are as follows: west clock source > internal clock source. NE4 traces the clock of the master node (NE1), and thus the clock source priorities for NE4 in a descending order are as follows: east clock source > internal clock source. The SSM or extended SSM protection need not be configured.
l l l l
Issue 03 (2011-04-10)
11-9
Figure 11-7 Clock synchronization policy for a ring network (on which not only the SDH signal is transmitted)
BSC NE1 3-EM6T-1/ Internal W E NE4 East/ Internal
W West/ Internal NE2 E
W W E
Clock
NE3
West/ Internal
Clock Synchronization Policy for a Port Aggregation Network

On a port aggregation network, services of several OptiX RTN NEs are aggregated to the upper level RTN NE through the optical transmission line, tributary, or Ethernet. Plan the clock synchronization policy for a port aggregation network according to the following principles: l l The upper level NE accesses a clock source (which can be an external clock source, a line clock source, or an Ethernet clock source). A lower-level NE traces the line clock source or the Ethernet clock source of its upper-level NE, if the service of the lower-level NE is aggregated to the upper-level NE through an optical transmission line or Ethernet. If the service of a lower-level NE is aggregated to the upper-level NE only through the E1 signal, the lower-level NE should trace the tributary clock source (E1 ports 1 and 5 on the E1 tributary board support the tributary clock source). If the service of a lower-level NE is aggregated to the upper-level NE only through the E1 signal and the lower-level NE is connected to many hops of downstream radio links, tracing the tributary clock source causes anomalies such as pointer justifications. In this case, the lower-level NE should trace the external clock source output by the upper level NE. The SSM or extended SSM protection need not be configured.
Figure 11-8 shows the clock synchronization policy for a tributary port aggregation network. l The master node (NE1) accesses one external clock source. In this case, the clock source priorities for NE1 in a descending order are as follows: external clock source > internal clock source. The IF1 boards in slots 3 and5 on NE2 form a 1+1 IF protection, where the IF1 board in slot 3 functions as the main board. In addition, the radio links between NE1 and NE2 comprise the two IF1 boards. Hence, the clock source priorities for NE2 in a descending order are as follows: 3-IF1-1 > 5-IF1-1 > internal clock source.
11-10
The service of NE3 is aggregate to NE2 through ports 1 to 4 on the SP3S board in slot 1. Hence, the clock source priorities for NE3 in a descending order are as follows: 1-SP3S-1 > internal clock source. NE4 is connected to many hops of downstream radio links. In this case, if it traces the tributary clock source, pointer justifications occur on the downstream nodes. Hence, NE4 traces the external clock source output by NE2. The SSM protection or extended SSM protection need not be configured.
Figure 11-8 Clock synchronization policy for a port aggregation network (aggregation only through the tributary port)
NE3 NE1 NE2 1-SP3S-1/ Internal External/ Internal 3-IF1-1/ 5-IF1-1/ Internal NE4
Clock
External/ Internal
Clock Synchronization Policy for Transmission Across TDM Network

The clock synchronization policy for transmission across a leased TDM network is similar to that for a chain network. The difference is that the lower-level node connected to the TDM network needs to trace the tributary clock on the TDM network. Figure 11-9 shows the clock synchronization policy for transmission across a TDM network. l The main node NE1 is synchronized with the BSC through the FE port, and thus the clock source priorities for NE1 in a descending order are as follows: 3-EFP8-1 > internal clock source.
NOTE
The FE ports on the EFP8 board (PORT1 to PORT8) support synchronous Ethernet.
On NE2, the SP3D board in slot 2 provides the E1 link connected to the TDM network, and the NE is a lower-level node connected to the TDM network. Therefore, the clock source priorities for NE2 in a descending order are as follows: 2-SP3D-1 > internal clock source. The ISU2 boards in slots 3 and 5 on NE3 form a 1+1 IF protection group, where the ISU2 board in slot 3 functions as the main board. In addition, the radio links between NE3 and NE2 comprise the two ISU2 boards. Hence, the clock source priorities for NE3 in a descending order are as follows: 3-ISU2-1 > 5-ISU2-1 > internal clock source. The SSM protection or extended SSM protection is not configured.
Issue 03 (2011-04-10)
11-11
Figure 11-9 Clock synchronization policy for transmission across TDM network
BSC NE1 NE2 NE3 BTS
FE
E1 TDM network
E1
FE 3-IFU2-1/ 5-IFU2-1/ Internal
3-EFP8-1 / Internal Clock
2-SP3D-1/ Internal
Precautions of Planning a Clock Synchronization Policy

When planning a clock synchronization policy, pay attention to the following points: l The number of NEs on a long clock chain should not be more than 20. A number smaller than 10 is recommended. If a large number of NEs exist on a long clock chain, add one more clock source for signal compensation in the middle of the chain. It is recommended that the SDH optical port should be used at a convergence node to converge the TDM service. In this manner, the clock signal can be transmitted over the SDH signal rather than over the PDH signal, which ensures the quality of the clock signal.
Clock Synchronization Policy for a Base Station

If a synchronization signal is transmitted to a BTS through the radio transmission network, plan the synchronization policy according to the following principles: If the BTS can access the transmission network through an SDH optical port or Ethernet port, use the SDH optical port or Ethernet port to provide the timing reference signal for the BTS. If the BTS can access the transmission network only through the E1 signal, the external clock port is preferred to transmit the timing reference signal to the BTS. If the BTS can access the transmission network only through the E1 signal and the external clock port cannot be used, use the E1 port to transmit the timing reference signal to the BTS. If the output clock does not meet the requirement of the BTS, the NE that is connected to the BTS can use the tributary retiming function. If the BTS can be accessed to the transmission network through Ethernet only and does not support the synchronous Ethernet function, you can provide the timing reference signal to the BTS through the external clock port.
Tributary Retiming
When being transmitted by the OptiX RTN 950, the PDH signal must undergo mapping and demapping processes, during which the jitter occurs. In addition, pointer justifications during the network transmission process cause the jitter of the PDH signal. Tributary retiming helps to reduce the jitter of the PDH signal when it is transmitted on a transmission network. Tributary retiming realizes the transmission of the signal that combines
the timing reference signal and the PDH service signal. Hence, the transmitted PDH signal carries the timing information that is synchronized with the timing reference signal. Figure 11-10 shows how a BSC transmits the synchronization information to a BTS through the radio transmission network after the tributary retiming function is enabled. The radio transmission network extracts the tributary clock from the E1 signal that is transmitted from the BSC. This tributary clock functions as the synchronization reference clock for the radio transmission network to be synchronized with the clock of the BSC. The tributary retiming function is enabled on NE3. In this manner, NE3 transmits the E1 signal that carries the retiming clock information to the BTS (NE3 selects the system clock as the retiming clock). In addition, NE3 is synchronized with the BSC. Hence, the BTS can extract the clock signal of the BSC from the tributary signal. The basic working principle of tributary retiming is as follows: The tributary signal is written into a large-capacity first in first output (FIFO), and then the tributary signal is read from the FIFO through the retiming clock. In this manner, the output signal contains the retiming clock information, and FIFO eliminates the jitter and wander in the original tributary signal. The OptiX RTN 950 can select the system clock or the line clock in the uplink E1 signal as the retiming clock, depending on the specific networking. In general cases, the system clock is selected as the retiming clock. Figure 11-10 Tributary retiming
NE1 E1 BSC NE3 Write clk (downlink E1 clk) E1 NE2 NE3
E1
Clock
FIFO
E1 Read clk (retiming clk)
When using the tributary retiming function, pay attention to the following points: l l l The retiming clock should be synchronized with the clock of the BSC, and the retiming clock should not undergo mapping and demapping processes. The tributary retiming function uses the FIFO, which causes a delay of 125 us or more. Use this function when it is necessary. The retiming function requires that the entire transmission network should be synchronized with the service network that requires retiming. If certain NEs on the transmission network are not synchronized, slips occur. The transmission network can meet the retiming requirement of only one service network.
Issue 03 (2011-04-10)
11-13

This section describes the procedures for configuring the clock source, clock protection, and output clock. Figure 11-11 provides the procedures for configuring clocks. Figure 11-11 Configuration flow chart (clocks)
Required Optional Configuring clock sources Start
Configuring the SSM or extended SSM protection
Modifying clock switching conditions
Modifying clock restoration parameters Modifying parameters of the output clock
Setting parameters of PDH ports Querying the clock synchronization status
End
11-14
Issue 03 (2011-04-10)
Table 11-1 Procedures for configuring clocks Step 1 Operation A.9.1.1 Configuring the Clock Sources Description Required. The parameters are set as follows: l According to the clock source that is planned, set Clock Source. l The External Clock Source Mode and Synchronous Status Byte parameters are valid only for the external clock source. Set the two parameters according to the actual condition of the external clock. In general cases, the two parameters take the default values. 2 Configuri ng the SSM or extended SSM protection A.9.1.2 Configuri ng Clock Subnets Required when the SSM or extended SSM protection is used. Set the parameters as follows: l Set Protection Status according to the used protocol type. l If the clock uses the extended SSM protection, set Clock Source ID for the following clock sources: External clock source Internal clock source of the NE that accesses the external clock source Internal clock source of the NE that connects the intersecting ring and chain or connects the intersecting rings Line clock source that is accessed to the ring through the NE that connects the intersecting ring and chain or connects the intersecting rings and is configured with the line clock source on the ring The values of Clock Source ID for these clock sources should be different. A.9.1.4 Configuri ng the SSM Output Status A.9.1.5 Configuri ng the Clock ID Output Status Required when the SSM or extended SSM protection. When a line port is connected to the NE on the same clock subnet, set Output S1 Byte Info to Enabled. In other cases, set Output S1 Byte Info to Disabled. Required when the extended SSM protection is used. When a line port is connected to the NE on the same clock subnet, set Output Clock ID to Enabled.
Issue 03 (2011-04-10)
11-15
Step
Operation A.9.1.3 SelfDefined Clock Quality
A.9.1.8 Changing the Conditions for Clock Source Switching A.9.1.9 Modifying the Recovery Parameter of the Clock Source A.9.1.7 Configuring Clock Sources for External Clock Output
Optional.
Optional.
Optional. By default, the OptiX RTN 950 allows output of the system clock source through the external clock port. If the external clock port transmits the system clock source only, manual configuration is not required. If the external clock port needs to transmit other clock sources, such as a clock from a radio link or synchronous Ethernet clock, you need to configure the priority table for the phase-locked loop (PLL) clock source of the external clock port. Optional when the external clock port is used to transmit the clock reference signal for the customer equipment. Set the parameters according to the requirement of the customer equipment. In general cases, these parameters take the default values.
A.9.1.6 Modifying the Parameters of the Clock Output
A.5.2 Setting the Parameters of PDH Ports
Optional when the output tributary clock requires retiming. Set Retiming Mode to Retiming Mode of CrossConnect Clock for the tributary port. l When a clock subnet uses the internal clock source of an NE as the reference clock, set NE Clock Mode to Free-Run Mode for this NE; set NE Clock Mode to Tracing Mode for the other NEs. l When a clock subnet uses the clock out of the subnet as the reference clock, set NE Clock Mode to Tracing Mode for all the NEs.
A.9.1.10 Querying the Clock Synchronization Status
11-16
Issue 03 (2011-04-10)
11.3 Configuration Example (Clock for a TDM Radio Chain Network)

This section considers a TDM radio chain network as an example to describe how to configure the clock according to the network planning information. 11.3.1 Networking Diagram This section describes the networking information about the NEs. 11.3.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 11.3.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 5.3 Configuration Example (Radio Links on the TDM Radio Chain Network), configure the clocks according to the following network planning information (as shown in Figure 11-12): l l The radio transmission network is directly synchronized with the clock of the upstream third-party network. Clock synchronization signals are transmitted to the BTSs over E1 signals.
Figure 11-12 Networking diagram (clock on a TDM radio chain network)
BTS2 E1 BTS3
E1 STM-1 NE4 E1 NE3 E1 NE5 BTS5 BTS4 NE2 BTS1 NE1 BSC STM-1
E1 NE6
The clock connections shown in Figure 11-12 are described as follows.
Issue 03 (2011-04-10)
11-17
Table 11-2 Clock connections (NE11) Link Between NE11 and the thirdparty network Port 1-SL1D-1 (working port of a linear MSP group) 1-SL1D-2 (protection port of a linear MSP group) Description Configure these ports to synchronize clock signals with the upstream third-party network.
Table 11-3 Clock connections (NE12) Link Between NE12 and NE11 Port 3-IF1 (main IF board of a 1+1 HSB protection group) 5-IF1 (standby IF board of a 1+1 HSB protection group) Description Configure these boards to synchronize clock signals with the upstream third-party network.
Table 11-4 Clock connections (NE13) Link Between NE13 and NE12 Port 1-SL1D-1 Description Configure this port to synchronize clock signals with the upstream third-party network.
11-18
Issue 03 (2011-04-10)
Table 11-7 Clock connections (NE16) Link Between NE16 and NE15 Port 3-IF1 Description Configure this board to synchronize clock signals with the upstream third-party network.

Clock Source Information

According to 11.1.3 Clock Synchronization Policy, Figure 11-13 shows the clock source information. Figure 11-13 Clock source information (TDM radio chain network)
3-IF1-1/5-IF1-1 Internal
STM-1 NE14 NE13 1-SL1D-1/ Internal NE16 3-IF1-1/ Internal NE15 4-IF1-1/ 6-IF1-1/ Internal Clock NE12 3-IF1-1/ 5-IF1-1/ Internal NE11 1-SL1D-1/ 1-SL1D-2/ Internal
STM-1 Third party network
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio network is synchronized with the third party network through the SDH optical port and transmits the timing reference signal through the E1 port. Hence, the E1 retiming function need not be enabled.

Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure the clock sources. The values for the related parameters are provided as follows. Paramete r Clock Source Value NE1 1-SL1D-1 1-SL1D-2 Internal Clock Source NE2 3-IF1-1 5-IF1-1 Internal Clock Source NE3 1-SL1D-1 Internal Clock Source NE4 3-IF1-1 5-IF1-1 Internal Clock Source NE5 4-IF1-1 6-IF1-1 Internal Clock Source NE6 3-IF1-1 Internal Clock Source
Step 2 See A.9.1.10 Querying the Clock Synchronization Status and query the clock synchronization status of the NEs. NE Clock Mode of all the NEs should be Tracing Mode. ----End
11.4 Configuration Example (Clock for a TDM Radio Ring Network)

This section considers a TDM radio ring network as an example to describe how to configure the clock according to the network planning information. 11.4.1 Networking Diagram This section describes the networking information about the NEs. 11.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 11.4.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. Based on 5.4 Configuration Example (Radio Links on the TDM Radio Ring Network), configure the clocks according to the following network planning information (as shown in Figure 11-14): l l The radio transmission network is directly synchronized with the clock of the upstream third-party network. Clock synchronization signals are transmitted to the BTSs over E1 signals.
11-20
Issue 03 (2011-04-10)
Figure 11-14 Networking diagram (clocks on a TDM radio ring network)

Third party network
E1
NE21
E1 BTS21 E1 NE22 BTS22 E1 NE23 BTS23 NE24 E1 BTS24
The clock connections shown in Figure 11-14 are described as follows. Table 11-8 Clock connections (NE21) Link Between NE21 and the thirdparty network Port 2-SP3S Description Configure this board for synchronizing NE21 with the clock of the upstream thirdparty network.
Table 11-9 Clock connections (NE22) Link Between NE22 and NE21 Port 3-IF1 Description The ports are used to synchronizing NE22 with the clock of the upstream thirdparty network. The ports are used for enabling the re-timing function so that the BTSs can be more precisely synchronized with the clock of the upstream third-party network.
Between NE22 and BTS21 Between NE22 and BTS22
2-SP3S 2-SP3S
Issue 03 (2011-04-10)
11-21
Table 11-10 Clock connections (NE23) Link Between NE23 and NE22 Port 3-IF1 Description This port is used to synchronizing NE23 with the clock of The ports are used for enabling the re-timing function so that the BTSs can be more precisely synchronized with the clock of the upstream third-party network. This port is used for enabling the re-timing function so that the BTS can be more precisely synchronized with the clock of The ports are used for enabling the retiming function so that the BTSs can be more precisely synchronized with the clock of the upstream third-party network.
2-SP3S
Table 11-11 Clock connections (NE24) Link Between NE24 and NE21 Port 4-IF1 (main IF board of a 1+1 HSB protection group) 6-IF1 (standby IF board of a 1+1 HSB protection group) Between NE24 and BTS24 2-SP3S Description Configure these boards to synchronize clock signals with the upstream third-party network. Configure this board for enabling the re-timing function so that the BTS can be precisely synchronized with the clock of the upstream third-party network.

11-22
Issue 03 (2011-04-10)

According to 11.1.3 Clock Synchronization Policy, Figure 11-15 shows the clock source information. Figure 11-15 Clock source information (TDM radio ring network)
2-SP3S-1/ Internal Third party network E1 NE21
NE22 3-IF1-1 Internal
NE24 4-IF1-1/ 6-IF1-1 Internal
Clock
NE23 3-IF1-1/ Internal
Clock Protection
In this example, a PDH radio ring network is set up. Thus, only the clock source protection based on priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio network is synchronized with the BSC through the E1 port and transmits the timing reference signal through the E1 port. Hence, the E1 retiming function needs to be enabled. The retiming function needs to be enabled for the following ports: l l l NE22: 2-SP3S-1, 2-SP3S-5 NE23: 2-SP3S-1 NE24: 2-SP3S-1
NOTE
In application, the external clock port, rather than the E1 port, is preferred to transmit the timing reference signal to a BTS.

Issue 03 (2011-04-10)
11-23
Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure the clock sources. The values for the related parameters are provided as follows. Parameter Value NE21 Clock Source 2-SP3S-1 Internal Clock Source NE22 3-IF1-1 5-IF1-1 Internal Clock Source NE23 3-IF1-1 Internal Clock Source NE24 4-IF1-1 6-IF1-1 Internal Clock Source
Step 2 See A.5.2 Setting the Parameters of PDH Ports and set the PDH port parameters. The values for the related parameters are provided as follows. Parameter Value NE22 Retiming Mode Retiming Mode of Tributary Clock (2SP3S-1) Retiming Mode of Tributary Clock (2SP3S-5) Normal (other ports) NE23 Retiming Mode of Tributary Clock (2SP3S-1) Normal (other ports) NE24 Retiming Mode of Tributary Clock (2SP3S-1) Normal (other ports)
11.5 Configuration Example (Clock for a Hybrid Radio Chain Network)

This section considers a Hybrid radio chain network as an example to describe how to configure clocks according to the network planning information. 11.5.1 Networking Diagram This section describes the networking information about the NEs. 11.5.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 11.5.3 Configuration Process

This section describes the networking information about the NEs. Based on 5.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network), configure the clocks according to the following network planning information (as shown in Figure 11-16): l l The radio transmission network is directly synchronized with the clock of the BSC through a LAG consisting of two GE links. Clock synchronization signals are transmitted to the BTSs over FE signals.
Figure 11-16 Networking diagram (clocks on a Hybrid radio chain network)

FE BTS2 FE BTS3 GE NE4 FE NE3 FE NE5 BTS5 BTS4 NE2 BTS1 NE1 BSC GE
FE NE6
The clock connections shown in Figure 11-16 are described as follows. Table 11-12 Clock connections (NE1) Link Between NE1 and the BSC Port 1-EM6F-1 (main port of a LAG) 1-EM6F-2 (slave port of a LAG) Description The ports are used to synchronizing NE1 with the clock of the BSC.
Table 11-13 Clock connections (NE2) Link Between NE2 and NE1 Port 3-ISU2 (main IF board of a 1 +1 HSB protection group) 5-ISU2 (standby IF board of a 1+1 HSB protection group) Description The ports are used to synchronizing NE2 with the clock of the BSC.
Issue 03 (2011-04-10)
11-25
Table 11-14 Clock connections (NE3) Link Between NE3 and NE2 Port 1-EM6T-1 Description This port is used to synchronizing NE3 with the clock of the BSC.
Table 11-17 Clock connections (NE6) Link Between NE6 and NE5 Port 3-ISU2 Description This port is used to synchronizing NE6 with the clock of the BSC.


According to 11.1.3 Clock Synchronization Policy, Figure 11-17 shows the clock source information.
11-26
Issue 03 (2011-04-10)
Figure 11-17 Networking diagram (clock for a Hybrid radio chain network)
3-ISU2-1/ 5-ISU2-1 Internal GE NE4 NE3 NE2 GE NE1 1-EM6F-1/ 1-EM6F-2/ Internal BSC
NE6 3-ISU2-1/ Internal
NE5 4-ISU2-1/ 6-ISU2-1 Internal Clock
1-EM6T-1/ 3-ISU2-1/ Internal 5-ISU2-1 Internal
NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio transmission network is synchronized with the BSC through the GE port, and transmits the timing reference signal to the BTS through the FE port.

Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure the clock sources. The values for the related parameters are provided as follows. Paramete r Clock Source Value NE1 1-EM6F-1 1-EM6F-2 Internal Clock Source NE2 3-ISU2-1 5-ISU2-1 Internal Clock Source NE3 1-EM6F-1 Internal Clock Source NE4 3-ISU2-1 5-ISU2-1 Internal Clock Source NE5 4-ISU2-1 6-ISU2-1 Internal Clock Source NE6 3-ISU2-1 Internal Clock Source
Issue 03 (2011-04-10)
11-27
11.6 Configuration Example (Clock for a Hybrid Radio Ring Network)

This section considers a Hybrid radio ring network as an example to describe how to configure the clock according to the network planning information. 11.6.1 Network Diagram This section describes the networking information about the NEs. 11.6.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 11.6.3 Configuration Process This section describes the process for data configuration.
11.6.1 Network Diagram

This section describes the networking information about the NEs. Based on 5.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network), configure the clocks according to the following network planning information (as shown in Figure 11-18): l l The Hybrid radio transmission network is synchronized with NE21 on the PSN. OptiX RTN NEs transmit clock synchronization signals through their E1/FE ports to 2G/ 3G base stations.
Figure 11-18 Networking diagram (clock on a Hybrid radio ring network)
Packet network
R4 BTS21
FE
NE21 FE R4
E1 NE22 BTS22 FE NE23 R4 BTS23
NE24
BTS24
11-28
Issue 03 (2011-04-10)
The clock connections shown in Figure 11-18 are described as follows. Table 11-18 Clock connections (NE22) Link Between NE22 and NE21 Port 3-ISU2 (high-priority clock source, with the SSM protocol enabled) 4-ISU2 (low-priority clock source, with the SSM protocol enabled) Description Configure these ports to implement clock synchronization with the upstream PSN.
Table 11-19 Clock connections (NE23) Link Between NE23 and NE22 Port 3-ISU2 (high-priority clock source, with the SSM protocol enabled) 4-ISU2 (low-priority clock source, with the SSM protocol enabled) Description Configure these ports to implement clock synchronization with the upstream PSN.
Table 11-20 Clock connections (NE24) Link Between NE24 and NE21 Port 4-ISU2 (main IF board in a 1 +1 HSB protection group; high-priority clock source, with the SSM protocol enabled) 6-ISU2 (standby IF board in a 1+1 HSB protection group; high-priority clock source, with the SSM protocol enabled) Between NE24 and NE23 3-ISU2 (low-priority clock source, with the SSM protocol enabled) Description Configure these ports to implement clock synchronization with the upstream PSN.
Issue 03 (2011-04-10)
11-29


Based on 11.1.3 Clock Synchronization Policy, you can obtain the clock source information as shown in Figure 11-19. Figure 11-19 Information about clock sources (Hybrid radio ring network)
Packet network
NE21
NE22 3-ISU2-1/ 4-ISU2-1/ Internal
NE24 4-ISU2-1/ 6-ISU2-1/ 3-ISU2-1/ Internal NE23 3-ISU2-1/ 4-ISU2-1/ Internal
Clock
Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
Clock Synchronization Policy for 2G Base Stations - CES Retiming Function

In this example, 2G base stations extract clock information through E1 ports on the PSN. The PSN implements the following clock synchronization: l l Network-wide clock synchronization Synchronization between the network-wide clock and the service clock
Therefore, the PSN can use the CES retiming function for clock synchronization. That is, the PSN extracts system clock information from the E1 signal converted from a CES service and then provides the clock synchronization signal through E1 ports to base stations.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
11-30
Issue 03 (2011-04-10)
Clock Synchronization Policy for 3G Base Stations - Synchronous Ethernet Function

In this example, 3G base stations extract reference clock information from FE ports on the PSN. Therefore, the PSN can use the synchronous Ethernet function for clock synchronization with base stations. That is, the PSN provides clock synchronization signals to base stations through FE ports.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.

Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure the clock sources. The values for the related parameters are provided as follows. Parameter Value NE22 Clock Source 3-ISU2-1 4-ISU2-1 Internal Clock Source NE23 3-ISU2-1 4-ISU2-1 Internal Clock Source NE24 4-ISU2-1 6-ISU2-1 3-ISU2-1 Internal Clock Source
Step 2 See A.9.1.2 Configuring Clock Subnets and configure protection for clock sources. For NE22 to NE24, the values for the related parameters are provided as follows. Parameter Start Standard SSM Protocol Value Selected
NOTE
The other parameters take their default values.
Step 3 See A.9.1.10 Querying the Clock Synchronization Status and query the clock synchronization status. NE Clock Mode of all NEs should be Tracing Mode. ----End
11.7 Configuration Example (Clocks for a PSN)

This section uses clocks for a packet convergence ring and a Packet radio chain as examples to describe how to configure clocks according to the network planning information. 11.7.1 Networking Diagram This section describes the networking information about the NEs. 11.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 11.7.3 Configuration Process This section describes the process for data configuration.

This section describes the networking information about the NEs. Based on 3.2 Common Network Scenario of the IP Radio Network, configure the clocks according to the following network planning information (as shown in Figure 11-20): l l The BSC and RNC are synchronized with an external BITS clock. The PSN is synchronized with the same BITS clock as the BSC and RNC. The NEs on the PSN are synchronized with each other through physical clocks (clocks from microwave ports or clocks from Ethernet ports using the synchronous Ethernet function). The PSN transmits clock synchronization signals through its E1/FE ports to 2G/3G base stations.
Figure 11-20 Networking diagram (clocks for a PSN)

BTS33
FE

E1 E1 GE
R4
R4
FE GE
BTS34
R99

E1
NE11
GE
NE31
E1
NE21
E1
GE
E +G E1
BTS36
BTS35
BSC
R99 BTS37
R99 BTS38 RNC
11-32
Issue 03 (2011-04-10)
The clock connections shown in Figure 11-20 are described as follows. Table 11-21 Clock connections (NE11) Link Between NE11 and NE21 Port 2-EM6F-2 (high-priority clock source, with the SSM protocol enabled) 2-EM6F-1 (low-priority clock source, with the SSM protocol enabled) Description Configure Ethernet clocks extracted from ports that use the synchronous Ethernet function to implement clock synchronization with the upstream clock.
Table 11-22 Clock connections (NE21) Link Between NE21 and NE31 Port 1-EM6F-1 (high-priority clock source, with the SSM protocol enabled) 1-EM6F-2 (low-priority clock source, with the SSM protocol enabled) Description Configure Ethernet clocks extracted from ports that use the synchronous Ethernet function to implement clock synchronization with the upstream clock.
Table 11-23 Clock connections (NE31) Link Between NE31 and a BITS Port External clock port Description Configure the external clock port (CLK/TOD1) on the CSH board to implement clock synchronization with the external BITS clock.
Table 11-24 Clock connections (NE32) Link Between NE32 and NE31 Port 2-EM6F-2 (high-priority clock source, with the SSM protocol enabled) 2-EM6F-1 (low-priority clock source, with the SSM protocol enabled) Description Configure Ethernet clocks extracted from ports that use the synchronous Ethernet function to implement clock synchronization with the upstream clock.
Issue 03 (2011-04-10)
11-33
Table 11-25 Clock connections (NE33) Link Between NE33 and NE32 Port 4-ISU2 (main IF board in a 1 +1 HSB protection group) 6-ISU2 (standby IF board of a 1+1 HSB protection group) Description Configure microwave clocks to implement clock synchronization with the upstream clock.
Table 11-26 Clock connections (NE34) Link Between NE34 and NE33 Port 3-ISU2 (main IF board in a 1 +1 HSB protection group) Description Configure a microwave clock to implement clock synchronization with the upstream clock.


11.1.3 Clock Synchronization Policy provides clock source tracing information of the PSN and the clock source priority table of each NE. Figure 11-21 Clock source information (PSN)
BTS33 R4 NE34 NE33 BTS31 FE E1 BTS34 R99 E1 BTS32 GE NE32 NE11 E1 GE BTS36 BTS35 SSM NE21 E1 R99 BTS37 Clock NE31 E1 GE
E1
FE
R4 GE
R99 BTS38 RNC
E +G
BSC
11-34
Issue 03 (2011-04-10)
Table 11-27 Clock source priority table NE11 2-EM6F-2 2-EM6F-1 Internal clock source NE21 1-EM6F-1 1-EM6F-2 Internal clock source NE31 External clock source 1 Internal clock source NE32 2-EM6F-2 2-EM6F-1 Internal clock source NE33 3-ISU2-1 6-ISU2-1 Internal clock source NE34 3-ISU2-1 Internal clock source
Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
Clock Synchronization Policy for 2G Base Stations - CES Retiming Function

In this example, 2G base stations extract clock information through E1 ports on the PSN. The PSN implements the following clock synchronization: l l Network-wide clock synchronization Synchronization between the network-wide clock and the service clock
Therefore, the PSN can use the CES retiming function for clock synchronization. That is, the PSN extracts system clock information from the E1 signal converted from a CES service and then provides the clock synchronization signal through E1 ports to base stations.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
Clock Synchronization Policy for 3G Base Stations - Synchronous Ethernet Function

In this example, 3G base stations extract reference clock information from FE ports on the PSN. Therefore, the PSN can use the synchronous Ethernet function for clock synchronization with base stations. That is, the PSN provides clock synchronization signals to base stations through FE ports.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.

Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure clock sources. The values for the related parameters are provided as follows.
Paramete r Clock Source
Value NE11 2-EM6F-2 2-EM6F-1 Internal Clock Source NE21 1-EM6F-1 1-EM6F-2 Internal Clock Source NE31 External Clock Source 1 Internal Clock Source NE32 2-EM6F-2 2-EM6F-1 Internal Clock Source NE33 3-ISU2-1 6-ISU2-1 Internal Clock Source NE34 3-ISU2-1 Internal Clock Source
Step 2 See A.9.1.2 Configuring Clock Subnets and configure protection for clock sources. For NE11, NE21, and NE31 to NE34, the values for the related parameters are provided as follows. Parameter Start Standard SSM Protocol Value Selected
NOTE
The other parameters take their default values.
Step 3 See A.9.1.10 Querying the Clock Synchronization Status and query the clock synchronization status. NE Clock Mode of all NEs should be Tracing Mode. ----End
11.8 Configuration Example (Clocks Across a Third-party TDM Network)

This section considers Ethernet services transmitted across a third-party TDM network as an example and describes how to configure clocks according to the planning information. 11.8.1 Networking Diagram The section describes the networking information about the NEs. 11.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 11.8.3 Configuration Process This section describes the process for the data configuration.

The section describes the networking information about the NEs.
Based on 8.4 Configuration Example (Ethernet Services Traversing a TDM Network), configure the clocks according to the following network planning information (as shown in Figure 11-22): l l The transmission network is directly synchronized with the clock of the BSC through FE ports. Clock synchronization signals are transmitted to the BTS over FE ports.
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2NE6, see 11.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Figure 11-22 Networking diagram (clocks across a third-party TDM network)

BTS2 BTS6 FE TDM network E1 FE BTS1 NE7 BTS4 BSC
FE GE NE4 FE NE3 FE NE5 BTS5 NE2 NE1
FE
E1
FE NE6
Figure 11-23 Board configuration (clocks across a third-party TDM network)

NE13 NE cascade
ISU2 ISU2 SP3S CSH ISU2 NE6 ISU2 EM6T
NE14
FE E1 BTS12
SP3S
NE12
NE11
CSH ISU2 NE6 ISU2 EFP8 SP3D
FE
SP3D
GE
E1 E1 E1 FE BTS11 TDM network E1 BTS16
CSH
CSH
CSH ISU2 ISU2 SP3S
NE6 ISU2
EM6T SP3S
NE6 ISU2
EM6T
NE6
EFP8 SP3D
NE16 FE BTS15
NE15 E1
NE17 FE
BSC
The following figure shows the clock link connections of NE1 and NE7.
Table 11-28 Clock link connections (NE1) Link Connected to the leased TDM network Used Clock Port 2-SP3D-1 Description Used for synchronization with the TDM network.
Table 11-29 Clock link connections (NE7) Link Connected to the BSC Used Clock Port 4-EFP8-1 Description Used for synchronization with the BSC.


Based on 11.1.3 Clock Synchronization Policy, you can obtain the clock source information as shown in Figure 11-24. Figure 11-24 Information about clock sources (Hybrid radio chain network)
3-IFU2-1/ 5-IFU2-1 Internal GE NE4 E1 NE3 NE2 1-EM6T-1/ 3-IFU2-1/ Internal 5-IFU2-1 Internal NE1 2-SP3D-1/ Internal TDM network E1 FE NE7 4-EFP8-1/ Internal
NE6 3-IFU2-1/ Internal Clock
NE5 4-IFU2-1/ 6-IFU2-1 Internal
BSC
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2NE6, see 11.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Clock Protection
In this example, a chain network is set up. Therefore, only the clock source protection based on priorities is configured and the SSM or extended SSM protection is not configured.

In this example, the radio transmission network is synchronized with the BSC through the FE port on the EFP8 board of NE7, and transmits the timing reference signal to the base station through the FE ports that accesses services from the base station.

Procedure
Step 1 See A.9.1.1 Configuring the Clock Sources and configure the clock sources. The values for the relevant parameters are provided as follows. Parameter Value Range NE1 Clock Source 9-SP3D-1 Internal Clock Source NE7 4-EFP8-1 Internal Clock Source
Step 2 See A.9.1.10 Querying the Clock Synchronization Status and query the clock synchronization status of the NEs. For all NEs, set NE Clock Mode to Tracing Mode. ----End
Issue 03 (2011-04-10)
11-39
12 Configuring Auxiliary Ports and Functions
12
Configuring Auxiliary Ports and Functions
About This Chapter

The OptiX RTN 950 provides multiple auxiliary ports and functions. These functions require certain data configuration. 12.1 Auxiliary Ports and Functions This section describes the auxiliary ports and functions supported by the OptiX RTN 950, namely, the orderwire, synchronous data services, asynchronous data services, and wayside services. 12.2 Environment Monitoring Functions The OptiX RTN 950 supports the function of monitoring environment by means of external alarms and monitors an outdoor cabinet by means of its outdoor cabinet monitoring port. 12.3 Configuration Procedure (Monitoring the Outdoor Cabinet) This section describes how to perform parameter settings and other relevant operations as required in the procedures for configuring the function of monitoring the outdoor cabinet. 12.4 Configuration Example (Orderwire) This section considers the orderwire on a radio network as an example to describe how to plan the orderwire according to network planning information. 12.5 Configuration Example (Synchronous Data Services) This section considers a synchronous data service that transmits the network management information as an example to describe how to configure a synchronous data service according to the network planning information. 12.6 Configuration Example (Asynchronous Data Services) This section considers an asynchronous data service that transmits the NM messages as an example to describe how to configure an asynchronous data service according to the network planning information. 12.7 Configuration Example (Wayside E1 Services) This section considers a wayside E1 service that transmits the NM messages as an example to describe how to configure a wayside E1 service according to the network planning. 12.8 Configuration Example (External Alarms)
This section considers the centralized control of environment monitoring and equipment alarms through external alarms as an example to describe how to configure external alarms according to the network planning information. 12.9 Configuration Example (Monitoring the Outdoor Cabinet) This chapter describes the process of configuring the temperature and humidity thresholds for the PMU of the outdoor cabinet. This example helps you understand how to configure the function of monitoring the outdoor cabinet according to the network planning information.
12-2
Issue 03 (2011-04-10)
12.1 Auxiliary Ports and Functions

This section describes the auxiliary ports and functions supported by the OptiX RTN 950, namely, the orderwire, synchronous data services, asynchronous data services, and wayside services.
Orderwire
The OptiX RTN 950 supports one orderwire phone so that the operation or maintenance engineers at different workstations can perform voice communication through microwave or SDH overhead bytes. When using the orderwire phone, take the following precautions: l The orderwire phone numbers of all the NEs on the network must be of the same length. It is recommended that the orderwire telephone number is a 3-digit number and all orderwire telephone numbers on the entire network are unique. The dialing method of the orderwire phone of each node is dual-tone multifrequency. The call waiting time of each node should be set to the same value. If less than 30 nodes exist in the orderwire subnet, it is recommended that you set the call waiting time to five seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set the call waiting time to nine seconds. The equipment supports the orderwire group call function. When one set of the OptiX RTN equipment dials the orderwire group call number "888", the orderwire phones of all the OptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call, the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-tomultipoint group call changes to a point-to-point ordinary orderwire call. When the orderwire signals are transmitted over a radio link, they are always transmitted through one customized overhead byte. When the orderwire signals are transmitted over SDH fibers, they are transmitted through the E1 or E2 byte. By default, all the line ports, IF ports, and unconfigured synchronous data ports on the equipment function as the orderwire ports. Therefore, in normal cases, the orderwire ports needs to be configured only at the edge of the orderwire subnet. The equipment supports the transmission of orderwire overhead bytes through the 64 kbit/ s synchronous data ports or external clock ports. If multiple radio links or optical transmission lines exist between two NEs, the ports corresponding to these links should be configured as the orderwire ports. In this case, except for the hybrid radio links in N+1 protection, if one radio link is available between two NEs, the orderwire transmission between two NEs is normal. When the orderwire signals are transmitted over the hybrid radio links in N+1 protection, the protection link cannot transmit the orderwire signals. The equipment provides the orderwire ports on the AUX board. For definitions of the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
l l
l l
Synchronous Data Services

The synchronous data service is also called the F1 data service. The OptiX RTN 950 supports one synchronous data service. The microwave/SDH overhead bytes transmitted between two NEs can be used for transmitting one 64 kbit/s synchronous data service.
When using the synchronous data service, take the following precautions: l l l l The synchronous data service is fully transparently transmitted, and the transmission rate at the port is 64 kbit/s. The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors occur. The ports on the equipment comply with ITU-T G.703. When the orderwire signals are transmitted over a radio link, they are always transmitted through one customized overhead byte. When the orderwire signals are transmitted over SDH fibers, they are always transmitted through the F1 byte. The equipment supports the transmission of the overhead bytes in the synchronous data service through the external clock ports to realize the service spanning function. When the synchronous data service is transmitted over the protected radio links or optical transmission lines, the synchronous data service is also protected. The equipment provides the synchronous data service ports on the AUX. For definitions of the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
l l l
Asynchronous Data Services

The asynchronous data service is also called a transparent data service or a broadcast data port service. The OptiX RTN 950 supports one asynchronous data service. The microwave/SDH overhead bytes transmitted between two sites can be used for realizing full-duplex communication between the universal asynchronous receiver/transmitter (UART). When using the asynchronous data service, take the following precautions: l The asynchronous data service is fully transparently transmitted. The transmission rate and transmission control protocol need not be configured. The transmission rate at the port is 19.2 kbit/s. The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errors occur. The equipment provides the RS-232 electrical port that complies with ITU-T V.24/V.28. The equipment supports only point-to-point communications. When the orderwire signals are transmitted over radio links, they are always transmitted through one customized overhead byte. When the orderwire signals are transmitted over SDH fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes. The equipment supports the transmission of the overhead bytes in the asynchronous data service through the external clock ports to realize the service spanning function. When the asynchronous data service is transmitted over the protected radio links or optical transmission lines, the asynchronous data service is also protected. The equipment provides the asynchronous data ports on the AUX board. For definitions of the pins on the ports, see the OptiX RTN 950 IDU Hardware Description.
l l l l
l l l
Wayside E1 Services
The OptiX RTN 950 supports one wayside E1 service. The transmitted overhead bytes in the STM-1 radio signals can be used for transmitting one wayside E1 service between two sites in one hop of STM-1 radio link. When using the wayside E1 service, take the following precautions:
l l l l l l
The wayside E1 service is supported by only STM-1 radio links or E1 radio links. The wayside E1 service is fully and transparently transmitted, and the transmission rate at the port is 2048 kbit/s. The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur. The equipment does not support the pass-through of the wayside E1 service. Therefore, the wayside E1 service is transmitted only between two sites on one hop of radio link. When the wayside E1 service is transmitted over the radio links in 1+1 or N+1 protection mode, the wayside E1 service is also protected. The equipment adds or drops the wayside E1 service through the external clock port on the SCC, cross-connect and clock board. The external clock port complies with ITU-T G.703, and the impedance on the path is 120 ohms. For definitions of the pins on the external clock ports, see the OptiX RTN 950DU Hardware Description.
12.2 Environment Monitoring Functions

The OptiX RTN 950 supports the function of monitoring environment by means of external alarms and monitors an outdoor cabinet by means of its outdoor cabinet monitoring port.
External Alarms
External alarms are also called housekeeping alarms or relay alarms. The OptiX RTN 950 provides 4-input and 2-output external alarms. Figure 12-1 shows the interface circuit for external alarm input. When the external relay is switched off, the interface circuit generates a high-level signal. When the external relay is switched on, the interface circuit generates a low-level signal. The board generates corresponding alarms based on the level signal. External alarm input mainly achieves access of the relay alarms generated by the environmental alarm generator. Figure 12-1 Interface circuit for external alarm input
Circuit for external alarm input Output level +3.3 V/+5 V Pull-up resistance External system Relay
The interface circuit for external alarm output works in a similar manner as the external system shown in Figure 12-1. When the specified external alarm output conditions are met, the NE switches on or switches off the relay depending on the conditions that result in the alarm. When the specified external alarm output conditions are no longer met, the NE changes the relay to the reverse of its current state. External alarm output helps to provide equipment alarms to the centralized alarming device. The equipment provides external alarm ports on the AUX board. For pin assignments for the ports, see the OptiX RTN 950 IDU Hardware Description.
Monitoring of an Outdoor Cabinet

The OptiX RTN 950 supports the function of monitoring the power system and environment variables of the following outdoor cabinets: l APM30H: The advanced power module with heat exchanger cooler (APM30H) cabinet supports alternating current (AC) power input and direct current (DC) power output. It provides 7U of space for installing user equipment. TMC11H: The transmission cabinet of 11U high with heat exchanger (TMC11H) cabinet supports DC power input and DC power output. It provides 11U of space for installing user equipment. OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides 2U of space for installing user equipment.
NOTE
On the NMS, an outdoor cabinet is named based on its power input mode: An APM30H cabinet is named APM30 AC, a TCM11H cabinet is named APM30 DC, an OMB (AC power input) cabinet is named OMB AC, and an OMB (DC power input) cabinet is named OMB DC.
Table 12-1 describes the logical slots of outdoor cabinets supported by the OptiX RTN 950 and their functions. Table 12-1 Logical slots for supported outdoor cabinets Type of Outdoor Cabinet APM30 AC Logical Board PMU in slot 14 + TCU in slot 15 + TCU in slot 16 Function PMU in slot 14: power monitoring unit of the outdoor cabinet TCU in slot 15: temperature control unit of the outdoor cabinet TCU in slot 16: temperature control unit of the battery compartment in the outdoor cabinet APM30 DC TCU in slot 13 TCU in slot 13: temperature control unit of the outdoor cabinet PMU in slot 12: power monitoring unit of the outdoor cabinet TCU in slot 13: temperature control unit of the outdoor cabinet OMB DC TCU in slot 13 TCU in slot 13: temperature control unit of the outdoor cabinet
OMB AC
PMU in slot 12 + TCU in slot 13
12-6
Issue 03 (2011-04-10)
The OptiX RTN 950 provides the outdoor cabinet monitoring port on its system control, switching, and timing board. For pin assignments for the port, see the OptiX RTN 950 IDU Hardware Description.
12.3 Configuration Procedure (Monitoring the Outdoor Cabinet)

This section describes how to perform parameter settings and other relevant operations as required in the procedures for configuring the function of monitoring the outdoor cabinet.

Figure 12-2 provides the procedures for configuring the function of monitoring the outdoor cabinet. Figure 12-2 Configuration flow chart
Required Start Optional Set the function of an auxiliary port.
Set the type of the outdoor cabinet.
Set the logical boards of the outdoor cabinet.
Set the temperature and fan information of the outdoor cabinet.
Set the information about the power system of the outdoor cabinet.
Set the temperature and humidity thresholds of the PMU.
End
The procedures in the configuration flowchart are described as follows. Table 12-2 Procedures for configuring the function of monitoring the outdoor cabinet Step 1 Operation A.11.6.1 Configuring the Function of an Auxiliary Port Description Required. Set Interface Mode of the TOD2 port (CSH/CST) to MON.
12-7
Issue 03 (2011-04-10)
Step 2
Operation A.11.6.2 Setting the Type of the Outdoor Cabinet
Description Required. Ensure that the configured cabinet type is the same as the type of the actually used outdoor cabinet. Required. For logical slots for different types of outdoor cabinets and their functions, refer to Table 12-1 in 12.2 Environment Monitoring Functions.
A.1.1.4 Configuring the Logical Board
Configuring the function of monitoring the outdoor cabinet
Setting the temperature and fan information of the outdoor cabinet
Required if the temperature and fan information of the outdoor cabinet need to be monitored. It is recommended that the parameters take their default values, unless otherwise specified. Required if the power system information of the outdoor cabinet needs to be monitored. l Under Outdoor cabinet interface and Outdoor Cabinet PMU Electrical Source System Attribute, set the required power information according to the network planning information. l It is recommended that the parameters take their default values, unless otherwise specified.
NOTE This operation is supported only by APM30 AC and OBM AC cabinets. The OBM AC cabinets do not support setting parameters about the battery group.
Setting the information about the power system of the outdoor cabinet
12-8
Issue 03 (2011-04-10)
Step
Operation Setting the temperature and humidity thresholds of the PMU
Description Required if the temperature and humidity information of the PMU needs to be monitored. l Set Upper Threshold and Lower Threshold for temperature and humidity alarms according to the network planning information. l It is recommended that the parameters take their default values, unless otherwise specified.
NOTE This operation is supported only by APM30 AC and OBM AC cabinets.
12.4 Configuration Example (Orderwire)

This section considers the orderwire on a radio network as an example to describe how to plan the orderwire according to network planning information. 12.4.1 Networking Diagram This section describes the networking information about the NEs. 12.4.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 12.4.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 12-3, each NE needs to be configured with the orderwire. Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all the other radio links are configured with 1+0 non-protection.
Issue 03 (2011-04-10)
12-9
Figure 12-3 Networking diagram (orderwire)

1+0 1+1 NE4 1+0 1+0 NE3 NE2 NE1 E1
NE6
NE5
Table 12-3 Orderwire phone connections (NE1) Link Between NE1 and NE2 Port 3-IFU2 (main IF board) 5-IFU2 (standby IF board) Description Configure the ports to implement IF 1+1 protection.
Table 12-4 Orderwire phone connections (NE2) Link Between NE2 and NE1 Port 3-IFU2 (main IF board) 5-IFU2 (standby IF board) Between NE2 and NE3 F1 Description Configure the ports to implement IF 1+1 protection. The two NEs are interconnected through synchronous data ports.
Table 12-5 Orderwire phone connections (NE3) Link Between NE3 and NE2 Port F1 Description The two NEs are interconnected through synchronous data ports. Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
Between NE3 and NE4
3-IFU2
Between NE3 and NE5
4-IFU2
12-10
Issue 03 (2011-04-10)
Table 12-6 Orderwire phone connections (NE4) Link Between NE4 and NE3 Port 3-IFU2 Description Configure this port to receive and transmit radio service signals.
Table 12-7 Orderwire phone connections (NE5) Link Between NE5 and NE3 Port 4-IFU2 Description Configure this port to receive and transmit radio service signals. Configure this port to receive and transmit radio service signals.
Between NE5 and NE6
3-IFU2
Table 12-8 Orderwire phone connections (NE6) Link Between NE6 and NE5 Port 3-IFU2 Description Configure this port to receive and transmit radio service signals.

Information About Orderwire Phone Numbers

In this example, the number of NEs is very small. Therefore, the orderwire phone numbers are allocated in the format of 100+NE ID, as shown in Figure 12-4. Figure 12-4 Networking diagram (for orderwire)
1+0 104 NE4 1+0 1+0 NE3 E1 NE2 NE1 101 103 102 1+1
NE6
NE5 105 106
Issue 03 (2011-04-10)
12-11
Information About Orderwire Ports

l In this example, the service between NE2 and NE3 is forwarded through the E1 line. Therefore, service spanning is required. The 64 kbit/s synchronous data service port is used for service spanning. NE2 to NE6 are located on the orderwire subnet. Hence, they use the default orderwire ports (all the IF ports, line ports, and unconfigured synchronous data ports) that are automatically mapped by the equipment. NE1 is not located at the edge of the orderwire subnet. Hence, it is configured according to the situation of NE2 to NE6. If NE1 is located at the edge of the orderwire subnet and if it is connected to an IF ports or line ports on the other orderwire subnets, the IF ports or line ports are deleted from the orderwire ports through the NMS. The information about orderwire ports of each NE is provided in Table 12-9.
Table 12-9 Information about orderwire ports NE NE1 Orderwire Port 3-IFU2-1 5-IFU2-1 NE2 3-IFU2-1 5-IFU2-1 F1 NE3 3-IFU2-1 4-IFU2-1 F1 NE4 NE5 3-IFU2-1 3-IFU2-1 4-IFU2-1 NE6 3-IFU2-1
NOTE
l An external clock port can also be used to realize service spanning between NE2 and NE3. In this case, the external clock port needs to be added to the orderwire port through the NMS. l Certain orderwire ports are unnecessary. These ports do not, however, affect the orderwire phones if they do not receive orderwire signaling.
Information About Orderwire Parameters

l Fewer than 30 NEs exist on the orderwire subnet. Hence, the call waiting time needs to be set to five seconds for these NEs.
12-12
Issue 03 (2011-04-10)
In this example, the SDH optical transmission equipment is not involved on the orderwire subnet. Therefore, the overhead byte is set to E1 by default.

Procedure
Step 1 See A.11.1 Configuring Orderwire and configure the orderwire. The values for the related parameters are provided as follows. Paramete r Call Waiting Time(s) Phone 1 Selected Orderwir e Port Value NE1 5 NE2 5 NE3 5 NE4 5 NE5 5 NE6 5
101 3-IFU2-1 5-IFU2-1
102 3-IFU2-1 5-IFU2-1 F1
103 3-IFU2-1 4-IFU2-1 F1
104 3-IFU2-1
105 3-IFU2-1 4-IFU2-1
106 3-IFU2-1
----End
12.5 Configuration Example (Synchronous Data Services)

This section considers a synchronous data service that transmits the network management information as an example to describe how to configure a synchronous data service according to the network planning information. 12.5.1 Networking Diagram This section describes the networking information about the NEs. 12.5.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 12.5.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 12-5, the radio network transmits the network management messages of the third-party equipment. The third-party equipment and the NMS use the protocol converter to convert the network management messages carried by the Ethernet network into the network management messages carried by the 64 kbit/s synchronous data
service. Hence, the radio network needs to transparently transmit the corresponding synchronous data only. l l NE1 and NE6 add or drop 64 kbit/s synchronous data services. NE2, NE3, and NE5 pass through 64 kbit/s synchronous data services. Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all the other radio links are configured with 1+0 non-protection.
Figure 12-5 Networking diagram (synchronous data services)

3rd party NM 1+0 1+1 3rd party equipment NE4 1+0 ETH 1+0 64kbps NE6 NE5 NE3 NE2 NE1 64k/ETH Converter E1 64kbps ETH
64k/ETH Converter
Table 12-10 Connections of synchronous data services (NE1) Link Between NE1 and a protocol converter Between NE1 and NE2 Port F1 3-IFU2 (main IF board of a 1 +1 protection group) Description Configure this port to access synchronous data services. Configure the main IF board to transmit synchronous data services.
Table 12-11 Connections of synchronous data services (NE2) Link Between NE2 and NE1 Port 3-IFU2 (main IF board of a 1 +1 protection group) F1 Description Configure the main IF board to transmit synchronous data services. The two NEs are interconnected through synchronous data ports.
Between NE2 and NE3
12-14
Issue 03 (2011-04-10)
Table 12-12 Connections of synchronous data services (NE3) Link Between NE3 and NE5 Port 4-IFU2 Description Configure this port to transmit synchronous data services. The two NEs are interconnected through synchronous data ports.
Between NE3 and NE2
F1
Table 12-13 Connections of synchronous data services (NE5) Link Between NE5 and NE3 Port 4-IFU2 Description Configure this port to transmit synchronous data services. Configure this port to transmit synchronous data services.
Between NE5 and NE6
3-IFU2
Table 12-14 Connections of synchronous data services (NE6) Link Between NE6 and NE5 Port 3-IFU2 Description Configure this port to transmit synchronous data services. Configure this port to access synchronous data services.
Between NE6 and a protocol converter
F1

The service planning information contains the information about all the parameters required for configuring the NE data. l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line. Therefore, service spanning is required. The two synchronous data ports between NE2 and NE3 are interconnected with each other to realize the service spanning function. According to the service path, you can obtain the synchronous data service information provided in Table 12-15.
Issue 03 (2011-04-10)
12-15
Table 12-15 Information about the synchronous data service NE NE1 NE2 NE3 NE5 NE6 Data Channel 1 F1 3-IFU2-1 F1 4-IFU2-1 3-IFU2-1 Data Channel 2 3-IFU2-1 F1 4-IFU2-1 3-IFU2-1 F1
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3. l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active link is configured with the synchronous data service.

Procedure
Step 1 See A.11.2 Configuring the Synchronous Data Service and configure the synchronous data services. The values for the related parameters are provided as follows. Parameter Value NE1 Data Channel 1 Data Channel 2 F1 3-IFU2-1 NE2 3-IFU2-1 F1 NE3 F1 4-IFU2-1 NE5 4-IFU2-1 3-IFU2-1 NE6 3-IFU2-1 F1
----End
12.6 Configuration Example (Asynchronous Data Services)

This section considers an asynchronous data service that transmits the NM messages as an example to describe how to configure an asynchronous data service according to the network planning information. 12.6.1 Networking Diagram This section describes the networking information about the NEs. 12.6.2 Service Planning
The service planning information contains the information about all the parameters required for configuring the NE data. 12.6.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 12-6, the radio network transmits the network management information of the third-party equipment. The third-party equipment and the NMS use the protocol converter to convert the network management information carried by the Ethernet network into the network management information carried by the RS-232 synchronous data service. Hence, the radio network needs to transparently transmit the corresponding synchronous data only. l l NE1 and NE6 add or drop asynchronous data services. NE2, NE3, and NE5 pass through asynchronous data services. Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all the other radio links are configured with 1+0 non-protection.
Figure 12-6 Networking diagram (asynchronous data services)

3rd party NM 1+0 1+1 3rd party equipment NE4 1+0 ETH 1+0 RS-232 NE6 NE5 NE3 NE2 NE1 RS-232/ETH Converter E1 RS-232 ETH
RS-232/ETH Converter
Table 12-16 Connections of asynchronous data services (NE1) Link Between NE1 and a protocol converter Between NE1 and NE2 Port SERIAL1 3-IFU2 (main IF board of a 1 +1 protection group) Description Configure this port to access asynchronous data services. Configure the main IF board to transmit asynchronous data services.
Issue 03 (2011-04-10)
12-17
Table 12-17 Connections of asynchronous data services (NE2) Link Between NE2 and NE1 Port 3-IFU2 (main IF board of a 1 +1 protection group) SERIAL1 Description Configure the main IF board to transmit asynchronous data services. The two NEs are interconnected through asynchronous data ports.
Between NE2 and NE3
Table 12-18 Connections of asynchronous data services (NE3) Link Between NE3 and NE5 Port 4-IFU2 Description Configure this port to transmit asynchronous data services. The two NEs are interconnected through asynchronous data ports.
Between NE3 and NE2
SERIAL1
Table 12-19 Connections of asynchronous data services (NE5) Link Between NE5 and NE3 Port 4-IFU2 Description Configure this port to transmit asynchronous data services. Configure this port to transmit asynchronous data services.
Between NE5 and NE6
3-IFU2
Table 12-20 Connections of asynchronous data services (NE6) Link Between NE6 and NE5 Port 3-IFU2 Description Configure this port to transmit asynchronous data services. Configure this port to access asynchronous data services.
Between NE6 and a protocol converter
SERIAL1
12-18
Issue 03 (2011-04-10)

The service planning information contains the information about all the parameters required for configuring the NE data. l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line. Therefore, service spanning is required. The two asynchronous data ports between NE2 and NE3 are interconnected with each other to realize the service spanning function. In this example, the SDH equipment is not required to jointly transmit the asynchronous data service. Hence, the overhead byte is set to SERIAL1. According to the service path, you can obtain the asynchronous data service information provided in Table 12-21. Table 12-21 Information about the asynchronous data service NE NE1 NE2 NE3 NE5 NE6 Broadcast Data Source SERIAL1 3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1 Broadcast Data Sink 3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1 SERIAL1
l l
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3. l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active link is configured with the asynchronous data service.

Procedure
Step 1 See A.11.3 Configuring the Asynchronous Data Service and configure the asynchronous data services. The values for the related parameters are provided as follows. Parameter Value NE1 Overhead Byte Broadcast Data Source
Issue 03 (2011-04-10)
NE2 SERIAL1 3-IFU2-1
NE3 SERIAL1 SERIAL1
SERIAL1 SERIAL1
12-19
Parameter
Value NE1 NE2 SERIAL1 NE3 4-IFU2-1 NE5 3-IFU2-1 NE6 SERIAL1
Selected Broadcast Data Sink
3-IFU2-1
----End
12.7 Configuration Example (Wayside E1 Services)

This section considers a wayside E1 service that transmits the NM messages as an example to describe how to configure a wayside E1 service according to the network planning. 12.7.1 Networking Diagram This section describes the networking information about the NEs. 12.7.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 12.7.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. In the networking shown in Figure 12-7, the STM-1 radio network transmits the network management information of the third-party equipment. The third-party equipment and the NMS use the protocol converter to convert the network management information carried by the Ethernet network into the network management information carried by the wayside E1 service. To maximize the bandwidth utilization, the NEs transmit the service over the wayside E1 channel. Figure 12-7 Networking diagram (wayside E1 services)
3rd party equipment 3-IF1 to NE1 ETH E1 NE2 STM-1 NE1 3-IF1 to NE2 E1 ETH 3rd party NM
E1/ETH Converter
E1/ETH Converter
12-20
Issue 03 (2011-04-10)

The service planning information contains the information about all the parameters required for configuring the NE data. According to the service path, you can obtain the wayside E1 service information provided in Table 12-22. Table 12-22 Information about wayside E1 services NE IF Board Whether to Enable the Wayside E1 Service Enabled Enabled Input Slot of the Wayside E1 Service 7 7
NE1 NE2
3-IF1 3-IF1
NOTE
In the case of radio links configured with 1+1 or N+1 protection, only the active link is configured with the wayside E1 service.

Procedure
Step 1 See A.11.4 Configuring the Wayside E1 Service and configure the wayside E1 service. The values for the related parameters are provided as follows. Parameter Value NE1 Port 2M Wayside Enable Status 2M Wayside Input Board NE1-3-IF1-1 Enabled 7 NE2 NE2-3-IF1-1 Enabled 7
----End
12.8 Configuration Example (External Alarms)

This section considers the centralized control of environment monitoring and equipment alarms through external alarms as an example to describe how to configure external alarms according to the network planning information. 12.8.1 Networking Diagram
This section describes the networking information about the NEs. 12.8.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 12.8.3 Configuration Process This section describes the procedures for the data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 12-8, the external alarms on NE1 are required as follows: l l l External alarm input port 1 is used for connecting the alarm port on the smoke sensor. When the alarm port on the smoke sensor is closed, NE1 should report a fire alarm. External alarm input port 2 is used for connecting the alarm port on the water sensor. When the alarm port on the water sensor is closed, NE1 should report a water alarm. External alarm input port 3 is used for connecting the alarm port on the magnetic door switch sensor. When the alarm port on the magnetic door switch sensor is closed, NE1 should report an alarm, indicating that the cabinet door is open. External alarm output port 1 is used for connecting the centralized alarming boxes. When a major or critical alarm is generated on NE1, the alarm output port is closed.
Figure 12-8 Networking diagram (external alarms)

Input 1 Smoke sensor Input 2 NE1 Water sensor Input 3 Output 1 2-AUX
Magnetic door switch sensor
Centralized alarming box

Information About Input Alarms

According to the requirements, you can obtain the input alarm information provided in Table 12-23.
12-22
Issue 03 (2011-04-10)
Table 12-23 Information about input alarms Input External Alarm Interface 1 Alarm Name Fire alarm Usage Status Used Alarm Mode An alarm is generated when the port is closed. An alarm is generated when the port is closed. An alarm is generated when the port is closed. Severity Major
Interface 2
Water alarm
Used
Major
Interface 3
Open cabinet door
Used
Major
Information About Output Alarms

According to the requirements, you can obtain the output alarm information provided in Table 12-24. Table 12-24 Information about output alarms Output External Alarm Interface 1 Working Mode Automatic Mode
NOTE
The OptiX RTN 950 supports the automatic mode and the manual mode. The manual mode is used for commissioning the output alarms.

Procedure
Step 1 See A.11.5 Configure External Alarms and configure the external alarms. l The values for the input alarm parameters are provided as follows. Parameter Value NE1 Operation Object
Issue 03 (2011-04-10)
NE1-AUX-1
NE1-AUX-2
NE1-AUX-3
12-23
Parameter
Value NE1
Path Name Using Status Alarm Mode Alarm Severity
Fire alarm Used Relay Turns On/ Low Level Major Alarm
Water alarm Used Relay Turns On/ Low Level Major Alarm
Open cabinet door Used Relay Turns On/ Low Level Major Alarm
l The values for the output alarm parameters are provided as follows. Parameter Value NE1 Operation Object Use or Not NE1-AUX-1 Used
----End
12.9 Configuration Example (Monitoring the Outdoor Cabinet)

This chapter describes the process of configuring the temperature and humidity thresholds for the PMU of the outdoor cabinet. This example helps you understand how to configure the function of monitoring the outdoor cabinet according to the network planning information. 12.9.1 Network Diagram The section describes the networking information about the NEs. 12.9.2 Service Planning The service planning information contains the information about all the parameters required for configuring thresholds for temperature and humidity alarms of the PMU in the outdoor cabinet. 12.9.3 Configuration Process This section describes how to configure the temperature and humidity alarm thresholds for the power monitoring unit (PMU) of an APM30 alternating current (AC) cabinet. In this example, all configuration operations are performed on NE1.
12.9.1 Network Diagram

The section describes the networking information about the NEs. In this example, the OptiX RTN 950 is installed in an APM30 AC cabinet. As shown in Figure 12-9, the TOD2 port (CSH) on the OptiX RTN 950 (NE1) is connected to the COM_IN port on the APM30 AC cabinet. The OptiX RTN 950 supports the function of monitoring the PMU temperature and humidity information after the upper and lower thresholds for temperature and humidity alarms of the PMU are configured.
Figure 12-9 Network diagram (outdoor cabinet)
PMU
COM_IN
IDU
TOD2

The service planning information contains the information about all the parameters required for configuring thresholds for temperature and humidity alarms of the PMU in the outdoor cabinet.
Setting Alarm Thresholds for the PMU

l In this example, the thresholds for the temperature and humidity alarms are configured on the consumption of long-time stable operation of the PMU. It is recommended that the parameters take their default values, unless otherwise specified. In this example, the alarm thresholds for the PMU are configured as described in Table 12-25.
Table 12-25 Alarm thresholds for the PMU Parameter Upper threshold for the ambient temperature (C) Lower threshold for the ambient temperature (C) Upper threshold for the ambient humidity (%) Lower threshold for the ambient humidity (%) Value 60 -5 95 5
Issue 03 (2011-04-10)
12-25

This section describes how to configure the temperature and humidity alarm thresholds for the power monitoring unit (PMU) of an APM30 alternating current (AC) cabinet. In this example, all configuration operations are performed on NE1.
Procedure
Step 1 Follow the instructions in A.11.6.1 Configuring the Function of an Auxiliary Port . The values for the related parameters are provided as follows. Parameter Value 7-CSH-2 Interface Mode MON
Step 2 Follow the instructions in A.11.6.2 Setting the Type of the Outdoor Cabinet. The values for the related parameters are provided as follows. Parameter Outdoor Cabinet Type Value APM30 AC
Step 3 Follow the instructions in A.1.1.4 Configuring the Logical Board. Add the PMU logical board to slot 14 and the TCU logical boards to slots 15 and 16 on the Slot Layout. Step 4 Follow the instructions in A.11.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU. The values for the ambient temperature and humidity parameters are provided as follows. Parameter NE1-14-PMU Ambient Temperature ( C) Upper threshold Lower threshold 60 -5 Ambient Humidity (%) 95 5
----End
12-26
Issue 03 (2011-04-10)
13 Adding and Modifying Configuration Data
13
Adding and Modifying Configuration Data
About This Chapter

During the equipment commissioning and operating phases, you need to add or modify certain configuration data according to the actual requirements. 13.1 Common Task Collection (NEs) Common tasks associated with NEs include common configuration tasks associated with NE attributes. 13.2 Common Task Collection (Radio Links) This section describes the common configuration tasks associated with radio links. 13.3 Common Task Collection (TDM Services) This section describes the common configuration tasks associated with TDM services. 13.4 Common Task Collection (Packet-Plane Ethernet Services) This section describes the common configuration tasks associated with packet-plane Ethernet services. 13.5 Task Collection (EoPDH-Plane Ethernet Services) This section describes the common configuration tasks associated with EoPDH-plane Ethernet services.
Issue 03 (2011-04-10)
13-1
13.1 Common Task Collection (NEs)

Common tasks associated with NEs include common configuration tasks associated with NE attributes. Table 13-1 Common task collection (NE attributes) Task Creating NEs Application Scenario When using the NMS to perform centralized management of NEs, add the target NEs into the NE list. Configuration Operation A.1.1.1 Creating NEs by Using the Search Method or A.1.1.2 Creating NEs by Using the Manual Method Description l Generally, NEs are created by searching for the NE on the NMS. l The manual NE creation method is applicable only when several NEs need to be created on a large radio transmission network. -
Changing an NE ID
You need to change an NE ID, if the NE ID does not meet the network planning requirements (for example, if the NE ID is the same as another NE ID). You need to change the IP address of the gateway NE if changes occur in the external DCN between the NMS server and the gateway NE. After you conduct the settings on the NMS, the NE time is synchronized automatically and periodically. You can also synchronize the NE time manually if the NE time is lost due to NE faults.
A.1.1.5 Changing the NE ID
Changing the IP address of an NE
Changing the IP address of an NE
Synchronizing NE time
A.1.1.7 Synchronizing the NE Time
To ensure that the NE time is synchronized correctly, the time and time domain of the NMS server must be set correctly.
13-2
Issue 03 (2011-04-10)
13.2 Common Task Collection (Radio Links)

This section describes the common configuration tasks associated with radio links.
CAUTION
When you add or modify the configurations of a radio link, you need to modify the configurations of the NE that is located far from the NMS server and then modify the configurations of the NE that is located near to the NMS server.
NOTE
l In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio link. l In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the ODU information of the standby radio link. l In the case of XPIC configuration, you need to configure the IF/ODU information of the two radio links in different polarization directions separately. l In the case of N+1 protection, you need to configure the IF/ODU information of the N+1 radio links respectively. l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, STM-1 count, or modulation mode is set inconsistently for both ends of a Integrated IP radio link. This alarm should be cleared immediately. Otherwise, services may be configured unsuccessfully or interrupted.
Table 13-2 Common task collection (radio links) Task Changing the radio working mode of a TDM radio link Application Scenario You need to change the radio working mode of a TDM radio link, if the TDM radio link does not meet the service capacity requirements. Configuration Operation 1. A.4.6 Deleting CrossConnections Description If the capacity of the existing TDM services exceeds the capacity of the TDM radio link after the change, you need to delete the crossconnections of the excessive TDM services. Before you change the radio working mode, it is recommended that you consult the network planning department to check whether the radio link supports the new radio working mode.
13-3
2. A.2.4 Configuring the IF/ODU Information of a Radio Link
Issue 03 (2011-04-10)
Task Configuring the ATPC function
Application Scenario The ATPC function needs to be enabled for the radio link or the values of ATPC parameters need to be changed.
Configuration Operation A.5.8.2 Configuring the ATPC Attributes
Description To enable the ATPC function, set ATPC Enable Status to Enabled and change other ATPC parameter values according to the planning information. In Power Attributes of the ODU, change TX Power(dBm) or parameter values associated with power. In the case of IF 1+1 protection, the original IF board functions as the main IF board. Ensure that TX Status of the standby ODU is Unmute. l Before using the new modulation scheme, contact the network planning department to confirm that the Hybrid radio link supports the new Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity. l Ensure that the parameter values are the same at both ends of the Hybrid radio link.
Changing the transmit power
You can change the transmit power if the fading margin is insufficient but the transmit power can still be increased. To improve reliability of a 1+0 radio link, upgrade the 1+0 radio link to a 1+1 HSB/SD/ FD radio link.
Upgrading a 1 +0 radio link to a 1+1 HSB/SD/ FD radio link
1.A.2.1 Creating an IF 1+1 Protection Group
2.A.2.4 Configuring the IF/ODU Information of a Radio Link Changing the modulation scheme of a Hybrid radio link When the original modulation scheme does not meet the service requirements, you need to use another modulation scheme. A.5.8.6 Modifying the Hybrid/AM Attributes
13-4
Issue 03 (2011-04-10)
Task Changing the number of E1s on a Hybrid radio link
Application Scenario To adjust the number of E1s and Ethernet bandwidth, you need to change the number of E1s on the Hybrid radio link.
Configuration Operation A.5.8.6 Modifying the Hybrid/AM Attributes
Description l To reduce E1s with high priorities, you need to delete the corresponding cross-connections before changing Guarantee E1 Capacity. The change does not affect other E1 services or cause Ethernet service interruptions. l To increase E1s with high priorities, you need to add the corresponding cross-connections after changing Guarantee E1 Capacity. The change does not affect other E1 services or cause Ethernet service interruptions.
NOTE The number of added E1s should be within the specified range.
l To reduce E1s with low priorities, you need to delete the corresponding cross-connections before changing Full E1 Capacity. The change does not affect other E1 services or cause Ethernet service interruptions. l To increase E1s with low
Issue 03 (2011-04-10)
13-5
Task
Application Scenario
Configuration Operation
Description priorities, you need to add the corresponding cross-connections after changing Full E1 Capacity. The change does not affect other E1 services or cause Ethernet service interruptions.
NOTE The number of added E1s should be within the specified range.
l The MW_CFG_MIS MATCH alarm occurs when the number of E1 services is different on both ends of the radio link. The alarm clears when the number of E1 services is the same on both ends of the radio link.
13-6
Issue 03 (2011-04-10)
Task Changing the priority of E1 services on a Hybrid radio link
Application Scenario You can change the priority of E1 services on a Hybrid radio link.
Configuration Operation A.4.3 Modifying the Priorities of E1 Services
Description l When you change the priority of an E1, the E1 is interrupted transiently. l If the number of E1s with high priorities exceeds the value of Modulation Mode of the Guarantee AM Capacity, you need to increase the value of Modulation Mode of the Guarantee AM Capacity before changing the priorities.
13.3 Common Task Collection (TDM Services)

This section describes the common configuration tasks associated with TDM services. Table 13-3 Common task collection (TDM services) Task Adding TDM services Application Scenario More TDM services need to be accessed on the network. Configuration Operation A.4.1 Creating the Cross-Connections of Point-to-Point Services or A.4.2 Creating Cross-Connections of SNCP Services A.4.6 Deleting CrossConnections Description -
Deleting TDM services
If the line resources are insufficient, you need to delete the TDM services that are not used to release the corresponding resources.
Issue 03 (2011-04-10)
13-7
Task Upgrading an unprotected link to a linear MSP link
Application Scenario Upgrade an unprotected link to a linear MSP link to improve service reliability.
Configuration Operation A.3.1 Configuring Linear MSP
Description In the case of linear MSP, the existing line port functions as the working port. Upgrading an unprotected link to a linear MSP link does not interrupt the existing services. Only the normal services in the receive direction are converted to SNCP services. Therefore, you need to configure the unidirectional cross-connections from the SNCP services to the working trail and from the SNCP services to the protection trail so that the normal services both in the receive direction and in the transmit direction are converted to SNCP services.
Upgrading normal services to SNCP services
Upgrade normal services to SNCP services to improve service reliability.
A.4.7 Converting a Normal Service into an SNCP Service
13.4 Common Task Collection (Packet-Plane Ethernet Services)

This section describes the common configuration tasks associated with packet-plane Ethernet services. Table 13-4 Common task collection (Packet-plane Ethernet services) Task Creating Ethernet services Application Scenario Create the Ethernet services according to the service planning information. Configuration Operation 7 Configuring Native Ethernet Services on the Packet Plane Description -
13-8
Issue 03 (2011-04-10)
Task Setting or modifying the parameters of Ethernet ports
Application Scenario The service requirements or configuration at the opposite end change. As a result, the parameters of the Ethernet port need to be changed. Delete the Ethernet services that are not used to release the corresponding resources. l When the available bandwidth is insufficient, you can create a LAG to increase the bandwidth. l To improve link reliability, you can bind the links into a LAG.
Configuration Operation A.5.6 Setting the Parameters of Ethernet Ports
Description -
Deleting Ethernet services
A.6.3.12 Deleting an E-Line Service or A.6.3.13 Deleting E-LAN Services
Creating a LAG
A.6.2.1 Creating a LAG
l When using the LAG, set the port that is configured with services to the main port. l This operation briefly interrupts the existing services.
Changing logical ports connected to an E-LAN
The E-LAN service requirements change. As a result, the logical ports connected to the E-LAN need to be changed.
A.6.3.11 Changing Logical Ports Connected to a VB
You need to add or delete a logical port connected to an E-LAN, or modify attributes associated with a logical port connected to the E-LAN according to the actual planning information.
Issue 03 (2011-04-10)
13-9
Task Managing the MAC address table
Application Scenario l To disable certain MAC address hosts to use E-LAN services, you need to create MAC address blacklist entries. l To prevent certain MAC address entries from being aged, you need to create static MAC address entries. l To disable the aging function or modify the default aging time (five minutes), you need to set the aging parameters of corresponding MAC addresses.
Configuration Operation A.6.4 Managing the MAC Address Table
Description -
Adjusting QoS
The service requirements change. As a result, QoS needs to be adjusted.
A.6.7 Managing the QoS
Change the values of QoS parameters to ensure that the QoS control adapts to the changes in the service requirements.
13.5 Task Collection (EoPDH-Plane Ethernet Services)

This section describes the common configuration tasks associated with EoPDH-plane Ethernet services. Table 13-5 Task Collection (EoPDH-plane Ethernet services) Task Creating Ethernet services Application Scenario Create the Ethernet services according to the service planning information. Configuration Operation 8 Configuring EoPDH-Based Ethernet Services Remarks -
13-10
Issue 03 (2011-04-10)
Task Setting or modifying the parameters of Ethernet ports
Application Scenario The service requirements or configuration at the opposite end change. As a result, the parameters of the Ethernet port need to be changed. Delete the Ethernet services that are not used to release the corresponding resources. l When the available bandwidth is insufficient, you can create a LAG to increase the bandwidth. l To improve link reliability, you can bind the links into a LAG.
Configuration Operation A.7.4 Configuring Ethernet Ports
Remarks -
Deleting Ethernet services
A.7.2.7 Deleting an Ethernet Private Line Service or A. 7.2.8 Deleting an Ethernet LAN Service A.7.1 Managing LAGs
Creating a LAG
l When using the LAG, set the port that is configured with services to the main port. l This operation briefly interrupts the existing services.
Changing logical ports connected to a VB
The Ethernet LAN service requirements change. As a result, the logical ports connected to the VB need to be changed.
You need to add or delete the logical port connected to a VB, or modify attributes associated with the logical port connected to the VB according to the actual planning information.
Issue 03 (2011-04-10)
13-11
Task Managing the MAC address table
Application Scenario l To disable certain MAC address hosts to use Ethernet LAN services, you need to create MAC address blacklist entries. l To prevent certain MAC address entries from being aged, you need to create static MAC address entries. l To disable the aging function or modify the default aging time (five minutes), you need to set the aging parameters of corresponding MAC addresses.
Configuration Operation A.7.3 Managing the MAC Address Table
Remarks -
Adjusting QoS
The service requirements change. As a result, QoS needs to be adjusted.
Change the values of QoS parameters to ensure that the QoS control adapts to the changes in the service requirements.
13-12
Issue 03 (2011-04-10)
A Task Collection
A
A.3 Managing the MSP The OptiX RTN 950 supports the linear MSP.
Task Collection
This document describes various tasks involved in this document. A.1 Network Management Network management involves topology management, communication management, and security management. A.2 Managing Radio Links Before you configure the radio link between two microwave sites, you need to configure the corresponding information about the radio link.
A.4 Managing TDM Services The TDM services involve the SDH service and the PDH service. A.5 Managing Ports Correct parameter settings of ports are the basis of configuring ports that transmit services. A.6 Configuring Ethernet Services and Features on the Packet Plane Configurations of Ethernet services and features on the packet plane include Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.7 Configuring Ethernet Services and Features on the EoPDH Plane Configurations of Ethernet services and features on the EoPDH plane include relevant Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.8 Managing MPLS/PWE3 Services and Features The OptiX RTN 950 supports multiple MPLS/PWE3 services and features. A.9 Managing the Clock To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.10 Using the RMON The remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.11 Configuring Auxiliary Ports and Functions
Issue 03 (2011-04-10)
A-1
A Task Collection
The auxiliary ports and functions supported by the OptiX RTN 950 include the orderwire, synchronous data service, asynchronous data service, wayside E1 service, external alarm and monitoring the outdoor cabinet. A.12 Verifying Services and Features This topic describes how to verify service and feature configurations.
A-2
Issue 03 (2011-04-10)
A Task Collection
A.1 Network Management

Network management involves topology management, communication management, and security management. A.1.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.2 Configuring the Performance Monitoring Status of NEs By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually. A.1.3 Suppressing Alarms for Monitored Objects This topic describes how to suppress certain alarms for a specific monitored object. A.1.4 Managing Communications To manage the NE by the NMS, ensure that the DCN communication is normal. A.1.5 Configuring Service Access of NEs You can ensure the security of a network by setting service access of the NEs on the network. A.1.6 Configuring an NE User NE users refer to the users who log in to and operate NEs. Different types of NE users are assigned different rights to log in and manage NEs.
A.1.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.1.1 Creating NEs by Using the Search Method The Web LCT can find all NEs that communicate with a specific gateway NE by using the IP address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition, the Web LCT can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable. A.1.1.2 Creating NEs by Using the Manual Method You can only create NEs one by one by using the manual method. The manual method, unlike the search method, does not allow creating NEs in batches. A.1.1.3 Logging In to an NE After an NE is created, you need to log in to the NE before managing the NE. A.1.1.4 Configuring the Logical Board If the logical board corresponding to the physical board is not added in the slot layout, add the logical board in the slot layout. If the physical board is inconsistent with the logical board in the slot layout, delete the inconsistent logical board and add the correct logical board. A.1.1.5 Changing the NE ID Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique. Modifying the NE ID does not interrupt services. A.1.1.6 Changing the NE Name To better identify the NE, name the NE according to the NE geographical location or the device connected to the NE.
Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-3
A Task Collection
A.1.1.7 Synchronizing the NE Time By setting the NE time to be synchronous with the time on the NMS or standard NTP server, you can record the exact time when alarms and abnormal events occur. A.1.1.8 Localizing the NE Time When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE time with the local time.
A.1.1.1 Creating NEs by Using the Search Method

The Web LCT can find all NEs that communicate with a specific gateway NE by using the IP address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition, the Web LCT can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable.
Prerequisite
l l The communication between the NMS and the NE must be normal. The NE user must have the authority of Operation Level or higher.
Tools, Equipment, and Materials

Web LCT
Procedure
Step 1 In NE List, click NE Search. Then, the Search NE dialog box is displayed. Step 2 Select the search mode. Step 3 Optional: If Search Mode is set to Search NE, you need to set the network segment. 1. 2. 3. 4. Click Manage Domain. The Manage Domain Search dialog box is displayed. Optional: Click Add, and set Domain Type and Domain Address to add a network segment. Optional: Select an existing network segment, and click Modify to modify the network segment. Optional: Select an existing network segment, and click Delete to delete the network segment.
NOTE
During initial configuration, Domain is 129.9.255.255 by default. After the gateway NE IP address of the searched NE is changed, you need to change the value of Domain. The default network segment cannot be modified and deleted.
Step 4 Click Search. Step 5 After the Web LCT finds the NEs to be managed, click End Search.
A-4
Issue 03 (2011-04-10)
A Task Collection
Step 6 Select the NE that needs to be added and click Add NE. A dialog box is displayed, indicating that the NE is added successfully. Step 7 Click OK. A new NE is already added to the NE list.
Step 8 Click Cancel. ----End
Related References
B.1.1.1 Parameter Description: NE Searching
A.1.1.2 Creating NEs by Using the Manual Method

You can only create NEs one by one by using the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The communication between the NMS and the NE to be created must be normal. If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be created belongs must be created.
Procedure
Step 1 In NE List, click Add NE. Then, select Europe. Then, the Add NE dialog box is displayed. Step 2 In the Add NE dialog box, set the NE parameters.
A Task Collection
NOTE
l The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS. l ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the networks that are managed by the same NMS. l Do not change the Extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID. l Set the parameters according to the network planning information.
Step 3 Click OK. A new NE is already added to the NE list. ----End
Related References
B.1.1.2 Parameter Description: NE Creation
A.1.1.3 Logging In to an NE
After an NE is created, you need to log in to the NE before managing the NE.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The NE to be managed is already created in NE List.

Web LCT
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
TIP
You can select multiple NEs at one time.
The NE Login dialog box is displayed.

A-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
A Task Collection
Step 2 Enter User Name and Password. Then, click OK.
NOTE
l The default User Name is lct. l The default Password for user lct is password.
Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is changed from Unknown to the current alarm status of the NE. Step 3 Click NE Explorer. The NE Explorer is displayed.
TIP
To quickly start the NE Explorer, double-click the NE to be managed in the NE list.

TIP
l Check the legend to learn the specific meanings of different colors and symbols in the slot layout diagram. l Click to collapse/expand the legend.
----End
Related References
B.1.1.3 Parameter Description: Login to an NE
A.1.1.4 Configuring the Logical Board

If the logical board corresponding to the physical board is not added in the slot layout, add the logical board in the slot layout. If the physical board is inconsistent with the logical board in the slot layout, delete the inconsistent logical board and add the correct logical board.
Prerequisite
l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. All the boards must be installed correctly.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-7
A Task Collection

Web LCT
Procedure
Step 1 Click the Slot Layout tab and click Add Physical Boards. Based on the slot layout, the NE automatically configures the logical boards that are required but still not be configured for certain physical boards. Step 2 Optional: On the slot to which the board is to be added, right-click, and then select Add XXX. XXX is the name of the board to be added. Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then select Delete.
NOTE
Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on the board.
----End

Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique. Modifying the NE ID does not interrupt services.
Prerequisite
The NE user must have the authority of Operation Level or higher.

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID. The Modify NE ID dialog box is displayed. Step 3 Specify New ID and New Extended ID.
Step 4 Click OK. A dialog box is displayed for confirmation, click OK. Step 5 Click OK. ----End
Related References
B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs
A.1.1.6 Changing the NE Name

To better identify the NE, name the NE according to the NE geographical location or the device connected to the NE.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Attribute from the Function Tree. Step 2 Enter the name of the NE in Name.
NOTE
The name of an NE cannot contain any space characters.
Issue 03 (2011-04-10)
A-9
A Task Collection
Step 3 Click Apply. ----End

By setting the NE time to be synchronous with the time on the NMS or standard NTP server, you can record the exact time when alarms and abnormal events occur.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. When you need to synchronize the NE time with the time on the NMS server, the time zone and time must be set correctly on the PC or server that is installed with the NMS software. When you need to synchronize the NE time with the time on the NTP server, the time on the NTP server must be set correctly and the NTP protocol must be normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Synchronization from the Function Tree. Step 2 Set the synchronous mode. If... You set Synchronous Mode to NULL You set Synchronous Mode to NM Then... Set the relevant parameters, and then click Apply. Set the relevant parameters, and then click Apply to perform step Step 5.
You set Synchronous Mode to Standard NTP Set the related parameters, and then click Apply to perform steps Step 3.
NOTE
A Task Collection
If you only need to synchronize the NE time and need not change the type of synchronization or parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize with NM Time.
Step 3 Configure the upper-layer standard NTP server of the NE. 1. 2. Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add. After setting the parameters of the standard NTP server, click OK.
NOTE
l If the NE is a GNE, set the external NTP server as the standard NTP server. l If the NE is a non-GNE, set the GNE as the standard NTP server.
Step 4 Optional: Configure standard NTP keys. 1. 2. Click the Standard NTP Key Management tab. Click Add. The Add Key dialog box is displayed.
3.
After the related parameters are configured, click OK.
Step 5 Optional: Set Start Time and click Apply. ----End
Related References
B.1.1.5 Parameter Description: NE Time Synchronization
A.1.1.8 Localizing the NE Time

When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE time with the local time.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Localization Management from the Function Tree. Step 2 Set the correct time zone and daylight saving time of the NE depending on the location of the NE.
Related References
B.1.1.6 Parameter Description: Localization Management of the NE Time
A.1.2 Configuring the Performance Monitoring Status of NEs

By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE Performance Monitor Time from the Function Tree. Step 2 Configure the parameters of the performance monitoring of NEs. 1. 2. 3. Select 15-Minute or 24-Hour. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled. l You can specify the start time of the performance monitoring function, only after selecting Enabled in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area. l You can specify the end time of the performance monitoring function, only after selecting Enabled and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4.
Click Apply.
----End
A.1.3 Suppressing Alarms for Monitored Objects

This topic describes how to suppress certain alarms for a specific monitored object.
Prerequisite
The NE user must have the authority of Maintenance Level or higher.
Tools, Instruments and Materials

Web LCT
A Task Collection
Procedure
Step 1 In NE Explorer, select the required board. Step 2 Choose Alarm > Alarm Suppression. Step 3 Set Monitored Object and click Query. Step 4 Set Status in Alarm Suppression. Step 5 Click Apply. ----End
A.1.4 Managing Communications

To manage the NE by the NMS, ensure that the DCN communication is normal. A.1.4.1 Setting NE Communication Parameters The communication parameters of an NE include the IP address of the NE, the gateway IP address, and the subnet mask. A.1.4.2 Configuring DCCs To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the network planning information. A.1.4.3 Configuring Extended ECC Communication If there is no DCC between two or more NEs, you can connect the Ethernet NM ports or NE cascading ports on the system control boards of the NEs to achieve extended ECC communication. A.1.4.4 Configuring DCC Transparent Transmission The OptiX equipment supports the DCC transparent transmission function. With this function, the equipment can transparently transmit NM messages when the OptiX equipment is used together with other equipment to form a network and can also transparently transmit the NM messages between ECC subnets. A.1.4.5 Creating Static IP Routes When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually. A.1.4.6 Setting Parameters of the OSPF Protocol When the OptiX RTN equipment interconnects with third-party equipment, routing protocol communication is supported after you set OSPF protocol parameters of the OptiX RTN equipment based on related requirements of the third-party equipment. A.1.4.7 Enabling the ARP Proxy The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. A.1.4.8 Configuring the CLNS Role When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX RTN 950 is L1. A.1.4.9 Configuring the OSI Tunnel
A Task Collection
The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on the IP network. In this manner, the network management message encapsulated in compliance with the OSI protocol can be transparently transmitted. A.1.4.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN The VLAN ID used by an inband DCN must be different from the VLAN ID used by services and the bandwidth by an inband DCN must meet the requirements of the transmission network for managing messages. A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports The network management information can be transmitted over a link by the inband DCN only when the inband DCN function is enabled on the ports at both ends of the link. A.1.4.12 Configuring the Protocol Type of the Inband DCN The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol supported by the inband DCN. Generally, it is recommended that you use the default value. A.1.4.13 Querying ECC Routes By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal. A.1.4.14 Querying IP Routes By querying IP routes, you can check whether the IP over DCC solution and inband DCN solution is configured correctly and whether the communication between NEs is normal. A.1.4.15 Querying OSI Routes By querying OSI routes, you can check whether the OSI over DCC solution is configured correctly and whether the communication between NEs is normal. A.1.4.16 Configuring Access Control When the equipment is connected to the NMS through an Ethernet service port, you need to configure access control.
A.1.4.1 Setting NE Communication Parameters

The communication parameters of an NE include the IP address of the NE, the gateway IP address, and the subnet mask.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree. Step 2 Configure the communication parameters of the NE. Step 3 Click Apply.
A Task Collection
NOTE
l When you configure multiple parameters, click Apply respectively. l For gateway NEs, Connection Mode is fixed to the default value Common + Security SSL.
----End
Related References
B.1.2.1 Parameter Description: NE Communication Parameter Setting
A.1.4.2 Configuring DCCs

To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the network planning information.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Rate Configuration tab. Step 3 Optional: Change the enable status of the DCC. 1. 2.
A-16
Double-click the cell in the Enabled/Disabled column to which the DCC corresponds. Select the required state from the drop-down list. Click Apply.
A Task Collection
Step 4 Optional: Change the protocol type of the DCC. 1. 2. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select the required protocol type from the drop-down list. Click Apply.
NOTE
l On the NMS interface, the first port on the system control, switching, and clock board (like 7CST-1) corresponds to its external clock port. l If the port is connected to the other ECC subnet, Enabled/Disabled is set to Disabled. l If the port is connected to a third-party network and does not exchange the network management information with other ports, Enabled/Disabled is set to Disabled. The values recommended for Protocol Type are as follows: l If the IP over DCC solution is adopted, Protocol Type is set to TCP/IP. l If the OSI over DCC solution is adopted, Protocol Type is set to OSI. l Default values are recommended in other scenarios.
Step 5 Optional: Create DCCs. 1. 2. Click Create. Then, the Create dialog box is displayed. Set the attributes of the DCC.
NOTE
The values recommended for Protocol Type are as follows: l If the IP over DCC solution is adopted, Protocol Type is set to TCP/IP. l If the OSI over DCC solution is adopted, Protocol Type is set to OSI. l Default values are recommended in other scenarios.
3.
Click OK.
----End
Related References
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration
A.1.4.3 Configuring Extended ECC Communication

If there is no DCC between two or more NEs, you can connect the Ethernet NM ports or NE cascading ports on the system control boards of the NEs to achieve extended ECC communication.
A Task Collection
Prerequisite

Web LCT
Context
The default extended ECC mode is Auto mode.
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the Function Tree. Step 2 Optional: You can disable the Auto mode function of the extended ECC.
1. 2.
Click Stop. A confirmation dialog box is displayed. Click OK.
Step 3 Optional: Set parameters for the extended ECC function in Specified mode at the server end. 1. 2. 3. 4. Set ECC Extended Mode to Specified mode. Set related parameters for the server end. Click Apply. A confirmation dialog box is displayed. Click OK.
Step 4 Set parameters for the extended ECC function in Specified mode at the client end. 1. 2. 3. 4. Set ECC Extended Mode to Specified mode. Set related parameters for the client end. Click Apply. A confirmation dialog box is displayed. Click OK.
Step 5 Enable the automatic extended ECC function.

NOTE
A Task Collection
Before enabling the automatic extended ECC function, you need to clear related parameters that are configured in Specified mode for the server end and client end.
1. 2. 3. 4. 5. 6. 7. 8.
Set ECC Extended Mode to Specified mode. To clear parameters configured for the server end, click Clear Server. A confirmation dialog box is displayed. Click OK. To clear parameters configured for the client end, click Clear Client. A confirmation dialog box is displayed. Click OK. Set ECC Extended Mode to Auto mode. Click Apply. A confirmation dialog box is displayed. Click OK.
----End
Related References
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
A.1.4.4 Configuring DCC Transparent Transmission

The OptiX equipment supports the DCC transparent transmission function. With this function, the equipment can transparently transmit NM messages when the OptiX equipment is used together with other equipment to form a network and can also transparently transmit the NM messages between ECC subnets.
Prerequisite
The NE user must have the authority of Operation Level or higher. The DCC bytes required by the transparent transmission function must not be used.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Transparent Transmission Management tab. Step 3 Click Create. Then, the Create DCC Trarnsparent Transmission Byte dialog box is displayed. Step 4 Set the parameters of the DCC transparent transmission byte.
A Task Collection
Step 5 Click OK. ----End
Related References
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management
A.1.4.5 Creating Static IP Routes

When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the IP Route Management tab. Step 3 Click New. Then, the Create an IP Route dialog box is displayed. Step 4 Set the parameters of the static IP route.
NOTE
The created static route has a lower priority than a dynamic route.

A Task Collection
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation
A.1.4.6 Setting Parameters of the OSPF Protocol

When the OptiX RTN equipment interconnects with third-party equipment, routing protocol communication is supported after you set OSPF protocol parameters of the OptiX RTN equipment based on related requirements of the third-party equipment.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the OSPF Parameter Settings tab. Step 3 Set the parameters of the OSPF protocol.
NOTE
Set the parameters according to the network planning information.
Issue 03 (2011-04-10)
A-21
A Task Collection
Step 4 Click Apply. Step 5 Optional: Set OSPF parameters for DCC channels. 1. 2. 3. Click the Port OSPF Parameter Settings tab. Set the OSPF parameters for DCC channels. Click Apply.
----End
Related References
B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
A.1.4.7 Enabling the ARP Proxy

The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the Proxy ARP tab. Step 3 Set the enable status of the proxy ARP.
NOTE
l The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE.
Related References
B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP
A-22
Issue 03 (2011-04-10)
A Task Collection
A.1.4.8 Configuring the CLNS Role

When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX RTN 950 is L1.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Step 2 Click the Network Layer Parameters tab. Step 3 Set the CLNS role of the NE.
NOTE
When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.
Step 4 Click Apply. The system displays the prompt. Step 5 Click Yes. ----End
Related References
B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter
A.1.4.9 Configuring the OSI Tunnel

The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on the IP network. In this manner, the network management message encapsulated in compliance with the OSI protocol can be transparently transmitted.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree.
A Task Collection
Step 2 Click the OSI Tunnel tab. Step 3 Click New. Then, the Create OSI Tunnel dialog box is displayed. Step 4 Set Remote IP Address and LAPD Actor.
Step 5 Click OK. Step 6 Configure the attributes of the OSI tunnel according to the network planning.
Related References
B.1.2.13 Parameter Description: OSI Management_OSI Tunnel
A.1.4.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN

The VLAN ID used by an inband DCN must be different from the VLAN ID used by services and the bandwidth by an inband DCN must meet the requirements of the transmission network for managing messages.
Prerequisite
The NE user must have the authority of System Level or higher.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Step 2 Click the Bandwidth Management tab. Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
NOTE
l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the Ethernet Board VLAN ID of the inband DCN can be changed manually. The same VLAN ID must be, however, is used on the network-wide inband DCN. l Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link. l IF Port Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the radio link.
Related References
B.1.2.14 Parameter Description: DCN Management_Bandwidth Management
A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports
The network management information can be transmitted over a link by the inband DCN only when the inband DCN function is enabled on the ports at both ends of the link.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Step 2 Click the Port Settings tab.
A Task Collection
Step 3 Select FE/GE. Step 4 Configure the enable status of the inband DCN function on ports.
NOTE
l Enabled Status specifies the enabling status of the port. l The network management information can be transmitted over the inband DCN when the DCN function is enabled for the ports at both ends of a link.
Step 5 Click Apply. Step 6 Select IF. Step 7 Configure the enable status of the inband DCN function on ports.
NOTE
l Enabled Status specifies the enabling status of the port. l The network management information can be transmitted over the inband DCN when the DCN function is enabled for the ports at both ends of a link.
Related References
B.1.2.15 Parameter Description: DCN Management_Port Setting
A.1.4.12 Configuring the Protocol Type of the Inband DCN

The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol supported by the inband DCN. Generally, it is recommended that you use the default value.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding board must be added to the Slot Layout.

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Communication > DCN Management from the Function Tree. Step 2 Click the Protocol Settings tab. Step 3 Set the protocol type of the inband DCN.
NOTE
l If the values of Protocol Type are different from each other, the equipment at both ends cannot be interconnected with each other. Therefore, Protocol Type must be set to the same value for the equipment at both ends of a link. l Set Protocol Type according to the network planning information. Generally, it is recommended that you set this parameter to IP.
Related References
B.1.2.16 Parameter Description: DCN Management_Protocol Setting
A.1.4.13 Querying ECC Routes

By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link Management List. ----End
Related References
B.1.2.5 Parameter Description: NE ECC Link Management
A Task Collection
A.1.4.14 Querying IP Routes

By querying IP routes, you can check whether the IP over DCC solution and inband DCN solution is configured correctly and whether the communication between NEs is normal.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the IP Route Management tab. Step 3 Click Query. Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with the planning information. ----End
Related References
B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management
A.1.4.15 Querying OSI Routes

By querying OSI routes, you can check whether the OSI over DCC solution is configured correctly and whether the communication between NEs is normal.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Step 2 Click the Routing Table tab. Step 3 Check whether the information in Link Adjacency Table meets the planning requirements. Step 4 Click the L1 Routing tab to check whether the information about the L1 routes is correct.
A Task Collection
Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct. ----End
Related References
B.1.2.12 Parameter Description: OSI Management_Routing Table
A.1.4.16 Configuring Access Control

When the equipment is connected to the NMS through an Ethernet service port, you need to configure access control.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > DCN Management from the Function Tree. Step 2 Click the Access Control tab. Step 3 Set the parameters for configuring access control.
NOTE
l If the Enabled Status is set to Enabled, this port can be used to support access of the management information from the NMS. l If the Enabled Status is set to Disabled, this port cannot be used to support access of the management information from the NMS.
Related References
B.1.2.17 Parameter Description: DCN Management_Access Control
A.1.5 Configuring Service Access of NEs

You can ensure the security of a network by setting service access of the NEs on the network.
A Task Collection
A.1.5.1 Configuring LCT Access to NEs When an NE is managed by the NMS, LCT access to the NE can be configured if required. A.1.5.2 Configuring Ethernet Access to NEs By default, the NMS can access an NE by using Ethernet ports. A.1.5.3 Configuring Serial Port Access to NEs By default, the NMS can access an NE through serial ports.
A.1.5.1 Configuring LCT Access to NEs

When an NE is managed by the NMS, LCT access to the NE can be configured if required.
Prerequisite

Web LCT
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE determines whether to permit the login of the LCT according to the status of LCT Access Control Switch. If the LCT requests to log in to an NE to which the NMS has not logged in, the NE permits the login of the LCT regardless of the status of LCT Access Control Switch. The NMS, however, can log in to an NE to which the LCT has logged in. That is, the login of the LCT does not affect the login of the NMS. After the NMS user logs in to the NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is set to Disable Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT Access Control from the Function Tree. Step 2 Click Access Allowed to enable the LCT access function.
NOTE
To disable the LCT access function, click Disable Access.
----End
A.1.5.2 Configuring Ethernet Access to NEs

By default, the NMS can access an NE by using Ethernet ports.
Prerequisite
A Task Collection

Web LCT
Background Information
l l It is recommended that the LCT accesses an NE through Ethernet ports. If you need to initialize an NE or perform software loading by using the LCT, the LCT needs to access the NE through Ethernet ports.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Set the status of the network port to Enabled and enable the Ethernet access function of the NE.
NOTE
To disable the Ethernet access function of an NE, set the status of the network port to Disabled.
Step 3 Click Apply. Then, a confirmation dialog box is displayed. Step 4 Click OK. Then, close the operation result dialog box that is displayed. ----End
A.1.5.3 Configuring Serial Port Access to NEs

By default, the NMS can access an NE through serial ports.
Prerequisite

Web LCT
Context
If the LCT cannot access an NE through serial ports when the Enable Serial Port Access check box is selected, the LCT access function may be disabled.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Select the Enable Serial Port Access check box and select Access NM. Step 3 Click Apply. and then close the displayed prompt dialog box.
A Task Collection
Step 4 Optional: Select the baud rate of the serial port from the Baud Rate drop-down list. Click Apply, and then close the displayed prompt dialog box. ----End
A.1.6 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are assigned different rights to log in and manage NEs. A.1.6.1 Creating an NE User Based on the operation rights, NE users are divided into five levels, which involve monitoring level, operation level, maintenance level, system level, and debugging level in an ascending order. Different levels of NE users can be created as required. A.1.6.2 Changing the Password of an NE User Periodically changing the password of an NE user ensures the NE security. A.1.6.3 Setting Warning Screen Parameters This topic describes how to enable the warning screen function. When a user logs in to an NE, the NMS can display some information to the user. The displayed information can be selfdefined.
A.1.6.1 Creating an NE User

Based on the operation rights, NE users are divided into five levels, which involve monitoring level, operation level, maintenance level, system level, and debugging level in an ascending order. Different levels of NE users can be created as required.
Prerequisite
l l The NE user must have the authority of System Level or higher. An online user can create a user at a lower level.

Web LCT
l l The default NE user is at the monitoring level. For security of NE data, NE users are assigned operation rights based on their responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree. Step 2 Click Create. The Add NE User dialog box is displayed. Step 3 Set the parameters of the NE user according to the planning information.
A Task Collection
NOTE
l A Debug Level NE user has all security and configuration authorities, and has the right to run debugging commands. l A System Level NE user has all security and configuration authorities. l A Maintenance Level NE user has some security authorities, some configuration authorities, the communication setting authority, and the log management authority. l An Operation Level NE user has all fault performance authorities, some security authorities, and some configuration authorities. l A Monitor Level NE user has the right to use all query commands, to log in, to log out, and to change its own password.
Related References
B.1.3.2 Parameter Description: NE User Management_Creation
A.1.6.2 Changing the Password of an NE User

Periodically changing the password of an NE user ensures the NE security.
Prerequisite
l l l The NE user must have the authority of System Level or higher. The NE user is created. An online user can change the password of a user at a lower level.

Web LCT
NOTE
Periodically change the password of an NE user to avoid password leaks.
Issue 03 (2011-04-10)
A-33
A Task Collection
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree. Step 2 Select the required NE user from the NE user management list, and click Set Password. The Change Password dialog box is displayed. Step 3 Input New Password, and input it again in Confirm Password.
A.1.6.3 Setting Warning Screen Parameters

This topic describes how to enable the warning screen function. When a user logs in to an NE, the NMS can display some information to the user. The displayed information can be selfdefined.
Prerequisite
The NE user must have the authority of Maintenance Level or higher.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Then, choose Security > NE Security Parameters from the Function Tree. Step 2 Set Warning Screen Switching and Warning Screen Information according to the planning information.
A Task Collection
Related References
B.1.3.1 Parameter Description: NE User Management
A.2 Managing Radio Links

Before you configure the radio link between two microwave sites, you need to configure the corresponding information about the radio link. A.2.1 Creating an IF 1+1 Protection Group If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1 +1 protection group. A.2.2 Creating an XPIC Workgroup If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup, the parameter settings including the channel bandwidth, transmit frequency, transmit power, and ATPC attribute are ensured to be the same for the two radio links. A.2.3 Setting the AM Attributes of the XPIC Workgroup After the XPIC Workgroup is created, you need to configure the AM attributes of the XPIC Integrated IP radio link according to the planned values. A.2.4 Configuring the IF/ODU Information of a Radio Link By performing this operation, you can configure the IF/ODU information for a radio link. A.2.5 Creating an N+1 Protection Group When multiple STM-1 or Integrated IP radio services are transmitted in the point-to-point mode, you can adopt the N+1 protection configuration. A.2.6 Querying the IF 1+1 Protection Status You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status. A.2.7 Querying the IF N+1 Protection Status You can learn about the current information of the IF N+1 protection by querying the IF N+1 protection status. A.2.8 IF 1+1 Protection Switching You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection switching. A.2.9 IF N+1 Protection Switching You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching. A.2.10 Starting/Stopping the N+1 Protection Protocol If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be restored to the initial state.
A Task Collection
A.2.1 Creating an IF 1+1 Protection Group

If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1 +1 protection group.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added on the Slot Layout. The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.

Web LCT
When a 1+0 service is converted into a 1+1 HSB protection through the configuration of the IF 1+1 protection group, the original service is not interrupted. The board where the original service exists, however, needs to be set to the working board.
Procedure
Step 1 For an IF 1+1 protection group comprised of ISU2 or ISX2 boards, set IF Service Type to appropriate values for the main and standby IF boards according to the network plan.
NOTE
l Ensure that the values of IF Service Type set for the main and standby IF boards are the same and meet the network plan requirements. l For ISU2 or ISX2 boards, the default value of IF Service Type is Hybrid(Native E1+ETH).
1. 2. 3. 4.
In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Changes the values of IF Service Type for the main and standby IF boards according to the network plan. Click Apply.
Step 2 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 3 Click the IF 1+1 Protection tab. Step 4 Click New. The Create IF 1+1 Protection dialog box is displayed. Step 5 Configure the parameters of the IF 1+1 protection group.
A-36
Issue 03 (2011-04-10)
A Task Collection
NOTE
l When Working Mode is set to HSB, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to realize the protection. l When Working Mode is set to FD, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With FD protection, the impact of the fading on signal transmission is reduced. l When Working Mode is set to SD, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With SD protection, the impact of the fading on signal transmission is reduced. l When Revertive Mode is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. It is recommended that you set this parameter to Revertive. l When Revertive Mode is set to Non-Revertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value. l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD. l Generally, if Working Mode is set to HSB, it is recommended that you set Enable Reverse Switching to Disabled; if Working Mode is set to SD, it is recommended that you set Enable Reverse Switching to Enabled. l Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Related References
B.2.5 Parameter: IF 1+1 Protection_Create
A.2.2 Creating an XPIC Workgroup

If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup, the parameter settings including the channel bandwidth, transmit frequency, transmit power, and ATPC attribute are ensured to be the same for the two radio links.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding XPIC IF boards and the ODUs connected to the XPIC IF boards are added to the Slot Layout.
Issue 03 (2011-04-10)
A Task Collection

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click New. The Create XPIC Protection Group dialog box is displayed. Step 4 Configure the parameters for the XPIC workgroup.
NOTE
l Set Link ID-V, Link ID-H, Transmit Power(dBM), Maximum Transmit Power(dBM), and Transmit Frequency(MHz) according the network planning information. Set Link ID-V, Link IDH, Transmit Power(dBM), T/R Spacing(MHz), and ATPC Status consistently between the two ends of a link. l In normal cases, Transmission Status is set to unmute.
Related References
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
A.2.3 Setting the AM Attributes of the XPIC Workgroup

After the XPIC Workgroup is created, you need to configure the AM attributes of the XPIC Integrated IP radio link according to the planned values.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Workgroup must be created.

Web LCT
The XPIC IF boards, IFX2 and ISX2, support Integrated IP radio, and the AM attributes can be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click the Hybrid/AM Configuration tab. Step 4 Configure the AM attributes of the XPIC Hybrid radio link.
NOTE
l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Modulation Mode of the Guarantee AM Capacity specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity.

A Task Collection
Related References
B.2.2 Parameter Description: Link Configuration_XPIC

By performing this operation, you can configure the IF/ODU information for a radio link.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added on the Slot Layout.

Web LCT
Precautions
l l l l l In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio link. In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the ODU information of the standby radio link. In the case of XPIC configuration, you need to configure the IF/ODU information of the two radio links in different polarization directions separately. In the case of N+1 protection, you need to configure the IF/ODU information of the N+1 radio links respectively. The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, STM-1 count, or modulation mode is set inconsistently for both ends of a Integrated IP radio link. This alarm should be cleared immediately. Otherwise, services may be configured unsuccessfully or interrupted.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF/ODU Configuration tab. Step 3 Click an IF board icon or ODU icon. The system displays the IF/ODU information of the radio link that the IF board or ODU connected to the IF board belongs to.
A-40
Issue 03 (2011-04-10)
A Task Collection
Step 4 Configure the corresponding IF information of the radio link. 1. Optional: For ISU2/ISX2 boards, set IF Service Type according to the network plan. Click Apply.
NOTE
After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
2.
Set other IF information.

NOTE
l Link ID is set according to the planning information. Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same. l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manual Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Modulation Mode of the Guarantee AM Capacity specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity.
Step 5 Click Apply. Step 6 Configure the corresponding ODU information of the radio link.
NOTE
l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When Power to Be Received(dBm) takes the default value, the antenna misalignment indicating function is disabled. l In normal cases, it is recommended that you set TX Status to unmute.
Issue 03 (2011-04-10)
A-41
A Task Collection
Related References
B.2.7 Parameter: Link Configuration_IF/ODU Configuration

When multiple STM-1 or Integrated IP radio services are transmitted in the point-to-point mode, you can adopt the N+1 protection configuration.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added on the Slot Layout. The IF1 boards must work in the STM-1 mode.

Web LCT
l l When an N+0 service is converted into an N+1 service through the configuration of the N +1 protection group, the original service is not interrupted. In the case of Integrated IP radio, the Hybrid/AM attributes must be the same for all the N +1 radio links in the N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 Click Create. The Create N+1 Protection dialog box is displayed.
A-42
Issue 03 (2011-04-10)
A Task Collection
Step 4 Configure the Attribute of the N+1 protection group. Step 5 Configure the mapping relation between the board and the slot. 1. 2. Select Working Unit from Select Mapping Direction. Select a port to which a working channel corresponds from Available Boards, and then click 3. .
Repeat Step 5.2 to select the ports to which other working channels correspond. Click .
4. 5.
Select Protection Unit from Select Mapping Direction. Select a port to which a protection channel corresponds from Available Boards, and then click .
Related References
B.2.3 Parameter Description: N+1 Protection_Create
A.2.6 Querying the IF 1+1 Protection Status

You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status.
Prerequisite
l l
Issue 03 (2011-04-10)
The NE user must have the authority of System Level or higher. The IF 1+1 protection must be configured.
A Task Collection

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Click Query. In Protection Group, check the IF 1+1 protection groups. Step 4 Select the IF 1+1 protection group whose protection status needs to be queried. Step 5 Select the board from Slot Mapping Relation. Step 6 Right-click on the selected board and choose Query Switching Status from the shortcut menu to check the protection status of the IF 1+1 protection group. ----End
Related References
B.2.6 Parameter Description: IF 1+1 Protection
A.2.7 Querying the IF N+1 Protection Status

You can learn about the current information of the IF N+1 protection by querying the IF N+1 protection status.
Prerequisite
l l The NE user must have the authority of System Level or higher. The IF N+1 protection must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 Click Query. In Protection Group, check the IF N+1 protection groups. Step 4 Select the protection group whose protection status needs to be queried. Step 5 Click Query Switching Status. In Slot Mapping Settings, check the IF N+1 protection status. ----End
Related References
B.2.4 Parameter Description: N+1 Protection
A Task Collection
A.2.8 IF 1+1 Protection Switching

You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection switching.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IF 1+1 protection must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 In Protection Group, select the protection group for protection switching. Step 4 In Slot Mapping Relation, select a working unit or the protection unit of the protection group, and then right-click the selected unit. Step 5 Choose the required switching mode from the shortcut menu. Step 6 In the dialog box that is displayed, click OK. The system displays the dialog box that indicates the successful operation. Step 7 Click OK. Step 8 Select the working unit or the protection unit, right-click Query Switching Status and check whether the switching is successful. ----End
A.2.9 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IF N+1 protection must be configured. The N+1 protection protocol is enabled.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 In Protection Group, select the protection group for protection switching. Step 4 In Slot Mapping Settings, select a working unit or the protection unit of the protection group, and then right-click the selected unit. Step 5 Choose the required switching mode from the shortcut menu. Step 6 In the dialog box that is displayed, click OK. The system displays the dialog box that indicates the successful operation. Step 7 Click OK. Step 8 Click Query Switching Status to check whether the switching operation is successful. ----End
A.2.10 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be restored to the initial state.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IF N+1 protection must be configured.

Web LCT
Precautions
l l Stopping the N+1 protection protocol causes a failure of the N+1 protection. When services are switched onto the protection channel, stopping the N+1 protection protocol causes switchover of the services back to the working tunnel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the N+1 protection protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 In Protection Group, select the protection group whose N+1 protection protocol needs to be started.
A Task Collection
Step 4 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box. Step 5 Click Query to check the protocol status. ----End
A.3 Managing the MSP

The OptiX RTN 950 supports the linear MSP. A.3.1 Configuring Linear MSP You can configure linear MSP to protect services over the optical fibers between two nodes. A.3.2 Querying the Status of the Linear MSP By using this operation, you can know the current information about the linear MSP. A.3.3 Performing Linear MSP Switching By using this operation, you can perform the external switching on the linear MSP. A.3.4 Starting/Stopping the Linear MSP Protocol If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored to the initial state.
A.3.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding board must be added on the Slot Layout.

Web LCT
When an unprotected service is converted into a linear MSP service by configuring the linear MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 Click Create. The system displays the Create a Linear Multiplex Section dialog box. Step 3 Set the parameters of the linear MSP group.
Issue 03 (2011-04-10)
A-47
A Task Collection
Follow-up Procedure
l In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections between the services and the working channels later. If extra services need to be transmitted, it is necessary to configure bidirectional cross-connections between the extra services and the protection channels. In the case of the 1+1 linear MSP, you need to configure bidirectional cross-connections between the services and the working channels later.
Related References
B.3.1 Parameter Description: Linear MSP_Creation
A.3.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The linear MSP must be configured.

Web LCT
A-48
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 Click Query > Query Protection Group to query the current linear MSP group. Step 3 In Protection Group, click the linear MSP group to be queried. Step 4 Click Query > Query Switching Status In Slot Mapping Settings, query the status of the linear MSP. ----End
Related References
B.3.2 Parameter Description: Linear MSP
A.3.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on the linear MSP.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The linear MSP must be configured. The protection protocol is enabled.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Settings, select the working unit or protection unit, and then right-click. Step 3 Right-click and select the required switching mode.
The confirmation dialog box is displayed.

A Task Collection
Step 4 Click OK.

NOTE
If the switching of a higher priority occurs in a channel, the switching of a lower priority will not occur in the channel.
----End
A.3.4 Starting/Stopping the Linear MSP Protocol

If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored to the initial state.
Prerequisite
l l The NE user must have the authority of System Level or higher. The linear MSP must be configured.

Web LCT
Precautions
l l Stopping the ring MSP protocol causes failure of ring MSP. When services are switched onto the protection channel, stopping the ring MSP protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted; if the working channel is faulty, the services are interrupted until the working channel is restored to normal or the protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be stopped. Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is displayed. Step 4 Click Query > Query Protection Group and check Protocol Status. ----End
A.4 Managing TDM Services

The TDM services involve the SDH service and the PDH service. A.4.1 Creating the Cross-Connections of Point-to-Point Services In a cross-connection of point-to-point services, one service source corresponds to one service sink. A.4.2 Creating Cross-Connections of SNCP Services The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink.
A Task Collection
A.4.3 Modifying the Priorities of E1 Services This section describes how to adjust the priorities of E1 services. A.4.4 Inserting E1_AIS upon a TU_AIS Condition On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS insertion function for the pass-through E1 services (that is, the services cross-connected to the IF1 board). A.4.5 Configuring the Automatic Switching of SNCP Services You can manually add certain alarms for the automatic switching of SNCP services. A.4.6 Deleting Cross-Connections When a service is not used, you can delete the cross-connections of this service to release the corresponding resources. A.4.7 Converting a Normal Service into an SNCP Service By converting a normal service into an SNCP service, you can convert the unidirectional crossconnections of a normal service into the unidirectional cross-connection in the receive direction of the SNCP service. A.4.8 Converting an SNCP Service to a Normal Service By converting an SNCP service to a normal service, you can convert the SNCP cross-connection in the receive direction into the unidirectional cross-connection of the normal service. A.4.9 Querying TDM Services You can learn about the TDM services that are configured for an NE by querying TDM services. A.4.10 Switching SNCP Services You can perform external switching on SNCP services by performing this operation. A.4.11 Querying the Protection Status of SNCP Services You can know the current information of an SNCP service by querying the protection status of SNCP services.
A.4.1 Creating the Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service sink.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding source and sink boards must be added on Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
A Task Collection
Step 3 Click New. The Create SDH Service dialog box is displayed. Step 4 Configure the parameters of a new SDH service.
Related References
B.4.1 Parameter Description: SDH Service Configuration_Creation
A.4.2 Creating Cross-Connections of SNCP Services

The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding source and sink boards must be added on Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create SNCP. The Create SNCP Service dialog box is displayed.
A Task Collection
Step 4 Configure the parameters of a new SNCP service.
Related References
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
A.4.3 Modifying the Priorities of E1 Services

This section describes how to adjust the priorities of E1 services.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding source and sink boards must be added in the Slot Layout. The E1 cross-connections must be created. The IF boards in the cross-connections must support the E1 priority function. The E1 priorities must be set already and need to be modified.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Query. Step 3 Select an E1 service in Cross-Connection. Step 4 Right-click the E1 service and choose Expand from the shortcut menu. Step 5 If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, doubleclick E1 Priority and select the target E1 priority from the drop-down list.
A Task Collection
NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the working source and the protection source of the SNCP service.
Step 6 If the number of E1 services configured on an IF board is the same as Full E1 Capacity, do as follows to interchange the priority levels of two E1 services: 1. 2. 3. 4. Add one to Full E1 Capacity for both ends of the radio link. Change E1 Priority of the E1 service with a higher priority to Low. Change E1 Priority of the E1 service with a lower priority to High. Change Full E1 Capacity to the original values for both ends of the radio link.
NOTE
If Full E1 Capacity uses its maximum value, do as follows to interchange the priority levels of two services. 1. Delete either E1 service. 2. Change the priority of the other E1 service. 3. Add the E1 service that was deleted, setting its E1 Priority to the required value.
A.4.4 Inserting E1_AIS upon a TU_AIS Condition

On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS insertion function for the pass-through E1 services (that is, the services cross-connected to the IF1 board).
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IFU2, IFX2, ISU2, or ISX2 board is added to Slot Layout.

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered Alarm Insertion from the Function Tree. Step 2 Select the E1 channels on the IF board that are involved in the SNCP and then set Insert E1_AIS to TU_AIS to Enable. Step 3 Click Apply. ----End
Related References
B.4.6 Parameter Description: TU_AIS Insertion B.4.6 Parameter Description: TU_AIS Insertion
A.4.5 Configuring the Automatic Switching of SNCP Services

You can manually add certain alarms for the automatic switching of SNCP services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The SNCP protection group must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group, and then right-click Initiation Condition to which the working service corresponds. Step 3 Set the initiation condition for the working service. Click OK.
NOTE
The conditions for automatic switching of higher order services are different from those of lower order services.
Step 4 Right-click Initiation Condition to which the protection service corresponds. Step 5 Set the initiation condition for the protection service. Click OK.
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation Condition of the protection service.
Issue 03 (2011-04-10)
A-55
A Task Collection
Related References
B.4.5 Parameter Description: SNCP Service Control
A.4.6 Deleting Cross-Connections

When a service is not used, you can delete the cross-connections of this service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The cross-connections of the service must be configured and the service must not be used.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Query to query the related data. Step 3 Delete the service. 1. 2. Right-click the service and choose Delete from the shortcut menu. Then, a dialog box is displayed, querying whether you need to delete the selected service. Click OK. Step 4 Click Query. The queried information should show that the cross-connection is already deleted. ----End

By converting a normal service into an SNCP service, you can convert the unidirectional crossconnections of a normal service into the unidirectional cross-connection in the receive direction of the SNCP service.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The unidirectional cross-connection of the normal service must be configured and the source of the cross-connection must be a line board.

Web LCT
A Task Collection
When this task is performed to convert a normal service into an SNCP service, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection. Right-click the selected service and choose Expand from the shortcut menu. Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to SNCP from the shortcut menu. Then, the Convert to SNCP Service dialog box is displayed. Step 4 Set the parameters of the SNCP service.
Related References
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
A.4.8 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP cross-connection in the receive direction into the unidirectional cross-connection of the normal service.
Prerequisite
l l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. The SNCP cross-connection in the receive direction must be configured. The current service must be transmitted on the working path.
A Task Collection

Web LCT
When this task is performed to convert an SNCP service into a normal service, the original services are not interrupted.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection Configuration from the Function Tree. Step 2 In Auto-Created Cross-Connection, select the configured service and click Service Convert. Step 3 Choose SNCP Protection Service Convert to Non-Protection Service or SNCP Working Service Convert to Non-Protection Service from the displayed menu.
NOTE
l To convert the cross-connection into a cross-connection between the working source and the service sink, choose SNCP Working Service Convert to Non-Protection Service. l To convert the cross-connection into a cross-connection between the protection source and the service sink, choose SNCP Protection Service Convert to Non-Protection Service.
----End
Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the working path or the unidirectional cross-connection between the service source and the protection path. The SNCP service can be converted into the normal service both in the receive direction and the transmit direction only after the deletion.
A.4.9 Querying TDM Services

You can learn about the TDM services that are configured for an NE by querying TDM services.
Prerequisite
l l The NE user must have the authority of System Level or higher. TDM services must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Query.
A Task Collection
Step 3 In Cross-Connection, query the TDM services. ----End
Related References
B.4.4 Parameter Description: SDH Service Configuration
A.4.10 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group for SNCP service switching. Step 3 Click Function. Select the required switching mode from the displayed menu. Step 4 In the displayed dialog box for confirmation, click OK. Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, close the displayed prompt dialog box. Step 6 Choose Function > Query Switching Status to check whether the switching operation is successful. ----End
A.4.11 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status of SNCP services.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group whose service protection status needs to be queried. Step 3 Click Function > Query Switching Status. ----End
Related References
A.5 Managing Ports

Correct parameter settings of ports are the basis of configuring ports that transmit services. A.5.1 Setting the Parameters of SDH Ports The parameters of SDH ports are used to configure the loopback on the SDH interface board and the laser status. A.5.2 Setting the Parameters of PDH Ports The parameters of PDH ports are used to configure the tributary loopback, service load indication, and tributary retiming. A.5.3 Configuring Overhead Bytes Generally, the default overload bytes can meet the requirements of the device. In certain special application scenarios, however, such as device interconnection, you need to change the overload bytes according to the requirements of the interconnected device. A.5.4 Setting Smart E1 Port Parameters Smart E1 ports can be configured as CES E1 ports or ATM E1 ports. A.5.5 Setting Serial Port Parameters When some 64 kbit/s timeslots of an Smart E1 port are used for transmission of ATM services, these timeslots can be considered as a serial port. A.5.6 Setting the Parameters of Ethernet Ports The parameters of Ethernet ports include basic attributes, traffic control, Layer-2 attributes, Layer-3 attributes, and advanced attributes. A.5.7 Setting Parameters of the IF_ETH Port This topic describes how to set the parameters of the IF_ETH port. The IF_ETH port is the internal Ethernet port on an IF board in IP radio mode and is used to receive and transmit Native ETH services or packet services. A.5.8 Setting Parameters of IF Ports This topic describes how to set the parameters of IF ports, including IF attributes, ATPC attributes, and AM attributes. A.5.9 Setting the Parameters of ODU Ports This section describes how to configure the parameters of ODU ports, including the transmit frequency attribute, power attribute, ODU attribute, and advanced attribute.
A Task Collection
A.5.1 Setting the Parameters of SDH Ports

The parameters of SDH ports are used to configure the loopback on the SDH interface board and the laser status.
Prerequisite

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Interface from the Function Tree. Step 2 Select By Board/Port(Path), and select Port or VC4 Path from the list box. Step 3 Set the parameters of SDH ports.
1.
Choose Port from the drop-down list, and then configure the parameters of SDH ports. Click Apply. A dialog box is displayed for confirmation. Click OK.
2.
Step 4 Set the parameters of VC-4 paths.
1. 2. 3.
Choose VC4 Path from the drop-down list, and then configure the parameters of VC-4 paths. Click Apply. A dialog box is displayed for confirmation. Click OK.
----End
Related References
B.5.7.1 Parameter Description: SDH Interfaces
A Task Collection

The parameters of PDH ports are used to configure the tributary loopback, service load indication, and tributary retiming.
Prerequisite

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel). Step 3 Select Path from the list box. Step 4 Configure the parameters of PDH ports.
Related References
B.5.8.1 Parameter Description: PDH Interfaces
A.5.3 Configuring Overhead Bytes

Generally, the default overload bytes can meet the requirements of the device. In certain special application scenarios, however, such as device interconnection, you need to change the overload bytes according to the requirements of the interconnected device. A.5.3.1 Configuring RSOHs When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in regenerator section overheads (RSOHs). A.5.3.2 Configuring VC-4 POHs When the HP_TIM, LP_TIM, or HP_SLM alarm is reported by the line board of the local or peer NE, you need to configure the J1 or C2 byte in VC-4 path overheads (POHs). A.5.3.3 Configuring VC-12 POHs When the E1 port board of the local or remote NE reports the LP_TIM or LP_TIM_VC12 alarm, you need to configure the signal flag in the J2 byte in VC-12 path overheads (POHs).
A Task Collection
A.5.3.1 Configuring RSOHs

When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in regenerator section overheads (RSOHs).
Prerequisite
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree. Step 2 Choose Display in Text Format or Display in Hexadecimal. Step 3 Configure the J0 byte. 1. 2. Double-click the parameter whose value needs to be changed. The Please Input the Overhead Byte dialog box is displayed. Configure overhead bytes.
3.
Click OK.
Step 4 Click Apply. A dialog box is displayed for confirmation. Step 5 Click OK. ----End
A Task Collection
Related References
B.5.9.1 Parameter Description: Regenerator Section Overhead
A.5.3.2 Configuring VC-4 POHs

When the HP_TIM, LP_TIM, or HP_SLM alarm is reported by the line board of the local or peer NE, you need to configure the J1 or C2 byte in VC-4 path overheads (POHs).
Prerequisite
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Step 2 Choose Display in Text Format or Display in Hexadecimal. Step 3 Optional: Configure the J1 byte. 1. 2. 3. Click the Trace Byte J1 tab. Double-click the parameter whose value needs to be changed. The Please Input Overhead Byte dialog box is displayed. Configure overhead bytes.
4. 5. 6.
Click OK. Click Apply. A dialog box is displayed for confirmation. Click OK.
Step 4 Optional: Configure the C2 byte. 1. 2. Click the Signal Flag C2 tab. Configure the required parameters.
A-64
Issue 03 (2011-04-10)
A Task Collection
3. 1. 2.
Click Apply. Click the Overhead Termination tab. Configure VC4 Overhead Termination.
Step 5 Configure the termination mode of the VC-4 overhead.
3. 4.
Click Apply. A dialog box is displayed for confirmation. Click OK.
----End
Related References
B.5.9.2 Parameter Description: VC-4 POHs

When the E1 port board of the local or remote NE reports the LP_TIM or LP_TIM_VC12 alarm, you need to configure the signal flag in the J2 byte in VC-12 path overheads (POHs).
Prerequisite
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC12 Path Overhead from the Function Tree. Step 2 Configure the J2 byte. 1. 2. 3. 4. Click the Trace Byte J2 tab. Choose Display in Text Format or Display in Hexadecimal. Double-click the parameter whose value needs to be changed. The Please input the overhead byte dialog box is displayed. Configure overhead bytes.
Issue 03 (2011-04-10)
A-65
A Task Collection
5. 6. 7.
Click OK. Click Apply. A dialog box is displayed for confirmation. Click OK.
----End
Related References
A.5.4 Setting Smart E1 Port Parameters

Smart E1 ports can be configured as CES E1 ports or ATM E1 ports. A.5.4.1 Setting Basic Attributes of Smart E1 Ports The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and encapsulation type. A.5.4.2 Setting Advanced Attributes of Smart E1 Ports The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback mode.
A.5.4.1 Setting Basic Attributes of Smart E1 Ports

The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and encapsulation type.
A Task Collection
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the required port and set the parameters.
Related References
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes
A.5.4.2 Setting Advanced Attributes of Smart E1 Ports

The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback mode.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the required port and set the parameters for its advanced attributes.
Related References
B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes
A.5.5 Setting Serial Port Parameters

When some 64 kbit/s timeslots of an Smart E1 port are used for transmission of ATM services, these timeslots can be considered as a serial port. A.5.5.1 Creating Serial Ports When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port. A.5.5.2 Setting Basic Attributes of Serial Ports The basic attributes of serial ports involve the parameters such as port mode and encapsulation type.
A.5.5.1 Creating Serial Ports

When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port.
Prerequisite
l l The NE user must have the authority of System Level or higher. The ports that travel services are set to Layer 1.

Web LCT
A-68
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Click New. The New Serial Interface dialog box is displayed. Step 4 Set the parameters for the serial port according to the planning information.
Related References
B.5.3.1 Parameter Description: Serial Port_Basic Attributes
A.5.5.2 Setting Basic Attributes of Serial Ports

The basic attributes of serial ports involve the parameters such as port mode and encapsulation type.
Prerequisite
l l The NE user must have the authority of System Level or higher. Serial ports are added.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the required port and set the parameters for the serial port according to the planning information.
A Task Collection
Related References
B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports
A.5.6 Setting the Parameters of Ethernet Ports

The parameters of Ethernet ports include basic attributes, traffic control, Layer-2 attributes, Layer-3 attributes, and advanced attributes. A.5.6.1 Setting the General Attributes of Ethernet Ports The general attributes of Ethernet ports define the physical-layer information, such as the interface mode, encapsulation type, and maximum frame length. A.5.6.2 Configuring the Traffic Control of Ethernet Ports After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link congestion. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports The L2 attributes of Ethernet ports define the link-layer information. A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports The Layer 3 attributes of Ethernet ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and Ethernet port IP addresses. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports This topic describes how to set the advanced attributes of Ethernet ports.
A.5.6.1 Setting the General Attributes of Ethernet Ports

The general attributes of Ethernet ports define the physical-layer information, such as the interface mode, encapsulation type, and maximum frame length.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree.
A Task Collection
Step 2 Click the General Attributes tab. Step 3 Configure the general attributes of Ethernet ports.
NOTE
l Port Mode specifies the mode of the Ethernet port. l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry MPLS tunnels. l Encapsulation Type specifies the method of the port to process the received packets. l If you set Encapsulation Type to Null, the port transparently transmits the received packets. l If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set Encapsulation Type to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard. l The Ethernet ports of different types support different Working Mode. l When the equipment on the opposite side works in auto-negotiation mode, set the Working Mode of the equipment on the local side to Auto-Negotiation. l When the equipment on the opposite side works in full-duplex mode, set the Working Mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. l When the equipment on the opposite side works in half-duplex mode, set the Working Mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side. l FE ports support 10M full-duplex, 10M half-duplex, 100M full-duplex, 100M half-duplex, and autonegotiation. l GE electrical ports support 10M full-duplex, 10M half-duplex, 100M full-duplex, 100M half-duplex, 1000M full-duplex, and auto-negotiation. l GE optical ports support 1000M full-duplex and auto-negotiation. l The value of Max Frame Length(byte) should be greater than the length of any frame to be transported. l Auto-Negotiation Ability specifies the auto-negotiation capability of the Ethernet port. l For GE optical ports, Auto-Negotiation Ability can be set to 1000M Full-Duplex only. l Auto-Negotiation Ability is valid only when Working Mode is set to Auto-Negotiation. l The SFP on the EM6F board supports the optical port and electrical port.
Related References
B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes

After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link congestion.
A Task Collection
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Flow Control tab. Step 3 Configure the traffic control of Ethernet ports.
NOTE
l Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to AutoNegotiation. l Auto-Negotiation Flow Control Mode of the equipment on the local side must be consistent with the auto-negotiation flow control mode of the equipment on the opposite side l The OptiX RTN 950 supports only two auto-negotiation flow control modes, namely, Disabled mode and Enable Symmetric Flow Control mode. l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to AutoNegotiation. l Non-Autonegotiation Flow Control Mode of the equipment on the local side must be consistent with the non-autonegotiation flow control mode of the equipment on the opposite side l The OptiX RTN 950 supports only two non-auto-negotiation flow control modes, namely, Disabled mode and Enable Symmetric Flow Control mode.
Related References
B.5.2.2 Parameter Description: Ethernet Interface_Flow Control
A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports

The L2 attributes of Ethernet ports define the link-layer information.
Prerequisite
l
A-72

A Task Collection
l l
The Ethernet board must be added on the Slot Layout. Port Mode of Ethernet ports are set to Layer 2.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Configure the L2 attributes of Ethernet ports.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ Type Domain. The default value is 88A8. l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be changed. l QinQ Type Domain should be set to the same value for all the ports on the EM6T/EM6F board . l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access. l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid. l Default VLAN ID is valid only when TAG is set to Access or Hybrid. l VLAN Priority is valid only when TAG is set to Access or Hybrid. l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN Priority is set according to the planning information. In normal cases, it is recommended that you use the default value.
Related References
B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports

The Layer 3 attributes of Ethernet ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and Ethernet port IP addresses.
Prerequisite
l l
Issue 03 (2011-04-10)
The NE user must have the authority of System Level or higher. Port Mode of Ethernet ports are set to Layer 3.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab.
Step 3 Set the parameters for Ethernet ports according to the planning information. Step 4 Click Apply. ----End
Related References
B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports

This topic describes how to set the advanced attributes of Ethernet ports.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Configure the advanced attributes of Ethernet ports.

A Task Collection
Related References
B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes
A.5.7 Setting Parameters of the IF_ETH Port

This topic describes how to set the parameters of the IF_ETH port. The IF_ETH port is the internal Ethernet port on an IF board in IP radio mode and is used to receive and transmit Native ETH services or packet services. A.5.7.1 Setting the General Attributes of the IF_ETH Port The general attributes of the IF_ETH port specify the basic information, including the port mode and encapsulation mode. A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer, including the tag attribute and QinQ type domain. A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports The Layer 3 attributes of IF_ETH ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and IF_ETH port IP addresses. A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port This topic describes how to set the advanced attributes of IF_ETH ports.

The general attributes of the IF_ETH port specify the basic information, including the port mode and encapsulation mode.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added to Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Set the general attributes of the IF_ETH port.
Issue 03 (2011-04-10)
A-75
A Task Collection
NOTE
l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels. l Encapsulation Type specifies the method of the port to process the received packets. l If Encapsulation Type is set to Null, the port transparently transmits the received packets. l If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. l If Encapsulation Type is set to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
Related References
B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes
A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port

The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer, including the tag attribute and QinQ type domain.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added to Slot Layout. The parameter Port Mode is set to Layer 2.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Setting the Layer 2 attributes of the IF_ETH port.
A-76
Issue 03 (2011-04-10)
NOTE
A Task Collection
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ Type Domain. The default value is 88A8. l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be changed. l If all the accessed services are frames that contain the VLAN tag (tagged frames), set Tag to "Tag Aware". l If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set Tag to "Access". l If the accessed services contain tagged frames and untagged frames, set Tag to "Hybrid". l Default VLAN ID is valid only when TAG is set to Access or Hybrid. l VLAN Priority is valid only when TAG is set to Access or Hybrid. l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN Priority needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
Related References
B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes
A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports

The Layer 3 attributes of IF_ETH ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and IF_ETH port IP addresses.
Prerequisite
l l The NE user must have the authority of System Level or higher. Port Mode of the ports on IF boards are set to Layer 3.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Set parameters for Layer 3 attributes of the ports on IF boards according to the planning information.

A Task Collection
Related References

This topic describes how to set the advanced attributes of IF_ETH ports.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added to Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Setting the advanced attributes of the IF_ETH port.
Related References
B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes
A.5.8 Setting Parameters of IF Ports

This topic describes how to set the parameters of IF ports, including IF attributes, ATPC attributes, and AM attributes. A.5.8.1 Setting IF Attributes In the case of different IF boards, different parameters need to be set. A.5.8.2 Configuring the ATPC Attributes To configure the ATPC function, set the ATPC attributes of the IF board. A.5.8.3 Setting Advanced AM Attributes By performing this operation, you can query and adjust the E1 capacity in each modulation scheme. A.5.8.4 Querying the AM Status By querying the AM status, you can trace the change of the modulation mode when the AM function is used. A.5.8.5 Querying the ATPC Adjustment Records
A Task Collection
By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function. A.5.8.6 Modifying the Hybrid/AM Attributes Any modifications to Hybrid/AM attributes must ensure that the Hybrid/AM attribute settings are the same for both ends of the adjusted radio link. Otherwise, the modifications do not take effect or services are interrupted.
A.5.8.1 Setting IF Attributes

In the case of different IF boards, different parameters need to be set.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added on the Slot Layout.

Web LCT
Context
l l l The IF1 board is used for TDM microwave. The IFU2 and ISU2 boards are general-purpose IF boards. The IFX2 and ISX2 boards are general-purpose XPIC IF boards.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Configure the parameters of general attributes. l In the case of the IF1:
l In the case of the IFU2:
l In the case of the IFX2:
l For the ISU2 board: 1. set IF Service Type according to the network plan. Click Apply.
NOTE
2.
Issue 03 (2011-04-10)
Set other general attributes.

A Task Collection
l For the ISX2 board: 1. set IF Service Type according to the network plan. Click Apply.
NOTE
2.
Set other general attributes.
NOTE
l Link ID is set according to the planning information. Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same. l Generally, IF Port Loopback is used to locate the faults that occur at each IF interface. The IF loopback is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal cases, this parameter is set to Non-Loopback. l 350 MHz Consecutive Wave Status can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, the services are interrupted. l If the XPIC IF board does not perform the XPIC function, XPIC Enabled should be set to Disabled. l Enable IEEE-1588 Timeslot needs to be set consistently between two ends of a radio link.
Step 4 Configure the parameters of Hybrid/AM attributes for different IF services. l For the IFU2 and IFX2 boards:
l For the ISU2 and ISX2 boards:
NOTE
l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manual Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Modulation Mode of the Guarantee AM Capacity specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme. l Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity.
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
A Task Collection
A.5.8.2 Configuring the ATPC Attributes

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added on the Slot Layout.
Precautions
l l For the IF boards that are configured with 1+1 protection, configure only the ATPC attributes of the main IF board. The following procedure describes the configuration of ATPC parameters in the IF port configuration dialog box of the IF board. You can also configure ATPC parameters in the Create XPIC Protection Group window.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the ATPC Attributes tab. Step 3 Configure the parameters of ATPC attributes.
NOTE
l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set ATPC Enable Status to Disabled. l If ATPC Automatic Threshold Enable Status is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link. l If ATPC Automatic Threshold Enable Status is set to Disabled, you need to manually set ATPC Upper Automatic Threshold(dBm) and ATPC Lower Automatic Threshold(dBm). l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB.
Related References
B.5.5.2 Parameter Description: IF Interface_ATPC Attribute
A Task Collection

By performing this operation, you can query and adjust the E1 capacity in each modulation scheme.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards must be added in the Slot Layout. The E1 priority function must be enabled.

Web LCT
l l The OptiX RTN 950 supports the configuration of E1 priorities. The IF boards that support this function are IFU2, IFX2, ISU2, and ISX2. For the ISU2 and ISX2 boards, only the Integrated IP radio that transmits Native E1 services supports the configuration of E1 priorities.
Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the AM Advanced Attributes tab. Step 3 Set each parameter for the advanced AM attributes.
Related References
B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
A.5.8.4 Querying the AM Status

By querying the AM status, you can trace the change of the modulation mode when the AM function is used.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards must be added in the Slot Layout.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Click Query. Step 4 Query the AM information in Hybrid/AM Configuration. ----End
Related References
A.5.8.5 Querying the ATPC Adjustment Records

By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ATPC Adjustment Records from the Function Tree. Step 2 Click Query to query the running information of the ATPC function. ----End
Related References
B.5.5.4 Parameter Description: ATPC Adjustment Records
A Task Collection
A.5.8.6 Modifying the Hybrid/AM Attributes

Any modifications to Hybrid/AM attributes must ensure that the Hybrid/AM attribute settings are the same for both ends of the adjusted radio link. Otherwise, the modifications do not take effect or services are interrupted.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards have been added in the Slot Layout.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Optional: Change the channel bandwidth. 1. 2. 1. 2. Set IF Channel Bandwidth to its planned value. Click Apply. Set Manually Specified Modulation Mode to its planned value. Click Apply.
Step 4 Optional: When the AM function is disabled, adjust the modulation mode.
Step 5 Disable the AM function. 1. 2. 1. Set AM Enable Status to Disabled and set Manually Specified Modulation Mode to its planned value. Click Apply. If the planned Modulation Mode of the Guarantee AM Capacity is lower than Manually Specified Modulation Mode, perform Step 4 and then change Manually Specified Modulation Modeto the planned Modulation Mode of the Guarantee AM Capacity. Set AM Enable Status to Enabled, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to their planned values. Click Apply.
Step 6 Optional: Enable the AM function.
2. 3.
Step 7 Optional: When the AM function is enabled, adjust the modulation mode.
A-84
Issue 03 (2011-04-10)
A Task Collection
If... You need to lower Modulation Mode of the Guarantee AM Capacity
Then... 1. Perform Step 5 to disable the AM function, and change Manually Specified Modulation Mode to the lowered Modulation Mode of the Guarantee AM Capacity. 2. Perform Step 6 to enable the AM function.
In other cases
1. Set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to their planned values. 2. Click Apply.
Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1 Capacity) in a radio link. If... Then...
You need to reduce the number of high- 1. Perform A.4.6 Deleting Cross-Connections priority E1 services to delete unnecessary E1 services. 2. Decrease Guarantee E1 Capacity. 3. Click Apply. You need to increase the number of high-priority E1 services 1. Increase Guarantee E1 Capacity. 2. If Enable E1 Priority is Enabled, increase Full E1 Capacity accordingly. 3. Click Apply. 4. Perform A.4.1 Creating the CrossConnections of Point-to-Point Services or A. 4.2 Creating Cross-Connections of SNCP Services to add required E1 services.
NOTE l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1 services. l Adding high-priority E1 services does not affect original E1 services.
Step 9 Optional: Change the number of low-priority E1 services (namely, Guarantee E1 Capacity) in a radio link. If... Then...
You need to reduce the number of low- 1. Perform A.4.6 Deleting Cross-Connections priority E1 services to delete unnecessary E1 services. 2. Decrease Full E1 Capacity. 3. Click Apply.
Issue 03 (2011-04-10)
A-85
A Task Collection
If...
Then...
You need to increase the number of low- 1. If Enable E1 Priority is Disabled, change priority E1 services Enable E1 Priority to Enabled. 2. Increase Full E1 Capacity. 3. Click Apply. 4. Perform A.4.1 Creating the CrossConnections of Point-to-Point Services or A. 4.2 Creating Cross-Connections of SNCP Services to add required E1 services. l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1 services. l Adding low-priority E1 services does not affect original E1 services. ----End
Related References
A.5.9 Setting the Parameters of ODU Ports

This section describes how to configure the parameters of ODU ports, including the transmit frequency attribute, power attribute, ODU attribute, and advanced attribute. A.5.9.1 Setting the Transmit Frequency Attribute of the ODU The transmit frequency attribute of the ODU is used to configure the transmit frequency of the ODU and T/R spacing. A.5.9.2 Querying the ODU Attribute The ODU attribute is used to query the information about the ODU. A.5.9.3 Setting the Power Attributes of the ODU The power attribute of the ODU is used to configure the transmit power and receive power of the ODU. A.5.9.4 Setting the Advanced Attributes of the ODU The advanced attributes of the ODU are used to configure the transmit status of the ODU. A.5.9.5 Setting the State of an ODU Transmitter The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the unmute state, the ODU transmits and receives microwave signals normally. When the ODU transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive microwave signals. A.5.9.6 Querying the History Transmit Power and Receive Power Querying the change trend of the history transmit power and receive power can provide reference for radio link troubleshooting.
A-86
Issue 03 (2011-04-10)
A Task Collection
A.5.9.1 Setting the Transmit Frequency Attribute of the ODU

The transmit frequency attribute of the ODU is used to configure the transmit frequency of the ODU and T/R spacing.
Prerequisite

Web LCT
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.
NOTE
l The value of Transmit Frequency(MHz) must not be less than the sum of the minimum transmit frequency supported by the ODU and a half of the channel spacing, and must not be more than the difference between the maximum transmit frequency supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies at both ends of a radio link should be one T/R spacing. l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the receive frequency. l A valid T/R spacing value is determined by the ODU itself, and T/R Spacing(MHz) should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Related References
B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute
A.5.9.2 Querying the ODU Attribute

The ODU attribute is used to query the information about the ODU.
Prerequisite
l
Issue 03 (2011-04-10)

A Task Collection
The IF boards and the ODUs to which the IF boards are connected must be added on the Slot Layout.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Equipment Information tab. Step 3 Click Query to obtain the information about the ODU.
----End
Related References
B.5.6.3 Parameter Description: ODU Interface_Equipment Information

The power attribute of the ODU is used to configure the transmit power and receive power of the ODU.
Prerequisite

Web LCT
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Power Attributes tab. Step 3 Configure the power attribute parameters of the ODU.
A-88
Issue 03 (2011-04-10)
NOTE
A Task Collection
l Maximum Transmit Power(dBm) is set according to the planning information. This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l The maximum transmit power adjusted by using the ATPC function should not exceed Maximum Transmit Power(dBm). l Transmit Power(dBm) is set according to the planning information. This parameter specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU or a value that exceeds Maximum Transmit Power(dBm). l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l Power to Be Received(dBm) is set according to the planning information. When this parameter takes the default value, the antenna misalignment indicating function is disabled. l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function is enabled.
Related References
B.5.6.2 Parameter Description: ODU Interface_Power Attributes
A.5.9.4 Setting the Advanced Attributes of the ODU

The advanced attributes of the ODU are used to configure the transmit status of the ODU.
Prerequisite

Web LCT
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Configure the parameters of the ODU, such as Configure Transmission Status.
Issue 03 (2011-04-10)
A-89
A Task Collection
NOTE
l RF Loopback function is used for fault locating for the RF interfaces. The RF Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, RF Loopback is set to Non-Loopback. l In normal cases, Configure Transmission Status is set to unmute.
Related References
B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes
A.5.9.5 Setting the State of an ODU Transmitter

The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the unmute state, the ODU transmits and receives microwave signals normally. When the ODU transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive microwave signals.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards and the ODUs connected to the IF boards must be added to the Slot Layout.

Web LCT
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Set Configure Transmission Status for the ODU.
NOTE
l In normal cases, Configure Transmission Status is set to unmute. l If Configure Transmission Status is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. l If Configure Transmission Status is set to unmute, the ODU can normally transmit and receive microwave signals.

A Task Collection
A.5.9.6 Querying the History Transmit Power and Receive Power

Querying the change trend of the history transmit power and receive power can provide reference for radio link troubleshooting.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards and the ODUs connected to the IF boards must be added to the Slot Layout.

Web LCT
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > Performance Graph Analyse from the Function Tree. Step 2 Specify the start time and end time of a specific time span.
NOTE
The time span starts from the last routine maintenance time to the current time.
Step 3 Set Monitoring Period and Power. Step 4 Click Draw. The history transmit and receive power curve of the ODU in the specified time span is displayed. ----End
A.6 Configuring Ethernet Services and Features on the Packet Plane

Configurations of Ethernet services and features on the packet plane include Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.6.1 Managing the ERPS The Ethernet ring protection switching (ERPS) on the FE/GE ring or Integrated IP radio ring can be configured to protect the Ethernet service. A.6.2 Managing the LAG Link aggregation allows one or multiple links that are attached to the same equipment to be aggregated together to form a LAG. The aggregated links can be considered as a single logical link by the MAC address. In this manner, the bandwidth is increased and the availability of the links is improved. A.6.3 Configuring Ethernet Services The Ethernet service is classified into two types, namely, E-Line service and E-LAN service. A.6.4 Managing the MAC Address Table The MAC address table is the core of the E-LAN service. The OptiX RTN 950 provides various functions for managing the MAC address table.
A Task Collection
A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC address table or a multicast frame whose destination MAC address is not listed in the multicast group. By default, the NE broadcasts the unknown frame. By setting the mode for processing an unknown frame of the E-LAN service, you can change the processing mode so that unknown frame can be discarded. A.6.6 Managing the MSTP The OptiX RTN 950 supports only the MSTP that generates the CIST. A.6.7 Managing the QoS By managing the QoS, you can provide the services of different levels for different service types. A.6.8 Using the IEEE 802.1ag OAM By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.6.9 Using the IEEE 802.3ah OAM By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links. A.6.10 LPT Configuration When you use LPT function, you need to configure the relationship between LPT ports and the related information of LPT ports.
A.6.1 Managing the ERPS

The Ethernet ring protection switching (ERPS) on the FE/GE ring or Integrated IP radio ring can be configured to protect the Ethernet service. A.6.1.1 Creating Ethernet Ring Protection Instances The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances. A.6.1.2 Setting the Parameters of Ethernet Ring Protocol The parameters to be set include the hold-off time, WTR time, and guard time. A.6.1.3 Querying the Status of the Ethernet Ring Protocol By using this operation, you can know the current status of the Ethernet ring protection switching (ERPS).
A.6.1.1 Creating Ethernet Ring Protection Instances

The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet boards, general-purpose IF boards, or general-purpose XPIC IF boards must be added to the Slot Layout.

Web LCT
A-92
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management. Step 2 Click New. The Create Ethernet Ring Protection Protocol Instance dialog box is displayed. Step 3 Set the parameters for the ERPS protection instance.
Related References
B.6.2.1 Parameter Description: ERPS Management_Creation
A.6.1.2 Setting the Parameters of Ethernet Ring Protocol

The parameters to be set include the hold-off time, WTR time, and guard time.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The protection instance of the ERPS must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
Step 3 Optional: Set the parameters of Ethernet ring protocol.

A Task Collection
Related References
B.6.2.2 Parameter Description: ERPS Management
A.6.1.3 Querying the Status of the Ethernet Ring Protocol

By using this operation, you can know the current status of the Ethernet ring protection switching (ERPS).
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Step 2 Click Query. Step 3 Query the status of the Ethernet ring protocol. ----End
Related References
A.6.2 Managing the LAG

Link aggregation allows one or multiple links that are attached to the same equipment to be aggregated together to form a LAG. The aggregated links can be considered as a single logical link by the MAC address. In this manner, the bandwidth is increased and the availability of the links is improved. A.6.2.1 Creating a LAG Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved, the new LAG must be created. A.6.2.2 Setting Parameters for LAGs
A Task Collection
The parameters for a LAG include port priorities and system priorities. In a static LAG, traffic is always carried by a port with a higher priority. A.6.2.3 Querying the Protocol Information of the LAG Through this operation, you can learn about the running information of the LACP used for the LAG.

Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved, the new LAG must be created.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board on which the LAG port to be created must be added to the Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New. The system displays the Create Link Aggregation Group dialog box. Step 4 Set the attributes of the LAG in Attribute Settings.
Issue 03 (2011-04-10)
A-95
A Task Collection
NOTE
l When Automatically Assign is selected, LAG No. cannot be set. l Revertive Mode can be set only when Load Sharing is set to Non-Sharing. l When Revertive Mode is set to Revertive Mode, the services are switched back to the former working channel after this channel is restored to normal. l Set Load Sharing to the same value as the peer equipment. It is recommended that you set Load Sharing to Non-Sharing at both ends if the LAGs are used for protection and set Load Sharing to Sharing at both ends if the LAGs are used for increasing bandwidths. l System Priority indicates the priority of a LAG. The smaller the value of System Priority, the higher the priority. l WTR Time(min) takes effect only when Revertive Mode is Revertive Mode.
Step 5 Set the LAG port in Port Settings. 1. 2. 3. Set Main Board and Main Port. In Available Slave Ports, select Board of the slave port. In Port, select the slave port, and then click
TIP
Hold on the Ctrl key or the Shift key on the keyboard to select multiple ports.
4.
Click OK.
Step 6 Optional: Set Switch LAG upon Air Interface SD to Enabled.

NOTE
This operation is necessary during the configuration of LAG at air interfaces if signals on the radio link deteriorate and LAG switching occurs.
----End
Related References
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
A Task Collection
A.6.2.2 Setting Parameters for LAGs

The parameters for a LAG include port priorities and system priorities. In a static LAG, traffic is always carried by a port with a higher priority.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board on which the LAG to be created must be added to Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Link Aggregation Parameters tab. Step 3 Set the port priority.
NOTE
l System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to Sharing. l After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect for the entire NE.
Related References
B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation
A.6.2.3 Querying the Protocol Information of the LAG

Through this operation, you can learn about the running information of the LACP used for the LAG.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The LAG must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click Query Step 4 In the Main Interface, select the LAG to be queried. Step 5 Query port status of the main and slave ports.
NOTE
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the specific information about the LAG from the shortcut menu.
Step 7 Click Close. Step 8 Click the Link Aggregation Parameters tab. Step 9 Click Query. Step 10 Query the port priority of the LAG. ----End
A.6.3 Configuring Ethernet Services

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service. A.6.3.1 Configuring the QinQ Link Configuring the QinQ link is the prerequisite for configuring QinQ private line services. A.6.3.2 Configuring UNI-UNI E-Line Services This topic describes how to create an E-Line service that is transparently transmitted end to end or is transmitted based on VLANs. A.6.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)
A Task Collection
This topic describes how to configure QinQ-based E-Line services. A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) This topic describes how to configure E-Line services carried by QinQ links. A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) This section describes how to configure E-Line services carried by PWs. A.6.3.6 Creating a VLAN Forwarding Table Item After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service packets can be switched at the source or sink end of the E-Line service. A.6.3.7 Configuring TPID for a Request VLAN When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the request VLAN is defaulted to be 0x88A8. The TPID can be set for an NE. A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipointto-multipoint mode through MAC address. A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several switching domains. A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several switching domains. A.6.3.11 Changing Logical Ports Connected to a VB This section describes how to change the logical ports connected to a VB and the attributes of the ports. A.6.3.12 Deleting an E-Line Service When an E-Line service is not used, you need to delete the E-Line service to release the corresponding resources. A.6.3.13 Deleting E-LAN Services When an E-LAN service is not required, you can delete this E-LAN service to release corresponding Ethernet resources.
A.6.3.1 Configuring the QinQ Link

Configuring the QinQ link is the prerequisite for configuring QinQ private line services.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout. On associated ports, the Encapsulation Type is set to QinQ.

Web LCT
Issue 03 (2011-04-10)
A-99
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Step 2 Click New. Step 3 Configure the basic attributes of the QinQ link.
Related References
B.6.1.6 Parameter Description: QinQ Link_Creation
A.6.3.2 Configuring UNI-UNI E-Line Services

This topic describes how to create an E-Line service that is transparently transmitted end to end or is transmitted based on VLANs.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Create. The Create E-Line Service dialog box is displayed. Step 3 Set Direction to UNI-UNI. Step 4 Configure the attributes of the E-Line service.
A-100
Issue 03 (2011-04-10)
A Task Collection
Step 5 Click Port Attributes. Step 6 Change the Ethernet port attributes of the source and sink ports. Click Apply Port Attributes. Step 7 Click OK. ----End
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
A.6.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)

This topic describes how to configure QinQ-based E-Line services.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. Ethernet boards have been added on the Slot Layout. For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Create. The Create E-Line Service dialog box is displayed. Step 3 Set Direction to NNI-NNI.
A Task Collection
Step 4 Set relevant attributes of the E-Line service.
Step 5 Optional: Click New to configure the source and sink ends.
NOTE
In this manner, you do not need to configure the QinQ links used at the source and sink ends according to the network planning information ahead of time. But, you need to set Encapsulation Type of ports corresponding to the QinQ links to QinQ ahead of time.
1. 2.
Click New. Set the attributes of the QinQ link at the source end.
3. 4. 5. 6.
Click Configure QinQ Link. Repeat Step 5.2 and Step 5.3 to set the attributes of the QinQ link at the sink end. Select Use existing resource. Click to add QinQ links to Source and Sink.
Step 6 Optional: Select Use existing resource and select created QinQ links as the QinQ links used at the source and sink ends.
NOTE
In this manner, you need to configure the QinQ links used at the source and sink ends according to the network planning information ahead of time.
1. 2.
A-102
Select Use existing resource. Click to add QinQ links to Source and Sink.
A Task Collection
Related References
A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)

This topic describes how to configure E-Line services carried by QinQ links.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. Ethernet boards have been added on the Slot Layout. For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Create. The Create E-Line Service dialog box is displayed. Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link. Step 4 Set relevant attributes of the E-Line service.
Issue 03 (2011-04-10)
A-103
A Task Collection
Step 5 Click Port Attributes. Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes. Step 8 Click QinQ Link. Step 9 Optional: Click New and create the QinQ link used at the sink end.
NOTE
In this manner, you do not need to configure the QinQ link used at the sink end according to the network planning information ahead of time. But you need to set Encapsulation Type of ports corresponding to the QinQ links to QinQ ahead of time.
1. 2.
Click New. Set the attributes of the QinQ link at the sink end.
3. 4. 5.
Click Configure QinQ Link. Select Use existing resource. Click to add the QinQ link to Sink.
6.
Click Configure QinQ Link.
Step 10 Optional: Select Use existing and select a created QinQ link as the QinQ link used at the sink end.
NOTE
In this manner, you need to configure the QinQ link used at the sink end according to the network planning information ahead of time.
1. 2.
Select Use existing resource. Click to add the QinQ link to Sink.
A-104
Issue 03 (2011-04-10)
A Task Collection
3.
Click Configure QinQ Link.
Related References
A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)

This section describes how to configure E-Line services carried by PWs.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet board is added on the Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Create. The Create dialog box is displayed. Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No Protection for the services. After successful service creation, add the APS protection when necessary. For details on how to add APS protection, see A.8.5.1 Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.
Issue 03 (2011-04-10)
A-105
A Task Collection
Step 5 Click Port Attributes. Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes. Step 8 Click PW and set the basic attributes of the PW.
Step 9 Click Apply. Step 10 Click Advanced Attributes. The Advanced Attributes dialog box is displayed. Step 11 Set the advanced attributes of the PW.
A Task Collection
Step 12 Click OK. Step 13 Click OK. ----End
Related References
A.6.3.6 Creating a VLAN Forwarding Table Item

After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service packets can be switched at the source or sink end of the E-Line service.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet board must be added to Slot Layout. The UNI-UNI E-Line service must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the E-Line service whose VLAN forwarding table entries need to be configured. Step 3 Click the VLAN Forwarding Table Item tab. Step 4 Click New. Step 5 Set the attributes of the new VLAN forwarding table item. Step 6 Click OK. ----End
A Task Collection
Related References
B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation
A.6.3.7 Configuring TPID for a Request VLAN

When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the request VLAN is defaulted to be 0x88A8. The TPID can be set for an NE.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Configuration > TPID Configuration from the Function Tree. Step 2 Set TPID(Hexadecimal) according to planning information.
A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services

The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipointto-multipoint mode through MAC address.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click Create. The Create E-LAN Service dialog box is displayed. Step 3 Click Configure the source and sink. Set the basic attributes of the E-LAN service according to network planning information.
NOTE
A Task Collection
Set Tag Type to Tag-Transparent.
Step 4 Configure the ports mounted to the bridge on the UNI side. 1. 2. 3. Click Get UNI Port. The Get UNI Port dialog box is displayed. Configure the ports mounted to the bridge on the UNI side. Click OK.
Step 5 Optional: Create split horizon groups. 1. 2. Click Set the service parameters and select Split Horizon Group. Click New. The Create Split Horizon Group dialog box is displayed. 3. Select a required port from Available Port List and click
NOTE
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
4.
Click OK.
Related References
B.6.1.4 Parameter Description: E-LAN Service_Creation
A Task Collection
A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several switching domains.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click Create. The Create E-LAN Service dialog box is displayed. Step 3 Click Configure the source and sink. Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Awared.
NOTE
A-110
Issue 03 (2011-04-10)
A Task Collection
4.
Click OK.
Related References
A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several switching domains.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click Create. The Create E-LAN Service dialog box is displayed. Step 3 Click Configure the source and sink. Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Awared.
Issue 03 (2011-04-10)
A-111
A Task Collection
Step 5 Configure the ports mounted to the bridge on the NNI side. 1. 2. 3. Click Get NNI Port. The Get NNI Port dialog box is displayed. Configure the ports mounted to the bridge on the NNI side. Click OK.
NOTE
4.
Click OK.

A Task Collection
Related References
A.6.3.11 Changing Logical Ports Connected to a VB

This section describes how to change the logical ports connected to a VB and the attributes of the ports.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The E-LAN services must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Add or delete logical ports connected to a VB. 1. 2. 3. 4. 5. Click Port Config. Click Get UNI Port and change the port on the UNI side. Click OK. Optional: Click Get NNI Port to change the port on the NNI side. Optional: Click OK.
NOTE
l Click l Click
to add ports to be mounted to the bridge. to delete ports mounted to the bridge.
l You can select more than one port by pressing and holding on the Ctrl key.
----End
A.6.3.12 Deleting an E-Line Service

When an E-Line service is not used, you need to delete the E-Line service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The E-Line service must be configured and the service is not used.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Query. Step 3 Select the E-Line service that needs to be deleted and then click Delete. Step 4 Click Query. At this time, the E-Line service is already deleted. ----End
A.6.3.13 Deleting E-LAN Services

When an E-LAN service is not required, you can delete this E-LAN service to release corresponding Ethernet resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. A configured E-LAN service is not required.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click Query. Then, close the dialog box that is displayed. Step 3 Select the E-LAN service to be deleted and click Delete. Then, a confirmation dialog box is displayed. Step 4 Click OK. Step 5 Click Query. At this time, the E-LAN service is already deleted. ----End
A.6.4 Managing the MAC Address Table

The MAC address table is the core of the E-LAN service. The OptiX RTN 950 provides various functions for managing the MAC address table. A.6.4.1 Creating a Static MAC Address Entry Through the creation of a static MAC address entry, the host with a specified MAC address is not affected by MAC address aging. In addition, the E-LAN service can be supported by the host that receives packets only. A.6.4.2 Creating a Blacklist Entry of MAC Addresses
A Task Collection
Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC address can be prohibited from using the E-LAN service. A.6.4.3 Configuring the Aging Parameters of a MAC Address Table By default, the aging function of a MAC address table is enabled and the aging time is five minutes. By configuring the aging parameters of a MAC address table, you can modify such parameters. A.6.4.4 Querying or Deleting a Dynamic MAC Address By querying or deleting a dynamic MAC address, you can query or delete all the MAC address entries that are learned by the E-LAN service.
A.6.4.1 Creating a Static MAC Address Entry

Through the creation of a static MAC address entry, the host with a specified MAC address is not affected by MAC address aging. In addition, the E-LAN service can be supported by the host that receives packets only.
Prerequisite
l l The E-LAN service must be created. The NE user must have the authority of Operation Level or higher.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be created. Step 3 Click the Static MAC Address tab. Step 4 Click New. The New Static MAC Address dialog box is displayed. Step 5 Configure the parameters of the static MAC address entry.
Related References
B.6.1.5 Parameter Description: E-LAN Service
A Task Collection
A.6.4.2 Creating a Blacklist Entry of MAC Addresses

Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC address can be prohibited from using the E-LAN service.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs to be created. Step 3 Click the Disabled MAC Address tab. Step 4 Click New. The New Disabled MAC Address dialog box is displayed. Step 5 Configure the blacklist entry of MAC addresses.
Related References
A.6.4.3 Configuring the Aging Parameters of a MAC Address Table

By default, the aging function of a MAC address table is enabled and the aging time is five minutes. By configuring the aging parameters of a MAC address table, you can modify such parameters.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC address table need to be configured. Step 3 Click the MAC Address Learning Parameters tab. Step 4 Configure the status of the aging function and set the aging time.
Related References
A.6.4.4 Querying or Deleting a Dynamic MAC Address

By querying or deleting a dynamic MAC address, you can query or delete all the MAC address entries that are learned by the E-LAN service.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be queried or cleared. Step 3 Click the Self-Learning MAC Address tab. Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check the dynamic MAC addresses in the MAC address table that is displayed. Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses. ----End
Related References
A Task Collection
A.6.5 Setting the Mode for Processing an Unknown Frame of the ELAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC address table or a multicast frame whose destination MAC address is not listed in the multicast group. By default, the NE broadcasts the unknown frame. By setting the mode for processing an unknown frame of the E-LAN service, you can change the processing mode so that unknown frame can be discarded.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frame needs to be set. Step 3 Click the Unknown Frame Processing tab. Step 4 Set the mode for processing an unknown frame of the E-LAN service.
Related References
A.6.6 Managing the MSTP

The OptiX RTN 950 supports only the MSTP that generates the CIST. A.6.6.1 Creating the MSTP Port Group When the NE needs to run the MSTP protocol together with the user network, the ports on the NE that are connected to the user network need to be configured as a port group. All the members in the port group are involved in the spanning tree algorithm of the user network. A.6.6.2 Setting the Bridge Parameters of the MSTP This topic describes how to set the bridge parameters and port parameters of the MSTP. A.6.6.3 Setting the Parameters of the CIST
A Task Collection
This topic describes how to set the CIST parameters, including the bridge priority, port priority, and path overheads. A.6.6.4 Querying the CIST Running Information By querying the CIST running information, you can be familiar with the current information of the CIST. A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP protocol) for the equipment that runs the spanning tree together with the local NE, you need to change the spanning tree protocol used by the port group on the local NE to be the same. A.6.6.6 Enabling/Disabling the MSTP Protocol This topic describes how to enable or disable the MSTP protocol of a port group or members of the port group. A.6.6.7 Modifying the Configuration Data of the MSTP Port Group This topic describes how to modify the configuration data of the MSTP port group.
A.6.6.1 Creating the MSTP Port Group

When the NE needs to run the MSTP protocol together with the user network, the ports on the NE that are connected to the user network need to be configured as a port group. All the members in the port group are involved in the spanning tree algorithm of the user network.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The boards where the member ports are located must be added in Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Click Create. Then, the Create Port Group dialog box is displayed. Step 4 Set the attributes of the port group. 1. 2. Set Protocol Type and Enable Protocol. Select the board where the member port is located from the drop-down list of Board under Apply Port. Select the member port from Available Port List. Then, click
TIP
3.
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting the ports.
Issue 03 (2011-04-10)
A-119
A Task Collection
4.
Click OK.
----End
Related References
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation
A.6.6.2 Setting the Bridge Parameters of the MSTP

This topic describes how to set the bridge parameters and port parameters of the MSTP.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The port group must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Bridge Parameters tab. Step 3 Select the port group ID. Step 4 Click the Bridge Parameters tab. Step 5 Set the attributes of the bridge.
Step 6 Click Apply. Step 7 Click the Port Parameter tab.

A Task Collection
Step 8 Set the parameters of each member of the port group.
Related References
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters
A.6.6.3 Setting the Parameters of the CIST

This topic describes how to set the CIST parameters, including the bridge priority, port priority, and path overheads.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The port group must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the CIST&MSTI Parameters tab. Step 3 Select the port group from the drop-down list of Port Group. Step 4 Set the parameters of the port group.
Issue 03 (2011-04-10)
A-121
A Task Collection
Related References
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters
A.6.6.4 Querying the CIST Running Information

By querying the CIST running information, you can be familiar with the current information of the CIST.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MSTP port group must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the CIST Running Information tab. Step 3 Click Query. Step 4 Query the CIST running information. ----End
A Task Collection
Related References
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group
When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP protocol) for the equipment that runs the spanning tree together with the local NE, you need to change the spanning tree protocol used by the port group on the local NE to be the same.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose spanning tree protocol needs to be changed.
A.6.6.6 Enabling/Disabling the MSTP Protocol

This topic describes how to enable or disable the MSTP protocol of a port group or members of the port group.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
A Task Collection
Step 2 Click the Port Group Parameters tab. Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for which the MSTP protocol needs to be enabled or disabled.
Step 4 Click Apply. Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to enable or disable the MSTP protocol of a port.
A.6.6.7 Modifying the Configuration Data of the MSTP Port Group

This topic describes how to modify the configuration data of the MSTP port group.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Click Config. Then, the Config Port Group dialog box is displayed. Step 4 Modify the configuration data of the MSTP port group. Option If... Description Then...
A-124
Issue 03 (2011-04-10)
A Task Collection
Option A member port needs to be added
Description 1. Select the board where the member ports are located from the drop-down list of Board. 2. Select the port to be added from Available Port List. 3. Click .
A member port needs to be deleted 1. Select the port to be deleted from Selected Port List. 2. Click .
TIP
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.
Related References
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration

By managing the QoS, you can provide the services of different levels for different service types. A.6.7.1 Creating a DS Domain By creating a DS domain, you can create the mapping relation of a new DS domain and configure the ports that use this mapping relationship. A.6.7.2 Modifying the Mapping Relationships for the DS Domain This topic describes how to modify the mapping relationships between packet priorities and PHB service classes in the ingress or egress direction of a DS domain.
A Task Collection
A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types This topic describes how to add or delete a port that uses the DS domain and set the packet type over the port. A.6.7.4 Creating a Port Policy By creating a port policy, you can create a scheduling, weight, and shaping of the egress queues. A.6.7.5 Modifying the Port Policy This section describes how to change the parameter values of a created port policy. A.6.7.6 Creating the Traffic By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream on a specified port. A.6.7.7 Setting the Port That Uses the Port Policy This section describes how to set the port that uses the port policy. A.6.7.8 Configuring Port Shaping This topic describes how to configure the traffic shaping for an egress port. A.6.7.9 Querying the Port Policy This topic describes how to query the port policy of a port. A.6.7.10 Querying the DS Domain of a Port This topic describes how to query the mapping relation between a port and a DS domain.
A.6.7.1 Creating a DS Domain

By creating a DS domain, you can create the mapping relation of a new DS domain and configure the ports that use this mapping relationship.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board of the Ethernet ports must be added on Slot Layout.

Web LCT
The OptiX RTN 950 has a default DS domain, whose Mapping Relation ID is 1 and Mapping Relation Name is default map.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Click New. The Create DS Mapping Relation dialog box is displayed. Step 3 On the main interface, configure the attributes of the DS domain.
NOTE
A Task Collection
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 4 Click the Ingress Mapping Relation tab. Step 5 Configure the mapping relations between the priorities of ingress packets and PHB service classes. Step 6 Click the Egress Mapping Relation tab. Step 7 Configure the mapping relations between the priorities of egress packets and PHB service classes. Step 8 Select Board where the application ports exist from Application Port. Step 9 Select a port from Available Port, and then click
TIP
Hold on the Ctrl key on the keyboard to select multiple ports.
NOTE
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
Issue 03 (2011-04-10)
A-127
A Task Collection
Related References
B.6.4.2 Parameter Description: DiffServ Domain Management_Create
A.6.7.2 Modifying the Mapping Relationships for the DS Domain

This topic describes how to modify the mapping relationships between packet priorities and PHB service classes in the ingress or egress direction of a DS domain.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Select the created DS domain and change its attributes on the main interface.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 3 Optional: Change the mapping relationship in the ingress direction. 1. 2. Click the Ingress Mapping Relation tab. Double-click the parameters whose values need to be changed and change the mapping relationship between the packet priorities and PHB classes in the ingress direction.
NOTE
3. 1. 2.
Click Apply. Click the Egress Mapping Relation tab. Double-click the parameters whose values need to be changed and change the mapping relationship between the packet priorities and PHB classes in the egress direction.
Step 4 Optional: Change the mapping relationship in the egress direction.
A-128
NOTE
A Task Collection
3.
Click Apply.
----End
Related References
B.6.4.1 Parameter Description: Diffserv Domain Management
A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types
This topic describes how to add or delete a port that uses the DS domain and set the packet type over the port.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Select the DS domain for which you need to add or delete an application port on the main interface. Step 3 Click the Apply Port tab. Step 4 Click Modify. Step 5 Add or delete a port that uses the DS domain. Option If...
Issue 03 (2011-04-10)
Description Then...
A Task Collection
Option You need to add a port that uses the DS domain
Description 1. Select the board where the application port is located from the drop-down list of Board. 2. Select the port to be added from the dropdown list of Available Port. 3. Click .
You need to delete a port that uses the DS 1. Select the board where the application port is domain located from the drop-down list of Board. 2. Select the port to be deleted from the port list of Selected Port. 3. Click You need to change the packet type identified by the port
TIP
Select a new packet type from the drop-down list of Packet Type.
A-130
Issue 03 (2011-04-10)
A Task Collection
NOTE
l C-VLAN indicates the client-side VLAN priority, and the value 7 indicates the highest priority. l S-VLAN indicates the server-side VLAN priority, and the value 7 indicates the highest priority. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet. l The packets trusted by the OptiX RTN 950 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS EXP value. By default, the untrusted packets are mapped to the BE service class for best-effort forwarding.
Related References
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification
A.6.7.4 Creating a Port Policy

By creating a port policy, you can create a scheduling, weight, and shaping of the egress queues.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board of the Ethernet ports must be added on Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree.
A Task Collection
Step 2 Create a port policy by adding a port policy on the NMS. 1. 2. 3. Click New. The Create Port Policy dialog box is displayed. Set the ID and name of the port policy. Configure the scheduling, weight, and shaping of the egress queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time. l The OptiX RTN 950 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE). l Policy Weight(%) specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l Bandwidth Limit indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled.
4.
Click OK.
Step 3 Create a port policy by duplicating an existing port policy. 1. 2. 3. 4. 5. Select a similar port policy and click Copy. Then, the Duplicate QoS Policy dialog box is displayed. Change the name of the port policy. Click OK. Select the duplicated port policy and change the scheduling, weight, and shaping of the egress queues. Click Apply.
----End
Related References
B.6.4.5 Parameter Description: Port Policy
A Task Collection
A.6.7.5 Modifying the Port Policy

This section describes how to change the parameter values of a created port policy.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The port policy must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Select the port policy whose parameter values need to be changed. Step 3 Double-click the parameters whose values need to be changed and change the queue scheduling, weight, and queue shaping of the port queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue has a certain period of service time. l The OptiX RTN 950 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE). l Policy Weight(%) specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l Bandwidth Limit indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled.
Related References
B.6.4.4 Parameter Description: Policy Management
A.6.7.6 Creating the Traffic

By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream on a specified port.
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout. The port policy must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Click the Traffic Classification Configuration tab. Step 3 Click New. The Create Traffic Classification dialog box is displayed. Step 4 Configure the attributes of a new traffic.
NOTE
Set the parameters according to the network planning information.

A Task Collection
Related References
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
A.6.7.7 Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout. The port policy must be created.
Tools, Instruments, and Materials

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Click the Applied Object tab. Step 3 Click Modify. Then, the Configure Port dialog box is displayed. Step 4 Set the port that uses the port policy. 1. 2. Select Board where the port that needs to use the port policy from Applied Port. Select a port from Available Port, and then click
TIP
3.
Issue 03 (2011-04-10)
Click OK.
A Task Collection
Step 5 Delete the port that uses the port policy. 1. Select the port to be deleted from Selected Port and click
TIP
2.
Click OK.
----End
Related References
A.6.7.8 Configuring Port Shaping

This topic describes how to configure the traffic shaping for an egress port.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be created on the Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 Click New. The New dialog box is displayed. Step 3 Set the parameters for the shaping of a port.
A Task Collection
NOTE
Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid. If the traffic shaping function is enabled, OptiX RTN 950 processes the packets in the buffer queue through the following methods when no packets are available in the queue. l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR.
Related References
B.6.4.7 Parameter Description: Port Shaping Management_Creation
A.6.7.9 Querying the Port Policy

This topic describes how to query the port policy of a port.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Select the created port policy. Step 3 Click the CoS Configuration tab. Step 4 Click Query.
A Task Collection
Step 5 Query the CoS configuration of the port policy. Step 6 Click the Traffic Classification Configuration tab. Step 7 Click Query. Step 8 Query the traffic classification of the port policy. Step 9 Click the Applied Object tab. Step 10 Click Query. Step 11 Query the ports that use the port policy. ----End
Related References
A.6.7.10 Querying the DS Domain of a Port

This topic describes how to query the mapping relation between a port and a DS domain.
Prerequisite

Web LCT
The OptiX RTN 950 has a default DS domain, whose Mapping Relation ID is 1 and Mapping Relation Name is default map. Before another DS domain is created, all the ports belong to this default DS domain.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Click the Ingress Mapping Relation tab. Step 3 Click Query. Step 4 Query the attributes of the DS domain and the mapping relation between the priority level of the packets in the ingress direction and the PHB service class. Step 5 Click the Egress Mapping Relation tab. Step 6 Click Query. Step 7 Query the attributes of the DS domain and the mapping relation between the priority level of the packets in the egress direction and the PHB service class.
A Task Collection
Step 8 Click the Apply Port tab. Step 9 Click Query. Step 10 Query the ports that use the DS domain. ----End
Related References
A.6.8 Using the IEEE 802.1ag OAM

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.6.8.1 Creating an MD A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different ranges and levels can provide users with differentiated OAM services. A.6.8.2 Creating an MA An MD can be divided into several independent maintenance associations (MAs). By creating MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM operations. A.6.8.3 Creating an MEP Point An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation. A.6.8.4 Creating Remote MEPs in an MA To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP. A.6.8.5 Creating an MIP The maintenance association intermediate points (MIPs) can respond to specific OAM packets. By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into several segments, therefore facilitating the detection of the Ethernet link. A.6.8.6 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source end, the sink equipment reports the corresponding alarm. A.6.8.7 Performing an LB Test During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MEP in the same maintenance association (MA). A.6.8.8 Performing an LT Test Based on the LB test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located according to the MIP through only one test. A.6.8.9 Activating the AIS After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP so that the higher level MP is informed of the fault information.
Issue 03 (2011-04-10)
A-139
A Task Collection
A.6.8.1 Creating an MD
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different ranges and levels can provide users with differentiated OAM services.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Choose New > New Maintenance Domain. The system displays the New Maintenance Domain dialog box. Step 4 Set the parameters of the MD.
NOTE
l Maintenance Domain Level specifies the level of the maintenance domain. l The values 0-2 indicate the carrier level, the values 3-4 indicate the supplier level, and the values 5-7 indicate the user level. l When the value is set to 0, the maintenance domain is at the lowest level. The values 0-7 indicate that the level increases in a sequential order. l The OAM packets whose level is higher than the preset value are transparently transmitted by the MEPs. The OAM packets whose level is lower than the preset value are directly discarded by the MEPs. The OAM packets whose level is the same as the preset value are responded to or terminated by the MEPs according to the message type.
Related References
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
A.6.8.2 Creating an MA
An MD can be divided into several independent maintenance associations (MAs). By creating MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM operations.
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MD must be created. The Ethernet service must be created.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association. The system displays the New Maintenance Association dialog box. Step 4 Set the parameters of the MA.
NOTE
Click
in Relevant Service. Select the corresponding services in the dialog box that is displayed.
Related References
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation

An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MA must be created.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point. The system displays the New MEP Point dialog box. Step 4 Set the parameters of the MEP point.
NOTE
l Each MEP needs to be configured with an MP ID, which is unique in the maintenance association. The MP ID is required in the OAM operation. l Direction specifies the direction of the MEP. l Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates the direction in which the packets are transmitted from the port. l In the case of the tests based on the MP IDs, CC Status must be set to Active.
Related References
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
Prerequisite
l l
A-142
The NE user must have the authority of Operation Level or higher. The MA must be created.
A Task Collection

Web LCT
PORT 10 on the EFP8 board does not support this operation.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Step 4 Click New. Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed. Step 5 Set the parameters of the new remote MEPs.
NOTE
If other MEPs may initiate OAM operations to an MEP in the same MA, set the other MEPs to be the remote MEPs.
Related References
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
A.6.8.5 Creating an MIP

The maintenance association intermediate points (MIPs) can respond to specific OAM packets. By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into several segments, therefore facilitating the detection of the Ethernet link.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MA must be created.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the MIP Point tab. Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New. Then, the New MIP Maintenance Point dialog box is displayed. Step 4 Set the parameters of the new MIP.
NOTE
l Each MIP needs to be configured with an MP ID, which is unique in the maintenance domain. The MP ID is required in the OAM operation. l To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the level of the MIP must be higher than the level of the MEP.
Related References
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
A.6.8.6 Performing a CC Test

After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source end, the sink equipment reports the corresponding alarm.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MEP must be created. The remote MEPs must be created.

Web LCT
l l Only the MEP can enable the CC test and function as the receiving and responding end in the test. During the CC check, the source MEP constructs and transmits continuity check message (CCM) packets periodically. After receiving the CCM packets from the source MEP, the
A-144
A Task Collection
sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to receive the CCM packets from the source MEP within the check period (that is, 3.5 times of the transmit period), it reports the alarm automatically. l Performing a CC test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate CC.
NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements. l To disable a CC test, select the MEP where the CC test is performed and then choose OAM > Deactivate.
----End
A.6.8.7 Performing an LB Test

During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MEP in the same maintenance association (MA).
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs in the same maintenance domain must be created. The remote MEPs must be created. The CC function must be enabled.

Web LCT
l l Only MEPs can initiate the LB test and function as the receive end in the test. During the LB test, the source MEP constructs and transmits the LBM frames and starts the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the source MEP. This indicates that the loopback is successful. If the source MEP timer times out, it indicates that the loopback fails. Performing an LB test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab.
A Task Collection
Step 3 Select the maintenance domain and maintenance association for the LB test. Step 4 Choose OAM > Start LB. Then, the LB Test dialog box is displayed. Step 5 Select the method for identifying the destination MP and set the parameters involved in the LB test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set to the Destination Maintenance Point ID. l To identify the destination MP according to the MAC address, select Maintenance Point MAC Address. Only the MAC address of the MEP can be set to the MAC address of the Destination Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window. ----End
Related References
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
A.6.8.8 Performing an LT Test

Based on the LB test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located according to the MIP through only one test.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs in the same MD must be created. The remote MEPs must be created. The CC function must be enabled.

Web LCT
l l Only MEPs can initiate the LT test and work as the termination point in the test. During the LT test, the source MEP constructs and transmits the LTM frames and starts the timer. All the MPs that receive the LTM frames send the LTR frame response. According to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the sink MEP.
A-146
A Task Collection
Performing an LT test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance domain and maintenance association for the LT test. Step 4 Choose OAM > Start LT. Then, the LT Test dialog box is displayed. Step 5 Select the method for identifying the destination MP and set the parameters involved in the LT test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set to the Destination Maintenance Point ID. l To identify the destination MP according to the MAC address, select Maintenance Point MAC Address. Only the MAC address of the MEP can be set to the MAC address of the Destination Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window. ----End
Related References
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
A.6.8.9 Activating the AIS

After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP so that the higher level MP is informed of the fault information.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs in the same MD must be created.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the MD and MA where the MEP is located. Step 4 Select the node to be monitored. Double-click or right-click AIS Active Status and then select Active or Inactive. Step 5 Click Apply. ----End
A.6.9 Using the IEEE 802.3ah OAM

By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links. A.6.9.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link. A.6.9.2 Enabling the Remote Alarm Support for Link Event After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed. A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Generally, the default value is used. You can modify the value according to the situation of the link. A.6.9.4 Performing Remote Loopback After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data. A.6.9.5 Enabling Self-Loop Detection After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.
A.6.9.1 Enabling the OAM Auto-Discovery Function

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisite

Web LCT
The OAM auto-discovery is realized through the auto-negotiation between the local equipment and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
A Task Collection
the OAM auto-discovery succeeds, the link performance is monitored according to the error frame threshold. You can set the error frame threshold on the NMS.
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the port, and set OAM Working Mode.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery fails. l If both ends of a link are in passive OAM mode, a link fault occurs, or either end of a link does not receive OAM protocol packets within 5 seconds, an alarm is reported, indicating that OAM autodiscovery fails.
Step 4 Set Enable OAM Protocol to Enabled.
Step 5 Click Apply. Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the opposite end. ----End
Related References
B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter
A.6.9.2 Enabling the Remote Alarm Support for Link Event

After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The OAM auto-discovery operation must successful on the equipment at both ends.

Web LCT
A Task Collection
After the OAM auto-discovery operation is successful at both ends, the link fault detection and performance detection are automatically started. l l To report the detected link fault event to the opposite equipment, you need to set Remote Alarm Support for Link Event to Enabled for the local equipment. To report the detected link fault event to the opposite equipment, you need to set Remote Alarm Support for Link Event to Enabled and set Error Frame Period Window (ms) and Error Frame Monitor Threshold (frame) for the local equipment. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the ETH_EFM_EVENT alarm, which is reported on the local end, by using the NMS. According to the alarm, you can determine the type of the link performance event. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite equipment detects a link fault event, you can query the ETH_EFM_REMFAULT alarm, which is reported at the local end, by using the NMS. According to the alarm, you can determine the fault type.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the corresponding port and set Remote Alarm Support for Link Event to Enabled.
Related References
A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold

The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Generally, the default value is used. You can modify the value according to the situation of the link.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM auto-discovery operation must be successful on the equipment at both ends.
A-150
A Task Collection

Web LCT
After the OAM auto-discovery operation is successful, the remote link event notification function is enabled and the monitoring time and errored frame threshold are set at the local end. If the local equipment detects a link event in the receive direction, it informs the opposite equipment of the link event. If the remote alarm for the link event is also supported at the opposite end, the opposite equipment can also inform the local equipment of the link event that is detected at the opposite end. Then, the corresponding alarm is reported at the local end.
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Error Frame Monitor tab. Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
NOTE
An alarm is reported if the number of errored frame events within Monitor Window or Period Window exceeds the specified monitoring threshold.
Related References
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
A.6.9.4 Performing Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.
Prerequisite
l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. The OAM auto-discovery operation must be successful at both ends of the link.
A Task Collection
l l
On the equipment that initiates the loopback, OAM Working Mode must be set to Active. The equipment that responds to the loopback must support the remote loopback.

Web LCT
l If a port is capable of responding to loopbacks, it enters the loopback responding state and reports the loopback responding alarm after receiving the command of enabling the remote loopback function sent from the opposite OAM port. In this case, the equipment that initiates the loopback enters the loopback initiating state and reports the loopback initiating alarm. Generally, after the remote loopback function is enabled, service packets, except the OAMPDU, are looped back at the remote end. After using the remote loopback function to complete the fault locating and the link performance detection, you need to disable the remote loopback function at the end where the loopback is initiated and then restore the services. At this time, the alarm is automatically cleared.
NOTE
l l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 4 Click Apply. Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM.
NOTE
To release remote loopbacks, select Disable Remote Loopback.
----End
A Task Collection
A.6.9.5 Enabling Self-Loop Detection

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The required board is already added on the Slot Layout. All the external physical ports on the Ethernet service processing board must be enabled.

Web LCT
l l After the loopback detection is enabled at an Ethernet port, the ETHOAM_SELF_LOOP alarm is reported if a loopback occurs at the port. On the EFP8 board, only PORT 10 supports this operation.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Set Loopback Check to Enabled. Step 4 Click Apply. ----End
A.6.10 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and the related information of LPT ports. A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network When you configure point-to-point LPT traversing an L2 network, it is unnecessary to bind LPT with Ethernet services. A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network When you configure point-to-point LPT traversing a PSN or QinQ network, it is necessary to bind LPT with services. A.6.10.3 Configuring Point-to-Multipoint LPT When you configure point-to-multipoint LPT, it is necessary to configure the primary and secondary points. A.6.10.4 Configuring Simple LPT If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically disabled through the LPT function.
A Task Collection
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network

When you configure point-to-point LPT traversing an L2 network, it is unnecessary to bind LPT with Ethernet services.
Prerequisite
l l The NE user must have the authority of System Level or higher. L2 services are configured.
NOTE
L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point manner.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Step 2 Click the Point-to-Point LPT tab. Step 3 Click Bind in the lower right corner of the pane based on the type of service network. Step 4 Choose L2 net from the shortcut menu. The Bind L2 net dialog box is displayed. Step 5 Set the parameters of the primary and secondary points of LPT.
Step 6 Click OK. Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 8 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
A Task Collection
A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network

When you configure point-to-point LPT traversing a PSN or QinQ network, it is necessary to bind LPT with services.
Prerequisite
l l l The NE user must have the authority of System Level or higher. QinQ services exclusively occupying UNI ports have been configured. E-Line services carried by PWs exclusively occupying UNI ports have been configured.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in 7.1.5.3 QinQ-Based E-Line Services. l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3 in 10.1.1.3 E-Line Services Carried on PWs.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Step 2 Click the Point-to-Point LPT tab. Step 3 Select PW or QinQ services that require the LPT function. Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut menu. Step 5 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 6 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
A.6.10.3 Configuring Point-to-Multipoint LPT

When you configure point-to-multipoint LPT, it is necessary to configure the primary and secondary points.
Prerequisite
l l The NE user must have the authority of System Level or higher. At least one of the following services has been configured. L2 services
A Task Collection
QinQ services sharing UNI ports E-Line services carried by PWs sharing UNI ports
NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-tomultipoint manner. l For the service models of QinQ services sharing UNI ports, see Model 3 in 7.1.5.3 QinQ-Based E-Line Services. l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in 10.1.1.3 E-Line Services Carried on PWs.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Step 2 Click the Point-to-Multipoint LPT tab. Step 3 Click New in the lower right corner of the pane based on the type of service network. Step 4 Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network. The Create LPT dialog box is displayed. Step 5 Set the parameters of the primary and secondary points of LPT. Step 6 Click OK. Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 8 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT
A.6.10.4 Configuring Simple LPT

If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically disabled through the LPT function.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding board must be added to the Slot Layout.

Web LCT
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > Simple LPT from the Function Tree. Step 2 Click New. The Create LPT dialog box is displayed.
Step 3 Configure the board and port of the Convergence Point. Step 4 Set Access Point. 1. 2. In the Board list, select the board of the access point. In Port, select the required port, and then click .
A.7 Configuring Ethernet Services and Features on the EoPDH Plane

Configurations of Ethernet services and features on the EoPDH plane include relevant Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.7.1 Managing LAGs Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved.
A Task Collection
A.7.2 Configuring Ethernet Services The EFP8 board supports EPL, EVPL, EPLAN, and EPVLAN services. A.7.3 Managing the MAC Address Table The MAC address table is the core of the Ethernet LAN service. The EFP8 board provides various functions for managing the MAC address table. A.7.4 Configuring Ethernet Ports The EFP8 board supports external FE ports and internal VCTRUNK ports. A.7.5 Managing the Spanning Tree Protocol The OptiX RTN OptiX RTN 950 supports Spanning Tree Protocol (STP) and Rapid Spanning Tree Protocol (RSTP). A.7.6 Managing the IGMP Snooping Protocol If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to implement the multicast function together with the router. A.7.7 Managing the QoS By managing the QoS, you can provide differentiated services for different service types. A.7.8 Using the IEEE 802.1ag OAM By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.7.9 Using the IEEE 802.3ah OAM By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links. A.7.10 Configuring LPT After enabling the LPT function for an Ethernet service, you need to configure the LPT port and the relevant information.
A.7.1 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved. A.7.1.1 Creating a LAG To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG. A.7.1.2 Setting Parameters for LAGs The parameters for a LAG include port priorities and system priorities. In a static LAG that uses the static aggregation mode, a port with a higher priority is always selected for transmitting services. A.7.1.3 Querying the Protocol Information of LAGs This section describes how to learn about the running information of the LACP protocol used by LAGs.

To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG.
A-158
Issue 03 (2011-04-10)
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The EFP8 board where the LAG ports are located must be added in the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New. The Create Link Aggregation Group dialog box is displayed. Step 4 In Attributes Settings, set the parameters of the LAG.
Step 5 In Port Settings, set the LAG ports. 1. 2. Set Main Port. Select a slave port from Available Standby Ports and then click
TIP
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.
Issue 03 (2011-04-10)
A-159
A Task Collection
Step 6 Click OK. A confirmation dialog box is displayed. Step 7 Click OK. ----End
Related References
B.7.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs

The parameters for a LAG include port priorities and system priorities. In a static LAG that uses the static aggregation mode, a port with a higher priority is always selected for transmitting services.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Parameters tab. Step 3 Set the parameters associated with the system priority and port priority.
A-160
Issue 03 (2011-04-10)
A Task Collection
Related References
A.7.1.3 Querying the Protocol Information of LAGs

This section describes how to learn about the running information of the LACP protocol used by LAGs.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 In the main interface, select the LAG to be queried. Step 4 Click Query to check the working status of the main and slave ports in the LAG.
NOTE
The system automatically displays the working status of the slave port at the bottom of the main interface.
Step 5 Right-click the LAG and select an option from the drop-down list. A dialog box is displayed, indicating the query result.
Step 6 Click Close. Step 7 Click the Link Aggregation Parameters tab. Step 8 Click Query to check the parameters associated with the port priority and system priority. ----End
A.7.2 Configuring Ethernet Services

The EFP8 board supports EPL, EVPL, EPLAN, and EPVLAN services.
A Task Collection
A.7.2.1 Creating Ethernet Private Line Services This section describes how to create EPL services and VLAN-based EVPL services. A.7.2.2 Creating Ethernet LAN Services This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services. A.7.2.3 Changing the Ports Connected to a VB This section describes how to change the ports connected to a VB, the enabling status of the ports, and Hub/Spoke attribute of the ports. A.7.2.4 Creating the VLAN Filtering Table To create an Ethernet LAN service in IVL learning mode, you need to create the VLAN filtering table for the VB. A.7.2.5 Creating QinQ-Based EVPL Services When creating a QinQ-based EVPL service, you need to set service information such as the service source, service sink, and QinQ type. A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant service information, including the attributes of the bridge and the ports that are connected to the bridge. A.7.2.7 Deleting an Ethernet Private Line Service When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources. A.7.2.8 Deleting an Ethernet LAN Service When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources.
A.7.2.1 Creating Ethernet Private Line Services

This section describes how to create EPL services and VLAN-based EVPL services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout.

Web LCT
Precautions
For the method of creating QinQ-based Ethernet private line services, see A.7.2.5 Creating QinQ-Based EVPL Services.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
A Task Collection
Step 2 Deselect Display QinQ Shared Service. Step 3 Click New. The Create Ethernet Line Service dialog box is displayed. Step 4 Set the attributes of the Ethernet private line service.
Step 5 Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the same as the result of directly setting the Ethernet service port attributes.
Step 6 Optional: Set the bound path. 1. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path.
Issue 03 (2011-04-10)
A-163
A Task Collection
2. 3. 4.
In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Direction of the bound path. Select required items in Available Resources and Available Timeslots and click .
5. 6. 7.
Optional: Repeat Step 6.4 to bind other VC paths. Click OK. A confirmation dialog box is displayed. Click OK.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the result of directly setting the attributes of VCTRUNKs.
Related References
B.7.1.1 Parameter Description: Ethernet Line Service_Creation
A.7.2.2 Creating Ethernet LAN Services

This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services.
Prerequisite
l l
A-164
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout.
A Task Collection

Web LCT
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the bridge according to the bridge type. l Set the attributes of the IEEE 802.1q bridge.
l Set the attributes of the IEEE 802.1d bridge.
Issue 03 (2011-04-10)
A-165
A Task Collection
Step 4 Set the ports to be connected to the bridge. 1. 2. Click Configure Mount. The Service Mount Configuration dialog box is displayed. Select a port from the ports listed in Available Mounted Ports, and then click . 3. Optional: Repeat Step 4.2 to mount other ports.
A-166
Issue 03 (2011-04-10)
A Task Collection
4. 1.
Click OK. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path.
Step 5 Optional: Set the bound path.
2. 3. 4.
5.
Issue 03 (2011-04-10)
Optional: Repeat Step 5.4 to bind other VC paths.

A Task Collection
6. 7.
Click OK. A confirmation dialog box is displayed. Click OK.

NOTE
Related References
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/802.1q Bridge

This section describes how to change the ports connected to a VB, the enabling status of the ports, and Hub/Spoke attribute of the ports.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Ethernet LAN services must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the VB that is already created, and click the Service Mount tab.
Step 3 Change the ports connected to the VB. 1. 2. To delete a mounted port, double-click the port under Mount Port and select Unconnected from the drop-down list. To add a mounted port, double-click the cell without any port under Mount Port and select the port to be connected to the VB.
Step 4 To change any parameter value of a mounted port, double-click the parameter value and specify a new value. Step 5 Click Apply. ----End
A Task Collection

To create an Ethernet LAN service in IVL learning mode, you need to create the VLAN filtering table for the VB.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created. In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB must be IVL.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab. Step 3 Create the VLAN filtering table. 1. 2. 3. Click New. The Create VLAN dialog box is displayed. Set VLAN ID(e.g:1,3-6). Select a port from the ports listed in Available forwarding ports, and then click . 4. Optional: Repeat Step 3.3 to select other forwarding ports.
5.
Click OK.
----End
Related References
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation
A Task Collection
A.7.2.5 Creating QinQ-Based EVPL Services

When creating a QinQ-based EVPL service, you need to set service information such as the service source, service sink, and QinQ type.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Select Display QinQ Shared Service. Step 3 Click New. The Create Ethernet Line Service dialog box is displayed. Step 4 Set the attributes of the QinQ-based EVPL service.
A-170
Issue 03 (2011-04-10)
A Task Collection
Step 5 Optional: Set the port attributes.

NOTE
Issue 03 (2011-04-10)
A-171
A Task Collection
2. 3. 4.
5. 6. 7.
NOTE
Related References
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services
A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant service information, including the attributes of the bridge and the ports that are connected to the bridge.
Prerequisite
l
A-172

A Task Collection
The EFP8 board must be added in the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the basic attributes of the IEEE 802.1ad bridge.
Step 4 Set service mounting relationships. 1. 2. 3. Click Configure Mount. The Service Mount Configuration dialog box is displayed. Set the parameters for configuring mounted services. Click Add Mount Port.
Issue 03 (2011-04-10)
A-173
A Task Collection
4. 5. 6.
Repeat Step 4.2 and Step 4.3 to add the other mounted ports. Click OK. Optional: You can change the Ethernet port attributes of the mounted ports in the Service Mount window.
2. 3.
A-174
In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Direction of the bound path.
A Task Collection
4.
Select required items in Available Resources and Available Timeslots and click .
5. 6. 7.
NOTE
Related References
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
A.7.2.7 Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet private line service must be configured and the service is not used.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click Query. Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete. A confirmation dialog box is displayed. Step 4 Click OK. Step 5 Click Query. At this time, the Ethernet private line service is already deleted. ----End
A.7.2.8 Deleting an Ethernet LAN Service

When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet LAN services must be configured and the service is not used.

Web LCT
Deleting an Ethernet LAN service involves the following tasks: 1. 2. Deleting the VLAN filtering table Deleting the service mounting configuration
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click Query. Step 3 Click the VLAN Filtering tab. Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete. A confirmation dialog box is displayed. Step 5 Click OK. Step 6 Click the Service Mount tab. Step 7 Select the Ethernet LAN service to be deleted and click Delete. A confirmation dialog box is displayed. Step 8 Click OK. Step 9 Click Query. At this time, the Ethernet LAN service is already deleted. ----End
A.7.3 Managing the MAC Address Table

The MAC address table is the core of the Ethernet LAN service. The EFP8 board provides various functions for managing the MAC address table. A.7.3.1 Creating a Static MAC Address Entry By performing this operation, you can ensure that the hosts with specific MAC addresses are not affected after the MAC addresses are aged and that Ethernet LAN services are also applicable to the hosts only receiving and not transmitting packets. A.7.3.2 Creating a Blacklist Entry of a MAC Address By performing this operation, you can ensure that the hosts with specific MAC addresses cannot use Ethernet LAN services. A.7.3.3 Setting the Aging Time of a MAC Address Table Entry The aging time of a MAC address table is five minutes by default.
A Task Collection
A.7.3.4 Querying or Deleting a Dynamic MAC Address This section describes how to query and delete self-learnt MAC addresses of Ethernet LAN services. A.7.3.5 Querying the Actual Capacity of a MAC Address Table This section describes how to query the actual capacity of a MAC address table.
A.7.3.1 Creating a Static MAC Address Entry

By performing this operation, you can ensure that the hosts with specific MAC addresses are not affected after the MAC addresses are aged and that Ethernet LAN services are also applicable to the hosts only receiving and not transmitting packets.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the VLAN Unicast tab. Step 3 Click New. The Create VLAN Unicast dialog box is displayed. Step 4 Set the parameters of the unicast entries.
Related References
B.7.1.6 Parameter Description: Ethernet LAN Service
A.7.3.2 Creating a Blacklist Entry of a MAC Address

By performing this operation, you can ensure that the hosts with specific MAC addresses cannot use Ethernet LAN services.
A Task Collection
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the created bridge and click the Disable MAC Address tab. Step 3 Click New. The Disable MAC Address Creation dialog box is displayed. Step 4 Set the parameters of the disabled MAC address entries.
Related References
A.7.3.3 Setting the Aging Time of a MAC Address Table Entry

The aging time of a MAC address table is five minutes by default.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree.
A Task Collection
Step 2 Modify the aging time of the MAC address table entry. 1. 2. Double-click MAC Address Aging Time corresponding to the EFP8 board. The MAC Address Aging Time dialog box is displayed. Set the duration and unit of the aging time.
3.
Click OK.
Related References
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries
A.7.3.4 Querying or Deleting a Dynamic MAC Address

This section describes how to query and delete self-learnt MAC addresses of Ethernet LAN services.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the created bridge and click the Self-learning MAC Address tab. Step 3 Click First Page, Previous, or Next to view the dynamic entries of a MAC address table page by page. Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC address. ----End
Related References
A.7.3.5 Querying the Actual Capacity of a MAC Address Table

This section describes how to query the actual capacity of a MAC address table.
A Task Collection
Prerequisite

Web LCT
Precautions
l In the case of EVPLAN services, you can query the capacity of a MAC address table where MAC addresses are queried based on VLAN IDs and the capacity of a MAC address table where MAC addresses are queried based on VB logical ports. In the case of EPLAN services, you can query the capacity of a MAC address table where MAC addresses are queried based on VB logical ports.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select a created bridge. Step 3 Query the actual number of dynamically learnt MAC addresses based on the VLAN IDs. 1. 2. 1. 2. Click the VLAN MAC Address Table Capacity tab. Click Query. Check the actual capacity of the MAC address table. Click the VB Port MAC Address Table Capacity tab. Click Query. Check the actual capacity of the MAC address table.
Step 4 Query the actual number of dynamically learnt MAC addresses based on the VB ports.
----End
Related References
A.7.4 Configuring Ethernet Ports

The EFP8 board supports external FE ports and internal VCTRUNK ports. A.7.4.1 Configuring External Ethernet Ports When an NE uses external ports on the EFP8 board to support access of Ethernet services, you need to set the attributes of the external ports so that external ports can work with the data communication equipment on the client side and therefore support normal access of Ethernet services. A.7.4.2 Configuring VCTRUNKs on an Ethernet Board When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) on an Ethernet board, you need to set the attributes of the VCTRUNK so that the Ethernet board works with the Ethernet board at the opposite end to implement transmission of the Ethernet services on the network.
A Task Collection
A.7.4.3 Modifying the Type Field of QinQ Frames The default type field of QinQ frames is 0x8100. A.7.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth When the LCAS function is enabled on an NE, you can dynamically increase or decrease the paths bound with a VCTRUNK to increase or decrease the bandwidth. The operation does not affect services.
A.7.4.1 Configuring External Ethernet Ports

When an NE uses external ports on the EFP8 board to support access of Ethernet services, you need to set the attributes of the external ports so that external ports can work with the data communication equipment on the client side and therefore support normal access of Ethernet services.
Prerequisite

Web LCT
Precautions
l l l Ethernet ports FE1-FE8 on the EFP8 board correspond to PORT1-PORT8 respectively. PORT9 on the EFP8 board is used to connect the EoPDH plane to the packet plane. PORT9 is provided by the Ethernet switching unit of the EFP8 board and is connected to the EoPDH plane. PORT9 forwards the Ethernet services from the packet plane to FE ports or VCTRUNKs on the EFP8 board.
Procedure
Step 1 In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select External Port. Step 3 Set the basic attributes of the port. 1. 2. Click the Basic Attributes tab. Set the basic attributes of the port.
3.
Click Apply.
Step 4 Set the flow control mode of the port. 1. 2. Click the Flow Control tab. Set the flow control mode of the port.
Issue 03 (2011-04-10)
A-181
A Task Collection
3. 1. 2.
Click Apply. Click the TAG Attributes tab. Set the TAG attribute of the port.
Step 5 Set the TAG attribute of the port.
3. 1. 2.
Click Apply. Click the Network Attributes tab. Set the network attributes of the port.
Step 6 Set the network attributes of the port.
3. 1. 2.
Click Apply. Click the Advanced Attributes tab. Set the advanced attributes of the port.
Step 7 Set the advanced attributes of the port.
3.
Click Apply.
----End
Related References
B.7.5.1 Parameter Description: Ethernet Port_External Port
A.7.4.2 Configuring VCTRUNKs on an Ethernet Board

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) on an Ethernet board, you need to set the attributes of the VCTRUNK so that the Ethernet board works with the Ethernet board at the opposite end to implement transmission of the Ethernet services on the network.
Prerequisite

Web LCT
Precautions
The EFP8 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be transmitted depending on information about the created Ethernet services.
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select Internal Port. Step 3 Optional: Set the TAG attribute of the VCTRUNK. 1. 2. Click the TAG Attributes tab. Set the TAG attribute of the VCTRUNK.
3.
Click Apply.
Step 4 Set the encapsulation and mapping protocol used by the VCTRUNK. 1. 2. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters.
3.
Click Apply.
Step 5 Optional: Set the network attributes of the VCTRUNK. 1. 2. Click the Network Attributes tab. Set the network attributes of the VCTRUNK.
3.
Click Apply.
Step 6 Configure the LCAS function for the port. 1. 2. Click the LCAS tab. Set the Enabling LCAS parameter and other LCAS parameters.
3.
Click Apply.
Step 7 Click Bound Path. Step 8 Optional: Set the bound path. 1. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path.
Issue 03 (2011-04-10)
A-183
A Task Collection
2. 3. 4.
5. 6. 7.
NOTE
----End
Related References
B.7.5.2 Parameter Description: Ethernet Port_Internal Port
A.7.4.3 Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree. Step 2 Modify the type field of QinQ frames.
Related References
B.7.5.3 Parameter Description: Type Field of QinQ Frames
A.7.4.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the paths bound with a VCTRUNK to increase or decrease the bandwidth. The operation does not affect services.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select Internal Port. Step 3 Click the Bound Path tab. Step 4 Click Configuration. The Bound Path Configuration dialog box is displayed. Step 5 Optional: Dynamically increase the VCTRUNK bandwidth. 1. 2. 3. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click .
A Task Collection
4.
Optional: Repeat Step 5.3 to bind other VC paths.
Step 6 Optional: Dynamically decrease the VCTRUNK bandwidth. 1. 2. 3. Deselect the Display in Combination check box. Select the VC paths to be deleted in Selected Bound Paths, and then click Optional: Repeat Step 6.2 to delete other VC paths. .
Step 7 Click OK. A confirmation dialog box is displayed. Step 8 Click OK. ----End
A.7.5 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 950 supports Spanning Tree Protocol (STP) and Rapid Spanning Tree Protocol (RSTP). A.7.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the bridge. A.7.5.2 Setting the Parameters of Spanning Tree Protocol If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment. A.7.5.3 Querying the Running Information About the Spanning Tree Protocol This topic describes how to query the running information about the spanning tree protocol (STP).
A Task Collection
A.7.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the bridge.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Click the Protocol Enabled tab. Step 3 Set Protocol Enabled and Protocol Type.
Step 4 Click Apply. A confirmation dialog box is displayed. Step 5 Click OK. ----End
Related References
B.7.2.1 Parameter Description: Spanning Tree_Protocol Enabling
A.7.5.2 Setting the Parameters of Spanning Tree Protocol

If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Set bridge parameters. 1. 2. Click the Bridge Parameters tab. Set bridge parameters.
3. 1. 2.
Click Apply. Click the Port Parameters tab. Set port parameters.
Step 3 Set port parameters.
3.
Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of the Ethernet port. 1. 2. Click the Point to Point Attribute tab. Set the point-to-point attribute of the port.
3.
Click Apply.
----End
Related References
B.7.2.2 Parameter Description: Spanning Tree_Bridge Parameters B.7.2.3 Parameter Description: Spanning Tree_Port Parameters B.7.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute
A.7.5.3 Querying the Running Information About the Spanning Tree Protocol
This topic describes how to query the running information about the spanning tree protocol (STP).
Prerequisite
l l l
A-188
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created.
A Task Collection
The STP or RSTP must be enabled for the bridge.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Query the bridge running information. 1. 2. 3. Click the Bridge Running Information tab. Click Query. Check the bridge running information.
Step 3 Query the port running information. 1. 2. 3. Click the Port Running Information tab. Click Query. Check the port running information.
----End
Related References
B.7.2.4 Parameter Description: Spanning Tree_Bridge Running Information B.7.2.5 Parameter Description: Spanning Tree_Port Running Information
A.7.6 Managing the IGMP Snooping Protocol

If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to implement the multicast function together with the router. A.7.6.1 Configuring the IGMP Snooping Protocol This section describes how to enable the IGMP Snooping protocol for a bridge and how to configure the method for the bridge to process unknown multicast packets. A.7.6.2 Configuring Static Multicast Entries This section describes how to configure and query information about static multicast entries. A.7.6.3 Modifying the Aging Time of a Multicast Table Entry The aging time of a MAC address table is eight minutes by default. A.7.6.4 Querying the Running Information of the IGMP Snooping Protocol By performing this operation, you can learn the information about the multicast table entries and router port when the bridge runs the IGMP Snooping protocol.
A.7.6.1 Configuring the IGMP Snooping Protocol

This section describes how to enable the IGMP Snooping protocol for a bridge and how to configure the method for the bridge to process unknown multicast packets.
A Task Collection
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created. The VLAN filtering table must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Enable IGMP Snooping Protocol tab. Step 3 Set the information about the IGMP Snooping protocol.
Related References
B.7.2.7 Parameter Description: IGMP Snooping Protocol_Enabling
A.7.6.2 Configuring Static Multicast Entries

This section describes how to configure and query information about static multicast entries.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created. The VLAN filtering table must be created. The IGMP Snooping protocol must be enabled for the bridge.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Static Multicast Table tab.
A Task Collection
Step 3 Click New. The Create Static Multicast Item dialog box is displayed. Step 4 Set the attributes of static multicast entries. 1. 2. Set VB ID, VLAN ID, and MAC Address. In Multicast Port, select the member ports corresponding to the static multicast entries. Click
TIP
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.
3.
Click OK.
----End
Related References
B.7.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries
A.7.6.3 Modifying the Aging Time of a Multicast Table Entry

The aging time of a MAC address table is eight minutes by default.
Prerequisite
l l l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created. The IGMP Snooping protocol must be enabled for the bridge.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Multicast Aging Time tab. Step 3 Modify the aging time of the multicast table entries.
Related References
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries
A.7.6.4 Querying the Running Information of the IGMP Snooping Protocol

By performing this operation, you can learn the information about the multicast table entries and router port when the bridge runs the IGMP Snooping protocol.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet LAN services must be created. The IGMP Snooping protocol must be enabled for the bridge.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Query the information about the router port. 1. 2. Click the Multicast Router Port Management tab. Click Query. Check the information about the router port.
Step 3 Query the information about the multicast table entries. 1.

A-192
Click the Multicast Table Item tab.

A Task Collection
2.
Click Query. Check the information about the multicast table entries.
----End

By managing the QoS, you can provide differentiated services for different service types. A.7.7.1 Creating a Flow A flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations. A.7.7.2 Creating the CAR CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR allocates the packets whose rates do not exceed the specified rate with higher priorities and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network. A.7.7.3 Creating the CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. A.7.7.4 Binding the CAR/CoS To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS. A.7.7.5 Configuring Traffic Shaping for Egress Queues This section describes how to enable traffic shaping for egress queues and how to set shapingassociated parameters.
A.7.7.1 Creating a Flow

A flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The associated Ethernet services must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab.
A Task Collection
Step 3 Click New. The New Flow dialog box is displayed. Step 4 Set the flow parameters.
Related References
B.7.4.1 Parameter Description: QoS Management_Creation of Flows
A.7.7.2 Creating the CAR

CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR allocates the packets whose rates do not exceed the specified rate with higher priorities and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CAR Configuration. Step 3 Click New. The New CAR dialog box is displayed. Step 4 Set the CAR parameters.
A-194
Issue 03 (2011-04-10)
A Task Collection
Related References
B.7.4.2 Parameter Description: QoS Management_Creation of CAR
A.7.7.3 Creating the CoS

By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CoS Configuration tab. Step 3 Click New. The New CoS dialog box is displayed. Step 4 Set the CoS parameters.
Issue 03 (2011-04-10)
A-195
A Task Collection
A-196
Issue 03 (2011-04-10)
A Task Collection
Related References
B.7.4.3 Parameter Description: QoS Management_Creation of CoS
A.7.7.4 Binding the CAR/CoS

To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The flow must be created. The CAR/CoS must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab.
A Task Collection
Step 3 Double-click Bound CAR and select the CAR to be bound. Step 4 Double-click Bound CoS and select the CoS to be bound. Step 5 Click Apply. ----End
Related References
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS
A.7.7.5 Configuring Traffic Shaping for Egress Queues

This section describes how to enable traffic shaping for egress queues and how to set shapingassociated parameters.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 In Port List, select a port. In Port Queue Shaping Information, set the traffic shaping information about the egress queues.
Related References
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues
A.7.8 Using the IEEE 802.1ag OAM

By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.7.8.1 Creating MDs
A Task Collection
A maintenance domain (MD) defines the scope and level of the 802.1ag OAM. The MDs of different levels and scopes can provide differentiated OAM services to users. A.7.8.2 Creating MAs A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation. A.7.8.3 Creating MPs MPs refer to function entities of IEEE 802.1ag OAM, including MEPs and MIPs. The functions of the IEEE 802.1ag OAM can be used only after MPs are created. A.7.8.4 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source, the source equipment reports the corresponding alarm. A.7.8.5 Performing an LB Test During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MP in the same maintenance association (MA). A.7.8.6 Performing an LT Test Based on the LB test, the linktrace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test. A.7.8.7 Activating the AIS After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP so that the higher level MP is informed of the fault information. A.7.8.8 Performing a Ping Test In a ping test, the ARP and ICMP Layer 3 protocol packets are used to test the connectivity, packet loss ratio, and delay of the service between the Ethernet service processing board and the data communication equipment (such as a switch or a router). A.7.8.9 Performing Performance Check A performance check achieves on-line detection of the packet loss ratio and delay of the service based on the check of the connectivity between the MPs on the Ethernet service processing board.
A.7.8.1 Creating MDs

A maintenance domain (MD) defines the scope and level of the 802.1ag OAM. The MDs of different levels and scopes can provide differentiated OAM services to users.
Prerequisite

Web LCT
Issue 03 (2011-04-10)
A-199
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 In the right pane, click OAM Configuration. The OAM Configuration dialog box is displayed.
NOTE
In this GUI, you can maintain or delete OAM MDs.
Step 3 Click New and choose Create MD from the drop-down list. The Create MD dialog box is displayed. Step 4 Set the parameters of the new MD.
Related References
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs
A.7.8.2 Creating MAs

A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation.
Prerequisite
l l
A-200
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout.
A Task Collection
The MD must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 In the right pane, click OAM Configuration. The OAM Configuration dialog box is displayed.
NOTE
In this GUI, you can maintain or delete OAM MAs.
Step 3 Click New and choose Create MA from the drop-down list.
The Create MA dialog box is displayed. Step 4 Set the parameters of the new MA.
Related References
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs

MPs refer to function entities of IEEE 802.1ag OAM, including MEPs and MIPs. The functions of the IEEE 802.1ag OAM can be used only after MPs are created.
Prerequisite
l l l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet services must be created and activated. The MD and MA must be created.
A Task Collection

Web LCT
Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in the same MD. In an existing MD involved in the same service flow, creating an MP of the same level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Click New. The Create MP dialog box is displayed. Step 3 Set the parameters of the new MP.
Step 4 Optional: Click Advanced. In the dialog box that is displayed, set the corresponding parameters and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations: l Activate the CC and set the sending period of the CC test. l Set the timeout time for the LB or LT test.
Related References
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs
A Task Collection
A.7.8.4 Performing a CC Test

After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source, the source equipment reports the corresponding alarm.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The Ethernet services must be created and activated. The MD and MA must be created. The MEPs must be created.

Web LCT
l l Only the MEP can enable the continuity test and function as the receive respond end for the test. The source MEP constructs CCM packets and transmits them periodically. After receiving the CCM packet from the source MEP, the sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to receive the CCM packet from the source MEP within the check period (that is, 3.5 times of the transmission interval), it reports the specific alarm automatically. Performing a CC test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
l Before the CC test, you can set CCM Sending Period(ms) according to the actual requirements. l To disable a CC test, right-click the MEP where the CC test is performed and then choose Activate CC from the shortcut menu.
TIP
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from the shortcut menu. l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC from the shortcut menu.
----End

During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MP in the same maintenance association (MA).
A Task Collection
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The source and sink MEPs in the same MD must be created. In the case of a standard MP, you must activate CC before an LB test.

Web LCT
l l Only an MEP can initiate an LB test. During the LB test, the source MEP constructs and transmits the LBM frames and starts the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the source MEP. This indicates that the loopback is successful. If the source MEP timer times out, it indicates that the loopback fails. Performing an LB test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that requires an LB test, click OAM Operation, and select Start LB. The LB Test dialog box is displayed. Step 3 Set the parameters involved in the LB test.
NOTE
l In the case of standard MPs, when an MIP functions as the receive end in the LB test, you need to select Test based on the MAC Address and set LB Sink MP MAC Address. l Before the LB test, you can set LB Timeout(ms) according to the actual requirements.
Step 4 Click Start LB. Then, the test result is displayed.

TIP
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
----End
Related References
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB
A Task Collection

Based on the LB test, the linktrace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The source and sink MEPs in the same MD must be created. In the case of a standard MP, you must activate CC before an LT test.

Web LCT
l l Only an MEP can initiate the LT test, and the MEP can work as the receive end in the test. During the LT test, the source MEP constructs and transmits the LTM frames and starts the timer. All the MPs that receive the LTM frames send the LTR frame response. According to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the sink MEP. Performing an LT test does not affect the services.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that requires an LT test, click OAM Operation, and select Start LT. Step 3 Set the parameters involved in the LT test.
NOTE
Before the test, you can set LT Timeout(ms) according to the actual requirements.
Step 4 Click Start LT. Then, the test result is displayed.

TIP
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End
Related References
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT
A Task Collection
A.7.8.7 Activating the AIS

After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP so that the higher level MP is informed of the fault information.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The source and sink MEPs in the same MD must be created. Only a standard MP supports this function.

Web LCT
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored. Double-click or right-click AIS Active Status and then select Active or Inactive.
A.7.8.8 Performing a Ping Test

In a ping test, the ARP and ICMP Layer 3 protocol packets are used to test the connectivity, packet loss ratio, and delay of the service between the Ethernet service processing board and the data communication equipment (such as a switch or a router).
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The source and sink MEPs in the same MD must be created. You must be aware of the IP addresses of the source MP and the sink MP in the ping test.

Web LCT
The source end of the ping test obtains the IP addresses of the source MP and sink MP, and constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets or ICMP packets parses the packets, and responds to the source end. After receiving the response
A Task Collection
packet, the source end reports the ping test result to the NE software (including the ratio of packet loss and time delay) based on the response packet.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored, click OAM Operation, and select Start Ping. The Ping Test dialog box is displayed. Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Ping Attempts for the ping packet.
Step 4 Set Destination IP Address and Local IP Address. Step 5 Click Start Ping. Then, the test result is displayed. ----End
A.7.8.9 Performing Performance Check

A performance check achieves on-line detection of the packet loss ratio and delay of the service based on the check of the connectivity between the MPs on the Ethernet service processing board.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The source and sink MEPs in the same MD must be created.

Web LCT
The performance check method provides an in-service test of packet loss ratio and delay based on the check of the connectivity between the MPs on the Ethernet service processing unit. A performance check is implemented as follows: The source MP initiates several LB tests and counts different packet loss ratio and delay values.
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect. The Performance Detect dialog box is displayed. Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test packet. Step 4 Set Source MP ID and Destination MP ID. Step 5 Click Start Detect. Then, the check result is displayed. ----End
A.7.9 Using the IEEE 802.3ah OAM

By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links. A.7.9.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is achieved based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the faults and performance of the link. A.7.9.2 Enabling the Link Event Notification After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed. A.7.9.3 Modifying the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Generally, the default value is used. You can modify the value according to the situation of the link. A.7.9.4 Performing the Remote Loopback After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.

The IEEE 802.3ah OAM is achieved based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the faults and performance of the link.
Prerequisite

Web LCT
The OAM auto-discovery is achieved based on auto-negotiation between the local equipment and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
A Task Collection
OAM auto-discovery is successful, the link performance is monitored according to the error frame threshold. You can set the error frame threshold on the NMS.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the port and set OAM Working Mode.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of either or both systems must be the active mode. Otherwise, OAM auto-discovery fails. l If the OAM modes of the two systems are passive modes, if a fault occurs on the link, or if one system fails to receive the OAM protocol message within five consecutive seconds, an alarm is reported, indicating that OAM auto-discovery fails.
Step 4 Select Enabled from the Enable OAM Protocol drop-down list.
Step 5 Click Apply. Step 6 Click the Remote OAM Parameter tab. Click Query to check the OAM capability of the opposite end. ----End
Related References
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter
A.7.9.2 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The OAM auto-discovery operation must be successful on the equipment at both ends.

Web LCT
A Task Collection
After the OAM auto-discovery operation is successful at both ends, the link fault detection and performance detection are automatically started. l l The local end can notify the opposite end of link fault events only if Remote Alarm Support for Link Event is set to Enabled at the local end. The local end can notify the opposite end of link performance events only if Remote Alarm Support for Link Event is set to Enabled and if the monitoring time and error frame thresholds are configured at the local end. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the ETHOAM_RMT_SD alarm, which is reported on the local end, by using the NMS. According to the alarm, you can determine the type of the link performance event. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite equipment detects a link fault event or encounters a fault that makes the equipment fail to be restored (such as a power failure), you can query the ETHOAM_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the NMS. Based on the alarm, you can determine the fault type.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the corresponding port and set Remote Alarm Support for Link Event to Enabled.
Related References
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter

The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Generally, the default value is used. You can modify the value according to the situation of the link.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM auto-discovery operation must be successful on the equipment at both ends.
A-210
A Task Collection

Web LCT
The local end notifies the opposite end after detecting a link event in the receive direction under the following conditions: l l The OAM auto-discovery operation is successful. Remote Alarm Support for Link Event is set to Enabled and the monitoring time and error frame thresholds have been configured at the local end.
If Remote Alarm Support for Link Event is also set to Enabled at the opposite end, the opposite end notifies the local end after detecting a link event, and then the local end generates the corresponding alarm.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Error Frame Monitor tab. Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
Related References
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring
A.7.9.4 Performing the Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The OAM auto-discovery operation must be successful on the equipment at both ends. On the equipment where the loopback is initiated, OAM Working Mode must be set to Active. The equipment that responds to the loopback must support remote loopbacks.

Web LCT
A Task Collection
l If a port is capable of responding to loopbacks, it enters the Respond Loopback of Remote state and reports the loopback responding alarm when receiving the command of enabling the remote loopback function sent from the opposite OAM port. In this case, the equipment that initiates the loopback enters the loopback initiating state and reports the loopback initiating alarm. Generally, after the remote loopback function is enabled, service packets, except the OAMPDU packets, are looped back at the remote end. After using the remote loopback function to locate faults and test link performance, you should disable the remote loopback function at the end where the loopback is initiated and then restore the services. At this time, the alarm clears automatically.
l l
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Choose Enable Remote Loopback from the OAM drop-down menu.
----End
A.7.10 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port and the relevant information. A.7.10.1 Configuring LPT for Point-to-Point Services When a point-to-point service uses the LPT function, you need to set LPT parameters both in the positive and reverse directions. A.7.10.2 Configuring LPT for Point-to-Multipoint Services To configure LPT for point-to-multipoint services, you need to specify the corresponding relationships between aggregation ports and access ports and LPT parameters.
A.7.10.1 Configuring LPT for Point-to-Point Services

When a point-to-point service uses the LPT function, you need to set LPT parameters both in the positive and reverse directions.
Prerequisite
l l l
A-212
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The PORT-based Ethernet private line services must be created and activated.
A Task Collection
l l
The data services must be configured as EPL services that are transmitted from PORTs to VCTRUNKs and do not carry any VLAN tags. An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

Web LCT
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select only one configuration mode to implement the LPT function.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Step 2 Click Query. Step 3 Select a PORT and a VCTRUNK, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off Time(ms) according to actual requirements.
Related References
B.7.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT
A.7.10.2 Configuring LPT for Point-to-Multipoint Services

To configure LPT for point-to-multipoint services, you need to specify the corresponding relationships between aggregation ports and access ports and LPT parameters.
Prerequisite
l l l
Issue 03 (2011-04-10)
The NE user must have the authority of Operation Level or higher. The EFP8 board must be added in the Slot Layout. The VLAN-based EVPL services must be created and activated.
A Task Collection
An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

Web LCT
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select only one configuration mode to implement the LPT function.
CAUTION
Before configuring the point-to-multipoint LPT function, make sure that the following two conditions are met. Otherwise, the services may be interrupted. l l The data services are displayed in the tree topology. The data service topology is consistent with the topology of the LPT.
Procedure
Step 1 In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears. Step 3 Click New. The Create LPT dialog box is displayed.
A-214
Issue 03 (2011-04-10)
A Task Collection
Step 4 Set the parameters in Convergence Point. Step 5 Set the parameters in Access Point. 1. 2. Select the ports from Port and then click If you select a VCTRUNK, set Bearer Mode. .
Related References
B.7.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT
A.8 Managing MPLS/PWE3 Services and Features

The OptiX RTN 950 supports multiple MPLS/PWE3 services and features. A.8.1 Managing Address Resolution The OptiX RTN 950 runs the Address Resolution Protocol (ARP) to set up mapping between MAC addresses and IP addresses of ports. A.8.2 Managing MPLS Tunnels Managing MPLS tunnels include managing MPLS OAM functions. A.8.3 Managing MPLS APS Protection Groups MPLS APS is the commonest protection mode for MPLS tunnels.
A Task Collection
A.8.4 Managing PWs All types of PWE3 services are carried by PWs. A.8.5 Managing a PW APS Protection Group PW APS provides protection for PWs. A.8.6 Managing CES Services The OptiX RTN 950 supports PWE3-based CES services. A.8.7 Managing ATM/IMA Ports On the OptiX RTN 950, ATM/IMA ports are mapped into one ATM TRUNK. A.8.8 Managing ATM Services The OptiX RTN 950 supports common ATM services (UNI-UNI) and PW-carried ATM services (UNI-NNI). A.8.9 ATM Traffic Management ATM traffic management includes ATM-Diffserv management and ATM policy management. A.8.10 Using ATM OAM ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and monitoring ATM performance.
A.8.1 Managing Address Resolution

The OptiX RTN 950 runs the Address Resolution Protocol (ARP) to set up mapping between MAC addresses and IP addresses of ports. A.8.1.1 Creating ARP Static Entries This topic describes how to create ARP entries that are not aged. A.8.1.2 Querying ARP Entries You can learn about ARP information. A.8.1.3 Converting Dynamic ARP Entries to Static ARP Entries During the equipment operation phase, you can change dynamic entries in the ARP table to static entries to improve stability of tunnels. A.8.1.4 Deleting Static ARP Entries When MAC addresses of interconnected ports change, you can delete the existing static ARP entries of the network element (NE) and create other ARP entries. A.8.1.5 Setting ARP Aging Time This topic describes how to set the ARP aging time. The default aging time is 20 minutes.
A.8.1.1 Creating ARP Static Entries

This topic describes how to create ARP entries that are not aged.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Create. The Add Address Parse dialog box is displayed. Step 3 Set the parameters for address resolution.
NOTE
Configure the MAC address in an ARP entry according to the MAC address of its next-hop equipment.
Step 4 Click OK. Then, the static ARP entry is successfully created. ----End
A.8.1.2 Querying ARP Entries

You can learn about ARP information.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Query and query ARP entries in the main interface. ----End
A.8.1.3 Converting Dynamic ARP Entries to Static ARP Entries

During the equipment operation phase, you can change dynamic entries in the ARP table to static entries to improve stability of tunnels.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Select the required dynamic ARP entry and click Switch to Static Type. Step 3 Click Query. Then, ARP List Type changes to Static for the selected dynamic ARP entry. ----End
A.8.1.4 Deleting Static ARP Entries

When MAC addresses of interconnected ports change, you can delete the existing static ARP entries of the network element (NE) and create other ARP entries.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Select the required static ARP entry and click Delete.
NOTE
When deleting dynamic ARP entries, click Clear. Exercise caution when performing this operation to avoid service interruption.
A confirmation dialog box is displayed. Step 3 Click OK. Step 4 Click Query. The selected static ARP entry is deleted. ----End
A.8.1.5 Setting ARP Aging Time

This topic describes how to set the ARP aging time. The default aging time is 20 minutes.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Control Plane Configuration > Aging Time from the Function Tree. Step 2 Select the required port, double-click it, and modify the parameter Dynamic ARP Entry Aging Time(min). Step 3 Click Apply. ----End
A.8.2 Managing MPLS Tunnels

Managing MPLS tunnels include managing MPLS OAM functions. A.8.2.1 Setting Basic MPLS Attributes This topic describes how to set basic MPLS attributes, including the LSR ID and the global label space. A.8.2.2 Creating a Unidirectional MPLS Tunnel When creating a unidirectional MPLS tunnel, you need to manually create a MPLS tunnel in the reverse direction. A.8.2.3 Creating a Bidirectional MPLS Tunnel During creation of a bidirectional MPLS tunnel, both the forward and reverse tunnels are created. A.8.2.4 Querying MPLS Tunnel Information You can learn about information about all MPLS tunnels configured for an NE. A.8.2.5 Deleting MPLS Tunnels If a tunnel is no longer used, you can delete it to free the corresponding transmission resources. A.8.2.6 Setting MPLS OAM Parameters This section describes how to set OAM parameters for MPLS tunnel availability test. A.8.2.7 Enabling/Disabling FDI When the FDI function of an NE is enabled, fault locating and protection switching can be performed more quickly. A.8.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels Before enabling CV/FD detection, you need to set MPLS OAM parameters. A.8.2.9 Querying LSP Running Status This topic describes how to query the MPLS tunnel status detected by MPLS OAM. A.8.2.10 Clearing OAM Configuration Data for MPLS Tunnels This topic describes how to restart MPLS OAM detection by clearing MPLS OAM configuration data. A.8.2.11 Performing an LSP Ping Test This topic describes how to detect whether an MPLS tunnel is available. A.8.2.12 Performing an LSP Traceroute Test You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Issue 03 (2011-04-10)
A-219
A Task Collection
A.8.2.1 Setting Basic MPLS Attributes

This topic describes how to set basic MPLS attributes, including the LSR ID and the global label space.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Step 2 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
CAUTION
When PWE3 services are configured on the NE, the PWE3 services may be interrupted if LSR ID of the NE is changed.
Step 3 Click Apply. A confirmation dialog box is displayed. Step 4 Click OK. ----End
Related References
B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels
A.8.2.2 Creating a Unidirectional MPLS Tunnel

When creating a unidirectional MPLS tunnel, you need to manually create a MPLS tunnel in the reverse direction.
Prerequisite
l l l
A-220
The NE user must have the authority of Operation Level or higher. The port attributes are set correctly. The LSR ID of each NE is set correctly.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click New and choose Unidirectional Tunnel from the drop-down list. Step 4 Select New Reverse Tunnel. Step 5 Set parameters for the new MPLS tunnel.
TIP
Click View Peer NE to view the status and tunnel information of the opposite NE.
Related References
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels
A Task Collection

During creation of a bidirectional MPLS tunnel, both the forward and reverse tunnels are created.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The port attributes have been correctly configured. The LSR ID of each NE has been correctly configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click New and choose Bidirectional Tunnel from the drop-down list. The New Unicast Bidirectional Tunnel dialog box is displayed. Step 4 Set parameters for the bidirectional MPLS tunnel.
A-222
Issue 03 (2011-04-10)
A Task Collection
Related References
B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels
A.8.2.4 Querying MPLS Tunnel Information

You can learn about information about all MPLS tunnels configured for an NE.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. MPLS tunnels are configured correctly.

Web LCT
Issue 03 (2011-04-10)
A-223
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click Query. Step 4 View the information about all MPLS tunnels configured for the NE in the main interface. ----End
Related References
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel
A.8.2.5 Deleting MPLS Tunnels

If a tunnel is no longer used, you can delete it to free the corresponding transmission resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. An MPLS tunnel is configured correctly and is no longer used to transmit services.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click Query. Step 4 Select the required MPLS tunnel and click Delete. A confirmation dialog box is displayed. Step 5 Click OK. Step 6 Click Query and find that the selected MPLS tunnel does not exist. ----End
A.8.2.6 Setting MPLS OAM Parameters

This section describes how to set OAM parameters for MPLS tunnel availability test.
Prerequisite
l l
A-224
The NE user must have the authority of Operation Level or higher. MPLS tunnels are created and enabled.
A Task Collection
Node Type is set to Ingress or Egress for tunnels.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required MPLS tunnel and set MPLS OAM parameters.
Related References
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters
A.8.2.7 Enabling/Disabling FDI

When the FDI function of an NE is enabled, fault locating and protection switching can be performed more quickly.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. MPLS tunnels are created and enabled.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the FDI tab. Step 3 Set Enable FDI based on the applications.
Related References
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI
A Task Collection
A.8.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels

Before enabling CV/FD detection, you need to set MPLS OAM parameters.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MPLS OAM function has been enabled and related parameters have been configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation. Step 4 Select the required operation from the drop-down list. 1. 2. To enable CV/FFD detection, click Start CV/FFD. Then, close the dialog box that is displayed. To disable CV/FFD detection, click Stop CV/FFD.
NOTE
l For unidirectional tunnels, this operation task can be performed only for a tunnel whose Node Type is Ingress. l For bidirectional tunnels, this operation task cannot be performed if Node Type is Transit. l After the MPLS OAM function is enabled, CV/FFD detection is enabled by default.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select the required tunnel, right-click the tunnel, and then select Start CV/ FFD or Stop CV/FFD from the drop-down list.
----End
A.8.2.9 Querying LSP Running Status

This topic describes how to query the MPLS tunnel status detected by MPLS OAM.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MPLS OAM detection function has been enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface. Step 4 Select Query LSP Status from the drop-down list. Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-down list.
----End
A.8.2.10 Clearing OAM Configuration Data for MPLS Tunnels

This topic describes how to restart MPLS OAM detection by clearing MPLS OAM configuration data.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MPLS OAM detection function has been enabled. The tunnel is not configured in any protection group.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface. Step 4 Select Clear OAM from the drop-down list.
A Task Collection
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM operations need to be performed, you need to re-enable and configure the OAM functions.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the dropdown list.
----End
A.8.2.11 Performing an LSP Ping Test

This topic describes how to detect whether an MPLS tunnel is available.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab. Step 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

TIP
Alternatively, you can select a tunnel, right-click the tunnel, and select Ping Test from the drop-down list.
The Ping Test dialog box is displayed. Step 4 Set parameters for a ping test.
A-228
Issue 03 (2011-04-10)
A Task Collection
Step 5 Click Start Test to check the test result.

NOTE
l If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping
A.8.2.12 Performing an LSP Traceroute Test

You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab. Step 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

TIP
Alternatively, you can select a tunnel, right-click the tunnel, and select Traceroute Test from the dropdown list.
The Traceroute Test dialog box is displayed. Step 4 Set parameters for the traceroute test.

A Task Collection
NOTE
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute
A.8.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels. A.8.3.1 Creating an MPLS APS Protection Group An MPLS APS protection group needs to be configured if a service carried by an MPLS tunnel needs to be protected. A.8.3.2 Querying MPLS APS Status You can know current information about MPLS APS by querying MPLS APS status on the NMS. A.8.3.3 Triggering MPLS APS Switching This topic describes how to trigger an external PW APS switching. A.8.3.4 Enabling/Disabling MPLS APS Protection If you first stop the MPLS APS protection protocol and then start it, the MPLS APS protection protocol is restored to its initial state.
A.8.3.1 Creating an MPLS APS Protection Group

An MPLS APS protection group needs to be configured if a service carried by an MPLS tunnel needs to be protected.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The working and protection MPLS tunnels have been created. MPLS OAM as been enabled for both working and protection MPLS tunnel in the protection group. The protection tunnel cannot carry extra services. PW APS protection is not configured for the service.

Web LCT
MPLS OAM needs to be enabled for working and protection tunnels. The detection packets used by MPLS OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms. If the packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission interval of FFD packets needs to be a value greater than the delay time.
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Click New. The New Tunnel Protection Group dialog box is displayed. Step 4 Set parameters for the MPLS APS protection group.
NOTE
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only when the MPLS APS protection group is successfully created on nodes at both ends.
Step 5 Click OK.. ----End
Related References
B.9.1.15 Parameter Description: Tunnel Protection Group_Creation
A.8.3.2 Querying MPLS APS Status

You can know current information about MPLS APS by querying MPLS APS status on the NMS.
Issue 03 (2011-04-10)
A-231
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MPLS APS protection group has been created. The MPLS APS protocol has been enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Click Query. Check basic information about the protection group. Step 4 Select the required protection group and click Function. Step 5 Select Query Switching Status from the drop-down list. ----End
Related References
B.9.1.14 Parameter Description: MPLS APS Protection Management
A.8.3.3 Triggering MPLS APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MPLS APS protection group has been created. The MPLS APS protocol has been enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Select the required protection group, click Function, and then select the required switching mode from the drop-down list.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and then select the required switching mode from the drop-down list.
A-232
Issue 03 (2011-04-10)
A Task Collection
Then, a confirmation dialog box is displayed. Step 4 Click OK.. Step 5 Click Function. Step 6 Select Query Switching Status from the drop-down list. Check whether switching is performed successfully. ----End
A.8.3.4 Enabling/Disabling MPLS APS Protection

If you first stop the MPLS APS protection protocol and then start it, the MPLS APS protection protocol is restored to its initial state.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MPLS APS protection group has been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Stop the MPLS APS protocol. 1. 2. Select the required protection group and click Function. Select Stop Protocol from the drop-down list.
CAUTION
After the MPLS APS protocol is stopped, the protection group fails. In addition, services are unavailable until the working channel is restored or the MPLS APS protocol is restarted, if services have been switched to the protection channel.
Issue 03 (2011-04-10)
A-233
A Task Collection
Step 4 Start the MPLS APS protocol. 1. 2. Select the required protection group and click Function. Select Start Protocol from the drop-down list.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and choose Start Protocol or Stop Protocol from the shortcut menu.
----End
A.8.4 Managing PWs

All types of PWE3 services are carried by PWs. A.8.4.1 Querying Information and Running Status of PWs This topic describes how to query information and running status of PWs. A.8.4.2 Creating an MS-PW This topic describes how to configure cross-connections for front-end and rear-end PWs at an S-PE node and create an MS-PW. A.8.4.3 Setting PW OAM Parameters This topic describes how to set OAM parameters for PW availability test. A.8.4.4 Performing a PW Ping Test This topic describes how to detect whether a PW is available. A.8.4.5 Performing a PW Traceroute Test You can detect fault points on an MS-PW by performing PW traceroute tests.
A.8.4.1 Querying Information and Running Status of PWs

This topic describes how to query information and running status of PWs.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. PW-carried services have been configured.

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW Management tab. Step 3 Click the PW Management tab. Step 4 Click Query. Step 5 In the main interface, check the basic information and running status of each PW. Step 6 After selecting a PW, to query other PW information, do as follows: 1. 2. Click the QoS Information tab and check QoS information of the PW. Click the Advanced Attributes tab and check the advanced attributes of the PW.
----End
Related References
B.9.1.9 Parameter Description: PW Management_PW Management
A.8.4.2 Creating an MS-PW

This topic describes how to configure cross-connections for front-end and rear-end PWs at an S-PE node and create an MS-PW.
Prerequisite

Web LCT
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet service as an example to describe how to create MS-PWs.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW Management tab. Step 3 Click the MS PW tab. Step 4 Click New. The Create MS PW dialog box is displayed. Step 5 In the main interface, configure basic service information.
A Task Collection
Step 6 Click the PW General Attributes tab and set PW parameters.
Step 7 Click the QoS tab and set QoS parameters.
Step 8 Click the Advanced Attributes tab and set advanced attributes.
Step 9 Click OK.. ----End
Related References
B.9.1.10 Parameter Description: PW Management_MS-PW Creation
A Task Collection
A.8.4.3 Setting PW OAM Parameters

This topic describes how to set OAM parameters for PW availability test.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. PW-carried services have been configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW and set PW OAM parameters.
Related References
B.9.1.11 Parameter Description: PW Management_PW OAM
A.8.4.4 Performing a PW Ping Test

This topic describes how to detect whether a PW is available.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. A PW has been created and enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW and click OAM Operation > PW Ping Test.
A Task Collection
TIP
Alternatively, you can select a PW, right-click the PW, and select PW Ping Test from the drop-down list.
The Ping Test dialog box is displayed. Step 4 Set parameters for a ping test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.9.1.12 Parameter Description: PW Management_PW Ping
A.8.4.5 Performing a PW Traceroute Test

You can detect fault points on an MS-PW by performing PW traceroute tests.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. A PW has been created and enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
TIP
A Task Collection
Alternatively, you can select a PW, right-click the PW, and select Traceroute Test from the drop-down list.
The Traceroute Test dialog box is displayed. Step 4 Set parameters for the traceroute test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.9.1.13 Parameter Description: PW Management_PW Traceroute
A.8.5 Managing a PW APS Protection Group

PW APS provides protection for PWs. A.8.5.1 Creating a PW APS Protection Group If MPLS APS cannot be configured to protect a PW-carried service, you can configure PW APS to protect the service. A.8.5.2 Configuring Slave Protection Pairs of PW APS During PW APS switching, the PWs in the slave protection pair are also switched. A.8.5.3 Querying PW APS Status You can know current information about a PW APS protection group by querying PW APS status on the NMS. A.8.5.4 Triggering PW APS Switching This topic describes how to trigger an external PW APS switching. A.8.5.5 Enabling/Disabling PW APS Protection If you first stop the PW APS protection protocol and then start it, the PW APS protection protocol is restored to its initial state.
A.8.5.1 Creating a PW APS Protection Group

If MPLS APS cannot be configured to protect a PW-carried service, you can configure PW APS to protect the service.
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. MPLS APS protection is not configured for the service. The tunnel carrying the working and protection PWs has been created.

Web LCT
PW OAM needs to be enabled for the working and protection PWs of a PW APS protection group. The detection packets used by PW OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms. If the packet transmission delay time of a PW exceeds 3.3 ms, the transmission interval of FFD packets needs to be a value greater than the delay time. CES services, ATM services, and E-Line services carried by PWs support PW APS. You can create a PW APS protection group during initial service configuration or after service configuration. l l l During initial service configuration, set Protection Type to PW APS, create the working and protection PWs, use the PWs to configure a PW APS protection group. If services are already configured, create the PW APS protection group in the Protection Group tab page. For SS-PWs and MS-PWs, configuration of the PW APS protection group needs to be done on both source NE and sink NE.
NOTE
l This topic describes how to configure PW APS after services are configured. l This topic uses a PW-carried E-Line service as an example to describe how to configure PW APS protection. The methods of configuring PW APS protection for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the required services and click the Protect Group tab. Step 3 Click PW APS. Step 4 Click New. The Configure PW dialog box is displayed. Step 5 Click the PW tab and set the basic attributes of the protection PW.
A-240
Issue 03 (2011-04-10)
A Task Collection
Step 6 Click the Protection Group tab and set information about the PW APS protection group.
NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when the PW APS protection group is successfully created on nodes at both ends.
Step 7 Click PW OAM and configure OAM information.

NOTE
l When the PW APS protection group is created, the PW OAM function is automatically enabled to detect the PW status. l You can also configure OAM information by choosing Configuration > MPLS Management > PW Management > PW OAM Parameter.

A Task Collection
Related References
B.9.1.16 Parameter Description: PW APS Protection Group_Creation
A.8.5.2 Configuring Slave Protection Pairs of PW APS

During PW APS switching, the PWs in the slave protection pair are also switched.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The mapping between a slave protection pair and a PW APS protection group has been specified. MPLS APS protection is not configured for the service. The tunnel carrying the working and protection PWs has been created.

Web LCT
CES services, ATM services, and E-Line services carried by PWs support PW APS slave protection pairs. The slave protection pairs are bound with a PW APS protection group. You can create a slave protection pair during initial service configuration or after service configuration. l l l During initial service configuration, set Protection Type to Slave Protection Pair, create the working and protection PWs, use the PWs to configure a slave protection pair. If services are already configured, create the slave protection pair in the Protection Group tab page. For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS protection group requires that the slave protection pair is added on both the source NE and sink NE.
NOTE
l This topic describes how to configure a slave protection pair after services are configured. l This topic uses a PW-carried E-Line service as an example to describe how to configure a slave protection pair. The methods of configuring slave protection pairs for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the required services and click the Protect Group tab. Step 3 Click Slave Protection Pair. Step 4 Click New. The Configure PW dialog box is displayed. Step 5 Click the General Attributes tab and set the basic attributes of the protection PW.
A Task Collection
Step 6 Click the Protect Group tab and set the ID of the PW APS protection group to which the slave protection pair is bound.
NOTE
You can manually enter an ID, or double-click the ID parameter and select from the drop-down list.
Related References
B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation
A.8.5.3 Querying PW APS Status

You can know current information about a PW APS protection group by querying PW APS status on the NMS.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The PW APS protection group has been created. The PW APS protocol has been enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree.
A Task Collection
Step 2 Click the PW APS Management tab. Step 3 Click Query. Check basic information about the protection group.
NOTE
If a slave protection pair is configured, information about the slave protection pair is displayed at the lower part of the main interface after you select the protection group.
Step 4 Select the required protection group. Click Function > Query Switching Status. Check the status of the protection group. ----End
A.8.5.4 Triggering PW APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The PW APS protection group has been created. The PW APS protocol has been enabled.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the PW APS Management tab. Step 3 Select the required protection group, click Function, and then select the required switching mode from the drop-down list.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and then select the required switching mode from the drop-down list.
Then, a confirmation dialog box is displayed.

A Task Collection
Step 4 Click OK. Step 5 Click Function and choose Query Switching Status from the drop-down list. Check whether switching is performed successfully. ----End
A.8.5.5 Enabling/Disabling PW APS Protection

If you first stop the PW APS protection protocol and then start it, the PW APS protection protocol is restored to its initial state.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The PW APS protection group has been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the PW APS Management tab. Step 3 Stop the PW APS protocol. 1. 2. Select the required protection group and click Function. Select Stop Protocol from the drop-down list.
CAUTION
After the PW APS protocol is stopped, the protection group fails. In addition, services are unavailable until the working channel is restored or the PW APS protocol is restarted, if services have been switched to the protection channel. Step 4 Start the PW APS protocol. 1. 2. Select the required protection group and click Function. Select Start Protocol from the drop-down list.
TIP
You can enable or disable the PW APS protocol by using either of the following methods: l Select the required protection group, right-click the protection group, and choose Start Protocol or Stop Protocol from the short-cut menu. l Set Enabling Status to Enabled or Disabled.
----End
A Task Collection
A.8.6 Managing CES Services

The OptiX RTN 950 supports PWE3-based CES services. A.8.6.1 Creating CES Services This topic describes how to create a CES service. During creation of a CES service, the PW for carrying the CES service is also created. A.8.6.2 Modifying CES Service Parameters This topic describes how to modify parameters related to CES services, such as CES alarm transparent transmission parameters. A.8.6.3 Querying CES Service Information This topic describes how to query information about a CES service. A.8.6.4 Deleting a CES Service. If a CES service is no longer used, you can delete it to free up the corresponding transmission resources. To delete a CES service, you need to delete the corresponding ACR clock configuration at both the source and sink nodes of the CES service. After the CES service is deleted, the corresponding PW is automatically deleted.
A.8.6.1 Creating CES Services

This topic describes how to create a CES service. During creation of a CES service, the PW for carrying the CES service is also created.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The attributes of the UNI port that carries the CES service have been configured. That is, Port Mode has been set to Layer 1, and Frame Format and Frame Mode have also been configured.

Web LCT
l Generally, UNI-NNI CES services are configured on the OptiX RTN 950. Therefore, this topic uses a UNI-NNI CES service as an example to describe how to configure CES services. It is recommended that you create protection information before creating a CES service. In this configuration example, Protection Type is set to No Protection. For details on how to configure protection information, see A.8.5.1 Creating a PW APS Protection Group and A.8.5.2 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Click New.
A Task Collection
The Create CES Service dialog box is displayed. Step 3 Set Mode to UNI-NNI. Configure basic information about the CES service carried by a PW.
NOTE
l If Mode is UNI-NNI, you can configure advanced attributes of the PW. l Set Protection Type to No Protection.
Step 4 Optional: Click Port Attributes tab and set the port attributes.
NOTE
Step 5 Click the PW tab and set the basic attributes of the PW.
NOTE
You can select Use existing resource and then use a created tunnel, or click New to create a tunnel. It is recommended that you plan and create required tunnels during initial service configuration.
Step 6 Click Advanced Attributes and set parameters for the advanced attributes.
Issue 03 (2011-04-10)
A-247
A Task Collection
Step 7 Click OK. Step 8 Click OK. ----End
Related References
B.9.2.2 Parameter Description: CES Service Management_Creation
A.8.6.2 Modifying CES Service Parameters

This topic describes how to modify parameters related to CES services, such as CES alarm transparent transmission parameters.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. CES services have been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Query. In the main interface, check basic service information. Step 3 Click PW General Attributes to query information about the PW that carry the service.
A Task Collection
Step 4 Modify advanced parameters. 1. 2. 3. Click the Advanced Attributes tab. Select the required PW, double-click a required advance attribute, and change the attribute value. Click Apply.
Step 5 Change protection group information. 1. 2. 3. 4. Click the Protection Group tab. Click PW APS. Change values of protection group parameters, such as Restoration Mode. Click Apply.
----End
Related References
B.9.2.1 Parameter Description: CES Service Management
A.8.6.3 Querying CES Service Information

This topic describes how to query information about a CES service.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. CES services have been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Query. In the main interface, check basic service information. Step 3 Click PW General Attributes to query information about the PW that carry the service. Step 4 Click QoS to check the QoS information of the CES service. Step 5 Click Advanced Attributes to check advanced attributes of the CES service. Step 6 Click Protect Group to check whether a protection group is configured and to check information about the protection group if configured. ----End
Related References
A Task Collection
A.8.6.4 Deleting a CES Service.

If a CES service is no longer used, you can delete it to free up the corresponding transmission resources. To delete a CES service, you need to delete the corresponding ACR clock configuration at both the source and sink nodes of the CES service. After the CES service is deleted, the corresponding PW is automatically deleted.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The CES service has been created and will no longer be used. No ACR clock has been configured for the CES service.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Delete. A confirmation dialog box is displayed. Step 3 Click OK. Step 4 Click Query to check whether the CES service is successfully deleted. ----End
A.8.7 Managing ATM/IMA Ports

On the OptiX RTN 950, ATM/IMA ports are mapped into one ATM TRUNK. A.8.7.1 Binding ATM TRUNKs An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial ports (SPs) that transmit ATM/IMA services. A.8.7.2 Configuring an IMA group If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the parameters of the IMA group. A.8.7.3 Setting ATM Port Parameters This topic describes how to configure ATM port parameters. A.8.7.4 Querying Running Status of an IMA Group This topic describes how to query the running status of an IMA group. A.8.7.5 Querying Link Running Status of an IMA Group This topic describes how to query the running status of the member links of an IMA group.
A.8.7.1 Binding ATM TRUNKs

An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial ports (SPs) that transmit ATM/IMA services.
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2. For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and configure A.5.5 Setting Serial Port Parameters.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the Binding tab. Step 3 Click Configuration. The Bound Path dialog box is displayed. Step 4 Configure the related parameters according to planning information. Then, click bind the required E1 ports or SPs to the ATM TRUNK. to
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select E1 in Level. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports, select Fractional E1 in Level.
Issue 03 (2011-04-10)
A-251
A Task Collection
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the parameters of the IMA group.
Related References
B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration

If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the parameters of the IMA group.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Group Management tab. Step 3 Configure the parameters of the IMA group according to planning information.
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in 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. l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must be the same because the OptiX RTN 950 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 On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame Length, and Maximum Delay Between Links (ms) to the same values. l Clock Mode is set to the same value for the interconnected ends of IMA links.
Related References
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management
A Task Collection
A.8.7.3 Setting ATM Port Parameters

This topic describes how to configure ATM port parameters.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the ATM Interface Management tab. Step 3 Configure and adjust the ATM port attributes.
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on the common ATM network or to the user-side interface 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 interface on the common ATM network. l The 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. l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise, packet loss will occur.
Related References
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management
A.8.7.4 Querying Running Status of an IMA Group

This topic describes how to query the running status of an IMA group.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Group States tab. Step 3 Click Query. Step 4 Query the running status of an IMA group. ----End
Related References
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status
A.8.7.5 Querying Link Running Status of an IMA Group

This topic describes how to query the running status of the member links of an IMA group.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Link States tab. Step 3 Click Query. Step 4 Query the running status of the member links of an IMA group. ----End
Related References
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status
A.8.8 Managing ATM Services

The OptiX RTN 950 supports common ATM services (UNI-UNI) and PW-carried ATM services (UNI-NNI). A.8.8.1 Creating ATM Services To create common ATM services, you only need to configure ATM connections and CoS mapping. To create ATM PWE3 services, you also need to configure the PW that carries ATM services. A.8.8.2 Modifying ATM Service Parameters
A Task Collection
This topic describes how to modify ATM service parameters. A.8.8.3 Querying ATM Services This topic describes how to query ATM services. A.8.8.4 Deleting an ATM Service This topic describes how to delete an ATM service. If an ATM service is no longer used, you can delete it to release its resources.
A.8.8.1 Creating ATM Services

To create common ATM services, you only need to configure ATM connections and CoS mapping. To create ATM PWE3 services, you also need to configure the PW that carries ATM services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Generally, UNIs-NNI ATM services are configured on the OptiX RTN 950. Therefore, this topic uses a UNIs-NNI ATM service as an example to describe how to configure ATM PWE3 services. Before creating ATM PWE3 services, you need to bind member links to the ATM TRUNK, set the parameters of the IMA group, and create the MPLS tunnels that carries PWs.

Web LCT
l l To create ATM PWE3 services (UNIs-NNI), it is recommended that you create services before configuring PW protection. Configuration will be simplified in this manner. In this configuration example, Protection Type is set to No Protection. For details on how to configure PW protection, see A.8.5.1 Creating a PW APS Protection Group and A. 8.5.2 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click New. The New ATM Service dialog box is displayed. Step 3 Configure the basic information about the ATM PWE3 service according to the planning information.
Issue 03 (2011-04-10)
A-255
A Task Collection
Step 4 Configure the attributes of the ATM connection. 1. 2. 3. Click New in the Connection tab page. The New Connection dialog box is displayed. Set the attributes of the ATM connection.
Step 5 Click the PW tab, and click New to configure the attributes of PWs. 1. Click the General Attributes tab and set the basic attributes of PWs.
2.
Click the QoS tab and enable the PW bandwidth restriction.
A-256
Issue 03 (2011-04-10)
A Task Collection
3.
Click the Advanced Attributes tab to configure the advanced attributes of PWs.
4.
Click OK.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
Related References
B.9.3.11 Parameter Description: ATM Service Management_Creation
A.8.8.2 Modifying ATM Service Parameters

This topic describes how to modify ATM service parameters.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. ATM PWE3 services are already created and their parameters need to be modified according to the planning information.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click Query.
A Task Collection
Step 3 Select the required ATM service and modify the parameters of the ATM service. Step 4 Click Apply. ----End
Related References
B.9.3.10 Parameter Description: ATM Service Management
A.8.8.3 Querying ATM Services

This topic describes how to query ATM services.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click Query. Step 3 Select the required ATM service and query the parameters of the ATM service. ----End
Related References
A.8.8.4 Deleting an ATM Service

This topic describes how to delete an ATM service. If an ATM service is no longer used, you can delete it to release its resources.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree.
A Task Collection
Step 2 Click Query. Step 3 Select the required ATM service and click Delete. Step 4 In the confirmation dialog box, click OK. ----End
A.8.9 ATM Traffic Management

ATM traffic management includes ATM-Diffserv management and ATM policy management. A.8.9.1 Creating an ATM-DiffServ Domain This topic describes how to create an ATM-DiffServ domain. If the default ATM-Diffserv domain does not serve the purpose, a new ATM-Diffserv needs to be created. A.8.9.2 Modifying an ATM-Diffserv Domain This topic describes how to modify an ATM-Diffserv domain. By performing this operation, you can modify the mapping relationship between ATM service types and PHB service classes. A.8.9.3 Creating an ATM Policy This topic describes how to create an ATM policy for an ATM connection. A.8.9.4 Modifying an ATM Policy This topic describes how to modify the QoS parameters of an ATM policy.
A.8.9.1 Creating an ATM-DiffServ Domain

This topic describes how to create an ATM-DiffServ domain. If the default ATM-Diffserv domain does not serve the purpose, a new ATM-Diffserv needs to be created.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree. Step 2 Click New. The New ATM CoS Mapping dialog box is displayed. Step 3 Configure the ATM-Diffserv domain according to the planning information.
Issue 03 (2011-04-10)
A-259
A Task Collection
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 950 provides different QoS policies for the queues of different service classes. 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.
Related References
B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
A.8.9.2 Modifying an ATM-Diffserv Domain

This topic describes how to modify an ATM-Diffserv domain. By performing this operation, you can modify the mapping relationship between ATM service types and PHB service classes.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree.
A Task Collection
Step 2 Click Query. Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 950 provides different QoS policies for the queues of different service classes. 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.
Related References
B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table
A.8.9.3 Creating an ATM Policy

This topic describes how to create an ATM policy for an ATM connection.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Step 2 Click New. The Create ATM Policy dialog box is displayed. Step 3 Configure the parameters of the ATM policy according to the planning information.
Related References
B.9.3.9 Parameter Description: ATM Policy Management_Creation
A.8.9.4 Modifying an ATM Policy

This topic describes how to modify the QoS parameters of an ATM policy.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Step 2 Click Query. Step 3 Select the required ATM policy and modify its parameters according to the planning information. Step 4 Click Apply. ----End
Related References
B.9.3.8 Parameter Description: ATM Policy Management
A.8.10 Using ATM OAM

ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and monitoring ATM performance. A.8.10.1 Setting Segment and End Attributes of AIS/RDI This topic describes how to set the segment and end attributes of AIS/RDI. A.8.10.2 Performing a Continuity Check Test This topic describes how to perform a continuity check (CC) test. A CC test can be performed to continuously check the unidirectional connectivity of an ATM link. A.8.10.3 Querying or Setting LLIDs This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be configured before an LB test. A.8.10.4 Performing an LB Test This topic describes how to perform a loopback (LB) test. An LB test can be performed to continuously check the bidirectional connectivity of an ATM link.
A.8.10.1 Setting Segment and End Attributes of AIS/RDI

This topic describes how to set the segment and end attributes of AIS/RDI.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. ATM services have been configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree.
A Task Collection
Step 2 Click the Segment End Attributes tab. Step 3 Set the segment and end attributes of AIS/RDI according to the planning information.
Related References
B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes
A.8.10.2 Performing a Continuity Check Test

This topic describes how to perform a continuity check (CC) test. A CC test can be performed to continuously check the unidirectional connectivity of an ATM link.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the CC Activation Status tab. Step 3 Configure the parameters of the CC test according to the planning information.
Related References
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status
A.8.10.3 Querying or Setting LLIDs

This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be configured before an LB test.
A Task Collection
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the LLID tab. Step 3 Set the LLIDs according to the planning information.
Related References
B.9.3.15 Parameter Description: ATM OAM Management_LLID

This topic describes how to perform a loopback (LB) test. An LB test can be performed to continuously check the bidirectional connectivity of an ATM link.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the Remote Loopback Test tab. Step 3 Configure the attributes of the LB test according to the planning information. Step 4 Select an ATM connection for which an LB test needs to be performed.
TIP
By pressing the Ctrl key on the keyboard, you can select multiple ATM connections at one time.
Step 5 Click Test.

A Task Collection
Step 6 Check Test Result.
----End
Related References
B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status
A.9 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.9.1 Managing Clocks at the Physical Layer This section describes how to synchronize clock signals by transmission of reference clock signals at the physical layer. A.9.2 Managing CES ACR Clocks CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to recover clock synchronization information carried by CES packets.
A.9.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmission of reference clock signals at the physical layer. A.9.1.1 Configuring the Clock Sources This topic describes how to configure the clock source according to the planned clock synchronization scheme to ensure that all the NEs on the network trace the same clock. A.9.1.2 Configuring Clock Subnets For simple networks, such as chain networks, you need not configure the clock source protection or you only need to configure the clock priority to implement the clock source protection. For complex networks, such as ring networks or intersecting and tangent rings that are derived from ring networks, you need to configure clock subnets and enable the standard SSM protocol or extended SSM protocol to implement the clock source protection. A.9.1.3 Self-Defined Clock Quality By default, the NE considers the clock quality extracted from the clock source as the clock quality. If the clock quality is zero (the synchronization quality is unknown), the clock is considered as unavailable clock. In the case of any special requirements, the user can define the clock quality for which the source clock quality and clock quality are zero. A.9.1.4 Configuring the SSM Output Status After the standard SSM protocol or extended synchronization status message (SSM) protocol is enabled, the NE transmits the SSM to other NEs through the SDH radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the SSM bytes from being transmitted on the link that is connected to other clock subnets. A.9.1.5 Configuring the Clock ID Output Status After the extended synchronization status message (SSM) protocol is enabled, the NE transmits the clock ID to other NEs through the radio link or optical line by default. To prevent two clock
A Task Collection
subnets from affecting each other, the NE needs to forbid the clock ID from being transmitted on the link that is connected to other clock subnets. A.9.1.6 Modifying the Parameters of the Clock Output The NE outputs the 2-Mbit/s external clock regardless of the clock quality. A.9.1.7 Configuring Clock Sources for External Clock Output By default, the OptiX RTN 950 allows output of the system clock source through the external clock port. If the external clock port needs to transmit other clock sources, such as a clock from a radio link or a synchronous Ethernet clock, you need to configure the priority table for the PLL clock source of the external port. A.9.1.8 Changing the Conditions for Clock Source Switching You can change the default conditions for clock source switching of the NE for special purposes. A.9.1.9 Modifying the Recovery Parameter of the Clock Source In the case of the special requirements, you can modify the recovery parameter of the clock source. A.9.1.10 Querying the Clock Synchronization Status You can know the current clock synchronization status of an NE by querying the clock synchronization status.
A.9.1.1 Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned clock synchronization scheme to ensure that all the NEs on the network trace the same clock.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Priority. Step 2 Click the System Clock Source Priority List tab. Step 3 Click Create. The Add Clock Source dialog box is displayed.
Issue 03 (2011-04-10)
A-267
A Task Collection
Step 4 Select the clock sources.

TIP
Hold on the Ctrl key on the keyboard to select multiple clock sources.
Step 5 Click OK. Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources. Step 7 Optional: Select a clock source and click clock source.
NOTE
or
to adjust the priority of this
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal clock source is always of the lowest priority.
Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
Related References
B.10.1.1 Parameter Description: Clock Source Priority Table
A.9.1.2 Configuring Clock Subnets

For simple networks, such as chain networks, you need not configure the clock source protection or you only need to configure the clock priority to implement the clock source protection. For complex networks, such as ring networks or intersecting and tangent rings that are derived from ring networks, you need to configure clock subnets and enable the standard SSM protocol or extended SSM protocol to implement the clock source protection.
A-268
Issue 03 (2011-04-10)
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The priority list of the clock source must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Clock Subnet tab. Step 3 Start the clock protection protocol and configure its parameters.
Related References
B.10.1.3 Parameter Description: Clock Subnet Setting_Clock Subnet
A.9.1.3 Self-Defined Clock Quality

By default, the NE considers the clock quality extracted from the clock source as the clock quality. If the clock quality is zero (the synchronization quality is unknown), the clock is considered as unavailable clock. In the case of any special requirements, the user can define the clock quality for which the source clock quality and clock quality are zero.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The priority level of a clock source must be set.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Received Quality tab.
A Task Collection
Step 3 Click the Clock Source Quality tab. Step 4 Set the self-defined clock quality.
NOTE
Generally, it is recommended that you use the default value.
Step 5 Click Apply. Step 6 Click the Manual Setting of 0 Quality Level tab. Step 7 Set the clock quality for which the quality level is zero.
NOTE
Generally, it is recommended that you use the default value.
Related References
B.10.1.4 Parameter Description: Clock Subnet Setting_Clock Quality
A.9.1.4 Configuring the SSM Output Status

After the standard SSM protocol or extended synchronization status message (SSM) protocol is enabled, the NE transmits the SSM to other NEs through the SDH radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the SSM bytes from being transmitted on the link that is connected to other clock subnets.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The priority level of a clock source must be set. The standard SSM or extended SSM protocol is enabled.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the SSM Output tab.
A Task Collection
Step 3 Set the SSM control status.
NOTE
l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started. l Output S1 Byte Info indicates whether the SSM is output at the line port. l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled. Otherwise, set this parameter to Disabled.
Related References
B.10.1.5 Parameter Description: Clock Subset Setting_SSM Output Control
A.9.1.5 Configuring the Clock ID Output Status

After the extended synchronization status message (SSM) protocol is enabled, the NE transmits the clock ID to other NEs through the radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the clock ID from being transmitted on the link that is connected to other clock subnets.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The priority level of a clock source must be set. The extended SSM protocol must be enabled.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Clock ID Output tab. Step 3 Set the clock ID control status.
Issue 03 (2011-04-10)
A-271
A Task Collection
NOTE
l Output Clock ID is valid only when the extended SSM protocol is started. l Output Clock ID indicates whether the clock source ID is output at the line port. l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to Disabled.
Related References
B.10.1.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Phase-Locked Source Output by External Clock. Step 2 Modify the parameters of the clock output.
Related References
B.10.1.10 Parameter Description: Output Phase-Locked Source of the External Clock Source
A.9.1.7 Configuring Clock Sources for External Clock Output

By default, the OptiX RTN 950 allows output of the system clock source through the external clock port. If the external clock port needs to transmit other clock sources, such as a clock from a radio link or a synchronous Ethernet clock, you need to configure the priority table for the PLL clock source of the external port.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Physical Clock > Clock Source Priority from the Function Tree. Step 2 Click the Priority for PLL Clock Sources of 1st External Output tab. Step 3 Click Create. The Add Clock Source dialog box is displayed. Step 4 Configure the clock sources for external clock output based on network planning information.
TIP
To select more than one clock source at a time, press and hold the Ctrl key when selecting the clock sources.
NOTE
l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock of the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual configuration is required. l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board, clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock Source to the corresponding clock source according to the network planning information.
Step 5 Click OK. Step 6 Select Internal Clock Source and click Delete.
----End
A.9.1.8 Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special purposes.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Step 2 Click the Clock Source Switching Condition tab. Step 3 Change the conditions for clock source switching.
Related References
B.10.1.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions
A.9.1.9 Modifying the Recovery Parameter of the Clock Source

In the case of the special requirements, you can modify the recovery parameter of the clock source.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Step 2 Click the Clock Source Reversion Parameter tab. Step 3 Set the recovery parameter of the clock source.
Related References
B.10.1.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
A Task Collection

You can know the current clock synchronization status of an NE by querying the clock synchronization status.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Synchronization Status. Step 2 Click Query. Step 3 Query the clock synchronization status. ----End
Related References
B.10.1.11 Parameter Description: Clock Synchronization Status
A.9.2 Managing CES ACR Clocks

CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to recover clock synchronization information carried by CES packets. A.9.2.1 Configuring the Primary Clock for an ACR Clock Domain An ACR clock domain can use the clock extracted from a CES service as its primary clock. A.9.2.2 Configuring Ports Using the Clock Domain An CES E1 port can transmit the clock information in the system clock domain or CES ACR clock domain.
A.9.2.1 Configuring the Primary Clock for an ACR Clock Domain

An ACR clock domain can use the clock extracted from a CES service as its primary clock.
Prerequisite
l l The NE user must have the authority of System Level or higher. CES services are configured.
Issue 03 (2011-04-10)
A-275
A Task Collection
Precautions
CAUTION
l An ACR clock domain can bind only the CES services from the E1 ports on a local board. l On the MD1 board, the four ACR clock domains can bind the CES services either from the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and from the latter 16 E1 ports on a local board. l A maximum of four ACR clock domains can bind CES services.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > ACR Clock from the Function Tree. Step 2 In CES Service, select an CES service for primary clock extraction.
Related References
B.10.2.1 Parameter Description: ACR Clock Source
A.9.2.2 Configuring Ports Using the Clock Domain

An CES E1 port can transmit the clock information in the system clock domain or CES ACR clock domain.
Prerequisite
l l The NE user must have the authority of System Level or higher. CES services are configured.
A-276
Issue 03 (2011-04-10)
A Task Collection
Precautions
CAUTION
l E1 ports output clocks from the system clock domain by default. Therefore, it is unnecessary to set application ports to the system clock domain if system clocks are to be used. l An ACR clock domain can only be applied to the E1 ports on a local board. l The E1 ports corresponding to the primary clock for an ACR clock domain must be added to the ACR clock domain. l On the MD1 board, the four ACR clock domains can bind the CES services either from the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and from the latter 16 E1 ports on a local board.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree. Step 2 Click New. The Create Clock Domain Port dialog box is displayed.
Step 3 Select Clock Domain. Step 4 In Clock Domain Board, select the board where the ACR clock domain resides. Step 5 Set the application ports to the ACR clock domain. 1.
Issue 03 (2011-04-10)
In Board, select a board that uses the ACR clock domain.

A Task Collection
2. 3.
In Available Port, select a port that transmits CES services. Click .
Related References
B.10.2.3 Parameter Description: Clock Domain_Creation
A.10 Using the RMON

The remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.10.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port. A.10.2 Configuring an Alarm Group for an Ethernet Port After you configure an RMON alarm group for an Ethernet port, you can monitor whether the performance value of the port crosses the configured thresholds in the long term. A.10.3 Configuring a History Control Group When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. A maximum of 50 historical performance entries can be saved. A.10.4 Browsing the Performance Data in the History Group of an Ethernet Port After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.
A.10.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding board must be added in the Slot Layout.

Web LCT
A-278
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the Statistics Group tab. Step 3 Set the required parameters for the statistics group. 1. 2. Select the performance items for which statistics need to be collected. Set Sampling Interval. Sampling Interval represents the time unit of the performance statistics.
Step 4 Click Resetting begins.

NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Related References
B.8.1 Parameter Description: RMON Performance_Statistics Group
A.10.2 Configuring an Alarm Group for an Ethernet Port

After you configure an RMON alarm group for an Ethernet port, you can monitor whether the performance value of the port crosses the configured thresholds in the long term.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding boards must be added in the Slot Layout.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the RMON Setting tab. Step 3 Select the boards that need to report RMON performance threshold-crossing alarms.
A Task Collection
Step 4 Set the parameters in the Event tab page.

NOTE
Threshold Detect specifies the mode for report RMON alarms. If Threshold Detect is set to Not Supported. threshold check is not supported for RMON performance events.
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
A.10.3 Configuring a History Control Group

When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. A maximum of 50 historical performance entries can be saved.
Prerequisite
l l
A-280
The NE user must have the authority of Operation Level or higher. The corresponding boards must be added in the Slot Layout.
A Task Collection

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History Control Group. Step 2 Set the parameters of the history control group. Step 3 Click Apply. ----End
Related References
B.8.3 Parameter Description: RMON Performance_History Control Group
A.10.4 Browsing the Performance Data in the History Group of an Ethernet Port
After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding boards must be added in the Slot Layout. The objects and performance events to be monitored must be set.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Group tab. Step 3 Set the parameters of the history group. 1. 2. 3. 4. Select the target port from Select port. Click and specify the required time span.
Select the performance items to browse. Under History Table Type, set the time span of the performance items to be browsed.
Issue 03 (2011-04-10)
A-281
A Task Collection
Step 4 Click Query. ----End
Related References
A.11 Configuring Auxiliary Ports and Functions

The auxiliary ports and functions supported by the OptiX RTN 950 include the orderwire, synchronous data service, asynchronous data service, wayside E1 service, external alarm and monitoring the outdoor cabinet. A.11.1 Configuring Orderwire The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use. A.11.2 Configuring the Synchronous Data Service The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N frame. Such a service is also called F1 data port service. A.11.3 Configuring the Asynchronous Data Service The OptiX RTN 950 supports the transmission of a channel of asynchronous data service with a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called broadcast data port service. A.11.4 Configuring the Wayside E1 Service The OptiX RTN 950 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service through 32 user-defined bytes in the SDH microwave frame. A.11.5 Configure External Alarms After the outputting of external alarms is configured, the alarm information of the OptiX RTN 950 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 950. A.11.6 Monitoring the Outdoor Cabinet The OptiX RTN 950 supports the function of monitoring the outdoor cabinet and its power monitoring unit (PMU).
A-282
Issue 03 (2011-04-10)
A Task Collection
A.11.1 Configuring Orderwire

The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use.
Prerequisite

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the General tab. Step 3 Configure the orderwire information.
Step 4 Click Apply. Step 5 Optional: Change the overhead bytes occupied by the orderwire. 1. 2. Click the Advanced tab. Configure Orderwire Occupied Bytes.
3.
Click Apply.
----End
Related References
B.11.1 Parameter Description: Orderwire_General
A Task Collection
B.11.2 Parameter Description: Orderwire_Advanced
A.11.2 Configuring the Synchronous Data Service

The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N frame. Such a service is also called F1 data port service.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board involved in the synchronous data service must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the F1 Data Port tab. Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click .
Related References
B.11.3 Parameter Description: Orderwire_F1 Data Port
A.11.3 Configuring the Asynchronous Data Service

The OptiX RTN 950 supports the transmission of a channel of asynchronous data service with a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte
A Task Collection
within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called broadcast data port service.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The board involved in the asynchronous data service must be configured.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the Broadcast Data Port tab. Step 3 Configure the parameters of the broadcast data port.
Related References
B.11.4 Parameter Description: Orderwire_Broadcast Data Port
A.11.4 Configuring the Wayside E1 Service

The OptiX RTN 950 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service through 32 user-defined bytes in the SDH microwave frame.
A Task Collection
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IF1 board must be added on the Slot Layout. The DCC channels corresponding to external clocks must be disabled.

Web LCT
The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM mode.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Related References
A.11.5 Configure External Alarms

After the outputting of external alarms is configured, the alarm information of the OptiX RTN 950 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 950.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The AUX board must be added on the Slot Layout.

Web LCT
A-286
Issue 03 (2011-04-10)
A Task Collection
Context
The external alarms of the OptiX RTN 950 are also considered as housekeeping alarms. The external alarm port of the OptiX RTN 950 is a relay port. This port can be either in the "on" state or in the "off" state. The OptiX RTN 950 provides two alarm output ports and four alarm input ports. The alarm input ports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of the input alarm) after the external alarm is triggered. To ensure that the external alarm port works normally, the external alarm cables must be correctly connected.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Configure the input alarm. 1. 2. Select Input Relay from the drop-down list. Configure the parameters of the input alarm.
3.
Click Apply.
Step 3 Configure the output alarm. 1. 2. Select Output Relay from the drop-down list. Configure the parameters of the output alarm.
3.
Click Apply.
----End
Related References
B.11.5 Parameter Description: Environment Monitoring Interface
A.11.6 Monitoring the Outdoor Cabinet

The OptiX RTN 950 supports the function of monitoring the outdoor cabinet and its power monitoring unit (PMU). A.11.6.1 Configuring the Function of an Auxiliary Port On the OptiX RTN 950, When the TOD2 port on the CSH/CST board is used for monitoring the outdoor cabinet, configure this function. A.11.6.2 Setting the Type of the Outdoor Cabinet
A Task Collection
After setting the type of the outdoor cabinet, you can set parameters for the logical boards of the outdoor cabinet according to the network planning information. A.11.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet By performing these operations, you can query the temperature and fan information of the outdoor cabinet. In addition, you can set temperature alarm thresholds and set the working mode of the fan. A.11.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet By performing these operations, you can query and set the information about the power module and the information about the storage batteries managed by the power monitoring unit (PMU) of the outdoor cabinet. A.11.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet The power monitoring unit (PMU) monitors the ambient temperature and humidity of the outdoor cabinet. A.11.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU When the ambient temperature exceeds the preset thresholds, the power monitoring unit (PMU) reports the ODC_TEMP_ABN alarm; when the relevant humidity exceeds the preset thresholds, the PMU reports the ODC_HUMI_ABN alarm.
A.11.6.1 Configuring the Function of an Auxiliary Port

On the OptiX RTN 950, When the TOD2 port on the CSH/CST board is used for monitoring the outdoor cabinet, configure this function.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The outdoor cabinet monitoring port on the OptiX RTN 950 has been connected to the COM_IN port on the outdoor cabinet. In addition, monitoring signal communication is normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Auxiliary Interface from the Function Tree. Step 2 Double-click Interface Mode. Select MON from the drop-down list.
A-288
Issue 03 (2011-04-10)
NOTE
A Task Collection
For the CSH/CST board, Interface Mode can be configured only for port 2.
Related References
B.10.3 Parameter Description: Auxiliary Ports
A.11.6.2 Setting the Type of the Outdoor Cabinet

After setting the type of the outdoor cabinet, you can set parameters for the logical boards of the outdoor cabinet according to the network planning information.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Interface Mode has been configured correctly under Auxiliary Interface.

Web LCT
Context
NOTE
The OptiX RTN 950 supports four types of outdoor cabinet, namely, APM30 AC, APM30 DC, OMB AC, and OMB DC cabinets. When being installed in the OMB AC or OMB DC cabinet, the OptiX RTN 950 can work as only a repeater. When using service cables such as E1 cables and Ethernet cables, install the OptiX RTN 950 in the APM30 AC or APM30 DC cabinet.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > NE Attribute from the Function Tree. Step 2 Set Outdoor Cabinet Type under NE Attribute.
NOTE
Ensure that the configured cabinet type is the same as the type of the actually used outdoor cabinet.

A Task Collection
A.11.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet
By performing these operations, you can query the temperature and fan information of the outdoor cabinet. In addition, you can set temperature alarm thresholds and set the working mode of the fan.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The TCU logical board has been added to the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Select Outdoor Cabinet Interface from the Environment Monitor Interface drop-down list. Step 3 Optional: Click Query to view the temperature and fan information.
Step 4 Optional: Set the working mode of the fan. 1. 2. Set Work Mode. Set other parameters according to the value of Work Mode. l If you set Work Mode to Temperature Control Speed Adjustment, you do not need to set the other parameters. l If you set Work Mode to Master Control Fan Speed Grade, you can set Fan Speed Grade Attribute to Fixation High Speed or Fixation Low Speed. l If you set Work Mode to Master Control Fan Speed Percent, you can set Speed of Internal Circulation Fan(RPM) and Speed of External Circulation Fan(RPM). 3. Click Apply.
NOTE
It is recommended that the parameters take their default values, unless otherwise specified.
Step 5 Optional: Set the temperature alarm thresholds. 1. 2. 3. Set High Temperature Threshold(C). Set Low Temperature Threshold(C). Click Apply.
NOTE
----End
A Task Collection
A.11.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet
By performing these operations, you can query and set the information about the power module and the information about the storage batteries managed by the power monitoring unit (PMU) of the outdoor cabinet.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The PMU logical board has been added to the Slot Layout.

Web LCT
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets. The OBM AC cabinets do not support setting and queries of parameters about the battery group.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Configure the information about the power system of the outdoor cabinet. 1. 2. 3. Select Outdoor Cabinet Interface from the Environment Monitor Interface drop-down list. Click Query to view the information about the power system of the outdoor cabinet. Modify the information about the power system of the outdoor cabinet.
4.
Click Apply.
NOTE
Step 3 Configure the information about the PMU of the outdoor cabinet. 1. 2. 3. Select Outdoor Cabinet PMU Electrical Source System Attribute from the Environment Monitor Interface drop-down list. Click Query to view the information about the PMU of the outdoor cabinet. Modify the information about the power system of the outdoor cabinet.
4.
Issue 03 (2011-04-10)
Click Apply.
A Task Collection
NOTE
----End
A.11.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet
The power monitoring unit (PMU) monitors the ambient temperature and humidity of the outdoor cabinet.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The PMU logical board has been added to the Slot Layout.

Web LCT
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Query the ambient humidity. 1. 2. 1. 2. Select Outdoor Cabinet Interface from the Environment Monitor Interface drop-down list. Click Query to obtain Relevant Humidity. Select Outdoor Cabinet Ambient Temperature from the Environment Monitor Interface drop-down list. Click Query to obtain Ambient Temperature(C).
Step 3 Query the ambient temperature.
----End
A.11.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU
When the ambient temperature exceeds the preset thresholds, the power monitoring unit (PMU) reports the ODC_TEMP_ABN alarm; when the relevant humidity exceeds the preset thresholds, the PMU reports the ODC_HUMI_ABN alarm.
Prerequisite
l l
A-292
The NE user must have the authority of Operation Level or higher. The PMU logical board has been added to the Slot Layout.
A Task Collection

Web LCT
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Select Outdoor Cabinet PMU Alarm Threshold from the Environment Monitor Interface drop-down list. Step 3 Select Operation Object, and set Upper Threshold and Lower Threshold for temperature and humidity alarms.
Step 4 Click Apply.

NOTE
----End
A.12 Verifying Services and Features

This topic describes how to verify service and feature configurations. A.12.1 Testing E1 Services Using PRBS If no BER tester is available, you can test E1 services by using the PRBS test system embedded in the equipment. A.12.2 Testing E1 Services by Using a BER Tester If a BER tester is available, the BER tester can be used to test E1 services. A.12.3 Testing Ethernet Services By testing Ethernet services, you can check whether the Ethernet services are available over radio links. The Ethernet services can be tested using the ETH-OAM function. Therefore, no tester is required. A.12.4 Testing ATM Services By testing ATM services, you can check whether ATM services are available over radio links. The ATM services can be tested using the ATM OAM function. Therefore, no tester is required. A.12.5 Testing AM Switching By testing AM switching, you can determine whether the AM switching is normal over radio links. A.12.6 Testing Protection Switching
A Task Collection
By testing protection switching, you can determine whether the protection switching is normal over radio links.
A.12.1 Testing E1 Services Using PRBS

If no BER tester is available, you can test E1 services by using the PRBS test system embedded in the equipment.
Prerequisite
l l The NE must be configured with E1 services, and the E1 services must be transmitted through the DDF. The communication between the NMS and the NE must be normal.

Web LCT
Precautions
CAUTION
l When a PRBS test is performed, the services carried on the tested path are interrupted. l The PRBS test can be performed only in a unidirectional manner and on one path at a time. l CES services do not support a PRBS test.
Procedure
Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree. Step 3 In the Function Tree, choose Configuration > PRBS Test. Step 4 Select the first E1 port, and then set the following PRBS-related parameters: l Direction: Cross l Duration: a value from 120 to 180 l Measured in Time: seconds
A Task Collection
Step 5 Click Start to Test. The system displays a dialog box indicating The operation may interrupt the service, are you sure to continue? Step 6 Click OK. Step 7 When the Progress column is 100%, click Query to check the test result. The curve diagram should be green. Step 8 Release the inloop set in Step 1. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 9 Repeat Step 1 through Step 8 to test all other E1 ports. ----End
A.12.2 Testing E1 Services by Using a BER Tester

If a BER tester is available, the BER tester can be used to test E1 services.
Prerequisite
The NE must be configured with E1 services, and the E1 services must be transmitted through the DDF.

l l Web LCT BER tester
NOTE
For a test of CES services in CES/PSN mode, a BER tester supporting Nx64 Kbit/s timeslot setting is necessary.
Issue 03 (2011-04-10)
A-295
A Task Collection
Procedure
Step 1 On the DDF at the central site, connect the BER tester to the first E1 port of the IDU. The BER tester indicates the AIS alarm. Figure A-1 Connecting the BER tester
DDF
RX TX
RX
TX
. . . .
1 2 3 4
BER tester
Step 2 On the NMS, perform an inloop for the corresponding E1 port at the remote site. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. Step 3 Test the bit errors for two minutes. There should be no bit errors.
NOTE
For a test of CES services, it is necessary to configure 64 Kbit/s timeslots on a BER tester to align with the timeslots carrying CES services.
Step 4 Release the inloop set in Step 2. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. Step 5 Repeat Step 1 through Step 4 to test all other E1 ports. ----End
A Task Collection
A.12.3 Testing Ethernet Services

By testing Ethernet services, you can check whether the Ethernet services are available over radio links. The Ethernet services can be tested using the ETH-OAM function. Therefore, no tester is required.
Prerequisite
Ethernet services must be configured.
NOTE
l It is recommended that you test low-priority Ethernet services in good weather conditions when the AM function works in the highest-efficiency modulation mode. l The tested Ethernet services can be Native Ethernet services, EoPDH services, or Ethernet services carried by PWs.

Web LCT
Test Connection Diagram

The following test procedure considers the Ethernet service from PORT2 on NE2 and PORT3 on NE3 to PORT1 on NE1 as an example, as shown in Figure A-2.The three Ethernet ports are not on the EFP8 boards. Figure A-2 Networking diagram for testing Ethernet services
NE 2 PORT 2
VLAN ID=100 PORT 1 NE 1
NE 3 Microwave network
PORT 3
VLAN ID=200
The VLAN ID of the Ethernet service from NE2 to NE1 is 100, and the VLAN ID of the Ethernet service from NE3 to NE1 is 200.
NOTE
If the Ethernet ports are on the EFP8 boards, you can still perform the following steps to test the Ethernet services by eliminating the need to set up the remote maintenance end point. In addition, the operations on the NMS are different. For details, see A.7.8.1 Creating MDs, A.7.8.2 Creating MAs, A.7.8.3 Creating MPs, and A.7.8.5 Performing an LB Test.
Issue 03 (2011-04-10)
A-297
A Task Collection
Procedure
Step 1 Configure the maintenance domains of NE1, NE2, and NE3. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Choose New > New Maintenance Domain. The New Maintenance Domain dialog box is displayed. Configure the parameters of the new maintenance domains. l Maintenance Domain Name: MD1 for NE1, NE2, and NE3 l Maintenance Domain Level: 4 for NE1, NE2, and NE3
NOTE
The maintenance domain names and the maintenance domain levels of the NEs must be the same.
4. 1. 2.
Click OK. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association. The New Maintenance Association dialog box is displayed. Configure the parameters of the new maintenance associations. l Maintenance Association Name: MA1 for NE1, NE2, and NE3 l Relevant Service: services from NE1 to NE2 and NE3
NOTE
Step 2 Configure the maintenance associations of NE1, NE2, and NE3.
3.
in Relevant Service, and select associated services in the New Maintenance Click Association dialog box.
4. 1. 2. 3.
Click OK. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point. The system displays the New MEP Point dialog box.
Step 3 Configure the MEPs of NE1, NE2, and NE3.
A-298
A Task Collection
4.
Configure the parameters of the new MEPs. l MP ID: 101 for NE1, 102 for NE2, and 103 for NE3 l Direction: Ingress for NE1, NE2, and NE3 l CC Status: activation for NE1, NE2, and NE3
5.
Click OK.
Step 4 Configure the remote MEPs for the maintenance associations of NE1, NE2, and NE3. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Click New. Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed. 5. Set the parameters of the new remote MEPs. l Remote Maintenance Point ID: 102 and 103 for NE1, and 101 for NE2 and NE3
NOTE
Set the Remote Maintenance Point ID of NE1 to the MP ID of NE2 and NE3, and set the Remote Maintenance Point ID of NE2 and NE3 to the MP ID of NE1.
6.
Click OK.
Step 5 Test the availability of the Ethernet services from NE1 to NE2 and NE3. 1. 2.
Issue 03 (2011-04-10)
Select an NE from the Object Tree in the NE Explorer of the NE1, and then choose Configuration > Ethernet OAM Management > Ethernet Service OAM. Select the MD, MA, and MEP that correspond to Port 1, click OAM.
A Task Collection
3. 4.
Select Start LB. The LB Test window is displayed. Select MP ID, and set the parameters in Test Node. l Source Maintenance Point ID: 101 (maintenance point ID of NE1) l Destination Maintenance Point ID: 102 (maintenance point ID of NE2) l Transmitted Packet Count: 20 (recommended) l Transmitted Packet Length: 64 (64 is a recommended value, and the parameter can also be set to 128, 256, 512, 1024, and 1280 for testing the Ethernet services of different packet lengths.)
NOTE
The maximum Packet Length is 1400.
l Transmitted Packet Priority: 7 (recommended)
5. 6.
Click Start Test. Check Detection Result. The LossRate in the Detection Result should be 0.
7.
Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3. l Source Maintenance Point ID: 101 (maintenance point ID of NE1) l Destination Maintenance Point ID: 103 (maintenance point ID of NE3) l Transmitted Packet Count: 20 (recommended) l Transmitted Packet Length: 64 (recommended) l Transmitted Packet Priority: 7 (recommended) The LossRate in the Detection Result should be 0.
----End
A-300
Issue 03 (2011-04-10)
A Task Collection
A.12.4 Testing ATM Services

By testing ATM services, you can check whether ATM services are available over radio links. The ATM services can be tested using the ATM OAM function. Therefore, no tester is required.
Prerequisite
l l End-to-end ATM services must be configured. The NE user must have the authority of Operation Level or higher.

Web LCT
When an LB test is performed on the ATM service, the segment and end attribute is set to specify the types of transmitted ATM OAM cells. l l When Segment End Attribute is set to Segment point, segment LB cells are transmitted. When Segment End Attribute is set to Endpoint, end-to-end LB cells are transmitted.

This example shows how to test the ATM service over a radio link hop. The method for testing the ATM services over multiple radio link hops is the same. Figure A-3 shows the test connection diagram. NE A and NE B are the OptiX RTN 950. The services of the boards on the NE1 and NE2 are configured as follows: Attribute UNI Service source Bound port NE A 3-MD1-1 (Trunk-1) 3-MD1-1 (Port-1) 3-MD1-2 (Port-2) VPI VCI NNI PW ID Service source Bound port VPI VCI 1 51 1 101 501 NE B 3-MD1-1 (Trunk-1) 3-MD1-1 (Port-1) 3-MD1-2 (Port-2) 101 501 1 101 501
Issue 03 (2011-04-10)
A-301
A Task Collection
Figure A-3 Connection diagram for testing the connectivity of the ATM service
UNI VPI 1 VCI 51 NNI VPI 101 VCI 501 VPI 101 NNI VCI 501 UNI VPI 101 VCI 501
NodeB
NE A
NE B
RNC
Procedure
Step 1 Set the segment and end attributes of the ATM services on the NE A and NE B. 1. 2. 3. 4. 5. In the NE Explorer, select an NE and then choose Configuration > ATM OAM Management from the Function Tree. Click the Segment and End Attribute tab, and choose the ATM service to be tested. As for NE A and NE B, set Segment and End Attribute to Segment point. As for NE A and NE B, set Connection Direction to Sink. Click Apply.
Step 2 Set the identifier at the loopback point from NE A to NE B. 1. 2. In the NE Explorer, select an NE and then choose Configuration > ATM OAM Management from the Function Tree. Click the LLID tab. Set Country Code, Network Code, and NE Code. Set the parameters of NE A as follows: l Set Country Code to 00 86. l Set Network Code to 00 16. l Set NE Code to 00 09 78 01 00 00 00 00 00 00 00. Set the parameters of NE B as follows: l Set Country Code to 00 86. l Set Network Code to 00 16. l Set NE Code to 00 09 78 02 00 00 00 00 00 00 00.
NOTE
If the default LLID is unique on a network, the default LLID can also be used.
3.
Click Apply.
Step 3 Test the ATM service from NE A to NE B. 1. 2. 3.

A-302
In the NE Explorer, select NE A and then choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab, and choose the ATM service to be tested. Set Loopback Point NE of the ATM service to be tested to NE B.
A Task Collection
4. 5.
Click Test to start an LB test. In normal situations, Test Result should be Test succeeded. If the test is not successful, see Maintenance Guide and rectify the fault based on the test result.
Step 4 Test the ATM service from NE B to NE A. 1. 2. 3. 4. 5. 6. With reference of Step 1, set Connection Direction of NE A to Sink; set Connection Direction of NE B to Source. Select NE B from the NE Explorer. Then, choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab, and choose the ATM service to be tested. Set Loopback Point NE of the ATM service to be tested to NE B. Click Test to start an LB test. In normal situations, Test Result should be Test succeeded. If the test is not successful, see Maintenance Guide and rectify the fault based on the test result. ----End
A.12.5 Testing AM Switching

By testing AM switching, you can determine whether the AM switching is normal over radio links. A.12.5.1 Testing AM Switching by Using a BER Tester If a BER tester is available, the BER tester can be used to test AM switching. A.12.5.2 Testing AM Switching Without a BER Tester If no BER tester is available, you can test AM switching by querying the bit errors over radio links.
A.12.5.1 Testing AM Switching by Using a BER Tester

If a BER tester is available, the BER tester can be used to test AM switching.
Prerequisite
l l l l The antennas have been aligned. The radio links must be the Integrated IP radio links for which the AM function is enabled. The E1 service must be configured. The weather is favorable.

Precautions
The following test procedure uses the E1 services between NEs as an example.
A Task Collection
Procedure
Step 1 Connect the BER tester to an E1 port on the local NE.
NOTE
Test the E1 services with the highest priority, which are not discarded in the lowest-order modulation mode.
Step 2 On the remote NE, perform an inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 3 Configure the Hybrid/AM attribute on the local NE. 1. 2. 3. 4. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation Mode to the same value as Modulation Mode of the Guarantee AM Capacity. Click Apply.
Step 4 Query the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation Mode should be Manually Specified Modulation Mode of a pre-set value.
Step 5 Use the BER tester to test the bit errors. The test result should show that no bit error occurs. Step 6 Configure the Hybrid/AM attribute to the planned values on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned values. Click Apply.
4.
Step 7 Query the AM working status on the local NE.

A Task Collection
1. 2. 3.
Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation mode should be Modulation Mode of the Full AM Capacity of a preset value.
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of Modulation Mode of the Full AM Capacity.
Step 8 Check the BER test result. There should be no bit errors. Step 9 Release the inloop set in Step 2. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
----End
A.12.5.2 Testing AM Switching Without a BER Tester

If no BER tester is available, you can test AM switching by querying the bit errors over radio links.
Prerequisite
l l l The antennas have been aligned. The radio links must be the Integrated IP radio links for which the AM function is enabled. The weather is favorable.

Web LCT
Procedure
Step 1 Configure the Hybrid/AM attribute on the local NE. 1. 2.
Issue 03 (2011-04-10)
Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab.
A Task Collection
3. 4. 1. 2. 3. 4. 5. 6.
On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation Mode to the same value as Modulation Mode of the Guarantee AM Capacity. Click Apply. Select the desired IF board from the Object Tree in NE Explorer. In the Function Tree, choose Performance > Current Performance. In Monitored Object Filter Condition, select All. Set Monitor Period to 15-Minute. In Count, select FEC Performance. In Display Options, select Zero Data and Consecutive Severely Errored Seconds Second. Click Query. In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0. If the value is not 0, choose Reset on the performance register to clear the existing performance values.
Step 2 Query the 15-minute performance value of the IF board on the local NE.
Step 3 Query the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation Mode should be Manually Specified Modulation Mode of a pre-set value.
Step 4 Reset the performance event register. 1. 2. 3. 4. 1. 2. 3. Select the desired IF board from the Object Tree in NE Explorer. In the Function Tree, choose Performance > Current Performance. Click Reset. The confirmation dialog box is displayed. Click OK. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned values. Click Apply.
Step 5 Configure the Hybrid/AM attribute to the planned values on the local NE.
4.
Step 6 Repeat Step 2. Wait for a period, and query the 15-minute performance value of the IF board on the local NE.
A Task Collection
In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0. Step 7 Query the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation mode should be Modulation Mode of the Full AM Capacity of a preset value.
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of Modulation Mode of the Full AM Capacity.
----End
A.12.6 Testing Protection Switching

By testing protection switching, you can determine whether the protection switching is normal over radio links. A.12.6.1 Testing IF 1+1 Switching You can verify whether the IF 1+1 protection function is in the normal state by checking the working board of the IF 1+1 protection group before and after the switching. A.12.6.2 Testing N+1 Protection Switching You can verify whether the IF N+1 protection function works normally by checking the working board of the IF N+1 protection group before and after the switching. A.12.6.3 Testing SNCP Switching You can verify whether SNCP works normally by checking the working port of the SNCP protection group before and after the switching. A.12.6.4 Testing ERPS Switching You can verify whether the ERPS function is in the normal state by checking the port status of the ERPS protection group before and after the switching. A.12.6.5 Testing MPLS APS Protection Switching By checking the change in the status of MPLS tunnels before and after the MPLS APS switching, you can verify whether the MPLS APS protection function is normal. A.12.6.6 Testing Linear MSP Switching You can verify whether the linear MSP group works normally by checking the working port of the linear MSP group before and after the switching. A.12.6.7 Switching the System Control Unit and the Cross-Connect Unit When the OptiX RTN 950 is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required.
A.12.6.1 Testing IF 1+1 Switching

You can verify whether the IF 1+1 protection function is in the normal state by checking the working board of the IF 1+1 protection group before and after the switching.
A Task Collection
Prerequisite
l l l The antennas have been aligned. The equipment is configured with IF 1+1 protection. E1 services are configured.


Figure A-4 Configuration for testing IF 1+1 switching NE A and NE B are configured as follows: l l l l Main IF board: ISU2 in slot 3 Standby IF board: ISU2 in slot 5 Main ODU: ODU in slot 23 Standby ODU: ODU in slot 25
NE A
NE B
As shown in Figure A-4, the following procedures use the E1 services between NE A and NE B that are configured with 1+1 HSB protection as an example.
NOTE
l If Working Mode of the IF 1+1 protection is set to HSB, TX Status should be set to Mute for the ODU on the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs at NE A. l If Working Mode of the IF 1+1 protection is set to SD, TX Status should be set to Mute for the ODU on the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs at NE A. l If Working Mode of the IF 1+1 protection is set to FD, TX Status should be set to Mute for the ODU on the main channel of NE B. The switching occurs at NE A.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Board of Device or Active Board of Channel in Protection Group before and after the protection switching.
A-308
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 Check whether a BER tester is available at the central site. If... A BER tester is available on site No BER tester is available on site Then... Perform Step 2 through Step 11. Perform Step 6 through Step 10.
Step 2 On NE A at the central site, connect one E1 port to the BER tester. Step 3 On NE B at the remote site, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. Step 5 Set Enable Reverse Switching in the 1+1 HSB protection group for NE A. 1. 2. 3. 4. 1. 2. 3. 4. Select the desired NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab. Select the corresponding protection group in Protection Group, and set Enable Reverse Switching to Enable. Click Apply. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab. Select the corresponding protection group in Protection Group, and click Query. In Protection Group, the value of Active Board of Device should be the main IF board 3-ISU2.
Step 6 Before the switching, query the status of the protection group that is configured on NE A.
Step 7 Set TX Status to Mute for the main ODU 23-ODU of NE A. 1. 2. 3. 4.

Issue 03 (2011-04-10)
Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Mute. Click Apply.
A Task Collection
Step 8 Check service availability after the switching. If... A BER tester is available on site Then... Check the test result on the BER tester. It should show that the services are restored after transient interruption. Refer to A.12.1 Testing E1 Services Using PRBS to test availability of the E1 services. Refer to A.12.3 Testing Ethernet Services to test availability of the Ethernet services.
No BER tester is available on site, and the E1 services are transmitted on the radio link No BER tester is available on site, and the Ethernet services are transmitted on the radio link
Step 9 After the switching, query the status of the protection group that is configured on NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab. Select the corresponding protection group in Protection Group, and click Query. In Protection Group, the value of Active Board of Device should be the standby IF board 5-ISU2.
Step 10 Set TX Status to Unmute for the main ODU 23-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Unmute. Click Apply.
Step 11 Release the software inloop set in Step 3. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 12 Restore the setting of Enable Reverse Switching in Step 5. 1. 2. 3. Select the desired NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab. Select the corresponding protection group in Protection Group, and set Enable Reverse Switching to Disable.
A-310
A Task Collection
4.
Click Apply.
----End
A.12.6.2 Testing N+1 Protection Switching

You can verify whether the IF N+1 protection function works normally by checking the working board of the IF N+1 protection group before and after the switching.
Prerequisite
l l The antennas have been aligned. The equipment must be configured with the N+1 protection.


Figure A-5 Configuration for testing N+1 protection switching NE A and NE B are configured as follows: l l l l Main IF boards: ISU2 in slot 3 and ISU2 in slot 5 Standby IF board: ISU2 in slot 4 Main ODUs: ODU in slot 23 and ODU in slot 25 Standby ODU: ODU in slot 24
NE A
NE B
As shown in Figure A-5, the following procedures consider the E1 services between NE A and NE B that are configured with the N+1 (N=2) configuration as an example.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Switching Status in Slot Mapping Relation before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
A Task Collection
If... A BER tester is available on site No BER tester is available on site
Then... Perform Step 2 to Step 10. Perform Step 5 to Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit error occurs. Step 5 Before the switching, query the status of the protection group that is configured on NE B. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. Select the ID of the protection group to be queried, and then click Query. In Slot Mapping Relation, Switching Status of the working units 3-ISU2-1 and 5ISU2-1 and the protection unit 4-ISU2-1 should be Normal.
NOTE
If a fault arises, you must rectify the fault and then proceed with the N+1 protection testing.
Step 6 Set TX Status to Mute for the main ODU 23-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Mute. Click Apply.
Step 7 Check service availability after the switching. If... A BER tester is available on site Then... Check the test result on the BER tester. It should show that the services are restored after a transient interruption.
Issue 03 (2011-04-10)
A-312
A Task Collection
If... No BER tester is available on site, and the E1 services are transmitted on the radio link. No BER tester is available on site, and the Ethernet services are transmitted on the radio link.
Then... See A.12.1 Testing E1 Services Using PRBS to test availability of the E1 services. See A.12.3 Testing Ethernet Services to test availability of the Ethernet service.
Step 8 After the switching, query the status of the protection group that is configured on NE B. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. Select the ID of the protection group to be queried, and then click Query. In Slot Mapping Relation, the Switching Status of the working unit 3-ISU2-1 for the service that is configured with the N+1 protection should be SF.
Step 9 Set TX Status to Unmute for the main ODU 23-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Unmute. Click Apply.
Step 10 Release the loopback set in Step 3. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
----End
A.12.6.3 Testing SNCP Switching

You can verify whether SNCP works normally by checking the working port of the SNCP protection group before and after the switching.
Prerequisite
l l
Issue 03 (2011-04-10)
The antennas have been aligned. The equipment is configured with the SNCP.
A Task Collection


As shown in Figure A-6, the following procedures consider the E1 services between NE A and NE C that are configured with SNCP as an example. Figure A-6 shows a network composed of radio links, and the test procedures are similar in the case of a network composed of optical fiber links. Figure A-6 Configuration for testing SNCP switching NE A and NE C are configured as follows: l l l l West IF board: ISU2 in slot 3 East IF board: ISU2 in slot 4 West ODU: ODU in slot 23 East ODU: ODU in slot 24
NE A
Protecting SNC
Working SNC
NE D NE B
NE C
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Current Channel in Working CrossConnections before an d after the protection switching.
A-314
Issue 03 (2011-04-10)
A Task Collection
Procedure
Step 1 Check whether a BER tester is available at the central site. If... A BER tester is available on site No BER tester is available on site Then... Perform Step 2 through Step 10. Perform Step 5 through Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE C, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. Step 5 Before the switching, query the status of the protection group that is configured on NE C. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE C, and choose Configuration > SNCP Service Control from the Function Tree. In Working Coross-Connections, select an SNCP service that is already created, then click Function, and finally select Query Switching Status. The current SNCP status of the equipment is displayed in Working CorossConnections and Protection Coross-Connections. In Current Status, Normal should be displayed. In Current Channel, Working Path should be displayed.
Step 6 Set TX Status to Mute for the west ODU 23-ODU of NE A. 1. 2. 3.

Issue 03 (2011-04-10)
Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Mute.
A Task Collection
4.
Click Apply.
Step 7 Check service availability after the switching. If... A BER tester is available on site Then... Check the test result on the BER tester. It should show that the services are restored after a transient interruption. See A.12.1 Testing E1 Services Using PRBS to test availability of the E1 services.
No BER tester is available on site, and the E1 services are transmitted on the radio link.
Step 8 After the switching, query the status of the protection group that is configured on NE C. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE C, and choose Configuration > SNCP Service Control from the Function Tree. Click Function, and then select Query Switching Status. The current SNCP status of the equipment is displayed in Working CorossConnections and Protection Coross-Connections. In Current Status, the service switching mode is displayed. In Current Channel, Protection Path should be displayed.
Step 9 Set TX Status to Unmute for the west ODU 23-ODU of NE A. 1. 2. 3. 4. 1. 2. 3. 4. 5. 6. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Unmute. Click Apply. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 10 Release the loopback set in Step 3.
----End
A Task Collection
A.12.6.4 Testing ERPS Switching

You can verify whether the ERPS function is in the normal state by checking the port status of the ERPS protection group before and after the switching.
Prerequisite
l l The equipment is configured with ERPS. The network cable for carrying the working and protection Ethernet services of ERPS is properly connected.

Web LCT

As shown in Figure A-7, the following procedures use the Ethernet services that are configured with ERPS between NE A and NE D as an example. The owner node is NE D. Figure A-7 Configuration for testing ERPS NE A, NE B, NE C, and NE D are configured as follows: l l l l Main IF board: ISU2 in slot 3 Standby IF board: ISU2 in slot 5 Main ODU: ODU in slot 23 Standby ODU: ODU in slot 25
Issue 03 (2011-04-10)
A-317
A Task Collection
East
West
NE B Protection channel West NE A
East
NE D
East Working channel West NE C East West
Procedure
Step 1 Before the switching, query the status of the protection group that is configured on NE D. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE D, and choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Select the ERPS protection group to be queried, and click Query. The value of Status of State Machine should be Idle.
Step 2 Refer to A.12.3 Testing Ethernet Services to test availability of the Ethernet services. The LossRate in the Detection Result should be 0. Step 3 Set TX Status to Mute for the west ODU 23-ODU of NE A.
A Task Collection
1. 2. 3. 4. 1. 2. 3.
Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Mute. Click Apply. Select the NE from the Object Tree in the NE Explorer of NE D, and choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Select the ERPS protection group to be queried, and click Query. The value of Status of State Machine should be Protection.
Step 4 After the switching, query the status of the protection group that is configured on NE D.
Step 5 Refer to A.12.3 Testing Ethernet Services to test availability of the Ethernet services. The LossRate in the Detection Result should be 0. Step 6 Set TX Status to Unmute for the west ODU 23-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the desired ODU, and set TX Status to Unmute. Click Apply.
----End
A.12.6.5 Testing MPLS APS Protection Switching

By checking the change in the status of MPLS tunnels before and after the MPLS APS switching, you can verify whether the MPLS APS protection function is normal.
Prerequisite
l l The MPLS tunnel protection group must be created properly. The NE user must have the authority of Operation Level or higher.

Web LCT
1:1 protection In normal situations, services are transmitted in the working tunnel. That is, services are transmitted and received in a different tunnel respectively. When the working tunnel is faulty, the equipment at the transmit end transmits services through the protection tunnel, and the equipment at the receive end receive services through the protection tunnel after a negotiation through the APS protocol. Therefore, service switching is realized.

Figure A-8 shows the connection diagram for testing MPLS APS protection switching. NE A and NE B are the OptiX RTN 950 NEs.
A Task Collection
Figure A-8 Connection diagram for testing the MPLS APS protection
Working Tunnel NE A NE B
Protection Tunnel
Procedure
Step 1 Query the switching status of the current MPLS tunnel 1:1 protection group on NE A and NE B. 1. 2. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab, right-click the tested protection group, and then choose Query Switching Status from the short-cut menu, to check the MPLS protection group configured on the NE.
3.
Choose the protection group for switching, and check its switching status. In normal situations, the switching status should be Normal.
Step 2 Switch the services to the protection tunnel manually and forcedly. 1. 2.
A-320
In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching.
A Task Collection
3.
Right-click the tested protection group, and then choose Forced Switching from the shortcut menu.
NOTE
l Forced switching: With the highest priority, the operation is performed no matter whether the current status of the protection tunnel is normal. l Manual switching: The operation is performed only when the status of the protection tunnel is normal.
Step 3 Query the switching status of the MPLS 1:1 protection groups on NE A and NE B after the switching. 1. 2. 3. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching. Right-click the tested protection group and then choose Query Switching Status from the short-cut menu, to check Switching Status of the tunnel protection group. In normal situations, the switching status should be Forced Switching. 4. Query Active Tunnel of the tunnel protection group. In normal situation, Working should be Standby, and Protection should be Active.
NOTE
l If Forced Switching is performed at the previous step, the state of the protection group should be Forced Switching. l If Manual Switching to Protection is performed at the previous step, the state of the protection group should be Manual (Working to Protection) Switching.
Step 4 Restore the services on NE A and NE B to the working tunnel. 1. 2. 3. 4. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching. Right-click the tested protection group and then choose Clear from the short-cut menu. Click Query. Services is restored to the working tunnel. ----End
A.12.6.6 Testing Linear MSP Switching

You can verify whether the linear MSP group works normally by checking the working port of the linear MSP group before and after the switching.
Prerequisite
l
Issue 03 (2011-04-10)
The equipment must be configured with linear MSP.

A Task Collection
The working and protection optical fibers of the linear MSP are connected properly.


Figure A-9 shows linear MSP composed of the OptiX RTN equipment through the connection of optical fibers. The following procedures consider the E1 services from NE A to NE B as an example. Figure A-9 Configuration for testing linear MSP switching
NE A Working channel NE B
Protection channel
Precautions
NOTE
If no BER tester is available on site, you can compare the values of West Switching Status in Slot Mapping Relation before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site. If... A BER tester is available on site No BER tester is available on site Then... Perform Step 2 to Step 10. Perform Step 5 to Step 9.
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE B, perform a software inloop at the corresponding E1 port by using the NMS. 1. 2. 3. 4. 5. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed.
A Task Collection
6.
Click OK.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. If bit errors occur, see the Maintenance Guide for handling the bit errors. Step 5 Before the switching, query the status of the protection group that is configured on NE A. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Linear MS from the Function Tree. In Slot Mapping Relation, select Working Unit. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the value of West Switching Status should be Idle.
NOTE
In the case of the working and protection units of the services that are configured with the linear MSP, the values of West Switching Status should be Idle. If a fault arises, you must rectify the fault and proceed with the linear MSP switching testing.
Step 6 Shut down the laser for the working unit on NE A. 1. 2. 3. 4. 5. 6. Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Close. Click Apply. The Confirm dialog box is displayed. Click OK.
Step 7 Check service availability after the switching. If... The BER tester is available on site Then... Check the test result on the BER tester. It should show that the services are restored after a transient interruption. See A.12.1 Testing E1 Services Using PRBS to test availability of the E1 services.
No BER tester is available on site, and the E1 services are transmitted on the optical fiber link.
Step 8 After the switching, query the status of the protection group that is configured on NE A. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Linear MS from the Function Tree. In Slot Mapping Relation, select Working Unit. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the value of West Switching Status should be Switch upon signal failure.
Issue 03 (2011-04-10)
A Task Collection
NOTE
In the case of the 1+1 linear MSP, Revertive Mode can be set to Revertive or Non-Revertive. In the case of the 1:N linear MSP, Revertive Mode is always set to Revertive. l After the automatic switching occurs on the equipment, the services are restored. If Revertive Mode is set to Revertive for the linear MSP, the change in values of West Switching Status and Protected Unit can be queried after the WTR time expires. l After the automatic switching occurs on the equipment, the services are restored. If Revertive Mode is set to Non-Revertive for the linear MSP, stop and then start the MSP protocol to restore the value of West Switching Status to Idle.
Step 9 Turn on the laser for the working unit on NE A. 1. 2. 3. 4. 5. 6. Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Open. Click Apply. The Confirm dialog box is displayed. Click OK. Step 10 Release the loopback set in Step 3. 1. 2. 3. 4. 5. 6. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK.
----End
A.12.6.7 Switching the System Control Unit and the Cross-Connect Unit
When the OptiX RTN 950 is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 Select the desired NE from the NE Explorer. Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree. Step 3 Select Cross-Connect Board 1+1 Protection. Step 4 Perform the 1+1 protection switching on the board. If... Active Board is set to Working Board Active Board is set to Protection Board Step 5 In the prompt that is displayed, click OK. ----End Then... Click Working/Protection Switching. Click Restore Working/Protection.
Issue 03 (2011-04-10)
A-325
B Parameters Description
Parameters Description
This chapter describes the parameters used in this document. B.1 Parameters for Network Management This topic describes the parameters that are related to network management. B.2 Radio Link Parameters This topic describes the parameters that are related to radio links. B.3 Multiplex Section Protection Parameters This topic describes the parameters that are related to multiplex section protection (MSP). B.4 SDH/PDH Service Parameters This topic describes the parameters that are related to SDH/PDH services. B.5 Parameters for Board Interfaces This topic describes the parameters that are related to board interfaces. B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane This section describes the parameters for the Ethernet services and Ethernet features on the packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.7 Parameters for Ethernet Services and Ethernet Features on the EoPDH Plane This section describes the parameters for the Ethernet services and Ethernet features on the EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.8 RMON Parameters This topic describes the parameters that are related to RMON performances. B.9 Parameters for MPLS/PWE3 Services This topic describes parameters that are related to MPLS/PWE3 services. B.10 Clock Parameters This topic describes the parameters that are related to clocks. B.11 Parameters for the Orderwire and Auxiliary Interfaces This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
Issue 03 (2011-04-10)
B-1
B.1 Parameters for Network Management

This topic describes the parameters that are related to network management. B.1.1 Parameters for NE Management This topic describes the parameters that are used for managing network elements (NEs). B.1.2 Parameters for Communications Management This topic describes the parameters that are used for communications management. B.1.3 Parameters for Network Security Management This topic describes the parameters that are related to network security management.
B.1.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs). B.1.1.1 Parameter Description: NE Searching This topic describes the parameters that are used for searching for NEs. B.1.1.2 Parameter Description: NE Creation This topic describes the parameters that are related to NE creation. B.1.1.3 Parameter Description: Login to an NE This topic describes the parameters that are used for logging into an NE. B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs This topic describes the parameters that are used for changing NE IDs. B.1.1.5 Parameter Description: NE Time Synchronization This topic describes the parameters that are used for synchronizing the time of NEs. B.1.1.6 Parameter Description: Localization Management of the NE Time This parameter describes the parameters that are used for localization management of the NE time. B.1.1.7 Parameter Description: License Management This topic describes the parameters that are used for managing the license. B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs This parameter describes the parameters that are used for automatically disabling the functions of an NE.
B.1.1.1 Parameter Description: NE Searching

This topic describes the parameters that are used for searching for NEs.
Navigation Path
In NE List, click NE Search.
B-2
Issue 03 (2011-04-10)
Parameters for Searching NEs

Parameter Domain Value Range 129.9.255.255 10.255.255.255 NE Name NE ID Gateway GNE Non-GNE Gateway IP Address Default Value 10.255.255.255 Description This parameter specifies the network segment to be searched. This parameter displays the name of the found NE. This parameter displays the ID of the found NE. This parameter displays whether the found NE is a GNE or non-GNE. This parameter displays the gateway IP address of the found NE. This parameter displays the communication port number of the found NE. This parameter displays the gateway type of the found NE.
Port No.
1400
1400
Gateway Type
IP Gateway
IP Gateway
Parameters for Managing a Network Segment

Parameter Domain Type Value Range GNE IP Domain GNE IP Address Default Value GNE IP Domain Description l To search for all the NEs that communicate with the GNE, select GNE IP Domain. l To search for the GNE only, select GNE IP Address.
Issue 03 (2011-04-10)
B-3
Parameter Domain Address
Value Range -
Default Value -
Description l When Domain Type is GNE IP Domain, enter the IP network segment where the GNE is located, for example, 129.9.255.255. l When Domain Type is GNE IP Address, enter the IP address of the GNE, for example, 129.9.x.x.
Related Tasks
A.1.1.1 Creating NEs by Using the Search Method
B.1.1.2 Parameter Description: NE Creation

This topic describes the parameters that are related to NE creation.
Navigation Path
In NE List, click Add NE. Then, select Europe.
Parameters on the Main Interface

Parameter NE ID Value Range 1 to 49135 Default Value Description l ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the networks that are managed by the same NMS. l Set this parameter according to the DCN planning information. l The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS. Extended ID 1 to 254 9 l Do not change the Extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID. l It is recommended that this parameter takes the default value.
B-4
Issue 03 (2011-04-10)
Parameter Gateway Type
Value Range IP Gateway Serial Port
Default Value IP Gateway
Description This parameter specifies the type of the gateway that is used for the communication between the Web LCT and the NEs. This parameter specifies the IP address of the gateway NE to which the NE to be created belongs. This parameter is displayed only when Gateway Type is set to IP Gateway.
IP Address
This parameter is set to 129.9.0.x when the NE is delivered from the factory. "x" indicates the basic NE ID that is set when the NE is delivered from the factory. l 1400 (when Gateway Type is set to IP Gateway) l COM1 (when Gateway Type is set to Serial Port) 1200bps
Port
l 1400 (when Gateway Type is set to IP Gateway) l COM1-COM32 (when Gateway Type is set to Serial Port)
This parameter specifies the port corresponding to the gateway NE to which the NE to be created belongs.
Baud Rate
1200bps 2400bps 4800bps 9600bps 19200bps 38400bps 57600bps 115200bps
This parameter specifies the communication rate between the NE to be created and the corresponding gateway NE. This parameter is displayed only when Gateway Type is set to Serial Port.
User Name
lct
This parameter specifies the name of the user. This parameter can take the default value in the case of initial login. The default password of user lct is password.
Password
Related Tasks
A.1.1.2 Creating NEs by Using the Manual Method
B.1.1.3 Parameter Description: Login to an NE

This topic describes the parameters that are used for logging into an NE.
Issue 03 (2011-04-10)
B-5
Navigation Path
In the NE List, select the target NE and click NE Login.
Parameters
Parameter User Name Value Range Default Value lct Description This parameter specifies the name of the user. This parameter can take the default value in the case of initial login. The default password of user lct is password. When this parameter is selected, enter User Name and Password to log in to all the selected NEs. When this parameter is selected, enter User Name and Password that were used for the latest login to log in to the NE.
Password Use the same user name and password to login Use the user name and password that was used last time
Selected Deselected Selected Deselected
Deselected
Deselected
Related Tasks
A.1.1.3 Logging In to an NE
B.1.1.4 Parameter Description: NE Attribute_Changing NE IDs

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the Function Tree. Click Modify NE ID.
B-6
Issue 03 (2011-04-10)
Parameters for Changing NE IDs

Parameter New ID Value Range Default Value Description l The new ID refers to the basic ID. If the extended ID is not used, the basic ID of an NE must be unique on the networks that are managed by the same NMS. l This parameter is set according to the planning information.
NOTE The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.
New Extended ID
1 to 254
If the number of existing NEs does not exceed the range represented by the basic ID, do not change the extended ID.
Related Tasks
B.1.1.5 Parameter Description: NE Time Synchronization

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Synchronization from the Function Tree. Set the synchronous mode.
Parameters for NE Time Synchronization

Parameter NE Name NE ID Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the ID of the NE.
Issue 03 (2011-04-10)
B-7
Parameter Synchronous Mode
Value Range Standard NTP NM Null
Default Value Null
Description l If this parameter is set to NM, the NE synchronizes the time of the NMS server. l If this parameter is set to Standard NTP, the NE synchronizes the Network Time Protocol (NTP) server through the standard NTP.
Standard NTP Authentication
Enabled Disabled
Disabled
This parameter is valid only when Synchronous Mode is set to Standard NTP.
Parameters for the Standard NTP Server

Parameter Standard NTP Server Flag Value Range NE ID NE IP Default Value NE ID Description l If the NE functions as the gateway NE, this parameter is set to IP. l If the NE functions as a non-gateway NE and communicates with the gateway NE through the HWECC protocol, this parameter is set to NE ID. l If the NE functions as a non-gateway NE and communicates with the gateway NE through the IP protocol, this parameter is set to IP.
B-8
Issue 03 (2011-04-10)
Parameter Standard NTP Server
Value Range -
Default Value -
Description l If the NE functions as the gateway NE, this parameter is set to the IP address of the external NTP server. l If the NE functions as a non-gateway NE, this parameter is set to the ID or IP address of the gateway NE.
Standard NTP Server Key
0 to 1024
l If the NTP server does not need to authenticated, this parameter is set to the value "0". l If the NTP server needs to be authenticated, the authentication is performed according to the allocated key of the NTP server. In this case, the NE authenticates the NTP server based on the key and the corresponding password (specified in the management of the standard NTP key).
Standard NTP Version
2 3
Set this parameter according to the settings for the standard NTP protocol version used at the peer end. This parameter specifies whether to select a server preferentially when multiple NTP servers are available.
Used First
Yes No
No
Parameters of the access control rights

Parameter ACL No. Value Range 1 to 250 Default Value 1 Description This parameter specifies the number of the ACL.
Issue 03 (2011-04-10)
B-9
Parameter NE Flag
Value Range NE ID NE IP
Default Value NE ID
Description l When ECC is used to communicate with the standard NTP server, set the parameter to NE ID. l When the IP protocol is used to communicate with the standard NTP server, set the parameter to NE IP.
NE Whether to Receive Data Packet Right Level
Yes No query synchronize server peer
Yes
This parameter specifies the ID or IP address of an NE. This parameter specifies whether to receive packets from an NE. The equipment provides four levels of access control. When an NTP access request is received on the local equipment, the request is matched with the levels from the minimum access limit to the maximum access limit, and the first matched level prevails. The matching order is as follows: l Peer (minimum access limit): The time request and the control query can be carried out for the NTP service of the local equipment. The local clock can also be synchronized with the remote server. l Server: The time request and the control query can be carried out for the NTP service of the local equipment, but the local clock is not synchronized to the remote server. l Synchronization: The time query is allowed for only the NTP service of the local equipment. l Query (maximum access limit): The control query can be carried out only for the NTP service of the local equipment.
query
Parameters of the NTP key management

Parameter Encryption Key Value Range MD5 1 to 1024 Default Value MD5 1 Description This parameter specifies the MD5 key algorithm. This parameter specifies the number of the key.
B-10
Issue 03 (2011-04-10)
Parameter Password Trusted
Value Range Yes No
Default Value No
Description This parameter specifies the password of the key. If you set this parameter to No, the key is verified but cannot be trusted during the clock synchronization. Therefore, the clock of the NE cannot be synchronized.
Parameters for Setting Automatic Synchronization

Parameter Synchronization Starting Time Value Range Default Value Description l This parameter specifies the start time of the synchronization period. After this parameter is specified, the NMS and the NE synchronize the time once at the intervals of Period(days). l It is recommended that you use the default value. DST Selected Deselected Deselected l This parameter indicates whether Synchronization Starting Time is the daylight saving time. l This parameter is set according to the actual situation. Period(days) 1 to 300 1 l This parameter indicates the period of synchronizing the time of the NE with the time of the NMS. l It is recommended that you use the default value.
Related Tasks
Issue 03 (2011-04-10)
B-11
B.1.1.6 Parameter Description: Localization Management of the NE Time

This parameter describes the parameters that are used for localization management of the NE time.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Localization Management from the Function Tree. Set the correct time zone and daylight saving time of the NE depending on the location of the NE.
Parameters for Localization Management of the NE Time

Parameter NE TimeZone DST Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the time zone. This parameter indicates whether DST is enabled.
Parameters for Time Zone

Parameter Time Zone Value Range Default Value Description l After the time zone is changed, the current time of the NE is changed accordingly. l This parameter is set according to the place where the NE is located. DST Selected Deselected Deselected l The parameters related to daylight saving time can be valid only when this parameter is selected. l This parameter is set according to the situation whether daylight saving time is used in the place where the NE is located. Offset 1 to 120 Unit: minute(s) Start Rule WEEK DATE Start Time WEEK This parameter specifies the offset value of the daylight saving time. This parameter specifies the method of adjusting the daylight saving time. This parameter specifies the start daylight saving time.
B-12
Issue 03 (2011-04-10)
Parameter End Rule
Value Range WEEK DATE
Default Value WEEK
Description This parameter specifies the method of adjusting the daylight saving time. This parameter specifies the end daylight saving time.
End Time
Related Tasks
A.1.1.8 Localizing the NE Time
B.1.1.7 Parameter Description: License Management

This topic describes the parameters that are used for managing the license.
Navigation Path
1. 2. In the NE Explorer, select the NE and then choose Configuration > License Management from the Function Tree. Click the License Management tab.
Parameters for Managing Licenses

Parameter Board File Type Capacity Load Value Range Default Value Description This parameter displays the boards that need to be supported by licenses. This parameter displays the license type corresponding to each board. This parameter displays the capacity of each board. This parameter displays whether the corresponding license file is loaded to each board.
B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs

This parameter describes the parameters that are used for automatically disabling the functions of an NE.
Navigation Path
1. 2.
Issue 03 (2011-04-10)
In the NE Explorer, select the NE and then choose Configuration > Automatic Disabling of NE Function from the Function Tree. Click the Automatic Disabling of NE Function tab.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-13
Parameters for Automatically Disabling the Functions of NEs

Parameter Operation Type Value Range Default Value Description This parameter indicates the type of the operation, such as loopback, and shutdown of the laser. This parameter specifies whether to automatically disable the operations such as loopback, and shutdown of the laser. This parameter specifies the time of automatically disabling the operations such as loopback, and shutdown of the laser.
Auto Disabling
Disabled Enabled
Enabled
Auto Disabling Time(min)
1 to 2880
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management. B.1.2.1 Parameter Description: NE Communication Parameter Setting This topic describes the parameters that are used for NE communication setting. B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration This topic describes the parameters that are used for configuring the DCC rate. B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management This topic describes the parameters that are used for DCC transparent transmission management. B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC This topic describes the parameters that are related to the extended ECCs of Ethernet ports. B.1.2.5 Parameter Description: NE ECC Link Management This topic describes the parameters that are used for NE ECC link management. B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management This topic describes the parameters that are used for IP route management. B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation This topic describes the parameters that are used for new static IP routes. B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings This topic describes the parameters that are used for OSPF settings. B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP This topic describes the parameters that are used for configuring the proxy ARP. B.1.2.10 Parameter Description: Port OSPF Setting This section describes the parameters that are used for setting port OSPF parameters. B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter This topic describes the parameters that are related to the network layer of the OSI protocol model. B.1.2.12 Parameter Description: OSI Management_Routing Table
B-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2011-04-10)
This topic describes the parameters that are related to OSI routing tables. B.1.2.13 Parameter Description: OSI Management_OSI Tunnel This topic describes the parameters that are related to the OSI tunnels. B.1.2.14 Parameter Description: DCN Management_Bandwidth Management This topic describes the parameters that are used for bandwidth management of the inband DCN. B.1.2.15 Parameter Description: DCN Management_Port Setting This topic describes the parameters that are used for setting ports of the inband DCN. B.1.2.16 Parameter Description: DCN Management_Protocol Setting This topic describes the parameters that are used for setting a protocol of the inband DCN. B.1.2.17 Parameter Description: DCN Management_Access Control This section describes the parameters for configuring access control. B.1.2.18 Parameter Description: Access Control This topic describes the parameters that are used for access control of the NMS.
B.1.2.1 Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree.
Parameters for NE Communication Setting

Parameter IP Value Range Default Value Before delivery, the IP address of the NE is set to 129.9.0.x. The letter x indicates the basic ID. 0.0.0.0 255.255.0.0 Description In the HWECC solution, an IP address is set according to the following rules: l The IP address, subnet mask, and default gateway of the gateway NE should meet the planning requirements of the external DCN. l If an NE uses the extended ECC, the IP address must be in the same network segment. l The IP address of other NEs should be set according to the NE ID. In this case, the IP address of an NE should be set in the format of 0x81000000+ID. That is, if the ID is 0x090001, the IP address should be set to 129.9.0.1. l Do not change the extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID. l It is recommended that this parameter takes the default value.
Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-15
Gateway IP Subnet Mask
Extended ID
1 to 254
Parameter NSAP Address
Value Range -
Default Value -
Description This parameter is valid only when the OSI over DCC solution is applied. This parameter is used to set only the area ID of an NSAP address. The other parts of the NSAP address are automatically generated by the NE. l Specifies the connection mode that the gateway NE allows the NMS to use for connecting to the gateway NE. l If the gateway NE has no special security requirement for connection to the NMS, Connection Mode can be set to Common. l If the gateway NE requests secure connection to the NMS for preventing information interception and cracking, Connection Mode needs to be set to Security SSL. l If NE communication security level needs to be the same as NMS communication security level, Connection Mode needs to be set to Common + Security SSL. l The default parameter value is recommended unless the gateway NE requires that the NMS use the SSL connection mode. l The parameter value takes effect only when it is set for a gateway NE and the gateway NE is connected to the NMS by means of the IP protocol.
Connection Mode
Common + Security SSL Common Security SSL
Common + Security SSL
Related Tasks
A.1.4.1 Setting NE Communication Parameters
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration

This topic describes the parameters that are used for configuring the DCC rate.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab.
B-16
Issue 03 (2011-04-10)
Parameters for DCC Rate Configuration

Parameter Port Enabled/Disabled Value Range Enabled Disabled Default Value Enabled Description This parameter indicates the port that is connected to the DCC channel. It is recommended that you use the default value, except for the following cases: l If the port is connected to the other ECC subnet, Enabled/Disabled is set to Disabled. l If the port is connected to a third-party network and does not exchange the network management information with other ports, Enabled/Disabled is set to Disabled. Channel D1-D3 D4-D12 D1-D12 D1-D1 D1-D1 (for the PDH radio whose transmission capacity is less than 16xE1) D1-D3 (for other cases) It is recommended that you use the default value, except for the following cases: l If the IP over DCC or OSI over DCC solution is adopted, Channel for the SDH line ports is set to a value that is the same as the value for third-party network. l If the DCC transparent transmission solution is adopted, the value of Channel for the SDH line ports should not conflict with the value that is set for the third-party network. DCC Resources Communication Status Protocol Type HWECC TCP/IP OSI HWECC This parameter indicates the DCC resources. This parameter indicates the communication status. It is recommended that you use the default value, except for the following cases: l If the IP over DCC solution is adopted, Protocol Type is set to TCP/IP. l If the OSI over DCC solution is adopted, Protocol Type is set to OSI. LAPD Role User Network User l This parameter is valid only when Protocol Type is set to OSI. l In the case of a DCC channel, LAPD Role must be set to User for one end and must be set to Network for the other end. LAPD MTU Displays the maximum LAPD packet size.
Issue 03 (2011-04-10)
B-17
Related Tasks
A.1.4.2 Configuring DCCs
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management

This topic describes the parameters that are used for DCC transparent transmission management.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Click the DCC Transparent Transmission Management tab. Click Create.
Parameters for DCC Transparent Transmission Management

Parameter Source Timeslot/ Porta Transparent Transmission of Overhead Bytes at Source Port Value Range D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 K1 K2 X1 X2 X3 X4 Default Value Description This parameter specifies the source timeslot or port. l Only one overhead byte can be selected each time. l X1, X2, X3, and X4 indicate the customized overhead bytes that are used for transmitting asynchronous data services. l An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel.
B-18
Issue 03 (2011-04-10)
Parameter Sink Timeslot/ Porta Transparent Transmission of Overhead Bytes at Sink Port
Value Range D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 K1 K2 X1 X2 X3 X4
Default Value -
Description This parameter specifies the sink timeslot or port. l Only one overhead byte can be selected each time. l An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel. l Generally, Transparent Transmission of Overhead Bytes at Sink Port can be set to a value that is the same as or different from the value in the case of Transparent Transmission of Overhead Bytes at Source Port.
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions the same regardless of the source port or sink port.
Related Tasks
A.1.4.4 Configuring DCC Transparent Transmission
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC

This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the Function Tree.
Parameters for the ECC Extended Mode

Parameter ECC Extended Mode Value Range Auto mode Specified mode Default Value Auto mode Description It is recommended that you use the default value.
Parameters for Setting the Server

Parameter IP Port Value Range 1601 to 1699 Default Value 0 Description This parameter indicates the IP address of the server. l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the server of the extended ECC. In normal cases, the NE that is close to the NMS functions as the server. l This parameter can be set to any value from 1601 to 1699.
Parameters for Setting the Client

Parameter Opposite IP Port Value Range 1601 to 1699 Default Value 0.0.0.0 0 Description l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the client of the extended ECC. Except for the NE that functions as the server, all other NEs that use the extended ECC can function as the client. l Opposite IP and Port are respectively set to the IP address of the server NE and the specified port number.
Related Tasks
A.1.4.3 Configuring Extended ECC Communication
B-20
Issue 03 (2011-04-10)
B.1.2.5 Parameter Description: NE ECC Link Management

This topic describes the parameters that are used for NE ECC link management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC Link Management from the Function Tree.
Parameter for NE ECC Link Management

Parameter Destination NE Transfer NE Distance Value Range Default Value Description This parameter specifies the sink NE of the ECC connection. This parameter specifies the next transfer NE and the direction of the ECC route. l This parameter specifies the number of NEs (excluding the source NE and sink NE) through which the ECC route passes, namely, the number of ECC packet forwarding attempts. The value can be set to a value that is greater than the number of actual ECC packet forwarding attempts. If the value is set to a value that is less than the number of actual ECC packet forwarding attempts, however, the destination NE fails to be accessed. l If the value is set to 0, it indicates that the source NE is adjacent to the destination NE. Level l This parameter indicates that multiple ECC routes from the source NE to the destination NE may be available. An ECC route of a higher priority is selected to transmit the packets to the destination NE. l If the ECC route is generated automatically, the priority is 4. l If the ECC route is added manually, the priority is 5. Mode SCC No. This parameter indicates the ECC routing mode. This parameter specifies the physical port through which the ECC route passes. The value of this parameter is automatically assigned the NE.
Issue 03 (2011-04-10)
B-21
Related Tasks
A.1.4.13 Querying ECC Routes
B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management

This topic describes the parameters that are used for IP route management.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the IP Route Management tab.
Parameters for IP Route Management

Parameter Destination Address Value Range Default Value Description This parameter indicates the destination address of the packets. This parameter can be set to a valid IP address of class A, B, or C only, but cannot be set to the IP address of the local host or the loopback address with the 127 field. This parameter indicates the subnet mask of the destination address of the packets. This parameter indicates the IP address of the gateway on the subnetwork where the NE is located, namely, the IP address of the next hop of the packets.
Subnet Mask Gateway
B-22
Issue 03 (2011-04-10)
Parameter Protocol
Value Range -
Default Value -
Description l DIRECT: indicates the route between the local NE and an adjacent NE. l STATIC: indicates the route that is created manually. l OSPF: indicates the route between the local NE and a non-adjacent NE. l RIP: indicates the route that is discovered by the routing information protocol. l OSPF_ASE: indicates the route whose Destination Address is beyond the OSPF domain. l OSPF_NSSA: indicates the route whose Destination Address is in a not so stubby area (NSSA). l A route can be deleted in the case of STATIC only, but cannot be edited in the other cases. l Compared with a dynamic route, a static route has a higher priority. If any conflict occurs, the static route is preferred.
Interface
This parameter indicates the interface that is used on the route. Interface is a concept specified in the TCP/IP protocol stack. In the TCP/IP protocol stack, you can create multiple types of interface, such as a loopback interface (namely, the interface whose IP address is 127.0.0.1), an Ethernet interface, and PPP interface. Each interface must have a unique interface name. This parameter indicates the maximum number of routers through which the packets are transmitted. Metric is used to indicate the overhead bytes that are transmitted to the destination address. The smaller the value, the less the overhead bytes. If multiple routes can reach the same destination address, a route whose overhead is less is preferred to transmit the packets.
Metric
Related Tasks
A.1.4.14 Querying IP Routes
Issue 03 (2011-04-10)
B-23
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

This topic describes the parameters that are used for new static IP routes.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the IP Route Management tab. Click New.
Parameters for Creating IP Routes

Parameter Destination Address Value Range Default Value Description This parameter specifies the destination address of the packets. This parameter can be set to a valid IP address of class A, B, or C only, but cannot be set to the IP address of the local host or the loopback address with the 127 field. This parameter indicates the subnet mask of the destination address of the packets. This parameter specifies the IP address of the gateway on the subnetwork where the NE is located, namely, the IP address of the next hop of the packets.
Subnet Mask Gateway
Related Tasks
A.1.4.5 Creating Static IP Routes
B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings

This topic describes the parameters that are used for OSPF settings.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the OSPF Parameter Settings tab.
B-24
Issue 03 (2011-04-10)
OSPF Parameters
Parameter Area Value Range Default Value 0.0.0.0 Description l The OSPF protocol supports the division of NEs into multiple areas. Only the NEs in the same area can transmit the OSPF packets to each other to generate the route. l When setting the area for the NEs, you need to set the NEs that run the OSPF protocol to the same area. DCC Hello Timer (s) 1 to 255 10 l DCC Hello Timer(s) specifies the Hello packet timer at the DCC interface. l The Hello packets are used for detecting the neighbor router on the network that is connected to the router. By periodically transmitting the hello packets, you can determine whether the interface on the neighbor router is still in the active status. l DCC Hello Timer(s) determines the interval for the hello packet timer to transmit the hello packets. l In the case of two interconnected NEs, DCC Hello Timer(s) must be set to the same value. DCC Neighbor Dead Time(s) 1 to 65535 40 l DCC Neighbor Dead Time(s) specifies the dead time of a neighbor router at the DCC interface. l If the local router fails to receive the hello packets from the connected neighbor router within the time specified in DCC Neighbor Dead Time(s), it considers that the neighbor router is unavailable. l DCC Neighbor Dead Time(s) should be set to a value that is a minimum of twice the value of DCC Hello Timer (s). l In the case of adjacent NEs, DCC Neighbor Dead Time(s) must be set to the same value. Otherwise, the OSPF protocol fails to operate normally. DCC Retransmission Timer(s) 1 to 65535 5 DCC Retransmission Timer(s) specifies the interval for transmitting a request through the DCC interface to retransmit the link state advertisement (LSA) packets.
Issue 03 (2011-04-10)
B-25
Parameter DCC Delay(s)
Value Range 1 to 3600
Default Value 1
Description l DCC Delay(s) specifies the delay time to transmit the LSA packets through the DCC interface. l The LSA packets in the LSA database of the local router are aged as the time elapses, but are not aged when they are being transmitted on the network. Hence, before the LSA packets are transmitted, you need to increase the age of the LSA packets based on the value of DCC Delay(s).
LAN Hello Timer (s)
1 to 255
10
l DCC Hello Timer(s) specifies the hello packet timer at the LAN interfaces. l The hello packets are used for detecting the neighbor router on the network that is connected to the router. By periodically transmitting the hello packets, you can determine whether the interface on the neighbor router is still in the active status. l LAN Hello Timer(s) determines the interval for the hello packet timer of the NE to transmit the hello packets. l In the case of two interconnected NEs, LAN Hello Timer(s) must be set to the same value.
LAN Neighbor Dead Time(s)
1 to 65535
40
l LAN Neighbor Dead Time(s) specifies the dead time of a neighbor router at the LAN interface. l If the local router fails to receive the hello packets from the connected neighbor router within the time specified in LAN Neighbor Dead Time(s), it considers that the neighbor router is unavailable. l LAN Neighbor Dead Time(s) should be set to a value that is a minimum of two times the value of LAN Neighbor Dead Time(s). l In the case of adjacent NEs, DCC Neighbor Dead Time(s) must be set to the same value. Otherwise, the OSPF protocol fails to operate normally.
B-26
Issue 03 (2011-04-10)
Parameter LAN Retransmission Timer(s) LAN Delay(s)
Default Value 5
Description LAN Retransmission Timer(s) specifies the time for transmitting a request for retransmission of the LSA packets through the LAN interface. l LAN Delay(s) specifies the delay time to transmit the LSA packets through the LAN interface. l The LSA packets in the LSA database of the local router are aged as the time elapses, but are not aged when they are being transmitted on the network. Hence, before the LSA packets are transmitted, you need to increase the age of the LSA packets based on the value of LAN Delay(s).
1 to 3600
OSPF Status
Enabled Disabled
Enabled
Specifies whether to enable the OSPF.
STUB Area
Enabled Disabled
Disabled
l Specifies whether to enable the STUB Area. l Set this parameter as required.
NSSA Area
Enabled Disabled
Disabled
l Specifies whether to enable the NSSA Area. l Set this parameter as required.
Direct route
Enabled Disabled
Disabled
l Specifies whether to enable the Direct route. l Direct route: the route detected by the link layer protocol. l Set this parameter as required.
Static route
Enabled Disabled
Disabled
l Specifies whether to enable the Static route. l Static route: the route manually configured by the network administrator. l Set this parameter as required.
RIP route
Enabled Disabled
Disabled
l Specifies whether to enable the RIP route. l RIP route: the route detected by the routing protocol. l Set this parameter as required.
Issue 03 (2011-04-10)
B-27
Parameter Opaque LSA of External Network Port
Value Range Enabled Disabled
Default Value Disabled
Description l Specifies whether to enable the Opaque LSA of External Network Port. l If this parameter is set to Enabled, it indicates that the Ethernet NM interface is used to transmit NM message. l Set this parameter as required.
LAN Interface
Enabled Disabled
Disabled
l Specifies whether to enable the OSPF at the Ethernet NM interface. l If this parameter is set to Enabled, it indicates that the Ethernet NM interface achieves OSPF communication with other equipment.
Related Tasks
A.1.4.6 Setting Parameters of the OSPF Protocol
B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP

This topic describes the parameters that are used for configuring the proxy ARP.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the Proxy ARP tab.
B-28
Issue 03 (2011-04-10)
Parameters for configuring the proxy ARP

Parameter Proxy ARP Value Range Disabled Enabled Default Value Disabled Description l The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE.
Related Tasks
A.1.4.7 Enabling the ARP Proxy
B.1.2.10 Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Navigation Path
1. 2. In the NE Explorer, select the required NE and choose Communication > IP Protocol Stack Management from the Function Tree. Click the Port OSPF Parameter Settings tab.
Port OSPF Parameters

Parameter Port Path Type
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description Displays the ports that allow OSPF parameters to be set. Displays the current DCC channel type.
B-29
Parameter OSPF Status
Default Value Enabled
Description l Specifies whether to enable the OSPF. l Set this parameter as required.
Opaque LSA of External Network Port
Enabled Disabled
Enabled
l Specifies whether DCC channels support Opaque LSAs. l Set this parameter as required.
B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter

This topic describes the parameters that are related to the network layer of the OSI protocol model.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the Network Layer Parameters tab.
Network Layer Parameters

Parameter NE Configuration Role Value Range ES L1 L2 Default Value L1 Description This parameter indicates the name of the NE. l An NE whose Configuration Role is set to L1 cannot function as a neighbor of an NE in the other area. It uses a route in the local area only and accesses the other area by distributing the default route of the nearest L2 NE. l An NE whose Configuration Role is set to L2 can function as a neighbor of an NE in the other area and can use a route in the backbone area. The backbone area is a collection that is formed by consecutive L2 NEs. That is, the L2 NE of all the roles must be consecutive (connected to each other).
NOTE Configuration Role cannot be set to ES.
Current Role
This parameter indicates the current role.
Related Tasks
A.1.4.8 Configuring the CLNS Role
B.1.2.12 Parameter Description: OSI Management_Routing Table

This topic describes the parameters that are related to OSI routing tables.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the Routing Table tab.
Parameters for Link Adjacency Table

Parameter Port Data Link Layer Adjacency No. Value Range Default Value Description This parameter indicates the port used for OSI communication. This parameter indicates the protocol that is used at the data link layer. l This parameter specifies the identifier of the adjacency that is set up by two NEs through the OSI protocol. One adjacency number corresponds to an OSI adjacency. l The value is dynamically allocated by the NE. Adjacency Type Adjacency State Peer End Area ID This parameter indicates the type of the adjacency. This parameter indicates the state of the adjacency. This parameter indicates the area ID that is contained in the NSAP address of the opposite NE. This parameter indicates the system ID of the opposite NE. Generally, the system ID is the MAC address.
Peer End System ID
Parameters for L1 and L2 Routing Tables

Parameter Destination Area ID Destination SYSID Value Range Default Value Description This parameter indicates the area ID of the destination NE. This parameter indicates the system ID of the destination NE. Generally, the system ID is the MAC address.
B-31
Issue 03 (2011-04-10)
Parameter Metric
Value Range -
Default Value -
Description This parameter indicates the number of hops that reach the destination NE or destination area. This parameter indicates the number of the adjacent link that is connected to the destination NE. This parameter indicates the number of the adjacent link that is connected to the destination NE.
Adjacency No.1
Adjacency No.2
Related Tasks
A.1.4.15 Querying OSI Routes
B.1.2.13 Parameter Description: OSI Management_OSI Tunnel

This topic describes the parameters that are related to the OSI tunnels.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the OSI Tunnel tab.
Parameters for OSI Tunnel Attributes

Parameter Remote IP Address LAPD Actor Value Range User Network Default Value User Description This parameter indicates the IP address of the opposite end of the OSI tunnel. l This parameter specifies the LAPD actor. l If the adjacent NEs run the OSI protocol, they can perform the LAPD negotiation only when the LAPD actor is set to User at one end and is set to Network at the other end. Efficient LAPD Enable Configurable LAPD Enable Enabled Disabled Enabled This parameter indicates whether the current LAPD is enabled. This parameter specifies whether the LAPD is enabled.
B-32
Issue 03 (2011-04-10)
LAPD Parameters
Parameter Remote IP Address L2 Wait Time to Retry(s) Value Range 1 to 20 Default Value 1 Description This parameter indicates the IP address of the opposite end of the OSI tunnel. l This parameter specifies L2 Wait Time to Retry(s). l L2 Wait Time to Retry(s) indicates the interval for retransmitting packets at the LAPD link layer. l L2 Wait Time to Retry(s) needs to be set according to the network situation. If the network is in good situation, L2 Wait Time to Retry(s) can be set to a smaller value. Otherwise, it is recommended that you set L2 Wait Time to Retry(s) to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. L2 Retry Times 2 to 6 3 l This parameter specifies L2 Retry Times. l L2 Retry Times indicates the maximum number of packet retransmission attempts at the LAPD link layer. l L2 Retry Times needs to be set according to the network situation. If the network is in good situation, L2 Retry Times can be set to a smaller value. Otherwise, it is recommended that you set L2 Retry Times to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
Issue 03 (2011-04-10)
B-33
Parameter L3 Hello Timer(s)
Default Value 3
Description l This parameter specifies L3 Hello Timer(s). l L3 Hello Timer(s) indicates the Hello packet timer at the LAPD link network layer. It is used for periodical transmission of the Hello packets. l The Hello timer determines the interval for transmitting the Hello packets once. L3 Hello Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 Hello Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 Hello Timer(s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
L3 ES Timer(s)
1 to 200
50
l This parameter specifies L3 ES Timer (s). l L3 ES Timer(s) indicates the ES configuration timer at the LAPD link network layer. It is used for setting the time to transmit the configuration information on the ES route. l L3 ES Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 ES Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 Hello Timer(s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
B-34
Issue 03 (2011-04-10)
Parameter L3 IS Timer(s)
Default Value 10
Description l This parameter specifies L3 IS Timer (s). l L3 IS Timer(s) indicates the IS configuration timer at the LAPD link network layer. It is used for setting the time to transmit the configuration information through the L1/L2 router. l L3 IS Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 IS Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 IS Timer (s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
L3 Hold Timer(s)
2 to 63
l This parameter specifies L3 Hold Timer (s). l L3 Hold Timer(s) indicates the hold timer at the LAPD link network layer. l L3 Hold Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 Hold Timer(s) can be set to a smaller value. Otherwise, it is recommended that you set L3 IS Timer(s) to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
COST
1 to 63
20
l This parameter specifies COST. l COST indicates the overhead value of the virtual LAPD that corresponds to the OSI tunnel. l The overhead value determines whether this link is perverted. If the overhead value is smaller, this link has a higher priority to be selected. l This parameter needs to set according to the planning information.
Related Tasks
A.1.4.9 Configuring the OSI Tunnel
B.1.2.14 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband DCN.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Click the Bandwidth Management tab.
Parameters for Bandwidth Management

Parameter Ethernet Board VLAN ID Value Range 2 to 4094 Default Value 4094 Description l The equipment on the traditional DCN can be connected to the NMS through the SCC board, but the OptiX RTN 950 can also be connected to the NMS through an Ethernet interface. If an Ethernet port is used to carry the network management information, the NE differentiates the network management information and Ethernet service information according to the VLAN ID. l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the Ethernet Board VLAN ID of the inband DCN can be changed manually. The same VLAN ID must be, however, is used on the network-wide inband DCN. Bandwidth(Kbit/s) 64 to 1000 512 Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. IF Port Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the radio link.
E1 Port Bandwidth(Kbit/s) Tunnel Bandwidth (Kbit/s) IF Port Bandwidth (Kbit/s)
64 to 1000
512
Related Tasks
A.1.4.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN
B.1.2.15 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports of the inband DCN.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Click the Port Settings tab.
Parameters for Setting Ports

Parameter Port Name Enabled Status Value Range Enabled Disabled Default Value Enabled Description This parameter indicates the port name. l Enabled Status specifies the enabling status of the port. l The network management information can be transmitted over the inband DCN when the DCN function is enabled for the ports at both ends of a link.
Related Tasks
A.1.4.11 Configuring the Enable Status of the Inband DCN Function on Ports
B.1.2.16 Parameter Description: DCN Management_Protocol Setting

This topic describes the parameters that are used for setting a protocol of the inband DCN.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree, and then choose Communication > DCN Management from the Function Tree. Click the Protocol Settings tab.
Parameters for Setting a Protocol

Parameter Port Name Protocol Type Value Range IP HWECC Default Value IP Description Displays the port name. l If the values of Protocol Type are different from each other, the equipment at both ends cannot be interconnected with each other. Therefore, Protocol Type must be set to the same value for the equipment at both ends of a link. l Set Protocol Type according to the network planning information. Generally, it is recommended that you set this parameter to IP.
Issue 03 (2011-04-10)
B-37
Related Tasks
A.1.4.12 Configuring the Protocol Type of the Inband DCN
B.1.2.17 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l l In the NE Explorer, select the NE from the Object Tree and then choose Communication > DCN Management from the Function Tree. Click the Access Control tab.
Parameters
Parameter Port Name Enabled Status Value Range Disabled Enabled Default Value Disabled Description Displays the Ethernet ports that support this function. l Specifies the enabling status of the port. l If the Enabled Status is set to Enabled, this port can be used to support access of the management information from the NMS. l If the Enabled Status is set to Disabled, this port cannot be used to support access of the management information from the NMS. IP Address Subnet Mask 0.0.0.0 0.0.0.0 Specifies the IP address of the port. Specifies the submask of the port.
Related Tasks
A.1.4.16 Configuring Access Control
B.1.2.18 Parameter Description: Access Control

This topic describes the parameters that are used for access control of the NMS.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access Control from the Function Tree.
B-38
Issue 03 (2011-04-10)
Parameters for Ethernet Access Control

Parameter Enable Ethernet Access PORT Value Range Selected Deselected Default Value Description After The First Network Port is selected, the NE can access the NMS through the Ethernet port. This parameter displays the NMS port and the NE cascading port on the system control, switching, and timing board. This parameter specifies the working modes of the NMS port and the NE cascading port on the system control, switching, and timing board.
Work Mode
adapt 10M Half_Duplex 10M Full_Duplex 100M Half_Duplex 100M Full_Duplex
Actual Work Mode
This parameter displays the working modes of the NMS port and the NE cascading port on the system control, switching, and timing board.
Parameters for Access Control over Serial Ports

Parameter Enable Serial Port Access Access Command Line Access NM Value Range Selected Deselected Selected Deselected Selected Deselected Baud Rate 1200 2400 4800 9600 19200 38400 57600 115200 9600 Deselected Deselected Default Value Description After Enable Serial Port Access is selected, the NE can access the NMS or command lines through the serial port. If Access Command Line is selected, the serial interface can be used to access the command line terminal. If Access NM is selected, the serial interface can be used to access the NMS. l This parameter specifies the data transmission rate in the communications through serial ports. l This parameter is set according to the rate of the serial port at the opposite end, and the rates at both ends must be the same.
Issue 03 (2011-04-10)
B-39
B.1.3 Parameters for Network Security Management

This topic describes the parameters that are related to network security management. B.1.3.1 Parameter Description: NE User Management This topic describes the parameters that are related to NE user management. B.1.3.2 Parameter Description: NE User Management_Creation This topic describes the parameters that are used for creating an NE user. B.1.3.3 Parameter Description: LCT Access Control This topic describes the parameters that are used for LCT access control.
B.1.3.1 Parameter Description: NE User Management

This topic describes the parameters that are related to NE user management.
Navigation Path
Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree.
Parameters for NE user management

Parameter NE NE User User Level NE User Flag Value Range Default Value Description Displays the current NE name. Displays the registered NE user name. Displays the registered NE user level. Displays whether a registered NE user is logged in. Displays the user group to which a registered NE user belongs. Displays whether a registered NE user is allowed to log in to the NE. Displays whether a registered NE user is permanently valid.
User Group Belonged
Login Allowed
Permanently Valid or not
B-40
Issue 03 (2011-04-10)
Parameter Valid From
Value Range -
Default Value -
Description Displays the time when a registered NE user logged in to the NE for the first time. Displays the time when a registered NE user logged in to the NE for the last time. Displays whether a registered user password can be changed.
Valid Till
Whether the password is allowed to be modified immediately
Related Tasks
A.1.6.3 Setting Warning Screen Parameters
B.1.3.2 Parameter Description: NE User Management_Creation

This topic describes the parameters that are used for creating an NE user.
Navigation Path
1. 2. Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree. Click Create.

Parameter NE User Value Range Default Value Description Specifies the name of a registered NE user.
NOTE The name of an NE cannot contain any space or Chinese characters.
Issue 03 (2011-04-10)
B-41
Parameter User Level
Value Range Monitor Level Operation Level Maintenance Level System Level Debug Level
Default Value Monitor Level
Description l A Debug Level NE user has all security and configuration authorities, and has the right to run debugging commands. l A System Level NE user has all security and configuration authorities. l A Maintenance Level NE user has some security authorities, some configuration authorities, the communication setting authority, and the log management authority. l An Operation Level NE user has all fault performance authorities, some security authorities, and some configuration authorities. l A Monitor Level NE user has the right to use all query commands, to log in, to log out, and to change its own password.
New Password Confirm Password Whether the password is allowed to be modified immediately
Yes No
Yes
l Specifies the password for a new NE user. Enter the same value as New Password. Specifies whether the password of a registered NE user can be changed.
Related Tasks
A.1.6.1 Creating an NE User
B-42
Issue 03 (2011-04-10)
B.1.3.3 Parameter Description: LCT Access Control

This topic describes the parameters that are used for LCT access control.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Security > LCT Access Control from the Function Tree.
Parameters for LCT Access Control

Parameter NE LCT Access Control Switch Value Range Access Allowed Disable Access Default Value Access Allowed Description This parameter indicates the name of the NE. l No NMS user logs in to the NE. In this case, when the LCT requests an LCT user to log in to the NE, the NE does not check the status of LCT Access Control Switch, and directly allows the LCT user to log in to the NE. l An NMS user first logs in to the NE. In this case, when the LCT requests an LCT user to log in to the NE, the NE determines whether to allow the LCT user to log in to the NE through the LCT according to the status of LCT Access Control Switch. l An LCT user first logs in to the NE. In this case, when the NMS requests an NMS user to log in to the NE, the NMS user can directly log in to the NE. After the NMS user successfully logs in to the NE, the online LCT user is not affected. l When both the LCT user and NMS user log in to the NE, the online LCT user is not affected after LCT Access Control Switch is set to Disable Access.
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links. B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation This topic describes the parameters that are related to the XPIC function. B.2.2 Parameter Description: Link Configuration_XPIC This topic describes the parameters that are related to the XPIC function. B.2.3 Parameter Description: N+1 Protection_Create This topic describes the parameters that are used for creating an IF N+1 protection group.
B.2.4 Parameter Description: N+1 Protection This topic describes the parameters that are related to IF N+1 protection. B.2.5 Parameter: IF 1+1 Protection_Create This topic describes the parameters that are used for creating an IF 1+1 protection group. B.2.6 Parameter Description: IF 1+1 Protection This topic describes the parameters that are related to IF 1+1 protection. B.2.7 Parameter: Link Configuration_IF/ODU Configuration This topic describes the parameters that are used for configuring the IF/ODU.
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation

This topic describes the parameters that are related to the XPIC function.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the XPIC tab. Click New.
Parameters
Parameter IF Channel Bandwidth Value Range 28M 40M 56M Default Value Description l This parameter specifies the channel spacing when the XPIC function is enabled. l When this parameter is set to 56M or 40M, the high-power ODU must be used.
NOTE The IFX2 board does not support the value 40M.
Polarization Direction-V Polarization Direction-H
l This parameter indicates the polarization direction of a radio link. l It is recommended that you install the two XPIC IF boards that form an XPIC workgroup in the slots that are at the same layer or in the same column, and set the IF port on the XPIC IF board that has a smaller slot number to Link ID-V and the IF port on the other XPIC IF board to Link ID-H. l Set Link ID-V and Link ID-H. l A link ID is an identifier of a radio link and is used to prevent the radio links
Issue 03 (2011-04-10)
Link ID-V
1 to 4094
B-44
Parameter Link ID-H
Value Range
Default Value 2
Description between sites from being wrongly connected. l When the link ID received by an NE is different from the link ID set for the NE, the NE reports an MW_LIM alarm and inserts the AIS. l These two parameters are set according to the planning information. These two parameters must be set to different values, but Link ID-V must be set to the same value at both ends of a link and Link ID-H must also be set to the same value at both ends of a link.
Transmit Power (dBM)
l This parameter specifies the transmit power of an ODU. The value of this parameter must not exceed the rated power range supported by the ODU. l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter is set according to the planning information.
Maximum Transmit Power (dBM)
l This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed this value. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-45
Parameter Transmit Frequency(MHz)
Value Range -
Default Value -
Description l This parameter indicates the channel central frequency. l The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing. l This parameter is set according to the planning information.
T/R Spacing(MHz)
l This parameter specifies the spacing between the transmit frequency and the receive frequency of an ODU to prevent mutual interference between the transmitter and the receiver. l If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive frequency. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Transmission Status
unmute mute
unmute
l When this parameter is set to mute, the ODU does not transmit microwave signals but can normally receive microwave signals. l When this parameter is set to unmute, the ODU normally transmits and receives microwave signals. l In normal cases, Transmission Status is set to unmute.
B-46
Issue 03 (2011-04-10)
Parameter ATPC Status
Value Range Disabled Enabled
Description l This parameter specifies whether the ATPC function is enabled. l When this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes.
ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm)
-45.0 -70.0
l The central value between the ATPC upper threshold and the ATPC lower threshold is set as the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set the ATPC upper threshold only when ATPC Automatic Threshold Enable Status is set to Disabled.
Issue 03 (2011-04-10)
B-47
Parameter ATPC Automatic Threshold Enable Status
Description l This parameter specifies whether the automatic threshold function is enabled. l If this parameter is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link.
Related Tasks
A.2.2 Creating an XPIC Workgroup
B.2.2 Parameter Description: Link Configuration_XPIC

This topic describes the parameters that are related to the XPIC function.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the XPIC tab.

Parameter Group ID Polarization Direction-V Link ID-V Value Range Default Value Description This parameter indicates the ID of the work group. This parameter indicates the IF port to which the polarization direction V corresponds. This parameter indicates the link ID to which the polarization direction V corresponds. This parameter indicates the IF port to which the polarization direction H corresponds. This parameter indicates the link ID to which the polarization direction H corresponds.
Polarization Direction-H Link ID-H
B-48
Issue 03 (2011-04-10)
Parameter IF Channel Bandwidth
Value Range 28M 40M 56M
Default Value -
Description l IF Channel Bandwidth refers to the channel spacing of the corresponding radio links. l When this parameter is set to 56M or 40M, the high-power ODU must be used. l This parameter is set according to the planning information.
NOTE The IFX2 board does not support the value 40M.
Power to Be Received -V(dBm)
-90.0 to -20.0
-10.0
l This parameter is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-49
Parameter Power to Be Received -H(dBm)
Value Range -90.0 to -20.0
Default Value -10.0
Description l This parameter is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Maximum Transmit Power (dBm)
l This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed this value. l This parameter is set according to the planning information.
B-50
Issue 03 (2011-04-10)
Parameter Transmit Power (dBm)
Value Range -
Default Value -
Description l This parameter indicates or specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power range of the ODU. l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter is set according to the planning information.
Transmit Frequency(MHz)
l This parameter indicates or specifies the transmit frequency of the ODU, namely, the channel central frequency. l The value of this parameter must not be less than the sum of the lower TX frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. l This parameter needs to be set according to the planning information.
Issue 03 (2011-04-10)
B-51
Parameter T/R Spacing(MHz)
Value Range -
Default Value -
Description l This parameter indicates or specifies the spacing between the transmit frequency and receive frequency of the ODU to prevent mutual interference between the transmitter and receiver. l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, this parameter is set to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Transmission Status
unmute mute
unmute
l This parameter indicates or specifies the transmit status of the ODU. l If this parameter is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. l If this parameter is set to unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, this parameter is set to unmute.
Parameters for Hybrid/AM Configuration

Parameter Group ID Polarization direction Value Range Default Value Description This parameter indicates the ID of the work group. This parameter indicates the IF port to which the polarization direction H or the polarization direction V corresponds.
B-52
Issue 03 (2011-04-10)
Parameter AM Status
Description l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. Hence, the Hybrid radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled.
Modulation Mode of the Guarantee AM Capacity
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
This parameter specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme.
NOTE Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity.
This parameter is valid only when AM Status is set to Enabled. Modulation Mode of the Full AM Capacity QPSK 16QAM 32QAM 64QAM 128QAM 256QAM This parameter specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme.
This parameter is valid only when AM Status is set to Enabled.
Issue 03 (2011-04-10)
B-53
Parameter Manual Modulation Mode
Value Range QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
Default Value QPSK
Description This parameter specifies the modulation scheme that the radio link uses for signal transmission. This parameter is valid only when AM Status is set to Disabled.
Transmit-End Modulation Mode Receive-End Modulation Mode
Displays the modulation mode at the transmit end. Displays the modulation mode at the receive end.
Parameters for ATPC Management

Parameter Group ID ATPC Enable Status Value Range Disabled Enabled Default Value Description This parameter indicates the object to be set. l This parameter specifies whether the ATPC function is enabled. l If this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes. ATPC Upper Threshold(dBm) l Set the central value between the ATPC upper threshold and the ATPC lower
B-54
Issue 03 (2011-04-10)
Parameter ATPC Lower Threshold(dBm)
Value Range -
Default Value -
Description threshold to a value for the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) o the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set this parameter only when ATPC Automatic Threshold Enable Status is set to Disabled. l This parameter specifies whether the ATPC automatic threshold function is enabled. l If this parameter is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link. l If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm).
Disabled Enabled
Related Tasks
A.2.3 Setting the AM Attributes of the XPIC Workgroup
B.2.3 Parameter Description: N+1 Protection_Create

This topic describes the parameters that are used for creating an IF N+1 protection group.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. Click Create.
Issue 03 (2011-04-10)
B-55

Parameter WTR time(s) Value Range 300 to 720 Default Value 600 Description l This parameter specifies the wait-torestore (WTR) time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l It is recommended that you use the default value. SD enable Enabled Disabled Enabled l This parameter specifies whether the signal degradation switching function of N+1 protection is enabled. l When this parameter is set to Enabled, the signal degradation condition is considered as a trigger condition of protection switching. l It is recommended that you set this parameter to Enabled.
Slot Mapping Relation Parameters

Parameter Select Mapping Direction Value Range Working Unit Protection Unit Default Value Working Unit Description l This parameter specifies the mapping direction of N+1 protection. l This parameter is set according to the planning information. Available Boards l In the case of N+1 protection, map N IF ports as Working Unit and map the remaining IF port as Protection Unit. l This parameter is set according to the planning information. Mapped Boards This parameter indicates the working unit and protection unit that have been set.
Related Tasks
B.2.4 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab.
Protection Group Parameters

Parameter Protection Group ID WTR Time(s) Value Range 300 to 720 Default Value Description This parameter indicates the ID of the protection group. l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l It is recommended that you use the default value. SD Enable Enabled Disabled l This parameter indicates or specifies whether the SD switching function of N +1 protection is enabled. l When this parameter is set to Enabled, the SD condition is considered as a trigger condition of protection switching. l It is recommended that you set this parameter to Enabled. Protocol Status This parameter indicates the status of the switching control protocol.
Protection Unit Parameters

Parameter Protection Unit Line Value Range Default Value Description This parameter indicates the protection unit. This parameter indicates the information about the working board or protection board. This parameter indicates the switching state. This parameter indicates the protected unit. This parameter indicates the local end or remote end.
Switching Status Protected Unit Remote/Local End Indication
Issue 03 (2011-04-10)
B-57
Related Tasks
A.2.7 Querying the IF N+1 Protection Status
B.2.5 Parameter: IF 1+1 Protection_Create

This topic describes the parameters that are used for creating an IF 1+1 protection group.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab. Click New.
Parameters
Parameter Working Mode Value Range HSB FD SD Default Value HSB Description l This parameter specifies the working mode of the IF 1+1 protection. l When Working Mode is set to HSB, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to realize the protection. l When Working Mode is set to FD, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With FD protection, the impact of the fading on signal transmission is reduced. l When Working Mode is set to SD, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With SD protection, the impact of the fading on signal transmission is reduced. l The FD mode and SD mode are compatible with the HSB switching function. l This parameter is set according to the planning information.
B-58
Issue 03 (2011-04-10)
Parameter Revertive Mode
Value Range Revertive Non-Revertive
Default Value Revertive
Description l This parameter specifies the revertive mode of the IF 1+1 protection. l When Revertive Mode is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. It is recommended that you set this parameter to Revertive. l When Revertive Mode is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal.
WTR Time(s)
300 to 720
600
l This parameter specifies the wait-torestore (WTR) time. l When the time after the former working channel is restored to normal reaches the set WTR Time(s), a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value.
Issue 03 (2011-04-10)
B-59
Parameter Enable Reverse Switching
Description l This parameter indicates whether the reverse switching function is enabled. l When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When Enable Reverse Switching at the source end is set to Enabled and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD. l Generally, if Working Mode is set to HSB, it is recommended that you set Enable Reverse Switching to Disabled; if Working Mode is set to SD, it is recommended that you set Enable Reverse Switching to Enabled.
Working Board Protection Board
This parameter specifies the working board of the protection group. This parameter specifies the protection board of the protection group.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Related Tasks
A.2.1 Creating an IF 1+1 Protection Group
B.2.6 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the IF 1+1 Protection tab.
B-60
Issue 03 (2011-04-10)

Parameter Protection Group ID Working Mode Value Range HSB FD SD Default Value Description This parameter indicates the ID of the protection group. l This parameter indicates the working mode of the created IF 1+1 protection group. l In HSB mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to realize the protection. l In FD mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With FD protection, the impact of the fading on signal transmission is reduced. l In SD mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With SD protection, the impact of the fading on signal transmission is reduced. l The FD mode and SD mode are compatible with the HSB switching function. l This parameter is set according to the planning information. Revertive Mode Revertive Non-Revertive l This parameter indicates or specifies the revertive mode of the protection group. l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l It is recommended that you set this parameter to Revertive.
Issue 03 (2011-04-10)
B-61
Parameter WTR Time(s)
Default Value -
Description l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Enable Reverse Switching
Enable Disable
l This parameter indicates or specifies whether the reverse switching function is enabled. l When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. l This parameter is valid only when Working Mode is set to HSB or SD.
Switching Status of Device
l This parameter indicates the switching state on the equipment side. l Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query.
Switching Status of Channel
l This parameter indicates the switching state on the channel side. l Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query.
Active Board of Device Active Board of Channel
This parameter indicates the current working board on the equipment side. This parameter indicates the current working board on the channel side.
NOTE
Each of the parameters Working Mode, Revertive Mode, and WTR Time(s) must be set to the same value at both ends of a radio hop.
B-62
Issue 03 (2011-04-10)

Parameter Unit Slot Mapping Settings Working Status of Device Signal Status of Channel Value Range Default Value Description This parameter indicates the working board and protection board. This parameter indicates the names and ports of the working board and protection board. This parameter indicates the working state on the equipment side. This parameter indicates the status of the link signal.
Related Tasks
A.2.6 Querying the IF 1+1 Protection Status
B.2.7 Parameter: Link Configuration_IF/ODU Configuration

This topic describes the parameters that are used for configuring the IF/ODU.
Navigation Path
1. 2. In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab.
Issue 03 (2011-04-10)
B-63
Parameters for Configuring the IF

Parameter Working Mode Value Range 1,4E1,7MHz,QPSK 2,4E1,3.5MHz, 16QAM 3,8E1,14MHz,QPS K 4,8E1,7MHz, 16QAM 5,16E1,28MHz,QP SK 6,16E1,14MHz, 16QAM 7,STM-1,28MHz, 128QAM 8,E3,28MHz,QPSK 9,E3,14MHz, 16QAM 10,22E1,14MHz, 32QAM 11,26E1,14MHz, 64QAM 12,32E1,14MHz, 128QAM 13,35E1,28MHz, 16QAM 14,44E1,28MHz, 32QAM 15,53E1,28MHz, 64QAM Default Value Description l This parameter indicates or specifies the work mode of the radio link in "work mode number, service capacity, channel spacing, modulation mode" format. l This parameter is set according to the planning information. The work modes of the IF boards at the two ends of a radio link must be the same.
NOTE The IF1 board supports this parameter.
B-64
Issue 03 (2011-04-10)
Parameter Link ID
Default Value 1
Description l Link ID indicates or specifies the ID of a radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l If the value of Received Radio Link ID does not match the preset value of Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports MW_LIM alarm to the NMS, indicating that the link IDs do not match. l Link ID is set according to the planning information. Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same.
Received Link ID
l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match. l When the radio link becomes faulty, this parameter is displayed as an invalid value.
IF Service Type
Hybrid(Native E1 +ETH) Hybrid(Native STM-1+ETH) SDH
Hybrid(Native E1 +ETH)
l Displays or specifies the type of services carried by the IF board. l If the Integrated IP radio transmits Native E1 services, set this parameter to Hybrid(Native E1+ETH). l If the Integrated IP radio transmits Native STM-1 services, set this parameter to Hybrid(Native STM-1 +ETH). l If the SDH radio transmits SDH services, set this parameter to SDH.
NOTE The ISU2 and ISX2 boards support this parameter.
Issue 03 (2011-04-10)
B-65
Parameter IF Channel Bandwidth
Value Range 7M 14M 28M 40M 56M
Default Value -
Description IF Channel Bandwidth indicates the channel spacing of the corresponding radio link. This parameter is set according to the planning information.
NOTE l This parameter is not applicable to the IF1 board. l The IFU2 board does not support the value 40M. l The IFX2 board does not support the values 7M, 14M, and 40M. l The ISX2 board supports the channel spacings of 7M and 14M only when the XPIC function is disabled.
AM Mode AM Status
Disabled Enabled
Disabled
This parameter is not applicable to the OptiX RTN 950. l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manual Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Hence, the Integrated IP radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled. l The ISX2/ISU2 does not support the AM function when IF Service Type is SDH.
NOTE This parameter is not applicable to the IF1 board.
Manual Modulation Mode
QPSK
l This parameter specifies the modulation scheme that the radio link uses for signal transmission. l This parameter is valid only when AM Status is set to Disabled.
B-66
Issue 03 (2011-04-10)
Parameter Modulation Mode of the Guarantee AM Capacity
Default Value QPSK
Description l This parameter is valid only when AM Status is set to Enabled. l Modulation Mode of the Guarantee AM Capacity specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation scheme.
Modulation Mode of the Full AM Capacity
QPSK
l This parameter is valid only when AM Status is set to Enabled. l Modulation Mode of the Full AM Capacity specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme.
NOTE Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity. NOTE This parameter is not applicable to the IF1 board.
STM-1 Capacity
l Specifies the STM-1 capacity of the IF board. l This parameter is available only when IF Service Type is set to Hybrid(Native STM-1+ETH) and SDH. l If IF Service Type is Hybrid(Native STM-1+ETH), this parameter can be set to 0 or 1. l If IF Service Type is SDH, this parameter can be set to 1 or 2.
NOTE The IF1, IFU2, and IFX2 boards do not support this parameter.
Issue 03 (2011-04-10)
B-67
Parameter Guarantee E1 Capacity
Value Range -
Default Value -
Description l If AM Status is set to Enabled, this parameter needs to be set according to IF Channel Bandwidth, Modulation Mode of the Guarantee AM Capacity, and the actually transmitted services. l If AM Status is set to Disabled, this parameter needs to be set according to IF Channel Bandwidth, Manually Specified Modulation Mode, and the actually transmitted services. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity Range Data Service Bandwidth(Mbit/ s) Enable E1 Priority
Displays the E1 capacity range of the IF board in guarantee capacity modulation mode. Displays the data service bandwidth of the IF board. l This parameter specifies whether to enable the E1 priority function. l This parameter is valid only when AM Status is set to Enabled. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Disabled Enabled
Disabled
B-68
Issue 03 (2011-04-10)
Parameter Full E1 Capacity
Value Range -
Default Value -
Description l This parameter specifies the number of transmitted E1 services in Modulation Mode of the Full AM Capacity. l This parameter is valid if Enable E1 Priority is set to Enabled. l E1 service bandwidth in full capacity mode Service bandwidth in full capacity mode - Service bandwidth in guarantee capacity mode + E1 service bandwidth in guarantee capacity mode. In addition, the number of E1 services in full capacity modulation mode should be smaller than or equal to the maximum number of E1 services in full capacity modulation mode. l The Full E1 Capacity must be set to the same value at both ends of a radio link. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Full E1 Capacity Range
Displays the E1 capacity range of the IF board in full capacity modulation mode.
Parameters for Configuring the RF

Parameter TX Frequency (MHz) Value Range Default Value Description l This parameter indicates or specifies the transmit frequency of the ODU, namely, the channel central frequency. l The value of this parameter must not be less than the sum of the lower TX frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. l This parameter needs to be set according to the planning information.
Issue 03 (2011-04-10)
B-69
Parameter Range of TX Frequency(MHz)
Value Range -
Default Value -
Description l This parameter indicates the range of the transmit frequency of the ODU. l The Range of Frequency(MHz) depends on the specifications of the ODU.
Actual TX Frequency(MHz) Actual RX Frequency(MHz) T/R Spacing(MHz)
This parameter indicates the actual transmit frequency of the ODU. This parameter indicates the actual receive frequency of the ODU. l This parameter specifies the spacing between the transmit frequency and the receive frequency of an ODU to prevent interference between them. l If Station Type of the ODU is TX high, the TX frequency is one T/R spacing higher than the receive frequency. If Station Type of the ODU is TX low, the TX frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Actual T/R Spacing(MHz)
This parameter indicates the actual T/R spacing of the ODU.
B-70
Issue 03 (2011-04-10)
Parameters for Configuring the Power

Parameter TX Power(dBm) Value Range Default Value Description l This parameter indicates or specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power range of the ODU. l This parameter cannot take a value greater than the preset value of Maximum Transmit Power(dBm). l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter needs to be set according to the planning information. TX Power Range (dBm) Actual TX Power (dBm) This parameter indicates the range of the transmit power of the ODU. l This parameter indicates the actual transmit power of the ODU. l If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
Issue 03 (2011-04-10)
B-71
Parameter Power to Be Received(dBm)
Default Value -10.0
Description l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When Power to Be Received(dBm) takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Actual RX Power (dBm) TX Status
Unmute Mute
Unmute
This parameter indicates the actual receive power of the ODU. l This parameter indicates or specifies the transmit status of the ODU. l When this parameter is set to Mute, the transmitter of the ODU does not work but can normally receive microwave signals. l When this parameter is set to Unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, it is recommended that you set TX Status to unmute.
Actual TX Status
This parameter indicates the actual transmit status of the ODU.
B-72
Issue 03 (2011-04-10)
Equipment Information
Parameter Frequency(GHz) Equipment Type Value Range Default Value Description This parameter indicates the frequency band where the ODU operates. l This parameter indicates the equipment type of the ODU. l PDH and SDH indicate the transmission capacity only and are irrelevant to the type of transmitted service. Station Type l This parameter indicates whether the ODU is a Tx high station or a Tx low station. l The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station. Produce SN This parameter indicates the manufacturing serial number and the manufacturer code of the ODU. This parameter indicates the level of the output power of the ODU.
Transmission Power Type
Related Tasks
B.3 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP). B.3.1 Parameter Description: Linear MSP_Creation This topic describes the parameters that are used for creating linear MSP groups. B.3.2 Parameter Description: Linear MSP This topic describes the parameters that are related to linear MSP groups.
B.3.1 Parameter Description: Linear MSP_Creation

This topic describes the parameters that are used for creating linear MSP groups.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Click Create.
Issue 03 (2011-04-10)
B-73

Parameter Protection Type Value Range 1+1 Protection 1:N Protection Default Value 1+1 Protection Description l This parameter specifies the protection type of the linear MSP group. l In the case of 1+1 linear MSP, one working channel and one protection channel are required. When the working channel fails, the service is switched from the working channel to the protection channel. l In the case of 1:N linear MSP, N working channels and one protection channel are required. Normal services are transmitted on the working channels and extra services are transmitted on the protection channel. When one working channel fails, the services are switched from this working channel to the protection channel, and the extra services are interrupted. l If extra services need to be transmitted or several working channels are required, select 1:N Protection. l This parameter is set according to the planning information.
B-74
Issue 03 (2011-04-10)
Parameter Switching Mode
Value Range Single-Ended Switching Dual-Ended Switching
Default Value Single-Ended Switching (1 +1 Protection) Dual-Ended Switching (1:N Protection)
Description l This parameter specifies the switching mode of the linear MSP. l In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. l In dual-ended mode, the switching occurs at both ends at the same time. l If the linear MSP type is set to 1:N Protection, Switching Mode can be set to DualEnded Switching only.
Revertive Mode
Non-Revertive Revertive
Non-Revertive (1+1 Protection) Revertive (1:N Protection)
l This parameter specifies the revertive mode of the linear MSP. l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When this parameter is set to Non-Revertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l It is recommended that you set this parameter to Revertive. l If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only.
Issue 03 (2011-04-10)
B-75
Default Value 600
Description l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
SD Switching
Enabled Disabled
Enabled
l This parameter indicates or specifies whether the switching at the SD alarm of the linear MSP is enabled. l When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that you set this parameter to Enabled.
Protocol Type
New Protocol Restructure Protocol
New Protocol
l The new protocol is supported at the early stage, and the mainstream protocol version is used currently. l The restructure protocol optimizes the new protocol and provides better measures to protect the new protocol, thus ensuring that the new protocol runs in a better manner. l The new protocol is more mature, and the restructure protocol complies with the standard. It is recommended that you use the new protocol. l You must ensure that the interconnected NEs run the protocols of the same type.
B-76
Issue 03 (2011-04-10)

Parameter Select Mapping Direction Value Range West Working Unit West Protection Unit Default Value West Working Unit Description This parameter specifies the mapping direction of the linear MSP.
Available Boards
l This parameter specifies the mapping board and port in the mapping direction. l If the protection type is set to 1+1 Protection, only one line port can be mapped as West Working Unit. l Only one line port can be mapped as West Protection Unit. l The line port mapped as West Protection Unit and the line port mapped as West Working Unit should be configured for different boards if possible.
Mapped Boards
This parameter indicates the preset slot mapping relations, including the mapping direction and the corresponding mapping mode.
Related Tasks
A.3.1 Configuring Linear MSP
B.3.2 Parameter Description: Linear MSP

This topic describes the parameters that are related to linear MSP groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree.

Parameter Protection Group ID Value Range Default Value Description This parameter indicates the ID of the protection group.
Issue 03 (2011-04-10)
B-77
Value Range -
Default Value -
Description l This parameter indicates the protection type of the linear MSP group. l In the case of 1+1 linear MSP, one working channel and one protection channel are required. When the working channel fails, the service is switched from the working channel to the protection channel. l In the case of 1:N linear MSP, N working channels and one protection channel are required. Normal services are transmitted on the working channels and extra services are transmitted on the protection channel. When one working channel fails, the services are switched from this working channel to the protection channel, and the extra services are interrupted. l If extra services need to be transmitted or several working channels are required, select 1:N Protection.
Switching Mode
Single-Ended Switching Dual-Ended Switching
l This parameter indicates or specifies the switching mode of the linear MSP. l In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. l In dual-ended mode, the switching occurs at both ends at the same time. l If the linear MSP type is set to 1:N Protection, Switching Mode can be set to Dual-Ended Switching only.
B-78
Issue 03 (2011-04-10)
Value Range Non-Revertive Revertive
Default Value -
Description l This parameter indicates or specifies the revertive mode of the linear MSP. l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l It is recommended that you set this parameter to Revertive. l If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only.
WTR Time(s)
300 to 720
l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
SD Switching
Enabled Disabled
l This parameter indicates or specifies whether the reverse switching function is enabled. l When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that you set this parameter to Enabled.
Issue 03 (2011-04-10)
B-79
Parameter Protocol Type
Value Range New Protocol Restructure Protocol
Default Value -
Description l The new protocol is supported at the early stage, and the mainstream protocol version is used currently. l The restructure protocol optimizes the new protocol and provides better measures to protect the new protocol, thus ensuring that the new protocol runs in a better manner. l You must ensure that the interconnected NEs run the protocols of the same type. l The new protocol is more mature, and the restructure protocol complies with the standard. It is recommended that you use the new protocol.
Protocol Status SD/SF PRI Switching Tag
High priority Low priority
High priority
This parameter indicates the protocol status of the linear MSP. l This parameter displays or specifies whether an SD/SF condition is a highpriority or low-priority switching condition. l When SD/SF PRI Switching Tag is set to High priority, bits 1 to 4 of the K1 byte uses 1101 to indicate a high-priority SF switching request and 1011 to indicates a high-priority SD switching request. l When SD/SF PRI Switching Tag is set to Low priority, bits 1 to 4 of the K1 byte uses 1100 to indicate a low-priority SF switching request and 1010 to indicates a low-priority SD switching request. l It is recommended that this parameter take its default value.

Parameter Protection Unit Value Range Default Value Description This parameter indicates that which of the units, namely, the west protection unit or the west working unit, is currently in the protection status.
B-80
Issue 03 (2011-04-10)
Parameter West Line
Value Range -
Default Value -
Description This parameter indicates the west protection unit and the west working unit of the linear MSP. This parameter indicates the switching status of the line. When Switching Mode is set to DualEnded Switching, the central office end that issues the switching command is displayed.
West Switching Status Remote/Local End Indication
Related Tasks
A.3.2 Querying the Status of the Linear MSP
B.4 SDH/PDH Service Parameters

This topic describes the parameters that are related to SDH/PDH services. B.4.1 Parameter Description: SDH Service Configuration_Creation This parameter describes the parameters that are used for creating point-to-point crossconnections. B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation This topic describes the parameters that are used for creating SNCP services. B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services This topic describes the parameters that are used for converting normal services into SNCP services. B.4.4 Parameter Description: SDH Service Configuration This topic describes the parameters that are used for configuring SDH services (namely, configuring cross-connections). B.4.5 Parameter Description: SNCP Service Control This topic describes the parameters that are used for controlling SNCP services. B.4.6 Parameter Description: TU_AIS Insertion This section describes the parameters for TU_AIS insertion.
B.4.1 Parameter Description: SDH Service Configuration_Creation

This parameter describes the parameters that are used for creating point-to-point crossconnections.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree.
Issue 03 (2011-04-10)
2. 3.
Click Scheme to change the VC-12 timeslot numbering policy used by the crossconnection. Click New.
Parameters
Parameter Level Value Range VC12 VC3 VC4 Default Value VC12 Description l This parameter specifies the level of the service to be created. l If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. l If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. l If all the services on a VC-4 channel pass through the NE, set this parameter to VC4. Direction Bidirectional Unidirectional Bidirectional l When this parameter is set to Unidirectional, create only the crossconnections from the service source to the service sink. l When this parameter is set to Bidirectional, create the crossconnections from the service source to the service sink and the crossconnections from the service sink to the service source. l In normal cases, it is recommended that you set this parameter to Bidirectional. Source Source Port Source VC4 This parameter specifies the slot of the service source. This parameter specifies the port of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
B-82
Issue 03 (2011-04-10)
Parameter Source Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter indicates the timeslot range of the service source. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Sink Sink Port Sink VC4
This parameter specifies the slot of the service sink. This parameter specifies the port of the service sink. l This parameter specifies the number of the VC-4 channel where the service sink is located. l This parameter cannot be set when Sink Slot is set to the slot of the tributary board.
l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-83
Parameter E1 Priority
Value Range High Low None
Default Value -
Description l This parameter specifies the priority of an E1 service. This parameter is available only if the E1 priority function is enabled for the ports configured in the cross-connections. l If E1 Priority is set to High, transmission of the E1 service is ensured in any modulation scheme. l If E1 Priority is set to Low, transmission of the E1 service is ensured only in fullcapacity modulation scheme l If the service priority is not specified during service creation, E1 Priority is None. In this case, the E1 priority of a service needs to be changed after the service is created.
Related Tasks
A.4.1 Creating the Cross-Connections of Point-to-Point Services
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation

This topic describes the parameters that are used for creating SNCP services.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. Click Scheme to change the VC-12 timeslot numbering policy used by the crossconnection. Click Create SNCP.

Parameter Service Type Value Range SNCP Default Value SNCP Description This parameter indicates that the type of the service to be created is SNCP.
B-84
Issue 03 (2011-04-10)
Parameter Direction
Value Range Bidirectional Unidirectional
Default Value Bidirectional
Description l When this parameter is set to Unidirectional, create only the crossconnections from the SNCP service source to the SNCP service sink. l When this parameter is set to Bidirectional, create the crossconnections from the SNCP service source to the service sink and the crossconnections from the SNCP service sink to the service source. l In normal cases, it is recommended that you set this parameter to Bidirectional.
Level
VC12 VC3 VC4
VC12
l This parameter specifies the level of the SCNP service to be created. l If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. l If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. l If all the services on a VC-4 channel pass through the NE, set this parameter to VC4.
Issue 03 (2011-04-10)
B-85
Parameter Hold-off Time (100ms)
Default Value 0
Description l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Revertive Mode
Revertive
l This parameter specifies whether to switch the service to the original working channel after the fault is rectified. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
B-86
Issue 03 (2011-04-10)
Default Value 600
Description l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Source Source Port Source VC4
This parameter specifies the slot of the service source. This parameter specifies the port of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
Source Timeslot Range(e.g.1,3-6)
l This parameter indicates the timeslot range of the service source. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-87
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Related Tasks
A.4.2 Creating Cross-Connections of SNCP Services
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP services.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree. If a bidirectional SDH service is created, select this service in Cross-Connection. Rightclick the selected service and choose Expand from the shortcut menu. Select the unidirectional service. Right-click the selected service and choose Convert to SNCP from the shortcut menu.

Parameter Service Type Direction Value Range SNCP Unidirectional Default Value SNCP Description This parameter indicates that the type of the service to be created is SNCP. This parameter indicates the direction of the SNCP service.
B-88
Issue 03 (2011-04-10)
Parameter Level
Value Range -
Default Value -
Description l This parameter indicates the level of the SNCP service. l If the service is an E1 service or a data service that is bound with VC-12 channels, the parameter value is VC12. l If the service is a data service that is bound with VC-3 channels, the parameter value is VC3. l If all the services on a VC-4 channel pass through the NE, the parameter value is VC4.
Hold-off Time (100ms)
0 to 100
l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Issue 03 (2011-04-10)
B-89
Value Range Non-Revertive Revertive
Default Value Revertive
Description l This parameter specifies whether to switch the service to the original working channel after the fault is rectified. If this parameter is set to "Revertive", the service is switched from the protection channel to the original working channel. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Source Source Port Source VC4
This parameter specifies the slot of the service source. This parameter specifies the port of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
B-90
Issue 03 (2011-04-10)
Parameter Source Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter indicates the timeslot range of the service source. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Related Tasks
B.4.4 Parameter Description: SDH Service Configuration

This topic describes the parameters that are used for configuring SDH services (namely, configuring cross-connections).
Issue 03 (2011-04-10)
B-91
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree.
Cross-Connection Parameters
Parameter Level Value Range VC12 VC3 VC4 Default Value Description l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed. Source Slot Source Timeslot/ Path Sink Slot Sink Timeslot/ Path E1 Priority High Low None This parameter indicates the slot of the service source. This parameter indicates the timeslot or timeslot range of the service source. This parameter indicates the slot of the source sink. This parameter indicates the timeslot or timeslot range of the service sink. l This parameter specifies the priority of an E1 service. This parameter is available only if the E1 priority function is enabled for the ports configured in the cross-connections. l If E1 Priority is set to High, transmission of the E1 service is ensured in any modulation scheme. l If E1 Priority is set to Low, transmission of the E1 service is ensured only in fullcapacity modulation scheme l If the service priority is not specified during service creation, E1 Priority is None. In this case, the E1 priority of a service needs to be changed after the service is created.
B-92
Issue 03 (2011-04-10)
Parameters for Automatically Created Cross-Connections

Parameter Level Value Range VC12 VC3 VC4 Default Value Description l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed. Source Slot Source Timeslot/ Path Sink Slot Sink Timeslot/ Path This parameter indicates the slot of the service source. This parameter indicates the timeslot or timeslot range of the service source. This parameter indicates the slot of the source sink. This parameter indicates the timeslot or timeslot range of the service sink.
Related Tasks
A.4.9 Querying TDM Services

This topic describes the parameters that are used for controlling SNCP services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree.

Parameter Protection Group ID Service Type Value Range Default Value Description Displays the ID of the protection group. This parameter indicates the service protection type of the protection group.
Issue 03 (2011-04-10)
B-93
Parameter Source
Value Range -
Default Value -
Description This parameter indicates the timeslots where the working service source and protection service source of the protection group are located. This parameter indicates the timeslots where the working service sink and protection service sink of the protection group are located. l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed.
Sink
Level
VC12 VC3 VC4
Current Status
This parameter indicates the current switching mode and switching status of the services of the protection group. l This parameter indicates or specifies the revertive mode of the service. l This parameter determines whether to switch the service from the protection channel to the original working channel after the fault is rectified. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
Revertive Mode
Revertive Non-Revertive
B-94
Issue 03 (2011-04-10)
Default Value -
Description l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Hold-off Time (100ms)
0 to 100
l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Issue 03 (2011-04-10)
B-95
Parameter Initiation Condition
Value Range -
Default Value None
Description l This parameter indicates or specifies the conditions that trigger the protection switching of the service. l After being selected as Initiation Condition, an alarm becomes a condition for triggering switching of an SNCP service. l It is recommended that you set Initiation Condition to the same condition for Working Service and Protection Service. l The protection switching conditions in Initiation Condition are optional values not included in the default values, and they are set according to the planning information.
Current Channel
This parameter indicates whether the working service or protection service is currently received by the protection group. This parameter displays the current switching request type.
Switching Request
Related Tasks
A.4.5 Configuring the Automatic Switching of SNCP Services A.4.11 Querying the Protection Status of SNCP Services
B.4.6 Parameter Description: TU_AIS Insertion

This section describes the parameters for TU_AIS insertion.
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered Alarm Insertion from the Function Tree.

Table B-1 Parameters on the main interface Parameter Port Value Range Default Value Description Displays the slot ID of the IF board and the ID of the IF port.
B-96
Issue 03 (2011-04-10)
Parameter High Channel Low Channel Insert E1_AIS to TU_AIS
Value Range Enable Disable
Default Value Disable
Description Displays the higher order path number of the IF board. Displays the lower order path number of the IF board. If this parameter is set to Enable for an E1 path and the E1 path detects the E1_AIS alarm, the TU_AIS alarm is inserted into this path.
Related Tasks
A.4.4 Inserting E1_AIS upon a TU_AIS Condition A.4.4 Inserting E1_AIS upon a TU_AIS Condition
B.5 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces. B.5.1 PDH Port Parameters This topic describes the parameters that are related to PDH ports supported by Smart E1 interface boards. B.5.2 Parameters for the Ports on Ethernet Boards This section describes the parameters for the Ethernet ports on the packet plane. B.5.3 Serial Port Parameters This topic describes the parameters that are related to serial ports. B.5.4 Microwave Interface Parameters This topic describes the parameters that are related to IF_ETH interfaces. B.5.5 IF Board Parameters This topic describes parameters that are related to IF boards. B.5.6 ODU Parameters This topic describes parameters that are related to ODUs. B.5.7 Parameters for SDH Interface Boards This topic describes parameters that are related to SDH interface boards. B.5.8 Parameters for PDH Interface Boards This topic describes parameters that are related to PDH interface boards. B.5.9 Parameters for Overhead This topic describes the parameters that are related to overhead.
B.5.1 PDH Port Parameters

This topic describes the parameters that are related to PDH ports supported by Smart E1 interface boards.
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes This topic describes the parameters that are related to the basic attributes of PDH ports. B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes This topic describes the parameters that are related to the advanced attributes of PDH ports.
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes

This topic describes the parameters that are related to the basic attributes of PDH ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click the General Attributes tab.

Parameter Port Name Port Mode Value Range Layer 1 Layer 2 Default Value Layer 2 Description Displays the ID of a service port. Specifies or displays the customized port name. l Specifies the working mode of a PDH port. l When this parameter is set to Layer 1, the port can transmit TDM signals. A port can transmit CES and serial services only if this parameter is set to Layer 1. l When this parameter is set to Layer 2, the port can transmit ATM signals.
B-98
Issue 03 (2011-04-10)
Parameter Encapsulation Type
Value Range -
Default Value -
Description l Displays Encapsulation Type of a PDH port. l When Port Mode is Layer 1, Encapsulation Type takes its default value Null. l When Port Mode is Layer 2, Encapsulation Type takes its default value ATM.
Related Tasks
A.5.4.1 Setting Basic Attributes of Smart E1 Ports
B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of PDH ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click the Advanced Attributes tab.

Parameter Port Value Range Default Value Description Displays the name of a service port.
Issue 03 (2011-04-10)
B-99
Parameter Frame Format
Value Range Unframe Double Frame CRC-4 Multiframe
Default Value CRC-4 Multiframe
Description l Specifies the frame format. l If a CES service uses the emulation mode of CESoPSN, this parameter can assume the value CRC-4 Multiframe or Double Frame. The value CRC-4 Multiframe is recommended. l If a CES service uses the emulation mode of SAToP, this parameter needs to assume the value Unframe. l The value of Frame Format must be the same at the local and opposite ends.
Line Encoding Format
Displays the line encoding format. The parameter value is always HDB3.
B-100
Issue 03 (2011-04-10)
Parameter Loopback Mode
Value Range Non-Loopback Inloop Outloop
Default Value Non-Loopback
Description l Specifies the loopback status for a port. l Non-Loopback indicates that loopbacks are cancelled or not performed. l Inloop indicates that the signals that need to be transmitted to the opposite end are looped back. l Outloop indicates that the received signals are looped back. l This function is used for fault locating for the PDH ports. This function affects services over related ports. Therefore, exercise precaution before starting this function. l Generally, this parameter is set to Non-Loopback.
Impedance
Displays the port impedance.
Issue 03 (2011-04-10)
B-101
Parameter Frame Mode
Value Range 30(ATM) 31(ATM,CES)
Default Value -
Description l 30 timeslots: In an E1 frame format, timeslots 1 to 15 and 17 to 31 are used to transmit service data, and timeslot 16 is used to transmit signaling. l 31 timeslots: In an E1 frame format, timeslots 1 to 31 are used to transmit service data. l This parameter is unavailable if Frame Format is Unframe. l The port frame modes need to be the same at the local and opposite ends.
Retiming Mode
Master Mode Slave Mode System Clock Mode
Master Mode
l Master Mode: The system clock is used as the output clock of services. l Slave Mode: The CES ACR clock is used as the output clock of services. The port inputting E1 clocks on Slave is set to Slave Mode. l System Clock Mode: The upstream E1 line clock of the opposite equipment is used as the output clock of services. The port inputting E1 clocks on Master is set to System Clock Mode
Composite Port Loopback Service Load Indication
For the OptiX RTN 950, this parameter cannot be configured. For the OptiX RTN 950, this parameter cannot be configured.
B-102
Issue 03 (2011-04-10)
Parameter Equalize Input Signal
Value Range -
Default Value -
Description For the OptiX RTN 950, this parameter cannot be configured. For the OptiX RTN 950, this parameter cannot be configured.
Equalize Outpput Signal
Related Tasks
A.5.4.2 Setting Advanced Attributes of Smart E1 Ports
B.5.2 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the packet plane. B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of an Ethernet interface. B.5.2.2 Parameter Description: Ethernet Interface_Flow Control This topic describes the parameters that are related to flow control. B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes. B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes This topic describes the parameters that are related to the Layer 3 attributes of Ethernet ports. B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes.
B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the General Attributes tab.

Parameter Port Name Value Range Default Value Description Displays the port name. Specifies the port name.
Issue 03 (2011-04-10)
B-103
Parameter Enable Port
Description l Specifies whether an Ethernet port is enabled. An Ethernet port can receive, process, and forward Ethernet services only if this parameter is set to Enabled. l Set this parameter according to the planning information.
NOTE Port 10 of the EFP8 board does not support this parameter.
Port Mode
Layer 2 Layer 3
Layer 2
l Port Mode specifies the mode of the Ethernet port. l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry MPLS tunnels.
NOTE Port 10 of the EFP8 board does not support the value Layer 3.
B-104
Issue 03 (2011-04-10)
Value Range Null 802.1Q QinQ
Default Value -
Description l Encapsulation Type specifies the method of the port to process the received packets. l If you set Encapsulation Type to Null, the port transparently transmits the received packets. l If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set Encapsulation Type to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
Issue 03 (2011-04-10)
B-105
Parameter Working Mode
Value Range Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex 1000M Full-Duplex
Default Value Auto-Negotiation
Description l The Ethernet ports of different types support different Working Mode. l When the equipment on the opposite side works in autonegotiation mode, set the Working Mode of the equipment on the local side to AutoNegotiation. l When the equipment on the opposite side works in full-duplex mode, set the Working Mode of the equipment on the local side to 10M FullDuplex, 100M FullDuplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. l When the equipment on the opposite side works in half-duplex mode, set the Working Mode of the equipment on the local side to 10M HalfDuplex, 100M HalfDuplex, or AutoNegotiation depending on the port rate of the equipment on the opposite side. l FE ports support 10M full-duplex, 10M halfduplex, 100M fullduplex, 100M halfduplex, and autonegotiation. l GE electrical ports support 10M fullduplex, 10M halfduplex, 100M fullduplex, 100M half-
B-106
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description duplex, 1000M fullduplex, and autonegotiation. l GE optical ports support 1000M fullduplex and autonegotiation.
Max Frame Length (byte)
1518 to 9600
1522
The value of Max Frame Length(byte) should be greater than the length of any frame to be transported. l Auto-Negotiation Ability specifies the auto-negotiation capability of the Ethernet port. l For GE optical ports, Auto-Negotiation Ability can be set to 1000M Full-Duplex only. l Auto-Negotiation Ability is valid only when Working Mode is set to AutoNegotiation.
Auto-Negotiation Ability
Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex 1000M Full-Duplex
FE: 100M Full-Duplex GE: 1000M Full-Duplex
Logical Port Attribute
Optical Port Electrical Port
l This parameter specifies the attribute of the logical port. l The SFP on the EM6F board supports the optical port and electrical port.
Physical Port Attribute
This parameter indicates the attribute of the physical port.
Related Tasks
A.5.6.1 Setting the General Attributes of Ethernet Ports
Issue 03 (2011-04-10)
B-107
B.5.2.2 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Flow Control tab.

Parameter Port Non-Autonegotiation Flow Control Mode Value Range Disabled Enable Symmetric Flow Control Default Value Disabled Description This parameter indicates the port name. l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to AutoNegotiation. l Non-Autonegotiation Flow Control Mode of the equipment on the local side must be consistent with the non-autonegotiation flow control mode of the equipment on the opposite side l The OptiX RTN 950 supports only two nonauto-negotiation flow control modes, namely, Disabled mode and Enable Symmetric Flow Control mode.
B-108
Issue 03 (2011-04-10)
Parameter Auto-Negotiation Flow Control Mode
Value Range Disabled Enable Symmetric Flow Control
Description l Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to Auto-Negotiation. l Auto-Negotiation Flow Control Mode of the equipment on the local side must be consistent with the auto-negotiation flow control mode of the equipment on the opposite side l The OptiX RTN 950 supports only two auto-negotiation flow control modes, namely, Disabled mode and Enable Symmetric Flow Control mode.
Related Tasks
B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Layer 2 Attributes tab.

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Issue 03 (2011-04-10)
B-109
Parameter Port QinQ Type Domain
Value Range -
Default Value -
Description This parameter indicates the port name. l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ Type Domain. The default value is 88A8. l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be changed. l QinQ Type Domain should be set to the same value for all the ports on the EM6T/ EM6F board .
TAG
Tag Aware Access Hybrid
Tag Aware
l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access. l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
NOTE TAG specifies the TAG flag of a port. For details about the TAG flags and associated frameprocessing methods, see Table B-2.
B-110
Issue 03 (2011-04-10)
Parameter Default VLAN ID
Default Value 1
Description l Default VLAN ID is valid only when TAG is set to Access or Hybrid. l Default VLAN ID is set according to the actual situations.
NOTE For details about the functions of Default VLAN ID, see Table B-2.
VLAN Priority
0 to 7
l VLAN Priority is valid only when TAG is set to Access or Hybrid. l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN Priority is set according to the planning information. In normal cases, it is recommended that you use the default value.
NOTE For details about the functions of VLAN Priority, see Table B-2.
Table B-2 Methods used by Ethernet interfaces to process data frames Port Type of Data Frame Tagged frame Untagged frame Processing Method Tag Aware The port receives the frame. The port discards the frame. Access The port discards the frame. The ports add the VLAN tag, to which Default VLAN ID and VLAN Priority correspond, to the frame and receive the frame. Hybrid The port receives the frame. The ports add the VLAN tag, to which Default VLAN ID and VLAN Priority correspond, to the frame and receive the frame.
Ingress UNI
Issue 03 (2011-04-10)
B-111
Port
Type of Data Frame Tagged frame
Processing Method Tag Aware The port transmits the frame. Access The port strips the VLAN tag from the frame and then transmits the frame. Hybrid l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Egress UNI
Related Tasks
A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports
B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes

This topic describes the parameters that are related to the Layer 3 attributes of Ethernet ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Layer 3 Attributes tab.

NOTE
Layer 3 Attributes is valid only if Port Mode is set to Layer 3.
Parameter Port
Value Range -
Default Value -
Description Displays the port name.
B-112
Issue 03 (2011-04-10)
Parameter Enable Tunnel
Description l If Enable Tunnel is set Enabled, a port identifies and processes MPLS labels. l Enable Tunnel is available if you set Port Mode to Layer 3 in the General Attributes tab.
Max Reserved Bandwidth(kbit/s) TE Measurement Admin Group Specify IP Address
Manually Unspecified
Unspecified
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. l Specifies the method of setting the IP address of a port. l The value Unspecified indicates that the IP addresses do not need to be configured. l The value Manually indicates that the IP address of the port can be manually configured.
IP Address
0.0.0.0
l Specifies the IP address of a port. l This parameter is available when Specify IP Address is Manually. l The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment.
Issue 03 (2011-04-10)
B-113
Parameter IP Mask
Value Range -
Default Value 255.255.255.252
Description l Specifies the subnet mask of a port. l This parameter is available when Specify IP Address is Manually.
Board for Borrowed IP Address Board for Borrowed IP Address
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Related Tasks
A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports
B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Advanced Attributes tab.

Parameter Port Port Physical Parameters Value Range Default Value Description This parameter indicates the port name. This parameter indicates the physical parameters of the port.
B-114
Issue 03 (2011-04-10)
Parameter MAC Loopback
Value Range Non-Loopback Inloop
Description l This parameter specifies the loopback state at the MAC layer. When this parameter is set to Inloop, the Ethernet signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
PHY Loopback
Non-Loopback Inloop
Non-Loopback
l This parameter specifies the loopback state at the PHY layer. When this parameter is set to Inloop, the Ethernet physical signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
MAC Address
This parameter indicates the MAC address of the port. This parameter indicates the rate at which the data packets are transmitted. This parameter indicates the rate at which the data packets are received. This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port. This parameter indicates whether to enable the loop port shutdown function. This parameter indicates the egress PIR bandwidth.
Transmitting Rate(kbit/ s) Receiving Rate(kbit/s)
Loopback Check
Enabled Disabled
Disabled
Loopback Port Shutdown Egress PIR Bandwidth (Kbit/s)
Enabled Disabled -
Disabled
Issue 03 (2011-04-10)
B-115
Parameter Enabling Broadcast Packet Suppression
Description l This parameter specifies whether to limit the traffic rate of the broadcast packets according to the proportion of the broadcast packets in the total packets. When the equipment at the opposite end may encounter a broadcast storm, this parameter is set to Enabled. l If Ethernet services are E-LAN services, the recommended value is Enabled. l This parameter takes effect only for E-LAN services in the ingress direction.
0 to 100
30
When the proportion of the broadcast packets in the total packets exceeds the value of this parameter, the received broadcast packets are discarded. The value of this parameter should be more than the proportion of the broadcast packets in the total packets before the broadcast storm occurs. In normal cases, this parameter is set to default value.
Related Tasks
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports
B.5.3 Serial Port Parameters

This topic describes the parameters that are related to serial ports. B.5.3.1 Parameter Description: Serial Port_Basic Attributes This topic describes the parameters that are related to the basic attributes of series ports. B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports
This topic describes parameters that are used for creating serial ports.
B.5.3.1 Parameter Description: Serial Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of series ports.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Click the General Attributes tab.

Parameter Port Value Range Default Value Description Displays the name of the port where a serial service is configured. Specifies or displays the customized port name. l Specifies or displays the serial port level. l 64K Timeslot: 64 kbit/ s timeslots of E1 signals can be bound.
NOTE The OptiX RTN 950 supports 64K Timeslot only.
Name Level
Used Port
Displays the physical port that carries a serial service. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Displays the timeslots that a serial service occupies. The timeslots can be consecutive or not. l Displays or specifies the port mode. l A port supports ATM encapsulation if its Port Mode is Layer 2.
High Channel Low Channel 64K Timeslot
Port Mode
Layer 2
Layer 2
Issue 03 (2011-04-10)
B-117
Value Range -
Default Value -
Description l Displays and specifies the encapsulation type of a PW. l When Port Mode is Layer 2, this parameter displays ATM.
Max Data Packet Size (byte)
The OptiX RTN 950 does not support this parameter.
Related Tasks
A.5.5.1 Creating Serial Ports
B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports

This topic describes parameters that are used for creating serial ports.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the New tab.

Parameter Port Number(e.g:1,3-6) Value Range Default Value Description Specifies the port where the serial service is configured. Specifies the customized port name. l Specifies the serial port level. l When this parameter is set to 64K Timeslot , E1 timeslots can be bound.
NOTE The OptiX RTN 950 supports only the parameter value 64K Timeslot .
Name Level
64K Timeslot
64K Timeslot
Used Board
Specifies the board where a serial port is located.

Issue 03 (2011-04-10)
B-118
Parameter Used Port High Channel Low Channel(e.g:1,3-6) 64K Timeslot(e.g:1,3-6)
Value Range -
Default Value -
Description Displays the board where a serial port is located. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Specifies the 64 kbit/s timeslots to be bound with the serial port. The timeslots can be consecutive or not.
Related Tasks
A.5.5.2 Setting Basic Attributes of Serial Ports
B.5.4 Microwave Interface Parameters

This topic describes the parameters that are related to IF_ETH interfaces. B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of microwave interfaces. B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces. B.5.4.3 Parameter Description: Microwave Interface_Layer 3 Attributes This topic describes the parameters that are related to the Layer 3 attributes of an IF_ETH port. B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the General Attributes tab.
Issue 03 (2011-04-10)
B-119
Parameters
Parameter Port Name Port Mode Value Range Layer 2 Layer 3 Default Value Layer 2 Description This parameter indicates the corresponding IF port. This parameter indicates or specifies the customized port name. l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels. Encapsulation Type Null 802.1Q QinQ 802.1Q l Encapsulation Type specifies the method of the port to process the received packets. l If Encapsulation Type is set to Null, the port transparently transmits the received packets. l If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. l If Encapsulation Type is set to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
Related Tasks

This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Layer 2 Attributes tab.
Parameters for Layer 2 Attributes

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
B-120
Issue 03 (2011-04-10)
Parameter Port QinQ Type Domain
Value Range -
Default Value -
Description This parameter indicates the corresponding IF port. l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ Type Domain. The default value is 88A8. l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be changed.
Tag
Tag Aware
l If all the accessed services are frames that contain the VLAN tag (tagged frames), set Tag to "Tag Aware". l If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set Tag to "Access". l If the accessed services contain tagged frames and untagged frames, set Tag to "Hybrid".
NOTE Tag specifies the TAG flag of a port. For details about the TAG flags and associated frameprocessing methods, see Table B-3.
Default VLAN ID
1 to 4094
l Default VLAN ID is valid only when TAG is set to Access or Hybrid. l Default VLAN ID needs to be set according to the actual situations.
NOTE For details about the functions of Default VLAN ID, see Table B-3.
VLAN Priority
0 1 2 3 4 5 6 7
l VLAN Priority is valid only when TAG is set to Access or Hybrid. l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN Priority needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
NOTE For details about the functions of VLAN Priority, see Table B-3.
Issue 03 (2011-04-10)
B-121
Table B-3 Data frame processing Status Type of Data Frame Tagged frame Untagged frame Processing Method Tag Aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" is added to the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame. The port receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" is added to the frame. l If the VLAN ID in the frame is "Default VLAN ID", the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not "Default VLAN ID", the port directly transmits the frame.
Ingress Port
Egress Port
Tagged frame
The port transmits the frame.
Related Tasks
A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port

This topic describes the parameters that are related to the Layer 3 attributes of an IF_ETH port.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Layer 3 Attributes tab.
B-122
Issue 03 (2011-04-10)

Parameter Port Enable Tunnel Value Range Disabled Enabled Default Value Disabled Description Displays the corresponding IF port. l A port identifies and processes MPLS labels, if its Enable Tunnel is set Enabled. l Enable Tunnel is available if you set Port Mode to Layer 3 in the General Attributes tab. Max Reserved Bandwidth(kbit/s) Admin Group Specify IP Address Manually Unspecified Unspecified The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. l Specifies the method of setting the IP address of a port. l The value Unspecified indicates that the IP addresses do not need to be configured for a port. l The value Manually indicates that the IP address of a port can be manually configured. IP Address 0.0.0.0 l Specifies the IP address for a port. l This parameter is available when Specify IP Address is Manually. l The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment.
Issue 03 (2011-04-10)
B-123
Parameter IP Mask
Value Range -
Default Value 255.255.255.252
Description l Specifies the subnet mask of a port. l This parameter is available when Specify IP Address is Manually.
Related Tasks
A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports
B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Advanced Attributes tab.
Parameters for Advanced Attributes

Parameter Port Radio Link ID Value Range 1 to 4094 Default Value 1 Description This parameter indicates the corresponding IF port. l This parameter specifies the ID of the radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l The ID of each radio link of an NE must be unique, and the link IDs at both ends of a radio link must be the same. Received Radio Link ID l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match with the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match.
Parameter IF Port Loopback
Value Range -
Default Value -
Description l This parameter indicates the loopback status of the IF interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the IF signals transmitted to the opposite end are looped back. l Outloop indicates that the received IF signals are looped back. l Generally, this parameter is used to locate the faults that occur at each IF interface. The IF loopback is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal cases, this parameter is set to Non-Loopback.
Composite Port Loopback
l This parameter indicates the loopback status on the composite interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the composite signals transmitted to the opposite end are looped back. l Outloop indicates that the received composite signals are looped back. l In normal cases, this parameter is set to Non-Loopback.
Error Frame Discard Enabled
Enabled Disabled
Enabled
l This parameter indicates or specifies whether to discard the Ethernet frame when a CRC error occurs in an Ethernet frame. l If the Ethernet service transmitted on the IF_ETH port is a voice service or a video service, you can set this parameter to Disabled.
MAC Address Transmitting Rate (Kbit/s) Receiving Rate (Kbit/s)
This parameter indicates the MAC address of the port. This parameter indicates the transmit rate of the local port. This parameter indicates the receive rate of the local port.
Issue 03 (2011-04-10)
B-125
Parameter MAC Loopback
Value Range Non-Loopback Inloop
Description l This parameter specifies the loopback state at the MAC layer. When this parameter is set to Inloop, the Ethernet signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
NOTE The ISU2 and ISX2 boards can not be set to Inloop.
Speed Air Interface Transmission at L2
Disabled Enabled
Disabled
l If Speed Air Interface Transmission at L2 is set to Enabled, the Layer-2 Ethernet packets transmitted at microwave ports will be compressed to improve transmission efficiency. l If the Layer 2 header compression function can be enabled for the ISU2 or ISX2 board, it is recommended that you set Speed Air Interface Transmission at L2 to Enabled. l The settings of Speed Air Interface Transmission at L2 must be the same at both ends of a radio link.
Speed Air Interface Transmission at L3
Disabled Enabled
Disabled
l If Speed Air Interface Transmission at L3 is set to Enabled, the IP packets transmitted at microwave ports will be compressed to improve transmission efficiency. l If the Layer 3 header compression function can be enabled for the ISU2 or ISX2 board, it is recommended that you set Speed Air Interface Transmission at L3 to Enabled. l The settings of Speed Air Interface Transmission at L3 must be the same at both ends of a radio link.
NOTE l The ISU2 and ISX2 boards support this parameter. l When Speed Air Interface Transmission at L3 is set to Enabled, Encapsulation Type of the ISU2 and ISX2 boards cannot be set to Null.
B-126
Issue 03 (2011-04-10)
Parameter Loopback Check
Description This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port. This parameter indicates whether to enable the automatic shut-down of looped ports. l This parameter specifies whether to limit the traffic rate of the broadcast packets according to the proportion of the broadcast packets in the total packets. When the equipment at the opposite end may encounter a broadcast storm, this parameter is set to Enabled. l If Ethernet services are E-LAN services, the recommended value is Enabled. l This parameter takes effect only for ELAN services in the ingress direction.
Loopback Port Shutdown Broadcast Packet Suppression
Disabled Enabled Disabled Enabled
Disabled
Disabled
0 to 100
30
When the proportion of the broadcast packets in the total packets exceeds the value of this parameter, the received broadcast packets are discarded. The value of this parameter should be more than the proportion of the broadcast packets in the total packets before the broadcast storm occurs. In normal cases, this parameter is set to default value.
Related Tasks
B.5.5 IF Board Parameters

This topic describes parameters that are related to IF boards. B.5.5.1 Parameter Description: IF Interface_IF Attribute This topic describes the parameters that are related to IF attributes. B.5.5.2 Parameter Description: IF Interface_ATPC Attribute This topic describes the parameters that are related to the ATPC attributes. B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes This section describes the parameters that are used for configuring the advanced attributes. B.5.5.4 Parameter Description: ATPC Adjustment Records This topic describes the parameters that are related to ATPC adjustment records. B.5.5.5 Parameter Description: PRBS Test
This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS) test.

This topic describes the parameters that are related to IF attributes.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab.
Parameters
Parameter Port Radio Work Mode Value Range 1,4E1,7MHz,QPSK 2,4E1,3.5MHz, 16QAM 3,8E1,14MHz,QPS K 4,8E1,7MHz, 16QAM 5,16E1,28MHz,QP SK 6,16E1,14MHz, 16QAM 7,STM-1,28MHz, 128QAM 8,E3,28MHz,QPSK 9,E3,14MHz, 16QAM 10,22E1,14MHz, 32QAM 11,26E1,14MHz, 64QAM 12,32E1,14MHz, 128QAM 13,35E1,28MHz, 16QAM 14,44E1,28MHz, 32QAM 15,53E1,28MHz, 64QAM
Default Value -
Description This parameter indicates the corresponding IF interface. l This parameter indicates or specifies the work mode of the radio link in "work mode number, service capacity, channel spacing, modulation mode" format. l This parameter is set according to the planning information. The work modes of the IF boards at the two ends of a radio link must be the same.
NOTE The IF1 board supports this parameter.
Parameter IF Service Type
Value Range Hybrid(Native E1 +ETH) Hybrid(Native STM-1+ETH) SDH
Default Value Hybrid(Native E1 +ETH)
Description l Displays or specifies the type of services carried by the IF board. l If the Integrated IP radio transmits Native E1 services, set this parameter to Hybrid(Native E1+ETH). l If the Integrated IP radio transmits Native STM-1 services, set this parameter to Hybrid(Native STM-1 +ETH). l If the SDH radio transmits SDH services, set this parameter to SDH.
Radio Link ID
1 to 4094
l Link ID indicates or specifies the ID of a radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l If the value of Received Radio Link ID does not match the preset value of Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports MW_LIM alarm to the NMS, indicating that the link IDs do not match. l Link ID is set according to the planning information. Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same.
Received Radio Link ID
l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match. l When the radio link becomes faulty, this parameter is displayed as an invalid value.
Issue 03 (2011-04-10)
B-129
Parameter IF Port Loopback
Description l This parameter indicates or specifies the loopback status of the IF interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the IF signals transmitted to the opposite end are looped back. l Outloop indicates that the received IF signals are looped back. l Generally, IF Port Loopback is used to locate the faults that occur at each IF interface. The IF loopback is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal cases, this parameter is set to Non-Loopback.
2M Wayside Enable Statusa
Disabled Enabled
Disabled
l This parameter indicates or specifies whether the radio link transmits the wayside E1 service. l The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz, 16QAM mode.
2M Wayside Input Boarda
l This parameter indicates or specifies the slot in which the 2M wayside service is accessed. l This parameter can be set only when 2M Wayside Enable Status is set to Enabled. l The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz, 16QAM mode.
350 MHz Consecutive Wave Status
Stop Start
Stop
l This parameter indicates or specifies the status of transmitting the 350 MHz carrier signals at the IF interface. l 350 MHz Consecutive Wave Status can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, the services are interrupted.
B-130
Issue 03 (2011-04-10)
Parameter XPIC Enabledb
Description l This parameter indicates or specifies whether the XPIC function of the XPIC IF board is enabled. l If the XPIC IF board does not perform the XPIC function, XPIC Enabled should be set to Disabled.
Enable IEEE-1588 Timeslotc
Enabled Disabled
Disabled
Enable IEEE-1588 Timeslot needs to be set consistently between two ends of a radio link.
NOTE
l a. The IFU2 and IFX2 boards do not support way-side services. l b. The IFU2, ISU2, and IF1 boards do not support the XPIC function. l c. The IF1 board does not support the IEEE-1588 timeslot function.
Parameters for Hybrid/AM Configuration

NOTE
The IF1 board does not support Hybrid/AM configuration.
Parameter Port IF Channel Bandwidth
Value Range 7M 14M 28M 40M 56M
Default Value -
Description This parameter indicates the corresponding IF port. IF Channel Bandwidth indicates the channel spacing of the corresponding radio link. This parameter is set according to the planning information.
NOTE l This parameter is not applicable to the IF1 board. l The IFU2 board does not support the value 40M. l The IFX2 board does not support the values 7M, 14M, and 40M. l The ISX2 board supports the channel spacings of 7M and 14M only when the XPIC function is disabled.
Issue 03 (2011-04-10)
B-131
Parameter AM Status
Description l When AM Status is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manual Modulation Mode. l When AM Status is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Hence, the Integrated IP radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled. l The ISX2/ISU2 does not support the AM function when IF Service Type is SDH.
Modulation Mode of the Guarantee AM Capacity
QPSK
l This parameter is valid only when AM Status is set to Enabled. l Modulation Mode of the Guarantee AM Capacity specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation scheme.
Modulation Mode of the Full AM Capacity
QPSK
l This parameter is valid only when AM Status is set to Enabled. l Modulation Mode of the Full AM Capacity specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation scheme.
B-132
Issue 03 (2011-04-10)
Parameter Manually Specified Modulation Mode
Default Value QPSK
Description l This parameter specifies the modulation scheme that the radio link uses for signal transmission. l This parameter is valid only when AM Status is set to Disabled.
STM-1 Capacity
l Specifies the STM-1 capacity of the IF board. l This parameter is available only when IF Service Type is set to Hybrid(Native STM-1+ETH) and SDH. l If IF Service Type is Hybrid(Native STM-1+ETH), this parameter can be set to 0 or 1. l If IF Service Type is SDH, this parameter can be set to 1 or 2.
NOTE The IFU2 and IFX2 boards do not support this parameter.
Enable E1 Priority
Disabled Enabled
Disabled
l This parameter specifies whether to enable the E1 priority function. l This parameter is valid only when AM Status is set to Enabled. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity
l If AM Status is set to Enabled, this parameter needs to be set according to IF Channel Bandwidth, Modulation Mode of the Guarantee AM Capacity, and the actually transmitted services. l If AM Status is set to Disabled, this parameter needs to be set according to IF Channel Bandwidth, Manually Specified Modulation Mode, and the actually transmitted services. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity Range
Displays the E1 capacity range of the IF board in guarantee capacity modulation mode.
Issue 03 (2011-04-10)
B-133
Parameter Data Service Bandwidth(Mbit/ s) Full E1 Capacity
Value Range -
Default Value -
Description Displays the data service bandwidth of the IF board. l This parameter specifies the number of transmitted E1 services in Modulation Mode of the Full AM Capacity. l This parameter is valid if Enable E1 Priority is set to Enabled. l E1 service bandwidth in full capacity mode Service bandwidth in full capacity mode - Service bandwidth in guarantee capacity mode + E1 service bandwidth in guarantee capacity mode. In addition, the number of E1 services in full capacity modulation mode should be smaller than or equal to the maximum number of E1 services in full capacity modulation mode. l The Full E1 Capacity must be set to the same value at both ends of a radio link. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Full E1 Capacity Transmit-End Modulation Mode Receive-End Modulation Mode Guarantee AM Service Capacity (Mbit/s) Full AM Service Capacity(Mbit/s) Transmitted AM Service Capacity (Mbit/s) Received AM Service Capacity (Mbit/s) E1 Capacity For High Priority
Displays the E1 capacity range of the IF board in full capacity modulation mode. Displays the modulation mode at the transmit mode. Displays the modulation mode at the receive mode. Displays the guarantee AM service capacity.
Displays the full AM service capacity. Displays the transmitted AM service capacity. Displays the received AM service capacity.
Displays the number of configured highpriority E1s.
B-134
Issue 03 (2011-04-10)
Related Tasks
A.5.8.1 Setting IF Attributes A.5.8.4 Querying the AM Status A.5.8.6 Modifying the Hybrid/AM Attributes A.11.4 Configuring the Wayside E1 Service
B.5.5.2 Parameter Description: IF Interface_ATPC Attribute

This topic describes the parameters that are related to the ATPC attributes.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Click the ATPC Attributes tab.
Parameters
Parameter Port ATPC Enable Status Value Range Disabled Enabled Default Value Disabled Description This parameter indicates the corresponding IF interface. l This parameter specifies whether the ATPC function is enabled. l When this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set ATPC Enable Status to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes. ATPC Upper Threshold(dBm)
Issue 03 (2011-04-10)
-45.0
l Set the central value between the ATPC upper threshold and the ATPC lower
B-135
Parameter ATPC Lower Threshold(dBm)
Value Range -
Default Value -70.0
Description threshold to a value for the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set the ATPC upper threshold only when ATPC Automatic Threshold(dBm) is set to Disabled. l This parameter specifies whether the ATPC automatic threshold function is enabled. l If ATPC Automatic Threshold Enable Status is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link. l If ATPC Automatic Threshold Enable Status is set to Disabled, you need to manually set ATPC Upper Automatic Threshold(dBm) and ATPC Lower Automatic Threshold(dBm).
Enabled Disabled
Disabled
ATPC Upper Automatic Threshold(dBm) ATPC Lower Automatic Threshold(dBm)
l This parameter indicates that the equipment automatically uses the preset ATPC upper and lower thresholds. l This parameter is valid only when ATPC Automatic Threshold Enable Status is set to Enabled.
Related Tasks
A.5.8.2 Configuring the ATPC Attributes
B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes

This section describes the parameters that are used for configuring the advanced attributes.
B-136
Issue 03 (2011-04-10)
Navigation Path
l l In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from the Function Tree. Click the AM Advanced Attributes tab.
Parameters
Parameter Port Modulation Mode E1 Capacity Value Range Default Value Description This parameter indicates the corresponding IF interface. Displays the modulation schemes. l You can specify the number of E1s that can be transmitted in intermediate modulation scheme, by setting the advanced attributes correspondingly. l Generally, it is recommended that this parameter takes the default value. To ensure that a specific number of E1s can be transmitted in intermediate modulation scheme, adjust the E1 capacity in each modulation scheme according to the network planning information. l If the E1 priority function is enabled, the maximum number of allowed E1 services in the current mode = Min {[Bandwidth of the air interface in the current mode - (Bandwidth for the assured capacity - Assured E1 number x 2Mbps)]/2Mbps, E1 number in the highest-gain modulation mode}. Data Service Bandwidth(Mbit/ s) Displays the data service bandwidth.
Related Tasks
B.5.5.4 Parameter Description: ATPC Adjustment Records

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Parameter Port Event NO. Adjustment Time Adjustment Direction Switchover Transmitted Power(dBm) Received Power (dBm) Value Range Default Value Description This parameter indicates the port for the ATPC adjustment. This parameter indicates the number of the ATPC adjustment event. This parameter indicates the time of the ATPC adjustment. This parameter indicates the direction of the adjustment at the port. This parameter indicates the switching operation at the port. This parameter indicates the transmitted power of the port to be switched. This parameter indicates the received power of the port to be switched.
Related Tasks
A.5.8.5 Querying the ATPC Adjustment Records
B.5.5.5 Parameter Description: PRBS Test

Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port for the PRBS test.
B-138
Issue 03 (2011-04-10)
Parameter Direction
Value Range Cross Tributary
Default Value Cross
Description l This parameter indicates or specifies the direction of the PRBS test. l In the tributary direction, the PRBS test is performed to check the connectivity of the cable from the tributary board to the DDF. l In the cross-connect direction, the PRBS test is performed to check the processing of the service from the tributary board to the NE at the remote end.
Duration Measured Time
1 to 255 s 10min h
1 s
This parameter indicates or specifies the duration of the PRBS test. This parameter indicates or specifies the time unit used for the PRBS test.
Start Time Progress Total PRBS Accumulating Mode
Selected Deselected
Deselected
This parameter indicates the start time of the PRBS test. This parameter indicates the progress percentage of the PRBS test. This parameter indicates the number of bit errors that occur in the PRBS test. This parameter specifies whether to display the values in accumulative mode. If Accumulating Mode is selected, it indicates that the values are displayed in accumulative mode.
B.5.6 ODU Parameters

This topic describes parameters that are related to ODUs. B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute This topic describes the parameters that are related to radio frequency attributes of an ODU. B.5.6.2 Parameter Description: ODU Interface_Power Attributes This topic describes the parameters that are used for configuring the power attributes of the ODU. B.5.6.3 Parameter Description: ODU Interface_Equipment Information This topic describes the parameters that are used for configuring the equipment information of the ODU. B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes of the ODU.
B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute

This topic describes the parameters that are related to radio frequency attributes of an ODU.
Navigation Path
l l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Radio Frequency Attributes tab.
Parameters
Parameter Board Transmit Frequency(MHz) Value Range Default Value Description This parameter indicates the corresponding ODU. l This parameter indicates or specifies the transmit frequency of the ODU, namely, the central frequency of the channel. l The value of Transmit Frequency (MHz) must not be less than the sum of the minimum transmit frequency supported by the ODU and a half of the channel spacing, and must not be more than the difference between the maximum transmit frequency supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies at both ends of a radio link should be one T/R spacing. l This parameter is set according to the planning information.
B-140
Issue 03 (2011-04-10)
Parameter T/R Spacing(MHz)
Value Range -
Default Value -
Description l This parameter indicates or specifies the spacing between the transmit frequency and receive frequency of the ODU to prevent mutual interference of the transmitter and receiver. l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, T/R Spacing(MHz) is set to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and T/R Spacing (MHz) should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Actual Transmit Frequency(MHz) Actual Receive Frequency(MHz) Actual T/R Spacing(MHz) The range of frequency point (MHz)
This parameter indicates the actual transmit frequency of the ODU. This parameter indicates the actual receive frequency of the ODU. This parameter indicates the actual T/R spacing of the ODU. This parameter indicates the working range of the frequency of the ODU.
Related Tasks
A.5.9.1 Setting the Transmit Frequency Attribute of the ODU
B.5.6.2 Parameter Description: ODU Interface_Power Attributes

This topic describes the parameters that are used for configuring the power attributes of the ODU.
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree.
Issue 03 (2011-04-10)
Click the Power Attributes tab.
Parameters
Parameter Board Maximum Transmit Power (dBm) Value Range Default Value Description This parameter indicates the corresponding ODU. l Maximum Transmit Power(dBm) is set according to the planning information. This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed Maximum Transmit Power (dBm). Transmit Power (dBm) l Transmit Power(dBm) is set according to the planning information. This parameter specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU or a value that exceeds Maximum Transmit Power (dBm). l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services.
B-142
Issue 03 (2011-04-10)
Parameter Power to Be Received(dBm)
Default Value -10.0
Description l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l Power to Be Received(dBm) is set according to the planning information. When this parameter takes the default value, the antenna misalignment indicating function is disabled.
TX High Threshold(dBm)
l If the value of the actual transmit power of the ODU is greater than the preset value of TX High Threshold(dBm), the system separately records the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX High Threshold (dBm) and the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) in the performance events. l If the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) and is lower than the preset value of TX High Threshold(dBm), the system records the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) in the performance events.
Issue 03 (2011-04-10)
B-143
Parameter TX Low Threshold (dBm)
Value Range -
Default Value -
Description l If the value of the actual transmit power of the ODU is lower than the preset value of TX Low Threshold(dBm), the system does not record it. l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function is enabled.
RX High Threshold(dBm)
l If the value of the actual receive power of the ODU is lower than the preset value of RX Low Threshold(dBm), the system records the duration when the value of the actual receive power of the ODU is lower than the preset value of RX Low Threshold(dBm) and duration when the value of the actual transmit power of the ODU is lower than the preset value of RX High Threshold (dBm)in the performance events. l If the value of the actual receive power of the ODU is greater than the preset value of RX Low Threshold(dBm) and is lower than the preset value of RX High Threshold(dBm), the system records the duration when the value of the actual receive power of the ODU is Lower than the preset value of RX High Threshold (dBm) in the performance events. l If the value of the actual receive power of the ODU is greater than the preset
B-144
Issue 03 (2011-04-10)
Parameter RX Low Threshold (dBm)
Value Range -
Default Value -
Description value of RX High Threshold(dBm), the system does not record it.
Actual Transmit Power(dBm)
l This parameter indicates the actual transmit power of the ODU. l If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
Actual Receive Power(dBm) Actual Power Range(dBm) Transmission Power Type
This parameter indicates the actual receive power of the ODU. This parameter indicates the range of the actual transmit power of the ODU. This parameter indicates the level of the output power of the ODU.
Related Tasks
B.5.6.3 Parameter Description: ODU Interface_Equipment Information

This topic describes the parameters that are used for configuring the equipment information of the ODU.
Issue 03 (2011-04-10)
B-145
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Equipment Information tab.
Parameters
Parameter Board Frequency(GHz) Equipment Type Value Range Default Value Description This parameter indicates the corresponding ODU. This parameter indicates the frequency band where the ODU operates. l This parameter indicates the equipment type of the ODU. l PDH and SDH indicate the transmission capacity only and are irrelevant to the type of transmitted service. T/R Spacing(MHz) Intermediate Frequency Bandwidth (MHz) IF Bandwidth Type Station Type This parameter indicates the T/R spacing of the ODU. This parameter indicates the IF frequency bandwidth of the ODU. Displays the IF bandwidth type. l This parameter indicates whether the ODU is a Tx high station or a Tx low station. l The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station. Transmission Power Type Produce Time Produce SN This parameter indicates the level of the output power of the ODU. This parameter indicates the manufacturing time of the ODU. This parameter indicates the manufacturing serial number and the manufacturer code of the ODU.
Related Tasks
A.5.9.2 Querying the ODU Attribute
B-146
Issue 03 (2011-04-10)
B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes of the ODU.
Navigation Path
l l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Advanced Attributes tab.
Parameters
Parameter Board RF Loopback Value Range Non-Loopback Inloop Default Value Non-Loopback Description This parameter indicates the corresponding ODU. l This parameter indicates or specifies the loopback status of the RF interface of the ODU. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the RF signals transmitted to the opposite end are looped back. l RF Loopback function is used for fault locating for the RF interfaces. The RF Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, RF Loopback is set to Non-Loopback. Configure Transmission Status unmute mute unmute l This parameter indicates or specifies the transmit status of the ODU. l If Configure Transmission Status is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. l If Configure Transmission Status is set to unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, Configure Transmission Status is set to unmute. Actual Transmission Status
Issue 03 (2011-04-10)
Displays the ODU manufacturer information.
B-147
Parameter Factory Information Remarks
Value Range -
Default Value -
Description This parameter indicates the manufacturer information about the ODU. Specifies the remarks of the ODU.
Related Tasks
A.5.9.4 Setting the Advanced Attributes of the ODU
B.5.7 Parameters for SDH Interface Boards

This topic describes parameters that are related to SDH interface boards. B.5.7.1 Parameter Description: SDH Interfaces This topic describes the parameters that are related to the SDH interfaces. B.5.7.2 Parameter Description: Automatic Laser Shutdown This topic describes the parameters that are related to the automatic laser shutdown (ALS) function.
B.5.7.1 Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Interface from the Function Tree. Select By Board/Port(Path), and select Port or VC4 Path from the list box.
Parameters
Parameter Port Laser Switcha Value Range On Off Default Value On Description This parameter indicates the corresponding SDH interface. l This parameter indicates or specifies the on/off state of the laser. l This parameter is set for SDH optical interfaces only. l In normal cases, this parameter is set to On.
B-148
Issue 03 (2011-04-10)
Parameter Optical(Electrical) Interface Loopbacka
Description l This parameter indicates or specifies the loopback status on the SDH interface. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the SDH signals transmitted to the opposite end are looped back. l Outloop indicates that the received SDH signals are looped back. l This function is used for fault locating for the SDH interfaces. The Optical (Electrical) Interface Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback.
VC4 Loopbackb
Non-Loopback Inloop Outloop
Non-Loopback
l This parameter indicates or specifies the loopback status in the VC-4 path. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the VC-4 signals transmitted to the opposite end are looped back. l Outloop indicates that the received VC-4 signals are looped back. l This function is used for fault locating for the VC-4 paths. The VC4 Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback.
NOTE
l a: Indicates the parameters that are supported when Port is selected from the list box. l b: Indicates the parameters that are supported when VC4 Path is selected from the list box.
Related Tasks
A.5.1 Setting the Parameters of SDH Ports
B.5.7.2 Parameter Description: Automatic Laser Shutdown

This topic describes the parameters that are related to the automatic laser shutdown (ALS) function.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Parameter Optical Interface Auto Shutdown Value Range Disabled Enabled Default Value Disabled Description This parameter indicates the corresponding optical interface. l This parameter indicates or specifies whether the Auto Laser Shutdown function is enabled or disabled for the laser. l The ALS function allows the laser to shut down automatically when an optical port does not carry services, an optical fiber is broken, or no optical signal is received. l You can set On Period(ms), Off Period (ms), and Continuously On-test Period (ms) only when this parameter is set to Enabled. On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies the period when a shutdown laser automatically starts up and tests whether the optical fiber is normal. This parameter indicates or specifies the period when the laser does not work (with the ALS function being enabled). This parameter indicates or specifies the period when a shutdown laser is manually started up and tests whether the optical fiber is normal.
Off Period(ms)
2000 to 300000
60000
Continuously OnTest Period(ms)
2000 to 300000
90000
B.5.8 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards. B.5.8.1 Parameter Description: PDH Interfaces This topic describes the parameters that are related to the PDH interfaces. B.5.8.2 Parameter Description: PRBS Test
B.5.8.1 Parameter Description: PDH Interfaces

This topic describes the parameters that are related to the PDH interfaces.
Navigation Path
1. 2. 3. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Select By Board/Port(Channel). Select Path from the list box.
Parameters
Parameter Port Tributary Loopback Value Range Non-Loopback Inloop Outloop Default Value Non-Loopback Description This parameter indicates the corresponding port. l This parameter indicates or specifies the loopback status in the associated path of the tributary unit. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the PDH signals transmitted to the opposite end are looped back. l Outloop indicates that the received PDH signals are looped back. l This function is used for fault locating for the paths of the tributary unit. The Tributary Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback. Port Impedance This parameter indicates the impedance of a path, which depends on the tributary unit.
Issue 03 (2011-04-10)
B-151
Parameter Service Load Indication
Value Range Load Non-Loaded
Default Value Load
Description l This parameter indicates or specifies the service loading status in a specific path. l When this parameter is set to Load, the board detects whether alarms exist in the path. l When this parameter is set to NonLoaded, the board does not detect whether there are alarms in the path. l If a path does not carry any services, you can set this parameter to Non-Loaded for the path to mask all the alarms. If a path carries services, you need to set this parameter to Load for the path.
Retiming Mode
Normal Retiming Mode of Tributary Clock Retiming Mode of Cross-Connect Clock
Normal
l This parameter indicates or specifies the retiming mode of a specific path. l By using the retiming function, the retiming reference signal from the SDH network and the service data signal are combined and then sent to the client equipment, thus decreasing the output jitter in the signal. In this way, the retiming function ensures that the service code flow can normally transfer the retiming reference signal. l When this parameter is set to Normal, the retiming function is not used. l When this parameter is set to Retiming Mode of Tributary Clock, the retiming function is used with the clock of the upstream tributary unit traced. l When this parameter is set to Retiming Mode of Cross-Connect Clock, the retiming function is used with the clock of the cross-connect unit traced. l It is recommended that the external clock, instead of the retiming function, should be used to provide reference clock signals for the equipment. l If the retiming function is required, it is recommended that you set this parameter to Retiming Mode of Cross-connect Clock.
Equalize Input Signal
Unequalized Equalized
Unequalized
l This parameter indicates whether the input signals are equalized. l It is recommended that you set this parameter to default value.
B-152
Issue 03 (2011-04-10)
Parameter Equalize Output Signal
Value Range Unequalized Equalized
Default Value Unequalized
Description l This parameter indicates whether the output signals are equalized. l It is recommended that you use the default value.
Related Tasks
B.5.8.2 Parameter Description: PRBS Test

Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Port Direction Value Range Cross Tributary Default Value Cross Description This parameter indicates the port for the PRBS test. l This parameter indicates or specifies the direction of the PRBS test. l In the tributary direction, the PRBS test is performed to check the connectivity of the cable from the tributary board to the DDF. l In the cross-connect direction, the PRBS test is performed to check the processing of the service from the tributary board to the NE at the remote end. Duration Measured Time 1 to 255 s 10min h Start Time Progress This parameter indicates the start time of the PRBS test. This parameter indicates the progress percentage of the PRBS test.
B-153
1 s
This parameter indicates or specifies the duration of the PRBS test. This parameter indicates or specifies the time unit used for the PRBS test.
Issue 03 (2011-04-10)
Parameter Total PRBS Accumulating Mode
Value Range Selected Deselected
Default Value Deselected
Description This parameter indicates the number of bit errors that occur in the PRBS test. This parameter specifies whether to display the values in accumulative mode. If Accumulating Mode is selected, it indicates that the values are displayed in accumulative mode.
B.5.9 Parameters for Overhead

This topic describes the parameters that are related to overhead. B.5.9.1 Parameter Description: Regenerator Section Overhead This topic describes the parameters that are related to the regenerator section overheads (RSOHs). B.5.9.2 Parameter Description: VC-4 POHs This topic describes the parameters that are related to the VC-4 path overheads (POHs). B.5.9.3 Parameter Description: VC-12 POHs This topic describes the parameters that are related to the VC-12 path overheads (POHs).
B.5.9.1 Parameter Description: Regenerator Section Overhead

This topic describes the parameters that are related to the regenerator section overheads (RSOHs).
Navigation Path
1. 2. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.
Parameters for Setting the Display Format

Parameter Display in Text Format Display in Hexadecimal Value Range Selected Deselected Selected Deselected Deselected Default Value Selected Description This parameter specifies the display in the text format. This parameter specifies the display in the hexadecimal format.
B-154
Issue 03 (2011-04-10)

Parameter Object J0 to be Sent ([Mode]Content) Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the J0_MM alarm, this parameter is set according to the J0 byte to be received at the opposite end. l This parameter specifies the J0 byte to be received. l If this parameter is set to [Disabled], the board does not monitor the received J0 byte. l It is recommended that you use the default value. J0 Received ([Mode]Content) This parameter indicates the J0 byte that is actually received.
J0 to be Received ([Mode]Content)
[Disabled]
Related Tasks
A.5.3.1 Configuring RSOHs

This topic describes the parameters that are related to the VC-4 path overheads (POHs).
Navigation Path
1. 2. Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.

Issue 03 (2011-04-10)
B-155
Parameters for the Trace Byte J1

Parameter Object J1 to be Sent ([Mode]Content) Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the HP_TIM or LP_TIM alarm, this parameter is set according to the J1 byte to be received at the opposite end. l If this parameter is set to [Disabled], the board does not monitor the received J1 byte. l It is recommended that you use the default value. J1 Received ([Mode]Content) This parameter displays the J1 byte that is actually received.
J1 to be Received ([Mode]Content)
[Disabled]
Parameters for the Signal Flag C2

Parameter Object C2 to be Sent Value Range Default Value Description This parameter indicates the object to be set. If the NE at the opposite end reports the HP_SLM alarm, this parameter is set according to the C2 byte to be received at the opposite end. If the NE at the local end reports the HP_SLM alarm, this parameter is set according to the C2 byte to be sent at the opposite end. This parameter displays the C2 byte that is actually received.
C2 to be Received
C2 Received
Parameters for Overhead Termination

Parameter Object Value Range Default Value Description This parameter indicates the object to be set.
B-156
Issue 03 (2011-04-10)
Parameter VC4 Overhead Termination
Value Range Termination Pass-Through Auto
Default Value Auto
Description l If this parameter is set to PassThrough, the NE forwards the original overhead after monitoring the VC-4 path overhead regardless of the C2 byte. l If this parameter is set to Termination, the NE generates the new VC-4 path overhead according to the board setting after monitoring the VC-4 path overhead regardless of the C2 byte. l If this parameter is set to Auto, the VC-4 path overhead in the VC-4 pass-through service is passed through, and the VC-4 path overhead in the VC-12 service is terminated. l It is recommended that you use the default value.
Related Tasks

This topic describes the parameters that are related to the VC-12 path overheads (POHs).
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC12 Path Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.
2.

Issue 03 (2011-04-10)
B-157
Parameters for the Trace Byte

Parameter Object J2 to be Sent Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the LP_TIM or LP_TIM_VC12 alarm, this parameter is set according to the J2 byte to be received by the NE at the opposite end. l If this parameter is set to [Disabled], the board does not monitor the received J2 byte. l It is recommended that you use the default value.
NOTE IF boards do not support this parameter.
J2 to be Received
[Disabled]
J2 Received
This parameter displays the J2 byte that is actually received.
Related Tasks
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.6.1 Parameters for Ethernet Services This topic describes the parameters that are related to Ethernet services. B.6.2 Parameters for Ethernet Protocols This topic describes the parameters that are related to the Ethernet protocol. B.6.3 Parameters for the Ethernet OAM This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.6.4 QoS Parameters This topic describes the parameters that are related to QoS.
B.6.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services. B.6.1.1 Parameter Description: E-Line Service_Creation
This topic describes the interface parameters that are used for creating an Ethernet line (E-Line) service. B.6.1.2 Parameter Description: E-Line Service This topic describes the parameters that are related to E-Line services. B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation This topic describes the parameters that are used for creating VLAN forwarding table items. B.6.1.4 Parameter Description: E-LAN Service_Creation This topic describes the parameters that are used for creating an Ethernet local area network (ELAN) service. B.6.1.5 Parameter Description: E-LAN Service This topic describes the parameters that are related to E-LAN services. B.6.1.6 Parameter Description: QinQ Link_Creation This topic describes the parameters that are used for creating a QinQ link.

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line) service.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click Create.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Table B-4 Service direction of UNI-UNI Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-UNI.
Service Name
Direction
UNI-UNI UNI-NNI NNI-NNI
UNI-UNI
Issue 03 (2011-04-10)
B-159
Parameter BPDU
Value Range Not Transparent Transparent
Default Value Not Transparent
Description l This parameter specifies the transparent transmission ID of the bridge protocol data unit (BPDU) packets. It is used to indicate whether the E-Line service transparently transmits the BPDU packets. l If the BPDU packets are used as the service packets and transparently transmitted to the opposite end, set this parameter to Transparent. That is, the parameter value Transparent takes effect only if Encapsulation Type of the source and sink ports of the E-Line service are Null. l In other cases, set this parameter to Not Transparent. l This parameter is set according to the planning information.
MTU(bytes) Service Tag Role
This parameter cannot be set here. The OptiX RTN 950 does not support this parameter.
B-160
Issue 03 (2011-04-10)
Parameter Source Interface
Value Range -
Default Value -
Description l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Source VLAN ID
1 to 4094
l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number and value of VLANs must be the same value of Sink VLAN ID. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
Issue 03 (2011-04-10)
B-161
Parameter Sink Interface
Value Range -
Default Value -
Description l The value of this parameter cannot be the same as the value of Source Port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Sink VLAN ID
1 to 4094
l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number and value of VLANs must be the same value of Source VLAN ID. l If this parameter is set to null, all the services at the sink port are used as the service sink. l If this parameter is not set to null, only the service that contains the VLAN ID at the sink port can be used as the service sink.
B-162
Issue 03 (2011-04-10)
Table B-5 Service direction of UNI-NNI (carried by PWs) Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-NNI. Not Transparent For UNI-NNI ETH PWE3 services, the parameter value is always Not Transparent. This parameter cannot be set here. The OptiX RTN 950 does not support this parameter. l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Service Name
Direction
UNI-UNI
BPDU
Not Transparent Transparent
Source Interface
Issue 03 (2011-04-10)
B-163
Parameter Source VLAN ID
Default Value -
Description l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
Pri
The OptiX RTN 950 does not support this parameter. For UNI-NNI ETH PWE3 services, the parameter value is always PW.
Bearer Type
QinQ Link PW
PW
B-164
Issue 03 (2011-04-10)
Value Range No Protection PW APS Slave Protection Pair
Default Value No Protection
Description l If this parameter is set to PW APS, working and protection PWs need to be configured. l If this parameter is set to Slave Protection Pair, you need to bind the slave PW APS protection group with the master PW APS protection group. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Table B-6 Service direction of UNI-NNI (carried by QinQ links) Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-NNI. Not Transparent For UNI-NNI QinQ services, the parameter value is always Not Transparent. This parameter cannot be set here. The OptiX RTN 950 does not support this parameter.
Service Name
Direction
UNI-UNI
BPDU
Issue 03 (2011-04-10)
B-165
Parameter Source Interface
Value Range -
Default Value -
Description l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Source VLAN ID
1 to 4094
l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
Pri
The OptiX RTN 950 does not support this parameter. For NNI-NNI QinQ services, the parameter value is always QinQ Link.
Bearer Type
QinQ Link PW
PW
B-166
Issue 03 (2011-04-10)
Table B-7 Service direction of NNI-NNI Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to NNI-NNI. Not Transparent For NNI-NNI QinQ services, the parameter value is always Not Transparent . This parameter cannot be set here. The OptiX RTN 950 does not support this parameter.
Service Name
Direction
UNI-UNI
BPDU
Parameters for Port Attributes

Parameter Port Name Enable Port Value Range Enabled Disabled Default Value Description This parameter displays the UNI port. l This parameter displays or specifies whether the port is enabled. l Ethernet services can be received, processed, and forwarded normally only if Port Enable is set to Enabled. l Port Enable is already set in Ethernet Interface.
Issue 03 (2011-04-10)
B-167
Parameter Port Mode
Value Range Layer 2 Layer 3
Default Value -
Description l Specifies the working mode of an Ethernet port. l If this parameter is set to Layer 2, the port can be used to access Ethernet services from the user equipment or to carry Ethernet services that exclusively occupy the port. l When this parameter is set to Layer 3, Ethernet services over the port can be carried by PWs.
Encapsulation Type
Null 802.1Q QinQ
l This parameter displays or specifies the method of the port to process the received packets. l If you set this parameter to Null, the port transparently transmits the received packets. l If you set this parameter to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set this parameter to QinQ, the port identifies the packets that comply with the IEEE 802.1ad standard.
B-168
Issue 03 (2011-04-10)
Default Value -
Description l The Ethernet ports of different types support different working modes. l When the equipment on the opposite side works in autonegotiation mode, set the working mode of the equipment on the local side to AutoNegotiation. l When the equipment on the opposite side works in full-duplex mode, set the working mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. l When the equipment on the opposite side works in half-duplex mode, set the working mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side. l The GE optical interface supports the 1000M full-duplex mode only.
Issue 03 (2011-04-10)
B-169
Parameter Tag
Value Range Tag Aware Access Hybrid
Default Value Tag Aware
Description l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access. l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
Specify IP Address
Unspecified Manually
l Displays or selects the method to configure IP addresses of ports. l The value Unspecified indicates that the IP addresses do not need to be configured for a port. l The value Manually indicates that the IP address of a port can be manually configured. l This parameter is available when Port Mode is Layer 3.
IP Address
l Displays or specifies the IP address of the port. l This parameter is available when Specify IP Address is Manually.
IP Mask
l Displays or specifies the subnet mask of the port. l This parameter is available when Specify IP Address is Manually.
B-170
Issue 03 (2011-04-10)
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when is UNI-NNI and Bearer Type is PW. l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Parameter PW ID
Value Range -
Default Value -
Description Specifies the ID of the PW that carries services. Automatic ID assignment is recommended. Labels for static PWs need to be manually assigned. l Specifies the type of the PW. l PW Type indicates whether P-TAG is added to Ethernet frames that are encapsulated for transmission on PWs. If it is not required to add VLAN IDs, set this parameter to Ethernet. If it is required to add VLAN IDs, set this parameter to Ethernet Tagged Mode and then set Request VLAN in the Advanced Attributes tab.
PW Signaling Type PW Type
Static Ethernet Ethernet Tagged Mode
Static Ethernet
PW Direction PW Encapsulation Type
Bidirectional MPLS
Bidirectional MPLS
Displays the direction of the PW. Displays the encapsulation type of the packets on the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel selection mode
16 to 1048575 16 to 1048575 -
Issue 03 (2011-04-10)
B-171
Parameter Tunnel Type Ingress Tunnel
Value Range MPLS New Use existing PWs
Default Value MPLS New
Description Displays the type of the tunnel that carries the PW. A tunnel needs to be created or selected. If no tunnel is available, creation of a PW will fail. For a bidirectional tunnel, the system will configure the egress tunnel automatically. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned.
Egress Tunnel
New Use existing resource
New
Peer LSR ID
Parameters of Advanced Attributes (PW)

Parameter Control Word Value Range No Use Default Value No Use Description For ETH PWE3 services, the parameter value is always No Use. l Specifies the mode of PW connectivity check. l None indicates that VCCV is not used. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. VCCV Verification Mode Ping None Ping l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, do not set this parameter to None.
Control Channel Type
None Alert Label
Alert Label
B-172
Issue 03 (2011-04-10)
Parameter Request VLAN
Value Range -
Default Value -
Description l Set this parameter when PW Type is Ethernet Tagged Mode. l If the received packets do not carry any VLAN IDs, the PW will add VLAN IDs to the packets as required by the setting of this parameter.
QoS Parameters (PWs)

Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel. Policy CIR(Kbit/s) The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) Specifies the committed burst size (CBS) of a PW.
Issue 03 (2011-04-10)
B-173
Parameter PIR(Kbit/s)
Value Range -
Default Value -
Description Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR.
PBS(byte) EXP LSP Mode
Pipe
Pipe
Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
Protection Group Parameters (PW APS)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to PW APS.
Parameter Protection Type Protection Group ID Enabling Status
Description Specifies the protection type. Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
B-174
Issue 03 (2011-04-10)
Parameter Protection Mode
Value Range -
Default Value -
Description Displays the protection mode.

NOTE The OptiX RTN 950 supports 1:1 protection mode.
Switching Mode
Displays the switching mode to be used when a PW fails.

NOTE The OptiX RTN 950 supports dual-ended switching.
Revertive
Non-revertive Revertive
Revertive
l This parameter specifies whether to switch services back to the original working PW after it recovers. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
WTR Time(min)
1 to 12
l Specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive. l The default value is recommended.
Issue 03 (2011-04-10)
B-175
Parameter Hold-off Time(100ms)
Default Value 0
Description l Specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered. l The default value is recommended.
OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to PW APS. l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management > PW OAM Parameter from the Function Tree.
Parameter OAM Status
Value Range -
Default Value -
Description Displays the enabling status of PW OAM.
B-176
Issue 03 (2011-04-10)
Parameter Detection Mode
Value Range Auto-Sensing Manual
Default Value Auto-Sensing
Description l Specifies the detection mode of OAM packets. l Manual: The connectivity check (CC) packets are sent at the interval specified by the user. l Auto-Sensing: The connectivity check (CC) packets are sent at the interval of receiving PW OAM packets. l If Detection Mode is set to Manual, you need to set the PW OAM detection packets to be received and transmitted. l The value AutoSensing is recommended.
Issue 03 (2011-04-10)
B-177
Parameter Detection Packet Type
Value Range CV FFD
Default Value CV
Description 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. l If Detection Mode is set to Auto-Sensing, this parameter specifies the PW OAM detection packets to be transmitted. l If Detection Mode is set to Manual, this parameter specifies the PW OAM detection packets to be received and transmitted. l The value FFD is assumed for PW APS and the value CV is assumed for continuous connectivity check on PWs.
Detection Packet Period (ms)
3.3 10 20 50 100 200 500
50
l Specifies the period of detection packets. l This parameter is configurable when Detection Packet Type is FFD and assumes the fixed value of 1000 when Detection Packet Type is CV. l Set this parameter to 3.3 for PW APS.
LSR ID to be Received PW ID to be Received
Specifies the LSR ID to be received. Specifies the PW ID to be received.
B-178
Issue 03 (2011-04-10)
Protection Group Parameters (Slave Protection Pair)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to Slave Protection Pair.
Parameter Protection Mode Protection Group ID
Value Range -
Default Value -
Description Displays the protection mode. Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Parameters of QinQ Links

Parameter New Value Range Selected Deselected Default Value Description If you select New, create a QinQ link for carrying a QinQ-based E-Line service. If you select New, select a QinQ link that has already been created for carrying a QinQ-based E-Line service. l This parameter displays the source end of a QinQ-based ELine service. l This parameter is valid only if Direction is set to NNI-NNI. Sink This parameter displays the sink end of a QinQbased E-Line service.
Use existing resource
Selected Deselected
Source
Issue 03 (2011-04-10)
B-179
Parameter QinQ Link ID
Value Range 1-4294967295
Default Value -
Description l This parameter specifies the ID of a QinQ link. l This parameter is valid only if you select New.
NOTE The OptiX RTN 950 supports 1024 QinQ links, whose IDs must be different from each other.
Board Port
l This parameter specifies the board and port for carrying a QinQ link. l This parameter is valid only if you select New.
S-Vlan ID
1-4094
l This parameter specifies the S-VLAN ID for a QinQ link. l Set this parameter according to the network planning information. l This parameter is valid only if you select New.
Related Tasks
A.6.3.2 Configuring UNI-UNI E-Line Services A.6.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links) A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)
B.6.1.2 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
B-180
Issue 03 (2011-04-10)

Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter indicates the ID of the E-Line service. This parameter indicates or specifies the name of the E-Line service. This parameter indicates the source node. This parameter indicates the sink node. The OptiX RTN 950 does not support this parameter. This parameter cannot be queried here. This parameter indicates the transparent transmission tag of the bridge protocol data unit (BPDU) packets. This parameter is used to indicate whether the Ethernet line transparently transmits the BPDU packets.
Service Name
Source Node Sink Node Service Tag Role
MTU(byte) BPDU
Not Transparently Transmitted Transparently Transmitted
Parameters Associated with UNI Ports

Parameter Port Value Range Default Value Description This parameter indicates the UNI port.
Issue 03 (2011-04-10)
B-181
Parameter VLANs
Default Value -
Description This parameter indicates or specifies the VLAN ID of the UNI port. l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. l If this parameter is set to null, all the services of the UNI work as the service source or service sink. l If this parameter is not set to null, only the services of the UNI port whose VLAN IDs are included in the set value of this parameter work as the service source or service sink.
NNI Parameters (PW)

Parameter PW ID Working Status Value Range Default Value Description This parameter displays the PW ID. This parameter displays the working status of a PW.
Issue 03 (2011-04-10)
B-182
Parameter Enable Status PW Signaling Type
Value Range -
Default Value -
Description This parameter displays whether a PW is enabled. This parameter displays the PW signaling type.
NOTE The OptiX RTN 950 uses static PWs only.
PW Type PW Direction PW Encapsulation Type
This parameter displays the configured PW type. This parameter displays the direction of the PW. This parameter displays the PW encapsulation type.
NOTE The OptiX RTN 950 uses MPLS only.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Type
This parameter displays the configured PW ingress label. This parameter displays the configured PW egress label. This parameter displays the type of the tunnel that carries a PW. This parameter displays the opposite LSR ID. This parameter displays the ingress tunnel. This parameter displays the egress tunnel. For ETH PWE3 services, the parameter value is always No Use. This parameter displays the control channel type. This parameter displays the VCCV mode.
MPLS
MPLS
Peer LSR ID Ingress Tunnel Egress Tunnel Control Word
Control Channel Type VCCV Verification Mode
Issue 03 (2011-04-10)
B-183
Parameter Local Working Status
Value Range -
Default Value -
Description Displays the working status of the PW at the local end. This parameter displays the working status of the PW at the remote end. This parameter displays the comprehensive working status of the PW. This parameter displays the request VLAN. This parameter displays the deployment status. This parameter displays the automatic tunnel selection policy. The OptiX RTN 950 does not support request VLAN TPID of the PW level.
Remote Working Status
Compositive Working Status Request VLAN Deployment Status Tunnel Automatic Selection Policy TPID
Parameters Associated with QinQ Links

Parameter QinQ Link ID Value Range 1 to 4294967295 Default Value Description l This parameter indicates the QinQ link ID of the QinQ link connected to the NNI port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service.
B-184
Issue 03 (2011-04-10)
Parameter Port
Value Range -
Default Value -
Description l This parameter indicates the NNI port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service.
S-VLAN ID
l This parameter indicates or specifies the VLAN ID of the NNI port. l This parameter is valid only when Direction is set to UNI-NNI or NNI-NNI in the process of creating an E-Line service. l This parameter is preset in QinQ Link.
QoS Parameters
Parameter PW ID Direction Value Range Default Value Description This parameter displays the PW ID. l This parameter displays the direction of the PW. l Egress indicates the egress direction of the PW. l Ingress indicates the ingress direction of the PW.
Issue 03 (2011-04-10)
B-185
Value Range -
Default Value -
Description This parameter displays or specifies whether the bandwidth limit function is enabled for a PW to prevent network congestion. l Regarding transmission channels, this function can be used to limit the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
Policy
The OptiX RTN 950 does not support this parameter. This parameter displays or specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
CIR (Kbit/s)
CBS (kbyte)
This parameter displays or specifies the committed burst size (CBS) of a PW. This parameter displays or specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR.
PIR (kbit/s)
PBS (kbyte)
This parameter displays or specifies the peak burst size (PBS) of a PW.
B-186
Issue 03 (2011-04-10)
Parameter EXP
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
LSP Mode
Pipe
Pipe
Parameters for the Port Attributes

Parameter Port Enable Port Value Range Default Value Description Displays the port information. l This parameter indicates whether to enable the port. l This parameter is preset in General Attributes of Ethernet Interface.
Issue 03 (2011-04-10)
B-187
Default Value -
Description l This parameter indicates the encapsulation type of the port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. l If this parameter is set to Null, the port transparently transmits the received packets. l If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. l If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard. l This parameter is preset in General Attributes of Ethernet Interface.
TAG
l This parameter displays the tag of the port. l This parameter is preset in Layer 2 Attributes of Ethernet Interface .

NOTE
The following parameters are available only after the PW APS protection group is configured.
B-188
Issue 03 (2011-04-10)
Parameter Protection Group ID
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the protection mode. l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Working PW ID Protection PW ID Protection Mode Enabling Status
Enabled Disabled
Switchover Mode

NOTE The OptiX RTN 950 supporting dual-ended switching.
Restoration Mode
l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
Issue 03 (2011-04-10)
B-189
Parameter WTR Time(min)
Value Range 1 to 12
Default Value -
Description l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
Hold-off Time(100ms)
0 to 100
l Displays or specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered.
Switchover Status
Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.
Protocol Status Working Path Status Protection Path Status

NOTE
The following parameters are available only after the slave protection pair is configured.
B-190
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair. Displays the PW type.
Working PW ID
Protection PW ID
PW Type
B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation

This topic describes the parameters that are used for creating VLAN forwarding table items.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the VLAN Forwarding Table Item tab. Click New.
Parameters for VLAN Forwarding Table Item

Parameter Source Interface Type Value Range V-UNI Default Value V-UNI Description This parameter specifies the network attribute of the source interface. This parameter specifies the source interface. This parameter specifies the VLAN ID of the source service. This parameter specifies the network attribute of the sink interface.
Source Interface Source VLAN ID
1 to 4094
Sink Interface Type
V-UNI
V-UNI
Issue 03 (2011-04-10)
B-191
Parameter Sink Interface Sink VLAN ID
Default Value -
Description This parameter specifies the sink interface. This parameter specifies the VLAN ID of the sink service.
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in Sink VLAN ID when the service is transmitted from Sink Interface. l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the other VLAN forwarding table item is configured reversely. l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of VLAN IDs.
Related Tasks
A.6.3.6 Creating a VLAN Forwarding Table Item

This topic describes the parameters that are used for creating an Ethernet local area network (ELAN) service.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Click Create.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Parameter Service ID Value Range 1 to 4294967294 Default Value Description l This parameter specifies the ID of the E-LAN service. l The OptiX RTN 950 supports simultaneous creation of an E-LAN service only. Service Name This parameter specifies the name of the E-LAN service.
B-192
Issue 03 (2011-04-10)
Parameter BPDU
Value Range -
Default Value -
Description l This parameter indicates the transparent transmission tag of the BPDU packets. l In the case of an ELAN service, this parameter supports only Not Transparently Transmitted and cannot be set manually. l Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
Issue 03 (2011-04-10)
B-193
Parameter Tag Type
Value Range C-Awared S-Awared Tag-Transparent
Default Value C-Awared
Description l C-Awared indicates that the packets are learnt according to CTag (the VLAN tag on the client-side). To create the 802.1q bridge, set this parameter to CAwared. l S-Awared indicates that the packets are learnt according to STag (the VLAN tag at the carrier service layer). To create the 802.1ad bridge, set this parameter to SAwared. l Tag-Transparent indicates that the packets are transparently transmitted. To create the 802.1d bridge, set this parameter to TagTransparent. l This parameter is set according to the planning information.
B-194
Issue 03 (2011-04-10)
Parameter Self-Learning MAC Address
Description l This parameter specifies whether to enable the MAC address self-learning function. l If the MAC selflearning function of an Ethernet LAN is enabled, the Ethernet LAN learns an MAC address according to the original MAC address in the packet and automatically refreshes the MAC address forwarding table. l If the MAC selflearning function of an Ethernet LAN is disabled, a static MAC address forwarding table is recommended to be configured.
MAC Address Learning Mode
IVL SVL
l This parameter indicates the mode used to learn an MAC address. l When the bridge uses the SVL mode, all the VLANs share one MAC address table. If the bridge uses the IVL mode, each VLAN has an MAC address table.
Port
This parameter displays the port name.
Issue 03 (2011-04-10)
B-195
Parameter Port Type
Value Range -
Default Value -
Description This parameter displays the port type. l When the parameter value is UNI, the port connected to the bridge is a UNI port. That is, this port functions as the UNI port connected to the IEEE 802.1d bridge or IEEE 802.1q bridge. l When the parameter value is NNI, the port connected to the bridge is an NNI port. That is, this port functions as the NNI port connected to the IEEE 802.1ad bridge. l When the parameter value is UNI (PORT +S-VLAN), a specific S-VLAN ID is added to all the traffic flows that are received by the UNI port connected to the IEEE 802.1ad bridge. l When the parameter value is UNI (PORT +C-VLAN+SVLAN), a specific SVLAN ID is added to all the traffic flows that are received by the UNI port connected to the IEEE 802.1ad bridge and contain the specific C-VLAN ID.
B-196
Issue 03 (2011-04-10)
Parameter VLAN
Default Value -
Description l This parameter is valid only when Tag Type is set to C-Awared and Tag is set to Access or Hybrid. l When the parameter value is null, it indicates that the entire physical port is connected to the bridge. l You need to set this parameter according to the planning information.
Issue 03 (2011-04-10)
B-197
Parameter C-VLAN
Default Value -
Description l This parameter is valid only when Tag Type is set to S-Awared. l This parameter specifies the VLAN ID of the UNI port. l You may set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l When the parameter value is null, the ELAN service exclusively occupies the corresponding UNI port; that is, the entire physical UNI port is connected to the bridge. l When the parameter value is not null, a specific S-VLAN ID is added to only the traffic flows that are received by the UNI port and contain this VLAN ID.
B-198
Issue 03 (2011-04-10)
Parameter S-VLAN
Default Value -
Description l This parameter is valid only when Tag Type is set to S-Awared. l This parameter specifies the S-VLAN ID that needs to be added to traffic flows received by the UNI port or the S-VLAN ID that the NNI port can identify. l You need to set this parameter according to the planning information.
Enable Port
l This parameter displays whether the port is enabled. l Ethernet services can be received, processed, and forwarded normally only if Enable Port is set to Enabled. l Enable Port is already set in Ethernet Interface.
Issue 03 (2011-04-10)
B-199
B-200
Issue 03 (2011-04-10)
Default Value -
Description l This parameter specifies the method of the port to process the received packets. l If you set this parameter to Null, the port transparently transmits the received packets. l If you set this parameter to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set this parameter to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
Tag
Tag Aware
l If all the accessed services are frames with the VLAN tag (tagged frames), this parameter is set to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), this parameter is set to Access. l If the accessed services contain tagged frames and untagged frames, this parameter is set to Hybrid.
Default VLAN
1 to 4094
l Default VLAN ID is valid only when TAG is set to Access or Hybrid. l Default VLAN ID is set according to the actual situations.
Issue 03 (2011-04-10)
B-201
Parameters on the Main Interface (Setting Service Parameters)

Parameter Split Horizon Group Value Range Selected Deselected Split Horizon Group ID Default Value Deselected Description This parameter specifies whether to create a split horizon group. l This parameter displays the ID of the split horizon group. l The ID of the split horizon group is 1 by default and cannot be specified manually. Split Horizon Group Member l A split horizon group member indicates the logical port member in the split horizon group. l The port members that are added to the same split horizon group cannot communicate with each other. l The OptiX RTN 950 supports only the division of the split horizon group members according to the Ethernet physical port. l If a UNI or NNI logical port of the 802.1ad bridge is added to a split horizon group member, the physical port that is mounted with the logical port is automatically added to the split horizon group member.
Related Tasks
A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services
B-202
Issue 03 (2011-04-10)

This topic describes the parameters that are related to E-LAN services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree.

Parameter Service ID Value Range 1 to 4294967294 Default Value Description l This parameter indicates the ID of the E-LAN service. l The supports simultaneous creation of an E-LAN service only. Service Name This parameter specifies the name of the E-LAN service. l This parameter indicates the transparent transmission tag of the BPDU packets. l In the case of an ELAN service, this parameter supports only Not Transparently Transmitted and cannot be set manually. l Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
BPDU
Issue 03 (2011-04-10)
B-203
Parameter Tag Type
Value Range C-Awared S-Awared Tag-Transparent
Default Value C-Awared
Description l C-Awared indicates that the packets are learnt according to CTag (the VLAN tag on the client-side). To create the 802.1q bridge, set this parameter to CAwared. l S-Awared indicates that the packets are learnt according to STag (the VLAN tag at the carrier service layer). To create the 802.1ad bridge, set this parameter to SAwared. l Tag-Transparent indicates that the packets are transparently transmitted. To create the 802.1d bridge, set this parameter to TagTransparent.
B-204
Issue 03 (2011-04-10)
Parameter Self-Learning MAC Address
Value Range Enabled
Description l This parameter indicates whether to enable the MAC address self-learning function. l If the MAC selflearning function of an Ethernet LAN is enabled, the Ethernet LAN learns an MAC address according to the original MAC address in the packet and automatically refreshes the MAC address forwarding table. l If the MAC selflearning function of an Ethernet LAN is disabled, a static MAC address forwarding table is recommended to be configured.
MAC Address Learning Mode
l This parameter indicates the mode used to learn an MAC address. l When the bridge uses the SVL mode, all the VLANs share one MAC address table. If the bridge uses the IVL mode, each VLAN has an MAC address table.
Port Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port name.
Issue 03 (2011-04-10)
B-205
Parameter Port Type
Value Range -
Default Value -
Description This parameter displays the port type. l When the parameter value is UNI, the port connected to the bridge is a UNI port. That is, this port functions as the UNI port connected to the IEEE 802.1d bridge or IEEE 802.1q bridge. l If the parameter value is NNI, the port connected to the bridge is an NNI port. That is, this port functions as the NNI port connected to the IEEE 802.1ad bridge. l If the parameter value is UNI (PORT+SVLAN), a specified SVLAN ID is added to all the traffic flows received by the UNI port connected to the IEEE 802.1ad bridge. l If the parameter value is UNI (PORT+CVLAN+S-VLAN), a specific S-VLAN ID is added to all the traffic flows that are received by the UNI port connected to the IEEE 802.1ad bridge and contain the specific CVLAN ID.
VLAN C-VLAN S-VLAN
This parameter displays the VLAN ID. This parameter displays the C-VLAN ID. This parameter displays the S-VLAN ID.
B-206
Issue 03 (2011-04-10)
Parameter Enable Port
Value Range -
Default Value -
Description l This parameter displays whether the port is enabled. l Ethernet services can be received, processed, and forwarded normally only if Enable Port is set to Enabled. l Enable Port is already set in Ethernet Interface.
Issue 03 (2011-04-10)
B-207
B-208
Issue 03 (2011-04-10)
Default Value -
Description l This parameter specifies the method of the port to process the received packets. l If you set this parameter to Null, the port transparently transmits the received packets. l If you set this parameter to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set this parameter to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
Tag
Tag Aware
l If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to "Tag Aware". l If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to "Access". l If the accessed services contain tagged frames and untagged frames, set this parameter to "Hybrid".
Default VLAN ID
1 to 4094
l Default VLAN ID is valid only when Tag is set to Access or Hybrid. l Default VLAN ID is set according to the actual situations.
Issue 03 (2011-04-10)
B-209
Parameters for Static MAC Addresses

Parameter VLAN ID Value Range Default Value Description l This parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset static MAC address entries are valid for all VLANs. l If MAC Address Learning Mode is set to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l This parameter is set according to the planning information. MAC Address l This parameter indicates or specifies the static MAC address. l A static MAC address is an address that is set manually. It is not aged automatically and needs to be deleted manually. l Generally, a static MAC address is used for the port that receives but does not forward Ethernet service packets or the port whose MAC address need not be aged automatically. Egress Interface l This parameter specifies the Ethernet port that corresponds to the MAC address. l This parameter is set according to the planning information.
B-210
Issue 03 (2011-04-10)
Parameters for Self-Learning MAC Address

Parameter VLAN ID Value Range Default Value Description l This parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset self-learning MAC address entries are valid for all VLANs. l If MAC Address Learning Mode is set to IVL, the preset selflearning MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l This parameter is set according to the planning information. MAC Address l This parameter indicates or specifies the self-learning MAC address. A selflearning MAC address is also called a dynamic MAC address. l A self-learning MAC address is an entry obtained by a bridge in SVL or IVL learning mode. A self-learning MAC address can be aged. Egress Interface l This parameter specifies the Ethernet port that corresponds to the MAC address. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-211
Parameters Associated with MAC Address Learning

Parameter Aging Ability Value Range Enabled Disabled Aging Time(min) 1 to 65535 5 Default Value Enabled Description The OptiX RTN 950 supports enabling/ disabling of the aging function and aging time for the MAC address table. If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time. The aging time of a MAC address table is 5 minutes by default.
Parameters for Disabled MAC Addresses

Parameter VLAN ID Value Range Default Value Description This parameter indicates or specifies the VLAN ID of the service. A disabled MAC address is valid for the VLAN whose VLAN ID is equal to the preset VLAN ID.
B-212
Issue 03 (2011-04-10)
Parameter MAC Address
Value Range -
Default Value -
Description l This parameter specifies or indicates the disabled MAC address. A disabled MAC address is also called a blacklisted MAC address. l This parameter is used for discarding an entry, also called a black hole entry, whose data frame that contains a specific destination MAC address. A disabled MAC address needs to be set manually and cannot be aged.
Parameters for the Split Horizon Group

Parameter Split Horizon Group ID Value Range Default Value 1 Description l This parameter indicates the ID of the split horizon group. l The default split horizon group ID is 1 and cannot be set manually.
Issue 03 (2011-04-10)
B-213
Parameter Split Horizon Group Member
Value Range -
Default Value -
Description l A split horizon group member indicates the logical port member in the split horizon group. l The port members that are added to different split horizon groups cannot communicate with each other. l The supports only the division of the split horizon group members according to the Ethernet physical port. l If a UNI or NNI logical port of the 802.1ad bridge is added to a split horizon group member, the physical port that is mounted with the logical port is automatically added to the split horizon group member.
Parameters for Unknown Frame Processing

Parameter Frame Type Value Range Unicast Multicast Handing Mode Discard Broadcast Broadcast Default Value Description This parameter indicates the type of the received unknown frame. Selects the method of processing the unknown frame. If this parameter is set to Discard, the unknown frame is directly discarded. If this parameter is set to Broadcast, the unknown frame is broadcast at the forwarding port.
B-214
Issue 03 (2011-04-10)
Related Tasks
A.6.4.1 Creating a Static MAC Address Entry A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.4.4 Querying or Deleting a Dynamic MAC Address A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
B.6.1.6 Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Click New.
Parameters for the General Attributes

Parameter QinQ Link ID Value Range 1 to 4294967295 Default Value Description This parameter specifies the ID of the QinQ link.
NOTE The OptiX RTN 950 supports 1024 QinQ links, whose IDs must be different from each other.
Board
This parameter specifies the board where the QinQ link is located. This parameter specifies the port where the QinQ link is located. l This parameter specifies the VLAN ID (at the network operator side) for the QinQ link. l This parameter is set according to the planning information.
Port
S-Vlan ID
1 to 4094
Related Tasks
A.6.3.1 Configuring the QinQ Link
B.6.2 Parameters for Ethernet Protocols

This topic describes the parameters that are related to the Ethernet protocol. B.6.2.1 Parameter Description: ERPS Management_Creation This topic describes the parameters that are used for creating ERPS management tasks. B.6.2.2 Parameter Description: ERPS Management This topic describes the parameters that are used for Ethernet ring protection switching (ERPS) management. B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation This topic describes the parameters that are used for creating MSTP port groups. B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration This topic describes the parameters that are used for creating MSTP port groups. B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters This topic describes the parameters that are related to MSTP bridges. B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters This topic describes the parameters that are related to the MSTP CIST. B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST This topic describes the parameters that are related to the running information about the MSTP CIST. B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation This topic describes the parameters that are used for creating a link aggregation group (LAG). B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation This section describes the parameters for port priorities and system priorities. B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT This topic describes the parameters that are related to point-to-point LPT. B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT This topic describes the parameters that are related to creating point-to-point LPT. B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT This topic describes the parameters that are related to point-to-multipoint LPT. B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT This topic describes the parameters that are related to creating point-to-multipoint LPT.
B.6.2.1 Parameter Description: ERPS Management_Creation

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management. Click New.
B-216
Issue 03 (2011-04-10)
Parameters
Parameter ERPS ID Value Range 1 to 8 Default Value Description l This parameter specifies the ID of the Ethernet ring protection switching (ERPS) instance. l The IDs of ERPS instances on an NE must be different from each other. East Port This parameter specifies the east port of the ERPS instance. This parameter specifies the west port of the ERPS instance. l This parameter specifies whether the node on the ring is the ring protection link (RPL) owner. l Only one node on the ring can be set as the RPL owner for each Ethernet ring. RPL Port l This parameter specifies the RPL port. l There is only one RPL port and this RPL port must be the east or west port on the RPL owner node.
West Port
RPL Owner Ring Node Flag
Yes No
No
Issue 03 (2011-04-10)
B-217
Parameter Control VLAN
Default Value -
Description l This parameter specifies the VLAN ID of Control VLAN. l Each node on the Ethernet ring transmits the R-APS packets on the dedicated ring APS (R-APS) channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN cannot be duplicate with the VLAN IDs that are contained in the service packets. l The Control VLAN must be set to the same value for all the NEs on an ERPS ring.
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01
This parameter indicates the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01.
Related Tasks
A.6.1.1 Creating Ethernet Ring Protection Instances

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS) management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree.
Parameters
Parameter ERPS ID Value Range 1 to 8 Default Value Description This parameter indicates the ID of the ERPS instance. This parameter indicates the east port of the ERPS instance. This parameter indicates the west port of the ERPS instance. This parameter indicates whether a node on the ring is the ring protection link (RPL) owner. This parameter indicates the RPL port. l This parameter indicates or specifies the VLAN ID of Control VLAN. l Each node on the Ethernet ring transmits the R-APS packets on the dedicated ring APS (R-APS) channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN cannot be duplicate with the VLAN IDs that are contained in the service packets or inband DCN packets. l The Control VLAN must be set to the same value for all the NEs on an ERPS ring.
East Port
West Port
RPL Owner Ring Node Flag
Yes No
RPL Port Control VLAN
1 to 4094
Issue 03 (2011-04-10)
B-219
Parameter Destination Node
Value Range 01-19-A7-00-00-01
Default Value -
Description This parameter indicates the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01. l This parameter indicates or specifies the hold-off time of the ERPS hold-off timer. l The hold-off timer is used for negotiating the protection switching sequence when the ERPS coexists with other protection schemes so that the fault can be rectified in the case of other protection switching (such as LAG protection) before the ERPS occurs. When a node on the ring detects one or more new faults, it starts up the hold-off timer if the preset hold-off time is set to a value that is not 0. During the hold-off time, the fault is not reported to trigger an ERPS. When the holdoff timer times out, the node checks the link status regardless whether the fault that triggers the startup of the timer exists. If the fault exists, the node reports it to trigger an ERPS. This fault can be the same as or different from the fault that triggers the initial startup of the hold-off timer.
Hold-Off Time(ms)
0 to 10000, in step of 100
B-220
Issue 03 (2011-04-10)
Parameter Guard Time(ms)
Value Range 10 to 2000, in step of 10
Default Value 500
Description l This parameter indicates or specifies the guard time of the ERPS guard timer. l The nodes on the ring continuously forward the R-APS packets to the Ethernet ring. As a result, the outdated RAPS packets may exist on the ring network. After a node on the ring receives the outdated R-APS packets, an incorrect ERPS may occur. The ERPS guard timer is an R-APS timer used for preventing a node on the ring from receiving outdated R-APS packets. When a faulty node on the ring detects that the switching condition is cleared, the node starts up the guard timer and starts to forward the RAPS (NR) packets. During this period, the R-APS packets received by the node are discarded. The received R-APS packets are forwarded only after the time of the guard timer expires.
Issue 03 (2011-04-10)
B-221
Parameter WTR Time(mm:ss)
Default Value 5
Description l This parameter indicates or specifies the WTR time of the WRT timer in the case of ERPS protection. l The WTR time refers to the duration from the time when the working channel is restored to the time when the switching is released. When the working channel is restored, the WTR timer of the RPL owner starts up. In addition, a signal that indicates the operation of the WTR timer is continuously output in the timing process. When the WTR timer times out and no switching request of a higher priority is received, the signal indicating the operation of the WTR timer is not transmitted. In addition, the WTR release signal is continuously output. l The WTR timer is used to prevent frequent switching caused by the unstable working channel.
Packet Transmit Interval(s)
1 to 10
This parameter displays or specifies the interval for sending R-APS packets periodically. This parameter indicates or specifies the level of the maintenance entity. This parameter indicates the last switching request.
Entity Level
0 to 7
Last Switching Request
B-222
Issue 03 (2011-04-10)
Parameter RB Status
Value Range -
Default Value -
Description This parameter indicates the RB (RPL Blocked) status of the packets received by the working node. l noRB: The RPL is not blocked. l RB: The RPL is blocked.
DNF Status
This parameter indicates the DNF status of the packets received by the working node. l noDNF: The R-APS packets do not contain the DNF flag. In this case, the packets are forwarded by the node that detects the fault on a non-RPL link, and the node that receives the packets is requested to clear the forwarding address table. l DNF: The R-APS packets contain the DNF flags. In this case, the packets are forwarded by the node that detects the fault on an RPL link, and the node that receives the packets is informed not to clear the forwarding address table.
Issue 03 (2011-04-10)
B-223
Parameter State Machine Status
Value Range -
Default Value -
Description This parameter indicates the status of the state machine at the working node. l Idle: The Ethernet ring is in normal state. For example, no node on the Ethernet ring detects any faults or receives the R_APS (NR, RB) packets. l Protection: The Ethernet ring is in protected state. For example, a fault on the node triggers the ERPS, or a node on the ring is in the WTR period after the fault is rectified.
Node Carried with Current Packet
This parameter indicates the MAC address carried in the R-APS packets received by the current node. The MAC address refers to the MAC address of the source node that initiates the switching request. Displays the status of the east port. Displays the status of the west port.
East Port Status West Port Status
Related Tasks
A.6.1.2 Setting the Parameters of Ethernet Ring Protocol A.6.1.3 Querying the Status of the Ethernet Ring Protocol
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
B-224
Issue 03 (2011-04-10)
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Port Group Parameters tab. Click Create.

Parameter Protocol Type Value Range MSTP STP Default Value MSTP Description This parameter specifies the protocol type. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 950 supports the CIST MSTP only. l STP: stands for Spanning Tree Protocol. Enable Protocol Enabled Disabled Disabled l This parameter specifies whether to enable the protocol of the port group or a member port in the port group. l If the STP or MSTP is enabled, the spanning tree topology is automatically reconfigured. As a result, the services are interrupted.
Parameters for Application Ports

Parameter Board Value Range Default Value Description This parameter specifies the board where the member of port group is located. This parameter indicates the available port list in which a port can be added to the port group.
B-225
Available Port List
Issue 03 (2011-04-10)
Parameter Selected Port List
Value Range -
Default Value -
Description This parameter indicates the selected ports that can be added to the port group.
Related Tasks
A.6.6.1 Creating the MSTP Port Group
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Port Group Parameters tab. On the main interface, select the port group to be configured. Click Config. The Config Port Group dialog box is displayed.
Parameters for the Added Port

Parameter Board Value Range Default Value Description This parameter specifies the board where the member of port group is located. This parameter indicates the available port list in which a port needs to be added to the port group. This parameter indicates the selected ports that need to be added to the port group.
Available Port List
Selected Port List
Related Tasks
A.6.6.7 Modifying the Configuration Data of the MSTP Port Group
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Bridge Parameters tab.

Parameter Port Group ID Value Range Default Value Description l This parameter indicates the ID of the port group. l This parameter can be set to only the port group ID that is automatically allocated. MST Domain Name The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Redaction Level
Mapping List
Bridge Parameters
Parameter Port Group ID Value Range Default Value Description l This parameter indicates the ID of the port group. l This parameter can be set to only the port Group ID that is automatically allocated. MST Domain Max Hop Count 20 Specifies the maximum hop count of the MSTP.
Issue 03 (2011-04-10)
B-227
Parameter Network Diameter
Value Range 2 to 7
Default Value 7
Description l This parameter specifies the MSTP network diameter. l Network Diameter is related to the link whose number of switches is the most and is indicated by the number of switches that are connected to the link. When you set Network Diameter for the switches, the MSTP automatically sets Max Age(s), Hello Time(s), and Forward Delay(s) to the more appropriate values for the switches. l If the value of Network Diameter is greater, the network is in a larger scale.
Hello Time(s)
1 to 10
l This parameter specifies the interval for transmitting the CBPDU packets through the bridge. l The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.
B-228
Issue 03 (2011-04-10)
Parameter Max Age(s)
Value Range 6 to 40
Default Value 20
Description l This parameter specifies the maximum age of the CBPDU packet that is recorded by the port. l The greater the value, the longer the transmission distance of the CBPDU, which indicates that the network diameter is greater. When the value of this parameter is greater, it is less possible that the bridge detects the link fault in a timely manner and thus the network adaptation ability is reduced.
Forward Delay(s)
4 to 30
15
l This parameter specifies the holdoff time of a port in the listening state and in the learning state. l The greater the value, the longer the delay of the network state change. Hence, the topology changes are slower and the recovery in the case of faults is slower.
Port Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port in the port group.
Issue 03 (2011-04-10)
B-229
Parameter Enable Edge Attribute
Description l This parameter specifies the management edge attributes of the port. l This parameter specifies whether to set the port as an edge port. The edge port refers to the bridge port that is connected to the LAN. In normal cases, this port does not receive or transmit BPDU messages. l This parameter can be set to Enabled only when the port is directly connected to the data communications terminal equipment, such as a computer. In other cases, it is recommended that you use the default value.
Actual Edge Attribute
This parameter indicates the actual management edge attributes of the port.
B-230
Issue 03 (2011-04-10)
Parameter Point-to-Point Attribute
Value Range false true auto
Default Value auto
Description l This parameter specifies the point-topoint attribute of the port. l false: forced nonpoint-to-point link attribute l true: forced point-topoint link attribute l auto: automatically detected point-topoint link attribute l If this parameter is set to auto, the bridge determines Actual Point-to-Point Attribute of the port according to the actual working mode. If the actual working mode is full-duplex, the actual point-to-point attribute is true. If the actual working mode is half-duplex, Actual Point-to-Point Attribute is false. l Only the designated port whose Actual Point-to-Point Attribute is "True" can transmit the rapid state migration request and response. l It is recommended that you use the default value.
Actual Point-to-Point Attribute
This parameter indicates the actual point-to-point attribute of the port.
Issue 03 (2011-04-10)
B-231
Parameter Max Transmit Packet Count
Default Value 3
Description l This parameter specifies the maximum number of packets to be transmitted. l The maximum number of packets to be transmitted by the port refers to the maximum number of MSTP packets that the port can transmit within 1s. l This parameter needs to be set according to the planning information.
Related Tasks
A.6.6.2 Setting the Bridge Parameters of the MSTP
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the CIST&MSTI Parameters tab.

Parameter Port Group MSTI ID Value Range 0 Default Value 0 Description This parameter specifies the port group. This parameter indicates the MSTI ID. The value 0 indicates common and internal spanning tree (CIST). The OptiX RTN 950 supports only the MSTP that uses CIST.
B-232
Issue 03 (2011-04-10)
Parameter Bridge Priority
Default Value 32768
Description l The most significant 16 bits of the bridge ID indicate the priority of the bridge. l When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. l If the priorities of all the bridges in the STP/ MSTP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
Port Parameters
Parameter Port Priority Value Range 0 to 240, in step of 16 Default Value 128 Description This parameter indicates the port in the port group. l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher. Path Cost 1 to 200000000 200000 l This parameter indicates the status of the network that the port is connected to. l In the case of the bridges on both ends of the path, set this parameter to the same value.
Related Tasks
A.6.6.3 Setting the Parameters of the CIST
Issue 03 (2011-04-10)
B-233
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST

This topic describes the parameters that are related to the running information about the MSTP CIST.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the CIST Running Information tab.

Parameter Port Group ID Protocol Running Mode Value Range MSTP STP Default Value Description This parameter indicates the ID of the port group. l This parameter indicates the running mode of the protocol. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 950 supports only the CIST-based MSTP. l STP: stands for Spanning Tree Protocol.
B-234
Issue 03 (2011-04-10)
Parameter Bridge Priority
Default Value 32768
Description l This parameter indicates the priority of the bridge. l The most significant 16 bits of the bridge ID indicate the priority of the bridge. l When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. l If the priorities of all the bridges in the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
Bridge MAC Address
This parameter indicates the MAC address of the bridge. This parameter indicates the priority of the root bridge. This parameter indicates the MAC address of the root bridge. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Root Bridge Priority
0 to 61440, in step of 4096
32768
Root Bridge MAC Address External Path Cost ERPC Domain Root Bridge Priority Domain Root Bridge MAC Address Internal Path Cost IRPC
Issue 03 (2011-04-10)
B-235
Parameter Root Port Priority
Default Value 128
Description l This parameter indicates the priority of the root port. l The most significant eight bits of the ID of the root port indicate the priority of the root port. l When the value is smaller, the priority is higher.
Root Port Hello Time(s)
This parameter indicates the root port. l This parameter indicates the interval for transmitting CBPDU packets through the bridge. l The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.
Max Age(s)
6 to 40
20
l This parameter specifies the maximum age of the CBPDU packet that is recorded by the port. l The greater the value, the longer the transmission distance of the CBPDU, which indicates that the network diameter is greater. When the value of this parameter is greater, it is less possible that the bridge detects the link fault in a timely manner and thus the network adaptation ability is reduced.
B-236
Issue 03 (2011-04-10)
Parameter Forward Delay(s)
Value Range 4 to 30
Default Value 15
Description l This parameter specifies the holdoff time of a port in the listening state and in the learning state. l The greater the value, the longer the delay of the network state change. Hence, the topology changes are slower and the recovery in the case of faults is slower.
MST Domain Max Hop Count Topology Change Count
The OptiX RTN 950 does not support this parameter. This parameter indicates the identifier of the topology change. This parameter indicates the duration of the last topology change. This parameter indicates the count of the topology changes.
Last Topology Change Time(s) Topology Change Count
Port Parameters
Parameter Port Enable Protocol Value Range Enabled Disabled Default Value Disabled Description This parameter indicates the port in the port group. This parameter indicates whether the protocol of the port group or a member of the port group is enabled. This parameter indicates the role of a port.
Port Role
Disabled
Issue 03 (2011-04-10)
B-237
Parameter Port Status
Value Range Discarding Learning Forwarding
Default Value Discarding
Description This parameter indicates the state of a port. l Discarding: receives only BPDU packets l Learning: only receives or transmits BPDU packets l Forwarding: forwards user traffic, and transmits/receives BPDU packets
Priority
0 to 240, in step of 16
128
l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher.
Path Cost
1 to 200000000
200000
l This parameter indicates the status of the network that the port is connected to. l In the case of the bridges on both ends of the path, set this parameter to the same value.
Bridge Priority
0 to 61440, in step of 4096
32768
l The most significant 16 bits of the bridge ID indicate the priority of the bridge. l When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. l If the priorities of all the bridges in the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
B-238
Issue 03 (2011-04-10)
Parameter Bridge MAC Address
Value Range -
Default Value -
Description This parameter indicates the MAC address of the bridge. l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher.
Designated Port Priority
0 to 240, in step of 16
Design Port Edge Port Attribute
Disabled Enabled
0 Disabled
This parameter indicates the designated port. l This parameter specifies the management edge attributes of the port. l This parameter specifies whether to set the port as an edge port. The edge port refers to the bridge port that is connected to the LAN. In normal cases, this port does not receive or transmit BPDU messages. l This parameter can be set to Enabled only when the port is directly connected to the data communications terminal equipment, such as a computer. In other cases, it is recommended that you use the default value.
Actual Edge Port Attribute
Disabled
This parameter indicates the actual management edge attributes of the port.
Issue 03 (2011-04-10)
B-239
Parameter Point to Point
Value Range false true auto
Default Value auto
Description l This parameter specifies the point-topoint attribute of the port. l false: forced nonpoint-to-point link attribute l true: forced point-topoint link attribute l auto: automatically detected point-topoint link attribute l If this parameter is set to auto, the bridge determines Actual Point to Point Attribute of the port according to the actual working mode. If the actual working mode is full-duplex, the actual point-to-point attribute is true. If the actual working mode is half-duplex, Actual Point to Point Attribute is false. l Only the designated port whose Actual Point-to-Point Attribute is "True" can transmit the rapid state migration request and response. l It is recommended that you use the default value.
Actual Point to Point
This parameter indicates the actual point-to-point attribute of the port.
B-240
Issue 03 (2011-04-10)
Parameter Max Count of Transmitting Message
Default Value 3
Description l This parameter indicates the maximum number of packets to be transmitted. l The maximum number of packets to be transmitted by the port refers to the maximum number of MSTP packets that the port can transmit within 1s.
Protocol Running Mode
STP MSTP
l This parameter indicates the running mode of the protocol. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 950 supports only the CIST-based MSTP. l STP: stands for Spanning Tree Protocol.
Hello Time(s)
1 to 10
l This parameter indicates the interval for transmitting the CBPDU packets through the bridge. l The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.
Issue 03 (2011-04-10)
B-241
Parameter Max Age(s)
Value Range 6 to 40
Default Value 20
Description l This parameter specifies the maximum age of the CBPDU packet that is recorded by the port. l The greater the value, the longer the transmission distance of the CBPDU, which indicates that the network diameter is greater. When the value of this parameter is greater, it is less possible that the bridge detects the link fault in a timely manner and thus the network adaptation ability is reduced.
Forward Delay(s)
4 to 30
15
l This parameter specifies the holding time of a port in the listening state and in the learning state. l The greater the value, the longer the delay of the network state change. Hence, the topology changes are slower and the recovery in the case of faults is slower.
Remain Hop
Related Tasks
A.6.6.4 Querying the CIST Running Information
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation

This topic describes the parameters that are used for creating a link aggregation group (LAG).
B-242
Issue 03 (2011-04-10)
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Click the Link Aggregation Group Management tab. Click New.

Parameter LAG No. Value Range Default Value 1 Description l This parameter specifies the LAG number to be set manually. l This parameter is valid only when Automatically Assign is not selected. Automatically Assign Selected Deselected Selected l This parameter indicates whether LAG No. is allocated automatically. l When Automatically Assign is selected, LAG No. cannot be set. LAG Name This parameter specifies the LAG name.
Issue 03 (2011-04-10)
B-243
Parameter LAG Type
Value Range Static Manual
Default Value Static
Description l Static: You can create a LAG. When you add or delete a member port to or from the LAG, the Link Aggregation Control Protocol (LACP) protocol is required. In a LAG, a port can be in selected, standby, or unselected state. The aggregation information is exchanged among different equipment through the LACP protocol to ensure that the aggregation information is the same among all the nodes. l Manual: You can create a LAG. When you add or delete a member port, the LACP protocol is not required. The port can be in the up or down state. The system determines whether to aggregate a port according to its physical state (UP or DOWN), working mode, and rate.
B-244
Issue 03 (2011-04-10)
Value Range Revertive Mode Non-Revertive Mode
Default Value Non-Revertive Mode
Description l Revertive Mode can be set only when Load Sharing is set to NonSharing. l When Revertive Mode is set to Revertive Mode, the services are switched back to the former working channel after this channel is restored to normal. l When Revertive Mode is set to NonRevertive Mode, the status of the LAG does not change after the former working channel is restored to normal. That is, the services are still transmitted on the protection channel.
Issue 03 (2011-04-10)
B-245
Parameter Load Sharing
Value Range Sharing Non-Sharing
Default Value Non-Sharing
Description l Set Load Sharing to the same value as the peer equipment. It is recommended that you set Load Sharing to Non-Sharing at both ends if the LAGs are used for protection and set Load Sharing to Sharing at both ends if the LAGs are used for increasing bandwidths. l Sharing: Each member link of a LAG processes traffic at the same time and shares the traffic load. The sharing mode can increase a bandwidth utilization for the link. When the LAG members change, or certain links fail, the system automatically re-allocates the traffic. l Non-Sharing: Only one member link of a LAG carries traffic, and the other link is in the standby state. In this case, a hot backup mechanism is provided. When the active link of a LAG is faulty, the system activates the standby link, thus preventing link failure.
B-246
Issue 03 (2011-04-10)
Parameter System Priority
Default Value 32768
Description l System Priority indicates the priority of a LAG. The smaller the value of System Priority, the higher the priority. l When a local LAG negotiates with an opposite LAG through LACP packets, both LAGs can obtain the system priorities of each other. Then, the LAG of the higher system priority is considered as the comparison result of both LAGs so that the aggregation information is consistent at both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the comparison result based on the LAG with smaller system MAC address is considered as the result of both LAGs and is used to ensure that the aggregation information is consistent at both LAGs.
WTR Time(min)
1 to 30
10
l Specifies the WTR time for the LAG. l WTR Time(min) takes effect only when Revertive Mode is Revertive Mode.
Issue 03 (2011-04-10)
B-247
Parameter Switch LAG upon Air Interface SD
Description l This parameter specifies whether to enable the switching triggered by bit errors. l If Switch LAG upon Air Interface SD is set to Enabled, the MW_BER_SD alarm will trigger the LAG switching at the air interface.
Port Settings Parameters

Parameter Main Board Value Range Default Value Description l This parameter specifies the main board in a LAG. l This parameter is set according to the planning information. Main Port l This parameter specifies the main port in a LAG. l After a LAG is created, you can add Ethernet services to the main port only. Services cannot be added to a slave port. When Load Sharing is set to NonSharing, the link connected to the main port is used to transmit the services, and the link connected to the slave port is used for protection. Board (Available Slave Ports) l This parameter specifies the slave board in a LAG. l This parameter is set according to the planning information.
B-248
Issue 03 (2011-04-10)
Parameter Port (Available Slave Ports)
Value Range -
Default Value -
Description l This parameter specifies the salve port in a LAG. l The slave ports in a LAG are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the LAG.
Selected Standby Ports
This parameter indicates the selected slave ports.
Related Tasks

This section describes the parameters for port priorities and system priorities.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Click the Link Aggregation Parameters tab.

Parameter Port Value Range Default Value Description This parameter indicates the port whose priority can be set. l This parameter indicates the priorities of the ports in a LAG as defined in the LACP protocol. The smaller the value, the higher the priority. l When ports are added into a LAG, the port of the highest priority is preferred for service transmission.
Port Priority
0 to 65535
32768
Parameter System Load Sharing Hash Algorithm
Value Range Source MAC Destination MAC Source and Destination MAC Source IP Destination IP Source and Destination IP MPLS Label
Default Value Source and Destination IP
Description l System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to Sharing. l The load sharing computation methods include computation based on MAC addresses (based on the source MAC address, based on the destination MAC address, and based on the source MAC address + sink MAC address), computation based on IP addresses (based on the source IP address, based on the destination IP address, and based on the source IP address and sink IP address), and computation based on MPLS labels. l After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect for the entire NE. l For PW-carried UNINNI E-Line services, System Load Sharing Hash Algorithm cannot be set to MPLS Label.
Related Tasks
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT

This topic describes the parameters that are related to point-to-point LPT.
B-250
Issue 03 (2011-04-10)
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Click the Point-to-Point LPT tab.
Parameters on the main interface

Parameter Binding Status Value Range Default Value Description This parameter displays the binding status of pointto-point services. This parameter displays the port where the primary point of point-to-point LPT resides. This parameter displays the type of secondary point for point-to-point LPT. This parameter displays the port where the secondary point of pointto-point LPT resides. This parameter displays the status of point-to-point LPT. This parameter displays or specifies the enabling status of point-to-point LPT. The LPT function can take effect only when LPT Enabled is set to Enabled. Recovery Times(s) 1-600 1 This parameter displays or specifies the recovery time of point-to-point LPT. This parameter displays or specifies the hold-off time of point-to-point LPT. This parameter displays the switching mode of point-to-point LPT. Pointto-point LPT is available only in strict mode.
B-251
Primary Function Point
Secondary Function Point Type
Secondary Function Point
LPT Instance Status
LPT Enabled
Enabled Disabled
Disabled
Hold-Off Times(ms)
0-10000
1000
Switching Mode
Issue 03 (2011-04-10)
Parameter Fault Detection Mode
Value Range PW OAM LPT OAM
Default Value LPT OAM
Description This parameter displays the fault detection mode of point-to-multipoint LPT. l LPT-enabled NEs periodically transmit LPT OAM packets in specific formats to check the status of an L2 service network or QinQ service network. If the LPT OAM packets are absent for 3.5 fault detection periods or the number and contents of received LPT OAM packets are incorrect, the NEs consider that a network-side fault occurred and the LPT switching is triggered. l To detect a networkside fault on a PSN, LPT OAM or PW OAM packets can be used. Note that the PW OAM function must be enabled on NEs before usage of PW OAM packets.
Fault Detection Period (100ms)
3-100
10
This parameter displays or specifies the fault detection period of pointto-point LPT. This parameter displays the status of a user-side port. This parameter displays the NET IDs of LPT packet out ports at both ends.
User-Side Port Status
L2 net ID-L2 Peer net ID
Related Tasks
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT

This topic describes the parameters that are related to creating point-to-point LPT.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Click the Point-to-Point LPT tab. Click Bind in the lower right corner of the pane based on the type of service network. Choose PW+QinQ or L2 net from the shortcut menu based on the type of service network.

Parameter L2 net ID Value Range 1-4294967295 Default Value Description This parameter specifies the NET ID of LPT packet out port at the local end. This parameter specifies the NET ID of LPT packet out port at the opposite end. This parameter specifies the port where the primary point of point-to-point LPT resides. This parameter specifies the VLAN ID that is carried by a point-to-point LPT packet to traverse an L2 network. This parameter specifies the out port of a point-topoint LPT packet.
L2 Peer net ID
1-4294967295
VLAN ID
1-4094
LPT package out port
Related Tasks
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT

This topic describes the parameters that are related to point-to-multipoint LPT.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree.
Issue 03 (2011-04-10)
2.
Click the Point-to-Multipoint LPT tab.
Parameters of Primary Point

Parameter Primary Function Point Type Value Range Default Value Description This parameter displays the type of primary point for point-to-multipoint LPT. This parameter displays the port where the primary point of point-tomultipoint LPT resides. This parameter displays the status of point-tomultipoint LPT. This parameter displays the enabling status of point-to-multipoint LPT. This parameter displays or specifies the recovery time of point-to-multipoint LPT. This parameter displays or specifies the hold-off time of point-to-multipoint LPT. This parameter displays the switching mode of point-to-multipoint LPT. Point-to-point LPT is available only in strict mode. l Strict mode A primary point triggers LPT switching when all its secondary points detect faults. l Non-strict mode A primary point triggers LPT switching when anyone of its secondary points detects a fault.
LPT Instance Status
LPT Enabled
Enabled Disabled
Disabled
Recovery Times(s)
1-600
Hold-Off Times(ms)
0-10000
1000
Switching Mode
Strict mode Non-strict mode
Strict mode
B-254
Issue 03 (2011-04-10)
Parameter Fault Detection Mode
Value Range PW OAM LPT OAM
Default Value LPT OAM
Description This parameter displays the fault detection mode of point-to-multipoint LPT. l LPT-enabled NEs periodically transmit LPT OAM packets in specific formats to check the status of an L2 service network or QinQ service network. If the LPT OAM packets are absent for 3.5 fault detection periods or the number and contents of received LPT OAM packets are incorrect, the NEs consider that a network-side fault occurred and the LPT switching is triggered. l To detect a networkside fault on a PSN, LPT OAM or PW OAM packets can be used. Note that the PW OAM function must be enabled on NEs before usage of PW OAM packets.
Fault Detection Period (100ms)
3-100
10
This parameter displays or specifies the fault detection period of pointto-multipoint LPT. This parameter displays the status of a user-side port. This parameter displays the NET IDs of LPT packet out ports at both ends, when the service network is an L2 network.
Issue 03 (2011-04-10)
B-255
Parameters of Secondary Point

Parameter Access Point Type Value Range Default Value Description This parameter displays the type of second point for point-to-multipoint LPT. This parameter displays the port or PW ID for the secondary point of pointto-multipoint LPT. This parameter displays the status of a user-side port. This parameter displays the NET IDs of LPT packet out ports at both ends, when the service network is an L2 network.
Access Point
Related Tasks
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT

This topic describes the parameters that are related to creating point-to-multipoint LPT.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management > LPT from the Function Tree. Click the Point-to-Multipoint LPT tab. Click New in the lower right corner of the pane based on the type of service network. Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.
B-256
Issue 03 (2011-04-10)
Parameters of primary point

Parameter Point Type Value Range UNI PW QinQ L2 net Default Value Description This parameter specifies the type of primary point for point-to-multipoint LPT. The value range of this parameter pertains to the type of service network. If the primary point is on the access side, select UNI; if the primary point is on the network side, set the parameter as follows. l If the service network is a PSN, select PW. l If the service network is a QinQ network, select QinQ. l If the service network is an L2 network, select L2 net. Board This parameter specifies the board where the primary point of point-tomultipoint LPT resides. This parameter is valid only when Point Type is set to UNI. Port This parameter specifies the port where the primary point of point-tomultipoint LPT resides. This parameter is valid only when Point Type is set to UNI. Point ID This parameter specifies the service ID for the primary point of point-tomultipoint LPT. This parameter is valid only when Point Type is set to PW or QinQ.
Issue 03 (2011-04-10)
B-257
Parameter L2 net ID
Value Range 1-4294967295
Default Value -
Description This parameter specifies the NET ID of a local NE. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
L2 Peer net ID
1-4294967295
This parameter specifies the NET ID of an opposite NE. This parameter is valid only when Point Type is set to L2 net.
VLAN ID
1-4094
This parameter specifies the VLAN ID that is carried by an LPT packet to traverse an L2 network. This parameter is valid only when Point Type is set to L2 net.
LPT package out port
This parameter specifies the out port of an LPT packet. This parameter is valid only when Point Type is set to L2 net.
Parameters of secondary point

Parameter Point Type Value Range UNI PW QinQ L2 net Default Value Description This parameter displays or specifies the type of secondary point for pointto-multipoint LPT.
B-258
Issue 03 (2011-04-10)
Parameter Board
Value Range -
Default Value -
Description This parameter specifies the board where the secondary point of pointto-multipoint LPT resides. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
Available Points
This parameter displays the available ports where the secondary point of point-to-multipoint LPT can reside. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
Selected Points
This parameter displays the selected port where the secondary point of pointto-multipoint LPT resides. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
L2 net ID
1-4294967295
This parameter specifies the NET ID of a local NE. This parameter is valid only when Point Type is set to UNI.
L2 Peer net ID
1-4294967295
This parameter specifies the NET ID of an opposite NE. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
Issue 03 (2011-04-10)
B-259
Parameter VLAN ID
Value Range 1-4094
Default Value -
Description This parameter specifies the VLAN ID that is carried by an LPT packet to traverse an L2 network. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
LPT Package out port
This parameter specifies the out port of an LPT packet. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
Related Tasks
B.6.3 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation This topic describes the parameters that are used for creating maintenance domains. B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation This topic describes the parameters that are used for creating maintenance associations. B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation This topic describes the parameters that are used for creating a maintenance association end point (MEP). B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation This topic describes the parameters that are used for creating a remote MEP. B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation This topic describes the parameters that are used for creating a maintenance association intermediate point (MIP). B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling This topic describes the parameters that are used for enabling the LB.
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling This topic describes the parameters that are used for enabling the LT. B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter This topic describes the OAM parameters that are related to Ethernet ports. B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring This topic describes the parameters that are used for monitoring the OAM error frames at the Ethernet port.
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation

This topic describes the parameters that are used for creating maintenance domains.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Choose New > New Maintenance Domain.

Parameter Maintenance Domain Name Value Range Default Value default Description l This parameter specifies the name of the maintenance domain. l The maintenance domain refers to the network for the Ethernet OAM. l This parameter can contain a maximum of eight bytes.
Issue 03 (2011-04-10)
B-261
Parameter Maintenance Domain Level
Value Range 0 1 2 3 4 5 6 7
Default Value 0
Description l Maintenance Domain Level specifies the level of the maintenance domain. l The values 0-2 indicate the carrier level, the values 3-4 indicate the supplier level, and the values 5-7 indicate the user level. l When the value is set to 0, the maintenance domain is at the lowest level. The values 0-7 indicate that the level increases in a sequential order. l The OAM packets whose level is higher than the preset value are transparently transmitted by the MEPs. The OAM packets whose level is lower than the preset value are directly discarded by the MEPs. The OAM packets whose level is the same as the preset value are responded to or terminated by the MEPs according to the message type.
Related Tasks
A.6.8.1 Creating an MD
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation

This topic describes the parameters that are used for creating maintenance associations.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association.

Parameter Maintenance Domain Name Value Range Default Value Description This parameter indicates the maintenance domain of the created maintenance association.
B-262
Issue 03 (2011-04-10)
Parameter Maintenance Association Name
Value Range -
Default Value -
Description l This parameter specifies the name of the maintenance association, which is a domain related to a service. Through maintenance association division, the connectivity check (CC) can be performed on the network that transmits a service instance. l This parameter can contain a maximum of eight bytes.
Relevant Service
This parameter specifies the service instance that is related to the maintenance association. l This parameter specifies the interval for transmitting packets in the CC. l The CC is performed to check the availability of the service.
CC Test Transmit Period
1s 10s 1m 10m
1s
Related Tasks
A.6.8.2 Creating an MA
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

This topic describes the parameters that are used for creating a maintenance association end point (MEP).
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point.

Parameter Maintenance Domain Name Maintenance Association Name Board Value Range Default Value Description This parameter indicates the maintenance domain of the created MEP. This parameter indicates the maintenance association of the created MEP. This parameter specifies the board where the MEP is located.
B-263
Issue 03 (2011-04-10)
Parameter Port VLAN MP ID
Default Value -
Description This parameter specifies the port where the MEP is located. This parameter indicates the VLAN ID of the current service. l This parameter specifies the MEP ID. l Each MEP needs to be configured with an MP ID, which is unique in the maintenance association. The MP ID is required in the OAM operation.
Direction
Ingress Egress
Ingress
l Direction specifies the direction of the MEP. l Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates the direction in which the packets are transmitted from the port.
CC Status
Active Inactive
Active
l This parameter specifies whether to enable the CC function of the MEP. l In the case of the tests based on the MP IDs, CC Status must be set to Active.
AIS Active Status
Active Inactive
Active
l This parameter specifies the AIS active status. l If several MDs exist on a link, to locate a fault accurately, set AIS Active Status to Active and Client Layer Level that functions to suppress the AIS information. l After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP, informing the higher level MP of the fault information; if this MP does not activate the AIS, it does not report the fault.
Client Layer Level
1 to 7
l Normally, if an MP is set to level n, Client Layer Level that functions to suppress the AIS information should be set to n+1. l Client Layer Level is valid only if AIS Active Status is Active.
Related Tasks
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation

This topic describes the parameters that are used for creating a remote MEP.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Click New.

Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value Range 1 to 2048 Default Value Description This parameter indicates the maintenance domain of the MEP. This parameter indicates the maintenance association of the created MEP. l This parameter specifies the ID of the remote MEP. l If other MEPs may initiate OAM operations to an MEP in the same MA, set the other MEPs to be the remote MEPs.
Related Tasks
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation

This topic describes the parameters that are used for creating a maintenance association intermediate point (MIP).
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the MIP Point tab. Select the maintenance domain in which an MIP needs to be created, and then click New.
Issue 03 (2011-04-10)
B-265

Parameter Maintenance Domain Name Board Port MP ID Value Range 1 to 2048 Default Value Description This parameter indicates the maintenance domain of the MIP. This parameter specifies the board where the MIP is located. This parameter specifies the port where the MIP is located. l This parameter specifies the MIP ID. l Each MIP needs to be configured with an MP ID, which is unique in the maintenance domain. The MP ID is required in the OAM operation.
NOTE To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the level of the MIP must be higher than the level of the MEP.
Related Tasks
A.6.8.5 Creating an MIP
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

This topic describes the parameters that are used for enabling the LB.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain and maintenance association for the LB test. Choose OAM > Start LB.

Parameter MP ID Value Range Selected Deselected Maintenance Point MAC Address Selected Deselected Selected Default Value Deselected Description This parameter needs to be selected if the LB test is performed on the basis of Destination Maintenance Point IDs. This parameter needs to be selected if the LB test is performed on the basis of MAC addresses.
Issue 03 (2011-04-10)
B-266
Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID
Value Range -
Default Value -
Description This parameter indicates the name of the maintenance domain for the LB test. This parameter indicates the name of the maintenance association for the LB test. l This parameter specifies the source maintenance point in the LB test. l Only the MEP can be set to the source maintenance point.
Destination Maintenance Point ID
l This parameter specifies the destination maintenance point in the LB test. l Only the MEP ID can be set to the Destination Maintenance Point ID. l Destination Maintenance Point ID can be set only when MP ID is selected.
Destination Maintenance Point MAC Address
00-00-00-00-00-00
l This parameter specifies the MAC address of the port where the destination maintenance point is located in the LB test. l Only the MAC address of the MEP can be set to the MAC address of the Destination Maintenance Point MAC Address. l Destination Maintenance Point MAC Address can be set only when Sink Maintenance Point MAC Address.
Transmitted Packet Count
1 to 255
l This parameter specifies the number of packets transmitted each time in the LB test. l When the value is greater, the required duration is longer.
Transmitted Packet Length
64 to 1400
64
l This parameter specifies the length of a transmitted LBM packet. l If the packet length is different, the test result may be different. In normal cases, it is recommended that you use the default value.
Transmitted Packet Priority
0 to 7
l This parameter specifies the priority of transmitting packets. l 0 indicates the lowest priority, and 7 indicates the highest priority. In normal cases, this parameter is set to the highest priority.
Issue 03 (2011-04-10)
B-267
Parameter Detection Result
Value Range -
Default Value -
Description This parameter indicates the relevant information and result of the LB test.
Related Tasks
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain and maintenance association for the LT test. Choose OAM > Start LT.
Test Node Parameters

Parameter MP ID Value Range Selected Deselected Maintenance Point MAC Address Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Selected Deselected Selected Default Value Deselected Description This parameter needs to be selected if the LT test is performed on the basis of MP IDs. This parameter needs to be selected if the LT test is performed on the basis of MAC addresses. This parameter indicates the name of the maintenance domain for the LT test. This parameter indicates the name of the maintenance association for the LT test. l This parameter specifies the source maintenance point in the LT test. l Only the MEP can be set to the source maintenance point. l This parameter specifies the destination maintenance point in the LT test. l Only the MEP ID can be set to the Destination Maintenance Point ID. l Destination Maintenance Point ID can be set only when MP ID is selected.
Destination Maintenance Point ID
Parameter Destination Maintenance Point MAC Address
Value Range -
Default Value 00-00-00-00-00-00
Description l This parameter specifies the MAC address of the port where the destination maintenance point is located in the LT test. l Only the MAC address of the MEP can be set to the MAC address of the Destination Maintenance Point MAC Address. l Destination Maintenance Point MAC Address can be set only when Sink Maintenance Point MAC Address.
Parameters for the Detection Result

Parameter Source Maintenance Point ID Destination Maintenance Point ID/MAC Response Maintenance Point ID/MAC Hop Count Value Range Default Value Description This parameter indicates the source maintenance point in the LT test. This parameter indicates the MAC address of the port where the destination maintenance point is located in the LT test. This parameter indicates the MAC address of the port where the responding maintenance point is located in the LT test. l This parameter indicates the number of hops from the source maintenance point to the responding maintenance point or to the destination maintenance point in the LT test. l The number of hops indicates the adjacent relation between the responding maintenance point to the source maintenance point. The number of hops increases by one when a responding point occurs on the link from the source maintenance point to the destination maintenance point. Test Result This parameter indicates the result of the LT test.
1 to 64
Related Tasks

This topic describes the OAM parameters that are related to Ethernet ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Click the OAM Parameter tab.

Parameter Port Enable OAM Protocol Value Range Enabled Disabled Default Value Disabled Description This parameter indicates the corresponding port. l This parameter indicates or specifies whether to enable the OAM protocol. l After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to create the OAM connection with the opposite end. OAM Working Mode Active Passive Active l This parameter indicates or specifies the working mode of the OAM. l The port whose OAM working mode is set to Active can initiate the OAM connection. l The port whose OAM working mode is set to Passive can only wait for the opposite end to send the OAM connection request. l The OAM working mode of the equipment at only one end can be Passive. Remote Alarm Support For Link Event Enabled Disabled Enabled l This parameter indicates or specifies whether the local link events can be notified to the opposite end. l If the alarms caused by link events can be reported, that is, if the number of performance events (for example, error frame period, error frame, error frame second, and error frame signal cycle) at the local end exceeds the preset threshold, these performance events are notified to the port at the opposite end through the link event notification function. l This parameter is set according to the planning information.
Parameter Remote Side Loopback Response
Description l This parameter indicates or specifies whether the port responds to the remote loopback. l Remote loopback indicates that the local OAM entity transmits packets to the remote OAM entity for loopback. The local OAM entity can locate the fault and test the link performance through loopback data analysis. l If a port does not support remote loopback response, this port does not respond to the loopback request from the remote port regardless of the OAM port status.
Loopback Status
Non-Loopback Initiate Loopback at Local Respond Loopback of Remote
This parameter indicates the loopback status at the local end.

NOTE Loopback Status is valid only after you choose OAM > Enable Remote Loopback.
OAM Discovery Status Port Transmit Status Port Receive Status
This parameter indicates the OAM discovery status at the local end. This parameter indicates the status of transmitting packets at the local end. This parameter indicates the status of receiving packets at the local end.
Related Tasks
A.6.9.1 Enabling the OAM Auto-Discovery Function A.6.9.2 Enabling the Remote Alarm Support for Link Event
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the Ethernet port.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM from the Function Tree. Click the OAM Error Frame Monitor tab.
Issue 03 (2011-04-10)
B-271

Parameter PORT Error Frame Monitor Window (ms) Error Frame Monitor Threshold (frames) Value Range 1000 to 60000, in step of 100 1 to 4294967295, in step of 1 Default Value 1000 Description This parameter indicates the corresponding port. This parameter specifies the duration of monitoring error frames. l This parameter specifies the threshold of monitoring error frames. l Within the specified value of Error Frame Monitor Window(ms), if the number of error frames on the link exceeds the preset value of Error Frame Monitor Threshold(frame), an alarm is reported. 1488 to 892800000, in step of 1 1 to 892800000, in step of 1 892800000 This parameter specifies the window of monitoring the error frame period. l This parameter specifies the threshold of monitoring the error frame period. l Within the specified value of Error Frame Period Window(frame), if the number of error frames on the link exceeds the preset value of Error Frame Period Threshold(frame), an alarm is reported. 10 to 900, in step of 1 10 to 900, in step of 1 60 1 This parameter specifies the time window of monitoring the error frame second. l This parameter specifies the threshold of monitoring error frame seconds. l If any error frame occurs in one second, this second is called an errored frame second. Within the specified value of Error Frame Second Window(s), if the number of error frames on the link exceeds the preset value of Error Frame Second Threshold(s), an alarm is reported. 1 to 60, in step of 1 1 This parameter specifies the window of monitoring the error frame signal period.
Error Frame Period Window (frame) Error Frame Period Threshold (frames)
Error Frame Second Window(s) Error Frame Second Threshold (s)
Error Frame Signal Periodic Monitor Window (Entries)
B-272
Issue 03 (2011-04-10)
Parameter Error Frame Signal Periodic Monitor Threshold (Entries)
Default Value 1
Description l This parameter specifies the threshold of monitoring the error frame signal period. l Within the specified value of Error Frame Signal Periodic Monitor Window(Entries), if the number of error signals exceeds the preset value of Error Frame Signal Periodic Monitor Threshold(Entries), an alarm is reported.
Related Tasks
B.6.4 QoS Parameters

This topic describes the parameters that are related to QoS. B.6.4.1 Parameter Description: Diffserv Domain Management This topic describes the parameters that are used for managing DiffServ domains. B.6.4.2 Parameter Description: DiffServ Domain Management_Create This parameter describes the parameters that are used for creating DiffServ (DS) domains. B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports. B.6.4.4 Parameter Description: Policy Management This topic describes the parameters that are related to port policies. B.6.4.5 Parameter Description: Port Policy This topic describes the parameters that are used for creating port policies. B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration This parameter describes the parameters that are used for creating traffic classification. B.6.4.7 Parameter Description: Port Shaping Management_Creation This topic describes the parameters that are used for creating port shaping management tasks.

This topic describes the parameters that are used for managing DiffServ domains.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree.
Issue 03 (2011-04-10)
B-273

Parameter Mapping Relation ID Value Range 1 to 8 Default Value 1 Description This parameter indicates the ID of the mapping relation between DiffServ domains. This parameter indicates the name of the mapping relation between DiffServ domains.
Mapping Relation Name
Default Map
NOTE
If one default DiffServ domain exists on the OptiX RTN 950 equipment, Mapping Relation ID is set to 1, and Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Parameters for Ingress Mapping Relation

Parameter CVLAN Value Range 0 to 7 Default Value Description l This parameter indicates the priority of the C-VLAN of the ingress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority. SVLAN 0 to 7 l This parameter indicates the priority of the S-VLAN of the ingress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
B-274
Issue 03 (2011-04-10)
Parameter IP DSCP
Value Range 0 to 63
Default Value -
Description l This parameter indicates the DSCP priority of the IP addresses of the ingress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
0 to 7
l Displays the MPLS EXP value of ingress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
NOTE The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Issue 03 (2011-04-10)
B-275
Parameter PHB
Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
Default Value -
Description l This parameter indicates the per-hop behavior (PHB) service class of the DiffServ domain. l The PHB service class refers to the forwarding behavior of the DiffServ node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value, and MPLS EXP value) contained in the packets of the DiffServ domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
NOTE The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. It is the same case with the AF2, AF3, and AF4.
B-276
Issue 03 (2011-04-10)
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7 Default Value Description l This parameter indicates the PHB service class of the DiffServ domain. l The PHB service class refers to the forwarding behavior of the DiffServ node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS value) contained in the packets of the DiffServ domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
CVLAN
0 to 7
l This parameter indicates the priority of the C-VLAN of the egress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
Issue 03 (2011-04-10)
B-277
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description l This parameter indicates the priority of the S-VLAN of the egress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
IP DSCP
0 to 63
l This parameter indicates the DSCP priority of the IP addresses of the ingress packets. l The DSCP refers to bits 0-5 of the DS field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
0 to 7
l Displays the MPLS EXP value of egress packets. l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted priority type (MPLS EXP value) and specifies the PHB service class of the packet according to the mappings between packet priorities and PHB service classes.
B-278
Issue 03 (2011-04-10)

Parameter Port Value Range Default Value Description This parameter indicates the port that uses the DiffServ domain. The packets trusted by the OptiX RTN 950 are the C_VLAN, S_VLAN and IP DSCP packets that contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS value. By default, the untrusted packets are mapped to the BE service class for best-effort forwarding.
NOTE l The trusted packet priorities of a UNI port include DSCP value, CVLAN priority, and SVLAN priority. For the E-Line services that are transparently transmitted end to end (UNI-UNI), a UNI port only trusts DSCP value. l An NNI port carrying MPLS/PWE3 services trusts only packets with MPLS EXP values. l The trusted packet priorities of a QinQ link NNI port are configured according to the planning information.
Packet Type
CVLAN SVLAN IP-DSCP MPLS-EXP
CVLAN
Related Tasks
A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.10 Querying the DS Domain of a Port
B.6.4.2 Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Issue 03 (2011-04-10)
B-279
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Click New.
2.

Parameter Mapping Relation ID Value Range 2 to 8 Default Value Description This parameter specifies the ID of the mapping relation of a DS domain. This parameter specifies the name of the mapping relation of a DS domain.
Mapping Relation Name
Parameters for Ingress Mapping Relation

Parameter CVLAN Value Range 0 to 7 Default Value Description l This parameter specifies the C-VLAN priority of the ingress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority. SVLAN 0 to 7 l This parameter specifies the S-VLAN priority of the ingress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
B-280
Issue 03 (2011-04-10)
Parameter IP DSCP
Value Range 0 to 63
Default Value -
Description l This parameter specifies the DSCP priority of the IP addresses of the ingress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
l Displays the MPLS EXP value of ingress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
Issue 03 (2011-04-10)
B-281
Parameter PHB
Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
Default Value -
Description l This parameter indicates the PHB service class of the DS domain. l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
B-282
Issue 03 (2011-04-10)
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7 Default Value Description l This parameter indicates the PHB service class of the DS domain. l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
CVLAN
0 to 7
l This parameter specifies the C-VLAN priority of the egress packets. l C-VLAN indicates the client-side VLAN priority, and the value 7 indicates the highest priority.
Issue 03 (2011-04-10)
B-283
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description l This parameter specifies the S-VLAN priority of the egress packets. l S-VLAN indicates the server-side VLAN priority, and the value 7 indicates the highest priority.
IP DSCP
0 to 63
l This parameter specifies the DSCP priority of the IP addresses of the egress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
l Displays the MPLS EXP value of egress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
B-284
Issue 03 (2011-04-10)

Parameter Board Value Range Default Value Description This parameter specifies the board that uses the mapping relations between DS domains. This parameter displays the available port list from which you can select the port that uses the mapping relations between DS domains. This parameter displays the selected port list. The ports in the list use the mapping relations between DS domains.
Available Port
Port
Issue 03 (2011-04-10)
B-285
Parameter Packet Type
Value Range cvlan svlan ip-dscp mpls-exp
Default Value cvlan
Description l This parameter specifies the type of the packet. l The packets trusted by the OptiX RTN 950 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS EXP value. By default, the untrusted packets are mapped to the BE service class for besteffort forwarding.
Related Tasks
A.6.7.1 Creating a DS Domain
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports.
B-286
Issue 03 (2011-04-10)
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Select the DS domain to be changed in the main interface. Click the Apply Port tab. Click Modify.
2. 3. 4.
Parameters for Configuring the Applied Ports

Parameter Mapping Relation Name Value Range Default Value Description This parameter indicates the name of the mapping relation of a DS domain. The packets trusted by the OptiX RTN 950 are the CVLAN, S-VLAN, IP DSCP packets, and MPLS packets that respectively contain the C-VLAN priority, S-VLAN priority, IP DSCP value and MPLS EXP value. By default, the untrusted packets are mapped to the BE service class for besteffort forwarding.
Packet Type
CVLAN SVLAN IP-DSCP MPLS-EXP
CVLAN
Board
This parameter specifies the board where the port is located.

B-287
Issue 03 (2011-04-10)
Parameter Available Port Selected Port
Value Range -
Default Value -
Description This parameter indicates the available port. This parameter indicates the selected port. The selected port is applied to the DS domain.
NOTE
If one default DS domain exists on the OptiX RTN 950, Mapping Relation ID is set to 1, and Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Related Tasks
A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types

This topic describes the parameters that are related to port policies.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Click the CoS Configuration tab.
Parameters
Parameter Policy ID Policy Name Value Range Default Value Description This parameter indicates the policy ID of the port. This parameter indicates or specifies the policy name of the port.
B-288
Issue 03 (2011-04-10)
Parameter CoS
Value Range CS7 CS6 EF AF4 AF3 AF2 AF1 BE
Default Value -
Description l The BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 service classes respectively map eight queuing entities. The OptiX RTN 950 provides different QoS policies for the queues at different service classes. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
Issue 03 (2011-04-10)
B-289
Value Range SP WRR
Default Value CS7, CS6, EF, BE: SP AF4, AF3, AF2, AF1: WRR
Description l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time. l The OptiX RTN 950 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE).
B-290
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description l This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
l This parameter specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l This parameter can be set only when Grooming Police After Reloading is set to WRR. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Disabled
l This parameter indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
CIR(kbit/s)
Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
Issue 03 (2011-04-10)
B-291
Parameter PIR(kbit/s)
Value Range -
Default Value -
Description l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR. l This parameter is set according to the planning information.
CBS(byte)
l It is recommended that you set the value of the CBS equal to the value of the PIR. In actual traffic shaping processing, only the PBS is valid. l This parameter is set according to the planning information.
B-292
Issue 03 (2011-04-10)
Parameter PBS(byte)
Value Range -
Default Value -
Description l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
A.6.7.5 Modifying the Port Policy A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.9 Querying the Port Policy
B.6.4.5 Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Click the CoS Configuration tab. Click New. The Create Port Policy dialog box is displayed.
Parameters
Parameter Policy ID Automatically Assign Value Range Selected Deselected Default Value Deselected Description This parameter specifies the policy ID of the port. This parameter specifies whether to automatically allocate the policy ID of the port policy. After this parameter is selected, the system automatically allocates the policy ID, and then the policy ID cannot be set manually.
B-293
Issue 03 (2011-04-10)
Parameter Policy Name
Value Range -
Default Value -
Description This parameter specifies the policy name of the port. l The BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 service classes respectively map eight queuing entities. The OptiX RTN 950 provides different QoS policies for the queues at different service class. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
CoS
CS7 CS6 EF AF4 AF3 AF2 AF1 BE
B-294
Issue 03 (2011-04-10)
Value Range SP WRR
Default Value CS7, CS6, EF, BE: SP AF4, AF3, AF2, AF1: WRR
Description l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time. l The OptiX RTN 950 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE).
Issue 03 (2011-04-10)
B-295
Parameter
Value Range
Default Value
Description l This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
l Policy Weight(%) specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l This parameter can be set only when Grooming Police After Reloading is set to WRR. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Disabled
l Bandwidth Limit indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
CIR(kbit/s)
Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
B-296
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR. l This parameter is set according to the planning information.
CBS(byte)
l It is recommended that you set the value of the CBS equal to the value of the PIR. In actual traffic shaping processing, only the PBS is valid. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-297
Parameter PBS(byte)
Value Range -
Default Value -
Description l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
A.6.7.4 Creating a Port Policy
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration

This parameter describes the parameters that are used for creating traffic classification.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Click the Traffic Classification Configuration tab. Click New.

Parameter Traffic Classification ID Value Range 1 to 1024 Default Value Description This parameter specifies the ID of the traffic classification.
B-298
Issue 03 (2011-04-10)
Parameter ACL Action
Value Range Permit Deny
Default Value Permit
Description l The access control list (ACL) determines whether to forward or discard the packets that enter the port according to the specified matching rules. l When ACL Action is set to Permit, the ingress port accepts and then performs QoS processing for only the packets that meet the specified mapping rules. l When ACL Action is set to Deny, the ingress port discards the packets that meet the specified mapping rules.
Ingress Parameters
Parameter Logical Relation Between Matched Rules Value Range And Default Value And Description l This parameter specifies the logical relationship between the traffic classification matching rules. l The OptiX RTN 950 supports the setting of the logical AND between multiple matching rules.
Issue 03 (2011-04-10)
B-299
Parameter Match Type
Value Range DSCP Value CVlan ID CVlan priority SVlan ID SVlan priority
Default Value -
Description l After you click Add or Delete, complex traffic classification can be performed on the traffic that enters the ingress port according to the preset matching rules. l In the case a specific service, complex traffic classification can be divided into basic traffic types according to the DSCP value, C-VLAN ID, CVLAN priority, SVLAN ID, or SVLAN priority. Traffic type is based on the associated Ethernet packets. Therefore, this parameter is set according to the packet type and the planning information.
Match Value
DSCP Value: 0 to 63 CVlan ID: 1 to 4094 CVlan priority: 0 to 7 SVlan ID: 1 to 4094 SVlan priority: 0 to 7
l If the matching value of the packets is the same as the preset Match Value, the packets match the rules of complex traffic classification. l This parameter is set according to the planning information.
Wildcard
This parameter has a fixed value of 0.
B-300
Issue 03 (2011-04-10)
Parameter CoS
Default Value -
Description l This parameter specifies the PHB service class queue mapped by the traffic classification packets. l If this parameter is set to empty (-), the traffic classification packets map the PHB service class queue according the mapping relation specified in the topic about Diffserv domain management. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Enabled
l This parameter indicates or specifies whether the CAR operation is performed for the flow in the ingress direction. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-301
Parameter CIR(kbit/s)
Value Range -
Default Value -
Description l When the rate of the packets is not more than the CIR, the packets are marked blue and pass the CAR policing. These packets are first forwarded in the case of network congestion. l When the rate of the packets is more than the CIR but not more than the PIR, the packets whose rate is more than the CIR can pass the restriction of the CAR and are marked yellow. The processing method of the packets marked yellow can be set to "Pass" or "Remark". "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port. If a network congestion event occurs again, the packets marked yellow can be processed according to the new priority. l This parameter is set according to the planning information.
B-302
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description l When the rate of the packets is more than the PIR, the packets that exceed the rate restriction are marked red and directly discarded. l When the rate of the packets is more than the CIR but not more than the PIR, the packets whose rate is more than the CIR can pass the restriction of the CAR and are marked yellow. The processing method of the packets marked yellow can be set to "Pass" or "Remark". "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port. If a network congestion event occurs again, the packets marked yellow can be processed according to the new priority. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-303
Parameter CBS(byte)
Value Range -
Default Value -
Description l During a certain period, if the rate of the packets whose processing method is marked "Pass" is not more than the CIR, certain burst packets are allowed and can be first forwarded in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. l This parameter is set according to the planning information.
PBS(byte)
l During a certain period, if the rate of the packets whose processing method is marked "Pass" is more than the CIR but not more than the PIR, certain burst packets are allowed and marked yellow. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
B-304
Issue 03 (2011-04-10)
Parameter Coloration Mode
Value Range Color Blindness
Default Value Color Blindness
Description l This parameter specifies the CAR operation performed by the equipment on the packets. The packets are dyed according to the result of the CAR operation. The dying rule is determined by the comparison between the rate of the packets and the preset CAR value. l The OptiX RTN 950 supports Color Blindness only.
Packet Color
Red Yellow Green
Packets can be dyed in three colors: red, yellow, and green. The packets in red are first discarded. l This parameter specifies the method of handling the packets. l Discard: The packets are discarded. l Pass: The packets are forwarded. l Remark: The packets are remarked. "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port.
Handling Mode
Discard Pass Remark
Issue 03 (2011-04-10)
B-305
Parameter Relabeled CoS
Default Value -
Description If the handling method is set to "Remark", you can reset the CoS of the packets.
Egress Parameters
Parameter Bandwidth Limit Value Range Disabled Enable Default Value Enable Description l This parameter indicates or specifies whether the traffic shaping is performed in the egress function. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
B-306
Issue 03 (2011-04-10)
Parameter CIR(kbit/s)
Value Range -
Default Value -
Description l In the case that no packets exist in the egress queue: When the rate of the packets is not more than the CIR, these packets directly enter the egress queue. l In the case that certain packets exist in the egress queue: The packets whose rate passes the restriction of the PIR directly enter the egress queue, which forwards the packets to the next port at the CIR. l This parameter is set according to the planning information.
Issue 03 (2011-04-10)
B-307
Value Range -
Default Value -
Description l In the case that no packets exist in the egress queue: If the rate of the packets is more than the CIR but is not more than the PIR, the packets whose rate is more than the CIR enter the egress queue, which forwards the packets to the next port at the CIR. If the rate of the packets is more than the PIR, the packets are directly discarded. l In the case that certain packets exist in the egress queue: The packets whose rate passes the restriction of the PIR directly enter the egress queue, which forwards the packets to the next port at the CIR. l This parameter is set according to the planning information.
CBS(byte)
l If the rate of the packets is not more than the CIR during a certain period, the burst packets are directly transmitted. The maximum traffic of the burst packets is determined by the CBS. l This parameter is set according to the planning information.
B-308
Issue 03 (2011-04-10)
Parameter PBS(byte)
Value Range -
Default Value -
Description l If the rate of the packets is more than the CIR but is not more than the PIR during a certain period, the burst packets enter the egress queue. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
A.6.7.6 Creating the Traffic
B.6.4.7 Parameter Description: Port Shaping Management_Creation

This topic describes the parameters that are used for creating port shaping management tasks.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Click New.
Parameters for Port Shaping Management

Parameter Slot No. Port CIR (kbit/s) CBS (byte) PIR (kbit/s) Value Range Default Value Description This parameter specifies the slot ID. This parameter specifies the port. Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
B-309
Issue 03 (2011-04-10)
Parameter PBS (byte)
Value Range -
Default Value -
Description If the traffic shaping function is enabled, OptiX RTN 950 processes the packets in the buffer queue through the following methods when no packets are available in the queue. l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR.
Related Tasks
A.6.7.8 Configuring Port Shaping
B.7 Parameters for Ethernet Services and Ethernet Features on the EoPDH Plane
This section describes the parameters for the Ethernet services and Ethernet features on the EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.7.1 Parameters for Ethernet Services This section describes the parameters for EoPDH-plane Ethernet services. B.7.2 Parameters for Ethernet Protocols This section describes the parameters for EoPDH-plane Ethernet protocols. B.7.3 Parameters for the Ethernet OAM This section describes the parameters for the Ethernet OAM on the EoPDH plane. B.7.4 QoS Parameters This section describes the parameters for the QoS on the EoPDH plane. B.7.5 Parameters for the Ports on Ethernet Boards This section describes the parameters for the Ethernet ports on the EoPDH plane.
B.7.1 Parameters for Ethernet Services

This section describes the parameters for EoPDH-plane Ethernet services. B.7.1.1 Parameter Description: Ethernet Line Service_Creation This section describes the parameters for creating an Ethernet line service. B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services This section describes the parameters associated with QinQ-based Ethernet line services, which need to be set on the NMS. B.7.1.3 Parameter Description: Ethernet Line Service This section describes the parameters for Ethernet line services. B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/802.1q Bridge This section describes the parameters for creating an Ethernet LAN service. B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service This section describes the parameters associated with IEEE 802.1ad bridge-based Ethernet LAN services, which need to be set on the NMS. B.7.1.6 Parameter Description: Ethernet LAN Service This section describes the parameters for creating an Ethernet LAN service. B.7.1.7 Parameter Description: VLAN Filtering Table_Creation This section describes the parameters for creating VLAN filtering tables. B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries This section describes the parameters associated with the aging time of MAC address table entries, which need to be set on the NMS.
B.7.1.1 Parameter Description: Ethernet Line Service_Creation

This section describes the parameters for creating an Ethernet line service.
Navigation Path
1. 2. 3. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Deselect Display QinQ Shared Service. Click New.

Table B-8 Parameters on the main interface Parameter Board Service Type Value Range EPL EVPL(QinQ) Direction Bidirectional Unidirectional Bidirectional l If this parameter is set to Unidirectional, you only need to create a service from the service source to the service sink. That is, there is traffic only in the direction from the service source to the sink port. l If this parameter is set to Bidirectional, you need to create a service from the service source to the service sink and a service from the service sink to the service source. That is, there is traffic in the direction from the service source to the sink port and in the direction from the service sink to the source port at the same time. l In normal cases, it is recommended that you set this parameter to Bidirectional. Source Port l Specifies the port of the service source. l When you create bidirectional Ethernet services from a PORT to a VCTRUNK, it is recommended that you set the PORT to the source port. Default Value EPL Description Displays the board name. Specify the Ethernet service type to EPL.
B-312
Issue 03 (2011-04-10)
Parameter Source VLAN(e.g. 1,3-6)
Value Range 1-4095
Default Value -
Description l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the hyphen (-) to represent consecutive numbers. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number of VLANs must be the same as the value of Sink VLAN(e.g. 1,3-6). l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that carries a specified VLAN ID at the source port can be used as the service source.
Sink Port
l Specifies the port of the service sink. l This parameter cannot take the same value as Source Port. l When you create bidirectional Ethernet services from a PORT to a VCTRUNK, it is recommended that you set the VCTRUNK to the sink port.
Sink VLAN(e.g. 1,3-6)
1-4095
l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the hyphen (-) to represent consecutive numbers. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number of VLANs must be the same as the value of Source VLAN(e.g. 1,3-6). l If this parameter is set to null, all the services at the sink port are used as the service sink. l If this parameter is not set to null, only the service that carries a specified VLAN ID at the sink port can be used as the service sink.
Issue 03 (2011-04-10)
B-313
Table B-9 Parameters for port attributes Parameter Port Port Type Port Enabled Value Range Enabled Disabled Default Value Description Displays the ports involved in the Ethernet service. Displays the network attribute of the Ethernet port. l When the source port or the sink port is set to a PORT, set Port Enabled to Enabled. l This parameter need not be set when the source port or sink port is a VCTRUNK. TAG Tag Aware Access Hybrid l If all the accessed services are frames with VLAN tags (tagged frames), set this parameter to Tag Aware. l If all the accessed services are frames without VLAN tags (untagged frames), set this parameter to Access. l If the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Table B-10 Parameters for bound paths Parameter Configurable Ports Level Value Range VCTRUNK1VCTRUNK16 Default Value Description Specifies the VCTRUNK to bind paths. Displays the level of the bound VC path. In the case of the EFP8 board, this parameter always takes the value of VC12-Xv. Direction Bidirectional Uplink Downlink Available Resources Bidirectional l Specifies the direction of the bound path. l Set this parameter to Bidirectional unless otherwise specified. l Displays the available VC4 paths. l In the case of the EFP8 board, this parameter always takes the value of VC4-1. VC12-1-VC12-63 Specifies the available timeslots.
Available Timeslots
B-314
Issue 03 (2011-04-10)
Parameter Bound Path
Value Range -
Default Value -
Description You need to plan and set this parameter according to the following principles: l The capacity of the VCTRUNK is determined by the actual bandwidth required by the services. l The EFP8 board supports 16 VCTRUNKs. Each VCTRUNK can bind a maximum of 16 VC-12 paths and the total number of bound VC-12 paths cannot exceed 63.
Number of Bound Paths
Displays the number of the bound VC path.
Related Tasks
A.7.2.1 Creating Ethernet Private Line Services
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services
This section describes the parameters associated with QinQ-based Ethernet line services, which need to be set on the NMS.
Navigation Path
1. 2. 3. In the NE Explorer, select the EFP8 board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Select Display QinQ Shared Service. Click New.

Table B-11 Parameters on the main interface Parameter Board Service Type Value Range EPL EVPL(QinQ) Default Value EPL Description Displays the board name. Specifies the service type to EVPL(QinQ).
Issue 03 (2011-04-10)
B-315
Parameter Direction
Value Range Bidirectional Unidirectional
Default Value Bidirectional
Description l When this parameter is set to Unidirectional, only the service from the service source to the service sink is created. That is, the service source is forwarded only to the sink port. l When this parameter is set to Bidirectional, both the service from the service source to the service sink and the service from the service sink to the service source are created. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port. l It is recommended that you set this parameter to Bidirectional.
Operation Type
l Add S-VLAN l Transparently transmit CVLAN l Transparently transmit SVLAN l Transparently transmit SVLAN and CVLAN l Translate SVLAN l Translate SVLAN and transparently transmit CVLAN l Strip S-VLAN
Strip S-VLAN
l When used for private line services, QinQ can process VLAN tags in different manners as required. l When Service Direction is set to Unidirectional, you can set Operation Type to Strip S-VLAN. l Set this parameter according to actual situations.
Source Port
l Specifies the port where the service source resides. l When creating a bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use the PORT as the source port.
B-316
Issue 03 (2011-04-10)
Parameter Source C-VLAN (e.g. 1, 3-6)
Value Range 1-4095
Default Value -
Description l You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Sink C-VLAN (e.g. 1, 3-6). l When you set this parameter to null, all the services of the source port work as the service source. l When you set this parameter to a nonnull value, only the services of the source port whose VLAN IDs are included in the value range of this parameter work as the service source.
Source S-VLAN
1-4095
l This parameter must be set to a numerical value. l Only the service of the source port whose S-VLAN ID is equal to the value of this parameter work as the service source.
Sink Port
l Specifies the port where the service sink resides. l This parameter must be set to be a value different from Source Port. l When creating a bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use the VCTRUNK as the sink port.
Issue 03 (2011-04-10)
B-317
Parameter Sink C-VLAN(e.g. 1, 3-6)
Value Range 1-4095
Default Value -
Description l You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Source CVLAN(e.g. 1, 3-6). l When you set this parameter to null, all the services of the sink port work as the service sink. l When you set this parameter to a nonnull value, only the services of the sink port whose VLAN IDs are included in the value range of this parameter work as the service sink.
Sink S-VLAN
1-4095
l This parameter must be set to a numerical value. l Only the services of the sink port whose S-VLAN IDs are equal to the value of this parameter work as the service sink.
C-VLAN Priority S-VLAN Priority
AUTO AUTO Priority 0 to Priority 7
AUTO AUTO
Displays the C-VLAN priority. Specifies the S-VLAN priority. The bigger the value, the higher the priority.
Table B-12 Parameters of port attributes Parameter Port Port Type Port Enabled Value Range Enabled Disabled Default Value Description Displays the ports that are configured to transmit the service. Displays the network attribute of the Ethernet port. l When the source port or the sink port is set to a PORT, set Port Enabled to Enabled. l This parameter need not be set when the source port or sink port is a VCTRUNK.
B-318
Issue 03 (2011-04-10)
Parameter TAG
Value Range -
Default Value -
Description This parameter is invalid for QinQ line services.
Table B-13 Parameters for bound paths Parameter Configurable Ports Level Value Range VCTRUNK1VCTRUNK16 Default Value Description Specifies the VCTRUNK to bind paths. Displays the level of the bound VC path. In the case of the EFP8 board, this parameter always takes the value of VC12-Xv. Direction Bidirectional Uplink Downlink Available Resources Bidirectional l Specifies the direction of the bound path. l Set this parameter to Bidirectional unless otherwise specified. l Displays the available VC4 paths. l In the case of the EFP8 board, this parameter always takes the value of VC4-1. VC12-1-VC12-63 Specifies the available timeslots. You need to plan and set this parameter according to the following principles: l The capacity of the VCTRUNK is determined by the actual bandwidth required by the services. l The EFP8 board supports 16 VCTRUNKs. Each VCTRUNK can bind a maximum of 16 VC-12 paths and the total number of bound VC-12 paths cannot exceed 63. Number of Bound Paths Displays the number of the bound VC path.
Available Timeslots Bound Path
Related Tasks
A.7.2.5 Creating QinQ-Based EVPL Services
B.7.1.3 Parameter Description: Ethernet Line Service

This section describes the parameters for Ethernet line services.
Navigation Path
In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.

Table B-14 Parameters on the main interface (Display QinQ Shared Service is not selected) Parameter Service Type Direction Source Port Source VLAN Sink Port Sink VLAN Value Range Default Value Description Displays the service type. Displays the service direction. Displays the port of the service source. Displays the VLAN ID of the service source. Displays the port of the service sink. Displays the VLAN ID of the service sink.
Table B-15 Parameters on the main interface (Display QinQ Shared Service is selected) Parameter Service Type Direction Source Port Source C-VLAN Source S-VLAN Value Range Default Value Description Displays the service type. Displays the service direction. Displays the port of the service source. Displays the VLAN ID of the service source. l Displays the S-VLAN ID of the service source. l This parameter can be set only for the QinQ-based EVPL service. Sink Port Sink C-VLAN Sink S-VLAN Displays the port of the service sink. Displays the VLAN ID of the service sink. l Displays the S-VLAN ID of the service sink. l This parameter can be set only for the QinQ-based EVPL service. C-VLAN Priority l Displays the priority of the C-VLAN. l This parameter can be set only for the QinQ-based EVPL service.
B-320
Issue 03 (2011-04-10)
Parameter S-VLAN Priority
Value Range -
Default Value -
Description l Displays the priority of the S-VLAN. l This parameter can be set only for the QinQ-based EVPL service.
Table B-16 Parameters for port attributes Parameter Port Port Type Port Enabled Value Range Default Value Description Displays the port name. Displays the network attribute of the Ethernet port. When the source port or sink port is a PORT, this parameter indicates whether the port is enabled. Displays the tag attribute of the Ethernet port.
TAG
Table B-17 Parameters for bound paths Parameter VCTRUNK Port Level Direction Bound Path Number of Bound Paths Value Range Default Value Description Displays the VCTRUNK that binds VC paths. Displays the level of the bound VC paths. Displays the direction of the bound VC paths. Displays the serial numbers of the bound VC paths. Displays the number of the bound VC paths.
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/802.1q Bridge
This section describes the parameters for creating an Ethernet LAN service.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Issue 03 (2011-04-10)
2.
Click New.

Table B-18 Parameters on the main interface Parameter Board VB name Value Range Default Value Description Displays the board that is configured with a bridge. Describes the bridge. It is recommended that you set this parameter to a character string that indicates the function of the bridge. l If this parameter is set to 802.1q, an IEEE 802.1q bridge is created. l If this parameter is set to 802.1d, an IEEE 802.1d bridge is created. l IVL/Ingress Filter Enable (IEEE 802.1q bridge and the IEEE 802.1ad bridge) l SVL/Ingress Filter Disable (IEEE 802.1d bridge) l When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, each VLAN has an MAC address table. l When the filtering function is enabled at the ingress port, the ingress port checks the VLAN tags of all incoming packets. If the VLAN ID contained in the VLAN tag of a packet is not included in the VLAN filtering table, the packet is discarded. When the filtering function is disabled at the ingress port, the ingress port does not check any VLAN tag of the incoming packets.
Bridge Type
802.1q 802.1d 802.1ad
802.1q
Bridge Switch Mode
l IVL/Ingress Filter Enable (supported by the IEEE 802.1q bridge and IEEE 802.1ad bridge, unsupported by the IEEE 802.1d bridge) l SVL/Ingress Filter Disable (supported by the IEEE 802.1d bridge and IEEE 802.1ad bridge, unsupported by the IEEE 802.1q bridge)
Bridge Learning Mode Ingress Filter MAC Address Selflearning
Displays the learning mode of the bridge. Displays whether the filtering function is enabled at the ingress port. Displays whether the MAC address selflearning of the bridge is enabled.
B-322
Issue 03 (2011-04-10)
Table B-19 Parameters for mounting services Parameter VB Port Mount Port Value Range Default Value Description Displays the ID of the logical port on the bridge. Displays or specifies which physical port or VCTRUNK on the Ethernet switch board is mounted to the bridge. Displays the network attribute of the port mounted to the bridge. Displays or specifies whether the port mounted to the bridge is enabled. Displays or specifies the tag attribute of the port mounted to the bridge.
Port Type Port Enabled
Disabled Enabled
TAG
Access Tag Aware Hybrid
Default VLAN ID
Displays or specifies the default VLAN ID of the port mounted to the bridge. This parameter is valid only when you set the tag attribute of the port to Access or Hybrid.
Working Mode
Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex
Displays or specifies the working mode of the port mounted to the bridge.
Service Direction C-VLAN S-VLAN S-VLAN Priority C-VLAN Priority
Displays the direction of the service. The IEEE 802.1d/802.1q bridge does not support this parameter. The IEEE 802.1d/802.1q bridge does not support this parameter. The IEEE 802.1d/802.1q bridge does not support this parameter. The IEEE 802.1d/802.1q bridge does not support this parameter.
Issue 03 (2011-04-10)
B-323
Table B-20 Parameters for mounting configuration Parameter Available Mounted Ports Selected Mounted Ports Value Range Default Value Description Displays which physical port or VCTRUNK on the Ethernet switch board can be mounted to the bridge. Displays which physical port or VCTRUNK on the Ethernet switch board is mounted to the bridge.
B-324
Issue 03 (2011-04-10)
Related Tasks
A.7.2.2 Creating Ethernet LAN Services
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
This section describes the parameters associated with IEEE 802.1ad bridge-based Ethernet LAN services, which need to be set on the NMS.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click New.

Table B-22 Parameters on the main interface Parameter Board VB Name Value Range Default Value Description Displays the board where the bridge is configured. This parameter is a string that describes the bridge. It is recommended that you set this parameter to a character string that contains the information about the detailed application of the bridge. When this parameter is set to 802.1ad, create the IEEE 802.1ad bridge.
Bridge Type
802.1q 802.1d 802.1ad
802.1q
Issue 03 (2011-04-10)
B-325
Parameter Bridge Switch Mode
Value Range l IVL/Ingress Filter Enable (supported by the 802.1q bridge and 802.1ad bridge, unsupported by the 802.1d bridge) l SVL/Ingress Filter Disable (supported by the 802.1d bridge and 802.1ad bridge, unsupported by the 802.1q bridge)
Default Value l IVL/Ingress Filter Enable (the 802.1q bridge and the 802.1ad bridge) l SVL/Ingress Filter Disable (the 802.1d bridge)
Description l When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables. l If the ingress filter is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filter is disabled, the preceding described check is not conducted.
Bridge Learning Mode Ingress Filter MAC Address Selflearning
Displays the bridge learning mode. Displays whether the ingress filter function is enabled. Displays whether the MAC address selflearning function of the bridge is enabled.
Table B-23 Parameters of service mounting Parameter VB Port Mount Port Value Range Default Value Description Displays the ID of the logical port of the bridge. Displays or specifies the external port or VCTRUNK on the Ethernet switching board that is connected to the bridge. Displays the network attribute of the external port/VCTRUNK connected to the bridge. Displays or specifies whether the external port connected to the bridge is enabled. This parameter is invalid in the case of Ethernet LAN services based on 802.1ad bridge.
Port Type
Port Enabled
Disabled Enabled
TAG
B-326
Issue 03 (2011-04-10)
Parameter Default VLAN ID
Value Range -
Default Value -
Description Displays or specifies the default VLAN ID. This parameter is valid only when TAG is set to Access or Hybrid.
Working Mode
Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex
Auto-Negotiation
Displays or specifies the working mode of the external port.
Service Direction C-VLAN
Displays the service direction. Displays or specifies the C-VLAN ID that the data frames carry. Is valid only when the bridge is an IEEE 802.1ad bridge and Operation Type is set to Add S-VLAN Base for Port and CVLAN. Specifies the mapping relationship between the C-VLAN ID carried by the data frames and the S-VLAN ID to be added.
S-VLAN
Displays or specifies the S-VLAN ID that the data frames carry. l When Operation Type is set to Add SVLAN Base for Port, this parameter specifies that the data frames that enter the IEEE 802.1ad bridge need to be added with the S-VLAN ID. l When Operation Type is set to Add SVLAN Base for Port and C-VLAN, this parameter and C-VLAN specify the mapping relationship between the SVLAN ID to be added and the C-VLAN ID carried by the data frames that enter the IEEE 802.1ad bridge. l When Operation Type is set to Mount Port, this parameter is invalid. l When Operation Type is set to Mount Port and Base for Port and S-VLAN, this parameter specifies the S-VLAN ID to be carried by the data frames that enter the IEEE 802.1ad bridge.
S-VLAN Priority C-VLAN Priority
Displays or specifies the S-VLAN priority. Displays or specifies the C-VLAN priority.
Issue 03 (2011-04-10)
B-327
Table B-24 Parameters of service mounting Parameter Operation Type Value Range Add S-VLAN base for port Add S-VLAN base for Port and CVLAN Mount Port Mount Port and base for Port and SVLAN VB Port Mount Port Specifies the ID of the logical port of the bridge. Selects the external port or VCTRUNK on the Ethernet switching board that is connected to the bridge. Displays the port type. Is valid only when Operation Type is set to Add S-VLAN Base for Port and CVLAN. Specifies the mapping relationship between the C-VLAN ID carried by the data frames and the S-VLAN ID to be added. S-VLAN 1-4095 l When Operation Type is set to Add SVLAN Base for Port, this parameter specifies that the data frames that enter the IEEE 802.1ad bridge need to be added with the S-VLAN ID. l When Operation Type is set to Add SVLAN Base for Port and C-VLAN, this parameter and C-VLAN specify the mapping relationship between the SVLAN ID to be added and the C-VLAN ID carried by the data frames that enter the IEEE 802.1ad bridge. l When Operation Type is set to Mount Port, this parameter is invalid. l When Operation Type is set to Mount Port and Base for Port and S-VLAN, this parameter specifies the S-VLAN ID to be carried by the data frames that enter the IEEE 802.1ad bridge. Default Value Add S-VLAN base for port Description For the meaning of each operation type, see Application of the QinQ Technology in 802.1ad Bridge Services.
Port Type C-VLAN
1-4095
B-328
Issue 03 (2011-04-10)
Parameter S-VLAN Priority
Value Range AUTO Priority 0 to Priority 7
Default Value AUTO
Description Specifies the S-VLAN priority.
C-VLAN Priority Port Enabled Service Direction
AUTO -
AUTO -
Specifies the C-VLAN priority. Displays or specifies whether the external port connected to the bridge is enabled. Displays the service direction.
Issue 03 (2011-04-10)
B-329
Related Tasks
A.7.2.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

This section describes the parameters for creating an Ethernet LAN service.
Navigation Path
In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.

Table B-26 Parameters on the main interface Parameter Board VB ID VB Name Value Range Default Value Description Displays the board that is configured with a bridge. Displays the ID of the bridge. This parameter is a character string that describes the bridge. It is recommended that you set this character string to a value that indicates the specific purpose of the bridge. Displays the type of the bridge. Displays the switching mode of the bridge. Displays the learning mode of the bridge. Displays whether the filtering function is enabled at the ingress port. Displays whether the MAC address selflearning of the bridge is enabled.
Bridge Type Bridge Switch Mode Bridge Learning Mode Ingress Filter MAC Address selfLearning
Table B-27 Parameters for mounting services Parameter VB Port Mount Port Value Range Default Value Description Displays the ID of the logical port of the bridge. Displays or specifies which physical port or VCTRUNK on the Ethernet switch board is mounted to the bridge.
Issue 03 (2011-04-10)
B-330
Parameter Port Type Port Enabled Hub/Spoke
Value Range Hub Spoke
Default Value Hub
Description Displays the network attribute of the port mounted to the bridge. Displays or specifies whether the port mounted to the bridge is enabled. Displays or specifies the Hub/Spoke attribute of the port mounted to the bridge. l Hub ports can mutually access each other. l Hub ports and Spoke ports can mutually access each other. l Spoke ports cannot mutually access each other.
TAG
Displays or specifies the TAG attribute of the mounted port in the case of Ethernet LAN services based on 802.1d bridge or 802.1q bridge. This parameter is invalid in the case of Ethernet LAN services based on 802.1ad bridge.
Default VLAN ID
Displays or specifies the default VLAN ID of the port mounted to the bridge. This parameter is valid only when you set the tag attribute of the port to Access or Hybrid.
Working Mode Service Direction C-VLAN
Displays or specifies the working mode of the port mounted to the bridge. Displays the direction of the service. Displays or specifies the C-VLAN ID carried by the data frame. This parameter is valid only when the bridge is an IEEE 802.1ad bridge and Operation Type is Add S-VLAN Base for Port and C-VLAN. This parameter specifies the mapping relation between the C-VLAN tag carried by the data frame and the S-VLAN tag to be added.
Issue 03 (2011-04-10)
B-331
Parameter S-VLAN
Value Range -
Default Value -
Description Displays or specifies the S-VLAN ID carried by the data frame. l When Operation Type is set to Add SVLAN Base for Port, this parameter specifies the S-VLAN to be added to the data frames that enter the IEEE 802.1ad bridge. l When Operation Type is set to Add SVLAN Base for Port and C-VLAN, this parameter and C-VLAN specify the mapping relation between the S-VLAN tag to be added and the C-VLAN tag carried by the data frame that enters the IEEE 802.1ad bridge. l When Operation Type is set to Mount Port, this parameter is invalid. l When Operation Type is set to Mount Port and Base for Port and S-VLAN, this parameter specifies the S-VLAN tag to be carried by the data frames that enter the IEEE 802.1ad bridge.
S-VLAN Priority C-VLAN Priority
Displays the priority of the S-VLAN. Displays the priority of the C-VLAN.
Table B-28 Parameters for VLAN filtering table Parameter VLAN ID VB Port Forwarding Physical Port Value Range Default Value Description Displays the VLAN ID that needs to be filtered in forwarding. Displays the ID of the logical port of the bridge. Displays the actually specified forwarding port. l Selected forwarding ports can send packets only among themselves. l Selected forwarding ports can only forward the packet that carries the VLAN ID tag. These ports discard the packet that carries other VLAN tags. l The broadcast packets transmitted by any of Selected forwarding ports can be forwarded only among Selected forwarding ports.
Table B-29 Parameters for VLAN unicast Parameter VLAN ID Value Range Default Value Description l This parameter is invalid for the 802.1d bridge and the 802.1ad bridge that adopt the SVL learning mode. The entry applies to all VLANs. l In the case of the 802.1d bridge and the 802.1ad bridge that adopt the SVL learning mode, the entry applies to only the VLAN with the ID specified by this parameter. l Set this parameter according to the planning information. MAC Address l Displays or specifies the static MAC address. l A static MAC address is an address that is set manually. It does not age automatically and needs to be deleted manually. l Generally, a static MAC address is used for the port that receives but does not forward Ethernet service packets or the port whose MAC address need not age automatically. VB Port Physical Port Displays the ID of the logical port of the bridge. l Specifies the Ethernet port that corresponds to the MAC address. l Set this parameter according to the planning information. Aging Status Displays the aging status of the entries.
Table B-30 Parameters for disabling MAC addresses Parameter VLAN ID Value Range Default Value Description Displays or specifies the VLAN ID of the service. A disabled MAC address is valid for the VLAN with the ID as specified by this parameter.
Issue 03 (2011-04-10)
B-333
Parameter MAC Address
Value Range -
Default Value -
Description l Displays or specifies the disabled MAC address. A disabled MAC address is also called a blacklisted MAC address. l The data frame that contains a disabled destination MAC address is discarded. A disabled MAC address needs to be set manually and does not age.
Table B-31 Parameters for bound paths Parameter VCTRUNK Port Level Service Direction Bound Path Number of Bound Paths Value Range Default Value Description Displays the VCTRUNK to bind VC paths. Displays the level of the bound VC paths. Displays the direction of the bound VC paths. Displays the bound paths. Displays the number of bound paths.
Table B-32 Parameters for self-learned MAC addresses Parameter MAC Address Value Range Default Value Description l Displays or specifies the self-learned MAC address. A self-learned MAC address is also called a dynamic MAC address. l The entries of self-learned MAC addresses are obtained when the bridge uses the SVL or IVL learning mode. A self-learned MAC address ages. VB Port Displays the ID of the logical port of the bridge.
B-334
Issue 03 (2011-04-10)
Parameter VLAN ID
Value Range -
Default Value -
Description l If the bridge uses the SVL learning mode, this parameter is invalid. That is, the preset self-learned MAC address entries are valid for all VLANs. l If the bridge uses the IVL learning mode, the preset self-learned MAC address entries are valid only for the VLAN with the ID specified by this parameter. l Set this parameter according to the planning information.
Table B-33 Parameters for VLAN MAC address table capacity Parameter VLAN ID Actual MAC Address Table Capacity Value Range Default Value Description Displays the VLAN ID specified for querying the self-learned MAC addresses. Displays how many MAC addresses are actually self-learned in the query condition of a specific VLAN ID.
Table B-34 Parameters for VB port MAC address table capacity Parameter VB Port Value Range Default Value Description Displays the ID of the logical port of the bridge. The ID is specified for querying the self-learned MAC addresses. Displays how many MAC addresses are actually self-learned in the query condition of a specific VB port.
Actual MAC Address Table Capacity
Related Tasks
A.7.3.1 Creating a Static MAC Address Entry A.7.3.2 Creating a Blacklist Entry of a MAC Address A.7.3.4 Querying or Deleting a Dynamic MAC Address A.7.3.5 Querying the Actual Capacity of a MAC Address Table
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation

This section describes the parameters for creating VLAN filtering tables.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
NOTE
In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB must be IVL.
3.
Click New.

Table B-35 Parameters on the main interface Parameter VB VLAN ID(e.g. 1,3-6) Value Range 1-4095 Default Value 1 Description Displays the bridge whose VLAN filtering table is to be created. Specifies the VLAN IDs in the VLAN filtering table. l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l Set this parameter as required. Available forwarding ports Selected forwarding ports Displays the ports mounted to the bridge. Displays the selected forwarding ports. l The selected forwarding ports can send packets only among themselves. l The selected forwarding ports can only forward the packet that carries the VLAN ID (e.g:1,3-6) tag. These ports discard the packet that carries other VLAN tags. l The broadcast packet that carries the VLAN ID(e.g.1,3-6) tag can be forwarded only among the selected forwarding ports.
Related Tasks
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries

This section describes the parameters associated with the aging time of MAC address table entries, which need to be set on the NMS.
Navigation Path
In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree.

Table B-36 Parameters on the main interface Parameter Board MAC Address Aging Time Value Range l 1 to 120 Min l 1 to 120 Hour l 1 to 120 Day Default Value 5 Min Description Displays the Ethernet board. l If one entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this entry is deleted automatically. This mechanism is called aging, and this period is called the aging time. l If you set this parameter to a very large value, the bridge stores excessive MAC address table entries that are outdated, which exhausts the resources of the MAC address forwarding table. l If you set this parameter to a very small value, the bridge may delete the MAC address table entry that is required, which reduces the forwarding efficiency. l It is recommended that this parameter takes the default value.
Related Tasks
A.7.3.3 Setting the Aging Time of a MAC Address Table Entry
B.7.2 Parameters for Ethernet Protocols

This section describes the parameters for EoPDH-plane Ethernet protocols. B.7.2.1 Parameter Description: Spanning Tree_Protocol Enabling This section describes the parameters for the types of spanning tree protocols and for enabling the spanning tree protocols. B.7.2.2 Parameter Description: Spanning Tree_Bridge Parameters
This section describes the parameters for the spanning tree protocol. B.7.2.3 Parameter Description: Spanning Tree_Port Parameters This section describes the parameters associated with the spanning tree protocol, which need to be set on the NMS. B.7.2.4 Parameter Description: Spanning Tree_Bridge Running Information This section describes the parameters associated with the type and enabled status of the spanning tree protocol, which need to be set on the NMS. B.7.2.5 Parameter Description: Spanning Tree_Port Running Information This section describes the parameters associated with the type and enabled status of the spanning tree protocol, which need to be set on the NMS. B.7.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute This section describes the parameters associated with the point-to-point attribute of the spanning tree protocol, which need to be set on the NMS. B.7.2.7 Parameter Description: IGMP Snooping Protocol_Enabling This section describes the parameters for enabling the IGMP snooping protocol. B.7.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries This section describes the parameters for creating static multicast table entries. B.7.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries This section describes the parameters for the aging time of multicast table entries. B.7.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs This topic describes the parameters for creating a link aggregation group (LAG). B.7.2.11 Parameter Description: Ethernet Link Aggregation_Link Aggregation This section describes the parameters for port priorities and system priorities. B.7.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT This section describes the parameters for creating point-to-point service LPT. B.7.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT This section describes the parameters for creating point-to-multipoint service LPT. B.7.2.14 Parameter Description: Port Mirroring_Creation This section describes the parameters for creating port mirroring tasks.
B.7.2.1 Parameter Description: Spanning Tree_Protocol Enabling

This section describes the parameters for the types of spanning tree protocols and for enabling the spanning tree protocols.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Protocol Enabled tab.
2.
B-338

Table B-37 Parameters on the main interface Parameter VB Protocol Enabled Value Range Enabled Disabled Default Value Disabled Description Displays the created bridge. l Indicates whether to enable the spanning tree protocol. l Try to avoid Layer 2 service loopbacks in the service networking. If no loop occurs, you need not start the STP/ RSTP. l If the loop is already formed in the service networking, you must start the STP or RSTP. Protocol Type STP RSTP RSTP l This parameter is valid only when Protocol Enabled is Enabled. l The protocol type should be set according to the requirement of the interconnected Ethernet equipment. The default value is recommended unless otherwise specified.
Related Tasks
A.7.5.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
B.7.2.2 Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Bridge Parameters tab.
2.

Table B-38 Parameters on the main interface Parameter VB Value Range Default Value Description Displays the created bridge.
Issue 03 (2011-04-10)
B-339
Parameter Priority
Value Range 0-61440
Default Value 32768
Description l The most significant 16 bits of the bridge ID indicate the priority of the bridge. l When the value is smaller, the priority is higher. As a result, the bridge is more likely to be selected as the root bridge. l If the priorities of all the bridges on the STP network take the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
MAC Address Max Age(s)
6-40
20
Displays the MAC address of a bridge. l Indicates the maximum age of the CBPDU packet that is recorded by the port. l The greater the value, the longer the transmission distance of the CBPDU packet, and the greater the network diameter. When the value of this parameter is greater, however, the link fault detection of the bridge is slower and thus the network adaptability is reduced.
Hello Time(s)
1-10
l Indicates the interval for transmitting CBPDU packets through the bridge. l The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. As the value of this parameter increases, however, the topology stability decreases.
Forward Delay(s)
4-30
15
l Indicates the holding time of a port in the listening state and in the learning state. l The greater the value, the longer the delay of the network state change. Therefore, the topology changes are slower and recovery in the case of faults is slower.
TxHoldCout(per second)
1-10
Indicates how many times the port transmits CBPDU packets in every second.
Related Tasks
B-340
Issue 03 (2011-04-10)
B.7.2.3 Parameter Description: Spanning Tree_Port Parameters

This section describes the parameters associated with the spanning tree protocol, which need to be set on the NMS.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Port Parameters tab.

Table B-39 Parameters on the main interface Parameter Port Priority Value Range 0-240 Default Value 128 Description Displays the created bridge. l The most significant eight bits of the port ID indicate the port priority. l The smaller the value of this parameter, the higher the priority. Port Path Cost 1-200000000 l Indicates the status of the network to which the port is connected. l In the case of the bridges on both ends of the path, set this parameter to the same value. Status Admin Edge Attribute Enabled Disabled Disabled Displays the state of a port. l Is valid only when the RSTP is used. l Specifies whether to set the port to an edge port. The edge port refers to the bridge port that is connected only to the LAN. The edge port receives the BPDU and does not transmit the BPDU. l Set this parameter to Enabled only when the Ethernet port on the Ethernet board is directly connected to the data communication terminal equipment, such as a computer. In other cases, it is recommended that this parameter takes the default value.
Issue 03 (2011-04-10)
B-341
Parameter Protocol Enabled
Description l Specifies whether the STP or RSTP is enabled for the port. l When this parameter is set to Disabled, the port does not process or transmit the BPDU. l It is recommended that this parameter takes the default value.
Auto Edge Detection
Enabled Disabled
Disabled
l Is valid only when Admin Edge Attribute is set to Enabled. l When this parameter is set to Enabled, if the bridge detects that this port is connected to the port of another bridge, the RSTP considers this port as a nonedge port. l When Admin Edge Attribute is set to Enabled, set this parameter to Enabled. In other cases, it is recommended that this parameter takes the default value.
Related Tasks
B.7.2.4 Parameter Description: Spanning Tree_Bridge Running Information

This section describes the parameters associated with the type and enabled status of the spanning tree protocol, which need to be set on the NMS.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Bridge Running Information tab.

Table B-40 Parameters on the main interface Parameter VB Priority Value Range Default Value Description Displays the created bridge. Displays the priority of the bridge. The most significant 16 bits of the bridge ID indicate the priority of the bridge.
Issue 03 (2011-04-10)
B-342
Parameter MAC Address Designed Root Bridge Priority Designed Root Bridge MAC Address Root Path Cost
Value Range -
Default Value -
Description Displays the MAC address of the bridge. Displays the priority of the specified bridge. Displays the MAC address of the specified bridge. Displays the root path cost. The root path cost is the path cost of the root port and is used for calculating the network topology. Displays the root port of the spanning tree protocol. Displays the maximum age of the CBPDU packet that is recorded by the port. Displays the interval for transmitting the CBPDU packets through the bridge. Displays the holding time of a port in listening state and in learning state. Displays the number of times that each port transmits CBPDU packets per second.
Root Port Max Age(s) Hello Time(s) Forward Delay(s) HoldCout
Related Tasks
B.7.2.5 Parameter Description: Spanning Tree_Port Running Information

This section describes the parameters associated with the type and enabled status of the spanning tree protocol, which need to be set on the NMS.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Port Running Information tab.

Table B-41 Parameters on the main interface Parameter Port
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description Displays the logical port of the bridge.

B-343
Parameter Port ID Port Status Port Path Cost Designated Port D Designated Root Bridge Priority Designated Root Bridge MAC Address Designated Path Cost Designated Bridge Priority Designated Bridge MAC Address Topology Detection Edge Port Status Running Time(s)
Value Range -
Default Value -
Description Displays the port ID. Displays the port status. Displays the port path cost. Displays the ID of the specified port. Displays the priority of the specified root bridge. Displays the MAC address of the specified root bridge. Displays the specified path cost. Displays the priority of the specified bridge. Displays the MAC address of the specified bridge. Displays the enabled status of topology detection. Displays the enabled status of the edge port. Displays the duration when the topology remains unchanged.
Related Tasks
B.7.2.6 Parameter Description: Spanning Tree_Point-to-Point Attribute

This section describes the parameters associated with the point-to-point attribute of the spanning tree protocol, which need to be set on the NMS.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board, and choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Click the Point to Point Attribute tab.
B-344
Issue 03 (2011-04-10)

Table B-42 Parameters on the main interface Parameter Port Point-to-point Attribute Value Range Adaptive connection Link connection Shared media Default Value Adaptive connection Description Displays the internal and external ports on the Ethernet board. l This parameter is valid only when the RSTP is used. l If this parameter is set to Adaptive connection, the bridge determines the actual point-to-point attribute of the port according to the actual working mode of the port. If the port works in full-duplex mode, the actual point-to-point attribute of the port is True. If the port works in half-duplex mode, the actual point-topoint attribute of the port is False. l If you set this parameter to Link connection, the actual point-to-point attribute of the port is True. l If you set this parameter to Shared media, the actual point-to-point attribute of the port is False. l Only the port whose actual point to point attribute is True can transmit the fast transition request and response messages. l It is recommended that this parameter takes the default value.
Related Tasks
B.7.2.7 Parameter Description: IGMP Snooping Protocol_Enabling

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Click the Enable IGMP Snooping Protocol tab.
2.
Issue 03 (2011-04-10)
B-345

Parameter Board VB Protocol Enable Value Range Enabled Disabled Default Value Disabled Description Displays the board name. Displays the ID of the bridge. l Specifies whether to enable the IGMP snooping protocol. l If the IGMP multicast router exists on the interconnected Ethernet network, enable the IGMP snooping protocol according to the requirements of the router. The Discarded Tag of the Packet Excluded in the Multicast Group Enabled Disabled Enabled l This parameter specifies the method of the port to process unknown multicast packets. When the IEEE 802.1q or 802.1ad bridge receives the multicast packets whose multicast addresses are not included in the multicast table, these packets are considered as unknown packets. l This parameter is valid only when Protocol Enable is Enabled. l If this parameter is set to Enabled, unknown multicast packets are discarded. l If this parameter is set to Disabled, unknown multicast packets are broadcast in the VLAN. l Set this parameter as required by the IGMP multicast server. Max.NonResponse Times 1 to 4 3 If the bridge transmits an IGMP group query packet to the multicast member ports, the router port starts the timer for the query of the maximum response time. If the bridge does not receive the IGMP report packet within the maximum response time, the bridge adds one to the no-response times of the multicast member port. When the noresponse times of the port exceed the preset threshold, the bridge deletes the multicast member from the multicast group.
Related Tasks
A.7.6.1 Configuring the IGMP Snooping Protocol
B-346
Issue 03 (2011-04-10)
B.7.2.8 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries
This section describes the parameters for creating static multicast table entries.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Click the Static Multicast Table tab. Click New.
2. 3.

Parameter VB ID VLAN ID MAC Address Value Range Default Value Description Displays the ID of the created bridge. Specifies the VLAN ID of the static multicast table entry. l Specifies the MAC address in the static multicast table. l Set this parameter as required. Multicast Port l Specifies the port as an entry in the static multicast table. l An entry in the static multicast table does not age.
Related Tasks
A.7.6.2 Configuring Static Multicast Entries
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries
This section describes the parameters for the aging time of multicast table entries.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Click the Multicast Aging Time tab.
2.
Issue 03 (2011-04-10)
B-347

Parameter Board Multicast Aging Time(Min) Value Range 1-120 Default Value 8 Description Displays the board name. l Specifies the aging time for multicast table entries. When a dynamic multicast table entry is not updated in a certain period (that is, no IGMP request from this multicast address is received), this entry is automatically deleted. This mechanism is called aging, and this period is called aging time. l If this parameter is set to a very great value, the bridge stores excessive multicast table entries that are no longer needed, which exhausts the resources of the multicast table. l If this parameter is set to a very small value, the bridge may delete the multicast table entry that is needed, which reduces the forwarding efficiency. l The default value is recommended.
Related Tasks
A.7.6.3 Modifying the Aging Time of a Multicast Table Entry
B.7.2.10 Parameter Description: Ethernet Link Aggregation_Creation of LAGs

This topic describes the parameters for creating a link aggregation group (LAG).
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Click the Link Aggregation Group Management tab. Click New.
2. 3.
Attribute Parameters
Parameter LAG No LAG Name Value Range 1-12 Default Value 1 Description Specifies the LAG number. Specifies the LAG name.
B-348
Issue 03 (2011-04-10)
Parameter LAG Type
Value Range Static Manual
Description l Static: A static LAG is created by the user. To add or delete a member port, you need to run the Link Aggregation Control Protocol (LACP) protocol. In a static LAG, a port can be in selected, standby, or unselected state. By running the LACP protocol, devices exchange aggregation information so that they share the same aggregation information. l Manual: A manual LAG is created by the user. When you add or delete a member port, you need not run the LACP protocol. In a manual LAG, a port can be in the UP or DOWN state. The system determines whether to aggregate a port according to its physical state (UP or DOWN), working mode, and rate.
Load Sharing
Sharing Non-Sharing
Sharing
l Sharing: In a sharing LAG, all member ports always share the traffic load. The sharing mode can improve bandwidth utilization on a link. When the member ports are changed or some member ports fail, the traffic load of each member port is automatically re-allocated. l Non-Sharing: In a non-sharing LAG, only one member port carries the traffic load and the other member ports are in Standby state. Actually, a non-sharing LAG works in hot-standby mode. When the active port fails, the system selects a standby port to substitute for the failed port, thus preventing a link failure.
Sharing Mode
IP Sharing Mode MAC Sharing Mode
IP Sharing Mode
You can set this parameter only when Load Sharing is Sharing. l You can set this parameter only when Load Sharing is Non-Sharing. l If this parameter is set to Revertive, services are automatically switched back to the working path after the working path recovers. l If this parameter is set to NonRevertive, services are still transmitted in the protection path after the working path recovers and the LAG remains the same.
Revertive Mode
Revertive Non-Revertive
Revertive
Issue 03 (2011-04-10)
B-349
Port Setting Parameters

Parameter Main Port Value Range Default Value Description l Specifies the main port in a LAG. l After a LAG is created, you can add Ethernet services to the main port only. That is, services cannot be added to a slave port. l When Load Sharing is set to NonSharing, the link connected to the main port is the working path and the links connected to the slave ports are protection paths. Available Standby Ports l Specifies the salve port in a LAG. l After a LAG is created, you need to perform manual operations to add or delete a slave port. Displays the selected slave ports.
Selected Standby Ports
Related Tasks

This section describes the parameters for port priorities and system priorities.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Click the Link Aggregation Parameters tab.
2.

Parameter Port Port Priority Value Range 0-65535 Default Value 32768 Description Displays the port name. l This parameter is valid only when LAG Type of a LAG is set to Static. l This parameter indicates the priorities of the ports in a LAG as defined in the LACP protocol. The smaller the value, the higher the priority.
B-350
Issue 03 (2011-04-10)
Parameters for the system settings

Parameter System Priority Value Range 0-65535 Default Value 32768 Description l This parameter is valid only when LAG Type of a LAG is set to Static. l This parameter indicates the priority of a LAG. The smaller the value, the higher the priority. l When the local LAG and the opposite LAG negotiate through LACP packets, one can obtain the system priority of the other. The LAG with the higher system priority is considered as the comparison result. Then, the aggregation information is consistent at both ends. If the local LAG and the opposite LAG have the same system priority, the MAC addresses are compared. The LAG with a lower MAC address is considered as the comparison result. Then, the aggregation information is consistent at both ends. System MAC Address Displays the MAC address of the system.
Related Tasks
B.7.2.12 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT

This section describes the parameters for creating point-to-point service LPT.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Click Query.
2.

Parameter Port VCTRUNK Port Value Range Default Value Description Displays the port name. Displays the VCTRUNK used by the Ethernet service.
B-351
Issue 03 (2011-04-10)
Parameter Direction
Value Range -
Default Value -
Description l Displays the direction of the Ethernet service at the port. l The service direction is set to positive when the source port is a PORT and the sink port is a VCTRUNK; the service direction is set to reverse when the source port is a VCTRUNK and the sink port is a PORT.
LPT
Yes No
No
Specifies whether to enable the LPT.
Bearer Mode
GFP(HUAWEI) Ethernet GFP-CSF
GFP(HUAWEI)
l Specifies the bearer mode of the LPT packets. l The default value is recommended.
PORT-Type Port Hold-Off Time(ms)
0-10000
100
l When the link on which Ethernet services are transmitted is configured with other protection schemes, you need to set the hold-off time of LPT. This enables the NE to notify the equipment at both ends of a transmission network of the fault on the transmission link only when the other protection schemes fail. l This parameter is valid only in the positive direction of LPT.
VCTRUNK Port Hold-Off Time(ms)
0-10000
100
l When the link on which Ethernet services are transmitted is configured with other protection schemes, you need to set the hold-off time of LPT. This enables the NE to notify the equipment at both ends of a transmission network of the fault on the transmission link only when the other protection schemes fail. l This parameter is valid only in the reverse direction of LPT.
Related Tasks
A.7.10.1 Configuring LPT for Point-to-Point Services
B.7.2.13 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT

This section describes the parameters for creating point-to-multipoint service LPT.
B-352
Issue 03 (2011-04-10)
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Click PtoMP LPT. Then, the LPT Management dialog box appears. Click New.
2. 3.
Parameters for Convergence Points

Parameter Port Bearer Mode Value Range GFP(HUAWEI) Ethernet GFP-CSF Port Hold-Off Time(ms) 0-10000 0 Default Value GFP(HUAWEI) Description Specifies the port of the convergence point. l This parameter can be set only when the selected port is a VCTRUNK. l The default value is recommended. When the link on which Ethernet services are transmitted is configured with other protection schemes, you need to set the hold-off time of LPT. This enables the NE to notify the equipment at both ends of a transmission network of the fault on the transmission link only when the other protection schemes fail.
Parameters for Access Points

Parameter Port Bearer Mode Value Range GFP(HUAWEI) Ethernet GFP-CSF Default Value GFP(HUAWEI) Description Specifies the port at the access node. l This parameter can be set only when the selected port is a VCTRUNK. l The default value is recommended.
Related Tasks
A.7.10.2 Configuring LPT for Point-to-Multipoint Services
B.7.2.14 Parameter Description: Port Mirroring_Creation

This section describes the parameters for creating port mirroring tasks.
Issue 03 (2011-04-10)
B-353
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Interface Management > Port Mirroring from the Function Tree. Click New.
2.

Parameter Board Mirror Listener Port Value Range Default Value Description Displays the board name. l After the mirroring function of the port is configured, you can monitor all the mirrored ports by analyzing the packets at the mirroring port only. As a result, you can easily manage the ports. l Mirror Listener Port indicates the port that sends the packets copied from Uplink Listened Port and Downlink Listened Port. l Mirror Listener Port cannot be set to a port that carries any service. Mirrored Upstream Port Mirrored Downstream Port l Mirrored Upstream Port and Mirrored Downstream Port indicate the ports that copy packets for Mirror Listener Port. l Mirrored Upstream Port can be a PORT or a VCTRUNK. As a PORT, the port copies the packets that it receives; as a VCTRUNK, the port copies the packets that it transmits. Mirror Listener Port sends the packets copied from Mirrored Upstream Port. l Mirrored Downstream Port can be a PORT or a VCTRUNK. As a PORT, the port copies the packets that it transmits; as a VCTRUNK, the port copies the packets that it receives. Mirror Listener Port sends the packets copied from Mirrored Downstream Port.
NOTE The transmit direction and receive direction mentioned in this section are related to the local NE.
B.7.3 Parameters for the Ethernet OAM

This section describes the parameters for the Ethernet OAM on the EoPDH plane.
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs This topic describes the parameters for creating maintenance domains (MDs). B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs This section describes the parameters for creating maintenance associations (MAs). B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs This section describes the parameters for creating a maintenance point (MP). B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB This section describes the parameters for enabling the LB. B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT This topic describes the parameters for enabling the LT. B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter This section describes the OAM parameters that are related to Ethernet ports. B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring This section describes the parameters for monitoring the OAM error frames at the Ethernet port. B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter This section describes the parameters for monitoring the OAM errored frames at the Ethernet port.
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs

This topic describes the parameters for creating maintenance domains (MDs).
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. In the right pane, click OAM Configuration. Click New and choose Create MD from the drop-down list.
2. 3.

Table B-43 Parameters on the main interface Parameter Maintenance Domain Name Value Range For example: MD1 Default Value Description Specifies the name of the MD.
Issue 03 (2011-04-10)
B-355
Parameter Maintenance Domain Level
Value Range Consumer High(7) Consumer Middle(6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0)
Default Value Operator Low(0)
Description Specifies the level of the MD. The greater the value, the higher the level.
Related Tasks
A.7.8.1 Creating MDs
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs

This section describes the parameters for creating maintenance associations (MAs).
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. In the right pane, click OAM Configuration. Click New and choose Create MA from the drop-down list.
2. 3.

Table B-44 Parameters on the main interface Parameter Maintenance Domain Name Maintenance Association Name Value Range For example: MD1 For example: MA1 Default Value Description Displays the MD in which an MA is to be created. This parameter specifies the name of the MA, which is a service-related domain. By creating MAs, the connectivity check (CC) can be performed on the network that transmits a particular service instance.
B-356
Issue 03 (2011-04-10)
Related Tasks
A.7.8.2 Creating MAs
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs

This section describes the parameters for creating a maintenance point (MP).
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Click New.
2.

Table B-45 Parameters on the main interface Parameter Maintenance Domain Name Value Range Default Value NULL Description Specifies the maintenance domain (MD) of the MP.
NOTE An MD is not required for a common MP. For the creation of a common MP, select NULL.
Maintenance Association Name
NULL
Specifies the maintenance association (MA) of the MP.

NOTE An MA is not required for a common MP. For the creation of a common MP, select NULL.
Node VLAN ID
Specifies the port where you want to create an MP. l Configures the ID of the VLAN to which the service of the MP belongs. The information is contained in the OAM data packet. The MPs with the same VLAN ID in an MD can communicate with each other. l This parameter can be null in the case of PORT services, but need to be set in the case of PORT+VLAN services.
MP ID
Standard MP: 00-00-0000 to FFFF-1FFF Common MP: 00-00-0000 to FFFF-FF00
00-00-0000
Uniquely identifies an MP. From the highest to the lowest, the first byte indicates the network number, the second byte indicates the number of the node in the local network, and the third and forth bytes indicate the ID of the MP on the network node. The MP ID must be unique in the entire network.
B-357
Issue 03 (2011-04-10)
Parameter Type
Value Range MEP MIP
Default Value MEP
Description Specifies the MP type defined in IEEE 802.1ag. An MP can be a maintenance association end point (MEP) or a maintenance association intermediate point (MIP). l Specifies the direction of the MEP. l Set this parameter to Ingress if the OAM data initiated by the MEP travels through the Ethernet switching unit on the local NE. Otherwise, set this parameter to Egress.
Direction
Ingress Egress
Ingress

Table B-46 Parameters for advanced attributes Parameter Level Value Range Consumer High(7) Consumer Middle (6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0) CC Status Active Inactive LB Timeout(ms) 3000 to 60000, in step of 100 5000 Inactive Specifies whether to enable the connectivity check (CC) function at an MP. l Specifies the timeout duration of an LB test. l This parameter can be set only for an MEP. LT Timeout(ms) 3000 to 60000, in step of 100 5000 l Specifies the timeout duration of an LT test. l This parameter can be set only for an MEP. Default Value Provider High(4) Description Specifies the level of a common MP. The greater the value, the higher the level.
NOTE This parameter is valid only for a common MP (NULL).
B-358
Issue 03 (2011-04-10)
Parameter CCM Sending Period(ms)
Value Range Standard MP: 1000 10000 6000 600000 Common MP: 1000 to 60000, in step of 100
Default Value Standard MP 1000 Common MP: 5000
Description Specifies the interval for sending the CCM packet at the MP where the CC test is performed. l If this parameter takes a very small value, service bandwidth decreases significantly. l If this parameter takes a very great value, the CC test will become less capable in detecting service interruptions. The default value is recommended. l This parameter can be set only for an MEP.
Related Tasks
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB

This section describes the parameters for enabling the LB.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Select the node that requires an LB test, click OAM Operation, and select Start LB.
2.

Table B-47 Parameters on the main interface Parameter LB Source MP ID Value Range Default Value Description Specifies the ID of the source maintenance point in the LB test. Specifies the ID of the sink maintenance point in the LB test. Indicates the result of one LB test.
LB Sink MP ID
Test Result
Issue 03 (2011-04-10)
B-359
Parameter Test based on the MAC Address
Value Range Selected Not selected
Default Value Not selected
Description Select this parameter for an LB test based on MAC addresses.

NOTE This parameter is valid only for a standard MP.
LB Sink MP MAC Address
Specifies the MAC address of the sink maintenance point in the LB test. This parameter is valid only in the case of Test based on the MAC Address.
Related Tasks
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT

This topic describes the parameters for enabling the LT.
Navigation Path
1. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Select the node that requires an LT test, click OAM Operation, and select Start LT.
2.

Table B-48 Parameters on the main interface Parameter LT Source MP ID LT Sink MP ID Responding MP ID Responding MP Type Value Range Default Value Description Specifies the source MP in the LT test. Specifies the sink MP in the LT test. Displays the MP that responds to the test. Displays the type of the MP that responds to the test.
B-360
Issue 03 (2011-04-10)
Parameter Hop Count
Value Range -
Default Value -
Description Displays the count of hops between the source MP and the responding MP. That is, the number of responding MPs from the source MP to a certain responding MP in an LT test. Indicates the result of one LT test.
Test Result
Related Tasks
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter

This section describes the OAM parameters that are related to Ethernet ports.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click the OAM Parameter tab.

Table B-49 Parameters on the main interface Parameter PORT Enable OAM Protocol Value Range Enabled Disabled Default Value Disabled Description Displays the name of the external Ethernet port. Specifies whether the point-to-point OAM protocol (IEEE 802.3ah protocol) is enabled. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the opposite end.
Issue 03 (2011-04-10)
B-361
Parameter OAM Working Mode
Value Range Active Passive
Default Value Active
Description The negotiation mode of IEEE 802.3ah includes active and passive modes. If this parameter is set to Active, the port can initiate an OAM connection. If this parameter is set to Passive, the port can only respond to the OAM connection requests from the opposite end.
Remote Alarm Support for Link Event
Enabled Disabled
Enabled
Specifies whether the detected link event is notified to the opposite end (for example, error frame periods, error frames, and error frame seconds). Displays the maximum length of the OAM packets. This parameter takes the same value as the Maximum Frame Length of the external port.
Max OAM Packet Length(byte)
Loopback Status
Displays the loopback status.
Related Tasks
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring

This section describes the parameters for monitoring the OAM error frames at the Ethernet port.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click the OAM Error Frame Monitor tab.
B-362
Issue 03 (2011-04-10)

Table B-50 Parameters on the main interface Parameter PORT Error Frame Monitor Window (ms) Value Range For example: PORT1 1000 to 60000, in step of 100 Default Value 1000 Description Displays the name of the external Ethernet port. In the specified Error Frame Monitor Window (ms), if the number of error frames exceeds the specified Error Frame Monitor Threshold (Entries) due to the link degradation, the link event alarm is reported. Specifies the threshold of monitoring error frames. Within the specified value of Error Frame Period Window (frames), if the number of error frames on the link exceeds the preset value of Error Frame Period Threshold (frames), an alarm is reported. Specifies the threshold of monitoring the error frame period. If any error frame occurs in one second, this second is called an error frame second. Within the specified value of Error Frame Second Window(s), if the number of error frames on the link exceeds the preset value of Error Frame Second Threshold (s), an alarm is reported. Error Frame Second Threshold (s) 1 to 900, in step of 1 2 Specifies the threshold of monitoring error frame seconds.
Error Frame Monitor Threshold (frames) Error Frame Period Window (frames)
1 to 4294967295, in step of 1 14880 to 8928000, in step of 1
148800
Error Frame Period Threshold (frames) Error Frame Second Window(s)
1 to 892800000, in step of 1 10 to 900, in step of 1
60
Related Tasks
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter

This section describes the parameters for monitoring the OAM errored frames at the Ethernet port.
Issue 03 (2011-04-10)
B-363
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click the Remote OAM parameter tab.

Table B-51 Parameters on the main interface Field Port Remote OAM Working Mode Remote Alarm Support for Link Event Value Range Default Value Description Displays the name of the remote Ethernet port. Displays the working mode of the remote Ethernet port. Displays whether the remote Ethernet port can notify link events to the local port. Displays how the remote Ethernet port responds to a loopback. Displays whether the remote Ethernet port supports unidirectional operations. Displays the maximum OAM packet size supported by the remote Ethernet port.
Remote Side Loopback Response Unidirectional Operation
Max.OAM Packet Length (byte)
Related Tasks
A.7.9.2 Enabling the Link Event Notification
B.7.4 QoS Parameters

This section describes the parameters for the QoS on the EoPDH plane. B.7.4.1 Parameter Description: QoS Management_Creation of Flows This parameter describes the parameters for creating flows. B.7.4.2 Parameter Description: QoS Management_Creation of CAR This section describes the parameters for creating CAR. B.7.4.3 Parameter Description: QoS Management_Creation of CoS This section describes the parameters for creating CoS.
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS This section describes the parameters for creating CAR/CoS. B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues This section describes the parameters for shaping management of egress queues.
B.7.4.1 Parameter Description: QoS Management_Creation of Flows

This parameter describes the parameters for creating flows.
Navigation Path
1. 2. 3. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. Click New.
Issue 03 (2011-04-10)
B-365

Table B-52 Parameters on the main interface Parameter Flow Type Value Range Port Flow Port+VLAN Flow Port+SVLAN Flow Port+CVLAN +SVLAN Flow Port+VLAN +Priority Flow Default Value Port Flow Description l Port flow: The packets from a certain port are classified as a type of flow. The Ethernet service associated with this flow type is the line service or Layer 2 switching service that uses this port as the service source. l Port+VLAN flow: The packets that are from a certain port and have a specified VLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on VLAN) or EVPLAN service (based on 802.1q bridge) that uses this PORT +VLAN as the service source. l Port+SVLAN flow: The packets that are from a certain port and have a specified SVLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on 802.1ad bridge) that uses this PORT +SVLAN as the service source. l Port+CVLAN+SVLAN flow: The packets that are received from or transmitted to a certain port and have a specified CVLAN+SVLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on 802.1ad bridge) that uses this PORT +CVLAN+SVLAN as the service source. l Port+VLAN+Priority flow: The packets that are from a certain port and have a specified VLAN ID and a specified VLAN priority are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this Port+VLAN+Priority as the service source.
B-366
Issue 03 (2011-04-10)
Parameter Port
Value Range PORT1-PORT9, VCTRUNK1VCTRUNK16
Default Value PORT1
Description l When the associated service is the line service, set this parameter to the source port or sink port of the associated Ethernet service. l When the associated service is the Layer 2 switching service, set this parameter to a mounted port of the bridge.
VLAN ID
1-4095
l This parameter is valid only when Flow Type is set to Port+VLAN Flow or Port +VLAN+Priority Flow. l Set this parameter to the source VLAN of the associated Ethernet service.
C-VLAN
1-4095
l This parameter is valid only when Flow Type is set to Port+CVLAN+SVLAN Flow. l Set this parameter to the source CVLAN of the associated Ethernet service.
S-VLAN
1-4095
l This parameter is valid only when Flow Type is set to Port+SVLAN Flow or Port+SVLAN+CVLAN Flow. l Set this parameter to the source S-VLAN of the associated Ethernet service.
Priority
l This parameter is valid only when Flow Type is PORT+VLAN+Priority Flow. l This parameter indicates the VLAN priority of the flow-associated Ethernet services.
Related Tasks
A.7.7.1 Creating a Flow
B.7.4.2 Parameter Description: QoS Management_Creation of CAR

This section describes the parameters for creating CAR.
Navigation Path
1. 2. 3.
Issue 03 (2011-04-10)
In the NE Explorer, select the EFP8 board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CAR Configuration. Click New.

Table B-53 Parameters on the main interface Parameter CAR ID Value Range 1-512 Default Value 1 Description This parameter identifies a CAR operation, and is used to bind a flow to an associated CAR operation. Indicates whether to enable the CAR operation performed on the flow bound to the CAR. l Indicates the CIR. When the rate of a packet is not more than the CIR, this packet passes the restriction of the CAR and is forwarded first even in the case of network congestion. l The value of this parameter should not be more than the PIR. Committed Burst Size(kbyte) 0-1024 0 Indicates the CBS. When the rate of a packet that passes the restriction of the CAR is not more than the CIR in a certain period, some packets can burst and can pass the restriction of the CAR. These packets can be forwarded first even in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. Note that the CBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the CBS is determined by the CIR. The greater the CIR, the greater the CBS. l Indicates the PIR. When the rate of a packet is more than the PIR, the packet that exceeds the rate restriction is directly discarded. When the rate of packets is more than the CIR but is lower than or equal to the PIR, these packets whose rate exceeds the CIR can pass the restriction of the CAR and are marked yellow, and these packets are discarded first in the case of network congestion. l The value of this parameter should not be more than the port bandwidth.
Enabled/Disabled
Enabled Disabled
Disabled
Committed information Rate (kbit/s)
0-100032 Step: 64
Peak information Rate(kbit/s)
0-100032 Step: 64
B-368
Issue 03 (2011-04-10)
Parameter Maximum Burst Size(kbyte)
Value Range 0-1024
Default Value 0
Description Indicates the MBS. When the rate of the packet that passes the restriction of the CAR is more than the CIR but is not more than the PIR, some packets can burst and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The maximum traffic of the burst packets is determined by the MBS. Note that the MBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the MBS is determined by the PIR. The greater the PIR, the greater the MBS.
Related Tasks
A.7.7.2 Creating the CAR
B.7.4.3 Parameter Description: QoS Management_Creation of CoS

This section describes the parameters for creating CoS.
Navigation Path
1. 2. 3. In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CoS Configuration tab. Click New.

Table B-54 Parameters on the main interface Parameter CoS ID Value Range 1-64 Default Value 1 Description This parameter identifies a CoS operation, and is used to bind a flow to an associated CoS operation.
Issue 03 (2011-04-10)
B-369
Parameter CoS Type
Value Range simple VLAN Priority IPTOS DSCP
Default Value simple
Description l If the CoS type of a flow is set to simple, all the packets in this flow are directly scheduled to a specified egress queue. l If the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets. l If the CoS type of a flow is set to DSCP, the packets in this flow are scheduled to specified egress queues according to differentiated services code point (DSCP) in the IPv6 tags of these packets. l If the CoS type of a flow is set to IP TOS, the packets in this flow are scheduled to specified egress queues according to the TOS values carried in the IPv4 packets. This CoS type is applicable to IPv4 packets.
CoS parameter CoS Priority
0-7
Displays the CoS parameters corresponding to different CoS types. This parameter determines to which egress queue a packet is schedule. l Each Ethernet port on the EFP8 board supports eight egress port queues. Queues 1-8 respectively correspond to the CoS priorities from 0 to 7. l Queue 8, with the CoS priority of 7, is as SP queue. Queues 1-7, with the CoS priorities from 0 to 6, are WRR queues. The weighted proportion of these WRR queues is 1:2:4:8:16:32:64 (from priority 0 to priority 6). On the EFP8 board, the weighted proportion of these WRR queues cannot be changed. l If the traffic shaping feature of some queues is enabled, bandwidth is allocated first to the queues whose traffic shaping feature is enabled based on the CIR. The remaining bandwidth is allocated to the eight queues by using the SP+WRR algorithm.
Related Tasks
A.7.7.3 Creating the CoS
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS

This section describes the parameters for creating CAR/CoS.
Navigation Path
1. 2. In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab.

Table B-55 Parameters on the main interface Parameter Flow Type VB ID Port C-VLAN Value Range Default Value Description Displays the type of a flow. Displays the ID of the bridge. Displays the port where a flow is to be created. l Displays the C-VLAN. l This parameter is valid is Flow Type is Port+VLAN Flow, Port+CVLAN +SVLAN Flow, or Port+VLAN +Priority Flow. S-VLAN l Displays the S-VLAN. l This parameter is valid when Flow Type is Port+SVLAN Flow or Port +CVLAN+SVLAN Flow. Priority l Displays the priority of the flow. l This parameter is valid when Flow Type is Port+VLAN+Priority Flow. Bound CAR None This parameter indicates the CAR ID corresponding to a CAR operation. Different CAR IDs should be bound to different flows, even though the parameters of the CAR operations are the same. Indicates the CoS ID that corresponds to a CoS operation.
Bound CoS
None
Related Tasks
A.7.7.4 Binding the CAR/CoS
Issue 03 (2011-04-10)
B-371
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues

This section describes the parameters for shaping management of egress queues.
Navigation Path
In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > QoS Management > Port Shaping Management from the Function Tree.

Table B-56 Parameters on the main interface Parameter Port Port Queue Status Value Range Enabled Disabled CIR(kbit/s) 0-100032 Step: 64 0 Default Value Disabled Description Displays the port name. Displays the queue name. Indicates whether to enable the traffic shaping feature of an egress queue. l When the rate of a packet is not more than the CIR, this packet directly enters the egress queue. l The value of this parameter should not be more than the PIR. DCBS(kbyte) PIR(kbit/s) 0-100032 Step: 64 0 0 Displays the excess burst size. l When the rate of a packet is more than the PIR, the packet that exceeds the rate restriction is directly discarded. When the rate of packets is more than the CIR but not more than the PIR, the packets that exceed the restriction of the CIR enter the buffer of the CIR. When the buffer overflows, the packets are marked yellow and enter the egress queue, which enables the packets to be discarded first in the case of queue congestion. l The value of this parameter should not be more than the port bandwidth. DMBS(kbyte) 0 Displays the maximum excess burst size.
Related Tasks
A.7.7.5 Configuring Traffic Shaping for Egress Queues
B-372
Issue 03 (2011-04-10)
B.7.5 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the EoPDH plane. B.7.5.1 Parameter Description: Ethernet Port_External Port This section describes the parameters for Ethernet external ports. B.7.5.2 Parameter Description: Ethernet Port_Internal Port This section describes the parameters for Ethernet internal ports. B.7.5.3 Parameter Description: Type Field of QinQ Frames This section describes the parameters for setting the type field of QinQ frames.
B.7.5.1 Parameter Description: Ethernet Port_External Port

This section describes the parameters for Ethernet external ports.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port.

Table B-57 Parameters for the basic attributes Parameter Port Enabled/Disabled Value Range Enabled Disabled Default Value Disabled Description Displays the name of the external port. l If the port gains access to services, set this parameter to Enabled. Otherwise, set this parameter to Disabled. l If this parameter is set to Enabled for the port that does not access services, an ETH_LOS alarm may be generated. This parameter is invalid for PORT9.
Issue 03 (2011-04-10)
B-373
Value Range Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex
Description l Different types of Ethernet ports support different working modes. l If the opposite port works in autonegotiation mode, set this parameter to Auto-Negotiation. l If the opposite port works in full-duplex mode, set this parameter to 10M FullDuplex or 100M Full-Duplex, depending on the rate of the opposite port. l If the opposite port works in half-duplex mode, set this parameter to 10M HalfDuplex or 100M Half-Duplex, depending on the rate of the opposite port, or set this parameter to AutoNegotiation. This parameter is invalid for PORT9.
Maximum Frame Length
1518-2000
1522
l Set this parameter to a value greater than the maximum length of all the data frames to be transmitted. l The default value is recommended if the jumbo frame is not considered and the data frames contain only one layer of VLAN tags or even no tags. The value of 1526 or greater is recommended if the data frames contain two layers of tags, such as QinQ.
Port Physical Parameters
Displays the actual working status of a PORT. This parameter is invalid for PORT9.
MAC Loopback
Non-Loopback Loopback
Non-Loopback
l A MAC loopback is to loop back the Ethernet frames transmitted to the opposite port. l Use the default value unless otherwise specified.
PHY Loopback
Non-Loopback Loopback
Non-Loopback
l A PHY loopback is to loop back the Ethernet physical signals transmitted to the opposite port. l Use the default value unless otherwise specified. This parameter is invalid for PORT9.
B-374
Issue 03 (2011-04-10)
Table B-58 Parameters for flow control Parameter Port NonAutonegotiation Flow Control Mode Value Range Disabled Enable Symmetric Flow Control Mode Send Only Receive Only Default Value Disabled Description Displays the name of the external port. l This parameter is valid only when Working Mode is not set to AutoNegotiation. l If this parameter is set to Enable Symmetric Flow Control Mode, the port can send PAUSE frames and process the received PAUSE frames. l If this parameter is set to Send Only, the port can send PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l If this parameter is set to Receive Only, the port can process the received PAUSE frames but cannot send PAUSE frames in the case of congestion. l Set this parameter to the same as the nonautonegotiation flow control mode of the opposite port. Autonegotiation Flow Control Mode Disabled Enable Dissymmetric Flow Control Enable Symmetric Control Enable Symmetric/ Dissymmetric Flow Control Disabled l This parameter is valid only when Working Mode is Auto-Negotiation. l If this parameter is set to Enable Symmetric Control, the port can send PAUSE frames and process the received PAUSE frames. l If this parameter is set to Enable Dissymmetric Flow Control, the port can send PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l If this parameter is set to Enable Symmetric/Dissymmetric Flow Control, the port can function as follows: Sends and processes PAUSE frames. Sends but does not process PAUSE frames. Processes but does not send PAUSE frames. l Set this parameter according to the autonegotiation flow control mode of the opposite port. This parameter is invalid for PORT9.
Issue 03 (2011-04-10)
B-375
Table B-59 Parameters for the tag attributes Parameter Port TAG Value Range Tag Aware Access Hybrid Default Value Tag Aware Description Displays the name of the external port. l With different tag attributes, the port processes frames in different modes. For details, see Table B-62. l Set this parameter to Tag Aware if the port processes the frames with VLAN tags (or tagged frames). l Set this parameter to Access if the port processes the frames without VLAN tags (or untagged frames). l Set this parameter to Hybrid if the port processes the tagged frames and untagged frames. Default VLAN ID 1-4095 1 l This parameter is valid only when TAG is set to Access or Hybrid. l For the usage of this parameter, see Table B-62. l Set this parameter as required. VLAN Priority 0-7 0 l This parameter is valid only when TAG is set to Access or Hybrid. l For the usage of this parameter, see Table B-62. l When the VLAN priority is required for traffic classification or other purposes, set this parameter as required. Use the default value unless otherwise specified. Entry Detection Enabled Disabled Enabled l Indicates whether to check the incoming packets according to the tag attribute. l Set this parameter as required.
Table B-60 Parameters for the network attributes Parameter Port Value Range Default Value Description Displays the name of the external port.
B-376
Issue 03 (2011-04-10)
Parameter Port Attributes
Value Range UNI C-Aware S-Aware
Default Value UNI
Description l If this parameter is set to UNI, the port processes data frames according to the tag attribute. l If this parameter is set to C-Awareor SAware, the port processes the data frames by using the processing method of QinQ services. l Set this parameter to C-Aware or SAware when the port processes QinQ services. Otherwise, this parameter takes the default value.
Table B-61 Parameters for the advanced attributes Parameter Port Broadcast Packet Suppression Value Range Disabled Enabled Default Value Disabled Description Displays the name of the external port. This parameter specifies whether to restrict the traffic of broadcast packets according to the proportion of the broadcast packets to the total packets. Set this parameter to Enabled when a broadcast storm may occur at the opposite port. When the proportion of the received broadcast packets to the total packets crosses the threshold, the port discards the received broadcast packets. Set this parameter to a value greater than the proportion when no broadcast storm occurs. The value of 30% or greater is recommended. Specifies the traffic threshold of the port. You can specify the traffic monitoring period by setting Port Traffic Threshold Time Window(Min).
10%-100%
30%
Flow Threshold (Mbit/s)
0-100 (PORT1PORT8) 0-1000 (PORT9)
100 (PORT1PORT8) 1000 (PORT9)
Issue 03 (2011-04-10)
B-377
Parameter Port Traffic Threshold Time Window(Min)
Value Range 0-30
Default Value 0
Description Specifies the traffic monitoring period. l If Port Traffic Threshold Time Window(Min) is set to 0, an associated alarm is reported at the moment when the traffic received at the port crosses the value of Traffic Threshold(Mbit/s). l If the Port Traffic Threshold Time Window(Min) is set to a value other than 0, an associated alarm is reported only when the traffic received at the port always crosses the value of Traffic Threshold(Mbit/s) in the monitoring period.
Transmitting Rate (Kbit/s) Receiving Rate (Kbit/s) Loop Detection
Enabled Disabled
Disabled
Queries the actual transmitting rate of the port. Queries the actual receiving rate of the port. This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port.
Table B-62 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame Processing Method Tag aware Receives the frame. Discards the frame. Access Discards the frame. The port receives the frame after adding to the frame the VLAN tag that contains Default VLAN ID and VLAN Priority. Hybrid Receives the frame. The port receives the frame after adding to the frame the VLAN tag that contains Default VLAN ID and VLAN Priority.
Ingress port
B-378
Issue 03 (2011-04-10)
Direction
Type of Data Frame Tagged frame
Processing Method Tag aware Transmits the frame. Access The port strips the VLAN tag from the frame and then transmits the frame. Hybrid l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Egress port
Related Tasks
A.7.4.1 Configuring External Ethernet Ports
B.7.5.2 Parameter Description: Ethernet Port_Internal Port

This section describes the parameters for Ethernet internal ports.
Navigation Path
1. 2. In the NE Explorer, select the EFP8 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port.

Table B-63 Parameters for the tag attributes Parameter Port Value Range Default Value Description Displays the name of the internal port.
Issue 03 (2011-04-10)
B-379
Parameter TAG
Value Range Tag Aware Access Hybrid
Default Value Tag Aware
Description l With different tag attributes, the port processes frames in different modes. For details, see Table B-68. l Set this parameter to Tag Aware if the port processes the frames with VLAN tags (or tagged frames). l Set this parameter to Access if the port processes the frames without VLAN tags (or untagged frames). l Set this parameter to Hybrid if the port processes the tagged frames and untagged frames.
Default VLAN ID
1-4095
l This parameter is valid only when TAG is set to Access or Hybrid. l For the usage of this parameter, see Table B-68. l Set this parameter as required.
VLAN Priority
0-7
l This parameter is valid only when TAG is set to Access or Hybrid. l For the usage of this parameter, refer to Table B-68. l When the VLAN priority is required for traffic classification or other purposes, set this parameter as required. The default value is recommended unless otherwise specified.
Entry Detection
Enabled Disabled
Enabled
l Indicates whether to check the incoming packets according to the tag attribute. l Set this parameter as required.
Table B-64 Parameters for encapsulation or mapping Parameter Port Mapping Protocol Value Range GFP Default Value GFP Description Displays the name of the internal port. The default value is recommended. The EFP8 board supports GFP only. Scramble Scrambling Mode [X43+1] Unscrambled Scrambling Mode [X43+1] l Indicates the scrambling polynomial used by the mapping protocol. l The default value is recommended.
B-380
Issue 03 (2011-04-10)
Parameter Set Inverse Value for CRC Check Field Length
Value Range FCS32 No
Default Value FCS32
Description This parameter is invalid for the EFP8 board. l When the Ethernet board uses the GFP mapping protocol, set this parameter to FCS32 or No. l When you set this parameter to FCS32, a 32-bit FCS is used. l The default value is recommended.
FCS Calculated Bit Sequence
Big endian Little endian
Big endian
l When you set this parameter to Big endian, the least significant byte of the FCS is placed first and the most significant byte is placed last. l When you set this parameter to Little endian, the most significant byte of the FCS is placed first and the least significant byte is placed last. l The default value is recommended.
Extension Header Option
No
No
Indicates whether the GFP payload header contains the extension header and eHEC.
Table B-65 Parameters for the network attributes Parameter Port Port Attributes Value Range UNI C-Aware S-Aware Default Value UNI Description Displays the name of the internal port. l If this parameter is set to UNI, the port processes data frames according to the tag attribute. l If this parameter is set to C-Aware or SAware, the port processes the data frames by using the processing method of QinQ services. l Set this parameter to C-Aware or SAware when the port processes QinQ services. Otherwise, this parameter takes the default value.
Table B-66 Parameters for the LCAS Parameter Port Value Range Default Value Description Displays the name of the internal port.
Issue 03 (2011-04-10)
B-381
Parameter Enabling LCAS
Description l Indicates whether to enable the LCAS function. l The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth needs of the applications. As a result, the bandwidth utilization is improved.
LCAS Mode
Huawei Mode Standard Mode
Huawei Mode
l Indicates the sequence in which the LCAS sink sends the MST control packet and Rs-Ack control packet. l When you set this parameter to Huawei Mode, the LCAS sink first sends the RsAck and then sends the MST. l When you set this parameter to Standard Mode, the LCAS sink first sends the MST and then sends the RsAck. l If the equipment at the opposite end is the third-party equipment and does not support the Huawei mode, set this parameter to Standard Mode. Otherwise, set this parameter to Huawei Mode.
Hold Off Time(ms)
An integer ranging from 0, 2000 to 10000, in the increments of 100
2000
l When a member link is faulty, the LCAS performs switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and performs an LCAS switching. This parameter specifies the duration of the delay. l The default value is recommended.
WTR Time(s)
0-720
300
l When the time after a member link is restored to normal reaches the specified value of this parameter, the VCG uses the restored member link. l The default value is recommended.
TSD
Disabled Enabled
Disabled
l Indicates whether the TSD is used as a condition for determining whether a member link is faulty. In the case of the VC-12, the TSD refers to the BIP_SD. In the case of the VC-3, the TSD refers to the B3_SD_VC3. l The default value is recommended.
B-382
Issue 03 (2011-04-10)
Parameter Min. MembersTransmit Direction
Value Range 2-256
Default Value 16
Description l Specifies the minimum number of members in the transmit direction. After the LCAS is enabled, the LCAS_PLCT alarm is reported when the number of effective members in the transmit direction becomes lower than the minimum number specified by this parameter. l The default value is recommended.
Mini. MembersReceive Direction
2-256
16
l Specifies the minimum number of members in the receive direction. After the LCAS is enabled, the LCAS_PLCT alarm is reported when the number of effective members in the receive direction becomes lower than the minimum number specified by this parameter. l The default value is recommended.
Table B-67 Parameters for bound paths Parameter Configurable Ports Level Value Range VCTRUNK1VCTRUNK16 Default Value Description Specifies the VCTRUNK to bind paths. Displays the level of the bound VC path. In the case of the EFP8 board, this parameter always takes the value of VC12-Xv. Direction Bidirectional Uplink Downlink Available Resources Bidirectional l Specifies the direction of the bound path. l Set this parameter to Bidirectional unless otherwise specified. l Displays the available VC4 paths. l In the case of the EFP8 board, this parameter always takes the value of VC4-1. VC12-1-VC12-63 Specifies the available timeslots.
Available Timeslots
Issue 03 (2011-04-10)
B-383
Parameter Bound Path
Value Range -
Default Value -
Description You need to plan and set this parameter according to the following principles: l The capacity of the VCTRUNK is determined by the actual bandwidth required by the services. l The EFP8 board supports 16 VCTRUNKs. Each VCTRUNK can bind a maximum of 16 VC-12 paths and the total number of bound VC-12 paths cannot exceed 63.
Number of Bound Paths
Displays the number of the bound VC path.
Table B-68 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame Processing Method Tag aware Receives the frame. Discards the frame. Access Discards the frame. The port receives the frame after adding to the frame the VLAN tag that contains Default VLAN ID and VLAN Priority. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid Receives the frame. The port receives the frame after adding to the frame the VLAN tag that contains Default VLAN ID and VLAN Priority. l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Ingress port
Egress port
Tagged frame
Transmits the frame.
B-384
Issue 03 (2011-04-10)
Related Tasks
A.7.4.2 Configuring VCTRUNKs on an Ethernet Board
B.7.5.3 Parameter Description: Type Field of QinQ Frames

This section describes the parameters for setting the type field of QinQ frames.
Navigation Path
In the NE Explorer, select the EFP8 board from the Object Tree and choose Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.

Table B-69 Parameters on the main interface Parameter Board Value Range Default Value Description Displays the Ethernet board on which the type field of QinQ frames needs to be set. If the Ethernet board is the EFP8 board, this parameter always takes the value of EFP8. QinQ Type Area (Hexadecimal) 81 00 88 A8 91 00 0600 to FFFF 8100 Specifies the type field of QinQ frames. Set this parameter according to the type field of the accessed QinQ frames.
Related Tasks
A.7.4.3 Modifying the Type Field of QinQ Frames
B.8 RMON Parameters

This topic describes the parameters that are related to RMON performances. B.8.1 Parameter Description: RMON Performance_Statistics Group This topic describes the parameters that are related to RMON statistics groups. B.8.2 Parameter Description: RMON Performance_History Group This topic describes the parameters that are related to RMON history groups. B.8.3 Parameter Description: RMON Performance_History Control Group This topic describes the parameters that are related to RMON history control groups. B.8.4 Parameter Description: RMON Performance_RMON Setting This topic describes the parameters that are related to RMON setting.
Issue 03 (2011-04-10)
B-385
B.8.1 Parameter Description: RMON Performance_Statistics Group

This topic describes the parameters that are related to RMON statistics groups.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the Statistics Group tab.
Parameters
Parameter Select port Sampling Interval Event Value Range 5 to 150 Default Value 5 Description This parameter specifies the object to be monitored. This parameter specifies the duration of the monitoring period. This parameter indicates the queried performance events.
Related Tasks
A.10.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
B.8.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the History Group tab.
Parameters
Parameter Select port Period End Time from/to History Table Type Value Range 30-Second 30-Minute Custom Period 1 Custom Period 2
Default Value 30-Second
Description The parameter indicates the object to be monitored. This parameter specifies the start time and end time of the monitoring period. This parameter specifies the monitoring period.
Parameter Statistical Item Statistical Value Time Flag
Value Range -
Default Value -
Description This parameter indicates the performance items to be monitored. This parameter indicates the statistical value of the monitored performance items. This parameter indicates the time point of each performance event.
B.8.3 Parameter Description: RMON Performance_History Control Group

This topic describes the parameters that are related to RMON history control groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History Control Group.
Parameters
Parameter 30-Second Value Range Enabled Disabled 30-Minute Enabled Disabled Custom Period 1 Enabled Disabled Custom Period 2 Enabled Disabled Sampling Interval (s) 300 to 43200 (Custom Period 1) 300 to 86400 (Custom Period 2) Number of Items 1 to 50 900(Custom Period 1) 86400(Custom Period 2) 16 6(Custom Period 2) RMON Monitor Start Time Disabled Disabled Enabled Default Value Disabled Description This parameter indicates or specifies whether to enable the 30-Second monitoring function. This parameter indicates or specifies whether to enable the 30-Minute monitoring function. This parameter indicates or specifies whether to enable Custom Period 1. This parameter indicates or specifies whether to enable Custom Period 2. l This parameter indicates or specifies the monitoring period in Custom Period 1 and Custom Period 2. l The value must be an integer multiple of 30. This parameter indicates or specifies the quantity of the history registers. This parameter specifies the RMON start time.
Issue 03 (2011-04-10)
B-387
Related Tasks
A.10.3 Configuring a History Control Group

This topic describes the parameters that are related to RMON setting.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the RMON Setting tab.
Event Parameters
Parameter Event 30-Second Monitor 30-Minute Monitor Custom Period 1 Monitor Custom Period 2 Monitor Threshold Detect Value Range Enabled Disabled Enabled Disabled Enabled Disabled Enabled Disabled Report All Do Not Detect Report Only the Upper Threshold Report Only the Lower Threshold Report All Disabled Disabled Default Value Disabled Description This parameter indicates the performance event to be monitored. This parameter indicates or specifies whether to enable the monitoring function based on 30-Second Monitor. This parameter indicates or specifies whether to enable the 30-Minute Monitor monitoring function. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 1 Monitor. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 2 Monitor. l This parameter indicates or specifies the threshold detection method. l If the number of detected events reaches the preset threshold, the events are reported to the NMS. Otherwise, the events are not reported to the NMS. l If an event does not support this parameter, Not Supported is displayed. This parameter indicates or specifies the upper threshold. If the number of performance events exceeds the preset upper threshold, the corresponding performance events are reported.
Upper Threshold
B-388
Issue 03 (2011-04-10)
Parameter Lower Threshold
Value Range -
Default Value -
Description This parameter indicates or specifies the lower threshold. If the number of performance events is less than the preset lower threshold, the corresponding performance events are reported. This parameter indicates the unit of each threshold of the performance events.
Threshold Unit
Related Tasks
A.10.2 Configuring an Alarm Group for an Ethernet Port A.10.4 Browsing the Performance Data in the History Group of an Ethernet Port
B.9 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.
B.9.1 MPLS Tunnel Parameters This topic describes parameters that are related to MPLS tunnels. B.9.2 CES Parameters This topic describes parameters that are related to CES services. B.9.3 ATM Parameters This topic describes the parameters that are related to ATM services.
B.9.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels. B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels This topic describes parameters that are related to the basic configurations of MPLS tunnels. B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel This topic describes parameters that are related to static tunnels. B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels This topic describes parameters that are used for creating unidirectional tunnels. B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels This topic describes the parameters that are related to creating bidirectional tunnels. B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters This topic describes parameters that are related to MPLS OAM. B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI
This topic describes FDI parameters. B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping This topic describes the parameters that are related to the LSP Ping test. B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute This topic describes the parameters that are related to the LSP Traceroute test. B.9.1.9 Parameter Description: PW Management_PW Management This topic describes parameters that are related to PW management. B.9.1.10 Parameter Description: PW Management_MS-PW Creation This topic describes the parameters that are related to MS-PW creation. B.9.1.11 Parameter Description: PW Management_PW OAM This topic describes parameters that are related to PW OAM. B.9.1.12 Parameter Description: PW Management_PW Ping This topic describes the parameters that are related to the PW Ping test. B.9.1.13 Parameter Description: PW Management_PW Traceroute This topic describes the parameters that are related to the PW Traceroute test. B.9.1.14 Parameter Description: MPLS APS Protection Management This topic describes parameters that are related to MPLS APS protection management. B.9.1.15 Parameter Description: Tunnel Protection Group_Creation This topic describes the parameters that are related to creating a tunnel protection group. B.9.1.16 Parameter Description: PW APS Protection Group_Creation This topic describes the parameters that are used for creating a PW APS protection group. B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation This topic describes the parameters that are used for creating a slave protection pair of a PW APS protection group.
B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels

This topic describes parameters that are related to the basic configurations of MPLS tunnels.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Basic Configuration from the Function Tree.
B-390
Issue 03 (2011-04-10)

Parameter LSR ID Value Range Default Value 0.0.0.0 Description l Specifies or displays the LSR ID of an NE. On a PSN, each NE is assigned a unique LSR ID. l This parameter must be set in IPv4 address format. Start of Global Label Space 0-1015808 0 l Specifies the start value of a global label space. The OptiX RTN 950 supports a step of 2048. l The start value of a global label space is the smallest unicast tunnel label. When Start of Global Label Space is 0, the smallest unicast tunnel label is 16, with values 0 to 15 reserved. l On an MPLS-enabled network, global label spaces of NEs are recommended to overlap each other if possible. Global Label Space Size Start of Multicast Label Space Displays the size of a global label space. The OptiX RTN 950 does not support this parameter.
Related Tasks
A.8.2.1 Setting Basic MPLS Attributes
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel

This topic describes parameters that are related to static tunnels.
Issue 03 (2011-04-10)
B-391
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Click Query.
2. 3.

Parameter ID Name Enable Status Value Range Enabled Disabled Default Value Enabled Description Displays the tunnel ID. Specifies or displays the customized tunnel name. l Specifies or displays whether a tunnel is enabled.
NOTE The OptiX RTN 950 supports only the value Enabled.
Node Type
l Displays the node type. l For bidirectional tunnels, this parameter displays the node types of forward tunnels.
Direction CIR(kbit/s)
No Limit 1024-1024000
Displays the direction of a tunnel. l Specifies or displays the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth.
PIR(kbit/s) CBS(byte)
Issue 03 (2011-04-10)
B-392
Parameter PBS(byte) Bandwidth Remaining (kbit/s) In Port
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Displays the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. Displays the MPLS label that a forward tunnel carries when entering a node. Specifies the MPLS label that a reverse tunnel carries when entering a tunnel. Displays the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. Displays the MPLS label that a forward tunnel carries when leaving a node. Displays the MPLS label that a reverse tunnel carries when leaving a node. Displays the IP address of the next-hop port of a forward tunnel. Displays the IP address of the next-hop port of a reverse tunnel. Displays the LSR ID of the ingress node. Displays the LSR ID of the egress node. Displays the tunnel type.
Forward In Label
Reverse Out Label
Out Port
Forward Out Label
Reverse In Label
Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type
Issue 03 (2011-04-10)
B-393
Parameter EXP
Value Range 0-7 None
Default Value -
Description l Specifies or displays the value of the EXP field in the packets transmitted through MPLS tunnels. l For unidirectional tunnels, this parameter is available only if Node Type is Ingress. l For bidirectional tunnels, this parameter cannot be set if Node Type is Transit. l If this parameter is set to a value from 0 to 7, the EXP field takes its fixed value. l If this parameter takes its default value None, the EXP field varies based on the DiffServ mappings.
LSP Mode
Pipe
Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
NOTE On the OptiX RTN 950, this parameter can be set to Pipe only.
MTU(byte) Protection Group
The OptiX RTN 950 does not support this parameter. Displays the MPLS APS protection group to which a tunnel belongs.
B-394
Issue 03 (2011-04-10)
Parameter VLan ID
Value Range -
Default Value -
Description l Specifies or displays the VLAN ID that Ethernet packets carry when transmitted over MPLS tunnels. l If packets need to traverse a Layer 2 network, set the VLAN ID for the tunnel carried by the NNI port according to the VLAN planning requirements on the Layer 2 network. l Set this parameter to the same value for both ends of a tunnel.
Issue 03 (2011-04-10)
B-395
Parameter CoS
Default Value -
Description l This parameter specifies the PHB service class of an LLSP, if the type of an MPLS tunnel is L-LSP. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
Related Tasks
A.8.2.4 Querying MPLS Tunnel Information
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels

This topic describes parameters that are used for creating unidirectional tunnels.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree.
B-396
2. 3. 4.
Click the Static Tunnel tab. Click New and choose Unidirectional Tunnel from the drop-down list. The New Unicast Unidirectional Tunnel dialog box is displayed. Select New Reverse Tunnel.

Parameter Tunnel ID Value Range 1-65535 Default Value Description l Specifies the tunnel ID. l The total number of tunnels and PWs must be equal to or less than 1024. The number of tunnels that carry PWs are not included in the total. Tunnel Name Node Type Ingress Egress Transit Direction Bandwidth(kbit/s) No Limit 1024-1024000 No Limit Indicates the direction of a tunnel. l Specifies the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth. CBS(kbit/s) PIR(Byte) PBS(Byte) In Board/Logic Interface Type The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Specifies the board where the ingress port of a forward tunnel is located.
B-397
Ingress
Specifies the tunnel name. Specifies the node type of a forward tunnel.
Issue 03 (2011-04-10)
Parameter In Port
Value Range -
Default Value -
Description Specifies the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. l Specifies the MPLS label that a tunnel carries when entering a node. l This parameter can be set for only egress and transit nodes.
In Labela
16-1048575
Out Board/Logic Interface Type Out Port
Specifies the board where the egress port of a forward tunnel is located. Specifies the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. l Specifies the MPLS label that a tunnel carries when leaving a node. l This parameter can be set for only ingress and transit nodes.
Out Labela
16-1048575
Next Hop Address
l Specifies the port IP address of the next-hop node for a tunnel. l This parameter can be set for only ingress and transit nodes.
Source Node
l Specifies the LSR ID of the ingress node. l This parameter can be set for only egress nodes and transit nodes.
Sink Node
l Specifies the LSR ID of the egress node. l This parameter can be set for only ingress and transit nodes.
B-398
Issue 03 (2011-04-10)
Parameter Tunnel Type
Value Range E-LSP L-LSP
Default Value E-LSP
Description l Specifies the tunnel type. l The value E-LSP indicates that the EXP field is used to identify packet scheduling priorities of PWs. An E-LSP tunnel can contain PWs of eight packet scheduling priorities. l The value L-LSP indicates that the MPLS label value is used to identify packet scheduling priorities of PWs. An L-LSP tunnel can contain PWs of the same packet scheduling priority.
EXP
0-7 None
None
l Specifies the value of the EXP field in the packets transmitted through MPLS tunnels. l This parameter is available only if Node Type is Ingress. l If this parameter is set to a value from 0 to 7, the EXP field takes its fixed value. l If this parameter takes its default value None, the EXP field varies based on the DiffServ mappings.
LSP Mode
Pipe
NOTE The OptiX RTN 950 supports only the value Pipe.
Issue 03 (2011-04-10)
B-399
Parameter MTU CoS
Default Value BE
Description The OptiX RTN 950 does not support this parameter. l This parameter specifies the PHB service class of an LLSP, if the type of an MPLS tunnel is L-LSP. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
NOTE
At an MPLS node, in labels must be different from each other, out labels must also be different from each other, but out labels can be the same as in labels.
Related Tasks
A.8.2.2 Creating a Unidirectional MPLS Tunnel
B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels

This topic describes the parameters that are related to creating bidirectional tunnels.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Click New and choose Bidirectional Tunnel from the drop-down list.
2. 3.

Parameter Tunnel ID Value Range 1 to 65535 Default Value Description l Specifies the tunnel ID. l The total number of tunnels and PWs must be equal to or less than 1024. The number of tunnels that carry PWs is not included in the total. Tunnel Name Node Type Ingress Egress Transit Direction CIR(kbit/s) No Limit 1024-1024000 No Limit Indicates the direction of a tunnel. l Specifies the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth. CBS(kbit/s) PIR(Byte) PBS(Byte) The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Ingress Specifies the tunnel name. Specifies the node type of a forward tunnel.
Issue 03 (2011-04-10)
B-401
Parameter In Board/Logic Interface Type In Port
Value Range -
Default Value -
Description Specifies the board where the ingress port of a forward tunnel is located. Specifies the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. l Specifies the MPLS label that data carries when entering a forward tunnel. l This parameter can be set for only egress and transit nodes.
Forward In Labela
16 to 1048575
Reverse Out Labela
16 to 1048575
l Specifies the MPLS label that data carries when leaving a reverse tunnel. l This parameter can be set for only ingress and transit nodes.
Out Board/Logic Interface Type Out Port
Specifies the board where the egress port of a forward tunnel is located. Specifies the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. l Specifies the MPLS label that data carries when leaving a forward tunnel. l This parameter can be set for only ingress and transit nodes.
Forward Out Labela
16 to 1048575
Reverse In Labela
16 to 1048575
l Specifies the MPLS label that data carries when entering a reverse tunnel. l This parameter can be set for only egress and transit nodes.
B-402
Issue 03 (2011-04-10)
Parameter Forward Next Hop Address
Value Range -
Default Value -
Description l Indicates or specifies the IP address of the next hop in a forward tunnel. l This parameter can be set for only ingress and transit nodes.
Reverse Next Hop Address
l Indicates or specifies the IP address of the next hop in a reverse tunnel. l This parameter can be set for only egress and transit nodes.
Source Node
l Specifies the LSR ID of the ingress node. l This parameter can be set for only egress nodes and transit nodes.
Sink Node
l Specifies the LSR ID of the egress node. l This parameter can be set for only ingress and transmit nodes.
Tunnel Type
E-LSP L-LSP
E-LSP
l Specifies the tunnel type. l The value E-LSP indicates that the EXP field is used to identify packet scheduling priorities of PWs. An E-LSP tunnel can contain PWs of eight packet scheduling priorities. l The value L-LSP indicates that the MPLS label value is used to identify packet scheduling priorities of PWs. An L-LSP tunnel can contain PWs of the same packet scheduling priority.
Issue 03 (2011-04-10)
B-403
Parameter EXP
Value Range 0 to 7 None
Default Value None
Description l Specifies the value of the EXP field in the packets transmitted through MPLS tunnels. l This parameter cannot be set if Node Type is Transit. l If this parameter is set to a value from 0 to 7, the EXP field assumes the fixed value. l If this parameter takes the default value None, the EXP field is set based on the DiffServ mappings.
LSP Mode
Pipe
NOTE The OptiX RTN 950 supports only the value Pipe.
MTU
B-404
Issue 03 (2011-04-10)
Parameter CoS
Default Value BE
Description l This parameter specifies the PHB service class of an LLSP, if the type of an MPLS tunnel is L-LSP. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
NOTE
At an MPLS node, in labels must be different from each other, out labels must also be different from each other, but out labels can be the same as in labels.
Related Tasks
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
Issue 03 (2011-04-10)
B-405
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameter tab.
2.

Parameter Tunnel ID Tunnel Name Node Type Value Range Default Value Description Displays the tunnel ID. Displays the tunnel name. l Displays the node type. l For bidirectional tunnels, this parameter displays the node types of forward tunnels. Tunnel Direction OAM Status Enabled Disabled Disabled Displays the direction of a tunnel. l Specifies or displays whether the local node can perform and respond to OAM operations. l If OAM Status is Enabled, the local NE can perform and respond to OAM operations. l If OAM Status is Disabled, the local NE cannot perform and respond to OAM operations. l If MPLS APS protection needs to be configured or a CC test needs to be performed for the tunnel, OAM Status needs to be set to Enabled.
B-406
Issue 03 (2011-04-10)
Description l Specifies or displays the MPLS OAM detection mode. l Manual: During a CC test, MPLS OAM packets are sent at the interval specified by the user. l Auto-Sensing: During a CC test, MPLS OAM packets are sent at the interval for receiving MPLS OAM packets. l For a unidirectional tunnel, this parameter can be set for its egress node only. l For a bidirectional tunnel, if Detection Mode is set to Manual, you need to set the MPLS OAM detection packets to be received and transmitted. l Generally, the value Auto-Sensing is recommended.
Issue 03 (2011-04-10)
B-407
Value Range CV FFD
Default Value CV
Description 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. l For the egress node of a unidirectional tunnel, if Detection Mode is set to Manual, this parameter specifies the type of MPLS OAM detection packets to be received. l For a bidirectional tunnel, if Detection Mode is set to AutoSensing, this parameter specifies the type of MPLS OAM detection packets to be transmitted. l For a bidirectional tunnel, if Detection Mode is set to Manual, this parameter specifies the types of MPLS OAM detection packets to be received and transmitted. l The value FFD is assumed for MPLS APS and the value CV is assumed for continuous connectivity check on MPLS tunnels.
B-408
Issue 03 (2011-04-10)
Parameter Detection Packet Period (ms)
Value Range 3.3 10 20 50 100 200 500
Default Value 50
Description l Displays or specifies the OAM detection period. l This parameter is available only when Detection Packet Type is FFD. It takes its fixed value of 1000 ms when Detection Packet Type is CV. l Set this parameter to 3.3 for MPLS APS usually. If the packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission interval of FFD packets needs to be a value greater than the delay time.
Reverse Tunnel
l Specifies the mapping reverse tunnel of a forward tunnel. l For a bidirectional tunnel, this parameter cannot be set.
CV/FFD Status LSP Status LSP Defect Type Disable LSP Duration (ms) LSP Defect Location
Displays whether CV/ FFD is enabled. Displays whether an LSP is available. Displays the LSP defect type. Displays the duration when an LSP is unavailable. Displays the LSR ID of a node where LSP defects are detected.
Issue 03 (2011-04-10)
B-409
Parameter SD Threshold
Value Range 0-100
Default Value 0
Description l Specifies or displays the SD threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l For a unidirectional tunnel, this parameter can be set for its egress node only. l When this parameter is set to 0, SD threshold detection is not supported.
SF Threshold
0-100
l Specifies or displays the SF threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l For a unidirectional tunnel, this parameter can be set for its egress node only. l When this parameter is set to 0, SF threshold detection is not supported. l The SD threshold is not higher than the SF threshold.
Source Node Sink Node
Displays the source node of a tunnel. Displays the sink node of a tunnel.
Related Tasks
A.8.2.6 Setting MPLS OAM Parameters
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the FDI tab.
2.

Parameter Enable FDI Value Range Selected Not selected Default Value Selected Description l Specifies or displays whether Enable FDI is selected. l If the FDI function is enabled for a transit node, the transit node inserts an FDI packet to all LSPs that travel through the transit node when a fault occurs on the link between the ingress and transit nodes. On reception of the FDI packet, the egress node reports an alarm. In this case, if MPLS APS is configured correctly, protection switching is triggered before the egress node detects an LSP defect within a detection period. l Generally, the default parameter value is recommended.
Related Tasks
A.8.2.7 Enabling/Disabling FDI
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.
Issue 03 (2011-04-10)
B-411
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameters tab. Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping Test from the drop-down list.
2. 3.

Parameter Packet Count EXP Value Value Range 1 to 4294967295 0 to 7 Default Value 3 7 Description Specifies the number of test request packets. l Specifies the EXP value of the MPLS label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the MPLS label in test request packets. l The default value is recommended. Transmit Interval (10ms) 1 to 1000 100 l Specifies the interval for transmitting test request packets. l The default value is recommended. Packet Length 64 to 1400 64 l Specifies the length of test request packets. l The default value is recommended. Wait-to-Response Timeout Time(10ms) 1 to 6000 300 l Specifies the wait-toresponse timeout value. l The default value is recommended.
B-412
Issue 03 (2011-04-10)
Parameter Response Mode
Value Range IPv4 UDP Response No Response Application Control Channel
Default Value IPv4 UDP Response
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP Response indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP Response is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the egress node. If the egress node supports reverse channel response, set this parameter to Application Control Channel. If the egress node does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
Issue 03 (2011-04-10)
B-413
Parameter
Value Range
Default Value
Description
NOTE For a unidirectional tunnel, Response Mode cannot be set to Application Control Channel.
Related Tasks
A.8.2.11 Performing an LSP Ping Test
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute

This topic describes the parameters that are related to the LSP Traceroute test.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameters tab. Select the required tunnel, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
2. 3.

Parameter EXP Value Value Range 0 to 7 Default Value 7 Description l Specifies the EXP value of the MPLS label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the MPLS label in test request packets. l The default value is recommended. Packet Length 84 to 1400 84 l Specifies the length of test request packets. l The default value is recommended.
Parameter Wait-to-Response Timeout Time(10ms)
Default Value 300
Description l Specifies the wait-toresponse timeout value. l The default value is recommended.
Issue 03 (2011-04-10)
B-415
Value Range IPv4 UDP Response No Response Application Control Channel
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP Response indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP Response is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the egress node. If the egress node supports reverse channel response, set this parameter to Application Control Channel. If the egress node does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
B-416
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description
NOTE For a unidirectional tunnel, Response Mode cannot be set to Application Control Channel.
Related Tasks
A.8.2.12 Performing an LSP Traceroute Test
B.9.1.9 Parameter Description: PW Management_PW Management

This topic describes parameters that are related to PW management.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW Management tab. Click the PW Management tab.

Parameter PW ID Enable State PW Signaling Type PW Type Value Range Default Value Description Displays the ID of the PW that carries a service. Displays whether a PW is enabled. Displays the PW signaling type.
NOTE The OptiX RTN 950 uses only static PWs.
l Displays the PW type. Different PW types perform different service processing modes. l When a PW transmits E-Line services, set PW Type to Ethernet or Ethernet Tagged Mode. l If a PW transmits CES services, set PW Type to CESoPSN or SATop. l If a PW transmits ATM services, set PW Type to ATM n-to-one VCC Cell transport, ATM one-to-one VCC Cell Mode, ATM n-to-one VPC Cell transport, or ATM one-to-one VPC Cell Mode.
Issue 03 (2011-04-10)
B-417
Parameter Direction PW Ingress Label/Source Port PW Encapsulation Type
Value Range -
Default Value -
Description Displays the direction of a PW. Displays the ingress label at the source port of a PW. Displays the encapsulation type of the packets on a PW.
NOTE The OptiX RTN 950 supports only MPLS encapsulation.
PW Egress Label/Sink Port Opposite LSR ID Local Working Status Remote Working Status Compositive Working Status Tunnel Type
Displays the egress label at the sink port of a PW. Displays the LSR ID of the node at the other end of a PW. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end. Displays the working status of the entire PW.
Displays the type of the tunnel that carries a PW.

NOTE The OptiX RTN 950 supports only MPLS tunnels.
Tunnel
Displays the ID of the tunnel that carries a PW.
QoS Parameters
Table B-70 CES services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service.
B-418
Issue 03 (2011-04-10)
Parameter CIR(kbit/s) EXP
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Table B-71 E-Line services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service. Displays whether the bandwidth is limited. Displays the committed information rate (CIR) of a PW. Displays the committed burst size (CBS) of a PW. Displays the peak information rate (PIR) of a PW Displays the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. Displays the LSP mode.
NOTE The OptiX RTN 950 supports only Pipe.
Bandwidth Limit CIR(kbit/s)
CBS(byte) PIR(kbit/s)
Policy
Issue 03 (2011-04-10)
B-419
Table B-72 ATM services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service. Displays whether the bandwidth is limited. Displays the committed information rate (CIR) of a PW. Displays the committed burst size (CBS) of a PW. Displays the peak information rate (PIR) of a PW Displays the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Bandwidth Limit CIR(kbit/s)
PBS(byte) EXP Policy

Table B-73 CES services Parameter RTP Head Value Range Default Value Description Displays whether the CES service packets carry an RTP header. Displays the packet loading time. Displays the jitter buffer time for the received CES packets. The OptiX RTN 950 does not support this parameter.
Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode
B-420
Issue 03 (2011-04-10)
Parameter Egress Clock Mode Control Channel Type VCCV Verification Mode Enable CES Service Alarm Transparent Transmission Threshold of Entering R bit Inserting Status
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. Displays the control channel type. Displays the VCCV mode. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Threshold of Exiting R bit Inserting Status
Sequence Number Mode
Table B-74 E-Line services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode.
Control Channel Type VCCV Verification Mode
Issue 03 (2011-04-10)
B-421
Parameter Request VLAN
Value Range -
Default Value -
Description When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs.
Table B-75 ATM services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. Displays the control channel type. Displays the VCCV mode. Displays the maximum number of concatenated cells. Displays the packet loading time.
Control Channel Type VCCV Verification Mode Max Concatenated Cell Count Packet Loading Time (us)
Related Tasks
A.8.4.1 Querying Information and Running Status of PWs
B.9.1.10 Parameter Description: PW Management_MS-PW Creation

This topic describes the parameters that are related to MS-PW creation.
Navigation Path
1. 2. 3. 4. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW Management tab. Click the MS PW tab. Click New.
B-422
Issue 03 (2011-04-10)

Parameter ID Name MTU(bytes) Service Type Value Range ETH Service CES Service ATM Service Connection Type Port Transparent PVP PVC Port Transparent Default Value ETH Service Description Specifies the ID of MS-PW. Specifies the name of MS-PW. The OptiX RTN 950 does not support this parameter. l Specifies the type of services carried by the MS-PW. l Set this parameter according to the planning information. l This parameter is available only when Service Type is ATM Service. l PVP: Only the VPIs of the source and sink are exchanged. l PVP: The VPIs and VCIs of the source and sink are exchanged. l Port Transparent: ATM transparent transmission refers to the transparent transmission of ATM cells that are encapsulated into PWs as payloads.
Parameters for the Basic Attributes of PWs

Parameter PW ID Value Range Default Value Description Specifies the ID of the PW that carries services. Automatic ID assignment is recommended. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned.
PW Signaling Type
Static
Static
Issue 03 (2011-04-10)
B-423
Parameter PW Type
Value Range -
Default Value -
Description l Specifies the type of the PW. l Set this parameter to Ethernet if Service Type is ETH Service and no VLAN IDs need to be added. If it is required to add VLAN IDs, set this parameter to Ethernet Tag Mode and then set Request VLAN in the Advanced Attribute tab. l If Service Type is CES Service, the value CESoPSN indicates structureaware emulation, which allows timeslot compression; the value SAToP indicates structure-agnostic emulation, which does not allow timeslot compression. l If Service Type is ATM Service, set this parameter according to the value of Connection Type.
Displays the direction of the PW. Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Specifies the method to select tunnels.
NOTE The OptiX RTN 950 supports only the value Manually.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Selection Mode
16 to 1048575 16 to 1048575 Manually
Manually
B-424
Issue 03 (2011-04-10)
Parameter Tunnel Type Ingress Tunnel
Value Range MPLS -
Default Value MPLS -
Description Specifies the type of the tunnel that carries the PW. A created tunnel needs to be selected. If no tunnel is available, no PW can be created. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
Peer LSR ID
Egress Tunnel
QoS Parameters CES Services

Parameter EXP Value Range Default Value Description The OptiX RTN 950 does not support this parameter.
Ethernet services
Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
Issue 03 (2011-04-10)
B-425
Parameter Policy CIR(Kbit/s)
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
CBS(byte) PIR(Kbit/s)
Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR.
Pipe
Pipe
Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
B-426
Issue 03 (2011-04-10)
ATM services
Table B-76 ATM services Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. Policy CIR (Kbit/s) The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of the PW. It is recommended that you set this parameter to the same value as PIR. CBS (kbyte) PIR (kbit/s) Specifies the excess burst size of the PW. Specifies the peak information rate (PIR) of the PW. It is recommended that you set this parameter to the same value as CIR. PBS (kbyte) Specifies the maximum excess burst size of the PW.
Issue 03 (2011-04-10)
B-427
Parameter EXP
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter.
Parameters for the Advanced Attributes of PWs CES Services

Parameter RTP Header Value Range Disable Enable Default Value Disable Description l Specifies the RTP header. l The RTP header carries time stamps. l The default value is recommended. Jitter Compensation Buffering Time(us) 375 to 16000 8000 l Specifies the jitter buffer time for the received CES packets. l A greater value of this parameter means fewer impacts of transmission jitters on CES services, greater delays of CES services, and more resources occupied by CES services. l The default value is recommended.
NOTE Set Jitter Compensation Buffering Time(us) to a value greater than the value of Packet Loading Time (us) at the opposite end and the local end.
B-428
Issue 03 (2011-04-10)
Parameter Packet Loading Time (us)
Default Value 1000
Description l Specifies the length of fragments in the TDM data stream. Each fragment is encapsulated into one PW packet. l A greater value of this parameter means higher encapsulation efficiency but greater delays of CES services. l The default value is recommended.
Ingress Clock mode Egress Clock mode Control Channel Type
None CW Alert Label
CW
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. l The value CW indicates that the control word is supported.
None Ping
Ping
l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, do not set this parameter to None.
Issue 03 (2011-04-10)
B-429
Parameter 64K Timeslot Number
Value Range 1 to 31
Default Value 1
Description l Specifies the number of 64 kbit/s timeslots that transmit service traffic. If Frame Mode of the opposite end is 30, the source 64 kbit/s timeslots at the local end must include the 16th timeslot. l On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must be the same. l This parameter is unavailable if PW Type is SAToP.
Huawei Mode
Specifies the sequence number mode.
Ethernet services
Parameter Control Word Value Range No Use Default Value No Use Description For ETH PWE3 services, the parameter value is always No Use. l Specifies the mode of PW connectivity check. l None indicates that VCCV is not used. l Alert Label indicates VCCV packets in Alert Label encapsulation mode.
None Alert Label
Alert Label
B-430
Issue 03 (2011-04-10)
Parameter VCCV Verification Mode
Value Range Ping None
Default Value Ping
Description l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, do not set this parameter to None.
Request VLAN
l Set this parameter when PW Type is Ethernet Tagged Mode. l If the received packets do not carry any VLAN IDs, the PW will add VLAN IDs to the packets as required by the setting of this parameter.
ATM services
Parameter Control Word Value Range Must Use No Use Default Value Must Use Description l Specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Set Control Word to Must Use if PW Type is ATM 1:1.
Issue 03 (2011-04-10)
B-431
Parameter Control Channel Type
Value Range CW None Alert Label
Default Value CW
Description l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode.
Ping None
Ping
Max. Concatenated Cell Count
1 to 31
10
l Specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
B-432
Issue 03 (2011-04-10)
Parameter Packet Loading Time (us)
Default Value 1000
Description l Specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.
Related Tasks
A.8.4.2 Creating an MS-PW
B.9.1.11 Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab.

Parameter PW ID PW Type Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the type of the PW that carries the service.
Issue 03 (2011-04-10)
B-433
Description l Specifies or displays whether the local node can perform and respond to OAM operations. l If OAM Status is Enabled, the local NE can perform and respond to OAM operations. l If OAM Status is Disabled, the local NE cannot perform and respond to OAM operations. l If PW APS protection needs to be configured or a CC test needs to be performed for the tunnel, OAM Status needs to be set to Enabled.
Detection Mode
Auto-Sensing Manual
Auto-Sensing
l Specifies or displays the detection mode for PW OAM packets. l Manual: During a CC test, PW OAM packets are sent at the interval specified by the user. l Auto-Sensing: During a CC test, PW OAM packets are sent at the interval for receiving PW OAM packets. l If Detection Mode is set to Manual, you need to set the type of PW OAM detection packets to be received and transmitted. l The value AutoSensing is recommended.
B-434
Issue 03 (2011-04-10)
Value Range CV FFD
Default Value CV
Description 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. l If Detection Mode is set to Auto-Sensing, this parameter specifies the type of PW OAM detection packets to be transmitted. l If Detection Mode is set to Manual, this parameter specifies the type of PW OAM detection packets to be received and transmitted. l The value FFD is assumed for PW APS and the value CV is assumed for continuous connectivity check on PWs.
3.3 10 20 50 100 200 500
50
l Displays or specifies the OAM detection period. l If Detection Packet Type is FFD, this parameter can be set; if Detection Packet Type is CV, the value is always 1000. l Set this parameter to 3.3 for PW APS usually. If the packet transmission delay time of a PW exceeds 3.3 ms, the transmission interval of FFD packets needs to be a value greater than the delay time.
Issue 03 (2011-04-10)
B-435
Parameter SD Threshold (%)
Value Range 0-100
Default Value 0
Description l Specifies or displays the SD threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l When this parameter is set to 0, SD threshold detection is not supported.
SF Threshold (%)
0-100
l Specifies or displays the SF threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l When this parameter is set to 0, SF threshold detection is not supported. l The SD threshold is not higher than the SF threshold.
LSR ID to Be Received
l Specifies or displays the LSR ID to be received. l This parameter is available only if OAM Status is Disabled.
PW ID to be Received
l Specifies or displays the PW ID to be received. l This parameter is available only if OAM Status is Disabled.
Local Working Status Local PW Defect Type Local Disable PW Duration(ms)
Displays whether PWs at the local end are available. Displays the local PW defect type. Displays the duration when the local PW is unavailable.
B-436
Issue 03 (2011-04-10)
Parameter Local PW Defect Location Remote Working Status
Value Range -
Default Value -
Description Displays the local PW defect location. Displays whether PWs at the remote end are available. Displays the remote PW defect type. Displays the duration when the remote PW is unavailable. Displays the remote PW defect location.
Remote PW Defect Type Remote Disable PW Duration(ms) Remote PW Defect Location
Related Tasks
A.8.4.3 Setting PW OAM Parameters
B.9.1.12 Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab. Select the required PW and click OAM Operation > PW Ping Test.

Parameter Packet Count EXP Value Value Range 1 to 4294967295 0 to 7 Default Value 3 7 Description Specifies the number of test request packets. l Specifies the EXP value of the PW label in test request packets. The value 7 indicates the highest priority. l The default value is recommended.
Issue 03 (2011-04-10)
B-437
Parameter TTL
Default Value 255
Description l Specifies the time-tolive (TTL) value of the PW label in test request packets. l The default value is recommended.
Transmit Interval (10ms)
1 to 1000
100
l Specifies the interval for transmitting test request packets. l The default value is recommended.
Packet Length
64 to 1400
64
l Specifies the length of test request packets. l The default value is recommended.
Wait-to-Response Timeout Time(10ms)
1 to 6000
300
l Specifies the wait-toresponse timeout value. l The default value is recommended.
B-438
Issue 03 (2011-04-10)
Value Range IPv4 UDP Response No Response Application Control Channel Response
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel Response indicates that response is performed through the reverse channel. l The value IPv4 UDP indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the remote PE. If the remote PE supports reverse channel response, set this parameter to Application Control Channel Response. If the remote PE does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
Issue 03 (2011-04-10)
B-439
Parameter PW Peer ID PW Peer IP
Value Range -
Default Value -
Description Specifies the PW ID of the peer end. Specifies the IP address of the peer port.
Related Tasks
A.8.4.4 Performing a PW Ping Test
B.9.1.13 Parameter Description: PW Management_PW Traceroute

This topic describes the parameters that are related to the PW Traceroute test.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab. Select the required PW, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.

Parameter EXP Value Value Range 0 to 7 Default Value 7 Description l Specifies the EXP value of the PW label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the PW label in test request packets. l The default value is recommended. Packet Length 84 to 1400 84 l Specifies the length of test request packets. l The default value is recommended.
B-440
Issue 03 (2011-04-10)
Parameter Wait-to-Response Timeout Time(10ms)
Default Value 300
Description l Specifies the wait-toresponse timeout value. l The default value is recommended.
Issue 03 (2011-04-10)
B-441
Value Range IPv4 UDP Response No Response Application Control Channel Response
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel Response indicates that response is performed through the reverse channel. l The value IPv4 UDP indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the remote PE. If the remote PE supports reverse channel response, set this parameter to Application Control Channel Response. If the remote PE does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
B-442
Issue 03 (2011-04-10)
Related Tasks
A.8.4.5 Performing a PW Traceroute Test
B.9.1.14 Parameter Description: MPLS APS Protection Management

This topic describes parameters that are related to MPLS APS protection management.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab.

Parameter Protection Group ID Value Range Default Value Description l Displays the protection group ID. l The system automatically assigns IDs to the protection groups according to their creation sequence. Protection Type Switching Mode Dual-Ended Single-Ended Displays the protection group type. l Displays or specifies the switching mode of a protection group. l The value SingleEnded indicates that services are switched only in the direction where faults occur. l The value DualEnded indicates that services in both positive and reverse directions are switched to their protection channels when faults occur. l It is recommended that you set this parameter to Dual-Ended.
Issue 03 (2011-04-10)
B-443
Parameter BDI Status
Default Value -
Description l Specifies or displays whether the protection switching is triggered upon receiving BDI packets. l This parameter is available only when Switching Mode is set to Single-Ended. l If BDI Status is set to Enabled, the egress node notifies the ingress node of any detected faults by sending BDI packets; upon receiving BDI packets, the ingress node triggers protection switching.
Revertive Mode
l Specifies or displays whether to switch services to the original working tunnel after the fault is rectified. l The value Revertive indicates to perform the switching; the value Non-Revertive indicates not to perform the switching. l It is recommended that you set this parameter to Revertive.
B-444
Issue 03 (2011-04-10)
Value Range 1-12
Default Value -
Description l Specifies and displays the WTR time of the protection group. l When the preset WTR time expires after the original working tunnel recovers, services are switched to the original working tunnel. l This parameter is available only when Revertive Mode is Revertive. l It is recommended that you set this parameter to 5.
Hold-Time(100ms)
0-100
l Specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but wait until the hold-off time expires, and then detect whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered. l It is recommended that you set this parameter to 0.
Protocol Status Switching Status
Displays the protocol status. Displays the switching status of the protection group. Displays whether a tunnel is a working or protection tunnel.
Unit
Issue 03 (2011-04-10)
B-445
Parameter Active Tunnel Tunnel Status Tunnel Type Ingress Tunnel Egress Tunnel
Value Range -
Default Value -
Description Displays the currently used tunnel. Displays the tunnel status. Displays the tunnel type. Displays the ingress tunnel. Displays the egress tunnel.
Related Tasks
A.8.3.2 Querying MPLS APS Status
B.9.1.15 Parameter Description: Tunnel Protection Group_Creation

This topic describes the parameters that are related to creating a tunnel protection group.
Navigation Path
1. 2. 3. In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab. Click New.

Parameter Protection Type Value Range 1:1 Default Value 1:1 Description Specifies the protection type of the tunnel protection group.
NOTE The OptiX RTN 950 supports only the value 1:1.
B-446
Issue 03 (2011-04-10)
Parameter Switching Mode
Value Range Single-Ended Dual-Ended
Default Value Dual-Ended
Description l Specifies the switching mode to be adopted when a tunnel fails. l The value SingleEnded indicates that services are switched only in the direction where faults occur. l The value DualEnded indicates that services are switched to the protection channel in both directions when faults occur. l The value DualEnded is recommended.
BDI Status
Enabled Disabled
Disabled
l Specifies whether the protection switching is triggered upon receiving BDI packets. l This parameter is available only when Switching Mode is set to Single-Ended. l If BDI Status is set to Enabled, the egress node notifies the ingress node of any detected faults by sending BDI packets; upon receiving BDI packets, the ingress node triggers the protection switching.
Working Tunnel Type
MPLS Tunnel
MPLS Tunnel
Specifies the type of the working tunnel.

NOTE The OptiX RTN 950 supports only the value MPLS Tunnel.
Issue 03 (2011-04-10)
B-447
Parameter Working Ingress Tunnel ID
Value Range -
Default Value -
Description l Specifies the working tunnel of the protection group in the ingress direction. l If this parameter is set for a bidirectional tunnel, a value is automatically assigned to the parameter Working Egress Tunnel ID.
Working Ingress Tunnel Name Working Egress Tunnel ID
Displays the name of the working tunnel in the ingress direction. l Specifies the working tunnel of the protection group in the egress direction. l For a bidirectional tunnel, if the parameter Working Ingress Tunnel ID is set, a value is automatically assigned to the parameter Working Egress Tunnel ID.
Working Egress Tunnel Name Protection Tunnel Type
Displays the name of the working tunnel in the egress direction. Displays the type of protection tunnel, which is the same as the type of working tunnel. l Specifies the working tunnel of the protection group in the ingress direction. l If this parameter is set for a bidirectional tunnel, a value is automatically assigned to the parameter Protection Egress Tunnel ID.
Protection Ingress Tunnel ID
B-448
Issue 03 (2011-04-10)
Parameter Protection Ingress Tunnel Name Protection Egress Tunnel ID
Value Range -
Default Value -
Description Displays the name of the protection tunnel in the ingress direction. l Specifies the protection tunnel of the protection group in the egress direction. l For a bidirectional tunnel, if the parameter Protection Ingress Tunnel ID is set, a value is automatically assigned to the parameter Protection Egress Tunnel ID.
Protection Egress Tunnel Name Revertive Mode
Displays the name of the protection tunnel in the egress direction. l This parameter specifies whether to switch services back to the original working tunnel after it recovers. l The value Revertive indicates to switch services back to the original working tunnel after it recovers; the value NonRevertive indicates not to switch services back to the original working tunnel after it recovers. l The value Revertive is recommended.
Non-Revertive
Issue 03 (2011-04-10)
B-449
Parameter WTR Time(m)
Value Range 1 to 12
Default Value 5
Description l Specifies the WTR time of the protection group. l When the preset WTR time expires after the original working tunnel recovers, services are switched to the original working tunnel. l This parameter is available only when Revertive Mode is Revertive. l The default value is recommended.
Hold-Time(100ms)
0 to 100
l Specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered. l The default value is recommended.
Protocol Status
Disabled Enabled
Disabled
l Specifies the protocol status. l During the creation of a protection group, set Protocol Status to Disabled. After the APS protection group is configured at both ends, set Protocol Status to Enabled.
B-450
Issue 03 (2011-04-10)
Related Tasks
A.8.3.1 Creating an MPLS APS Protection Group
B.9.1.16 Parameter Description: PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
Navigation Path
The navigation path for CES services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click the Protect Group tab. Click the PW APS tab. Click New.
The navigation path for E-Line services is as follows: 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the Protect Group tab. Click the PW APS tab. Click New.
The navigation path for ATM services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click the Protect Group tab. Click the PW APS tab. Click New.

Parameter PW ID PW Signaling Type Value Range Static Default Value Static Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. Displays the PW type. Displays the direction of the PW.
PW Type PW Direction
Issue 03 (2011-04-10)
B-451
Parameter PW Encapsulation Type
Value Range -
Default Value -
Description Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the type of the tunnel that carries the PW. A tunnel needs to be created or selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
16 to 1048575 16 to 1048575 MPLS New Use existing resource
MPLS New
Peer LSR ID
Egress Tunnel
New
QoS Parameters
Table B-77 CES services Parameter EXP Value Range Default Value Description The OptiX RTN 950 does not support this parameter.
Table B-78 E-Line services Parameter PW ID Direction PW Type Value Range Default Value Description Displays the ID of the PW. Displays the direction of the PW. Displays the PW type.
B-452
Issue 03 (2011-04-10)
Default Value -
Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
Policy CIR(kbit/s)
The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. Displays the LSP mode.
Issue 03 (2011-04-10)
B-453
Table B-79 ATM services Parameter PW ID Direction PW Type Bandwidth Limit Value Range Disabled Enabled Default Value Description Displays the ID of the PW. Displays the direction of the PW. Displays the PW type. Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. CIR(kbit/s) Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP Policy Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
B-454
Issue 03 (2011-04-10)

Table B-80 CES services Parameter RTP Head Value Range Default Value Description Displays whether the CES service packets carry an RTP header. Displays the packet loading time. Displays the jitter buffer time for the received CES packets. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Displays the mode of PW connectivity check. Displays the VCCV verification mode. The VCCV verification is used for PW connectivity check. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode Egress Clock Mode Control Channel Type VCCV Verification Mode
Enable CES Service Alarm Transparent Transmission Threshold of Entering R bit Inserting Status
Issue 03 (2011-04-10)
B-455
Table B-81 E-Line services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode. When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs.
Control Channel Type VCCV Verification Mode Request VLAN
B-456
Issue 03 (2011-04-10)

Parameter Protection Type Protection Group ID Enabling Status Value Range Disabled Enabled Default Value Enabled Description Specifies the protection type. Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled. Protection Mode Displays the protection mode.
Switching Mode

Revertive
Revertive
Issue 03 (2011-04-10)
B-457
Value Range 1 to 12
Default Value 1
Description l Specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive. l The default value is recommended.
0 to 100
OAM Parameters
Parameter OAM Status Value Range Default Value Description Displays the enabling status of PW OAM.
B-458
Issue 03 (2011-04-10)
Issue 03 (2011-04-10)
B-459
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
Related Tasks
A.8.5.1 Creating a PW APS Protection Group
B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a slave protection pair of a PW APS protection group.
Navigation Path
The navigation path for CES services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click the Protect Group tab. Click the Slave Protection Pair tab. Click New.
The navigation path for E-Line services is as follows: 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the Protect Group tab. Click the Slave Protection Pair tab. Click New.
The navigation path for ATM services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click the Protect Group tab. Click the Slave Protection Pair tab. Click New.

Parameter PW ID PW Signaling Type Value Range Static Default Value Static Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. Displays the PW type. Displays the direction of the PW. Displays the encapsulation type of the PW.
B-461
PW Type PW Direction PW Encapsulation Type
Issue 03 (2011-04-10)
Parameter PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
Value Range 16 to 1048575 16 to 1048575 MPLS New Use existing resource
Default Value MPLS New
Description Specifies the PW Ingress label. Specifies the PW Egress label. Displays the type of the tunnel that carries the PW. A tunnel needs to be created or selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
Peer LSR ID
Egress Tunnel
New
QoS Parameters
Table B-83 CES services Parameter EXP Value Range Default Value Description The OptiX RTN 950 does not support this parameter.
Table B-84 E-Line services Parameter PW ID Direction PW Type Value Range Default Value Description Displays the ID of the PW. Displays the direction of the PW. Displays the PW type.
B-462
Issue 03 (2011-04-10)
Default Value -
Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
Policy CIR(kbit/s)
The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. Displays the LSP mode.
Issue 03 (2011-04-10)
B-463
Table B-85 ATM services Parameter PW ID Direction PW Type Bandwidth Limit Value Range Disabled Enabled Default Value Description Displays the ID of the PW. Displays the direction of the PW. Displays the PW type. Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. CIR(kbit/s) Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP Policy Specifies the peak burst size (PBS) of a PW. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
B-464
Issue 03 (2011-04-10)

Table B-86 CES services Parameter RTP Head Value Range Default Value Description Displays whether the CES service packets carry an RTP header. Displays the packet loading time. Displays the jitter buffer time for the received CES packets. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Displays the mode of PW connectivity check. Displays the VCCV verification mode. The VCCV verification is used for PW connectivity check. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode Egress Clock Mode Control Channel Type VCCV Verification Mode
Enable CES Service Alarm Transparent Transmission Threshold of Entering R bit Inserting Status
Issue 03 (2011-04-10)
B-465
Table B-87 E-Line services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode. When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs.
Control Channel Type VCCV Verification Mode Request VLAN
B-466
Issue 03 (2011-04-10)

Parameter Protection Mode Protection Group ID Value Range Default Value Description Displays the protection mode. Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Related Tasks
A.8.5.2 Configuring Slave Protection Pairs of PW APS
B.9.2 CES Parameters

This topic describes parameters that are related to CES services. B.9.2.1 Parameter Description: CES Service Management This topic describes the parameters that are related to CES service management. B.9.2.2 Parameter Description: CES Service Management_Creation This topic describes the parameters that are related to creating CES services.

This topic describes the parameters that are related to CES service management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree.

Parameter Service ID Service name Level Value Range Default Value Description Displays the ID of the CES service to be created. Displays or specifies the service name. Displays the level of the received TDM frames.
B-467
Issue 03 (2011-04-10)
Parameter Source Board Source High Channel
Value Range -
Default Value -
Description Displays the source board of the CES service. For the OptiX RTN 950, this parameter cannot be configured. Displays the source lower order path. Displays the source 64 kbit/s timeslot. l Specifies the priority of a CES service. This parameter is available only when Mode is set to UNI-NNI. l This parameter needs to be configured if QoS processing needs to be performed for different CES services. l CS6-CS7: indicate the highest service classes, which are mainly involved in signaling transmission. l EF: indicates the expedited forwarding of service, which is applicable to services of low transmission delay and low packet loss rate, for example, voice and video services. l AF1-AF4: indicate the assured forwarding classes of service, which are applicable to services that require an assured rate but no delay or jitter limit. l BE: is applicable to services that need not be processed in a special manner. l The default value is recommended.
Source Low Channel Source 64K Timeslot Pri
CS7 CS6 EF AF4 AF3 AF2 AF1 BE
B-468
Issue 03 (2011-04-10)
Parameter PW ID
Value Range -
Default Value -
Description Displays the ID of the PW that carries the CES service. This parameter is meaningful when the CES service type is UNI-NNI. Displays the tunnel that carries the PW. The tunnel must have been configured in advance. This parameter is meaningful when the CES service type is UNI-NNI. Displays the sink board of the CES service. This parameter is meaningful when the CES service type is UNI-UNI. For the OptiX RTN 950, this parameter cannot be configured. Displays the sink lower order path. This parameter is meaningful when the CES service type is UNIUNI. Displays the sink 64 kbit/s timeslot. This parameter is meaningful when the CES service type is UNI-UNI.
Tunnel
Sink Board
Sink High Channel
Sink Low Channel
Sink 64K Timeslot

Parameter PW ID Value Range Default Value Description Displays the ID of the PW that carries the CES service. Displays working status of the PW. Displays the enabling status of the PW.
Working Status PW Status
Issue 03 (2011-04-10)
B-469
Parameter PW Signaling Type
Value Range -
Default Value -
Description Displays the PW signaling type.

NOTE The OptiX RTN 950 supports static PWs only.
PW Type
Displays the PW type for CES service encapsulation. CESoPSN: Indicates structure-aware TDM circuit emulation service over packet switched network. Timeslot compression can be set. SAToP: Indicates structure-agnostic TDM over packet. Timeslot compression cannot be set. Displays the direction of the PW. Displays the tunnel type for PW encapsulation.
NOTE The OptiX RTN 950 supports MPLS only.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Peer LSR ID Local Operating Status
Displays the Ingress label of the PW that carries the CES service. Displays the Egress label of the PW that carries the CES service. Displays the LSR ID of the PW at the remote end. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end.
Remote Operating Status
B-470
Issue 03 (2011-04-10)
Parameter Overall Operating Status
Value Range -
Default Value -
Description Displays the compositive working status of the PW. The compositive working status is up when both ends are up, and is down when one end is down. Displays the type of the tunnel that carries the PW.
NOTE The OptiX RTN 950 supports MPLS tunnels only.
Tunnel type
Ingress Tunnel No
Displays the ID of the tunnel that carries the CES service. Displays the ID of the tunnel that carries the CES service. The OptiX RTN 950 does not support this parameter.
Egress Tunnel No
Tunnel For Auto Selection
QoS Parameters
Parameter PW ID Direction CIR(kbit/s) EXP Value Range Default Value Description Displays the PW ID. Displays the direction of the PW. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Parameters of Advanced Attributes

Parameter PW ID RTP Header Value Range Default Value Description Displays the PW ID. Displays the RTP header. The RTP header carries time stamps.
Issue 03 (2011-04-10)
B-471
Parameter Jitter Compensation Buffering Time(us)
Default Value -
Description l Displays or specifies the jitter buffer time. l The jitter buffer time guarantees the realtime performance of the CES service.
Packet Loading Time (us) Ingress Clock Mode Egress Clock Mode Control Channel Type VCCV Verification Mode
Displays the packet loading time. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Displays the mode of PW connectivity check. Displays the VCCV verification mode. The VCCV verification is used for PW connectivity check. Displays or specifies the enabling status of the transparent transmission of CES service alarms. If this function is enabled, the fault on the AC side of the CES service is notified to the remote end. Upon receiving the fault notification from the network side or the remote end, the local NE inserts the corresponding alarm to the AC side.
Enable CES Service Alarm Transparent Transmission
Enabled Disabled
B-472
Issue 03 (2011-04-10)
Parameter Threshold of Entering R Bit Inserting Status
Value Range 1-65535
Default Value -
Description Displays or specifies the threshold of packet loss ratio of CES services. The corresponding alarm will be reported once the actual packet loss ratio crosses this threshold. This parameter is available only when the transparent transmission of CES service alarms is enabled. Displays or specifies the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. This parameter is available only when the transparent transmission of CES service alarms is enabled. Specifies the sequence number mode. The Sequence Number Mode must be set to the same value at both ends of a radio link.
Threshold of Exiting R Bit Inserting Status
1-65535

NOTE
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW.
Working PW ID Protection PW ID
Issue 03 (2011-04-10)
B-473
Parameter Protection Mode Enabling Status
Default Value -
Description Displays the protection mode. l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Switchover Mode

Restoration Mode
l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
B-474
Issue 03 (2011-04-10)
Value Range 1 to 12
Default Value -
Description l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
0 to 100
Switchover Status
Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.

NOTE
The following parameters are available only after the slave protection pair is configured.
Issue 03 (2011-04-10)
B-475
Value Range -
Default Value -
Description Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair. Displays the PW type.
Working PW ID
Protection PW ID
PW Type
Related Tasks
A.8.6.2 Modifying CES Service Parameters A.8.6.3 Querying CES Service Information
B.9.2.2 Parameter Description: CES Service Management_Creation

This topic describes the parameters that are related to creating CES services.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click New.

Parameter Service ID(e.g.1,3-6) Value Range 1 to 4294967295 Default Value Description Specifies the service ID, which can also be automatically allocated. Specifies the service name. The value E1 indicates that the CES service is used to transmit the TDM services from E1 ports.
Issue 03 (2011-04-10)
Service name Level
E1
E1
B-476
Parameter Mode
Value Range UNI-NNI UNI-UNI
Default Value UNI-NNI
Description l Specifies the mode of CES service. l The value UNI-NNI indicates that the CES service is carried by a PW. Therefore, the information about the PW needs to be configured.
Source Board
Specifies the board where the source (UNI) of the CES service is located. The OptiX RTN 950 does not support this parameter. If Level is set to E1, this parameter indicates the E1 port where the service source is located. If Mode is set to UNI-NNI, this parameter can assume only one value. l Specifies the 64 kbit/s timeslot that transmits data. This parameter can assume multiple values. If Frame Mode of the opposite end is 30, the source 64 kbit/s timeslots at the local end must include the 16th timeslot. l On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must the same. l This parameter does not need to be set if Mode is UNI-NNI and PW Type is SAToP.
Source High Channel Source Low Channel (e.g.1,3-6)
Source 64K Timeslot (e.g.1,3-6)
1-31
1-31
Issue 03 (2011-04-10)
B-477
Parameter Pri
Default Value EF
Description l Specifies the priority of a CES service. This parameter is available only when Mode is set to UNI-NNI. l This parameter needs to be configured if QoS processing needs to be performed for different CES services. l CS6-CS7: indicate the highest service classes, which are mainly involved in signaling transmission. l EF: indicates the expedited forwarding of service, which is applicable to services of low transmission delay and low packet loss rate, for example, voice and video services. l AF1-AF4: indicate the assured forwarding classes of service, which are applicable to services that require an assured rate but no delay or jitter limit. l BE: is applicable to services that need not be processed in a special manner. l The default value is recommended.
B-478
Issue 03 (2011-04-10)
Description l Specifies the protection mode of the PW. This parameter is available only when Mode is UNI-NNI. l If this parameter is set to PW APS, working and protection PWs need to be configured. l When this parameter is set to Slave Protection Pair , you need to bind the slave PW APS protection group with the master PW APS protection group. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Sink Board
l Specifies the board where the sink of the CES service is located. l This parameter is available only when Mode is set to UNIUNI.
Sink High Channel Sink Low Channel(e.g. 1,3-6)
The OptiX RTN 950 does not support this parameter. l If Level is set to E1, this parameter indicates the E1 port where the service sink is located. l This parameter is available only when Mode is set to UNIUNI.
Issue 03 (2011-04-10)
B-479
Parameter Sink 64K Timeslot(e.g. 1,3-6)
Value Range 1-31
Default Value 1-31
Description l Specifies the 64 kbit/s timeslot that the service sink occupies. On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must the same. l This parameter is available only when Mode is set to UNIUNI.
Automatically Assign
Selected Deselected
Selected
Specifies whether to automatically allocate service IDs.

Parameter Port Name Port Mode Value Range Layer 1 Layer 2 Default Value Description Displays the port that carries the CES service. Displays or specifies the port mode. For CES services, this parameter must assume the value Layer 1. If Port Mode is set to Layer 1, Encapsulation Type assumes the default value Null and cannot assume any other values.
Encapsulation Type
B-480
Issue 03 (2011-04-10)
Parameter Frame Format
Value Range CRC-4 Multiframe Double Frame Unframe
Default Value -
Description l Displays or specifies the frame format. l If a CES service uses the emulation mode of CESoPSN, this parameter can assume the value CRC-4 Multiframe or Double Frame. The value CRC-4 Multiframe is recommended. l If a CES service uses the emulation mode of SAToP, this parameter needs to assume the value Unframe. l The value of Frame Format must be the same at the local and opposite ends.
Frame Mode
31 30
l 30 timeslots: In the E1 signal, timeslots 1 to 15 and 17 to 31 are used to transmit service data, and timeslot 16 is used to transmit signaling. l 31 timeslots: In the E1 signal, timeslots 1 to 31 are used to transmit service data. l This parameter is unavailable if Frame Format is set to Unframe. l The frame modes of the local port and opposite port need to be the same.
NOTE The OptiX RTN 950 does not support 30.
Issue 03 (2011-04-10)
B-481

NOTE
If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Parameter PW ID PW Signaling Type
Value Range Static
Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. l Specifies the type of the PW. This parameter is available only when Mode is UNI-NNI. l CESoPSN: Indicates structure-aware TDM circuit emulation service over packet switched network. Timeslot compression can be set. SAToP: Indicates structureagnostic TDM over packet. Timeslot compression cannot be set.
PW Type
CESoPSN SAToP
CESoPSN
Displays the direction of the PW. Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the type of the tunnel that carries the PW. A tunnel needs to be created or selected. If no tunnel is available, creation of a PW will fail.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Type Ingress Tunnel
16 to 1048575 16 to 1048575 MPLS New Use existing resource
MPLS New
B-482
Issue 03 (2011-04-10)
Parameter Peer LSR ID
Value Range -
Default Value -
Description Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
Egress Tunnel
New
QoS Parameters
Parameter EXP Value Range Default Value Description The OptiX RTN 950 does not support this parameter.
Parameters for the Advanced Attributes of PWs

Parameter RTP Header Value Range Disable Enable Huawei RTP Default Value Disable Description l Specifies the RTP header. l The RTP header carries time stamps. l The default value is recommended.
Issue 03 (2011-04-10)
B-483
Parameter Jitter Compensation Buffering Time (us)
Default Value 8000
Description l Specifies the jitter buffer time for the received CES packets. The step is 125. l A greater value of this parameter means fewer impacts of transmission jitters on CES services, greater delays of CES services, and more resources occupied by CES services. l The default value is recommended.
Packet Loading Time (us)
125 to 5000
1000
l Specifies the length of fragments in the TDM data stream. The step is 125. l A greater value of this parameter means higher encapsulation efficiency but greater delays of CES services. l The default value is recommended.
Ingress Clock Mode
Null Adaptive Clock Mode
Null
Egress Clock Mode
B-484
Issue 03 (2011-04-10)
Parameter Control Channel Type
Value Range None CW Alert Label
Default Value CW
Description l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. l The value CW indicates that the control word is supported.
None Ping
Ping
Enable CES Service Alarm Transparent Transmission
Disabled Enabled
Disabled
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 to the AC side.
Issue 03 (2011-04-10)
B-485
Parameter Threshold of Entering R Bit Inserting Status
Value Range 1-65535
Default Value 100
Description l The corresponding alarm will be reported if the number of consecutive lost packets crosses the threshold specified by this parameter. l This function is available only when the transparent transmission of CES service alarms is enabled.
Threshold of Exiting R Bit Inserting Status
1-65535
l The corresponding alarm will be cleared if the number of consecutive received packets crosses the threshold specified by this parameter. l This function is available only when the transparent transmission of CES service alarms is enabled.
Standard Mode
Specifies the sequence number mode. The Sequence Number Mode must be set to the same value at both ends of a radio link.

NOTE
Parameter Protection Type Protection Group ID
Value Range -
Default Value -
Description Specifies the protection type. Specifies the protection group ID.
B-486
Issue 03 (2011-04-10)
Parameter Enabling Status
Description l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Protection Mode
Displays the protection mode.

Switching Mode

Revertive
Revertive
Issue 03 (2011-04-10)
B-487
Value Range 1 to 12
Default Value 1
0 to 100
OAM Parameters
NOTE
Value Range -
Default Value -

Issue 03 (2011-04-10)
B-488
Issue 03 (2011-04-10)
B-489
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
B-490
Issue 03 (2011-04-10)

NOTE
Value Range -
Default Value -
Related Tasks
A.8.6.1 Creating CES Services
B.9.3 ATM Parameters

This topic describes the parameters that are related to ATM services. B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management This topic describes the parameters that are related to IMA group management. B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration This topic describes the parameters that are related to the bound paths in the ATM TRUNK. B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status This topic describes the parameters that are related to IMA group status. B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status This topic describes the parameters that are related to IMA link status. B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management This topic describes the parameters that are related to ATM interface management. B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table This topic describes the parameters that are related to configuration of the ATM service class mapping table. B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation This topic describes the parameters that are related to creation of the ATM service class mapping table. B.9.3.8 Parameter Description: ATM Policy Management This topic describes the parameters that are related to ATM policy management. B.9.3.9 Parameter Description: ATM Policy Management_Creation This topic describes the parameters that are related to creation of ATM policies.
B.9.3.10 Parameter Description: ATM Service Management This topic describes the parameters that are related to ATM service management. B.9.3.11 Parameter Description: ATM Service Management_Creation This topic describes the parameters that are related to creation of ATM services. B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes This topic describes the parameters that are related to segment end attributes of ATM OAM. B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status This topic describes the parameters that are related to the CC activation status of ATM OAM. B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status This topic describes the parameters that are related to the remote end loopback status of ATM OAM. B.9.3.15 Parameter Description: ATM OAM Management_LLID This topic describes the parameters that are related to LLID configuration.
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management

This topic describes the parameters that are related to IMA group management.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Group Management tab.

Parameter VCTRUNK Value Range Default Value Description Displays the ATM TRUNK.
B-492
Issue 03 (2011-04-10)
Parameter IMA Protocol Enable Status
Description l Specifies the IMA protocol enable status. l Set IMA Protocol Enable Status to Enabled if the links bound in 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.
Minimum Number of Active Transmitting Links
1 to 16
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 OptiX RTN 950 supports Symmetrical Mode and Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links and Minimum
Issue 03 (2011-04-10)
B-493
Parameter Minimum Number of Active Receiving Links
Value Range 1 to 16
Default Value 1
Description Number of Active Receiving Links must assume the same value on the two ends of an IMA link. l The default value is recommended.
IMA Protocol Version
1.0 1.1
1.1
l Specifies the IMA protocol version. 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.
B-494
Issue 03 (2011-04-10)
Parameter IMA Transmit Frame Length
Value Range 32 64 128 256
Default Value 128
Description l Specifies the IMA transmit frame length. l Based on the IMA frame format, the receive end rebuilds the ATM cell stream with the cells arriving from diverselydelayed 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 IMA Transmit Frame Length must assume the same value on the two ends of an IMA link. l The default value is recommended.
Issue 03 (2011-04-10)
B-495
Parameter IMA Symmetry Mode
Value Range Symmetrical Mode and Symmetrical Operation
Default Value Symmetrical Mode and Symmetrical Operation
Description l Specifies the symmetrical mode of the IMA group. l If the symmetrical mode and symmetrical operation is 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.
B-496
Issue 03 (2011-04-10)
Parameter Maximum Delay Between Links (ms)
Default Value 25
Description l Specifies the maximum differential delay that is allowed between the member links. l If the differential delay between a member link and the other member links exceeds the value, this link will be deactivated and deleted from the IMA group. l If this parameter is set to a value higher than the normal value range, the delay of IMA services will be prolonged and even packet loss will occur; if this parameter is set to a value lower than the normal value range, a working link will be deleted by mistake. l The Maximum Delay Between Links (ms) must assume the same value on the two ends of an IMA link. l The default value is recommended.
Clock Mode
CTC Mode ITC Mode
CTC Mode
l Specifies the clock mode of the IMA group. l Clock Mode is set to the same value for the interconnected ends of IMA links.
Related Tasks
B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration

This topic describes the parameters that are related to the bound paths in the ATM TRUNK.
Navigation Path
1. 2. 3. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the Binding tab. Click Configuration.

Parameter Available Boards Configurable Ports Level Value Range E1 Fractional E1 Default Value E1 Description Selects the available boards. Selects the configurable ATM trunks. Specifies the level of bound paths. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select E1 in Level. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports, select Fractional E1 in Level. Direction Displays the direction of bound paths. The fixed value is bidirectional. The OptiX RTN 950 does not support this parameter. Displays the ports that carry the available paths for IMA services.
NOTE For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and configure A.5.5 Setting Serial Port Parameters.
Optical Interface Available Resources
Available Timeslots Selected Bound Paths

B-498
The OptiX RTN 950 does not support this parameter. Displays the bound paths.
Issue 03 (2011-04-10)
Parameter VCTRUNK Level Direction
Value Range -
Default Value -
Description Displays the name of the ATM TRUNK. Displays the level of bound paths. Displays the direction of bound paths. The fixed value is bidirectional. Displays the bound paths. Displays the number of bound paths. Specifies whether to display bound paths in combination.
Bound Paths Number of Bound Paths Display in Combination
Selected Not selected
Selected
Related Tasks
A.8.7.1 Binding ATM TRUNKs
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status

This topic describes the parameters that are related to IMA group status.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Group States tab.

Parameter VCTRUNK Near-End Group Status Far-End Group Status Transmit Rate (cell/s) Receive Rate (cell/s) Value Range Default Value Description Displays the VCTRUNK. Displays the status of the near-end group. Displays the status of the far-end group. Displays the cell transmission rate. Displays the cell receiving rate.
Issue 03 (2011-04-10)
B-499
Parameter Number of Transmit Links Number of Receive Links Number of Activated Transmit Links Number of Activated Receive Links
Value Range -
Default Value -
Description Displays the number of transmit links. Displays the number of receive links. Displays the number of activated transmit links. Displays the number of activated receive links.
Related Tasks
A.8.7.4 Querying Running Status of an IMA Group
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status

This topic describes the parameters that are related to IMA link status.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Link States tab.

Parameter VCTRUNK E1 Link Differential Delay Check Status Near-End Receiving Status Near-End Transmitting Status Far-End Receiving Status Far-End Transmitting Status Value Range Default Value Description Displays the VCTRUNK. Displays E1 links. Displays the status of the deferential delay check. Displays the near-end receiving status. Displays the near-end transmitting status. Displays the far-end receiving status. Displays the far-end transmitting status.
B-500
Issue 03 (2011-04-10)
Related Tasks
A.8.7.5 Querying Link Running Status of an IMA Group
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management

This topic describes the parameters that are related to ATM interface management.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the ATM Interface Management tab.

Parameter Port Name Port Type Value Range UNI NNI Default Value UNI Description Displays the port. Displays or specifies the name of port. Specifies the type of ATM port. l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on the common ATM network or to the userside interface of the PE on the PSN network that transmits ATM PWE3 services. l NNI: the port connecting networkside devices. For example, the NNI port applies to the networkside interface on the common ATM network.
Issue 03 (2011-04-10)
B-501
Parameter ATM Cell Payload Scrambling
Description Specifies whether to enable payload scrambling of ATM cells. l The 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. l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise, packet loss will occur.
Min. VPI Max. VPI Min. VCI Max. VCI VCC-Supported VPI Count Loopback
No Loopback Outloop Inloop
No Loopback
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. Specifies the loopback status of the port.
Related Tasks
A.8.7.3 Setting ATM Port Parameters
B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table

This topic describes the parameters that are related to configuration of the ATM service class mapping table.
B-502
Issue 03 (2011-04-10)
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree.

Parameter Mapping Relation ID Mapping Relation Name UBR CBR RT-VBR NRT-VBR UBR+ Value Range BE AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF CS6 CS7 Default Value UBR: BE CBR: EF RT-VBR: AF31 NRT-VBR: AF21 UBR+: AF11 PORT-TRANS: BE Description Specifies the ID of the mapping table. Specifies the name of the mapping relationship. Displays or specifies the PHB service classes that correspond to different ATM service types. l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 950 provides different QoS policies for the queues of different service classes. 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.
Issue 03 (2011-04-10)
B-503
Parameter PORT-TRANS
Value Range
Default Value
Description
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.
Related Tasks
A.8.9.2 Modifying an ATM-Diffserv Domain
B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation

This topic describes the parameters that are related to creation of the ATM service class mapping table.
B-504
Issue 03 (2011-04-10)
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree. Click New.
2.

Parameter Mapping Relation ID Mapping Relation Name UBR CBR RT-VBR NRT-VBR UBR+ Value Range 2 to 8 BE AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF CS6 CS7 Default Value UBR: BE CBR: EF RT-VBR: AF31 NRT-VBR: AF21 UBR+: AF11 PORT-TRANS: BE Description Specifies the ID of the mapping table. Specifies the name of the mapping relationship. Specifies the PHB service classes that correspond to different ATM service types. l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 950 provides different QoS policies for the queues of different service classes. 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.
Issue 03 (2011-04-10)
B-505
Parameter PORT-TRANS
Value Range
Default Value
Description
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.
Related Tasks
A.8.9.1 Creating an ATM-DiffServ Domain
B.9.3.8 Parameter Description: ATM Policy Management

This topic describes the parameters that are related to ATM policy management.
Navigation Path
1. 2.
B-506
In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Click the ATM Policy tab.

Parameter Policy ID Policy Name Value Range Default Value 1 Description Displays the policy ID of the ATM service. Displays or specifies the policy name of the ATM service. The maximum length of the value is 64 bytes.
Issue 03 (2011-04-10)
B-507
Parameters for Configuring ATM Traffic

Parameter Service Type Value Range UBR CBR RT-VBR NRT-VBR UBR+ Default Value UBR Description Displays or specifies the type of the ATM service. l The UBR service is characterized by nonreal-time 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 rtVBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be
B-508
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description described as bursty. In addition, the rt-VBR service does not require a static amount of bandwidth. l Compared with the rtVBR service, the nrtVBR service does not require tightly constrained delay or delay variation, and is intended for non-realtime applications. l The UBR+ service is supplementary to the UBR service and is intended for 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.
Traffic Type Clp01Pcr(cell/s) Clp01Scr(cell/s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
90 to 74539 90 to 74539 90 to 74539 90 to 74539 2 to 200000 7 to 13300000 Enabled Disabled
Disabled
The Table B-89 lists the ATM service type, traffic type descriptor, and the related traffic parameters. ATM policies are configured based on these mapping relationships.
Displays or specifies the frame discarding mark in ATM policies. This parameter is effective to AAL5 traffic.
Issue 03 (2011-04-10)
B-509
Parameter UPC/NPC
Description Displays or specifies UPC/NPC. l UPC is user-side parameter control and NPC is network-side parameter control. l After UPC/NPC is enabled, the cells with a frame discarding mark will be discarded in network congestion.
Table B-89 Mapping relationship between ATM service types, traffic types, and traffic parameters ATM Service Type UBR ATM Traffic Type Descriptor NoTrafficDescriptor NoClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt CBR ClpTransparentNoScr ClpNoTaggingNoScr ClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt nrtVBR NoClpScr ClpNoTaggingScr ClpTaggingScr rtVBR ClpTransparentScr NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt UBR+ atmnotrafficdescriptormcr atmnoclpmcr Traffic Parameter 1 Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Mcr Clp01Pcr Traffic Parameter 2 CDVT CDVT CDVT Clp0Pcr Clp0Pcr CDVT Clp01Scr Clp0Scr Clp0Scr Clp01Scr Clp01Scr Clp0Scr Clp0Scr Clp01Mcr Traffic Parameter 3 MBS MBS MBS MBS MBS MBS MBS Traffic Parameter 4 CDVT CDVT CDVT CDVT -
B-510
Issue 03 (2011-04-10)
ATM Service Type
ATM Traffic Type Descriptor atmnoclpmcrcdvt
Traffic Parameter 1 Clp01Pcr
Traffic Parameter 2 Clp01Mcr
Traffic Parameter 3 CDVT
Traffic Parameter 4 -
Parameters for the application object

Parameter Service ID Value Range Default Value Description Displays the ID configured for the ATM service. Displays the name configured for the ATM service. Displays the link ID. Displays the direction of the service.
Service Name
Link ID Direction
Related Tasks
A.8.9.4 Modifying an ATM Policy
B.9.3.9 Parameter Description: ATM Policy Management_Creation

This topic describes the parameters that are related to creation of ATM policies.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Click New.

Parameter Policy ID Value Range Default Value 1 Description Specifies the policy ID of the ATM service. The policy ID can also be automatically allocated.
Issue 03 (2011-04-10)
B-511
Parameter Policy Name
Value Range Synchronous signal Signaling Voice Data Video
Default Value Synchronous signal
Description Specifies the policy name of the ATM service. The maximum length of the value is 64 bytes.
NOTE You can select one of the five ATM service policy names from the drop-down list or enter the policy name.
B-512
Issue 03 (2011-04-10)
Parameter Service Type
Value Range UBR CBR RT-VBR NRT-VBR UBR+
Default Value UBR
Description Specifies the type of the ATM service. l The UBR service is characterized by nonreal-time 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 rtVBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be described as bursty. In
Issue 03 (2011-04-10)
B-513
Parameter
Value Range
Default Value
Description addition, the rt-VBR service does not require a static amount of bandwidth. l Compared with the rtVBR service, the nrtVBR service does not require tightly constrained delay or delay variation, and is intended for non-realtime applications. l The UBR+ service is supplementary to the UBR service and is intended for 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.
Traffic Type Clp01Pcr(cell/s) Clp01Scr(cell/s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
90 to 74539 90 to 74539 90 to 74539 90 to 74539 2 to 200000 7 to 13300000 Enabled Disabled
Disabled
For the mapping relationships between ATM service types, ATM traffic type descriptors, and traffic parameters, see Table B-90. ATM policies are configured based on these mapping relationships.
Specifies the frame discarding mark in ATM policies. This parameter is effective to AAL5 traffic.
B-514
Issue 03 (2011-04-10)
Parameter UPC/NPC
Description l UPC is user-side parameter control and NPC is network-side parameter control. l After UPC/NPC is enabled, the cells with a frame discarding mark will be discarded in network congestion.
Table B-90 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters ATM Service Type UBR ATM Traffic Type Descriptor NoTrafficDescriptor NoClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt CBR ClpTransparentNoScr ClpNoTaggingNoScr ClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt nrtVBR NoClpScr ClpNoTaggingScr ClpTaggingScr rtVBR ClpTransparentScr NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt UBR+ atmnotrafficdescriptormcr atmnoclpmcr atmnoclpmcrcdvt Traffic Parameter 1 Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Mcr Clp01Pcr Clp01Pcr Traffic Parameter 2 CDVT CDVT CDVT Clp0Pcr Clp0Pcr CDVT Clp01Scr Clp0Scr Clp0Scr Clp01Scr Clp01Scr Clp0Scr Clp0Scr Clp01Mcr Clp01Mcr Traffic Parameter 3 MBS MBS MBS MBS MBS MBS MBS CDVT Traffic Parameter 4 CDVT CDVT CDVT CDVT -
Issue 03 (2011-04-10)
B-515
Related Tasks
A.8.9.3 Creating an ATM Policy

This topic describes the parameters that are related to ATM service management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree.

Parameter Service ID Service Name Service Type Deployment Status Value Range Default Value Description Displays the service ID. Displays or specifies the service name. Displays the ATM service type. Displays the deployment status of the ATM service.
Connection Parameters
Parameter Connection ID Connection Name Value Range Default Value Description Displays the connection ID of the ATM service. Displays or specifies the connection name of the ATM service. Displays the source port of the ATM service. Displays the ID of the PW that carries ATM PWE3 services, if any. Displays the sink board of the ATM service. Displays the VPI of the source port of the ATM service.
Source Port PW ID
Sink Port Source VPI
B-516
Issue 03 (2011-04-10)
Parameter Source VCI
Value Range -
Default Value -
Description Displays the VCI of the source port of the ATM service. Displays the VPI of the sink port of the ATM service. Displays the VCI of the sink port of the ATM service. Displays the QoS policy of the uplink ATM connection. Displays the QoS policy of the downlink ATM connection.
Sink VPI
Sink VCI
Uplink Policy
Down link Policy

Parameter Port Port Name Max. VPI Max. VCI VCC-Supported VPI Count Value Range Default Value Description Displays the port of the ATM IMA service. Displays the port name of the ATM IMA service. Displays the maximum VPI. Displays the maximum VCI. Displays the count of VPIs that are used for VC exchange.
Parameters for Bound Paths

Parameter VCTRUNK Level Value Range Default Value Description Displays the VCTRUNK. Displays the level of bound paths.
Issue 03 (2011-04-10)
B-517
Parameter Direction
Value Range -
Default Value -
Description Displays the direction of bound paths. The fixed value is bidirectional. Displays the bound paths. Displays the number of bound paths. Displays the status of the IMA group.
Bound Paths Number of Bound Paths IMA Group Status
Parameters of PWs
Tab General Attributes Parameter PW ID Work Status PW Status PW Signaling Type Value Range Default Value Description Displays the PW ID. Displays the working status of a PW. Displays whether a PW is enabled. Displays the PW signaling type.
NOTE The OptiX RTN 950 uses static PWs only.
PW Type
l Displays the configured PW type. l This parameter corresponds to the connection type. The encapsulation type can be 1:1 or N: 1 if the connection type is PVP or PVC.
Displays the direction of the PW. Displays the encapsulation type of the packets on the PW.
NOTE The OptiX RTN 950 uses MPLS only.
PW Incoming Label / Source Port

B-518
Displays the configured PW Ingress label.

Issue 03 (2011-04-10)
Tab
Parameter PW Outgoing Label / Sink Port Peer LSR ID Tunnel Type Ingress Tunnel No Egress Tunnel No Local Operating Status Remote Operating Status Overall Operating Status
Value Range -
Default Value -
Description Displays the configured PW Egress label. Displays the LSR ID of the destination. Displays the type of the tunnel. Displays the tunnel ID of the ingress tunnel. Displays the tunnel ID of the egress tunnel. Displays the local running status of PW. Displays the remote running status of PW. Displays the comprehensive working status of the PW. Displays the tunnel that is automatically selected. Displays the PW ID. Displays the direction of the PW.
Tunnel for Auto Selection QoS PW ID Direction
Issue 03 (2011-04-10)
B-519
Tab
Value Range -
Default Value -
Description Displays or specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel.
CIR (Kbit/s)
Displays or specifies the committed information rate. It is recommended that you set this parameter to the same value as PIR.
CBS (kbyte)
Displays or specifies the excess burst size of the PW. Displays or specifies the peak information rate. It is recommended that you set this parameter to the same value as CIR.
PIR (kbit/s)
PBS (kbyte)
Displays or specifies the maximum excess burst size of the PW. The OptiX RTN 950 does not support this parameter.
EXP
B-520
Issue 03 (2011-04-10)
Tab
Parameter Policy
Value Range -
Default Value -
Description The OptiX RTN 950 does not support this parameter. Displays or specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Displays or specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode.
Advanced Attributes
Control Word
Must Use No Use
CW None Alert Label
Ping None
l Displays or specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-ping function is required, do not set VCCV Verification Mode of PWs to None.
Issue 03 (2011-04-10)
B-521
Tab
Parameter Max. Concatenated Cell Count
Value Range 1 to 31
Default Value -
Description l Displays or specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
100 to 50000
l Displays or specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.
Parameters for CoS Mapping

Parameter PW ID Value Range Default Value Description Displays the ID of the PW that carries the service.
B-522
Issue 03 (2011-04-10)
Parameter CoS Mapping
Value Range -
Default Value -
Description Specifies the policy for mapping different ATM service levels to CoS priorities. By setting this parameter, different quality measures are provided for different ATM services.

NOTE
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the protection mode. l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Working PW ID Protection PW ID Protection Mode Enabling Status
Enabled Disabled
Switchover Mode

Issue 03 (2011-04-10)
B-523
Parameter Restoration Mode
Value Range Non-revertive Revertive
Default Value -
Description l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
WTR Time(min)
1 to 12
l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
0 to 100
B-524
Issue 03 (2011-04-10)
Parameter Switchover Status
Value Range -
Default Value -
Description Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.
Related Tasks
A.8.8.2 Modifying ATM Service Parameters A.8.8.3 Querying ATM Services
B.9.3.11 Parameter Description: ATM Service Management_Creation

This topic describes the parameters that are related to creation of ATM services.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click New.

Parameter Service ID Value Range 1 to 4294967295 Default Value Description Specifies the service ID. If Automatically Assign is selected, the system automatically allocates service IDs. Service Name Specifies the service name.
Issue 03 (2011-04-10)
B-525
Parameter Direction
Value Range UNIs-NNI UNI-UNI
Default Value UNIs-NNI
Description l 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.
Connection Type
PVC PVP Transparent
PVC
Specifies the connection type of the ATM service. For common ATM services (UNI-UNI): 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 (UNIs-NNI): l PVP: This value applies to the N-to-1/1to-1 VPC encapsulation mode. l PVC: This value applies to the N-to-1/1to-1 VCC encapsulation mode. For transparently transmitted ATM services, set Connection Type to Transparent.
B-526
Issue 03 (2011-04-10)
Description l Specifies the protection mode of the PW. This parameter is available only when Service Type is UNIsNNI. l Set this parameter according to the planning information.
Automatically Assign
Selected Not selected
Not selected
Specifies whether to automatically allocate service IDs.
Connection Parameters
Parameter Connection Name Source Port Source Bind Path Value Range Default Value Description Specifies the name of the ATM connection. Specifies the source port of the ATM service. Specifies the path bound with the source port of the ATM service. Specifies the VPI of the source port of the ATM service. Specifies the VCI of the source port of the ATM service. Specifies the ID of the PW that carries services. Specifies the sink board of the ATM service.
NOTE This parameter does not need to be set if Service Type is UNIs-NNI. This parameter needs to be set if Service Type is UNI-UNI and the value must be different from that of the source board.
Source VPI(eg.35,36-39)
UNI: 0 to 255 NNI: 0 to 4095
Source VCI(eg.35,36-39)
32 to 65535
PW ID Sink Port
1 to 4294967295 -
Issue 03 (2011-04-10)
B-527
Parameter Sink Bind Path
Value Range -
Default Value -
Description Specifies the path bound with the sink port of the ATM service.
NOTE When Direction is UNIsNNI, the sink port does not need to be set. If Direction is UNI-UNI, the sink port needs to be set and be different from the source port.
Sink VPI(eg.35,36-39)
UNI: 0 to 255 NNI: 0 to 4095
Specifies the VPI of the sink port of the ATM service. Specifies the VCI of the sink port of the ATM service. Specifies the QoS policy of the uplink ATM connection. Specifies the QoS policy of the downlink ATM connection.
Sink VCI(eg.35,36-39)
32 to 65535
Uplink Policy
Down link Policy
Parameters of PWs
NOTE
If the parameter Protection Type of PWs is set to PW APS, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Parameter PW ID
Value Range -
Default Value -
Description Specifies the ID of the PW that carries services. Automatic ID assignment is recommended. Displays the working status of the PW.
NOTE This parameter is available only after the PW parameters are configured.
Working Status
B-528
Issue 03 (2011-04-10)
Parameter Enable Status
Value Range -
Default Value -
Description Displays the enabling status of the PW.

NOTE This parameter is available only after the PW parameters are configured.
PW Signaling Type PW Type
Static The ATM connection type is PVC: l ATM n-to-one VCC cell transport l ATM one-to-one VCC Cell Mode The ATM connection type is PVP: l ATM n-to-one VPC cell transport l ATM one-to-one VPC Cell Mode
Static The ATM connection type is PVC: ATM n-to-one VCC cell transport The ATM connection type is PVP: ATM n-to-one VPC cell transport
Labels for static PWs need to be manually assigned. l Specifies the type of the PW. l In the case of ATM 1_to_1 encapsulation, one PW carries one VPC or VCC. l In the case of ATM n_to_1 encapsulation, one PW carries one or more VPCs or VCCs.
Bidirectional MPLS
Bidirectional MPLS
Displays the direction of the PW. Displays the encapsulation type of the packets on the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW. A tunnel needs to be created or selected. If no tunnel is available, creation of a PW will fail. For bidirectional tunnels. the system automatically configures the reverse tunnel, requesting no manual operation.
PW Ingress Label / Source Port PW Egress Label / Sink Port Tunnel Selection Mode Tunnel Type Ingress Tunnel
16 to 1048575 16 to 1048575 Manually MPLS New Use existing resource
Manually MPLS New
Egress Tunnel
New
Issue 03 (2011-04-10)
B-529
Parameter Peer LSR ID
Value Range -
Default Value -
Description Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned.
QoS Parameters
Table B-91 ATM services Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. Policy CIR (Kbit/s) The OptiX RTN 950 does not support this parameter. Specifies the committed information rate (CIR) of the PW. It is recommended that you set this parameter to the same value as PIR. CBS (kbyte) Specifies the excess burst size of the PW.
B-530
Issue 03 (2011-04-10)
Parameter PIR (kbit/s)
Value Range -
Default Value -
Description Specifies the peak information rate (PIR) of the PW. It is recommended that you set this parameter to the same value as CIR.
PBS (kbyte)
Specifies the maximum excess burst size of the PW. The OptiX RTN 950 does not support this parameter.
EXP
Parameters of Advanced Attributes

Parameter Control Word Value Range Must Use No Use Default Value Must Use Description l Specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Set Control Word to Must Use if PW Type is ATM 1:1. Control Channel Type CW None Alert Label CW l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode.
Issue 03 (2011-04-10)
B-531
Parameter VCCV Verification Mode
Value Range Ping None
Default Value Ping
Description l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, do not set this parameter to None.
Max. Concatenated Cell Count
1 to 31
10
l Specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
100 to 50000
1000
l Specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.

NOTE
B-532
Issue 03 (2011-04-10)
Parameter Protection Type Protection Group ID Enabling Status
Description Specifies the protection type. Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Protection Mode
Displays the protection mode.

Switching Mode

Revertive
Revertive
Issue 03 (2011-04-10)
B-533
Value Range 1 to 12
Default Value 1
0 to 100
OAM Parameters
NOTE
Value Range -
Default Value -

Issue 03 (2011-04-10)
B-534
Issue 03 (2011-04-10)
B-535
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
B-536
Issue 03 (2011-04-10)

NOTE
Value Range -
Default Value -
Parameters for CoS Mapping

Parameter PW ID CoS Mapping Value Range Default Value Description Displays the ID of the PW that carries service. Specifies the policy for mapping different ATM service levels to CoS priorities. By setting this parameter, different quality measures are provided for different ATM services.
Related Tasks
A.8.8.1 Creating ATM Services
B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes

This topic describes the parameters that are related to segment end attributes of ATM OAM.
Navigation Path
1. 2.
Issue 03 (2011-04-10)
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the Segment End Attributes tab.

Parameter Source Sink Connection Direction Value Range Source Sink Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service. Displays the direction of the ATM connection. l Source: indicates the forward direction. For common ATM services (UNIUNI), Source indicates the direction from the source end to the sink end of the ATM connection. For ATM PWE3 services (UNINNI), Source indicates the direction from the UNI port side to the MPLS interface side. l Sink: indicates the backward direction. For common ATM services (UNIUNI), Sink indicates the direction from the sink end to the source end of the ATM connection. For ATM PWE3 services (UNINNI), Sink indicates the direction from the MPLS interface side to the UNI port side.
B-538
Issue 03 (2011-04-10)
Parameter Segment and End Attribute
Value Range Non segment and Endpoint Segment point Endpoint Segment and Endpoint
Default Value Non segment and Endpoint
Description Specifies the segment and end attributes of the source and sink of the ATM connection. l Non segment and endpoint: intermediate point, which refers to the OAM node between two segment points or two end points. Therefore, intermediate points can be further classified into intermediate points between segment points, and intermediate points between end points. Upon detecting a fault, an intermediate point reports the corresponding alarms and inserts segment AIS cells and end AIS cells to the downstream. Afterwards, the intermediate point periodically sends these cells. An intermediate point does not catch any AIS/RDI cells. l Segment point: an end point of a segment. One ATM link consists of multiple segments. Upon detecting a fault, a segment point reports the corresponding alarms and inserts end AIS cells to the downstream. Afterwards, the segment point
Issue 03 (2011-04-10)
B-539
Parameter
Value Range
Default Value
Description periodically sends these cells. A segment point catches segment AIS/RDI cells only. l End point: an end point of an ATM link. It is usually an edge point on the ATM network. Upon detecting a fault, an end point reports the corresponding alarms but does not insert any AIS cells. An end point catches end AIS/ RDI cells only. l Segment and endpoint: a segment-end point, or an edge point of a segment and an end. Upon detecting a fault, a segmentend point reports the corresponding alarms but does not insert any AIS cells. A segment-end point catches the AIS/RDI cells of a segment and an end.
Related Tasks
A.8.10.1 Setting Segment and End Attributes of AIS/RDI
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status

This topic describes the parameters that are related to the CC activation status of ATM OAM.
B-540
Issue 03 (2011-04-10)
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the CC Activation Status tab.

Parameter Source Sink Value Range Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service.
Issue 03 (2011-04-10)
B-541
Parameter Connection Direction
Value Range Source Sink
Default Value -
Description Specifies the connection direction. l Source: indicates the forward direction. For common ATM services (UNIUNI), Source indicates the direction from the source end to the sink end of the ATM connection. For ATM PWE3 services (UNINNI), Source indicates the direction from the UNI port side to the MPLS interface side. l Sink: indicates the backward direction. For common ATM services (UNIUNI), Sink indicates the direction from the sink end to the source end of the ATM connection. For ATM PWE3 services (UNINNI), Sink indicates the direction from the MPLS interface side to the UNI port side.
B-542
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description Specifies the segment and end attributes of nodes. l Segment point: an end point of a segment. One ATM link consists of multiple segments. Segment CC cells are terminated at segment points. l End point: an end point of an ATM link. It is usually an edge point on an ATM network. End-to-end CC cells are terminated at end points.
Issue 03 (2011-04-10)
B-543
Parameter CC Activate Flag
Value Range Deactivate Source activate Sink activate Source + sink activate
Default Value -
Description l Specifies the CC activation flag. l Deactivate: This node does not transmit or receive CC cells. l Source activate: This point transmits but does not receive CC cells. l Sink activate: This point receives but does not transmit CC cells. If this point does not receive any service cells or CC cells within a time interval of 3.5 (0.5) seconds, it will report the LOC alarm and transmit AIS cells in the forward direction. l Source + sink activate: This node transmits and receives CC cells. If this point does not receive any service cells or CC cells within a time interval of 3.5 (0.5) seconds, it will report the LOC alarm and transmit AIS cells in the forward direction. l Once the node receives any CC cells or service cells, the LOC alarm will be cleared.
Related Tasks
A.8.10.2 Performing a Continuity Check Test
B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status

This topic describes the parameters that are related to the remote end loopback status of ATM OAM.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab.

Parameter Source Sink Value Range Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service.
Issue 03 (2011-04-10)
B-545
Parameter Connection Direction
Value Range Source Sink
Default Value -
Description Displays the direction of the ATM connection. l Source: indicates the forward direction. For common ATM services (UNIUNI), Source indicates the direction from the source end to the sink end of the ATM connection. For ATM PWE3 services (UNINNI), Source indicates the direction from the UNI port side to the MPLS interface side. l Sink: indicates the backward direction. For common ATM services (UNIUNI), Sink indicates the direction from the sink end to the source end of the ATM connection. For ATM PWE3 services (UNINNI), Sink indicates the direction from the MPLS interface side to the UNI port side.
B-546
Issue 03 (2011-04-10)
Value Range -
Default Value -
Description Specifies the segment and end attribute. l Segment LB cells are looped back only at a Segment point, Segment and Endpoint, or Non segment and Endpoint. l End-to-end LB cells are looped back only at an Endpoint or Segment and Endpoint.
Loopback Point NE
l Specifies the NE where the loopback point is located. l Before an end-to-end LB test, you need to set end points in the test domain. After the test, remove the end points. l Before a segment-tosegment LB test, you need to set segment points in the test domain. After the test, remove the segment points.
Test Result
Displays whether the loopback command is successfully issued.
Related Tasks
B.9.3.15 Parameter Description: ATM OAM Management_LLID

This topic describes the parameters that are related to LLID configuration.
Navigation Path
1. 2.
Issue 03 (2011-04-10)
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the LLID tab.

Parameter Country Code (Hexadecimal Code) Value Range Default Value 00 00 Description Displays or specifies the country code of the ATM service. The value is 2 bytes in length. Displays or specifies the network code of the ATM service. The value is 2 bytes in length. l Displays or specifies the NE code of the ATM service. The value is 11 bytes in length. l The default NE code can be used if it is unique on the network. l NE code and NE ID are associated. Therefore, each NE on the network has a unique NE code.
Network Code (Hexadecimal Code)
00 01
NE Code (Hexadecimal Code)
00 30 00 04 00 00 00 00 00 00 00
Related Tasks
A.8.10.3 Querying or Setting LLIDs
B.10 Clock Parameters

This topic describes the parameters that are related to clocks. B.10.1 Physical Clock Parameters This topic describes physical clock parameters. B.10.2 CES ACR Clock Parameters This topic describes CES ACR clock parameters. B.10.3 Parameter Description: Auxiliary Ports This topic describes parameters that are used for configuring an external time port as an RS-485 monitoring port.
B.10.1 Physical Clock Parameters

This topic describes physical clock parameters. B.10.1.1 Parameter Description: Clock Source Priority Table This topic describes the parameters that are related to the priority table of a clock source.
B.10.1.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port This topic describes the parameters that are related to the priority table for the phase-locked loop (PLL) clock source of the external clock port. B.10.1.3 Parameter Description: Clock Subnet Setting_Clock Subnet This topic describes the parameters that are related to a clock subnet. B.10.1.4 Parameter Description: Clock Subnet Setting_Clock Quality This topic describes the parameters that are related clock quality. B.10.1.5 Parameter Description: Clock Subset Setting_SSM Output Control This topic describes the parameters that are related to SSM output control. B.10.1.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status This topic describes the parameters that are used for enabling the clock ID function. B.10.1.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters This topic describes the parameters that are related to clock source restoration. B.10.1.8 Parameter Description: Clock Source Switching_Clock Source Switching This topic describes the parameters that are related to the switching status of a clock source. B.10.1.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions This section describes the parameters that are related to the switching conditions of clock sources. B.10.1.10 Parameter Description: Output Phase-Locked Source of the External Clock Source This topic describes the parameters of the output phase-locked source of the external clock source. B.10.1.11 Parameter Description: Clock Synchronization Status This topic describes the parameters that are related to the clock synchronization status.
B.10.1.1 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock source.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Priority. Click the System Clock Source Priority List tab.
Issue 03 (2011-04-10)
B-549
Parameters
Parameter Clock Source Value Range Default Value Description l External clock source 1 indicates the external clock source at the CLK or TIME1 port on the CST or CSH board in physical slot 7. External clock source 2 indicates the external clock source at the CLK or TIME1 port on the CST or CSH board in physical slot 8. l The internal clock source is always at the lowest priority and indicates that the NE works in the free-run mode. l The clock sources and the corresponding clock source priority levels are determined according to the clock synchronization schemes. External Clock Source Mode 2Mbit/s 2MHz 2Mbit/s l This parameter indicates the type of the external clock source signal. l This parameter is set according to the external clock signal. In normal cases, the external clock signal is a 2 Mbit/s signal.
B-550
Issue 03 (2011-04-10)
Parameter Synchronous Status Byte
Value Range SA4 to SA8
Default Value SA4
Description l This parameter is valid only when External Clock Source Mode is set to 2Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. l This parameter needs to be set only when the SSM or extended SSM is enabled. In normal cases, the external clock sources use the SA4 to transmit the SSM.
Clock Source Priority Sequence (Highest:1)
Displays the priority sequence of clock sources. 1 indicates the highest clock source priority.
Related Tasks
A.9.1.1 Configuring the Clock Sources
B.10.1.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port
This topic describes the parameters that are related to the priority table for the phase-locked loop (PLL) clock source of the external clock port.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Physical Clock > Clock Source Priority from the Function Tree. Click the Priority for PLL Clock Sources of 1st External Output tab.
Issue 03 (2011-04-10)
B-551
Parameters for configuring the priority table for the PLL clock source of the external clock port
Parameter Clock Source Value Range Default Value Internal Clock Source Description l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock of the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual configuration is required. l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board, clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock Source to the corresponding clock source according to the network planning information. Current Status Displays the valid status of clock sources.
B-552
Issue 03 (2011-04-10)
Parameter Lock Status
Value Range -
Default Value -
Description l The PLL clock source of the external clock port extracts only an unlocked clock source. l If a clock source is in locked state, the PLL clock source of the external clock port does not extract the clock source until the clock source is changed from the locked state to the unlocked state. l The internal clock source should not be in locked state.
Clock Source Priority (Highest: 1)
Displays the priority level of a clock source. 1 is the highest priority.
B.10.1.3 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the Clock Subnet tab.
Parameters for Setting a Clock Subnet

Parameter Affiliated Subnet Value Range Default Value Description The OptiX RTN 950 does not support this parameter.
Issue 03 (2011-04-10)
B-553
Parameter Protection Status
Value Range Start Extended SSM Protocol Start Standard SSM Protocol Stop SSM Protocol
Default Value Stop SSM Protocol
Description l The SSM protocol is a scheme used for synchronous management on an SDH network and indicates that the SSM is passed by the lower four bits of the S1 byte and can be exchanged between the nodes. The SSM protocol ensures that the equipment automatically selects the clock source of the highest quality and highest priority, thus preventing mutual clock tracing. l After the standard SSM protocol is started, the NE first performs the protection switching on the clock source according to the clock quality level information provided by the S1 byte. If the quality level of the clock source is the same, the NE then performs the protection switching according to the clock priority table. That is, the NE selects an unlocked clock source that is of the highest quality and highest priority from all the current available clock sources as the clock source to be synchronized and traced by the local station. l If the SSM protocol is stopped, it indicates
B-554
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description that the S1 byte is not used. The NE selects and switches a clock source only according to the sequence specified in the priority table. The clock source of the highest priority is used as the clock source to be traced. l After the SSM protocol is stopped, each NE performs the protection switching on the clock according to the preset priority table of the clock source only when the clock source of a higher priority is lost.
Clock Source
This parameter indicates the clock source that is configured for an NE. In Clock Source Priority, you can set whether to add or delete a clock source.
Issue 03 (2011-04-10)
B-555
Parameter Clock Source ID
Value Range (None) 1 to 15
Default Value (None)
Description l This parameter is valid only when the extended SSM protocol is started. l Clock source IDs are allocated for the following clock sources only: External clock source Internal clock source of the node that accesses the external clock sources Internal clock source of the joint node of a ring and a chain or the joint node of two rings Line clock source that enters the ring when the intra-ring line clock source is configured at the joint node of a ring and a chain or the joint node of two rings
Related Tasks
A.9.1.2 Configuring Clock Subnets
B.10.1.4 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the Received Quality tab.
B-556
Issue 03 (2011-04-10)
Parameters for Clock Source Quality

Parameter Clock Source Value Range Default Value Description This parameter indicates the name of the configured clock source. In Clock Source Priority, you can set whether to add or delete a clock source. This parameter specifies the quality level that is configured for the clock source. This function is required only in a special scenario or in a test. Generally, this parameter need not be set.
Configured Quality
Unknown Synchronization Quality G.811 Clock Signal G.812 Transit Clock Signal G.812 Local Clock Signal G.813 SDH Equipment Timing Source (SETS) Signal Do Not Use For Synchronization Automatic Extraction
Automatic Extraction
Received Quality
This parameter indicates the clock source quality signal received by the NE. The NE extracts the clock source quality signal from the S1 byte of each clock source.
Parameters for Manual Setting of 0 Quality Level

Parameter NE Name Value Range Default Value Description This parameter indicates the name of the NE.
Issue 03 (2011-04-10)
B-557
Parameter Quality Level 0
Value Range Do Not Use For Synchronization G.811 Reference Clock Between G.811 Reference Clock and G.812 Transit Clock G.812 Transit Clock Between G.812 Transit Clock and G.812 Local Clock G.812 Local Clock Between G.812 Local Clock and synchronous equipment timing source (SETS) SETS Clock Between synchronous equipment timing source (SETS) and quality unavailable
Default Value Do Not Use For Synchronization
Description This parameter specifies the clock quality whose level is manually set to zero. l Do Not Use For Synchronization: the notification information in the reverse direction of the selected synchronization clock source to avoid direct mutual locking of adjacent NEs. l G.811 Reference Clock: the clock signal specified in ITU-T G. 811. l Between G.811 Reference Clock and G.812 Transit Clock: lower than the quality level of the clock signal specified in ITU-T G.811 but higher than the quality level of the transit exchange clock signal specified in ITU-T G. 812. l G.812 Transit Clock: the transit exchange clock signal specified in ITU-T G.812. l Between G.812 Transit Clock and G. 812 Local Clock: lower than the quality level of the transit exchange clock signal specified in ITU-T G. 812 but higher than the quality level of the local exchange clock signal specified in ITU-T G.812. l G.812 Local Clock: the local exchange
B-558
Issue 03 (2011-04-10)
Parameter
Value Range
Default Value
Description clock signal specified in ITU-T G.812. l Between G.812 Local Clock and synchronous equipment timing source (SETS): lower than the quality level of the local exchange clock signal specified in ITU-T G.812 but higher than the quality level of the clock signal of the SETS. l SETS Clock: the clock signal of the SETS. l Between synchronous equipment timing source (SETS) and quality unavailable: lower than the quality level of the clock signal of the SETS but higher than the quality level unavailable in the synchronous timing source.
Related Tasks
A.9.1.3 Self-Defined Clock Quality
B.10.1.5 Parameter Description: Clock Subset Setting_SSM Output Control

This topic describes the parameters that are related to SSM output control.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the SSM Output tab.
Issue 03 (2011-04-10)
B-559
Parameters
Parameter Line Port Value Range Default Value Description l This parameter indicates the name of the line clock port. l Line Port: indicates the SSM quality information output port of the current available line clock source and the external clock source. This output port can transmit the quality information of the clock source by outputting the S1 byte to the downstream NE. Output S1 Byte Info Enabled Disabled Enabled l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started. l Output S1 Byte Info indicates whether the SSM is output at the line port. l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled. Otherwise, set this parameter to Disabled.
Related Tasks
A.9.1.4 Configuring the SSM Output Status
B.10.1.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

This topic describes the parameters that are used for enabling the clock ID function.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration.
B-560
2.
Click the Clock ID Output tab.
Parameters
Parameter Line Port Value Range Default Value Description l This parameter indicates the name of the line clock port. l Line Port: indicates the SSM quality information output port of the current available line clock source and the external clock source. This output port can transmit the quality information of the clock source by outputting the S1 byte to the downstream NE. Output Clock ID Enabled Disabled Enabled l Output Clock ID is valid only when the extended SSM protocol is started. l Output Clock ID indicates whether the clock source ID is output at the line port. l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to Disabled.
Related Tasks
A.9.1.5 Configuring the Clock ID Output Status
Issue 03 (2011-04-10)
B-561
B.10.1.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

This topic describes the parameters that are related to clock source restoration.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Switching. Click the Clock Source Reversion tab.
Parameters
Parameter NE Name Value Range Default Value Description This parameter indicates the name of the NE.
B-562
Issue 03 (2011-04-10)
Parameter Higher Priority Clock Source Reversion
Value Range Auto-Revertive Non-Revertive
Default Value Auto-Revertive
Description l When the quality of a higher-priority clock source degrades, the NE automatically switches the clock source to a lowerpriority clock source. If this parameter is set to Auto-Revertive, the NE automatically switches the clock source to the higherpriority clock source when this higherpriority clock source restores. If this parameter is set to Non-Revertive, the NE does not automatically switch the clock source to the higher-priority clock source when this higher-priority clock source restores. l Correct setting of Clock Source Switching Condition ensures the reliability of the clock source switching. To improve the clock quality, select AutoRevertive. Otherwise, to prevent jitter of the clock, generally, it is recommended that you set this parameter to Non-Revertive.
Issue 03 (2011-04-10)
B-563
Parameter Clock Source WTR Time(min.)
Value Range 0 to 12
Default Value 5
Description l This parameter specifies the duration from the time when the clock source restoration is detected to the time when the clock source switching is triggered. This parameter is used to avoid frequent switching of the clock source due to instability of the clock source state within a short time. l This parameter is valid only when Higher Priority Clock Source Reversion is set to AutoRevertive.
Related Tasks
A.9.1.9 Modifying the Recovery Parameter of the Clock Source
B.10.1.8 Parameter Description: Clock Source Switching_Clock Source Switching

This topic describes the parameters that are related to the switching status of a clock source.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Click the Clock Source Switching tab.
Parameters
Parameter Clock Source Value Range Default Value Description This parameter indicates the name of the clock source. This parameter indicates whether the clock source is valid.
Current Status
Valid Invalid
B-564
Issue 03 (2011-04-10)
Parameter Lock Status
Value Range Lock Unlock
Default Value -
Description l This parameter specifies the locking status of the clock source in the priority table. l Lock: A clock source in the priority table is in the locked state. The clock source in the locked state cannot be switched. l Unlock: A clock source in the priority table is in the unlocked state. The clock source in the unlocked state can be switched.
Switching Source
This parameter indicates the clock source to be traced by the NE after the switching. This parameter indicates the switching status of the current clock source.
Switching Status
Normal Manual Switching Forced Switching
B.10.1.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions

This section describes the parameters that are related to the switching conditions of clock sources.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching Conditions tab.
Parameters
Parameter NE Name Clock Source Value Range Default Value Description Displays the name of the NE. Displays the clock source.
Issue 03 (2011-04-10)
B-565
Parameter AIS Alarm
Value Range Yes No
Default Value No
Description l The default value is recommended. l When this parameter is set to Yes, it indicates that clock source switching occurs if the clock source reports the AIS alarm. l When this parameter is set to No, it indicates that no clock source switching occurs if the clock source reports the AIS alarm.
B1 BER ThresholdCrossing RLOS,RLOF and OOF/ RLOC Alarms
Yes
Yes
The parameter is invalid. This parameter indicates that clock switching occurs when the clock source reports the RLOS, RLOF, OOF, or LOC alarm. The parameter is invalid. The parameter is invalid. l The default value is recommended. l When this parameter is set to Yes, it indicates that clock source switching occurs if the clock source reports the B2-EXC alarm. l When this parameter is set to No, it indicates that no clock source switching occurs if the clock source reports the B2-EXC alarm.
CV Threshold-Crossing CV Threshold B2-EXC Alarm
Yes No
No
Related Tasks
A.9.1.8 Changing the Conditions for Clock Source Switching
B-566
Issue 03 (2011-04-10)
B.10.1.10 Parameter Description: Output Phase-Locked Source of the External Clock Source
This topic describes the parameters of the output phase-locked source of the external clock source.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Phase-Locked Source Output by External Clock.
Parameters
Parameter 2M Phase-Locked Source Number Value Range External Clock Source 1 External Clock Source 2 Default Value Description This parameter indicates the number of the external clock source output of the NE. l This parameter specifies the mode of the output clock. l This parameter needs to be set according to the requirements of the interconnected equipment. Generally, the output external clock signal is a 2 Mbit/s signal. External Clock Output Timeslot SA4 to SA8 ALL ALL l This parameter is valid only when External Clock Output Mode is set to 2Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the output clock signal is used to transmit the SSM. l If this parameter is set to ALL, it indicates that all the bits of the TS0 are used to transmit the SSM. l It is recommended that you use the default value.
External Clock Output Mode
2Mbit/s 2MHz
2Mbit/s
Issue 03 (2011-04-10)
B-567
Parameter External Source Output Threshold
Value Range Threshold Disabled Not Inferior to G.813 SETS Signal Not Inferior to G.812 Local Signal Not Inferior to G.812 Transit Clock Signal Not Inferior to G.811 Clock Signal
Default Value Threshold Disabled
Description l This parameter specifies the lowest quality of the output clock. If the clock quality is lower than the value of this parameter, it indicates that the external clock source does not output any clock signal. l If this parameter is set to Threshold Disabled, it indicates that the external clock source always outputs the clock signal. l It is recommended that you use the default value.
2M Phase-Locked Source Failure Condition
No Failure Condition AIS LOF AIS OR LOF
No Failure Condition
l This parameter specifies the failure condition of the 2 Mbit/s phase-locked clock source. l It is recommended that you use the default value.
2M Phase-Locked Source Failure Action
Shut Down Output 2M Output S1 Byte Unavailable Send AIS
Shut Down Output
l This parameter is valid only when 2M PhaseLocked Source Failure Condition is not set to No Failure Condition. l This parameter specifies the operation of the 2 Mbit/s phaselocked loop (PLL) when the 2 Mbit/s phase-locked clock source meets the failure conditions. l It is recommended that you use the default value.
B-568
Issue 03 (2011-04-10)
Related Tasks
B.10.1.11 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization status.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Synchronization Status.
Parameters
Parameter NE Name NE Clock Mode Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the working mode of the NE clock. This parameter indicates the synchronization quality information of the S1 byte. This parameter indicates the clock synchronization source of the S1 byte. This parameter indicates the synchronization source.
S1 Byte Synchronization Quality Info
S1 Byte Clock Synchronous Source Synchronous Source
Issue 03 (2011-04-10)
B-569
Parameter Data Output Method in Holdover Mode
Value Range Normal Data Output Keep the Latest Data
Default Value Normal Data Output
Description l When all the reference timing signals are lost, the slave clock changes to the holdover mode. At this time, the slave clock works based on the latest frequency information stored before the reference timing signals are lost. Then, the frequency of the oscillator drifts slowly to ensure that the offset between the frequency of the slave clock and the reference frequency is very small. As a result, the impact caused by the drift is limited within the specified requirement. l Normal Data Output: The slave clock works based on the latest frequency information stored before the reference timing signals are lost, and the holdover duration depends on the size of the phase-locked clock register on the equipment. The holdover duration can be up to 24 hours. l Keep the Latest Data: The slave clock works in holdover mode all the time based on the latest frequency information stored before the reference timing signals are lost.
Related Tasks
B.10.2 CES ACR Clock Parameters

This topic describes CES ACR clock parameters. B.10.2.1 Parameter Description: ACR Clock Source This topic describes parameters that are related to the ACR clock source. B.10.2.2 Parameter Description: Clock Domain This topic describes parameters that are related to clock domains. B.10.2.3 Parameter Description: Clock Domain_Creation This topic describes the parameters for creating a clock domain.
B.10.2.1 Parameter Description: ACR Clock Source

This topic describes parameters that are related to the ACR clock source.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > ACR Clock from the Function Tree.

Parameter ACR Clock Source CES Service Value Range Default Value Description Identifies the ACR clock domain. This parameter displays or specifies the CES service that the master ACR clock source uses. This parameter displays the CES service from which the current ACR clock source is obtained.
Current CES Service
Related Tasks
A.9.2.1 Configuring the Primary Clock for an ACR Clock Domain
B.10.2.2 Parameter Description: Clock Domain

This topic describes parameters that are related to clock domains.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree.

Parameter Clock Domain Clock Domain Board Value Range Default Value Description Displays the clock domain. Displays the board where the clock domain is located. Displays the Smart E1 ports that are bound to a clock domain.
Clock Port
B.10.2.3 Parameter Description: Clock Domain_Creation

This topic describes the parameters for creating a clock domain.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree. Click New.

Parameter Clock Domain Value Range System Clock Domain CES ACR1 Clock Domain CES ACR2 Clock Domain CES ACR3 Clock Domain CES ACR4 Clock Domain Clock Domain Board Displays the board where the clock domain is located. Specifies the board where the Smart E1 port is located. Displays the Smart E1 ports that are not bound to a clock domain. Default Value System Clock Domain Description Specifies the clock domain to be bound.
Board
Available Port
B-572
Issue 03 (2011-04-10)
Parameter Selected Port
Value Range -
Default Value -
Description Displays the Smart E1 ports that are bound to a clock domain.
Related Tasks
A.9.2.2 Configuring Ports Using the Clock Domain
B.10.3 Parameter Description: Auxiliary Ports

This topic describes parameters that are used for configuring an external time port as an RS-485 monitoring port.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > Auxiliary Interface from the Function Tree.

Parameter Port Value Range Default Value Description Displays the port that functions as the auxiliary port. Specifies the working mode of the auxiliary port. l If the running status of the outdoor cabinet needs to be monitored, set Interface Mode to MON. l For an external time input/output port, set Interface Mode to 1st external time or 2nd external time.
Interface Mode
1st external clock 2nd external clock 1st external time 2nd external time MON Orderwire S1/F1 Commissioning serial port
1st external clock
Related Tasks
A.11.6.1 Configuring the Function of an Auxiliary Port
B.11 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
Issue 03 (2011-04-10)
B-573
B.11.1 Parameter Description: Orderwire_General This topic describes the parameters that are used for general orderwire features. B.11.2 Parameter Description: Orderwire_Advanced This topic describes the parameters that are used for advanced orderwire features. B.11.3 Parameter Description: Orderwire_F1 Data Port This topic describes the parameters that are used for F1 data ports. B.11.4 Parameter Description: Orderwire_Broadcast Data Port This topic describes the parameters that are used for broadcast data ports. B.11.5 Parameter Description: Environment Monitoring Interface This topic describes the parameters that are used for environment monitoring interfaces.
B.11.1 Parameter Description: Orderwire_General

This topic describes the parameters that are used for general orderwire features.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the General tab.
Parameters
Parameter Call Waiting Time (s) Value Range 1 to 9 Default Value 9 Description l This parameter indicates the waiting time after the local station dials the number. If the calling station does not receive the response message from the called station within the call waiting time, it automatically removes the communication connection. l If less than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to five seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to nine seconds. l The call waiting time should be set to the same for all the NEs. Dialling Mode Pulse Dual-Tone Frequency Dual-Tone Frequency This parameter indicates the dialling mode of the orderwire phone.
B-574
Issue 03 (2011-04-10)
Parameter Conference Call
Value Range -
Default Value 888
Description l This parameter indicates the telephone number of the network-wide orderwire conference call. l When an OptiX RTN 950 dials the telephone number 888, the orderwire phones of all the NEs on the orderwire subnet ring. When an OptiX RTN 950 receives the call, the orderwire phones on the other NEs do not ring. In this case, the orderwire point-to-multipoint group call changes to a point-to-point call between two NEs. l The telephone number of the orderwire conference call should be the same for all the nodes on the same subnet. l The telephone number of the orderwire conference call must have the same length as the telephone number of the orderwire phone (phone 1) at the local site.
Phone 1
100 to 99999999
101
l This parameter specifies the orderwire phone number of the local station. An addressing call refers to a point-to-point call. l The length of the orderwire phone number of each NE should be the same. It is recommended that you set the phone number to a three-digit number. l The orderwire phone number of each NE should be unique. It is recommended that the phone numbers are allocated from 101 for the NEs in a sequential order according to the NE IDs. l The orderwire phone number cannot be set to the group call number 888 and cannot start with 888.
Available Orderwire Port Selected Orderwire Port
This parameter indicates the available port for the orderwire phone. This parameter indicates the selected port for the orderwire phone.
Related Tasks
Issue 03 (2011-04-10)
B-575
B.11.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the Advanced tab.
Parameters for Bytes Occupied by Orderwire Phones

Parameter Orderwire Occupied Bytes Value Range E1 E2 Default Value E1 Description l This parameter specifies the overhead byte that is used to transmit the orderwire signals. l Regardless the parameter value, the radio link always uses a customized overhead byte to transmit the orderwire signals. Hence, this parameter should be set according to the occupied SDH overhead bytes in the ordinary SDH.
Related Tasks
B.11.3 Parameter Description: Orderwire_F1 Data Port

This topic describes the parameters that are used for F1 data ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab.
Parameters
Parameter Available Data Path Value Range Default Value Description l This parameter indicates the available F1 data channel. l Two data channels should be selected for the configuration. Number This parameter indicates the number of the F1 data port.
Issue 03 (2011-04-10)
B-576
Parameter Data Channel 1 Data Channel 2
Value Range -
Default Value -
Description l If an SDH optical or electrical line port is selected, this parameter corresponds to the F1 byte in the SDH frame at the line port. l If an IF port is selected, this parameter corresponds to the customized F1 byte in the microwave frame at the IF port. l If F1 is selected, this parameter corresponds to the F1/S1 interface on the AUX board. The F1/S1 interface complies with ITU-T G.703 and operates at the rate of 64 kbit/s.
Related Tasks
A.11.2 Configuring the Synchronous Data Service
B.11.4 Parameter Description: Orderwire_Broadcast Data Port

This topic describes the parameters that are used for broadcast data ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab.
Parameters for Broadcast Data Ports

Parameter Overhead Byte Value Range SERIAL1 to SERIAL4 Default Value SERIAL1 Description l In the case of an SDH optical/electrical line, the preset overhead byte is used to transmit the asynchronous data services. l In the case of a radio link, a customized serial overhead byte in the microwave frame is used to transmit the asynchronous data services.
Issue 03 (2011-04-10)
B-577
Parameter Broadcast Data Source
Value Range -
Default Value No Data
Description l When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding AUX board is used. l When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. l When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
Available Broadcast Data Sink Selected Broadcast Data Sink
This parameter indicates the available broadcast data sink. l When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding AUX board is used. l When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. l When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
Related Tasks
A.11.3 Configuring the Asynchronous Data Service
B.11.5 Parameter Description: Environment Monitoring Interface

This topic describes the parameters that are used for environment monitoring interfaces.
Navigation Path
Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree.
Parameters for the General Attributes

Parameter Operation Object Value Range Default Value Description This parameter indicates the operation object.
B-578
Issue 03 (2011-04-10)
Parameter Relay Control Mode
Value Range Auto Control Manual Control
Default Value Auto Control
Description l Auto Control: If an alarm is reported, the alarming relay is started up automatically. Otherwise, the alarming relay is shut down. l Manual Control: Relay Status in Major Alarm(K0) and Relay Status in Critical Alarm(K1) need to be set.
Relay Status in Major Alarm(K0)
Disabled Enabled
Disabled
l This parameter indicates that the status of the relay is set manually for major alarms. l Enable: The relay is set to the "ON" status for major alarms. l Disabled: The relay is set to the "OFF" status for major alarms. l This parameter is valid only when Relay Control Mode is set to Manual Control.
Relay Status in Critical Alarm(K1)
Disabled Enabled
Disabled
l This parameter indicates that the status of the relay is set manually for critical alarms. l Enable: The relay is set to the enabled status for critical alarms. l Disabled: The relay is set to the disabled status for critical alarms. l This parameter is valid only when Relay Control Mode is set to Manual Control.
Parameters for the Input Relay

Parameter Operation Object Path Name Using Status Value Range Unused Used Default Value Unused Description This parameter indicates the operation object. This parameter indicates or specifies the name of the channel. This parameter specifies whether the alarm interface of the input relay is used.
Issue 03 (2011-04-10)
B-579
Parameter Alarm Mode
Value Range Relay Turns Off/ High Level Relay Turns On/ Low Level
Default Value Relay Turns Off/ High Level
Description l If this parameter is set to Relay Turns Off/High Level, an alarm is generated when the relay is turned off. l If this parameter is set to Relay Turns On/Low Level, an alarm is generated when the relay is turned on. l This parameter is valid only when Using Status is set to Used.
Alarm Severity
Critical Alarm Major Alarm Minor Alarm Warning Alarm
Critical Alarm
This parameter specifies the severity of the alarm that is generated at the input relay.
Parameters for the Output Relay

Parameter Operation Object Path Name Use or Not Value Range Unused Used Default Value Unused Description This parameter indicates the operation object. This parameter indicates or specifies the name of the output channel. This parameter specifies whether the alarm interface of the output relay is used.
Parameters for the Temperature Attributes

Parameter Operation Object Monitor Status Temperature Upper Threshold (DEG.C) Temperature Lower Threshold (DEG.C) Value Range Default Value Description This parameter indicates the operation object. This parameter indicates whether the temperature attribute is monitored. This parameter indicates the upper temperature threshold of the board. When the actual temperature is higher than the preset value, an alarm is generated. This parameter indicates the lower temperature threshold of the board. When the actual temperature is lower than the preset value, an alarm is generated.
B-580
Issue 03 (2011-04-10)
Parameters for the Alarm Relay

Parameter Alarm Severity Value Range Critical Alarm Major Alarm Minor Alarm Warning Alarm Alarm Output Channel CSK-1 CSK-2 CSK-3 CSK-4 CSK-1 This parameter specifies the channel of the output alarm relay. Default Value Description This parameter indicates the severity of the alarm.
Related Tasks
A.11.5 Configure External Alarms
Issue 03 (2011-04-10)
B-581
C Glossary
C
Terms are listed in an alphabetical order. C.1 0-9 This section provides the terms starting with numbers. C.2 A-E This section provides the terms starting with letters A to E. C.3 F-J This section provides the terms starting with letters F to J. C.4 K-O This section provides the terms starting with letters K to O. C.5 P-T This section provides the terms starting with letters P to T. C.6 U-Z This section provides the terms starting with letters U to Z.
Glossary
Issue 03 (2011-04-10)
C-1
C Glossary
C.1 0-9
This section provides the terms starting with numbers. 1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
C.2 A-E
This section provides the terms starting with letters A to E.
A
ABR ACAP access control list ACL adaptive modulation See available bit rate See adjacent channel alternate polarization A list of entities, together with their access rights, which are authorized to have access to a resource. See access control list A technology that is used to automatically adjust the modulation mode according to the channel quality. When the channel quality is favorable, the equipment adopts a highefficiency modulation mode to improve the transmission efficiency and the spectrum utilization of the system. When the channel quality is degraded, the equipment adopts the low-efficiency modulation mode to improve the anti-interference capability of the link that carries high-priority services. See analog to digital converter Network elements that provide access to all or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/ or dropped from (extracted) the STM-N signal as it passed through the ADM. Address Resolution Protocol (ARP) is 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. The address resolution is a process in which the host converts the target IP address into a target MAC address before transmitting a frame. The basic function of the ARP is to query the MAC address of the target equipment through its IP address. A channel configuration method, which uses two adjacent channels (a horizontal polarization wave and a vertical polarization wave) to transmit two signals. See add/drop multiplexer 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. See assured forwarding A collection of objects that makes a whole. An aggregation can be a concrete or conceptual set of whole-part relationships among objects.
ADC add/drop multiplexer
Address Resolution Protocol
adjacent channel alternate polarization ADM administrative unit
AF aggregation
C-2
C Glossary
AIS
See alarm indication signal
alarm automatic report When an alarm is generated on the device side, the alarm is reported to the Network Management System (NMS). Then, an alarm panel prompts and the user can view the details of the alarm. alarm cascading Alarm Filtering The shunt-wound output of the alarm signals of several subracks or cabinets. An NE reports the detected alarm to the element management system (EMS). Based on the filter state of the alarm, the EMS determines whether to display or save the alarm information. If the filter state of an alarm is set to Filter, the alarm is not displayed or stored on the EMS. The alarm, however, is still monitored by the NE.
alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. alarm suppression A function used not to monitor alarms for a specific object, which may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board. See adaptive modulation An electronic circuit that converts continuous signals to discrete digital numbers. The reverse operation is performed by a digital-to-analog converter (DAC). See automatic protection switching See Address Resolution Protocol 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. A protocol for the transmission of a variety of digital signals using uniform 53 byte cells. A transfer mode in which the information is organized into cells; it is asynchronous in the sense that the recurrence of cells depends on the required or instantaneous bit rate. Statistical and deterministic values may also be used to qualify the transfer mode. See Asynchronous Transfer Mode ATM permanent virtual circuit See automatic transmit power control A device used to increase the attenuation of an Optical Fiber Link. Generally used to ensure that the signal at the receive end is not too strong. See administrative unit Capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic. A method of adjusting the transmit power based on fading of the transmit signal detected at the receiver 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.
AM analog to digital converter APS ARP assured forwarding
Asynchronous Transfer Mode
ATM ATM PVC ATPC attenuator AU automatic protection switching automatic transmit power control available bit rate
Issue 03 (2011-04-10)
C-3
C Glossary
B
backward defect indication bandwidth When detecting a defect, the sink node of an LSP uses backward defect indication (BDI) to inform the upstream end of the LSP of a downstream defect along the return path. A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate. A logical entity that connects the BTS with the MSC in a GSM network. It interworks with the BTS through the Abis interface, the MSC through the A interface. It provides the following functions: radio resource management, base station management, power control, handover control, and traffic measurement. One BSC controls and manages one or more BTSs in an actual network.
base station controller
base transceiver station A Base Transceiver Station terminates the radio interface. It allows transmission of traffic and signaling across the air interface. The BTS includes the baseband processing, radio equipment, and the antenna. basic input/output system BDI BE BER best effort 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. See backward defect indication See best effort See bit error rate 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. The binding strap is 12.7 mm wide, with one hook side (made of transparent polypropylene material) and one mat side (made of black nylon material). See basic input/output system See bit interleaved parity An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network. A method of error monitoring. With even parity an X-bit code is generated by the transmitting equipment 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, etc. 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 X-bit sequences in the covered portion of the signal. The covered portion includes the BIP-X. See bridge protocol data unit
binding strap BIOS BIP bit error bit error rate bit interleaved parity
BPDU
C-4
Issue 03 (2011-04-10)
C Glossary
bridge protocol data unit
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. A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address. See base station controller See base transceiver station A storage area used for handling data in transit. Buffers are used in internetworking to compensate for differences in processing speed between network devices. Bursts of data can be stored in buffers until they can be handled by slower processing devices. In a program, buffers are created to hold some amount of data from each of the files that will be read or written. In a streaming media application, the program uses buffers to store an advance supply of audio or video data to compensate for momentary delays.
broadcast BSC BTS buffer
C
cable tie cable tray cable trough CAR CBR CBS CC CCC CCDP CCM CE The tape used to bind the cables. N/A N/A See committed access rate See constant bit rate See committed burst size See connectivity check See circuit cross connect See co-channel dual polarization See continuity check message See customer edge
central processing unit The computational and control unit of a computer. The CPU is the device that interprets and executes instructions. The CPU has the ability to fetch, decode, and execute instructions and to transfer information to and from other resources over the computer's main data-transfer path, the bus. CES CF CGMP channel See circuit emulation service See compact flash See Cisco Group Management Protocol A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. The channel can be established through wire, radio (microwave), fiber or a combination of the three. The amount of information transmitted per second in a channel is the information transmission speed, expressed in bits per second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s (1012 bit/s).
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. C-5
Issue 03 (2011-04-10)
C Glossary
CIR circuit cross connect circuit emulation service
See committed information rate An implementation of MPLS L2VPN through the static configuration of labels. 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. N/A See common and internal spanning tree A switch of the highest priority is elected as the root in an MSTP network. The method to keep the time on each node being synchronized with a clock source in a network. A channel configuration method, which uses a horizontal polarization wave and a vertical polarization wave to transmit two signals. The Co-Channel Dual Polarization is twice the transmission capacity of the single polarization. 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. A packet whose priority is determined by defined colors. A traffic control method that uses a set of rate limits to be applied to a router interface. CAR is a configurable method by which incoming and outgoing packets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined. committed burst size. 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.
Cisco Group Management Protocol CIST CIST root clock tracing co-channel dual polarization coarse wavelength division multiplexing colored packet committed access rate
committed burst size
committed information The rate at which a frame relay network agrees to transfer information in normal rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket. common and internal spanning tree compact flash The single spanning tree calculated by STP and RSTP together with the logical continuation of that connectivity by using MST Bridges and regions, calculated by MSTP to ensure that all LANs in the bridged local area network are simply and fully connected. Compact flash (CF) was originally developed as a type of data storage device used in portable electronic devices. For storage, CompactFlash typically uses flash memory in a standardized enclosure. A process that combines multiple virtual containers. The combined capacities can be used a single capacity. The concatenation also keeps the integrity of bit sequence. Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically.
concatenation connectivity check
C-6
Issue 03 (2011-04-10)
C Glossary
constant bit rate
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. CCM is used to detect the link status. Used to protect optical fibers. See central processing unit See cyclic redundancy check A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate the cross-connect interference between two polarization waves in the CCDP. 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. See coarse wavelength division multiplexing 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.
continuity check message corrugated pipe CPU CRC cross polarization interference cancellation customer edge CWDM cyclic redundancy check
D
data communication network data communications channel A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF). The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-M channel. A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram, UDP datagram. See direct current See DC-return common (with ground) DC-return common (with ground) See DC-return common (with ground) See DC-return isolate (with ground) 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. 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.
Datagram DC DC-C DC-C DC-C DC-I DC-return common (with ground) DC-return common (with ground)
Issue 03 (2011-04-10)
C Glossary
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with ground) 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 DCN DDF DDN DE differentiated services See data communications channel See data communication network See digital distribution frame See digital data network See discard eligible A service architecture that provides the end-to-end QoS function. It consists of a series of functional units implemented at the network nodes, including a small group of perhop forwarding behaviors, packet classification functions, and traffic conditioning functions such as metering, marking, shaping and policing. A marker in the header of each IP packet that prompts network routers to apply differentiated grades of service to various packet streams. It is specified by the DiffServ policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and other IP-based network service providers to offer different levels of service to customers. See differentiated services 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. A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals. A digital modulation controls the changes in amplitude, phase, and frequency of the carrier based on the changes in the baseband digital signal. In this manner, the information can be transmitted by the carrier. Electrical current whose direction of flow does not reverse. The current may stop or change amplitude, but it always flows in the same direction. A bit in the frame relay header. It indicates the priority of a packet. If a node supports the FR QoS, the rate of the accessed FR packets is controlled. When the packet traffic exceeds the specified traffic, the DE value of the redundant packets is set to 1. In the case of network congestion, the packets with DE value as 1 are discarded at the node. 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. A DS node that connects one DS domain to a node either in another DS domain or in a domain that is not DS-capable. In the DifferServ mechanism, the DS domain is a domain consisting of a group of network nodes that share the same service provisioning policy and same PHB. It provides point-to-point QoS guarantees for services transmitted over this domain. A DS node located at the center of a DS domain. It is a non-DS boundary node. A DS-compliant node, which is subdivided into DS boundary node and ID interior node. See differentiated services code point
differentiated services code point
DiffServ digital data network
digital distribution frame digital modulation
direct current discard eligible
Distance Vector Multicast Routing Protocol DS boundary node DS domain
DS interior node DS node DSCP
C-8
Issue 03 (2011-04-10)
C Glossary
dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves orthogonally polarized. DVMRP See Distance Vector Multicast Routing Protocol
E
E-Aggr E-LAN E-Line E-Tree EBS ECC EF electromagnetic compatibility See Ethernet aggregation See Ethernet LAN See Ethernet line See Ethernet-tree See excess burst size See embedded control channel See expedited forwarding Electromagnetic compatibility is the 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. Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment. The sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field. 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. See electromagnetic compatibility See electromagnetic interference A mark on a cable, a subrack, or a cabinet for identification. See Ethernet private line See Ethernet private LAN service A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading. See Ethernet ring protection switching See electrostatic discharge Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap. A technology complemented in LAN. It adopts 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. The Ethernet network features high reliability and easy maintaining. A technology complemented in LAN. It adopts 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. The Ethernet network features high reliability and easy maintaining..
electromagnetic interference electrostatic discharge embedded control channel EMC EMI Engineering label EPL EPLAN equalization ERPS ESD ESD jack Ethernet
Ethernet
Issue 03 (2011-04-10)
C-9
C Glossary
Ethernet aggregation Ethernet LAN Ethernet line Ethernet private LAN service Ethernet private line Ethernet ring protection switching Ethernet virtual private LAN service Ethernet virtual private line Ethernet-tree ETS ETSI European Telecommunications Standards Institute EVPL EVPLAN excess burst size
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual connection). A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet virtual connection). A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual connection). An Ethernet service type, which carries Ethernet characteristic information over a dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. 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. protection switching mechanisms for ETH layer Ethernet ring topologies. An Ethernet service type, which carries Ethernet characteristic information over a shared bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. An Ethernet service type, which carries Ethernet characteristic information over shared bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server layer networks. An Ethernet service type that is based on a Point-to-multipoint Ethernet Virtual Connection. European Telecommunication Standards See European Telecommunications Standards Institute A standards-setting body in Europe. Also the standards body responsible for GSM.
See Ethernet virtual private line See Ethernet virtual private LAN service 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. An operation to check if the protection switching protocol functions normally. The protection switching is not really performed. Connecting a storage system to more disk enclosures through connection cables, thus expanding the capacity of the storage system. 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".
Exercise Switching expansion expedited forwarding
C-10
Issue 03 (2011-04-10)
C Glossary
C.3 F-J
This section provides the terms starting with letters F to J.
F
failure If the fault persists long enough to consider the ability of an item with a required function to be terminated. The item may be considered as having failed; a fault has now been detected. Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables), 100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical fibers). The link pulse that is used to encode information during automatic negotiation. See frequency diversity See forward defect indication See fast Ethernet See forward error correction fast failure detection A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack. 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. See First in First out A member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTP roles: one must be an FTP client and the other an FTP server. A stack management mechanism. The first saved data is first read and invoked. For normal traffic signals, switches normal traffic signal to the protection section, unless an equal or higher priority switch command is in effect or SF condition exists on the protection section, by issuing a forced switch request for that traffic signal. Forward defect indication (FDI) is 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. A bit error correction technology that adds the correction information to the payload at the transmit end. Based on the correction information, the bit errors generated during transmission are corrected at the receive end.
fast Ethernet
fast link pulse FD FDI FE FEC FFD fiber patch cord field programmable gate array
FIFO File Transfer Protocol
First in First out Forced switch
forward defect indication
forward error correction
Issue 03 (2011-04-10)
C Glossary
Forwarding plane FPGA fragment Fragmentation frame
Also referred to as the data plane. The forwarding plane is connection-oriented, and can be used in Layer 2 networks such as an ATM network. See field programmable gate array Piece of a larger packet that has been broken down to smaller units. Process of breaking a packet into smaller units when transmitting over a network medium that cannot support the original size of the packet. A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties. A diversity scheme that enables two or more microwave frequencies with a certain frequency interval are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. See File Transfer Protocol A full-duplex, or sometimes double-duplex system, allows communication in both directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line telephone networks are full-duplex, since they allow both callers to speak and be heard at the same time. A good analogy for a full-duplex system would be a two-lane road with one lane for each direction.
frequency diversity
FTP full-duplex
G
gateway network element GE generic framing procedure A network element that is used for communication between the NE application layer and the NM application layer See gigabit Ethernet A framing and encapsulated method which can be applied to any data type. It has been standardized by ITU-T SG15.
generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is to adapt the traffic to network resources that can be provided by the downstream router to avoid packet discarding and congestion. GFP gigabit Ethernet See generic framing procedure GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge (switch) or a router as the center, it gives full play to the performance and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that are private, causing the length of the links to be sufficient for backbone applications in a building and campus. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users. See gateway network element See Global Positioning System
Global Positioning System GNE GPS
C-12
Issue 03 (2011-04-10)
C Glossary
graphical user interface A visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen. GTS GUI guide rail See generic traffic shaping See graphical user interface Components to guide, position, and support plug-in boards.
H
HA half-duplex See high availability A transmitting mode in which a half-duplex system provides for communication in both directions, but only one direction at a time (not simultaneously). Typically, once a party begins receiving a signal, it must wait for the transmitter to stop transmitting, before replying. See high level data link control A type of QoS that can control the traffic of users, and perform the scheduling according to the priority of user services. HQoS has a perfect 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. Typically, a scheme in which two modules operate in active/standby mode to achieve high availability. When the active module fails, the standby module automatically takes over the system functions of the active module. The HDLC protocol is a general purpose protocol which operates at the data link layer of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by adding a trailer and a header. 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. In an SDH network, the higher order path layers provide a server network from the lower order path layers. The priority of the tunnel with respect to holding resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the resources occupied by the tunnel can be preempted by other tunnels. A network connection between two distant nodes. For Internet operation a hop represents a small step on the route from one main computer to another. A mechanism of ensuring device running security. The environment variables and storage information of each running device are synchronized to the standby device. When the faults occur on the running device, the standby device can take over the services in the faulty device in automatic or manual way to ensure the normal running of the entire system. See higher order path See hierarchical quality of service See hot standby See High Speed Downlink Packet Access
HDLC hierarchical quality of service
high availability
high level data link control High Speed Downlink Packet Access
higher order path Hold priority
hop hot standby
HP HQoS HSB HSDPA

Issue 03 (2011-04-10)
C Glossary
HSM HTB hybrid radio
hitless switch mode high tributary bus The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.
I
ICMP IDU IEC IEEE IETF IF IGMP IGMP snooping See Internet Control Message Protocol See indoor unit See International Electrotechnical Commission See Institute of Electrical and Electronics Engineers See Internet Engineering Task Force See intermediate frequency See Internet Group Management Protocol A multicast constraint mechanism running on a layer 2 device. This protocol manages and controls the multicast group by listening to and analyze the Internet Group Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner, the spread of the multicast data on layer 2 network can be prevented efficiently. See inverse multiplexing over ATM The indoor unit of the split-structured radio equipment. It implements accessing, multiplexing/demultiplexing, and IF processing for services. A method of looping the signals from the cross-connect unit back to the cross-connect unit. 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.
IMA indoor unit Inloop Institute of Electrical and Electronics Engineers
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF signal. Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generate routes.
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward Intermediate System datagrams or packets through a packet-based network, a process called routing. routing protocol internal spanning tree International Electrotechnical Commission International Organization for Standardization A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0. The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronic standards. An international association that works to establish global standards for communications and information exchange. Primary among its accomplishments is the widely accepted ISO/OSI reference model, which defines standards for the interaction of computers connected by communications networks.
C-14
Issue 03 (2011-04-10)
C Glossary
International Telecommunication UnionTelecommunication Standardization Sector Internet Control Message Protocol
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. 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). 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. The protocol for managing the membership of Internet Protocol multicast groups among the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships. The TCP/IP standard protocol that defines the IP packet as the unit of information sent across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part. The entire protocol suite is often referred to as TCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791. A update version of IPv4. It is also called IP Next Generation (IPng). The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF). IPv6 is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. A update version of IPv4. It is also called IP Next Generation (IPng). The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF). IPv6 is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. The ATM inverse multiplexing technique involves inverse multiplexing and demultiplexing 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. This is referred to as an IMA group. See Internet Protocol See Internet protocol version 6 See Internet protocol version 6 See Intermediate System to Intermediate System routing protocol See International Organization for Standardization See internal spanning tree See International Telecommunication Union-Telecommunication Standardization Sector
Internet Engineering Task Force
Internet Group Management Protocol Internet Protocol
Internet protocol version 6
Internet protocol version 6
inverse multiplexing over ATM
IP IPV6 IPv6 IS-IS ISO IST ITU-T
Issue 03 (2011-04-10)
C-15
C Glossary
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system instability.
C.4 K-O
This section provides the terms starting with letters K to O.
L
L2VPN label switched path See Layer 2 virtual private network 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 normal routing mechanisms, or through configuration. Basic element of 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. See Link Aggregation Control Protocol See link aggregation group See local area network See local area network link access protocol-SDH A component that generates directional optical waves of narrow wavelengths. The laser light has better coherence than ordinary light. The fiber system takes the semi-conductor laser as the light source. A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits and distributes packet data based on the MAC address. Since the MAC address is the second layer of the OSI model, this data forwarding method is called layer 2 switch.
label switching router
LACP LAG LAN LAN LAPS Laser
layer 2 switch
Layer 2 virtual private A virtual private network achieved by Layer 2 switching technologies in the packet network switched (IP/MPLS) network. LB LCAS LCT line rate line rate forwarding Link Aggregation Control Protocol See loopback See link capacity adjustment scheme local craft terminal The maximum packet forwarding capacity on a cable. The value of line rate equals the maximum transmission rate capable on a given type of media. The line rate equals the maximum transmission rate capable on a given type of media. A method of bundling a group of physical interfaces together as a logical interface to increase bandwidth and reliability. For related protocols and standards, refer to IEEE 802.3ad.
C-16
Issue 03 (2011-04-10)
C Glossary
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link 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 in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitlessly 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. Protection provided by the bypass tunnel for the link on the working tunnel. The link is a downstream link adjacent to the PLR. When the PLR fails to provide node protection, the link protection should be provided. linear multiplex section protection 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). 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). When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel. See Loss Of Frame loss of multiframe A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors. See loss of pointer See Loss Of Signal A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost frame delineation. This is used to monitor the performance of the PHY layer. Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost the pointer to the start of cell in the payload. This is used to monitor the performance of the PHY layer. Loss of signal (LOS) indicates that there are no transitions occurring in the received signal. lower order path link-state pass through See label switched path
Link Protection
LMSP local area network
local area network
Locked switching
LOF LOM loopback LOP LOS Loss Of Frame
loss of pointer
Loss Of Signal LP LPT LSP
Issue 03 (2011-04-10)
C-17
C Glossary
LSR
See label switching router
M
MA MAC MAC MADM main topology See maintenance association See media access control See media access control multiple add/drop multiplexer A interface that displays the connection relation of NEs on the NMS (screen display). The default client interface of the NMS, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs, subnets in the network, the communication status as well as the basic network operation status. All topology management functions are accessed here. That portion of a Service Instance, preferably all of it or as much as possible, the connectivity of which is maintained by CFM. It is also a full mesh of Maintenance Entities. A MEP is an actively managed CFM Entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM frames and track any responses. It is an end point of a single Maintenance Association, and terminates a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association. The network or the part of the network for which connectivity is managed by CFM. The devices in an MD are managed by a single ISP. Maintenance Point (MP) is one of either a MEP or a MIP. A type of database used for managing the devices in a communications network. It comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network. Switches normal traffic signal to the protection section, unless a failure condition exists on other sections (including the protection section) or an equal or higher priority switch command is in effect, by issuing a manual switch request for that normal traffic signal.
maintenance association maintenance association end point
maintenance domain maintenance point management information base manual switch
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies, unit depending on the network576 bytes on X.25 networks, for example, 1500 bytes on Ethernet, and 17,914 bytes on 16 Mbps 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. MBS MCF MD MDI Mean Time Between Failures Mean Time To Repair maximum burst size See message communication function See maintenance domain See medium dependent interface The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. The average time that a device will take to recover from a failure.
C-18
Issue 03 (2011-04-10)
C Glossary
media access control
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. 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. The electrical and mechanical interface between the equipment and the media transmission. See maintenance association end point maintenance end point The MCF is composed of a protocol stack that allows exchange of management information with their prs. See management information base maintenance intermediate point A piece of angle plate with holes in it on a rack. It is used to fix network elements or components. See maintenance point maintenance point identification See Multiprotocol Label Switching The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network. In this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of different media types, such as ATM, FR, VLAN, Ethernet, and PPP. The MPLS OAM provides continuity check for a single LSP, and provides a set of fault detection tools and fault correct mechanisms for MPLS networks. The MPLS OAM and relevant protection switching components implement the detection function for the CRLSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs. In this way, the impact of a fault can be lowered to the minimum. See multiprotocol label switching traffic engineering
media access control
medium dependent interface MEP MEP message communication function MIB MIP mounting ear MP MPID MPLS MPLS L2VPN
MPLS OAM
MPLS TE
Issue 03 (2011-04-10)
C-19
C Glossary
MPLS TE tunnel
In the case of reroute deployment, or when traffic needs to be transported through multiple trails, multiple LSP tunnels might be used. In traffic engineering, such a group of LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has two identifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquely define the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE or FILTER_SPEC object. See multiplex section See multiplex section protection See Multiple Spanning Tree Protocol See Mean Time Between Failures See Mean Time To Repair See maximum transmission unit A process of transmitting packets of data from one source to many destinations. The destination address of the multicast packet uses Class D address, that is, the IP address ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast group rather than a host. Multiple spanning tree protocol. The MSTP 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. The trail between and including two multiplex section trail termination functions. 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. 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. N/A
MS MSP MSTP MTBF MTTR MTU Multicast
Multiple Spanning Tree Protocol
multiplex section multiplex section protection Multiprotocol Label Switching
multiprotocol label switching traffic engineering
N
N+1 protection NE NE Explorer A radio link protection system composed of N working channels and one protection channel. See network element The main operation interface, of the NMS, which is used to manage the telecommunication equipment. In the NE Explorer, the user can query, manage and maintain the NE, boards, and ports on a per-NE basis.
C-20
Issue 03 (2011-04-10)
C Glossary
network element
A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control and communication(SCC) board which manages and monitors the entire network element. The NE software runs on the SCC board.
Network Management A system in charge of the operation, administration, and maintenance of a network. System network service access A network address defined by ISO, through which entities on the network layer can point access OSI network services. network to network interface next hop NLP NMS NNI node An internal interface within a network linking two or more elements. The next router to which a packet is sent from any given router as it traverses a network on its journey to its final destination. normal link pulse See Network Management System See network to network interface A node stands for a managed device in the network. For a device with a single frame, one node stands for one device. For a device with multiple frames, one node stands for one frame of the device. Therefore, a node does not always mean a device. A parameter of the FRR protection. It indicates that the bypass tunnel should be able to protect the downstream node that is involved in the working tunnel and adjacent to the PLR. The node cannot be a merge point, and the bypass tunnel should also be able to protect the downstream link that is involved in the working tunnel and adjacent to the PLR. A network element whose communication with the NM application layer must be transferred by the gateway network element application layer. See non-gateway network element See network service access point not stop forwarding
Node Protection
non-gateway network element non-GNE NSAP NSF
O
OAM ODF ODU OM One-to-One Backup See operation, administration and maintenance See optical distribution frame See outdoor unit Operation and maintenance A local repair method in which a backup tunnel is separately created for each protected tunnel at a PLR.
open shortest path first 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 of the network topology which is identical on all routers in the area.
Issue 03 (2011-04-10)
C-21
C Glossary
Open Systems Interconnection
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. A group of network support functions that monitor and sustain segment operation, 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. A device installed at the end of a fiber, optical source or receive unit. It is used to couple the optical wave to the fiber when connected to another device of the same type. A connector can either connect two fiber ends or connect a fiber end and an optical source (or a detector).+ A frame which is used to transfer and spool fibers. A channel that provides voice communication between operation engineers or maintenance engineers of different stations. See Open Systems Interconnection See open shortest path first The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for RF signals. A method of looping back the input signals received at a port to an output port without changing the structure of the signals. The ranger of optical energy level of output signals.
operation, administration and maintenance
optic fiber connector
optical distribution frame orderwire OSI OSPF outdoor unit Outloop Output optical power
C.5 P-T
This section provides the terms starting with letters P to T.
P
packet switched network Packing case Path A telecommunication network which works in packet switching mode. A case which is used for packing the board or subrack. A performance resource object defined in the network management system. The left end of a path is a device node whose port needs to be specified and the right end of a path is a certain IP address which can be configured by the user. By defining a path in the network management system, a user can test the performance of a network path between a device port and an IP address. The tested performance may be the path delay, packet loss ratio or other aspects. See peak burst size See printed circuit board
PBS PCB
C-22
Issue 03 (2011-04-10)
C Glossary
PCI bus PDH PDU PE peak burst size
PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bit for interconnecting chips, expansion boards, and processor/memory subsystems. See plesiochronous digital hierarchy See protocol data unit See provider edge A parameter 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 this parameter should be not less than the maximum length of the IP packet that might be forwarded. A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLS enabled network. It refers to the process whereby the outermost label of an MPLS tagged packet is removed by a Label Switched Router (LSR) before the packet is passed to an adjacent Label Edge Router (LER). 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). See per-hop behavior See penultimate hop popping See peak information rate 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.
peak information rate penultimate hop popping
per-hop behavior
PHB PHP PIR plesiochronous digital hierarchy
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is perpendicular to the plane of horizon, this electromagnetic wave is called vertically polarized wave; if the electric field vector of the electromagnetic wave is parallel to the plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the tip of the electric field vector, at a fixed point in space, describes a circle, this electromagnetic wave is called circularly polarized wave. A direct current power distribution box at the upper part of a cabinet, which supplies power for the subracks in the cabinet. See Point-to-Point Protocol See priority queue See pseudo random binary sequence primary reference clock 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.
Power box PPP PQ PRBS PRC printed circuit board
Issue 03 (2011-04-10)
C-23
C Glossary
priority queue
An abstract data type in computer programming that supports the following three operations: 1) InsertWithPriority: add an element to the queue with an associated priority 2) GetNext: remove the element from the queue that has the highest priority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3) PeekAtNext (optional): look at the element with highest priority without removing it A cable which connects the equipment and the protection grounding bar. Usually, one half of the cable is yellow; while the other half is green. A specific path that is part of a protection group and is labeled protection. It is a data packet at the network layer of the OSI model. A device that is located in the backbone network of the MPLS VPN structure. A PE is responsible for VPN user management, establishment of LSPs between PEs, and exchange of routing information between sites of the same VPN. During the process, 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.
protection ground cable Protection path protocol data unit provider edge
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence values of any of the other elements, similar to real random sequences. pseudo wire 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 A type of end-to-end Layer 2 transmitting technology. It emulates the essential attributes edge-to-edge of a 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 Multiplexed (TDM) circuit and SONET/SDH. The simulation approximates to the real situation. PSN PTN PW PWE3 See packet switched network packet transport network See pseudo wire See pseudo wire emulation edge-to-edge
Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It encapsulates the tag of the user's private virtual local area network (VLAN) into the tag of the public VLAN. The packet carries two layers of tags to travel through the backbone network of the carrier. In this manner, the layer 2 virtual private network (VPN) is provided for the user. See quality of service See quadrature phase shift keying
QoS QPSK
quadrature phase shift A modulation method of data transmission through the conversion or modulation and keying 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.
C-24
Issue 03 (2011-04-10)
C Glossary
quality of service
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.
R
radio frequency A type of electric current in the wireless network using AC antennas to create an electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave. The AC with the frequency lower than 1 kHz is called low-frequency current. The AC with frequency higher than 10 kHz is called high-frequency current. RF can be classified into such high-frequency current. A device in the RNS which is in charge of controlling the use and the integrity of the radio resources.
radio network controller
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according to the specified higher limit and lower limit of a queue so that global TCP synchronization resulted in traditional Tail-Drop can be prevented. Rapid Spanning Tree Protocol RDI received signal level Received Signal Strength Indicator Receiver Sensitivity RED Reed-Solomon-Code 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. See remote defect indication The signal level at a receiver input terminal. The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD within a specified timeslot. The reference point for the measurement shall be the antenna Receiver sensitivity is defined as the minimum acceptable value of average received power at point R to achieve a 1 x 10-12 BER (The FEC is open). See random early detection A forward error correction code located before interleaving that enables correction of errors induced by burst noise. Widely used error correction scheme to fight transmission errors at the receiver site. See remote error indication A signal transmitted at the first opportunity in the outgoing direction when a terminal detects specific defects in the incoming signal.
REI remote defect indication
remote error indication A remote error indication (REI) is sent upstream to signal an error condition. There are two types of REI alarms: Remote error indication line (REI-L) is sent to the upstream LTE when errors are detected in the B2 byte. Remote error indication path (REI-P) is sent to the upstream PTE when errors are detected in the B3 byte. Request For Comments A document in which a standard, a protocol, or other information pertaining to the operation of the Internet is published. The RFC is actually issued, under the control of the IAB, after discussion and serves as the standard. RFCs can be obtained from sources such as InterNIC.
Issue 03 (2011-04-10)
C-25
C Glossary
Resource Reservation Protocol
The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. RSVP is a network control protocol like Internet Control Message Protocol (ICMP). A traffic control method. In telecommunication, when detecting that the transmit end transmits a large volume of traffic, the receive end sends signals to ask the transmit end to slow down the transmission rate. See radio frequency See Request For Comments See Routing Information Protocol remote network monitoring remote network monitoring See radio network controller An alarm directly caused by anomaly events or faults in the network. Some lower-level alarms always accompany a root alarm. A route is the path that network traffic takes from its source to its destination. In a TCP/ IP network, each IP packet is routed independently. Routes can change dynamically. A mapping table that stores the relationship between the original address, destination address, short message (SM) protocol type and account. The SMSC delivers an SM to the designated account according to the information set in the route table. 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. A table that stores and updates the locations (addresses) of network devices. Routers regularly share routing table information to be up to date. A router relies on the destination address and on the information in the table that gives the possible routes--in hops or in number of jumps--between itself, intervening routers, and the destination. Routing tables are updated frequently as new information is available. See received signal level See Received Signal Strength Indicator See Rapid Spanning Tree Protocol See Resource Reservation Protocol radio transmission node
reverse pressure
RF RFC RIP RMON RMON RNC Root alarm route route table
Routing Information Protocol
routing table
RSL RSSI RSTP RSVP RTN
S
SD SDH SEMF See space diversity See synchronous digital hierarchy See synchronous equipment management function
C-26
Issue 03 (2011-04-10)
C Glossary
service level agreement A service contract between a customer and a service provider that specifies the forwarding service a customer should receive. A customer may be a user organization (source domain) or another differentiated services domain (upstream domain). A SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. Service Level Agreement * A management-documented agreement that defines the relationship between service provider and its customer. It also provides specific, quantifiable information about measuring and evaluating the delivery of services. The SLA details the specific operating and support requirements for each service provided. It protects the service provider and customer and allows the service provider to provide evidence that it has achieved the documented target measure. See severely errored second The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the tunnel can preempt the resources required by other backup tunnels.
SES Setup Priority
severely errored second A one-second period which has a bit error ratio X 10-3 or at least one defect. Time interval of one second during which a given digital signal is received with an error ratio greater than 1 X 10 -3 (Rec. ITU R F. 592 needs correction). SF SFP side trough signal cable signal fail signal to noise ratio See signal fail See small form-factor pluggable The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet. Common signal cables cover the E1 cable, network cable, and other non-subscriber signal cable. A signal that indicates the associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active. The ratio of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel). 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. Designating or pertaining to a method of operation in which information can be transmitted in either direction, but not simultaneously, between two points. See service level agreement See Service Level Agreement * To divide data into the information units proper for transmission. A specification for a new generation of optical modular transceivers. See subnetwork connection
Simple Network Management Protocol
simplex SLA SLA* Slicing small form-factor pluggable SNC
Issue 03 (2011-04-10)
C-27
C Glossary
SNCP SNMP SNR space diversity
See subnetwork connection protection See Simple Network Management Protocol See signal to noise ratio A diversity scheme that enables two or more antennas separated by a specific distance to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Currently, only receive SD is used.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant network to block some undesirable redundant paths through certain algorithms and prune a loop network into a loop-free tree network. SSM static virtual circuit See Synchronization Status Message Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPN information by manual configuration of VC labels, instead of by a signaling protocol.
Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be transmitted across a single physical channel. It dynamically allocates bandwidth only to active input channels, to make better use of available bandwidth and allow more devices to be connected than with other multiplexing techniques. Compare with TDM. STM STM-1 STM-N STP sub-network See Synchronous Transport Module See synchronous transport mode-1 See synchronous transport module of order N See Spanning Tree Protocol Sub-network is the logical entity in the transmission network and comprises a group of network management objects. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a sub-network is used to contain the equipments which are located in adjacent regions and closely related with one another, and it is indicated with a sub-network icon on a topological view. The U2000 supports multilevels of sub-networks. A sub-network planning can better the organization of a network view. On the one hand, the view space can be saved, on the other hand, it helps the network management personnel focus on the equipments under their management. The technique used by the IP protocol to determine which network segment packets are destined for. The subnet mask is a binary pattern that is stored in the client machine, server or router and is matched with the IP address.
subnet mask
subnetwork connection A "transport entity" that transfers information across a subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork. subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. SVC switch See static virtual circuit To filter, forward frames based on label or the destination address of each frame. This behavior operates at the data link layer of the OSI model.
C-28
Issue 03 (2011-04-10)
C Glossary
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link. Message Nodes on an SDH network and a synchronization network acquire upstream clock 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. synchronous digital hierarchy 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. The SEMF converts performance data and implementation specific hardware alarms into object-oriented messages for transmission over DCCs and/or a Q interface.
synchronous equipment management function
synchronous transport Synchronous Transfer Mode at 155 Mbit/s. mode-1 Synchronous Transport Module An STM is the information structure used to support section layer connections in the SDH. It consists of information payload and Section Overhead (SOH) information fields organized in a block frame structure which repeats every 125. The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
synchronous transport A STM-N is the information structure used to support section layer connections in SDH. See ITU-T Recommendation G. 707 for STM modules of order 1, 4, 16 and 64. module of order N
T
tail drop A type of QoS. When a queue within a network router reaches its maximum length, packet drops can occur. When a packet drop occurs, connection-based protocols such as TCP slow down their transmission rates in an attempt to let queued packets be serviced, thereby letting the queue empty. This is also known as tail drop because packets are dropped from the input end (tail) of the queue. 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. tag control information See Transmission Control Protocol See time division multiplexing See traffic engineering See traffic engineering database
Tail drop
TCI TCP TDM TE TEDB
Telecommunication A protocol model defined by ITU-T for managing open systems in a communications Management Network network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services.
Issue 03 (2011-04-10) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. C-29
C Glossary
TIM time division multiplexing
trace identifier mismatch 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. A technique used in best-effort delivery systems to prevent packets that loop endlessly. The TTL is set by the sender to the maximum time the packet is allowed to be in the network. Each router in the network decrements the TTL field when the packet arrives, and discards any packet if the TTL counter reaches zero. See Telecommunication Management Network A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header. See tributary protection switch 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. TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to know the features of the dynamic TE of every links by expanding the current IGP, which uses the link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS contain some TE features, such as the link bandwidth and color. The maximum reserved bandwidth of the link and the unreserved bandwidth of every link with priority are rather important. Every router collects the information about TE of every links in its area and generates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLS TE network. It is a way of controlling the network traffic from a computer to optimize or guarantee the performance and minimize the delay. It actively adjusts the output speed of traffic in the scenario that the traffic matches network resources provided by the lower layer devices, avoiding packet loss and congestion. The protocol within TCP/IP that governs the breakup of data messages into packets to be sent via IP (Internet Protocol), and the reassembly and verification of the complete messages from packets received by IP. A connection-oriented, reliable protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in the ISO/OSI reference model. Tributary protection switching, a function provided by the equipment, is intended to protect N tributary processing boards through a standby tributary processing board. See two rate three color marker See time to live tributary unit 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.
time to live
TMN ToS priority TPS traffic engineering
traffic engineering database
Traffic shaping
Transmission Control Protocol
tributary protection switch trTCM TTL TU Tunnel
C-30
Issue 03 (2011-04-10)
C Glossary
two rate three color marker
The trTCM meters an IP packet stream and marks its packets based on two rates, Peak Information Rate (PIR) and Committed Information Rate (CIR), and their associated burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the CIR.
C.6 U-Z
This section provides the terms starting with letters U to Z.
U
U-VLAN UAS UBR UDP underfloor cabling UNI unicast unspecified bit rate A VLAN attribute indicating that the current VLAN is a user VLAN of an M-VLAN. Multicast services are copied from the M-VLAN to the user VLAN. unavailable second See unspecified bit rate See User Datagram Protocol The cables connected cabinets and other devices are routed underfloor. See user network interface The process of sending data from a source to a single recipient. No commitment to transmission. No feedback to congestion. This type of service is ideal for the transmission of IP datagrams. In case of congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the sender. An operation to report some or all configuration data of an NE to the NMS(Network Management system). The configuration data then covers the configuration data stored at the NMS side. 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 datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDP messages can be lost, duplicated, delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is, the destination device does not actively confirm whether the correct data packet is received.
upload
User Datagram Protocol
user network interface The interface between user equipment and private or public network equipment (for example, ATM switches).
V
V-UNI variable bit rate See virtual user-network interface 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. See variable bit rate See virtual container
VBR VC
Issue 03 (2011-04-10)
C Glossary
VCC VCG VCI VCTRUNK virtual channel connection virtual channel identifier virtual concatenation group virtual container
See virtual channel connection See virtual concatenation group See virtual channel identifier A virtual concatenation group applied in data service mapping, also called the internal port of a data service processing board The VC logical trail that carries data between two end points in an ATM network. A logical grouping of multiple virtual channel connections into one virtual connection. A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. A group of co-located member trail termination functions that are connected to the same virtual concatenation link The information structure used to support path layer connections in the SDH. It consists of information payload and path Overhead (POH) information fields organized in a block frame structure which repeats every 125 or 500 s. A logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number. This is often associated with switched Ethernet. The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which virtual path the cell belongs. 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 local area network virtual path identifier virtual private LAN service
virtual private network A system configuration, where the subscriber is able to build a private network via connections to different network switches that may include private network capabilities. virtual route forward VRF performs the function of establishing multiple virtual routing devices on one actual routing device. That is, the L3 interfaces of the device are distributed to different VRFs, performing the function of establishing multiple virtual route forwarding instances on the device. A virtual user-network interface, works as an action point to perform service classification and traffic control in HQoS. See virtual local area network 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). See voice over IP See virtual path identifier See virtual private LAN service See virtual private network See virtual route forward
virtual user-network interface VLAN voice over IP
VoIP VPI VPLS VPN VRF
C-32
Issue 03 (2011-04-10)
C Glossary
W
wait to restore WAN Web LCT weighted fair queuing The number of minutes to wait before services are switched back to the working line. See wide area network The local maintenance terminal of a transport network, which is located on the NE management layer of the transport network 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 synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio. weighted round Robin N/A WFQ wide area network See weighted fair queuing 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. A tool for fiber routing, which acts as the corrugated pipe. See weighted random early detection See weighted round Robin See wait to restore
winding pipe WRED WRR WTR
X
XPIC See cross polarization interference cancellation
Issue 03 (2011-04-10)
C-33

RTN 950 Configuration Guide (WebLCT) - (V100R003C00 - 03)

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

RTN 950 Configuration Guide (WebLCT) - (V100R003C00 - 03)

Enviado por

Direitos autorais:

Formatos disponíveis

OptiX RTN 950 Radio Transmission System V100R003C00

Configuration Guide (Web LCT)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

About This Document

About This Document

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

About This Document

Updates in Issue 03 (2011-04-10) Based on Product Version V100R003C00

A.11.6 Monitoring the Outdoor Cabinet

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

About This Document

Updates in Issue 02 (2011-01-20) Based on Product Version V100R003C00

Updates in Issue 01 (2010-12-30) Based on Product Version V100R003C00

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

4 Configuring the Network Topology.......................................................................................4-1

5 Configuring Radio Links..........................................................................................................5-1

6 Configuring TDM Services......................................................................................................6-1

7 Configuring Native Ethernet Services on the Packet Plane...............................................7-1

8 Configuring EoPDH-Based Ethernet Services.....................................................................8-1

9 Configuring MPLS Tunnels.....................................................................................................9-1

10 Configuring PWE3 Services.................................................................................................10-1

11 Configuring the Clock...........................................................................................................11-1

12 Configuring Auxiliary Ports and Functions......................................................................12-1

13 Adding and Modifying Configuration Data....................................................................13-1

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

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

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

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

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

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

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

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

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

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

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

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

1.1 Preparing Documents and Tools

1.2 Checking Configuration Conditions

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

2 Specifying the Configuration Procedure

Specifying the Configuration Procedure

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

2 Specifying the Configuration Procedure

Figure 2-1 Configuration flow chart (initial configuration)

Configuring the network topology

Configuring radio links

Configuring TDM services

Configuring Packet-Based Ethernet services Configuring EoPDH-Based Ethernet services

Configuring MPLS packet services

Configuring the clock

Configuring auxiliary ports and functions End Required Optional

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

2 Specifying the Configuration Procedure

Operation 7 Configuring Native Ethernet Services on the Packet Plane

8 Configuring EoPDH-Based Ethernet Services

Configuring MPLS packet services

9 Configuring MPLS Tunnels 10 Configuring PWE3 Services

11 Configuring the Clock 12 Configuring Auxiliary Ports and Functions

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