IDU 610620 Configuration Guide (T2000) - (V100R003 - 02) - VNM

OptiX RTN 600 Radio Transmission System V100R003
IDU 610/620 Configuration Guide (T2000)
Issue Date
02 2009-06-15
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
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:
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
OptiX RTN 600 Radio Transmission System IDU 610/620 Configuration Guide (T2000)
Contents
Contents
About This Document.....................................................................................................................1 1 Starting the T2000.......................................................................................................................1-1
1.1 Starting or Shutting Down the T2000.............................................................................................................1-2 1.1.1 Starting the Computer............................................................................................................................1-3 1.1.2 Starting the T2000 Server......................................................................................................................1-3 1.1.3 Viewing the T2000 Process Status.........................................................................................................1-4 1.1.4 Logging In to the T2000 Client..............................................................................................................1-4 1.1.5 Exiting a T2000 Client...........................................................................................................................1-5 1.1.6 Shutting Down the T2000 Server...........................................................................................................1-6 1.1.7 Shutting Down the Computer.................................................................................................................1-6 1.2 Entering the T2000 Common Views...............................................................................................................1-7 1.2.1 Opening the Main Topology..................................................................................................................1-7 1.2.2 Opening the NE Explorer.......................................................................................................................1-8
2 Topology Management.............................................................................................................2-1
2.1 Basic Concepts................................................................................................................................................2-2 2.1.1 Topology Management Functions..........................................................................................................2-2 2.1.2 Topology Objects...................................................................................................................................2-3 2.1.3 GNE and Non-Gateway NE...................................................................................................................2-3 2.1.4 Virtual NE..............................................................................................................................................2-3 2.1.5 Fiber Types.............................................................................................................................................2-4 2.2 Creating NEs...................................................................................................................................................2-4 2.2.1 Creating NEs by Using the Search Method...........................................................................................2-5 2.2.2 Creating NEs by Using the Manual Method..........................................................................................2-6 2.2.3 Creating Virtual NE...............................................................................................................................2-9 2.3 Configuring the NE Data...............................................................................................................................2-10 2.3.1 Uploading the NE Data........................................................................................................................2-10 2.3.2 Configuring the NE Data Manually.....................................................................................................2-11 2.4 Creating Fibers..............................................................................................................................................2-12 2.4.1 Creating Radio Links by Searching for the Radio Links.....................................................................2-12 2.4.2 Creating Radio Links by Filling the Link Table..................................................................................2-13 2.4.3 Creating SDH Fiber Links by Searching the SDH Fiber Links...........................................................2-14 2.4.4 Creating SDH Fiber Links by Filling the Link Table..........................................................................2-15 Issue 02 (2009-06-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
OptiX RTN 600 Radio Transmission System IDU 610/620 Configuration Guide (T2000) 2.4.5 Creating DCN Communication Cable..................................................................................................2-16
2.5 Creating a Topology Subnet..........................................................................................................................2-17 2.6 Adjusting Topology Objects.........................................................................................................................2-17 2.6.1 Balancing Load of the NE Explorer Process........................................................................................2-18 2.6.2 Modifying the NM Name.....................................................................................................................2-19 2.6.3 Modifying the NE Name......................................................................................................................2-20 2.6.4 Modifying the NE ID...........................................................................................................................2-20 2.6.5 Modifying the IP Address of an NE.....................................................................................................2-21 2.6.6 Adding Boards......................................................................................................................................2-22 2.6.7 Modifying Fiber/Cable Information.....................................................................................................2-23 2.6.8 Naming a Fiber/Cable..........................................................................................................................2-23 2.6.9 Copying Topology Objects..................................................................................................................2-24 2.6.10 Moving Topology Objects.................................................................................................................2-24 2.7 Deleting Topology Objects...........................................................................................................................2-25 2.7.1 Deleting Topology Subnets..................................................................................................................2-25 2.7.2 Deleting Fibers.....................................................................................................................................2-25 2.7.3 Deleting Boards....................................................................................................................................2-26 2.7.4 Deleting NEs........................................................................................................................................2-26
3 Configuring Radio Links on the Per-NE Basis.....................................................................3-1

3.1 Configuration Flow.........................................................................................................................................3-3 3.2 Creating IF 1+1 Protection..............................................................................................................................3-4 3.3 Creating an XPIC Workgroup.........................................................................................................................3-8 3.4 Configuring the IF/ODU Information of a Radio Link.................................................................................3-11 3.5 Configuring the Hybrid/AM Attribute..........................................................................................................3-16 3.6 Configuring the ATPC Function...................................................................................................................3-18 3.7 Creating an N+1 Protection Group................................................................................................................3-20 3.8 Creating REGs...............................................................................................................................................3-22
4 Configuring the MSP on the Per-NE Basis........................................................................... 4-1

4.1 Configuring the Ring MSP..............................................................................................................................4-2 4.2 Creating Linear MSP.......................................................................................................................................4-5
5 Configuring SDH/PDH Services on the Per-NE Basis........................................................5-1

5.1 Numbering Schemes for SDH Timeslots .......................................................................................................5-3 5.2 Creating Cross-Connections of Point-to-Point Services ................................................................................5-4 5.3 Creating Cross-Connections for SNCP Services............................................................................................5-7 5.4 Setting the Automatic Switching Conditions of SNCP Services..................................................................5-11 5.5 Deleting the Cross-Connections of a Point-to-Point Service........................................................................5-13 5.6 Deleting the Cross-Connections of a Service................................................................................................5-14 5.7 Converting Normal Services into SNCP Services........................................................................................5-15 5.8 Converting SNCP Services into Normal Services........................................................................................5-19
6 Configuring the Clock on the Per-NE Basis..........................................................................6-1

6.1 Clock Synchronization Scheme......................................................................................................................6-2 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-06-15)
Contents
6.2 Configuring the Clock Sources.......................................................................................................................6-7 6.3 Configuring Protection for Clock Sources .....................................................................................................6-9 6.4 Modifying the Parameters of the External Clock Output..............................................................................6-12 6.5 Customizing the Clock Parameters...............................................................................................................6-14
7 Configuring SDH/PDH Microwave-Based Ethernet Services on the Per-NE Basis ...........................................................................................................................................................7-1

7.1 Configuration Flow.........................................................................................................................................7-3 7.1.1 Configuring Point-to-Point EPL Services..............................................................................................7-3 7.1.2 Configuring PORT-Shared EVPL Services...........................................................................................7-4 7.1.3 Configuring VCTRUNK-Shared EVPL Services..................................................................................7-5 7.1.4 Configuring QinQ-Based EVPL Services .............................................................................................7-5 7.1.5 Configuring 802.1d Bridge-Based EPLAN Services.............................................................................7-5 7.1.6 Configuring 802.1q Bridge-Based EVPLAN Services..........................................................................7-6 7.1.7 Configuring 802.1ad Bridge-Based EVPLAN Services........................................................................7-7 7.2 Configuration Example (Point-to-Point EPL Services)..................................................................................7-7 7.2.1 Networking Diagram..............................................................................................................................7-8 7.2.2 Service Planning.....................................................................................................................................7-8 7.2.3 Configuring NE1..................................................................................................................................7-10 7.2.4 Configuring NE2..................................................................................................................................7-14 7.3 Configuration Example (PORT-Shared EVPL Services).............................................................................7-14 7.3.1 Networking Diagram............................................................................................................................7-14 7.3.2 Service Planning...................................................................................................................................7-15 7.3.3 Configuring NE1..................................................................................................................................7-18 7.3.4 Configuring NE2 and NE3...................................................................................................................7-23 7.4 Configuration Example (VCTRUNK-Shared EVPL Services)....................................................................7-23 7.4.1 Networking Diagram............................................................................................................................7-24 7.4.2 Service Planning...................................................................................................................................7-24 7.4.3 Configuring NE1..................................................................................................................................7-27 7.4.4 Configuring NE2..................................................................................................................................7-32 7.5 Configuration Example (802.1d Bridge-Based EPLAN Services)...............................................................7-32 7.5.1 Networking Diagram............................................................................................................................7-32 7.5.2 Service Planning...................................................................................................................................7-33 7.5.3 Configuring NE1..................................................................................................................................7-36 7.5.4 Configuring NE2 and NE3...................................................................................................................7-41 7.6 Configuration Example (802.1q Bridge-Based EVPLAN Services)............................................................7-41 7.6.1 Networking Diagram............................................................................................................................7-41 7.6.2 Service Planning...................................................................................................................................7-42 7.6.3 Configuring NE1..................................................................................................................................7-46 7.6.4 Configuring NE2 and NE3...................................................................................................................7-54
8 Configuring Hybrid Microwave-Based Ethernet Services on the Per-NE Basis...........8-1

8.1 Configuration Flows........................................................................................................................................8-2 8.1.1 Configuration Flow (Ethernet Services Accessed Through the EMS6 Board)......................................8-2 Issue 02 (2009-06-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
OptiX RTN 600 Radio Transmission System IDU 610/620 Configuration Guide (T2000) 8.1.2 Configuration Flow (Ethernet Services Accessed Through the IFH2 Board)........................................8-4
8.2 Configuration Example...................................................................................................................................8-4 8.2.1 Networking Diagram..............................................................................................................................8-5 8.2.2 Service Planning (Ethernet Services Accessed Through the EMS6 Board)..........................................8-6 8.2.3 Service Planning (Ethernet Services Accessed Through the IFH2 Board)..........................................8-10 8.2.4 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board)........................................8-11 8.2.5 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board)........................................8-20 8.2.6 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board).........................................8-29 8.2.7 Configuring NE3..................................................................................................................................8-31
9 Task Collection (Configuring Ethernet Services)................................................................9-1

9.1 Configuring Ethernet Ports..............................................................................................................................9-2 9.1.1 Configuring External Ethernet Ports......................................................................................................9-2 9.1.2 Configuring the Internal Port of the Ethernet Board..............................................................................9-9 9.1.3 Modifying the Type Field of Jumbo Frames........................................................................................9-17 9.1.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth........................................................9-17 9.2 Creating Ethernet Services............................................................................................................................9-19 9.2.1 Creating Ethernet Line Service............................................................................................................9-19 9.2.2 Creating the Ethernet LAN Service......................................................................................................9-24 9.2.3 Modifying the Mounted Port of a Bridge.............................................................................................9-29 9.2.4 Creating the VLAN Filter Table..........................................................................................................9-31 9.2.5 Deleting an Ethernet Private Line Service...........................................................................................9-33 9.2.6 Deleting an Ethernet LAN Service.......................................................................................................9-33 9.3 Configuring the Cross-Connections of Ethernet Services.............................................................................9-34 9.3.1 Creating Cross-Connections of Ethernet Services...............................................................................9-35 9.3.2 Deleting the Cross-Connections of an Ethernet Service......................................................................9-35 9.4 Configuring the QoS.....................................................................................................................................9-36 9.4.1 Creating a Flow....................................................................................................................................9-37 9.4.2 Creating the CAR.................................................................................................................................9-39 9.4.3 Creating the CoS..................................................................................................................................9-42 9.4.4 Binding the CAR/CoS..........................................................................................................................9-44 9.4.5 Configuring the Traffic Shaping..........................................................................................................9-45 9.4.6 Configuring the CoS of the IFH2 Board..............................................................................................9-47 9.4.7 Modifying CAR Parameters.................................................................................................................9-48 9.4.8 Modifying CoS Parameters..................................................................................................................9-49 9.5 Creating a LAG.............................................................................................................................................9-50 9.6 Configuring the Layer 2 Switching Feature..................................................................................................9-58 9.6.1 Creating the Entry of a MAC Address Table Manually ......................................................................9-59 9.6.2 Modifying the Aging Time of the MAC Address Table Entry............................................................9-60 9.6.3 Configuring the Spanning Tree Protocol ............................................................................................9-62 9.6.4 Configuring the IGMP Snooping Protocol...........................................................................................9-66 9.6.5 Modifying the Aging Time of the Multicast Table Item......................................................................9-68 9.6.6 Configuring the Broadcast Packet Suppression Function....................................................................9-69 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-06-15)
Contents
9.7 LPT Configuration........................................................................................................................................9-70
10 Configuring the Orderwire and Auxiliary Interfaces.....................................................10-1

10.1 Configuring the Orderwire..........................................................................................................................10-3 10.2 Configuring Synchronous Data Services....................................................................................................10-6 10.3 Configuring Asynchronous Data Services..................................................................................................10-8 10.4 Configuring External Alarms....................................................................................................................10-10 10.5 Configuration Example (Synchronous Data Services)..............................................................................10-13 10.5.1 Networking Diagram........................................................................................................................10-13 10.5.2 Service Planning...............................................................................................................................10-14 10.5.3 Configuration Process......................................................................................................................10-15 10.6 Configuration Example (Asynchronous Data Services)...........................................................................10-16 10.6.1 Networking Diagram........................................................................................................................10-16 10.6.2 Service Planning...............................................................................................................................10-17 10.6.3 Configuration Process......................................................................................................................10-18 10.7 Configuration Example (External Alarms)...............................................................................................10-20 10.7.1 Networking Diagram........................................................................................................................10-20 10.7.2 Service Planning...............................................................................................................................10-21 10.7.3 Configuration Process......................................................................................................................10-21
11 Configuring the Parameters of Various Ports ..................................................................11-1

11.1 Configuring the Parameters of SDH Interfaces ..........................................................................................11-2 11.2 Configuring the Parameters of PDH Interfaces ..........................................................................................11-3 11.3 Setting the Parameters of IF Ports...............................................................................................................11-6 11.4 Setting the Parameters of ODU Ports........................................................................................................11-11
12 Configuring Overhead Bytes...............................................................................................12-1

12.1 Configuring the IEEE 1588 Overhead........................................................................................................12-2 12.2 Configuring RSOHs....................................................................................................................................12-2 12.3 Configuring VC-4 POHs.............................................................................................................................12-4 12.4 Configuring VC-3 POHs.............................................................................................................................12-8 12.5 Configuring VC-12 POHs.........................................................................................................................12-10
13 Adding and Modifying the Configuration Data..............................................................13-1

13.1 Task Collection (Configuring SDH/PDH Services)....................................................................................13-2 13.2 Task Collection (Configuring Ethernet Services).......................................................................................13-7
A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1
Issue 02 (2009-06-15)
Figures
Figures
Figure 5-1 Numbering VC-12 timeslots by order................................................................................................5-3 Figure 5-2 Numbering VC-12 timeslots in the interleaved scheme ....................................................................5-4 Figure 6-1 Clock synchronization scheme for a chain network...........................................................................6-3 Figure 6-2 Clock synchronization scheme for a tree network..............................................................................6-4 Figure 6-3 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line) ...............................................................................................................................................................................6-5 Figure 6-4 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line) ...............................................................................................................................................................................6-6 Figure 6-5 Clock synchronization scheme for networking with convergence at tributary ports.........................6-7 Figure 7-1 Networking diagram...........................................................................................................................7-8 Figure 7-2 IDU board configuration ...................................................................................................................7-8 Figure 7-3 Configuring Ethernet services............................................................................................................7-9 Figure 7-4 Timeslot allocation of Ethernet services...........................................................................................7-10 Figure 7-5 Networking diagram.........................................................................................................................7-15 Figure 7-6 IDU board configuration (NE1)........................................................................................................7-15 Figure 7-7 IDU board configuration (NE2 and NE3)........................................................................................7-16 Figure 7-8 Configuring Ethernet services..........................................................................................................7-16 Figure 7-9 Timeslot allocation of Ethernet services...........................................................................................7-17 Figure 7-10 Networking diagram.......................................................................................................................7-24 Figure 7-11 IDU board configuration (NE1 and NE2)......................................................................................7-25 Figure 7-12 Configuring Ethernet services........................................................................................................7-25 Figure 7-13 Timeslot allocation of Ethernet services.........................................................................................7-27 Figure 7-14 Networking diagram.......................................................................................................................7-33 Figure 7-15 IDU board configuration (NE1)......................................................................................................7-33 Figure 7-16 IDU board configuration (NE2 and NE3)......................................................................................7-34 Figure 7-17 Configuring Ethernet services........................................................................................................7-34 Figure 7-18 Timeslot allocation of Ethernet services.........................................................................................7-35 Figure 7-19 Networking diagram.......................................................................................................................7-42 Figure 7-20 IDU board configuration (NE1)......................................................................................................7-42 Figure 7-21 IDU board configuration (NE2 and NE3)......................................................................................7-43 Figure 7-22 Configuring Ethernet services........................................................................................................7-43 Figure 7-23 Timeslot allocation of Ethernet services.........................................................................................7-45 Figure 8-1 Networking diagram...........................................................................................................................8-6 Figure 8-2 Configuration information of Ethernet parameters.............................................................................8-6 Issue 02 (2009-06-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Figures
OptiX RTN 600 Radio Transmission System IDU 610/620 Configuration Guide (T2000) Figure 8-3 Configuration diagram of the Ethernet services between NE2 and NE3.........................................8-10 Figure 10-1 Networking diagram.....................................................................................................................10-14 Figure 10-2 Timeslot allocation of synchronous data services........................................................................10-14
Figure 10-3 Networking diagram.....................................................................................................................10-17 Figure 10-4 Timeslot allocation diagram ........................................................................................................10-18 Figure 10-5 Networking diagram.....................................................................................................................10-21
viii
Issue 02 (2009-06-15)
Tables
Tables
Table 3-1 Configuring SDH/PDH radio links......................................................................................................3-3 Table 3-2 Configuring a Hybrid radio link...........................................................................................................3-4 Table 6-1 Navigation path for customizing the clock parameters......................................................................6-14 Table 7-1 Flow for configuring point-to-point EPL services by using Ethernet switching boards......................7-3 Table 7-2 Flow for configuring PORT-shared EVPL services............................................................................ 7-4 Table 7-3 Flow for configuring VCTRUNK-shared EVPL services...................................................................7-5 Table 7-4 Flow for configuring 802.1d bridge-based EPLAN services...............................................................7-6 Table 7-5 Flow for configuring 802.1q bridge-based EVPLAN services............................................................7-6 Table 7-6 Parameters of external Ethernet ports.................................................................................................. 7-9 Table 7-7 Parameters of internal Ethernet ports...................................................................................................7-9 Table 7-8 Parameters of external Ethernet ports................................................................................................7-16 Table 7-9 Parameters of internal Ethernet ports.................................................................................................7-17 Table 7-10 Parameters of EPL services..............................................................................................................7-17 Table 7-11 Parameters of external Ethernet ports..............................................................................................7-25 Table 7-12 Parameters of internal Ethernet ports...............................................................................................7-26 Table 7-13 Parameters of EPL services..............................................................................................................7-26 Table 7-14 Parameters of external Ethernet ports..............................................................................................7-34 Table 7-15 Parameters of internal Ethernet ports...............................................................................................7-34 Table 7-16 Parameters of Ethernet LAN services..............................................................................................7-35 Table 7-17 Parameters of external Ethernet ports..............................................................................................7-43 Table 7-18 Parameters of internal Ethernet ports...............................................................................................7-44 Table 7-19 Parameters of Ethernet LAN services..............................................................................................7-45 Table 8-1 Flow for configuring the Ethernet services accessed through the EMS6 board.................................. 8-2 Table 8-2 Flow for configuring the Ethernet services accessed through the IFH2 board....................................8-4 Table 8-3 Parameters of external ports of the EMS6 board................................................................................. 8-7 Table 8-4 Parameters of external ports of the IFH2 board...................................................................................8-7 Table 8-5 Parameters of Ethernet private line services (NE1).............................................................................8-7 Table 8-6 Parameters of Ethernet private line services (NE2).............................................................................8-8 Table 8-7 Flow configuration...............................................................................................................................8-8 Table 8-8 Parameters of the CARa.......................................................................................................................8-9 Table 8-9 Parameters of the CoS..........................................................................................................................8-9 Table 8-10 Parameters of the link aggregation group........................................................................................8-10 Table 8-11 Parameters of external Ethernet ports..............................................................................................8-11 Issue 02 (2009-06-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Tables
OptiX RTN 600 Radio Transmission System IDU 610/620 Configuration Guide (T2000) Table 8-12 Parameters of the CoS of the IFH2 board (NE2).............................................................................8-11 Table 8-13 Parameters of Ethernet services (NE3)............................................................................................8-11 Table 9-1 Methods used by ports to process data frames.....................................................................................9-8 Table 9-2 Methods used by ports to process data frames...................................................................................9-16 Table 9-3 Parameter of the Point-to-Point LPT..................................................................................................9-72 Table 9-4 Parameter of the Point-to-Multipoint LPT.........................................................................................9-73 Table 10-1 Configuration of the synchronous data port...................................................................................10-14 Table 10-2 Configuration of the asynchronous data services...........................................................................10-17 Table 10-3 Configuration of the external alarms..............................................................................................10-21 Table 13-1 Task collection (NE attributes)........................................................................................................13-2 Table 13-2 Task collection (radio link)..............................................................................................................13-3 Table 13-3 Task collection (services).................................................................................................................13-5 Table 13-4 Task collection (clock).....................................................................................................................13-6 Table 13-5 Task collection (orderwire)..............................................................................................................13-7 Table 13-6 Task collection (Ethernet services transmitted on the SDH microwave).........................................13-7 Table 13-7 Task collection (Ethernet services transmitted on the Hybrid microwave).....................................13-9
Issue 02 (2009-06-15)
About This Document
About This Document
Purpose
This document uses examples to describe the entire process of the initial configuration of the OptiX RTN 600 that adopts the IDU 610/620 by using the T2000. It can help the readers to easily grasp the method for configuring the OptiX RTN 600 and thus to complete all the actual configuration tasks.
Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 600 OptiX iManager T2000 Version V100R003 V200R007C03
Intended Audience
The intended audiences of this document are:
l l
Installation/Commissioning engineers Data configuration engineers
Before reading this document, you should be familiar with the following information:
l l l
Radio communication basics, especially the basics of network planning Basic functions and slots that are configured to house the boards of the OptiX RTN 600 Basic operations of the T2000
Issue 02 (2009-06-15)
About This Document
Organization
This document is organized as follows. Topic 1 Starting the T2000 2 Topology Management Description This topic describes how to use the quick start of the T2000 to know basic operations on the T2000. This topic describes how to manage NEs and optical fibers/ cables through the T2000 after creating their topologies on the T2000.
3 Configuring Radio Links This topic describes how to configure the radio link on an NE. on the Per-NE Basis 4 Configuring the MSP on the Per-NE Basis 5 Configuring SDH/PDH Services on the Per-NE Basis 6 Configuring the Clock on the Per-NE Basis 7 Configuring SDH/PDH Microwave-Based Ethernet Services on the Per-NE Basis 8 Configuring Hybrid Microwave-Based Ethernet Services on the Per-NE Basis 9 Task Collection (Configuring Ethernet Services) 10 Configuring the Orderwire and Auxiliary Interfaces 11 Configuring the Parameters of Various Ports 12 Configuring Overhead Bytes 13 Adding and Modifying the Configuration Data A Glossary This topic describes how to configure the MSP on an NE. This topic describes how to configure the SDH/PDH service on an NE. This topic describes how to configure the clock on an NE. This topic describes how to configure the Ethernet service based on the SDH/PDH microwave on an NE.
This topic describes how to configure the Ethernet service based on the hybrid microwave on an NE.
This topic describes common Ethernet configuration tasks.
This topic describes how to configure the orderwire and auxiliary interfaces. This topic describes how to configure the interface parameters of the board. This topic describes how to configure the overhead byte. This topic describes how to supplement and adjust the initially configured data in the equipment commissioning and operating stage. This topic lists the terms used in this document.
Issue 02 (2009-06-15)
About This Document
Topic B Acronyms and Abbreviations
Description This topic lists the acronyms and abbreviations used in this document.
Conventions
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. 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.
General Conventions
The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Issue 02 (2009-06-15)
About This Document
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, windows, 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.
Mouse Operation
The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made to previous issues.
Updates in Issue 02 (2009-06-15)

Second formal release. Known defects are fixed. The configuration of the 1588 clock overhead byte is described.
Updates in Issue 01 (2009-04-25)

Initial formal release.
Issue 02 (2009-06-15)
1 Starting the T2000
1
About This Chapter
Starting the T2000
The following pages introduces some preparation operations that will ensure a smooth, troublefree launch of the T2000. 1.1 Starting or Shutting Down the T2000 The T2000 uses the standard client/server architecture and multiple-user mode. So, you are recommended to start or shut down the T2000 by strictly observing the following procedure, in order not to affect other users that are operating the T2000. 1.2 Entering the T2000 Common Views The T2000 common views include Main Topology and NE Explorer. You can use these views to manage the topology, equipment.
Issue 02 (2009-06-15)
1-1
1.1 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multiple-user mode. So, you are recommended to start or shut down the T2000 by strictly observing the following procedure, in order not to affect other users that are operating the T2000.
Context
l
Start the computer and the T2000 application in the following steps: 1. 2. 3. Start the computer. Start the T2000 server. Start the T2000 client. Exit the T2000 client. Stop the T2000 server. Shut down the computer.
Shut down the T2000 application and the computer in the following steps: 1. 2. 3.
1.1.1 Starting the Computer To avoid computer damage or data loss, refer to the procedure provided to start the computer. The startup procedures of the workstation are different from those of a normal PC. Follow the correct procedure to perform the operations as required. 1.1.2 Starting the T2000 Server After starting the computer, you need to start the T2000 server. Then you can log in to the T2000 to manage the network. 1.1.3 Viewing the T2000 Process Status When you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use the System Monitor to view the T2000 process status to decide whether the server is faulty. 1.1.4 Logging In to the T2000 Client You can manage the network in the graphic user interface (GUI) only after logging in to the T2000 client. 1.1.5 Exiting a T2000 Client Before restarting the T2000 client or shutting down the T2000 server, you must exit the T2000 client. 1.1.6 Shutting Down the T2000 Server When the T2000 server is managing the system normally, do not perform this operation. In special circumstances, for example, when modifying the system time of the computer where the T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut down the T2000 server. 1.1.7 Shutting Down the Computer Normally, do not shut down the computer. In special situations, for example, when the computer becomes faulty, shut down the computer in the correct sequence. The shutdown procedures of the workstation are different from those of a normal PC. Follow the correct procedure to perform the operations as required.
1-2
Issue 02 (2009-06-15)
1.1.1 Starting the Computer

To avoid computer damage or data loss, refer to the procedure provided to start the computer. The startup procedures of the workstation are different from those of a normal PC. Follow the correct procedure to perform the operations as required.
Prerequisite
l l
The T2000 must be installed correctly. The power cable of the workstation or the computer, the power cable of the monitor, data line and Ethernet line must be connected correctly. If there is printer, modem or other peripherals, their power line and data line must be connected correctly.
Background Information
The T2000 can run in the UNIX or Windows operating system. The functions are the same in each operating system. To learn about the recommended hardware configuration, refer to the OptiX iManager T2000 Product Description.
Procedure
l On UNIX 1. 2. 3. 4. l 1. 2. 3. 4. ----End Power on the printer, modem and other peripherals. Power on the workstation and the Solaris is automatically started. The Prompt dialog box is displayed. Enter the Username and the Password in the Login dialog box. For example, User: t2000 (by default); Password: t2000 (by default). Click OK to open the Common Desktop Environment (CDE) window. Power on the printer, modem and other peripherals. Power on the computer and the Windows is automatically started. Enter the Username and the Password in the Login dialog box. For example, User: t2000 (by default); Password: t2000 (by default). Click OK to open the Windows user interface.
On Windows
1.1.2 Starting the T2000 Server

After starting the computer, you need to start the T2000 server. Then you can log in to the T2000 to manage the network.
Prerequisite
l l l l
The computer where the T2000 is installed must be started correctly. The operating system of the T2000 server must be running correctly. The T2000 license must be in the server directory. The SQL Server must be started and work normally.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
Issue 02 (2009-06-15)
Procedure
Step 1 Double-click the T2000Server icon on the desktop of the T2000 server. Step 2 In the Login dialog box, enterUser Name, Password and Server. For example, User Name: admin, Password: T2000 (T2000 is the default password of the admin user.) and Server: Local.
NOTE
Periodically change the password and memorize it.
Step 3 Click Login to display the System Monitor window. Wait until the core processes (including Ems Server, Schedulesrv Server, Security Server, Syslog Agent, Topo Server, WebLCT Server, Tomcat Service, Client Upgrader and Toolkit Server) and Database Server Process are in the Running state. Now the T2000 server is started successfully. Step 4 Optional: When needed, you can also start the Northbound Interface precesses (including Northbound Interface Module(iPASSAgent) Process, Northbound Interface Module (SNMP) Process, Naming Service, Notify Service and itnotify) manually. Step 5 Optional: If the System Monitor is started, you need use it to restart the T2000 server when needed. Choose System > Start Server on the Main Menu of the System Monitor. When the core processes and Database Server Process processes are in the Running state, the T2000 server is started properly. ----End
1.1.3 Viewing the T2000 Process Status

When you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use the System Monitor to view the T2000 process status to decide whether the server is faulty.
To view the status of the T2000 processes by UNIX command line, run the following command:
# /T2000/server/bin/showt2000server
If each process entered has a corresponding process ID and the specific ID does not change, the T2000 processes are normal.
Procedure
Step 1 In the System Monitor, click the Process tab. View the status of T2000 core processes (including Ems Server, Schedulesrv Server, Security Server, Syslog Agent, Topo Server, WebLCT Server, Tomcat Service, Client Upgrader and Toolkit Server), Database Server Process and Northbound Interface processes (including Northbound Interface Module(iPASSAgent) Process, Northbound Interface Module(SNMP) Process, Naming Service, Notify Service and itnotify). All the processes should be in the Running state. ----End
1.1.4 Logging In to the T2000 Client

You can manage the network in the graphic user interface (GUI) only after logging in to the T2000 client.
1-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-06-15)
Prerequisite
The T2000 server must be started correctly.
Procedure
Step 1 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop. Step 2 Enter the User Name, Password of the T2000 client. For example, User Name: admin; Password: T2000.
NOTE
l l
By default, the initial user name is admin, and the password is T2000. To protect the T2000 from unauthorized logins, you need to immediately change this password. The administrator needs to create new T2000 users and assign them to certain authority groups.
Step 3 Optional: Set the server parameters. 1. 2. 3. Click to display the Setting dialog box.
Click New to display another Setting dialog box. In the Setting dialog box, specify the IP Address, Mode and Server Name.
NOTE
l l l
The IP address is the IP address used by the T2000 server. The Mode has two options including Common and Security (SSL). When you choose the Security (SSL) mode, the communication between the client and the server is encrypted. The communication mode of the client must be consistent with that of the server. Otherwise, the client cannot log in to the server. To view the communication mode of the server, choose System > Communication Security Setting on the Main Menu of the System Monitor client. You need not enter the Port number. After the Mode is specified, the system selects a Port number automatically.
4. 5.
Click OK to complete adding a server. Click OK to complete the server settings.
Step 4 Select a server and click Login to access the T2000. ----End
1.1.5 Exiting a T2000 Client

Before restarting the T2000 client or shutting down the T2000 server, you must exit the T2000 client.
Prerequisite
The T2000 client must be started normally.
Procedure
Step 1 Choose File > Exit from the Main Menu. Step 2 Click OK in the confirmation dialog box.
Issue 02 (2009-06-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-5

NOTE
If the layout of the view is changed and not saved, the Confirm dialog box appears asking you whether to save the changes. After you confirm the dialog box, automatically exit the client.
----End
1.1.6 Shutting Down the T2000 Server

When the T2000 server is managing the system normally, do not perform this operation. In special circumstances, for example, when modifying the system time of the computer where the T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut down the T2000 server.
Prerequisite
All the T2000 clients connected to the T2000 server must be shut down.
Context
When performing the operations related to the database (such as initializing the T2000 database, restoring T2000 databases and restoring T2000 MO data) or the operations related to the T2000 (such as the upgrade, installing patches and re-installing the T2000), you need to shut down the T2000 server first. You are recommended to shut down the T2000 server in the way of shutting down the T2000 server and the System Monitor Client.
Procedure
l Shut down the T2000 server and the System Monitor.
NOTE
After shutdown, you can perform the operations related to the database (such as initializing the T2000 database, restoring T2000 databases and restoring T2000 MO data) or the operations related to the T2000 (such as the upgrade, installing patches and re-installing the T2000).
1. l
In the System Monitor, choose System > Shutdown System from the Main Menu.
NOTE
Shut down the T2000 server only.

After shutdown, you cannot perform the operations related to the database (such as initializing the T2000 database, restoring T2000 databases and restoring T2000 MO data) or the operations related to the T2000 (such as the upgrade, installing patches and re-installing the T2000).
1. 2. ----End
In the System Monitor, choose System > Stop Server from the Main Menu. Click OK in the confirmation dialog box. When all the processes are in the Stopped status, theT2000server is stopped normally.
1.1.7 Shutting Down the Computer

Normally, do not shut down the computer. In special situations, for example, when the computer becomes faulty, shut down the computer in the correct sequence. The shutdown procedures of the workstation are different from those of a normal PC. Follow the correct procedure to perform the operations as required.
Prerequisite
The T2000 server and client applications must be stopped.
Precaution
CAUTION
To avoid equipment damages or data loss, perform the following step one by one to shut down the workstation.
Procedure
l On UNIX platform 1. Enter the following commands in the terminal window, the UNIX workstation shuts down automatically:
% su root Password: rootkit # sync;sync;sync;sync;sync # shutdown -y -g0 -i5
NOTE
l l
rootkit is the default password of super user root. If the password is changed, enter the new password. To restart the Sun workstation, the last command is # shutdown -y -g0 -i6.
2. l 1. 2. 3. ----End
Turn off the monitor and the peripheral equipment. Choose Start > Shut down from the Windows desktop. Choose Shut down and click OK in the dialog box. The computer shuts down automatically. Turn off the monitor and the peripheral equipment.
On Windows platform
1.2 Entering the T2000 Common Views

The T2000 common views include Main Topology and NE Explorer. You can use these views to manage the topology, equipment. 1.2.1 Opening the Main Topology After opening the Main Topology, you can manage the network topology, for example, creating a topology object, creating a subnet, and locking the position of an NE icon in the topology. 1.2.2 Opening the NE Explorer The NE Explorer is the key interface for the T2000 to configure a single station. After opening the NE Explorer, you can configure, manage and maintain each NE, board or port in a hierarchical manner.
1.2.1 Opening the Main Topology

After opening the Main Topology, you can manage the network topology, for example, creating a topology object, creating a subnet, and locking the position of an NE icon in the topology.
Prerequisite
You must be an NM user with "NE and network monitor" authority or higher.
Procedure
l l To open the Main Topology, log in to the T2000. Choose Window > Main Topology from the Main Menu.
----End
1.2.2 Opening the NE Explorer

The NE Explorer is the key interface for the T2000 to configure a single station. After opening the NE Explorer, you can configure, manage and maintain each NE, board or port in a hierarchical manner.
Prerequisite
You must be an NM user with "NE and network monitor" authority or higher.
You can open a maximum of five NE Explorer windows at the same time.
Procedure
l Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu. ----End
1-8
Issue 02 (2009-06-15)
2 Topology Management
2
About This Chapter
Topology Management
You can manage NEs and fibers through the T2000 after creating their topologies on the T2000. 2.1 Basic Concepts Topology structure helps you to learn the layout of the entire network, and the networking and running information of the equipment. An understanding of basic topology concepts facilitates the topology management. 2.2 Creating NEs Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual equipment, you need to create the corresponding NEs on the T2000. There are two methods of creating NEs: creating a single NE and creating NEs in batches. When you need to create a large number of NEs, for example, during deployment, it is recommended that you create NEs in batches. When you need to create only a few NEs, it is recommended that you create the NEs one by one. 2.3 Configuring the NE Data Though an NE is successfully created, it is not configured. You need to configure the NE first so that the T2000 can manage and operate the NE. 2.4 Creating Fibers To implement the end-to-end service management on the NMS, you need to create the fibers first. 2.5 Creating a Topology Subnet The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet. 2.6 Adjusting Topology Objects You can modify the settings when creating the network topology by using the T2000. For example, adjust the optical NE source, modify the status of the preconfigured NE and so on. 2.7 Deleting Topology Objects When adjusting the network topology, generally, you need to delete some objects of the topology.
Issue 02 (2009-06-15)
2-1
2.1 Basic Concepts

Topology structure helps you to learn the layout of the entire network, and the networking and running information of the equipment. An understanding of basic topology concepts facilitates the topology management. 2.1.1 Topology Management Functions By topology management, you can set up and manage the entire network topology to present the networking and the status of the devices. You can browse the topology view to know and monitor the entire network status in real time. 2.1.2 Topology Objects Topology object refers to an operation object corresponding to the physical equipment. If you want to manage an NE, board, or fiber/cable on the T2000, you must first create its topology. 2.1.3 GNE and Non-Gateway NE The T2000 communicates with the NEs through the network to manage the network equipment. This type of NE that communicates directly with the T2000 through the network is called gateway NE (GNE). The other NEs that communicate with the T2000 through the GNE are called non-gateway NEs. 2.1.4 Virtual NE An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the T2000. Virtual NEs represent the topological relations between the equipment that the T2000 manages directly and the equipment the T2000 manages indirectly on the topology. If the equipment that is not managed by the T2000 exists in the network and there are trails created on the equipment, you can create a virtual NE on the T2000 to represent the equipment. 2.1.5 Fiber Types You can use the T2000 to manage fibers, radio links, Ethernet cables, DCN communication cables, and virtual fiber/cable in a centralized manner.
2.1.1 Topology Management Functions

By topology management, you can set up and manage the entire network topology to present the networking and the status of the devices. You can browse the topology view to know and monitor the entire network status in real time. Topology management allows you to perform the following operations:
l l l l l
Customize the view. You can define and organize different views as required. Add, delete, modify, cut, or paste subnets. Add, delete, modify, copy, paste, or cut topology nodes. Adjust the size of a topology view for convenient viewing. Set the background. You can obtain the location information on a device node through the location of the corresponding icon in the background. Search for a topology object globally to help the user identify the topology object. Present topology object types with different icons. For example, small icons are used to indicate the topology object status, such as the link status. Switch between views quickly through the navigation tree.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-06-15)
l l
2-2
l
Manage the topology with the auxiliary tools such as the aerial view, print, and filter.
2.1.2 Topology Objects

Topology object refers to an operation object corresponding to the physical equipment. If you want to manage an NE, board, or fiber/cable on the T2000, you must first create its topology. By creating topologies, the T2000 sets up the communication with physical equipment in the network. When the NE data are uploaded to the T2000, the topology in the T2000 has the same data as the physical equipment. After that, the NE and board configuration on the T2000 are directly sent to physical NEs. The T2000 is able to manage the following topologies, which are NE, board, port, channel, fiber, virtual fiber, microwave link, subnet, Ethernet cable, serial port cable, and extended ECC. Based on all these topologies, the T2000 can query the data or working status of corresponding objects in the physical network. The subnet, Ethernet cable and serial port cable are only logical concepts on the T2000, and cannot be managed physically through their topologies.
2.1.3 GNE and Non-Gateway NE

The T2000 communicates with the NEs through the network to manage the network equipment. This type of NE that communicates directly with the T2000 through the network is called gateway NE (GNE). The other NEs that communicate with the T2000 through the GNE are called non-gateway NEs.
GNE
The GNE communicates with the T2000 by using the communication protocol. The T2000 manages the network through GNEs. Each T2000 must connect to at least one GNE.
Non-gateway NE
The non-gateway NE communicates with the GNE by using the ECC or the extended ECC. The recommended number of non-gateway NEs (including non-gateway NEs that connects to the GNE by using the extended ECC) that connect to each GNE is fewer than 50. Do not connect more than 60 non-gateway NEs to a GNE.
NOTE
If the number of non-gateway NEs that connect to a GNE is more than 50, an alarm is reported on the T2000.
2.1.4 Virtual NE
An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the T2000. Virtual NEs represent the topological relations between the equipment that the T2000 manages directly and the equipment the T2000 manages indirectly on the topology. If the equipment that is not managed by the T2000 exists in the network and there are trails created on the equipment, you can create a virtual NE on the T2000 to represent the equipment. Different from actual NEs, a virtual NE does not need to be hardware-specific. It can be used to represent any unknown equipment. On the T2000, it is usually used to simulate the equipment that cannot be directly managed by the T2000, for example, the equipment that is not managed by the T2000, such as the third-party equipment.
You can configure boards for a virtual NE on the T2000. The process of creating and deleting a virtual NE is similar to that of an actual NE. Virtual NEs are not restricted by the license. The license does not define the maximum number of virtual NEs on the T2000. The concept of virtual NE just for the SDH equipment.
2.1.5 Fiber Types

You can use the T2000 to manage fibers, radio links, Ethernet cables, DCN communication cables, and virtual fiber/cable in a centralized manner.
Fiber
A fiber is used to connect the optical interfaces between different equipment and to provide a transmission channel at the physical layer for service signals. According to the physical feature of a fiber, the T2000 classifies the fiber as four types, which are G.652, G.653, G.654, and G. 655 fibers.
Radio Link
A radio link uses the microwave to connect different outdoor units of radio equipment.
Ethernet Cable
The Ethernet cable that the T2000 can manage is used to connect the communication interface of the gateway NE and the T2000 server.
DCN Communication Cable

A DCN communication cable is used to connect communication interfaces of different equipment and to provide an extra transmission channel at the physical layer for the management information.
Virtual Fiber/Cable
Virtual fiber/cable is a logical concept. It may contains several physical fibers, radio links, or even one or more complete networks.
2.2 Creating NEs

Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual equipment, you need to create the corresponding NEs on the T2000. There are two methods of creating NEs: creating a single NE and creating NEs in batches. When you need to create a large number of NEs, for example, during deployment, it is recommended that you create NEs in batches. When you need to create only a few NEs, it is recommended that you create the NEs one by one. 2.2.1 Creating NEs by Using the Search Method The T2000 can search 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 address. In
addition, the T2000 can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable. 2.2.2 Creating NEs by Using the Manual Method You can only create NEs one by one through the manual method. The manual method, unlike the search method, does not allow creating NEs in batches. 2.2.3 Creating Virtual NE To display the topological relations between the equipment that is directly managed by the T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform manner.
2.2.1 Creating NEs by Using the Search Method

The T2000 can search 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 address. In addition, the T2000 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 user must log in to the T2000. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The NE to be created must have normal communication with the T2000.
Procedure
Step 1 Choose File > Search for NE from the Main Menu. Step 2 Optional: Add a search domain. 1. 2. Click Add. The system displays the Input Search Domain dialog box. Select an address type and enter the search address.
Issue 02 (2009-06-15)
2-5
NOTE
l l
When Address type is set to NSAP Address, ensure that the T2000 is installed with the OSI protocol stack software. When Address type is set to IP Address of GNE or IP Address Range of GNE, and the T2000 server and gateway NE are not in the same network segment, ensure that the IP routes of the network segments to which the T2000 server and gateway NE belong are configured on the T2000 and related routers.
3.
Click OK.
Step 3 Optional: Repeat Step 2 to add several search domains. Step 4 Click Start. The Search for NE dialog box is displayed. Select Search for NE, click OK. After the search ends, the Result list displays all the NEs that are found. Step 5 Create NEs. 1. 2. 3. 4. 5. Select an NE that is not created from the Result list. Optional: Select the GNE ID of the NE. Click Create. The system displays the Create dialog box. Specify User Name and Password. Click OK. The icon of the created NE is displayed in the Main Topology. Step 6 Optional: Repeat Step 5 to create other NEs that are not created. ----End
2.2.2 Creating NEs by Using the Manual Method

You can only create NEs one by one through the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
Prerequisite
l l
The user must log in to the T2000. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The NE to be created must have normal communication with the T2000. 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.
l l
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Device. The system displays the Add Object dialog box. Step 2 Select the NE type from the Object Type tree. Step 3 Complete the following information: ID, Extended ID, Name, and Remarks.
Step 4 Set the Gateway Type parameter for the NE. If ... The Gateway Type parameter is set to Gateway Then ... Proceed to the next step.
The Gateway Type parameter is set to Non- Select the gateway to which the NE belongs, Gateway and go to Step 6. Step 5 Specify the protocol and IP address that the NE uses. If ... If the Protocol parameter is set to IP If the Protocol parameter is set to OSI Then ... Enter the IP Address of the NE. Enter the NSAP Address of the NE.
Issue 02 (2009-06-15)
2-7
Step 6 Specify NE User and Password. The default user name is root and the default password is password. Step 7 Click OK. Step 8 Click the Main Topology. The icon of the NE is displayed at the cursor position. ----End
Parameters
Parameter ID Value Range 1 to 49135 Default Value Description This parameter specifies the basic ID of the NE to be created. The NE ID that consists of the basic ID and extended ID is the identifier of the NE on the T2000. This parameter specifies the extended ID of the NE to be created. Generally, the extended ID is set to 9. The Name of each NE must be unique. It is recommended that you set Name to a character string that includes the location of the NE, the ID of the NE, or other information.
Extended ID
1 to 254
Name
2-8
Issue 02 (2009-06-15)
Parameter Gateway Type
Value Range Gateway, NonGateway
Default Value Non-Gateway
Description
l
If the NE to be created is a gateway NE, set Gateway Type to Gateway. If the NE to be created is a non-gateway NE, set Gateway Type to NonGateway. If the NE to be created can function as a gateway NE or a non-gateway NE, set Gateway Type according to the planning information for the DCN.
Affiliated Gateway
When Gateway Type is set to NonGateway, set the gateway NE to which the NE to be created belongs.
l
Protocol
IP, OSI
IP
When Gateway Type is set to Gateway, you need to set this parameter. When the OSI over DCC solution is applied, set this parameter to OSI. In the case of other situations, set this parameter to IP.
IP Address
This parameter specifies the IP address of the NE to be created. When Protocol is set to IP, you need to set this parameter. This parameter specifies the NSAP address of the NE to be created. When Protocol is set to OSI, you need to set this parameter. You only need to set the area ID, and the other parts are automatically generated by the NE.
NSAP Address
NOTE
l l
When Protocol is set to OSI, ensure that the T2000 is installed with the OSI protocol stack software. When Protocol is set to IP, and the T2000 server and gateway NE are not in the same network segment, ensure that the IP routes of the network segments to which the T2000 server and gateway NE belong are configured on the T2000 and related routers.
2.2.3 Creating Virtual NE

To display the topological relations between the equipment that is directly managed by the T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform manner.
Prerequisite
l
You must be an NM user with "NM operator" authority or higher.

Issue 02 (2009-06-15)
l
Applies to the SDH equipment.
Procedure
Step 1 Right-click the Main Topology and choose New > Device from the shortcut menu. The Add Object dialog box is displayed. Step 2 Choose NE > SDH Series > Virtual NE from the Object Tree. Step 3 Enter the ID, Name, and Remarks of the NE. Step 4 Click OK. Then click the Main Topology. The NE icon is displayed at the spot where you clicked the mouse button. ----End
2.3 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first so that the T2000 can manage and operate the NE. 2.3.1 Uploading the NE Data Generally, the NE data is configured by uploading the NE data. Uploading the NE data involves uploading the NE-side configurations, alarm data, and performance data to the NMS. 2.3.2 Configuring the NE Data Manually You need to manually configure the NE data during initialization. The operation clears original service data from NEs and then deliver the new configuration data to NEs.
2.3.1 Uploading the NE Data

Generally, the NE data is configured by uploading the NE data. Uploading the NE data involves uploading the NE-side configurations, alarm data, and performance data to the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully.
Context Procedure
Step 1 Double-click the unconfigured NE on the Main Topology. The NE Configuration Wizard dialog box is displayed. Step 2 Choose Upload and click Next. The Confirm dialog box is displayed indicating that the upload may take a long time. Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading is completed.
Step 4 Click Close. ----End
2.3.2 Configuring the NE Data Manually

You need to manually configure the NE data during initialization. The operation clears original service data from NEs and then deliver the new configuration data to NEs.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully.
When you manually configure the NE data, the original service data is cleared from the NEs. Therefore, the communications between the NEs and the T2000 may be interrupted and the subsequent procedures of manually configuring the NE data cannot be performed. In the case of the RTN NEs, this operation is used for configuring gateway NEs for the first time.
Procedure
Step 1 Select the NE whose data you want to configure. Double-click the unconfigured NE on the Main Topology. The NE Configuration Wizard dialog box is displayed. Step 2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating that manual configuration clears the data on the NE side. Step 3 Click OK. The Confirm dialog box is displayed indicating that manual configuration interrupts the service on the NE. Step 4 Click OK. The Set NE Attribute dialog box is displayed.
Step 5 Set NE Name, Equipment Type, NE Remarks and Subrack Type and then click Next. The NE slot window is displayed. Step 6 Optional: Click Query Logical Information to query the logical boards of the NE.
Step 7 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE
The Query Logical Information and Query Physical Information operations cannot be performed for a preconfigured NE.
Step 8 Right-click on the slot to add a board. Click Next to display the Send Configuration window. Step 9 Choose Verify and Run as required and click Finish.
NOTE
Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.
----End
2.4 Creating Fibers

To implement the end-to-end service management on the NMS, you need to create the fibers first. 2.4.1 Creating Radio Links by Searching for the Radio Links By searching for a radio link, the NMS can obtain the information about the radio link to which the specified IF interface is connected, and thus can create the radio link quickly. Generally, the search-and-create method is used to create radio links. 2.4.2 Creating Radio Links by Filling the Link Table After you manually fill in the table, the NMS can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed. 2.4.3 Creating SDH Fiber Links by Searching the SDH Fiber Links By searching for a fiber link, the NMS can obtain the information about the fiber link to which the specified optical interface is connected, and thus can create the fiber link quickly. Generally, the search-and-create method is used to create fiber links. 2.4.4 Creating SDH Fiber Links by Filling the Link Table After you manually fill in the table, the NMS can create radio links according to the configuration information about the links. This method is often used when the fiber link is not physically connected. 2.4.5 Creating DCN Communication Cable The T2000 can communicate with NEs through the Ethernet port or serial port. The NEs also communicate with each other through the extended ECC. Depending on the communication mode, different types of cables can be created on the T2000.
2.4.1 Creating Radio Links by Searching for the Radio Links

By searching for a radio link, the NMS can obtain the information about the radio link to which the specified IF interface is connected, and thus can create the radio link quickly. Generally, the search-and-create method is used to create radio links.
Prerequisite
l l
You must be an NM user with "NE maintainer" authority or higher. The IF board for each NE must be created on the T2000.
2-12
Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are called radio signals. The links that transmit radio signals are called radio links.
Procedure
Step 1 Choose File > Search for Fiber/Cable from the Main Menu. Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress bar is displayed.
NOTE
l l l
If you check the Do not search for ports of created fibers on T2000 check box, the system does not search for the ports at which radio links are already created. If you need to check consistency between the created radio links and the actual radio links, do not check this check box. If you check this check box and if all the selected ports radio links are created, a dialog box is displayed after the search is complete, telling that the search domain is empty.
Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful. Click Close. Step 4 In the Newly Searched Fiber list, select one or multiple radio links. Click Create Fiber/ Cable.
NOTE
When you select one or multiple radio links in the Newly Searched Fiber list, the radio links that conflict with the selected ones are automatically displayed in the Existing Conflicting Fiber list. In this case, refer to Step 5 to delete the conflicting radio links before the creation. During the creation of radio links, if the selected links are all in the Already created state, the system prompts No fiber to create.
Step 5 In the Existing Conflicting Fiber list, select one or multiple conflicting radio links (the Conflict with logical link (Y/N) value of which in the Misconnected Fiber list is displayed as Yes), Click Delete Fiber/Cable. ----End
Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can supplement the information about the radio link by modifying the fiber/cable information.
2.4.2 Creating Radio Links by Filling the Link Table

After you manually fill in the table, the NMS can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed.
Prerequisite
l l
You must be an NM user with "NE maintainer" authority or higher. The boards to be connected with radio links must be created.
Issue 02 (2009-06-15)
Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz is called a radio signal. The link that transmits radio signals is called a radio link.
Procedure
Step 1 Click the + sign. shortcut icon on the toolbar of the Main Topology and the cursor changes to a
Step 2 Click the source NE of the radio link on the Main Topology. Step 3 Select the source board and port in the Select the source end of the link dialog box. Step 4 Click OK and the cursor changes to a + sign. Step 5 Click the sink NE of the radio link on the Main Topology. Step 6 Select the sink board and port in the Select the sink end of the link dialog box.
TIP
When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Microwave Link dialog box.
Step 8 Click OK. The created radio link appears between the source and sink NEs on the Main Topology. ----End
2.4.3 Creating SDH Fiber Links by Searching the SDH Fiber Links
By searching for a fiber link, the NMS can obtain the information about the fiber link to which the specified optical interface is connected, and thus can create the fiber link quickly. Generally, the search-and-create method is used to create fiber links.
Prerequisite
l l
You must be an NM user with "NE maintainer" authority or higher. The optical interfaces of every NE must be connected using fibers.
2-14
l
The boards of every NE must be created on the T2000.
Context
l
If conflicting fibers are found during the creation, delete the conflicting fibers on the T2000 before you start creating fibers. When a fiber between two SDH NEs passes through a WDM NE, if the normal fiber between an SDH NE and a WDM NE has been created on the T2000, the fiber found by the trail search function is created as a virtual fiber. If the WDM NE is not created on the T2000, the fiber is created as a normal fiber. When a fiber is created, it is usually bidirectional. But when the fiber is connected to the ports of the REG functions or the SDH and WDM equipment, the fiber is unidirectional.
Procedure
Step 1 Choose File > Search for Fiber/Cable from the Main Menu. Step 2 In the left pane select some ports from one or more NEs and click Search to search for the fibers or cables. A progress bar is displayed showing the progress of the search.
NOTE
l l l
If you check the Do not search for ports of created fibers on T2000 check box, the system only searches for the ports that do not have fibers. To check if the created fiber is consistent with the actual fiber connection, leave the check box unchecked. If you check the Do not search for ports of created fibers on T2000 check box, and if all the selected ports have fibers created, the system displays a message indicating that the search field is null.
Step 3 A prompt appears telling you that the operation was successful. Click Close. Step 4 To create fibers, select one or more fibers from the Newly Searched Fiber list and click Create Fiber/Cable.
NOTE
When one or more fibers are selected in the Newly Searched Fiber list, fibers that conflict with the selected fibers, are shown in the Existing Conflicting Fiber list. If there is any conflicting fiber, proceed to Step 5 and delete it before creating fibers. During fiber creation, if all the selected fibers are in the Already created state, the system displays the message as follows: No fiber to create.
Step 5 To delete the conflicting fibers, from the Existing Conflicting Fiber list select one or more fibers whose values are Yes for the Existing Conflicting link (Y/N) parameter in the Misconnected Fiber list. Click Delete Fiber/Cable. ----End
Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can supplement the information about the fiber by modifying the fiber/cable information.
2.4.4 Creating SDH Fiber Links by Filling the Link Table

After you manually fill in the table, the NMS can create radio links according to the configuration information about the links. This method is often used when the fiber link is not physically connected.
Prerequisite
You must be an NM user with "NE operator" authority or higher. The boards to be connected with the fiber or cable have been created.
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu. Step 2 Click Create, and the Create Fibers in Batches dialog box is displayed. Step 3 Click Select Object, select all the NEs you need to create fiber/cable in the dialog box. Step 4 Click OK. Step 5 Click New in the Create Fibers in Batches dialog box. Step 6 Set Direction, Source NE, Source Port, Sink NE and Sink Port.
Step 7 Click Apply. Repeat Step 3 to create another fiber connection.

TIP
You can create multiple fibers/cables and set parameters in step 5, click Apply.
Step 8 Click Cancel to complete the settings. The created fiber connections are displayed in the Fiber/ Cable Information list. ----End
2.4.5 Creating DCN Communication Cable

The T2000 can communicate with NEs through the Ethernet port or serial port. The NEs also communicate with each other through the extended ECC. Depending on the communication mode, different types of cables can be created on the T2000.
Prerequisite
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Link from the shortcut menu. Step 2 Select a cable type from the expanded items.
Step 3 Enter the cable attributes in the right-hand pane. Step 4 Click OK. The cable is displayed on the Main Topology between the T2000 and the GNE. ----End
Postrequisite
If the NEs at the two ends of the DCN communication cables do not belong to the same subnet, you have to return to the upper-level view of the subnet to view the created DCN communication cables.
2.5 Creating a Topology Subnet

The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet.
Prerequisite
A topology subnet is created only to simplify the user interface and has no impact on the NEs.
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Subnet from the shortcut menu. Step 2 Click the Properties tab in the Add Object dialog box. Enter the attributes of the subnet. Step 3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane. . Click
NOTE
In the case of a similar dialog box for selecting objects,

l l
indicates that to select the objects to be selected on the left to the selected objects on the right. indicates that to select all the objects to be selected on the left to the selected objects on the right.
Step 4 Click OK. Click in the blank space of the Main Topology, the where you clicked. ----End
icon appears in the position
2.6 Adjusting Topology Objects

You can modify the settings when creating the network topology by using the T2000. For example, adjust the optical NE source, modify the status of the preconfigured NE and so on. 2.6.1 Balancing Load of the NE Explorer Process
To ensure a load balance of the NE Explorer process, you need to migrate NEs. When an NE Explorer instance manages too many NEs, you can create a new NE Explorer process and migrate some NEs to the new NE Explorer instance for management. 2.6.2 Modifying the NM Name You can modify the NM name as required. This operation does not affect the running of the T2000. 2.6.3 Modifying the NE Name You can modify the NE name as required. This operation does not affect the running of the NE. 2.6.4 Modifying the NE ID The ECC protocol uses the NE ID as the unique identifier of an NE. The T2000 also uses the NE ID to identify different NEs in the user interface and databases, and uses the NE ID as the key word in searches. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE, it results a collision in the ECC route. As a result, it becomes difficult to manage some NEs. In the commissioning or expansion process, when you need to adjust the original planning and modify the NE ID, you can use the T2000 to achieve it. 2.6.5 Modifying the IP Address of an NE After modifying the NE ID, you can modify the IP address of an NE based on the engineering planning. Modifying the IP address of an NE does not affect services, but modifying the IP address of a gateway NE affects the communication between the Web LCT and the NEs. 2.6.6 Adding Boards When manually configuring the NE data, you need to add boards on the NE Panel. You can either add the physical boards that actually operate on the NE or add the logical boards that do not exist on the actual equipment. 2.6.7 Modifying Fiber/Cable Information You can modify the name, attenuation, length, and type of a fiber/cable according to its connection status and physical features. 2.6.8 Naming a Fiber/Cable In the network management, you need to strictly plan the fiber names, to ensure that faults can be fast located during maintenance and troubleshooting. On the T2000, you can use the preset naming rules to name the fiber/cable. 2.6.9 Copying Topology Objects In the current topology view, you can copy a topology object from one subnet to another. 2.6.10 Moving Topology Objects In the current topology view, you can move a topology object from one subnet to another.
2.6.1 Balancing Load of the NE Explorer Process

To ensure a load balance of the NE Explorer process, you need to migrate NEs. When an NE Explorer instance manages too many NEs, you can create a new NE Explorer process and migrate some NEs to the new NE Explorer instance for management.
Prerequisite
l l
You must be an NM user with "NM maintainer" authority or higher. The deployment tool server is started.
2-18
Issue 02 (2009-06-15)
Context
NOTE
The type of the new NE Explorer instance must be the same as that of the NE Explorer instance with overloaded NEs.
Procedure
Step 1 Choose System > NE Deploy Management from the Main Menu. The NE Deploy Management window is displayed. Step 2 In the left-hand pane, select an NE Explorer instance, and click Migrate NE. The Migrate NE dialog box is displayed. Step 3 In Sink NE Explorer, select the new NE Explorer instance. Step 4 In the left-hand pane, select an NE that you want to move to the Sink NE Explorer, and click . The NE is displayed in the right-hand pane.
NOTE
You can repeat Step 4 to move multiple NEs.
Step 5 Optional: In the right-hand pane, select an NE that you want to move to the Source NE Explorer, and click
NOTE
. The NE is displayed in the left-hand pane.
You can repeat Step 5 to move multiple NEs.
Step 6 Click OK. The Operation Result dialog box is displayed indicating that the operation is successful. Step 7 Click Close. ----End
2.6.2 Modifying the NM Name

You can modify the NM name as required. This operation does not affect the running of the T2000.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Right-click the NM icon on the Main Topology and choose Attribute from the shortcut menu. Step 2 In the NM Attribute dialog box, enter a new NM name. Click OK.
Issue 02 (2009-06-15)
2-19
NOTE
The NM name can contain letters, symbols and numerals, but cannot contain the following special characters: | : * ? " < >.
----End
2.6.3 Modifying the NE Name

You can modify the NE name as required. This operation does not affect the running of the NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function Tree. Step 2 In the NE Attribute dialog box, enter a new NE name in Name. Click Apply. A prompt appears telling you that the operation was successful.
NOTE
An NE name can contain a maximum of 64 letters, symbols, and numerals, but cannot contain the following special characters: | : * ? " < >.
Step 3 Click Close. ----End
2.6.4 Modifying the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. The T2000 also uses the NE ID to identify different NEs in the user interface and databases, and uses the NE ID as the key word in searches. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE, it results a collision in the ECC route. As a result, it becomes difficult to manage some NEs. In the commissioning or expansion process, when you need to adjust the original planning and modify the NE ID, you can use the T2000 to achieve it.
Prerequisite
l l
You must be an NM user with "NE operator" authority or higher. The NE must be created.
Precautions
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.
2-20
Issue 02 (2009-06-15)
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed. Step 3 Enter the New ID and the New Extended ID. Click OK. Step 4 Click OK in the Warning dialog box. ----End
2.6.5 Modifying the IP Address of an NE

After modifying the NE ID, you can modify the IP address of an NE based on the engineering planning. Modifying the IP address of an NE does not affect services, but modifying the IP address of a gateway NE affects the communication between the Web LCT and the NEs.
Prerequisite
l l
The user must log in to the NE. You must be an NE user with "Maintenance Level" authority or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree. Step 2 Set the IP.
Step 3 Click Apply. A dialog box is displayed and click OK. ----End
Issue 02 (2009-06-15)
2-21
Parameters
Parameter IP Value Range Default Value This parameter is preset to 129.9.0.x during the factory delivery, where "x" indicates the basic ID. Description
l
If the NE is planned as the gateway NE, the NE IP address, subnet mask, and default gateway must comply with the requirements for planning the external DCN. If the NE is planned as a non-gateway NE, the IP addresses of other NEs should be set according to the NE IDs. In this case, the IP address should be set to 0x81000000 + NE ID. That is, if the NE ID is 0x090001, the IP address should be set to 129.9.0.1.
Postrequisite
After the IP address of the NE is changed, you need to log in to the NE again.
2.6.6 Adding Boards

When manually configuring the NE data, you need to add boards on the NE Panel. You can either add the physical boards that actually operate on the NE or add the logical boards that do not exist on the actual equipment.
Prerequisite
l l l
You must be an NM user with "NE operator" authority or higher. The NE must be created. There must be idle slot on the NE Panel.
Context
The physical boards are the actual boards inserted in the subrack. A logical board refers to a board that is created on the T2000. After a logical board is created, you can configure the relevant services. If the corresponding physical board is online, the configured services can be available.
NOTE
The NE panel is able to indicate the mapping relation between slots that house processing boards and interface boards. When you click a processing board that is paired with an interface board in the NE panel, the ID of the slot that houses the mapping interface board is displayed in orange.
Procedure
Step 1 Double-click the icon of the NE to open the NE Panel. Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list. ----End
2.6.7 Modifying Fiber/Cable Information

You can modify the name, attenuation, length, and type of a fiber/cable according to its connection status and physical features.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu. The information of all fiber/ cable is displayed in the pane on the right. Step 2 In the Name column, right-click the value for a fiber/cable and choose Modify Fiber/Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter a proper name for the fiber/cable and click OK. Click Close in the Operation Result dialog box. Step 3 In the Length(km) column, right-click the value for a fiber/cable and choose Modify Fiber/ Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter the actual length for the fiber/cable and click OK. Click Close in the Operation Result dialog box. Step 4 Modify the attenuation of a fiber. 1. 2. In the Attenuation column, right-click the value for a fiber and choose Modify Fiber/ Cable from the shortcut menu. In the Modify Fiber/Cable dialog box, enter the actual loss and click OK. Click Close in the Operation Result dialog box.
Step 5 Modify the type of the fiber. 1. 2. In the Type column, right-click the value for a fiber and choose Modify Fiber/Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, select the actual type of the fiber from the drop-down list and click OK. Click Close in the Operation Result dialog box.
----End
2.6.8 Naming a Fiber/Cable

In the network management, you need to strictly plan the fiber names, to ensure that faults can be fast located during maintenance and troubleshooting. On the T2000, you can use the preset naming rules to name the fiber/cable.
Prerequisite
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu. The information of all fiber/cable is displayed in the pane on the right. Step 2 Right-click a fiber/cable and choose Name by Rule from the shortcut menu.
The value in the Name field automatically changes according to the configured naming rule. ----End
2.6.9 Copying Topology Objects

In the current topology view, you can copy a topology object from one subnet to another.
Prerequisite
You must be an NM user with the "Topo Operator" authority or higher.
Context
l l
You cannot paste the same device or subnet to the destination subnet. You can press and hold Shift to select two or more objects. You can copy and paste multiple objects at a time.
Procedure
Step 1 In the topology view, go to the source subnet of the object that you want to copy. Click the object. Step 2 Choose Edit > Copy to copy the object to the clipboard. Step 3 Go to the destination subnet, choose Paste to paste the object in the subnet. ----End
2.6.10 Moving Topology Objects

In the current topology view, you can move a topology object from one subnet to another.
Prerequisite
Context
l
When you cut and paste an object, the object is copied to the destination subnet and deleted from the source subnet. You cannot paste the same device or subnet to the destination subnet.
Procedure
Step 1 In the topology view, go to the source subnet of the object that you want to move. Click the object. Step 2 Choose Edit > Cut to copy the object to the clipboard. Step 3 Go to the destination subnet, choose Paste to paste the object in the subnet. ----End
2.7 Deleting Topology Objects

When adjusting the network topology, generally, you need to delete some objects of the topology. 2.7.1 Deleting Topology Subnets When adjusting the topological structure of the network, you can delete a subnet from the Main Topology if the subnet is not needed. 2.7.2 Deleting Fibers When adjusting the network if you need to delete the NEs or change the links between NEs, you need to delete the fiber connections between the NEs. 2.7.3 Deleting Boards To modify the network configuration or the NE configuration, you may need to delete the boards from the NE Panel. 2.7.4 Deleting NEs If you have created a wrong NE, you can delete the NE from the T2000. Deleting an NE removes all information of the NE from the T2000 but does not affect the running of the equipment.
2.7.1 Deleting Topology Subnets

When adjusting the topological structure of the network, you can delete a subnet from the Main Topology if the subnet is not needed.
Prerequisite
Context
After a subnet is deleted, the topological objects in the original subnet are moved to the upperlevel subnet that the original subnet belongs to.
Procedure
Step 1 Right-click the subnet on the Main Topology, and choose the Delete shortcut menu. Step 2 Click Yes to delete the subnet. Step 3 Click Close in the Delete Object Results dialog box. ----End
2.7.2 Deleting Fibers

When adjusting the network if you need to delete the NEs or change the links between NEs, you need to delete the fiber connections between the NEs.
Prerequisite
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu. Step 2 Select the fiber you want to delete, right-click and choose Delete Fiber/Cable from the shortcut menu. The Warning dialog box is displayed. Click OK to delete the fiber/cable.
CAUTION
The deletion of the fiber/cable will delete the related protection subnets, trails and user-defined information. Exercise caution before you delete the fiber/cable. You can export the script of the entire network first to avoid deletion by mistake. Step 3 Click Step 4 Click Close in the Operation Result dialog box. ----End
2.7.3 Deleting Boards

To modify the network configuration or the NE configuration, you may need to delete the boards from the NE Panel.
Prerequisite
l l
You must be an NM user with "NE maintainer" authority or higher. The services and protection groups must be deleted.
Procedure
Step 1 Double-click the icon of the NE to open the NE Panel. Step 2 Right-click the board you want to delete and choose Delete from the shortcut menu. Step 3 Click OK in the Delete Board dialog box. Step 4 Click OK to delete the board. ----End
2.7.4 Deleting NEs

If you have created a wrong NE, you can delete the NE from the T2000. Deleting an NE removes all information of the NE from the T2000 but does not affect the running of the equipment.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Context
When the NE is not logged in, you can delete the NE on the T2000.
CAUTION
If an NE is deleted, the links related to the NE are also deleted.
Procedure
l Delete a single or RTN NE. 1. 2. l 1. Right-click the NE on the Main Topology and choose Delete > Delete Device from the shortcut menu. The Confirm dialog box is displayed. Click Yes. The NE icon is deleted from the Main Topology. Choose Configuration > Configuration Data Management from the Main Menu. The Configuration Data Management window is displayed. . The Configuration Data In the left-hand pane, select multiple NEs and click Management List pane displays the configuration data of all the selected NEs. Select the NEs to be deleted, right-click and choose Delete from the shortcut menu. The Delete the NE dialog box is displayed. Click OK.
Delete NEs in batches.
2. 3. 4. ----End
Issue 02 (2009-06-15)
2-27
3 Configuring Radio Links on the Per-NE Basis
Configuring Radio Links on the Per-NE Basis
About This Chapter

Before you configure the radio link between two microwave sites, you need to configure the corresponding information about the radio link. 3.1 Configuration Flow The flow of configuring SDH/PDH radio links is different from the flow of configuring Hybrid radio links. 3.2 Creating IF 1+1 Protection In the case of the IDU 620, if the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group. 3.3 Creating an XPIC Workgroup When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes. 3.4 Configuring the IF/ODU Information of a Radio Link This section describes how to configure the common IF/ODU information for each radio links in the SDH/PDH microwave. You can set the IF/ODU information that is frequently used by the SDH/PDH radio link based on each radio link. 3.5 Configuring the Hybrid/AM Attribute The Hybrid microwave supports the transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the reliable transmission of the E1 services and flexible transmission of the Ethernet services whose bandwidth is large and changes dynamically. 3.6 Configuring the ATPC Function To configure the ATPC function, set the ATPC attributes of the IF board. 3.7 Creating an N+1 Protection Group When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration. 3.8 Creating REGs
In the case of the 3+1 protection, you need to configure REGs for the secondary NE.
3-2
Issue 02 (2009-06-15)
3.1 Configuration Flow

The flow of configuring SDH/PDH radio links is different from the flow of configuring Hybrid radio links.
Configuring SDH/PDH Radio Links

Table 3-1 Configuring SDH/PDH radio links Step 1 Operation Configuring the IF 1+1 protection Remarks Required when the 1+1 HSB/FD/SD protection is configured. For details about the 1+1 HSB/FD/SD protection, see the OptiX RTN 600 Radio Transmission System Feature Description. 2 Creating the XPIC workgroup Required when the XPIC is configured. For details about the XPIC, see the OptiX RTN 600 Radio Transmission System Feature Description. 3 4 Configuring the IF/ODU information of a radio link Configuring the N+1 protection Required. Required when you need to configure the 2+1 protection. Required when you need to configure the 3+1 protection. For details about the N+1 protection, see the OptiX RTN 600 Radio Transmission System Feature Description. 5 6 Creating a REG Setting the ATPC attributes Required when the 3+1 protection is configured for the standby NE. Required when you set the ATPC threshold manually. For details about the ATPC, see the OptiX RTN 600 Radio Transmission System Feature Description.
Issue 02 (2009-06-15)
3-3
Configuring a Hybrid Radio Link

Table 3-2 Configuring a Hybrid radio link Step 1 Operation Configuring the IF 1+1 protection Remarks Required when the 1+1 HSB/FD/SD protection is configured. For details about the 1+1 HSB/FD/SD protection, see the OptiX RTN 600 Radio Transmission System Feature Description. 2 3 Configuring the IF/ODU information of a radio link Setting the Hybrid/AM attribute Required. For details about the Hybrid microwave, see the OptiX RTN 600 Radio Transmission System Feature Description. Required when you set the ATPC threshold manually. For details about the ATPC, see the OptiX RTN 600 Radio Transmission System Feature Description.
Setting the ATPC attributes
3.2 Creating IF 1+1 Protection

In the case of the IDU 620, if the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original services are not interrupted.
Precautions
The 18,2E1,3.5MHz,QPSK work mode does not support IF 1+1 protection.
3-4
Issue 02 (2009-06-15)
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Step 2 Click Create. The system displays the Create IF 1+1 Protection dialog box. Step 3 Set the parameters of the IF 1+1 protection group.
Step 4 Click OK. ----End
Issue 02 (2009-06-15)
3-5
Parameters
Parameter Working Mode Value Range HSB, FD, SD Default Value HSB Description
l
In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. In the 1+1 FD protection 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 the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection 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 the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information. 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. 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. It is recommended that you use the default value.
Revertive Mode
Revertive, NonRevertive
Revertive
3-6
Issue 02 (2009-06-15)
Parameter WTR Time (s)
Value Range 300 to 720
Default Value 600
Description
l
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. 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. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value. In the 1+1 FD/SD mode, two IF boards should be installed as a pair in slots 5 and 7 (the IF board in slot 5 is recommended to be the main board) or in slots 6 and 8 (the IF board in slot 6 is recommended to be the main board). In the 1+1 HSB mode, the IF boards can be installed in slots 58. It is recommended that you install two IF boards in a pair in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
Enable Reverse Switching
Enable, Disable
Enable
Working Board Protection Board
IF ports
NOTE
The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.
Postrequisite
l
In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU.
Issue 02 (2009-06-15)
3-7

l
In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE
The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby ODU after you create an IF 1+1 protection group.
3.3 Creating an XPIC Workgroup

When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IFX boards and the ODUs to which the IFX boards are connected must be created. The XPIC Enabled parameter must be set to Enabled (default value) for the IFX boards.
Procedure
Step 1 In the NE Explorer, select the NE and then 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 Set the parameters for the XPIC workgroup.
3-8
Issue 02 (2009-06-15)
Parameters
Parameter Polarization direction-V Polarization direction-H
l
Value Range IF ports of IFX boards
Default Value -
Description
l
Polarization direction-V and Polarization direction-H indicate the IF ports to which polarization direction V and polarization direction H correspond respectively. It is recommended that you install the two IFX boards that form an XPIC workgroup in the slots that are at the same layer or in the same column. Set the IF port on the IFX board that has a smaller slot number to Polarization direction-V and the IF port on the other IFX board to Polarization direction-H. Link ID-V and Link ID-H indicate the link IDs to which polarization direction V and polarization direction H correspond respectively. A Link ID is an identifier of a microwave link and is used to prevent the microwave links between sites from being wrongly connected. 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. Set these two parameters according to the planning information. These two parameters must be set to different values, but the Link ID-V must be set to the same value at the two ends of a link and the Link ID-H must also be set to the same value at the two ends of a link. The value of this parameter must not exceed the rated power range supported by the ODU. The TX power of the ODU must be set to the same value at the two ends of a microwave link. Set this parameter according to the planning information.
Link ID-V Link ID-H
1 to 4094
TX Power (dBm)
-10.0 to 35.0
Issue 02 (2009-06-15)
3-9
Parameter Transmission Frequency (MHz)
Value Range 0 to 4294967.295
Default Value 100
Description
l
The parameter specifies the channel center frequency. 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 greater than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. Set this parameter according to the planning information. When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. When Transmission Status is set to unmute, the ODU normally transmits and receives microwave signals. In normal cases, set this parameter to unmute. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the TX power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. During commissioning, set this parameter to Disabled to ensure that the TX power is not changed. After the commissioning, re-set the ATPC attributes. Set the central value of the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB.
Transmission Status
mute, unmute
mute
ATPC Enabled
Enabled, Disabled
Disabled
ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm)
-20 to -75 -35 to -90
-45 -70
3-10
Issue 02 (2009-06-15)
NOTE
Each of the ATPC parameters must be set to the same value at the two ends of a microwave link.
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU Configuration tab page if the used ODU supports two T/R spacings.
3.4 Configuring the IF/ODU Information of a Radio Link

This section describes how to configure the common IF/ODU information for each radio links in the SDH/PDH microwave. You can set the IF/ODU information that is frequently used by the SDH/PDH radio link based on each radio link.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. In the case of the IDU 610/620, the IF board and the ODU that connects to the IF board must be added.
Precautions
l
In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In this case, you need configure only the IF/ODU information of the main OptiX RTN 600. In 1+1 FD protection mode, one protection group corresponds to one radio link. In this case, you need configure the IF/ODU information of the main OptiX RTN 600 and the ODU information of the standby OptiX RTN 600. In the case of XPIC radio links, one XPIC workgroup corresponds to two radio links. The IF/ODU information of the radio links should be configured in the XPIC workgroup. In the case of N+1 radio links, one N+1 protection group corresponds to N+1 radio links and the IF/ODU information of the N+1 radio links should be set respectively.
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 IF/ODU Configuration. Step 3 Click an IF board icon or ODU icon. Then, the system displays the IF/ODU information of the radio link to which the IF board belongs. Step 4 Set the corresponding IF information of the radio link.
Issue 02 (2009-06-15)
3-11
Step 5 Click Apply. Step 6 Set the corresponding ODU information of the radio link. Step 7 Click Apply.
NOTE
Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio link.
----End
3-12
Issue 02 (2009-06-15)
Parameters
Parameter Work Mode Value Range 1,4E1,7MHz,QPS K 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,QPS K 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 16,5E1,7MHz,QPS K 17,10E1,14MHz,Q PSK 18,2E1,3.5MHz,QP SK
l
Default Value 1,4E1,7MHz,QPSK (IF1A/B) 5,16E1,28MHz,QP SK (IF0A/B) 7,STM-1,28MHz, 128QAM (IFX)
Description
l
This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format. The IF1A/IF1B board supports radio work modes 115 and the IF0A/IF0B board supports radio work modes 5 and 1618. The IFX board supports radio work mode 7. The IFH2 board of the IDU 620 does not support the setting of the Work Mode. Set this parameter according to the planning. The radio work modes of the IF boards at both the radio link must be the same.
Issue 02 (2009-06-15)
3-13
Parameter Link ID
Value Range 14094
Default Value 1
Description
l
As the identifier of a radio link, this parameter is used to avoid misconnection of radio links between sites. If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the TX power of the transmitter automatically traces the changes of the RX level at the receive end, within the ATPC controlled range. It is recommended that you set this parameter to Disabled in areas where fast fading severely affects the radio transmission. To ensure that the TX power does not change during the commissioning process, set this parameter to Disabled. After the commissioning is complete, you can set this parameter to another value. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board. When the function is disabled, the manually set ATPC upper and lower thresholds are used.
ATPC Enable Status
Enabled, Disabled
Disabled
ATPC Automatic Threshold Enable Status
Enabled, Disabled
Enabled
3-14
Issue 02 (2009-06-15)
Parameter TX Frequency (MHz)
Value Range 04294967.295
Default Value 0.0
Description
l
The parameter specifies the channel center frequency. This parameter cannot be set to a value that is less than the minimum TX frequency supported by the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU - 50% channel spacing. The difference between the TX frequencies of both the ends of a radio link is a T/R spacing. Set this parameter according to the planning. This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. The TX power of the ODU should be set to the same value at both the ends of a radio link. Set this parameter according to the planning. This parameter indicates the spacing between the TX frequency and receive frequency of the ODU. If Station Type of the ODU is TX high, the TX frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX frequency is one T/R spacing lower than the receive power. 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. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link. When this parameter is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. When this parameter is set to unmute, the ODU can normally receive and transmit microwave signals. Generally, this parameter takes the default value.
TX Power (dBm)
-10.0 to +35.0
-10.0
T/R Spacing (MHz)
04294967.295
0.0
TX Status
mute, unmute
unmute
Issue 02 (2009-06-15)
3-15
NOTE
The ATPC attributes at both the ends of a radio link should be set to the same.
3.5 Configuring the Hybrid/AM Attribute

The Hybrid microwave supports the transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the reliable transmission of the E1 services and flexible transmission of the Ethernet services whose bandwidth is large and changes dynamically.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
The IDU 620 supports the Hybrid/AM function. The IFH2 board is used as the Hybrid IF board.
Procedure
Step 1 Select the target Hybrid IF board in the NE Explorer. Then, choose Configuration > Hybrid/ AM Configuration from the Function Tree. Step 2 Click Query. Step 3 Set the parameters related to the Hybrid/AM function.
NOTE
To set the Hybrid IF board to work in super PDH mode of 40M/64QAM, do as follows: 1. Set AM Enable Status to Disable. Set Manually Specified Modulation Mode to 64QAM. Click Apply. 2. Set IF Channel Bandwidth to 40M. Click Apply.
Step 4 Click Apply. ----End
3-16
Issue 02 (2009-06-15)
Parameters
Parameter IF Channel Bandwidth Value Range In the case of the IFH2 board of the IDU 620:
l l l l l
Default Value 7M
Description IF Channel Bandwidth indicates the channel spacing of the corresponding radio links. Set this parameter to the planned value.
NOTE Only the combination of the IF Channel Bandwidth of 40M and the modulation mode of 64QAM forms the super PDH mode. The super PDH mode does not support the AM function.
7M 14M 28M 40M 56M -
AM Mode
Asymmetric
When this parameter is set to Asymmetric, an AM switching in one direction of the radio link (when the conditions for triggering the AM switching are met) does not cause an AM switching in the other direction of the radio link.
l
AM Enable Status
l l
Disable Enable
When this parameter is set to Disable, the radio link uses the specified modulation scheme only. In this case, you need to select Manually Specified Modulation Mode. When this parameter is set to Enable, the radio link uses the corresponding modulation scheme according to the channel conditions.
Hence, the Hybrid microwave can ensure the reliable transmission of the E1 services and provide dynamic bandwidth for the Ethernet services when the AM function is enabled. Modulation Mode of the Assured AM Capacity
l l l l l l
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
QPSK
This parameter specifies the lowest modulation scheme that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid microwave must ensure and the availability of the radio link that corresponds to this modulation scheme. This parameter is valid only when AM Enable Status is set to Enable.
Modulation Mode of the Full AM Capacity
l l l l l l
128QAM
This parameter specifies the highest modulation scheme that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid microwave and the availability of the radio link that corresponds to this modulation scheme. This parameter is valid only when AM Enable Status is set to Enable.
Issue 02 (2009-06-15)
3-17
Parameter Manually Specified Modulation Mode
Value Range
l l l l l l
Default Value -
Description This parameter specifies the modulation scheme that the radio link uses for the transmission. This parameter is valid only when AM Enable Status is set to Disable.
E1 Capacity
175
This parameter specifies the number of E1 services that can be transmitted in the Hybrid work mode. The value of this parameter cannot exceed the maximum number of E1 services permitted in Modulation Mode of the Assured AM Capacity.
3.6 Configuring the ATPC Function

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The related IF board must be added.
Precautions
l
In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC attributes of the main IF board. The following procedure describes the configuration of ATPC parameters in the IF interface configuration dialog box of the IF board. You can also set ATPC parameters in the following configuration dialog boxes:

Create an XPIC working group IF/ODU configuration
NOTE
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be modified.
Procedure
Step 1 Select the IF 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 Set the ATPC attributes.
Parameters
Parameter ATPC Enable Status Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. Set the central value of the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board. When the function is disabled, the manually set ATPC upper and lower thresholds are used.
ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm)
-20 to -75 -35 to -90
-45 -70
Enabled, Disabled
Enabled
Issue 02 (2009-06-15)
3-19

NOTE
l l
Each of the ATPC parameters must be set to the same value at the two ends of a microwave link. During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes.
3.7 Creating an N+1 Protection Group

When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be configured with 3+1 protection) must be created. The IF boards must work in the STM-1 mode.
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > N+1 Protection from the Function Tree. Step 2 Click Create. The system displays the Create an N+1 Protection Group dialog box. Step 3 Set the attributes of the N+1 protection group. Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select Working Unit. In Select Mapping Mode, select the line port to which a working channel corresponds and click 3. 4. 5. .
Repeat Step 4.2 to select the line ports to which other working channels correspond. In Select Mapping direction, select Protection Unit. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
3-20
Issue 02 (2009-06-15)
Parameters
Parameter WTR Time(s) Value Range 300 to 720 Default Value 600 Description
l
When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value. In the case of 2+1 protection, map two IF ports as Working Unit and map the remaining IF port as Protection Unit. In the case of the 3+1 protection, it is recommended that you map the two IF ports and the first line port of the STM-1 optical/electrical interface board that is connected to the secondary NE as Working Unit, and map the other line port as Protection Unit.
SD enable
Enabled, Disabled
Enabled
Slot Mapping Relation
NOTE
The N+1 protection groups of the equipment at both ends must have the same attributes.
Issue 02 (2009-06-15)
3-21
3.8 Creating REGs

In the case of the 3+1 protection, you need to configure REGs for the secondary NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface board that is connected to the primary NE must be created. The IF boards must work in the STM-1 mode.
Context
In the case of the 3+1 protection, you need to two configure REGs for the secondary NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > REG Configuration from the Function Tree. Step 2 Click Create. The system displays the Create REG dialog box. Step 3 Set the SD Enabled parameter. Step 4 Set the slot mapping relation. 1. 2. In Slot Mapping Direction, select West Line. In Select Mapping Mode, select the line port to which the west line corresponds and click . 3. 4. In Slot Mapping Direction, select East Line. In Select Mapping Mode, select the line port to which the east line corresponds and click .
3-22
Issue 02 (2009-06-15)
Step 5 Click OK. Step 6 Repeat Step 2 to Step 5, Create another REG.
----End
Issue 02 (2009-06-15)
3-23
Parameters
Parameter SD Enabled Value Range Enabled, Disabled Default Value Enabled Description
l
When this parameter is set to Enabled, the REG inserts an MS-AIS alarm when a B2_SD alarm is generated. It is recommended that you use the default value.
It is recommended that you map the IF port as West Line and the port of the STM-1 optical/electrical interface board as East Line.
3-24
Issue 02 (2009-06-15)
4 Configuring the MSP on the Per-NE Basis
Configuring the MSP on the Per-NE Basis
About This Chapter

The MSP includes the ring MSP and linear MSP. 4.1 Configuring the Ring MSP If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure the ring MSP. 4.2 Creating Linear MSP To protect the services carried by the optical fibers or STM-1e cables between two nodes, configure the linear MSP.
Issue 02 (2009-06-15)
4-1
4.1 Configuring the Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure the ring MSP.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the working unit and the protection unit are located must be configured.
When an unprotected service is converted into a ring MSP service by configuring the ring MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS from the Function Tree. Step 2 Click Create. A prompt is displayed, indicating that the service that is configured in the protection timeslot is changed to an extra service. Step 3 Click OK. The system displays the Create a Ring Multiplex Section dialog box. Step 4 Set the attributes of the ring MSP protection group according to the networking plan. Step 5 Set the slot mapping relation. 1. 2. 3. Set Local Node, West Node, and East Node according to the networking plan. In Select Mapping Direction, select West Line 1. In Select Mapping Mode, select the line port to which the working channel corresponds and click 4. 5. .
In Select Mapping Direction, select East Line 1. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
4-2
Issue 02 (2009-06-15)
Parameters
Parameter Level Protection Type Local Node Value Range 0 to 15 Default Value 0 Description The value is always set to STM-4. The value is always set to 2-fiber Bidirectional Multiplex Section.
l
This parameter specifies the node ID allocated to the local NE. The node ID of each NE must be unique.
West Node
0 to 15
This parameter specifies the node ID that is allocated to the NE to which the west line board of the local NE is connected. This parameter specifies the node ID that is allocated to the NE to which the east line board of the local NE is connected.
East Node
0 to 15
Issue 02 (2009-06-15)
4-3
Parameter WTR Time(s)
Default Value 600
Description
l
When the time after the former working channel is restored to normal reaches the set value of this parameter, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value. The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
SD enable
Enabled, Disabled
Enabled
Protocol Type
New Protocol, Restructure Protocol
New Protocol
It is recommended that you map the line port of the SL4 board in slot 6 as West Line 1 and map the line port of the SL4 board in slot 8 as East Line 1.
l
Map as VC4
Selected, Not selected
Not selected
If you select Map as VC4, the VC-4 is considered as the unit of the settings in the slot mapping relation. It is recommended that you use the default value.
NOTE
The protection groups of the NEs that form a ring multiplex section must be set with the same attributes except Local Node, West Node, and East Node.
Postrequisite
In the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional crossconnections between the services and the timeslots of the working channel (the first half of the timeslots of the line port) later. If extra services need to be transmitted, you need to configure bidirectional cross-connections between the extra services and the timeslots of the protection channel (the second half of the timeslots of the line port).
4-4
Issue 02 (2009-06-15)
4.2 Creating Linear MSP

To protect the services carried by the optical fibers or STM-1e cables between two nodes, configure the linear MSP.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the working unit and the protection unit are located must be configured.
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 attributes of the linear MSP group.
NOTE
When Protection Type is set to 1:N Protection. A prompt is displayed, indicating that the service that is configured in the protection timeslot is changed to an extra service.
Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select West Working Unit. In Select Mapping Mode, select the line port to which the working channel corresponds and click 3. 4. .
In Select Mapping direction, select West Protection Unit. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
Issue 02 (2009-06-15)
4-5
Parameters
Parameter Protection Type Switching Mode Value Range 1+1 Protection, 1:N Protection
l
Default Value 1+1 Protection

l
Description
l
Single-Ended Switching, DualEnded Switching (1+1 protection) Dual-Ended Switching (1:N protection)
Single-Ended Switching (1+1 protection) Dual-Ended Switching (1:N protection)

l
In the single-ended mode, if the services on the working channels in a certain direction need to be switched, only the services on the working channels in the direction are switched to the protection channels. In the dual-ended mode, the services on the working channels in two directions are switched to the protection channels. 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.
4-6
Issue 02 (2009-06-15)
Parameter Revertive Mode
Value Range
l
Default Value
l
Description
l
Non-Revertive, Revertive (1+1 protection) Revertive (1:N protection)
Non-Revertive (1 +1 protection) Revertive (1:N protection)
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. When extra services need to be transmitted or several working channels exist, select 1:N protection. In the case of other situations, it is recommended that you select the 1+1 single-ended and non-revertive mode.
WTR Time(s)
300 to 720
600
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value. The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
SD enable
Enabled, Disabled
Enabled
Protocol Type
New Protocol, Restructure Protocol
New Protocol
Issue 02 (2009-06-15)
4-7
Parameter Slot Mapping Relation
Value Range -
Default Value -
Description
l
In the case of 1+1 protection, only one line port can be mapped as West Working Unit; in the case of 1:N protection, a maximum of three line ports can be mapped as West Working Unit. Only one line port can be mapped as West Protection Unit. Ensure that the line port that is mapped as West Protection Unit and the line port that is mapped as West Working Unit are not on the same board, if possible.
NOTE
Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the same attributes.
Postrequisite
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 unidirectional cross-connections between the services and the protection channels, in addition to configuring the bidirectional cross-connections between the services and the working channels.
4-8
Issue 02 (2009-06-15)
5 Configuring SDH/PDH Services on the Per-NE Basis
Configuring SDH/PDH Services on the PerNE Basis
About This Chapter

The SDH/PDH services are classified into point-to-point services and SNCP services, according to the cross-connection type. 5.1 Numbering Schemes for SDH Timeslots Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or SDH radio links. 5.2 Creating Cross-Connections of Point-to-Point Services In a cross-connection of point-to-point services, one service source corresponds to one service sink. 5.3 Creating Cross-Connections for 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. 5.4 Setting the Automatic Switching Conditions of SNCP Services In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions. 5.5 Deleting the Cross-Connections of a Point-to-Point Service When a point-to-point service is not used, you can delete the cross-connections of this service to release the corresponding resources. 5.6 Deleting the Cross-Connections of a Service When a service is not used, you can delete the cross-connections of this service to release the corresponding resources. 5.7 Converting Normal Services into SNCP Services After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services. 5.8 Converting SNCP Services into Normal Services
Issue 02 (2009-06-15)
5-1
After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services.
5-2
Issue 02 (2009-06-15)
5.1 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, where 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, which is the default scheme adopted by the OptiX equipment.
Interleaved scheme This timeslot numbering scheme is also considered as line scheme, where 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 specific timeslot numbering scheme is required.
Figure 5-1 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
Issue 02 (2009-06-15)
5-3
Figure 5-2 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 VC-3 crossconnections and VC-12 cross-connections in a VC-4 path at the same time, 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.
5.2 Creating 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 source and sink boards must be configured. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Optional: Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot numbering policy used by the cross-connection. Step 3 Click Create. Then, the Create SDH Service dialog box is displayed. Step 4 Configure the cross-connections of the service.
5-4
Issue 02 (2009-06-15)
Step 5 Click OK.

NOTE
l l
When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may fail due to the limited number of licenses. The calculation of the required number of licenses is based on the total number of service timeslots of all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require the number of licenses that are used for 16xE1.
----End
Parameters
Parameter Level Value Range VC12/VC3/VC4 Default Value VC12 Description
l
This parameter indicates the level of the cross-connections. In the case of E1 services or data services in bound VC-12 paths, set this parameter to VC12. In the case of E3/T3 services or data services in bound VC-3 paths, set this parameter to VC3. If all the services in a VC-4 path are passed through the NE, set this parameter to VC4.
Issue 02 (2009-06-15)
5-5
Parameter Direction
Value Range Unidirectional, Bidirectional
Default Value Bidirectional
Description
l
When this parameter is set to Unidirectional, create the crossconnections from the service source to the service sink only. When this parameter is set to Bidirectional, create the crossconnections from the service source to the service sink and from the service sink to the service source. It is recommended that you set this parameter to Bidirectional.
Source Slot Source Port Source VC4
Sets the slot of the source service. This parameter indicates the port where the service source is located. This parameter indicates the number of the VC-4 path where the service source is located.
l
Source Timeslot Range(e.g.1,36)
This parameter indicates the timeslot range corresponding to the service source. This parameter can be set to a value or multiple values. When this parameter is set to multiples values, use "," to separate each value and use "" to indicate sequential numbers. For example, "1,3 6" indicates 1, 3, 4, 5, and 6. If the IF board works in the PDH mode, E1s/E3s 1n transmitted over radio correspond to VC-12/VC-3 timeslots 1 n. Ports 1n of E1 interface boards and E3/T3 interface boards correspond to VC-12/VC-3 timeslots 1n. The E1s 175 transmitted on the IFH2 board correspond to the 163 VC-12 timeslots of the first VC-4 and the 112 VC-12 timeslots of the second VC-4.
Sink Slot Sink Port Sink VC4
Sets the solt of the sink service. This parameter indicates the port where the service sink is located. This parameter indicates the number of the VC-4 path where the service sink is located.
5-6
Issue 02 (2009-06-15)
Parameter Sink Timeslot Range(e.g.1,36)
Value Range -
Default Value -
Description
l
This parameter indicates the timeslot range corresponding to the service sink. This parameter can be set to a value or multiple values. When this parameter is set to multiples values, use "," to separate each value and use "" to indicate sequential numbers. For example, "1,3 6" indicates 1, 3, 4, 5, and 6. If the IF board works in the PDH mode, E1s/E3s 1n transmitted over radio correspond to VC-12/VC-3 timeslots 1 n. Ports 1n of E1 interface boards and E3/T3 interface boards correspond to VC-12/VC3 timeslots 1n. The E1s 175 transmitted on the IFH2 board correspond to the 163 VC-12 timeslots of the first VC-4 and the 112 VC-12 timeslots of the second VC-4.
Activate Immediately
Yes, No
Yes
Sets whether to immediately activate the cross-connection. When you need to imposes the crossconnection immediately, it is recommended that you set this parameter to Yes.
5.3 Creating Cross-Connections for 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
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the source and the sink are must be configured.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot numbering policy used by the cross-connection. Step 3 Click Create SNCP. The system displays the Create SNCP Service dialog box.
Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
Step 5 Click OK.

NOTE
l l
When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may fail due to the limited number of licenses. The calculation of the required number of licenses is based on the total number of service timeslots of all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require the number of licenses that are used for 16xE1.
----End
Parameters
Parameter Service Type Value Range SNCP Default Value SNCP Description -
5-8
Issue 02 (2009-06-15)
Parameter Level
Value Range VC12, VC3, VC4
Default Value VC12
Description
l
Specifies the level of the crossconnection to be created. If the service is an E1 service or a data service that is bound with VC-12 paths, set this parameter to VC12. If the service is an E3/T3 service or a data service that is bound with VC-3 paths, set this parameter to VC3. If all the services in a VC-4 pass through the NE, set this parameter to VC4. 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. 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. It is recommended that you set this parameter to Revertive. When this parameter is set to Unidirectional, only the crossconnections in the SNCP receive direction are created. When this parameter is set to Bidirectional, both the crossconnections in the SNCP receive direction and the cross-connections in the SNCP transmit direction are created. It is recommended that you set this parameter to Bidirectional. When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. It is recommended that you use the default value because the SNCP cannot co-exist with other protection switching modes in the OptiX RTN 600.
Revertive Mode
Non-Revertive, Revertive
Non-Revertive
Direction
Unidirectional, Bidirectional
Bidirectional
Hold-off Time (100ms)
0 to 100
Issue 02 (2009-06-15)
5-9
Parameter WTR Time(s)
Default Value 600
Description
l
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value.
Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6)
Indicates the source slot of the service. Specifies the number of the VC-4 where the service source exists.
l
Specifies the timeslot range to which the service source corresponds. 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. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Sink Slot Sink VC4
Indicates the sink slot of the service. Specifies the number of the VC-4 where the service sink exists.
5-10
Issue 02 (2009-06-15)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description
l
Specifies the timeslot range to which the service sink corresponds. 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. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Configure SNCP Tangent Ring
Checked, Unchecked
Unchecked
After you select the Configure SNCP Tangent Ring check box, you can configure the SNCP services on tangent points of SNCP rings in a fast manner. Generally, it is not recommended to select this check box.
Activate Immediately
Yes, No
Yes
Sets whether to immediately activate the cross-connection that is configured. If you need to immediately deliver the crossconnection that is configured to NEs, set the value of this parameter to Yes.
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction is created. Hence, you need to configure a unidirectional cross-connection between the service and the working trail, and later, a unidirectional cross-connection between the service and the protection trail.
5.4 Setting the Automatic Switching Conditions of SNCP Services

In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions.
Issue 02 (2009-06-15)
5-11
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. An SNCP protection group at the VC-4 level must be configured.
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. Double-click Initiation Condition to which the working service corresponds. The system displays the Initiation Condition dialog box. Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection service corresponds. The system displays the Initiation Condition dialog box. Step 5 Repeat Step 3. Step 6 Click Apply. The system displays a prompt box asking you whether to carry out the switching. Step 7 Click Yes. ----End
Parameters
Parameter UNEQ Value Range Selected, Not selected Default Value Not selected Description
l
When this item is selected, the SNCP service considers the HP_UNEQ alarm as an SD switching condition. It is recommended that you use the default value.
5-12
Issue 02 (2009-06-15)
Parameter TIM
Value Range Selected, Not selected
Default Value Not selected
Description
l
When this item is selected, the SNCP service considers the HP_TIM alarm as an SD switching condition. It is recommended that you use the default value. When this item is selected, the SNCP service considers the B3_SD alarm as an SD switching condition. It is recommended that you use the default value. When this item is selected, the SNCP service considers the B3_EXC alarm as an SD switching condition. It is recommended that you use the default value.
SD
Not selected
EXC
Not selected
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation Condition of the protection service.
5.5 Deleting the Cross-Connections of a Point-to-Point Service

When a point-to-point service is not used, you can delete the cross-connections of this service to release the corresponding resources.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The cross-connections of the point-to-point service must be configured and the point-to-point service is not used.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Query the data. 1. Click Query. Then, the Confirm dialog box is displayed, prompting This operation will query service at the NE and update service date at the NM. Are you sure to continue?. 2.
Issue 02 (2009-06-15)
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded. 3. Click Close. Step 3 Select the cross-connection of the point-to-point service that needs to be deleted in CrossConnection. Step 4 Deactivate the service. 1. Click Deactivate. Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all selected services (only for activated services)?. Click OK. Another Confirm dialog box is displayed, prompting This services of the NE will be cleared by this operation. Are you sure to continue?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close. Click Delete. Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the selected services (only for inactive services)?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
2. 3. 4. 1.
Step 5 Delete the service.
2. 3.
Step 6 Click Query. At this time, the cross-connection of the point-to-point service is already deleted. ----End
5.6 Deleting the Cross-Connections of a Service

When a service is not used, you can delete the cross-connections of this service to release the corresponding resources.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The cross-connections of the service must be configured and the service is not be used.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Query the data. 1. Click Query. Then, the Confirm dialog box is displayed, prompting This operation will query service at the NE and update service date at the NM. Are you sure to continue?.
5-14
2. 3.
Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
Step 3 Select the cross-connection of the SNCP service that needs to be deleted in CrossConnection. Step 4 Deactivate the service. 1. Click Deactivate. Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all selected services (only for activated services?). 2. 3. 4. Click OK. Another Confirm dialog box is displayed, prompting This services of the NE will be cleared by this operation. Are you sure to continue?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
Step 5 Delete the service. 1. Click Delete. Then, the OK dialog box is displayed, prompting Are you sure to delete all the selected services (only for inactive services)?. 2. 3. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
Step 6 Click Query. At this time, the cross-connection of the SNCP service is already deleted. ----End
5.7 Converting Normal Services into SNCP Services

After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The unidirectional cross-connection of normal services must be configured and the source of the cross-connection must be a line board.
When this task is performed to convert a normal service into an SNCP service, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Optional: Query the data. 1. Click Query. Then, the Confirm dialog box is displayed, prompting This operation will query service at the NE and update service data at the NM. Are you sure to continue?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation Succeeded. Click Close.
2. 3.
Step 3 Select the bidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Expand to Unidirectional from the shortcut menu. Step 4 Select the unidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Convert to SNCP from the shortcut menu. Then, the Confirm dialog box is displayed, prompting If the normal service is change into a SNCP service, the service may be interrupted. Are you sure to continue?. Step 5 Click OK. Step 6 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
5-16
Issue 02 (2009-06-15)
Parameters
Parameter Revertive Mode Value Range Non-Revertive, Revertive Default Value Non-Revertive Description
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. 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. It is recommended that you set this parameter to Revertive.
Issue 02 (2009-06-15)
5-17
Parameter Hold-off Time (100ms)
Default Value 0
Description
l
When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. It is recommended that you use the default value because the SNCP cannot co-exist with other protection switching modes in the OptiX RTN 600. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value.
WTR Time(s)
300 to 720
600
Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6)
Indicates the source slot of the service. Specifies the number of the VC-4 where the service source exists.
l
Specifies the timeslot range to which the service source corresponds. 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, 36" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Sink Slot Sink VC4
Indicates the sink slot of the service. Specifies the number of the VC-4 where the service sink exists.
5-18
Issue 02 (2009-06-15)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description
l
Specifies the timeslot range to which the service sink corresponds. 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, 36" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later, you need to configure a unidirectional cross-connection between the service and the working trail, and a unidirectional cross-connection between the service and the protection trail. The normal service can be converted into the SNCP service both in the receive direction and the transmit direction only after the configuration.
5.8 Converting SNCP Services into Normal Services

After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The current service is transmitted in the working path. The SNCP cross-connection in the receive direction must be configured.
When this task is performed to convert an SNCP service into a normal service, the original services are not interrupted.
Issue 02 (2009-06-15)
5-19
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and choose Change to Normal Service from the shortcut menu. Step 3 Click OK. ----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path or the unidirectional cross-connection between the service 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.
5-20
Issue 02 (2009-06-15)
6 Configuring the Clock on the Per-NE Basis
Configuring the Clock on the Per-NE Basis
About This Chapter

All the transmission nodes on a digital transmission network must be synchronized. Otherwise, the overflow or exhaustion of the bits occurs in the buffer, which causes the sliding damage to the data flow. As a result, the data is incorrect. To ensure that all the NEs on the digital transmission network are synchronized, you need to configure the clock for each NE and need to configure the clock protection in the case of a complex network. 6.1 Clock Synchronization Scheme This section describes the clock synchronization schemes. You need choose the clock synchronization scheme for the OptiX RTN 600 (based on IDU 610/620) according to the actual networking architecture. 6.2 Configuring the Clock Sources This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock. 6.3 Configuring Protection for Clock Sources This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring networks, protection for the clock sources need to be implemented through the standard SSM protocol or extended SSM protocol. 6.4 Modifying the Parameters of the External Clock Output The NE outputs the 2 Mbit/s external clock regardless of the clock quality. 6.5 Customizing the Clock Parameters In certain situations, the user need modify the default switching conditions or self-defined quality of the clock sources.
Issue 02 (2009-06-15)
6-1
6.1 Clock Synchronization Scheme

This section describes the clock synchronization schemes. You need choose the clock synchronization scheme for the OptiX RTN 600 (based on IDU 610/620) according to the actual networking architecture.
Clock Synchronization Scheme for a Chain/Tree Network

The clock synchronization schemes for chain/tree networks are as follows:
l
If the main (first) node accesses a clock source (external clock or line clock), configure this clock source for this node. Configure the clock source of the higher-level radio link for other nodes. When the higher-level radio link adopts 1+1 protection, configure two clock sources for the corresponding node. Note that the clock source priority of the main radio link should be higher than the clock source priority of the standby radio link. When multiple higher-level radio links exist, (for example, when the radio link is configured with XPIC or N+1 protection), the node configures a microwave clock source for each radio link and allocates different clock priority levels based on the situation of each radio link. Do not configure the synchronization status message (SSM) or extended SSM protection.
l l
Figure 6-1 shows the clock synchronization scheme of a chain network.

l
The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence, the clock source priority levels are external clock source 1 and internal clock source in the descending order. The IF1A boards in slots 5 and 7 on NE2 form an IF 1+1 protection group (the board in slot 5 is the main board) and provide the radio link from NE1 to NE2. Hence, the clock source level priority levels are 5-IF1A-1, 7-IF1A-1, and internal clock source in the descending order. The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order. The IF1A board in slot 5 on NE4 provides the radio link from NE4 to NE3. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order. Do not configure the SSM or extended SSM protection.
6-2
Issue 02 (2009-06-15)
Figure 6-1 Clock synchronization scheme for a chain network

NE1 NE2 NE3 NE4
External 1/ Internal Master clock
5-IF1A-1/ 7-IF1A-1/ Internal
5-IF1A-1/ Internal
5-IF1A-1/ Internal
Figure 6-2 shows the clock synchronization scheme of a tree network.

l
The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source level priority levels are 4-SL1-1 and internal clock source in the descending order. The IFX boards in slots 5 and 7 on NE2 form an XPIC workgroup (the IFX board in slot 5 works on polarization V and the IFX board in slot 7 is works on polarization H) and provide the radio link from NE1 to NE2. Hence, the clock source level priority levels are 5-IF1A-1, 7-IF1A-1, and internal clock source in the descending order. The IF1A board in slot 5 on NE3 provides the radio link from NE3 to NE2. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order. The IF1A board in slot 5 on NE4 provides the radio link from NE4 to NE3. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order. Do not configure the SSM or extended SSM protection.
Issue 02 (2009-06-15)
6-3
Figure 6-2 Clock synchronization scheme for a tree network

NE3
NE1
NE2 5-IF1A-1/ Internal
NE4 4-SL1-1/ Internal 5-IFX-1/ 7-IFX-1/ Internal
Master clock
5-IF1A-1/ Internal
Clock Synchronization Scheme for a Ring Network

The clock synchronization schemes for a ring network formed by the OptiX RTN 600 equipment only or formed by the OptiX RTN 600 equipment and other OptiX equipment are as follows:
l
When the entire ring network line is an SDH line, set the SSM or extended SSM according to the clock synchronization schemes of an optical transmission network. When a PDH section exists on the line of the ring network, divide the ring network into two chains and set the synchronization according to the clock synchronization schemes of a chain network.
Figure 6-3 shows the clock synchronization scheme of a ring network of which the entire ring network line is an SDH line.
l l
The SSM or extended SSM protection is enabled on all the nodes in the ring network. The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence, the clock source priority levels are external clock source 1 and internal clock source in the descending order. The clock source priority levels of other nodes are the west clock source, east clock source, and internal clock source in the descending order.
6-4
Issue 02 (2009-06-15)
Figure 6-3 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line)
NE2 NE1 West/ East/ Internal West/ East/ Internal NE6
External 1/ Internal
West/ East/ Internal NE3 Master clock NE4 West/ East/ Internal NE5
West/ East/ Internal
Figure 6-4 shows the clock synchronization scheme of a ring network of which not the entire ring network line is an SDH line.
l
This ring network is formed by PDH microwave. Hence, divide the ring network at the main node NE1 into two chains: from NE1 to NE2 and from NE3 to NE4. The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source level priority levels are 4-SL1-1 and internal clock source in the descending order. NE2 traces the clock of the main node. Hence, the clock source level priority levels are the west clock source and internal clock source in the descending order. NE4 traces the clock of the main node. Hence, the clock source level priority levels are the east clock source and internal clock source in the descending order. NE3 traces the clock of NE4. Hence, the clock source level priority levels are the east clock source and internal clock source in the descending order. Do not configure the SSM or extended SSM protection.
Issue 02 (2009-06-15)
6-5
Figure 6-4 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line)
NE1
NE2 4-SL1-1/ Internal
NE4
West/ Internal
NE3
East/ Internal
Master clock
East/ Internal
Clock Synchronization Scheme for Networking with Convergence at Tributary Ports

Networking with convergence at tributary ports indicates that several OptiX RTN 600 NEs are converged to the higher-level OptiX RTN NE through the E1/E3 cable. The clock synchronization schemes for networking with convergence at tributary ports are as follows:
l l l
The higher-level NE accesses the clock source (external clock source or line clock source). The lower-level NEs trace the tributary clock sources (port 1 and port 5 of the PO1/PH1/ PD1 board can be used as the tributary clock sources). When a lower-level NE is connected to multiple hops of radio links, abnormal pointer adjustments may occur if the lower-level NE traces the tributary clock. Therefore, the lower-level NEs should trace the external clock output by the higher-level NE. Do not configure the SSM or extended SSM protection.
Figure 6-5shows the clock synchronization scheme for networking with convergence at tributary ports.
l
The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence, the clock source priority levels are external clock source 1 and internal clock source in the descending order. The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order. NE3 converges services TO NE2 through ports 14 of the PO1 board in slot 4. Hence, the clock source level priority levels are 4-PO1-1 and internal clock source in the descending order. Multiple microwave hops exist in the downstream of NE4. In this case, the downstream nodes will report point adjustments if NE4 adopts the tributary clock source. Hence, NE4
6-6
adopts the external clock output from NE2 as the external clock input to the PXC board in slot 1.
l
Do not configure the SSM or extended SSM protection.
Figure 6-5 Clock synchronization scheme for networking with convergence at tributary ports
NE3
NE1
NE2
4-PO1-1/ Internal NE4
External 1/ Internal
5-IF1A-1/ Internal
External/ Internal Master clock E1 External clock
Precautions for Making the Clock Synchronization Scheme

The precautions for making the clock synchronization scheme are as follows:
l
The number of the NEs on the long clock chain must not exceed 20. It is recommended that the long clock chain contains less than 10 NEs. If the long clock chain contains too many NEs, new clock sources need be added to the chain for use compensation. Use SDH interface boards to converge services at the convergence node. Thus, the clock signals can be passed over SDH signals not over PDH signals, which ensures the high quality of the clock.
6.2 Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The PXC boards and input/output clock source boards must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Priority from the Function Tree. Step 2 Click Create. The Add Clock Source dialog box is displayed. Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
Step 4 Click OK. Step 5 Optional: Repeat Step 2 to Step 4 to add other clock sources. Step 6 Optional: Select a clock source and click or to adjust the priority level of this clock source. The clock priority levels are arranged in the descending order from the first row to the last row. The internal clock source is fixed with the lowest priority. Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
6-8
Issue 02 (2009-06-15)
Parameters
Parameter Clock Source Value Range Default Value Description
l
External clock source 1 indicates the external clock source at the port of the PXC board in slot 1. External clock source 2 indicates the external clock source at the port of the PXC board in slot 3. IFH2-1(SDH) indicates the microwave clock source. IFH2-2(ETH) indicates the clock source of the synchronous Ethernet. The internal clock source is fixed with the lowest priority and indicates that the NE works in the free-run mode. Determine the clock sources and the corresponding clock source priority levels according to the clock synchronization schemes. This parameter indicates the type of the external clock source signal. Set this parameter depending on the external clock signal. Generally, the external clock signal is a 2 Mbit/s signal. This parameter is valid only when External Clock Source Mode is set to 2 Mbit/s. This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. This parameter need to be set only when the SSM or extended SSM is enabled. Generally, the external clock sources use the SA4 to pass the SSM.
External Clock Source Mode
2 Mbit/s, 2 MHz
2 Mbit/s
Synchronization Status Byte
SA4SA8
SA4
6.3 Configuring Protection for Clock Sources

This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring networks, protection for the clock sources need to be implemented through the standard SSM protocol or extended SSM protocol.
Issue 02 (2009-06-15)
6-9
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The clock source priority table must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Subnet Configuration from the Function Tree. Step 2 Enable the clock protection protocol. 1. 2. Click the Clock Subnet tab. Enable the clock protection protocol and set the protocol parameters.
3. 1. 2.
Click Apply. Click the SSM Output Control tab. Set the SSM output port.
Step 3 Set the SSM output port.
3. 1. 2.
Click Apply. Click the Clock ID Status tab. Set the clock ID output port.
Step 4 Optional: Set the clock ID output port.
6-10
Issue 02 (2009-06-15)
3.
Click Apply.
----End
Parameters
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 in 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 select the clock source with the highest quality and highest priority, thus preventing clock mutual tracing. The extended SSM protocol is the extension of the standard SSM protocol. It defines the unique ID for each clock source and uses the higher four bits of the S1 byte to pass the ID. The extended SSM protocol can be used to prevent the NEs from tracing their own clocks. If third-party equipment exists in the ring network, enable the SSM protocol. If only OptiX equipment exists in the ring network and clock mutual tracing can be prevented through certain configurations of the clock sources, the SSM protocol can also be enabled. If only OptiX equipment exists in the ring network, it is recommended that the extended SSM protocol is used. This parameter is used when the clock subnet need to be created on the NMS. The NEs that trace the same clock source should be allocated with the same clock subnet ID.
Affiliated Subnet
0255
Issue 02 (2009-06-15)
6-11
Parameter Clock Source ID
Value Range (None), 015
Default Value (None)
Description
l
This parameter is valid only when the SSM protocol is enabled. Allocate the clock source ID for the following clock sources only:

External clock sources 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
Control Status
Enabled, Disabled
Enabled
This parameter is valid only when the SSM protocol or the extended SSM protocol is enabled. This parameter indicates whether the SSM is output at the line port. When the line port is connected to an NE in the same clock subnet, set this parameter to Enabled; otherwise, set this parameter to Disabled. This parameter is valid only when the SSM protocol is enabled. This parameter indicates whether the clock source ID is output at the line port. When the line port is connected to an NE in the same clock subnet and the extended SSM protocol is enabled at the remote NE, set this parameter to Enabled; otherwise, set this parameter to Disabled.
Enable Status
Enabled, Disabled.
Enabled
6.4 Modifying the Parameters of the External Clock Output

The NE outputs the 2 Mbit/s external clock regardless of the clock quality.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The PXC board must be configured.
Precautions
In the OptiX RTN 600, external clock source 1 indicates the external clock on the PXC board in slot 1 and external clock source 2 indicates the external clock on the PXC board in slot 3.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Phase-Locked Source Output by External Clock from the Function Tree. Step 2 Modify the clock output parameters.
Parameters
Parameter External Clock Output Mode Value Range 2 Mbit/s, 2 MHz Default Value 2 Mbit/s Description
l
This parameter indicates the mode of the output clock. Set this parameter according to the requirements of the interconnected equipment. Generally, the output clock signal is a 2 Mbit/s signal. This parameter is valid only when External Clock Output Mode is set to 2 Mbit/s. This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. When this parameter is set to ALL, it indicates that each bit can transmit the SSM. It is recommended that this parameter takes the default value. This parameter indicates the lowest clock quality of the output clock. When the clock quality is lower than the parameter value, the signal is not output. When this parameter is set to Threshold Disabled, it indicates that the clock signal is continuously output. It is recommended that this parameter takes the default value.
External Clock Output Timeslot
SA4SA8, ALL
ALL
External Clock Output Threshold
Threshold Disabled, Not Inferior to G. 813 SETS Signal, Not Inferior to G. 812 Local Clock Signal, Not Inferior to G.812 Transit Clock Signal, Not Inferior to G.811 Clock Signal
Threshold Disabled
Issue 02 (2009-06-15)
6-13
Parameter 2M Phase-Locked Source Fail Condition
Value Range No Failure Condition, AIS, LOF, AIS OR LOF
Default Value No Failure Condition
Description
l
This parameter indicates the conditions when the 2M phase-locked clock source fails. It is recommended that you use the default value. This parameter is valid only when 2M Phase-Locked Source Fail Condition is No Failure Condition. This parameter indicates the action of the 2M phase-locked loop when 2M PhaseLocked Source Fail Condition is met. It is recommended that you use the default value.
2M Phase-Locked Source Fail Action
Shut Down Output, 2M Output S1 Byte Unavailable, Send AIS
Shut Down Output
6.5 Customizing the Clock Parameters

In certain situations, the user need modify the default switching conditions or self-defined quality of the clock sources. Table 6-1 lists the navigation path for customizing the clock parameters. For details, see the Online help of the NMS. Table 6-1 Navigation path for customizing the clock parameters Clock Parameter Clock source switching condition Navigation Path Select the NE from the Object Tree in the NE Explore. Choose Configuration > Clock > Clock Source Switching from the Function Tree. Select the NE from the Object Tree in the NE Explore. Choose Configuration > Clock > Clock Subnet Configuration from the Function Tree.
Clock source quality
6-14
Issue 02 (2009-06-15)
7 Configuring SDH/PDH Microwave-Based Ethernet Services on the Per-NE Basis
Configuring SDH/PDH Microwave-Based Ethernet Services on the Per-NE Basis
About This Chapter

In the case of the SDH/PDH microwave, Ethernet services are transmitted in a way similar to the Ethernet over SDH transmission mode. Hence, you need to configure the mapping relation between the Ethernet services and VCTRUNKs and configure the cross-connections between the paths bound with the VCTRUNKs and the timeslots contained in the cable, during the configuration of Ethernet services. 7.1 Configuration Flow This topic describes the configuration processes related to the Ethernet services. Before you configure Ethernet services according to the configuration flow, complete the basic NE configurations according to the flow for configuring SDH/PDH services based on the SDH/PDH microwave (including the configuration of the NE management and radio links). 7.2 Configuration Example (Point-to-Point EPL Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the point-to-point EPL service requirements. 7.3 Configuration Example (PORT-Shared EVPL Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the PORT-shared EVPL service requirements. 7.4 Configuration Example (VCTRUNK-Shared EVPL Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the VCTRUNK-shared EVPL service requirements. 7.5 Configuration Example (802.1d Bridge-Based EPLAN Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the requirements for the 802.1d bridge-based EPLAN services. 7.6 Configuration Example (802.1q Bridge-Based EVPLAN Services)
Issue 02 (2009-06-15)
7-1
This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the requirements for the 802.1q bridge-based EVPLAN services.
7-2
Issue 02 (2009-06-15)
7.1 Configuration Flow

This topic describes the configuration processes related to the Ethernet services. Before you configure Ethernet services according to the configuration flow, complete the basic NE configurations according to the flow for configuring SDH/PDH services based on the SDH/PDH microwave (including the configuration of the NE management and radio links). 7.1.1 Configuring Point-to-Point EPL Services Point-to-point EPL services are Ethernet transparent transmission services. The point-to-point EPL services are simple, and feature transparent transmission and dedicated bandwidth. 7.1.2 Configuring PORT-Shared EVPL Services The PORT-shared EVPL services are the EVPL services where the services in each VLAN of an Ethernet port are assigned with a dedicated bandwidth. In the case of the PORT-shared EVPL services, the client equipment needs to send data frames with VLAN tags. 7.1.3 Configuring VCTRUNK-Shared EVPL Services The VCTRUNK-shared EVPL services can meet the requirements of bandwidth-shared pointto-point virtual private line services for different users. 7.1.4 Configuring QinQ-Based EVPL Services The QinQ-based EVPL services can carry two layers of VLAN tags. 7.1.5 Configuring 802.1d Bridge-Based EPLAN Services A bridge is the functional unit that is used to connect two or more LANs. The services of different 802.1d bridges are isolated from each other, but the services in different VLANs of the same 802.1d bridge are not isolated from each other. The 802.1d bridge is applicable to EPLAN services. 7.1.6 Configuring 802.1q Bridge-Based EVPLAN Services A bridge is a functional unit that is used to connect two or more LANs. The services of different 802.1q bridges are isolated from each other and the services in different VLANs of the same 802.1q bridge are isolated from each other. The 802.1q bridge is applicable to EVPLAN services. 7.1.7 Configuring 802.1ad Bridge-Based EVPLAN Services The 802.1ad bridge-based EVPLAN services can use two layers of VLAN tags.
7.1.1 Configuring Point-to-Point EPL Services

Point-to-point EPL services are Ethernet transparent transmission services. The point-to-point EPL services are simple, and feature transparent transmission and dedicated bandwidth. Ethernet transparent transmission boards or Ethernet switching boards can be used to configure point-to-point EPL services. Table 7-1 Flow for configuring point-to-point EPL services by using Ethernet switching boards Procedur e 1 2 Operation Configuring external Ethernet ports Configuring internal Ethernet ports Remarks Required Required
Issue 02 (2009-06-15)
7-3
Procedur e 3
Operation Creating EPL services
Remarks
l
Required when the Ethernet switching boards are used Not required when the Ethernet transparent transmission boards are used
Creating cross-connections of Ethernet services
Required
7.1.2 Configuring PORT-Shared EVPL Services

The PORT-shared EVPL services are the EVPL services where the services in each VLAN of an Ethernet port are assigned with a dedicated bandwidth. In the case of the PORT-shared EVPL services, the client equipment needs to send data frames with VLAN tags. Ethernet switching boards are required for configuring the PORT-shared EVPL services. Table 7-2 Flow for configuring PORT-shared EVPL services Step 1 2 3 4 5 Operation Configuring external Ethernet ports Configure internal Ethernet ports Creating Ethernet private line services Creating the cross-connections of Ethernet services Configuring the QoS Remarks Required. Required. Required. Required. Optional. For details about the QoS, see the OptiX RTN 600 Radio Transmissio n System Feature Description.
NOTE
Configuring the QoS involves creating the flow, configuring the CAR, configuring the CoS, binding the CAR and CoS, and configuring the traffic shaping. For details about the QoS, see the OptiX RTN 600 Radio Transmission System Feature Description.
7-4
Issue 02 (2009-06-15)
7.1.3 Configuring VCTRUNK-Shared EVPL Services

The VCTRUNK-shared EVPL services can meet the requirements of bandwidth-shared pointto-point virtual private line services for different users. Ethernet switching boards are required for configuring VCTRUNK-shared EVPL services. Table 7-3 Flow for configuring VCTRUNK-shared EVPL services Step 1 2 3 4 5 Operation Configuring external Ethernet ports Configure internal Ethernet ports Creating Ethernet private line services Creating the cross-connections of Ethernet services Configuring the QoS Remarks Required. Required. Required. Required. Optional. For details about the QoS, see the OptiX RTN 600 Radio Transmissio n System Feature Description.
NOTE
Configuring the QoS involves creating the flow, configuring the CAR, configuring the CoS, binding the CAR and CoS, and configuring the traffic shaping. For details about the QoS, see the OptiX RTN 600 Radio Transmission System Feature Description.
7.1.4 Configuring QinQ-Based EVPL Services

The QinQ-based EVPL services can carry two layers of VLAN tags. For the method of configuring QinQ-based EVPL services, see the OptiX RTN 600 Radio Transmission System Feature Description.
7.1.5 Configuring 802.1d Bridge-Based EPLAN Services

A bridge is the functional unit that is used to connect two or more LANs. The services of different 802.1d bridges are isolated from each other, but the services in different VLANs of the same 802.1d bridge are not isolated from each other. The 802.1d bridge is applicable to EPLAN services. Ethernet switching boards are required for configuring the 802.1d bridge-based EPLAN services.
Table 7-4 Flow for configuring 802.1d bridge-based EPLAN services Step 1 2 3 4 Operation Configuring external Ethernet ports Configure internal Ethernet ports Creating Ethernet LAN services Modifying the mounted port of a bridge Remarks Required. Required. Required. Required when you need to set the port to the Spoke port. Required. Optional. Optional.
5 6 7
Creating the cross-connections of Ethernet services Configuring the Layer 2 switching feature Configuring the QoS
NOTE
Configuring the Layer 2 switching feature involves setting the MAC address table manually, configuring the spanning tree protocol, and modifying the aging time in the multicast table. For details about the Layer 2 switching feature, see the OptiX RTN 600 Radio Transmission System Feature Description. Configuring the QoS involves creating the flow, configuring the CAR, configuring the CoS, binding the CAR and CoS, and configuring the traffic shaping. For details about the QoS, see the OptiX RTN 600 Radio Transmission System Feature Description.
7.1.6 Configuring 802.1q Bridge-Based EVPLAN Services

A bridge is a functional unit that is used to connect two or more LANs. The services of different 802.1q bridges are isolated from each other and the services in different VLANs of the same 802.1q bridge are isolated from each other. The 802.1q bridge is applicable to EVPLAN services. Ethernet switching boards are required for configuring the 802.1q bridge-based EVPLAN services. Table 7-5 Flow for configuring 802.1q bridge-based EVPLAN services Step 1 2 3 Operation Configuring external Ethernet ports Configure internal Ethernet ports Creating Ethernet LAN services Remarks Required. Required. Required.
7-6
Issue 02 (2009-06-15)
Step 4
Operation Modifying the mounted port of a bridge
Remarks Required when you need to set the port to the Spoke port. Required. Required. Optional. Optional.
5 6 7 8
Creating the VLAN filtering table Creating the cross-connections of Ethernet services Configuring the Layer 2 switching feature Configuring the QoS
NOTE
Configuring the Layer 2 switching feature involves setting the MAC address table manually, configuring the spanning tree protocol, and modifying the aging time in the multicast table. For details about the Layer 2 switching feature, see the OptiX RTN 600 Radio Transmission System Feature Description. Configuring the QoS involves creating the flow, configuring the CAR, configuring the CoS, binding the CAR and CoS, and configuring the traffic shaping. For details about the QoS, see the OptiX RTN 600 Radio Transmission System Feature Description.
7.1.7 Configuring 802.1ad Bridge-Based EVPLAN Services

The 802.1ad bridge-based EVPLAN services can use two layers of VLAN tags. The 802.1ad bridge-based EVPLAN services are implemented based on the QinQ technology. For details, see the OptiX RTN 600 Radio Transmission System Feature Description.
7.2 Configuration Example (Point-to-Point EPL Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the point-to-point EPL service requirements. 7.2.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 7.2.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. 7.2.3 Configuring NE1 You can configure the Ethernet transparent transmission services of NE1 based on the parameters of the service planning, by using the NMS. 7.2.4 Configuring NE2
You can configure the point-to-point Ethernet private line services of NE2 based on the parameters of the service planning, by using the NMS.
7.2.1 Networking Diagram

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. As shown in Figure 7-1, NE1 and NE2 adopt the OptiX RTN 600 NEs configured with the IDU 620. The new service requirements are as follows:
l l l l
The two branches of User A that are located at NE1 and NE2 need communicate with each other over Ethernet. A 10 Mbit/s bandwidth is required. The two branches of User B that are located at NE1 and NE2 need communicate with each other over Ethernet. A 20 Mbit/s bandwidth is required. The service of User A need be isolated from the service of User B. The Ethernet equipment of User A and User B provide 100 Mbit/s Ethernet electrical ports of which the working mode is auto-negotiation, and does not support VLAN.
Figure 7-1 Networking diagram

User A1 NE 1 NE2 User A2
User B1
User B2
7.2.2 Service Planning

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. In the following example, NE1 and NE2 can use Ethernet transparent transmission boards to create point-to-point EPL services.
Board Configuration Information

Slot 8 on NE1/NE2 houses the EFT4 board. Figure 7-2 IDU board configuration
EXT IF1A FAN FAN
Slot 20
Slot7 Slot5 Slot3 Slot1
EXT EFT4 EXT EXT PH1 SCC SCC
EXT IF1A PXC PXC PXC PXC
7-8
Issue 02 (2009-06-15)
Ethernet Parameter Configuration

Figure 7-3 Configuring Ethernet services
NE1:8-EFT4
PORT1 User A1 PORT2 User B1 VCTRUNK1 VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-15 VCTRUNK1 VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-15
NE2:8-EFT4
PORT1 User A2 PORT2 User B2
SDH
Table 7-6 Parameters of external Ethernet ports Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length Flow Control NE1 8-EFT4 PORT1 Enabled AutoNegotiation 1522 Disabled PORT2 Enabled AutoNegotiation 1522 Disabled NE2 8-EFT4 PORT1 Enabled AutoNegotiation 1522 Disabled PORT2 Enabled AutoNegotiation 1522 Disabled
Table 7-7 Parameters of internal Ethernet ports Parameter Board Port Encapsulation Mapping Protocol LCAS Enabled Bound Path NE1 8-EFT4 VCTRUNK1 GFP VCTRUNK2 GFP NE2 8-EFT4 VCTRUNK1 GFP VCTRUNK2 GFP
Enabled VC4-2: VC12-1 VC12-5
Issue 02 (2009-06-15)
7-9
Timeslot Allocation Information

Figure 7-4 Timeslot allocation of Ethernet services
Station Timeslot NE1 5-IF1A-1 NE2 5-IF1A1-1
1#VC4
VC12:17-21 8-EFT4 8-EFT4 VC4-2:1-5 VC4-2:1-5 VC12:22-31 8-EFT4 8-EFT4 VC4-2:6-15 VC4-2:6-15 Add/Drop
The EPL service of User A is as follows:
Occupies VC-12 timeslots 1721 of the first VC-4 on the radio link between NE1 and NE2. Uses VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE1 and VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/ drop services. Occupies VC-12 timeslots 2231 of the first VC-4 on the radio link between NE1 and NE2. Uses VC-12 timeslots 615 in the second VC-4 of the EFT4 board in slot 8 of NE1 and VC-12 timeslots 615 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/ drop services.
The EPL service of User B is as follows:
7.2.3 Configuring NE1

You can configure the Ethernet transparent transmission services of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The EFT4 board must be added.
Procedure
Step 1 Configure Ethernet external ports. 1. In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the parameters, click Apply.
2.
7-10
Parameter Port
Value Range PORT1 PORT2
Description
l
The basic attributes of PORT1 and PORT2 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2.
Enabled/ Disabled Working Mode
Enabled Auto-Negotiation
In the case of the port that accesses services, set this parameter to Enabled. The Ethernet equipment of users work in auto-negotiation mode. Hence, the Working Mode of the external ports should be set to Auto-Negotiation.
Step 2 Configure Ethernet internal ports. 1. In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Set the parameters of VCTRUNK1 and VCTRUNK2. Set the encapsulation and mapping protocol used by the port. a. b. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters. After setting the parameters, click Apply. Value Range VCTRUN K1 GFP VCTRU NK2 Description
l l
2.
Paramete r Port Mapping Protocol 3.
The mapping protocol needs to be set for VCTRUNK1 and VCTRUNK2. In this example, Mapping Protocol is set to GFP.
Configure the LCAS function of the VCTRUNKs. a. b. Click the LCAS tab. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click Apply. Value Range VCTRU NK1 VCTRUN K2 Description Enabling LCAS needs to be set for VCTRUNK1 and VCTRUNK2.
Paramete r Port
Issue 02 (2009-06-15)
7-11
Paramete r Enabling LCAS
Value Range Enabled
Description
l l
In this example, the LCAS function is enabled. The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved.
4.
Set the VC paths to be bound with the VCTRUNKs. a. b. c. d. Click the Bound Path tab. Click Configuration. Then, the Bound Path Configuration dialog box is displayed. In Configurable Ports, select VCTRUNK1 and VCTRUNK2 as the ports to be configured. In Available Bound Paths, set Level and Service Direction of the bound paths. After setting the parameters, click OK. Then, click Yes in the dialog box that is displayed. Value Range VCTRUN K1 VC12 Bidirectional VCTRUN K2 Description In this example, VCTRUNK1 and VCTRUNK2 need to be bound with VC paths. In this example, the bound path is at the VC-12 level.
l
Paramete r Configura ble Ports Level Service Direction
If Service Direction is set to Bidirectional, the services from the service source to the service sink and from the service sink to the service source are created. In this example, this parameter adopts the default value.
Available Resources Available Timeslots
VC4-2 VC12-1 to VC12-5 VC12-6 to VC12-15
In this example, VC4-2 is the available resource.

l
VCTRUNK1 is bound with timeslots VC12-1 to VC12-5. VCTRUNK2 is bound with timeslots VC12-6 to VC12-15.
Activation Status
Activated
Indicates that VCTRUNK1 and VCTRUNK2 are active.
Step 3 Create the cross-connections of Ethernet services. 1. 2. In the NE Explorer, select NE1 from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Click Create. The Create SDH Service dialog box is displayed. After setting the parameters. Then, click OK.
7-12
l
Set the parameters of the cross-connections of VCTRUNK1 as follows. Parameter Level Direction Value Range VC12 Bidirectional Description In this example, the cross-connection is at the VC-12 level.
l
If Direction is set to Bidirectional, the services from the service source to the service sink and from the service sink to the service source are created. In this example, this parameter adopts the default value.
Source Source Timeslot Range(e.g.1,36) Sink Sink VC4 Sink Timeslot Range(e.g.1,36) Activate Immediately
5-IF1A 17-21
In this example, the 5-IF1A is the service source. In this example, the timeslots to which the service source corresponds are timeslots 17-21. In this example, the 8-EFT4 is the service sink. In this example, the service sink is located in VC4-2. In this example, the timeslots to which the service sink corresponds are timeslots 1-5. Delivers the configured cross-connection to NEs immediately.
8-EFT4 VC4-2 1-5 Yes
l
Source Source Timeslot Range(e.g.1,36)
5-IF1A 22-31
In this example, the 5-IF1A is the service source. In this example, the timeslots to which the service source corresponds are timeslots 22-31.
Issue 02 (2009-06-15)
7-13
Parameter Sink Sink VC4 Sink Timeslot Range(e.g.1,36) Activate Immediately
Value Range 8-EFT4 VC4-2 6-15
Description In this example, the 8-EFT4 is the service sink. In this example, the service sink is located in VC4-2. In this example, the timeslots to which the service sink corresponds are timeslots 6-15. Delivers the configured cross-connection to NEs immediately.
Yes
----End

You can configure the point-to-point Ethernet private line services of NE2 based on the parameters of the service planning, by using the NMS. The procedures for configuring NE2 are the same as the procedures for configuring NE1. For details, see 7.2.3 Configuring NE1.
7.3 Configuration Example (PORT-Shared EVPL Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the PORT-shared EVPL service requirements. 7.3.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 7.3.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. 7.3.3 Configuring NE1 You can configure the PORT-shared Ethernet private line services of NE1 based on the parameters of the service planning, by using the NMS. 7.3.4 Configuring NE2 and NE3 You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements.
As shown in Figure 7-5, NE1, NE2, and NE3 are the OptiX RTN 600 NEs that are configured with the IDU 620. 16xE1 services exist between NE1, NE2, and NE3. The new service requirements are as follows:
l
The headquarters C1 of User C are located at NE1 and the two branches of User C (C2 and C3) are located at NE2 and NE3. The services between C1 and C2 are transmitted in the VLAN of which the VLAN ID ranges from 100 to 110. The services between C1 and C3 are transmitted in the VLAN of which the VLAN ID ranges from 200 to 210. The services of C2 are isolated from the services of C3. The services of C2 and C3 require a 20 Mbit/s bandwidth respectively. The Ethernet equipment of C1, C2, and C3 provide 100 Mbit/s Ethernet electrical ports of which the working mode is auto-negotiation, and supports VLAN.

User C2 User C1 VLAN100-110 VLAN200-210 NE3 User C3 NE 1 NE2

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. In the following example, NE1 needs to use Ethernet switching boards to create PORT-shared EVPL services. NE2 and NE3 can use Ethernet transparent transmission boards to create PORTshared EVPL services.

Slot 8 of NE1 houses the EMS6 board. Slot 8 on NE2/NE3 houses the EFT4 board. Figure 7-6 IDU board configuration (NE1)
EXT IF1A FAN FAN
Slot 20
EXT EMS6 EXT EXT PD1 SCC SCC
Issue 02 (2009-06-15)
7-15
Figure 7-7 IDU board configuration (NE2 and NE3)

EXT FAN FAN
Slot 20

NE2:8-EFT4 NE1:8-EMS6
VCTRUNK1 VCTRUNK1 VC4-2:VC12:1-10
PORT1 User C2
PORT1 User C1
VC4-2:VC12:1-10 VCTRUNK2 VC4-2:VC12:11-20 VCTRUNK1 VC4-2:VC12:1-10
NE3:8-EFT4
PORT1 User C3
SDH
Table 7-8 Parameters of external Ethernet ports Parameter Board Port Enabled/Disabled Working Mode Maximum Frame Length Flow Control TAG Entry Detection NE1 8-EMS6 PORT1 Enabled Auto-Negotiation 1522 Disabled Tag Aware Enabled NE2 8-EFT4 PORT1 Enabled Auto-Negotiation 1522 Disabled NE3 8-EFT4 PORT1 Enabled Auto-Negotiation 1522 Disabled -
7-16
Issue 02 (2009-06-15)
Table 7-9 Parameters of internal Ethernet ports Parameter Board Port Encapsulation Mapping Protocol Enabling LCAS TAG Entry Detection Bound Path NE1 8-EMS6 VCTRUNK1 GFP VCTRUNK2 GFP NE2 8-EFT4 VCTRUNK1 GFP NE3 8-EFT4 VCTRUNK1 GFP
Enabled Tag Aware Enabled VC4-2: VC12-1 VC12-10
Enabled Tag Aware Enabled VC4-2: VC12-11 VC12-20
Table 7-10 Parameters of EPL services Parameter NE1 Private Line Service 1 Board Service Type Direction Source Port Source C-VLAN (e.g. 1,36) Sink Port Sink C-VLAN (e.g. 1,36) 8-EMS EPL Bidirectional PORT1 100-110 VCRTUNK1 100-110 PORT1 200-210 VCTRUNK2 200-210 Private Line Service 2

Station Timeslot NE2 5-IF1A-1 NE1 5-IF1A1-1 7-IF1A1-1 NE3 5-IF1A1-1
1#VC4
VC12:17-26 8-EMS6 8-EFT4 VC4-2:1-10 VC4-2:1-10 Add/Drop
VC12:17-26 8-EMS6 8-EFT4 VC4-2:11-20 VC4-2:1-10
Issue 02 (2009-06-15)
7-17
The EVPL service from C1 to C2 is as follows:
Occupies VC-12 timeslots 1726 of the first VC-4 on the radio link between NE1 and NE2. Uses VC-12 timeslots 110 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 110 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/ drop services. Occupies VC-12 timeslots 1726 of the first VC-4 on the radio link between NE1 and NE3. Uses VC-12 timeslots 1120 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 120 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop services.
The EVPL service from C1 to C3 is as follows:

You can configure the PORT-shared Ethernet private line services of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The EMS6 board must be added.
Procedure
Step 1 Configure Ethernet external ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 Description
l l
2.
Set the basic attributes of PORT1. The services of user C1 use PORT1.
Enabled AutoNegotiation
In the case of the port that accesses services, set this parameter to Enabled. The Ethernet equipment of users work in autonegotiation mode. Hence, the Working Mode of the external ports should be set to AutoNegotiation.
3.
7-18
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter Port
Value Range PORT1
Description
l l
The tag attributes of PORT1 need to be set. The services of user C1 use PORT1. If TAG is set to Tag Aware, the packets that carry VLAN tags are received. If TAG is set to Tag Aware, the packets that do not carry VLAN tags are discarded.
TAG
Tag Aware
Entry Detection
Enabled
In this example, the incoming packets from the port need to be checked according to the tag attributes.
Step 2 Configure Ethernet internal ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Set the parameters of VCTRUNK1 and VCTRUNK2. Set the encapsulation and mapping protocol used by the port. a. b. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters. After setting the parameters, click Apply. Value Range VCTRUN K1 GFP VCTRU NK2 Description
l l
2.
Paramete r Port Mapping Protocol
The encapsulation protocol needs to be set for VCTRUNK1 and VCTRUNK2. In this example, Mapping Protocol is set to GFP.
3.
Configure the LCAS function of the VCTRUNKs. a. b. Click the LCAS tab. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click Apply. Value Range VCTRU NK1 Enabled VCTRUN K2 Description Enabling LCAS needs to be set for VCTRUNK1 and VCTRUNK2.
l l
Paramete r Port Enabling LCAS
7-19
Issue 02 (2009-06-15)
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port TAG Value Range VCTRUNK1 Tag Aware VCTRUNK2 Description TAG Attributes need to be set for VCTRUNK1 and VCTRUNK2.
l
If TAG is set to Tag Aware, the packets that carry VLAN tags are received. If TAG is set to Tag Aware, the packets that do not carry VLAN tags are discarded.
Entry Detection
Enabled
5.
Set the VC paths to be bound with the VCTRUNKs. a. b. c. d. Click the Bound Path tab. Click Configuration. Then, the Bound Path Configuration dialog box is displayed. In Configurable Ports, select VCTRUNK1 as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths. After setting the parameters, click OK. Then, click Yes in the dialog box that is displayed. Value Range VCTRUN K1 VC12 Bidirectional VCTRUN K2 Description In this example, VCTRUNK1 and VCTRUNK2 need to be bound with VC paths. In this example, the bound path is at the VC-12 level.
l
VC4-2 VC12-1 to VC12-10 VC12-11 to VC12-20

l
7-20
Issue 02 (2009-06-15)
Paramete r Activation Status
Value Range Activated
Description Indicates that VCTRUNK1 and VCTRUNK2 are active.
Step 3 Create Ethernet private line services. 1. 2. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click New. The Create Ethernet Line Service dialog box is displayed. After setting the parameters, click OK.
l
Set the parameters of the Ethernet private line services on PORT1 and VCTRUNK1 as follows. Parameter Service Direction Value Range Bidirectional Description
l
Source Port Source VLAN (e.g. 1,3-6) Sink Port Sink VLAN (e.g. 1,3-6)
PORT1 100-110 VCTRUNK1 100-110
In this example, PORT1 is the service source port. The services whose VLAN IDs range from 100 to 110 are the source services. In this example, the VCTRUNK1 is the service sink port. The services whose VLAN IDs range from 100 to 110 are the sink services.
l
Source Port
PORT1
In this example, PORT1 is the service source port.

7-21
Issue 02 (2009-06-15)
Parameter Source VLAN (e.g. 1,3-6) Sink Port Sink VLAN (e.g. 1,3-6)
Value Range 200-210 VCTRUNK2 200-210
Description The services whose VLAN IDs range from 200 to 210 are the source services. In this example, the VCTRUNK2 is the service sink port. The services whose VLAN IDs range from 200 to 210 are the sink services.
l
l
When Direction is set to Bidirectional, create the cross-connections from the service source to the service sink and from the service sink to the service source. In this example, this parameter adopts the default value.
Source Source Timeslot Range(e.g.1,3 6) Sink Sink VC4 Sink Timeslot Range(e.g.1,3 6) Activate Immediately
5-IF1A 17-26
8-EMS6 VC4-2 1-10
In this example, the 8-EMS6 is the service sink. In this example, the service sink is located in VC4-2. In this example, the timeslots to which the service sink corresponds are timeslots 1-10. Delivers the configured cross-connection to NEs immediately.
Yes
Set the parameters of the cross-connections of VCTRUNK2 as follows.
7-22
Issue 02 (2009-06-15)
Parameter Level Direction
Value Range VC12 Bidirectional
Description In this example, the cross-connection is at the VC-12 level.

l
7-IF1A 17-26
8-EMS6 VC4-2 11-20
In this example, the 8-EMS6 is the service sink. In this example, the service sink is located in VC4-2. In this example, the timeslots to which the service sink corresponds are timeslots 1120. Delivers the configured cross-connection to NEs immediately.
Yes
----End
7.3.4 Configuring NE2 and NE3

You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS. The Ethernet services of NE2 and NE3 are point-to-point EPL services, and therefore should be configured according to the configuration example of point-to-point EPL services. For details, see 7.2.3 Configuring NE1.
7.4 Configuration Example (VCTRUNK-Shared EVPL Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the VCTRUNK-shared EVPL service requirements. 7.4.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements.
7.4.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. 7.4.3 Configuring NE1 You can configure the VCTRUNK-shared Ethernet private line services of NE1 based on the parameters of the service planning, by using the NMS. 7.4.4 Configuring NE2 You can configure the VCTRUNK-shared Ethernet private line services of NE2 based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. As shown in Figure 7-10, NE1 and NE2 are the OptiX RTN 600 NEs configured with the IDU 620. 16xE1 services exist between NE1 and NE2. The new service requirements are as follows:
l
The two branches of User D are located at NE1 and NE2, and need to communicate with each other. The two branches of User E are located at NE1 and NE2, and need to communicate with each other. The services of User D need to be isolated from the services of User E. The traffic of User D and User E, however, is supplementary to each other, and thus can share the 20 Mbit/s bandwidth. The Ethernet equipment of User D and User E provide 100 Mbit/s Ethernet electrical ports of which the working mode is auto-negotiation, and does not support VLAN.

User D1 NE 1 NE2 User D2 12
User E1
User E2

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. In the following example, NE1 and NE2 need to use Ethernet switching boards to create VCTRUNK-shared EVPL services.

Slot 8 on NE1/NE2 houses the EMS6 board. Figure 7-11 IDU board configuration (NE1 and NE2)
EXT FAN FAN
Slot 20
EXT EMS6 EXT EXT PH1 SCC SCC

NE1:8-EMS6
PORT1 User D1 PORT2 User E1 EPL1
VCTRUNK1
NE2:8-EMS6
EPL1
VCTRUNK1 VC4-2:VC12:1-10
PORT1 User D2 PORT2 User E2
EPL2
VC4-2:VC12:1-10
EPL2
SDH
Table 7-11 Parameters of external Ethernet ports Parameter Board Port Enabled/ Disabled Working Mode Maximum Frame Length Flow Control TAG Entry Detection Default VLAN ID
Issue 02 (2009-06-15)
NE1 8-EMS6 PORT1 Enabled AutoNegotiation 1522 Disabled Access Enabled 100 PORT2 Enabled AutoNegotiation 1522 Disabled Access Enabled 200
NE2 8-EMS6 PORT1 Enabled AutoNegotiation 1522 Disabled Access Enabled 100 PORT2 Enabled AutoNegotiation 1522 Disabled Access Enabled 200
7-25
Parameter VLAN Priority
NE1 0 0
NE2 0 0
Table 7-12 Parameters of internal Ethernet ports Parameter Board Port Encapsulation Mapping Protocol Enabling LCAS TAG Entry Detection Bound Path NE1 8-EMS6 VCTRUNK1 GFP Enabled Tag Aware Enabled VC4-2: VC12-1VC12-10 NE2 8-EMS6 VCTRUNK1 GFP Enabled Tag Aware Enabled VC4-2: VC12-1VC12-10
Table 7-13 Parameters of EPL services Parameter NE1 EPL Service 1 Board Service Type Direction Source Port Source CVLAN (e.g. 1,36) Sink Port Sink C-VLAN (e.g. 1,36) 8-EMS EPL Bidirectional PORT1 100 PORT2 200 EPL Service 2 NE2 EPL Service 1 8-EMS EPL Bidirectional PORT1 100 PORT2 200 EPL Service 2
VCRTUNK1 100
VCRTUNK1 200
VCTRUNK2 100
VCTRUNK2 200
7-26
Issue 02 (2009-06-15)

Station Timeslot NE1 5-IF1A-1 NE2 5-IF1A1-1
1#VC4
VC12:17-26 8-EMS6 VC4-2:1-10 Add/Drop 8-EMS6 VC4-2:1-10
The VCTRUNK-shared EVPL services of User D and User E occupy VC-12 timeslots 17 26 in the first VC-4 on the radio link from NE1 to NE2. VC-12 timeslots 110 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 110 in the second VC-4 of the EMS6 board in slot 8 of NE2 are used to add/ drop the services.

You can configure the VCTRUNK-shared Ethernet private line services of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
Procedure
Step 1 Configure Ethernet external ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 PORT2 Description
l
2.
The basic attributes of PORT1 and PORT2 need to be set. The services of user D1 use PORT1 and the services of user E1 use PORT2.
Enabled/ Disabled
Issue 02 (2009-06-15)
Enabled
In the case of the port that accesses services, set this parameter to Enabled.
7-27
Parameter Working Mode
Value Range Auto-Negotiation
Description The Ethernet equipment of users work in auto-negotiation mode. Hence, the Working Mode of the external ports should be set to Auto-Negotiation.
3.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 PORT2 Description
l
The tag attributes of PORT1 and PORT2 need to be set. The services of user D1 use PORT1 and the services of user E1 use PORT2.
TAG
Access
If TAG is set to Access:

l
The packets that carry VLAN tags are discarded. The packets that do not carry VLAN tags are tagged with Default VLAN ID and are then received. In this example, Default VLAN ID is set to 100 for PORT1. In this example, Default VLAN ID is set to 200 for PORT2.
Default VLAN ID
100
200
Entry Detection
Enabled
Step 2 Configure Ethernet internal ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Set the encapsulation and mapping protocol used by the port. a. b. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters. After setting the parameters, click Apply. Value Range VCTRUNK 1 GFP Description
l l
2.
Parameter Port Mapping Protocol

7-28
The encapsulation protocol of VCTRUNK1 needs to be set. In this example, Mapping Protocol is set to GPF.
Issue 02 (2009-06-15)
3.
Configure the LCAS function of the VCTRUNK. a. b. Click the LCAS tab. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click Apply. Value Range VCTRUN K1 Enabled Description In this example, Enabling LCAS needs to be set for VCTRUNK1.
l l
Parameter Port Enabling LCAS
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port TAG Value Range VCTRUNK1 Tag Aware Description The tag attributes of VCTRUNK1 need to be set.
l
If TAG is set to Tag Aware, the packets that carry VLAN tags are received. If TAG is set to Tag Aware, the packets that do not carry VLAN tags are discarded.
Entry Detection
Enabled
5.
Set the VC paths to be bound with the VCTRUNKs. a. b. c. d. Click the Bound Path tab. Click Configuration. Then, the Bound Path Configuration dialog box is displayed. In Configurable Ports, select VCTRUNK1 as the port to be bound. In Available Bound Paths, set Level and Direction of the bound paths. After setting the parameters, click OK. Then, click Yes in the dialog box that is displayed. Value Range VCTRUNK1 VC12 Description In this example, VCTRUNK1 needs to be bound with VC paths. In this example, the bound path is at the VC-12 level.
Paramete r Configura ble Ports Level
Issue 02 (2009-06-15)
7-29
Paramete r Service Direction
Value Range Bidirectional
Description
l
VC4-2 VC12-1 to VC12-10

l
Activation Status
Activated
Step 3 Create Ethernet private line services. 1. 2. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click New. The Create Ethernet Line Service dialog box is displayed. After setting the parameters, click OK.
l
l
PORT1 100 VCTRUNK1 100
In this example, PORT1 is the service source port. The service that has the VLAN ID of 100 is the source service. In this example, VCTRUNK1 is the service sink port. The service that has the VLAN ID of 100 is the sink service.
7-30
Issue 02 (2009-06-15)
l
l
PORT2 200 VCTRUNK1 200
In this example, PORT2 is the service source port. The service that has the VLAN ID of 200 is the source service. In this example, VCTRUNK1 is the service sink port. The service that has the VLAN ID of 200 is the sink service.
Step 4 Create the cross-connections of Ethernet services. 1. 2. In the NE Explorer, select NE1 and then choose Configuration > SDH Service Configuration from the Function Tree. Click Create. Then, the Create SDH Service dialog box is displayed. Click OK. Value Range VC12 Bidirectional Description In this example, the cross-connection is at the VC-12 level.
l
Source Source Timeslot Range(e.g.1,3 6) Sink Sink VC4
5-IF1A 17-26
In this example, the 5-IF1A is the service source. In this example, the timeslots to which the service source corresponds are timeslots 17-26. In this example, the 8-EMS6 is the service sink. In this example, the service sink is located in VC4-2.
8-EMS6 VC4-2
Issue 02 (2009-06-15)
7-31
Parameter Sink Timeslot Range(e.g.1,3 6) Activate Immediately
Value Range 1-10
Description In this example, the timeslots to which the service sink corresponds are timeslots 1-10. Delivers the configured cross-connection to NEs immediately.
Yes
----End

You can configure the VCTRUNK-shared Ethernet private line services of NE2 based on the parameters of the service planning, by using the NMS. The procedures for configuring NE2 are the same as the procedures for configuring NE1. For details, see 7.4.3 Configuring NE1.
7.5 Configuration Example (802.1d Bridge-Based EPLAN Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the requirements for the 802.1d bridge-based EPLAN services. 7.5.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 7.5.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. 7.5.3 Configuring NE1 You can configure the transparent bridge-based Ethernet LAN services of NE1 based on the parameters of the service planning, by using the NMS. 7.5.4 Configuring NE2 and NE3 You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. As shown in Figure 7-14, NE1, NE2, and NE3 are the OptiX RTN 600 NEs that are configured with the IDU 620. 16xE1 services exist between NE1, NE2, and NE3. The new service requirements are as follows:
l
The three branches of User F, which are F1, F2, and F3, are located at NE1, NE2, and NE3. F1 need communicate with F2 and F3, and thus a 10 Mbit/s bandwidth is required. Communication is not required between F2 and F3. The Ethernet equipment of User F provides 100 Mbit/s Ethernet electrical ports, of which the working mode is auto-negotiation, and supports VLAN. The VLAN ID and the number of the VLANs are unknown and may be changed.

NE2 User F2
NE 1 User F1
NE3 User F3

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. In the following example, the 802.1q VB is used to implement EPLAN services of which the user VLAN is not defined. NE1 needs to be configured with Ethernet switching boards. NE2 and NE3 need to be configured with Ethernet transparent transmission boards.

EXT IF1A FAN FAN
Slot 20
Issue 02 (2009-06-15)
7-33

EXT FAN FAN
Slot 20

NE2:8-EFT4 NE1:8-EMS6
VCTRUNK1 VCTRUNK1 VC4-2:VC12:1-5
PORT1 User F2
PORT1 User F1
VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-10
NE3:8-EFT4
VCTRUNK1 VC4-2:VC12:1-5
VB1
PORT1 User F3
SDH
Table 7-14 Parameters of external Ethernet ports Parameter Port Enabled/Disabled Working Mode Maximum Frame Length Flow Control Entry Detection NE1 PORT1 Enabled Auto-Negotiation 1522 Disabled Disabled NE2 PORT1 Enabled Auto-Negotiation 1522 Disabled NE3 PORT1 Enabled Auto-Negotiation 1522 Disabled -
Table 7-15 Parameters of internal Ethernet ports Parameter Port

7-34
NE1 VCTRUNK1 VCTRUNK2
NE2 VCTRUNK1
NE3 VCTRUNK1
Issue 02 (2009-06-15)
Parameter Encapsulation Mapping Protocol Enabling LCAS Entry Detection Bound Path
NE1 GFP GFP
NE2 GFP
NE3 GFP
Enabled Disabled VC4-2: VC12-1 VC12-5
Enabled Disabled VC4-2: VC12-6 VC12-10
Table 7-16 Parameters of Ethernet LAN services Parameter Board VB Name VB Type Bridge Switch Mode VB Mount Port Hub/Spoke PORT1 VCTRUNK1 VCTRUNK2 Ethernet LAN services of NE1 8-EMS VB1 802.1d IVL/Ingress Filter Enable PORT1, VCTRUNK1, VCTRUNK2 Hub Spoke Spoke

1#VC4
VC12:17-21 8-EMS6 8-EFT4 VC4-2:1-5 VC4-2:1-5 Add/Drop
VC12:17-21 8-EMS6 8-EFT4 8-EMS6 VC4-2:6-10 VC4-2:1-5 VC4-2:6-15
Issue 02 (2009-06-15)
7-35

l
The Ethernet LAN service of User F occupies VC-12 timeslots 1721 in the first VC-4 on the radio link from NE1 to NE2 and VC-12 timeslots 1721 in the first VC-4 on the radio link from NE1 to NE3. VC-12 timeslots 15 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop the Ethernet LAN service from NE1 to NE2. VC-12 timeslots 610 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop the Ethernet LAN service from NE1 to NE3.

You can configure the transparent bridge-based Ethernet LAN services of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
Procedure
Step 1 Configure Ethernet external ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 Description
l l
2.
The basic attributes of PORT1 need to be set. The services of user F1 use PORT1.
In the case of the port that accesses services, set this parameter to Enabled. The Ethernet equipment of users work in autonegotiation mode. Hence, the Working Mode of the external ports should be set to AutoNegotiation.
3.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 Description
l l
The tag attributes of PORT1 need to be set. The services of user F1 use PORT1.
Entry Detection
Disabled
If Entry Detection is set to Disabled, the VLAN IDs of the packets are not checked.
Issue 02 (2009-06-15)
7-36
Step 2 Configure Ethernet internal ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Set the parameters of VCTRCUNK1 and VCTRCUNK2. Set the encapsulation and mapping protocol used by the port. a. b. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters. After setting the parameters, click Apply. Value Range VCTRUN K1 GFP VCTRU NK2 Description
l l
2.
Paramete r Port Mapping Protocol
The encapsulation protocol needs to be set for VCTRUNK1 and VCTRUNK2. In this example, Mapping Protocol is set to GFP.
3.
Configure the LCAS function of the VCTRUNKs. a. b. Click the LCAS tab. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click Apply. Value Range VCTRU NK1 Enabled VCTRUN K2 Description Enabling LCAS needs to be set for VCTRUNK1 and VCTRUNK2.
l l
Paramete r Port Enabling LCAS
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Entry Detection Value Range VCTRUNK1 Disabled VCTRUNK2 Description TAG Attributes need to be set for VCTRUNK1 and VCTRUNK2. If Entry Detection is set to Disabled, the VLAN IDs of the packets are not checked.
5.
Issue 02 (2009-06-15)
Set the VC paths to be bound with the VCTRUNKs.

a. b. c. d.
Click the Bound Path tab. Click Configuration. Then, the Bound Path Configuration dialog box is displayed. In Configurable Ports, select VCTRUNK1 as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths. After setting the parameters, click OK. Then, click Yes in the dialog box that is displayed. Value Range VCTRUN K1 VC12 Bidirectional VCTRUN K2 Description In this example, VCTRUNK1 and VCTRUNK2 need to be bound with VC paths. In this example, the bound path is at the VC-12 level.
l
VC4-2 VC12-1 to VC12-5 VC12-6 to VC12-10

l
Activation Status
Activated
Step 3 Create Ethernet LAN services. 1. 2. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters as follows. Parameter VB Name VB Type Bridge Switch Mode Value Range VB1 802.1d SVL/Ingress Filter Disable (802.1d) Description In this example, VB Name is set to VB1. In this example, an IEEE 802.1d bridge is created. In this example, a transparent bridge is created, and the VLAN IDs of the packets over each port need not be checked.
3.
Click Configure Mount. The Service Mount Configuration dialog box is displayed. After setting the parameters, click OK.
7-38
Parameter selected forwarding ports 4. 1. 2. Click OK.
Value Range PORT1, VCTRUNK1, VCTRUNK2
Description PORT1, VCTRUNK1, and VCTRUNK2 are connected to the bridge.
Step 4 Modify the mounted port of bridge. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select the created bridge. Click the Service Mount tab. After setting the parameters, click Apply. Paramet er Mount Port Value Range PORT1 VCTRUN K1 VCTRUN K2 Description
l
Select PORT1, VCTRUNK1, and VCTRUNK2 as the mount ports. Only the port that is selected as Mount Port of a bridge functions in the packet forwarding process of the bridge.
Hub/ Spoke
Hub
Spoke
Spoke
The Spoke ports cannot access each other. The Hub port and the Spoke port can access each other. The Hub ports can access each other. Indicates that the VCTRUNK is active.
Activatio n Status
Activated
l
Set the parameters of the cross-connections of VCTRUNK1 as follows. Parameter Level Value Range VC12 Description In this example, the cross-connection is at the VC-12 level.
Issue 02 (2009-06-15)
7-39
Parameter Direction
Value Range Bidirectional
Description
l
5-IF1A 17-21
8-EMS6 VC4-2 1-5
Yes
l
Source Source Timeslot Range(e.g.1,3 6) Sink Sink VC4
7-IF1A 17-21
8-EMS6 VC4-2
In this example, the 8-EMS6 is the service sink. In this example, the service sink is located in VC4-2.
Issue 02 (2009-06-15)
7-40
Parameter Sink Timeslot Range(e.g.1,3 6) Activate Immediately
Value Range 6-10
Description In this example, the timeslots to which the service sink corresponds are timeslots 6-10. Delivers the configured cross-connection to NEs immediately.
Yes
----End

You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS. The Ethernet service of NE2/NE3 is a point-to-point EPL service, and therefore should be configured according to the configuration example of point-to-point EPL services. For details, see 7.2.3 Configuring NE1.
7.6 Configuration Example (802.1q Bridge-Based EVPLAN Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the requirements for the 802.1q bridge-based EVPLAN services. 7.6.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 7.6.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. 7.6.3 Configuring NE1 You can configure the 802.1q bridge-based EVPLAN services of NE1 based on the parameters of the service planning, by using the NMS. 7.6.4 Configuring NE2 and NE3 You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. As shown in Figure 7-19, NE1, NE2, and NE3 are the OptiX RTN 600 NEs that are configured with the IDU 620. 16xE1 services exist between NE1, NE2, and NE3. The new service requirements are as follows:

l l l l
The three branches of User G are located at NE1, NE2, and NE3 respectively, need form a LAN, and share a 10 Mbit/s bandwidth. The three branches of User H are located at NE1, NE2, and NE3 respectively, need form a LAN, and share a 20 Mbit/s bandwidth. The service of User G need be isolated from the service of User H. The Ethernet equipment of User G and User H provide 100 Mbit/s Ethernet electrical ports of which the working mode is auto-negotiation, and does not support VLAN.

NE2 User G2
User G1 NE 1
User H2
User H1 NE3 User G3
User H3

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the parameters that are required for configuring the new Ethernet services of the NEs. In the following example, NE1 needs to use Ethernet switching boards to create Ethernet LAN services. NE2 and NE3 can use Ethernet transparent transmission boards to create Ethernet LAN services.

EXT IF1A FAN FAN
Slot 20
7-42
Issue 02 (2009-06-15)

EXT FAN FAN
Slot 20
Configuring Ethernet Services

Based on the networking diagram, you can plan the configuration diagram and parameters of the Ethernet services on the two VLANs that are implemented by using the 802.1q network bridge. Figure 7-22 Configuring Ethernet services
NE2:8-EFT4
VCTRUNK1
NE1:8-EMS6
VLAN 100
PORT1 User G1 VCTRUNK1 VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-10
VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-15
PORT1 User G2 PORT2 User H2
VLAN 200
PORT2 User H1
VCTRUNK3 VC4-2:VC12:11-20 VCTRUNK4 VC4-2:VC12:21-30 VCTRUNK1 VC4-2:VC12:1-5 VCTRUNK2 VC4-2:VC12:6-15
NE3:8-EFT4
PORT1 User G3 PORT2 User H3
VB1
SDH
Table 7-17 Parameters of external Ethernet ports Paramete r Board Port Enabled/ Disabled NE1 8-EMS6 PORT1 Enabled PORT2 Enabled NE2 8-EFT4 PORT1 Enabled PORT2 Enabled NE3 8-EFT4 PORT1 Enabled PORT2 Enabled
Issue 02 (2009-06-15)
7-43
Paramete r Working Mode Maximum Frame Length Flow Control TAG Entry Detection Default VLAN ID VLAN Priority
NE1 AutoNegotiatio n 1522 AutoNegotiatio n 1522
Disabled Access Enabled 100 0
Disabled Access Enabled 200 0
Disabled -
Disabled -
Disabled -
Disabled -
Table 7-18 Parameters of internal Ethernet ports Param eter Board Port Encaps ulation Mappin g Protoco l Enablin g LCAS TAG Entry Detecti on NE1 8-EMS6 VCTR UNK1 GFP VCTR UNK2 GFP VCTR UNK3 GFP VCTR UNK4 GFP NE2 8-EFT4 VCTR UNK1 GFP VCTR UNK2 GFP NE3 8-EFT4 VCTR UNK1 GFP VCTR UNK2 GFP
Enable d Access Enable d
Enable d -
Enable d -
Enable d -
Enable d -
7-44
Issue 02 (2009-06-15)
Param eter Default VLAN ID VLAN Priority Bound Path
NE1 100 100 200 200
NE2 -
NE3 -
0 VC4-2: VC121 VC125
0 VC4-2: VC126 VC1210
0 VC4-2: VC1211 VC1220
0 VC4-2: VC1221 VC1230
VC4-2: VC121 VC125
VC4-2: VC126 VC1215
VC4-2: VC121 VC125
VC4-2: VC126 VC1215
Table 7-19 Parameters of Ethernet LAN services Parameter Board VB Name VB Type Bridge Switch Mode Mount Port VLAN Filtering Table Filtering Table VLAN ID Forwarding Port Ethernet LAN services of NE1 8-EMS VB1 802.1q IVL/Ingress Filter Enable PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3, VCTRUNK4 VLAN Filtering Table 1 100 PORT1, VCTRUNK1, VCTRUNK2 VLAN Filtering Table 2 200 PORT2, VCTRUNK3, VCTRUNK4

1#VC4
VC12:17-21 8-EMS6 8-EFT4 VC4-2:1-5 VC4-2:1-5 VC12:22-31 8-EMS6 8-EFT4 VC4-2:11-20 VC4-2:6-15 Add/Drop
VC12:17-21 8-EMS6 8-EFT4 VC4-2:6-10 VC4-2:1-5 VC12:22-31 8-EMS6 8-EFT4 VC4-2:21-30 VC4-2:6-15
Issue 02 (2009-06-15)
7-45
The Ethernet LAN service of User G:
Occupies VC-12 timeslots 1721 in the first VC-4 on the radio link from NE1 to NE2 and VC-12 timeslots 1721 in the first VC-4 on the radio link from NE1 to NE3. Uses VC-12 timeslots 15 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/ drop services between NE1 and NE2. Uses VC-12 timeslots 610 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 15 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/ drop services between NE1 and NE3. Occupies VC-12 timeslots 2231 in the first VC-4 on the radio link from NE1 to NE2 and VC-12 timeslots 2231 in the first VC-4 on the radio link from NE1 to NE3. Uses VC-12 timeslots 1120 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 615 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop services between NE1 and NE2. Uses VC-12 timeslots 2130 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12 timeslots 615 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop services between NE1 and NE3.
The Ethernet LAN service of User H:

You can configure the 802.1q bridge-based EVPLAN services of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
Procedure
Step 1 Configure Ethernet external ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 PORT2 Description
l
2.
The basic attributes of PORT1 and PORT2 need to be set. The services of user G1 use PORT1 and the services of user H1 use PORT2.
Enabled/ Disabled
7-46
Enabled
In the case of the port that accesses services, set this parameter to Enabled.
Issue 02 (2009-06-15)
Value Range Auto-Negotiation
Description The Ethernet equipment of users work in auto-negotiation mode. Hence, the Working Mode of the external ports should be set to Auto-Negotiation.
3.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1 PORT2 Description
l
The tag attributes of PORT1 and PORT2 need to be set. The services of user G1 use PORT1 and the services of user H1 use PORT2. If TAG is set to Access, the packets that carry VLAN tags are discarded. If TAG is set to Access, the packets that do not carry VLAN tags are tagged with Default VLAN ID and are then received. In this example, Default VLAN ID is set to 100 for PORT1. In this example, Default VLAN ID is set to 200 for PORT2.
TAG
Access
Default VLAN ID
100
200
Entry Detection
Enabled
Step 2 Configure Ethernet internal ports. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Set the encapsulation and mapping protocol used by the port. a. b. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters. After setting the parameters, click Apply. Value Range VCTRU NK1 VCTRU NK2 VCTR UNK3 VCTRU NK4 Description
l
2.
Param eter Port
The encapsulation protocol needs to be set for VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4.
7-47
Issue 02 (2009-06-15)
Param eter Mappi ng Protoc ol
Value Range GFP
Description
l
In this example, Mapping Protocol is set to GFP.
3.
Configure the LCAS function of the VCTRUNKs. a. b. Click the LCAS tab. Set Enabling LCAS and other LCAS parameters. After setting the parameters, click Apply. Value Range VCTRU NK1 Enabled VCTRU NK2 VCTR UNK3 VCTRU NK4 Description Enabling LCAS needs to be set for VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4.
l
Param eter Port
Enabli ng LCAS
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Param eter Port Value Range VCTRU NK1 Access VCTRU NK2 VCTR UNK3 VCTRU NK4 Description TAG Attributes need to be set for VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4.
l
TAG
If TAG is set to Access, the packets that carry VLAN tags are discarded. If TAG is set to Access, the packets that do not carry VLAN tags are tagged with Default VLAN ID and VLAN Priority and are then received.
7-48
Issue 02 (2009-06-15)
Param eter Entry Detecti on
Value Range Enabled
Description In this example, the incoming packets from the port need to be checked according to the tag attributes.
5.
Set the VC paths to be bound with the VCTRUNKs. a. b. c. d. Click the Bound Path tab. Click Configuration. Then, the Bound Path Configuration dialog box is displayed. In Configurable Ports, select VCTRUNK1 as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths. After setting the parameters, click OK. Then, click Yes in the dialog box that is displayed. Value Range VCTRU NK1 VCTRU NK2 VCTR UNK3 VCTRU NK4 Description In this example, VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4 are used to bind VC paths. In this example, the bound path is at the VC-12 level.
l
Param eter Config urable Ports Level Service Directi on
VC12 Bidirectional
Availa ble Resour ces
VC4-2
Issue 02 (2009-06-15)
7-49
Param eter Availa ble Timesl ots
Value Range VC12-1 to VC12-5 VC12-6 to VC12-1 0 VC1211 to VC1220 VC12-2 1 to VC12-3 0
Description
l
VCTRUNK1 is bound with timeslots VC12-1 to VC12-5. VCTRUNK2 is bound with timeslots VC12-6 to VC12-10. VCTRUNK3 is bound with timeslots VC12-11 to VC12-20. VCTRUNK4 is bound with timeslots VC12-21 to VC12-30.
Activat ion Status
Activated
Indicates that VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4 are active.
Step 3 Create Ethernet LAN services. 1. 2. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters as follows. Parameter VB Name VB Type Bridge Switch Mode Value Range VB1 802.1q IVL/Ingress Filter Enable (802.1q) Description In this example, VB Name is set to VB1. In this example, an IEEE 802.1q bridge is created. If the ingress filter is enabled, the VLAN tags are 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.
3.
Click Configure Mount. The Service Mount Configuration dialog box is displayed. After setting the parameters, click OK. Parameter selected forwarding ports Value Range PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3, VCTRUNK4 Description PORT1, PORT2, VCTRUNK1, VCTRUNK2, VCTRUNK3, and VCTRUNK4 are connected to the bridge.
4.
Click OK.
Step 4 Create a VLAN filtering table.

1. 2.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select the created bridge. Click the VLAN Filtering tab. After setting the parameters, click OK. Set the parameters of VLAN filtering table 1 as follows. Parameter VLAN ID(e.g: 1,3-6) selected forwarding ports Value Range 100 PORT1, VCTRUNK1, VCTRUNK2 Description PORT1, VCTRUNK1, and VCTRUNK2 are connected to the bridge.
Set the parameters of VLAN filtering table 2 as follows. Parameter VLAN ID(e.g: 1,3-6) selected forwarding ports Value Range 200 PORT2, VCTRUNK3, VCTRUNK4 Description PORT2, VCTRUNK3, and VCTRUNK4 are connected to the bridge.
Step 5 Create the cross-connections of Ethernet services. 1. 2. In the NE Explorer, select NE1 from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Click Create. Then, the Create SDH Service dialog box is displayed. After setting the parameters, click OK.
l
l
Source
5-IF1A
In this example, the 5-IF1A is the service source.
Issue 02 (2009-06-15)
7-51
Parameter Source Timeslot Range(e.g.1,3 6) Sink Sink VC4 Sink Timeslot Range(e.g.1,3 6) Activate Immediately
Value Range 17-21
Description In this example, the timeslots to which the service source corresponds are timeslots 17-21.
8-EMS6 VC4-2 1-5
Yes
l
7-IF1A 17-21
8-EMS6 VC4-2 6-10
Yes
Set the parameters of the cross-connections of VCTRUNK3 as follows.
7-52
Issue 02 (2009-06-15)
Value Range VC12 Bidirectional
Description In this example, the cross-connection is at the VC-12 level.

l
5-IF1A 22-31
8-EMS6 VC4-2 11-20
Yes
l
Source Source Timeslot Range(e.g.1,3 6) Sink

Issue 02 (2009-06-15)
7-IF1A 22-31
8-EMS6
In this example, the 8-EMS6 is the service sink.

7-53
Parameter Sink VC4 Sink Timeslot Range(e.g.1,3 6) Activate Immediately
Value Range VC4-2 21-30
Description In this example, the service sink is located in VC4-2. In this example, the timeslots to which the service sink corresponds are timeslots 21-30. Delivers the configured cross-connection to NEs immediately.
Yes
----End

You can configure the Ethernet services of NE2 and NE3 based on the parameters of the service planning, by using the NMS. The Ethernet service of NE2/NE3 is a point-to-point EPL service, and therefore should be configured according to the configuration example of point-to-point EPL services. For details, see 7.2.3 Configuring NE1.
7-54
Issue 02 (2009-06-15)
8 Configuring Hybrid Microwave-Based Ethernet Services on the Per-NE Basis
Configuring Hybrid Microwave-Based Ethernet Services on the Per-NE Basis
About This Chapter

You need not configure the mapping relations between the services and the VCTRUNKs or the cross-connections between the VCTRUNKs and the line timeslots, when configuring Hybrid microwave-based Ethernet services. 8.1 Configuration Flows The Hybrid microwave supports the transmission of E1 and Ethernet services. Configuring the services based on the Hybrid microwave involves configuring the microwave services and configuring the accessed Ethernet services. The Ethernet services are accessed through the Ethernet board EMS6 and then transparently transmitted to the Hybrid IF board IFH2, or are accessed directly through the GE port of the Hybrid IF board IFH2. 8.2 Configuration Example This topic uses an example to describe how to plan the service parameters and how to configure the NE parameters according to the requirements for the services based on the Hybrid microwave.
Issue 02 (2009-06-15)
8-1
8.1 Configuration Flows

The Hybrid microwave supports the transmission of E1 and Ethernet services. Configuring the services based on the Hybrid microwave involves configuring the microwave services and configuring the accessed Ethernet services. The Ethernet services are accessed through the Ethernet board EMS6 and then transparently transmitted to the Hybrid IF board IFH2, or are accessed directly through the GE port of the Hybrid IF board IFH2. 8.1.1 Configuration Flow (Ethernet Services Accessed Through the EMS6 Board) The Ethernet services that are accessed through the EMS6 board are processed and then transmitted to the IFH2 board. 8.1.2 Configuration Flow (Ethernet Services Accessed Through the IFH2 Board) The Ethernet services that are accessed through the IFH2 board are scheduled according the CoS.
8.1.1 Configuration Flow (Ethernet Services Accessed Through the EMS6 Board)
The Ethernet services that are accessed through the EMS6 board are processed and then transmitted to the IFH2 board. Table 8-1 Flow for configuring the Ethernet services accessed through the EMS6 board Step 1 Operation Configuring the Ethernet port of the IFH2 board Configuring the external port of an Ethernet board Remarks Required. This task is performed to configure the Ethernet port of the IFH2 board so that the IFH2 board can interconnect with the EMS6 board through this Ethernet port. The IFH2 board provides the GE port for accessing Ethernet services. The procedure for configuring the Ethernet port of the IFH2 board is similar to the procedure for configuring the external Ethernet port. The IFH2 board, however, supports the configuration of only the basic attributes and flow control function. 2 Configuring the Ethernet services of the EMS6 board Configuring the external port of an Ethernet board Required.
l
This task is performed to configure the Ethernet port of the EMS6 board that is used to access the user services. This task is performed to configure the Ethernet port of the EMS6 board so that the EMS6 board can interconnect with the IFH2 board through this Ethernet port.
8-2
Issue 02 (2009-06-15)
Step
Operation Creating Ethernet private line services Creating Ethernet LAN services Modifying the mounted port of a bridge Creating the VLAN filtering table Configuring the Layer 2 switching feature Configuring the QoS
Remarks Required when you need to configure Ethernet private line services. Required when you need to configure Ethernet LAN services. Required when you need to set Hub/Spoke Attribute to Spoke, thus isolating the communication between different ports. Required when you need to create the 802.1q bridge. Optional.
Optional. Required when the Hybrid microwave uses the IF 1+1 protection.
Configuring the 1+1 protection for the Ethernet services in the Hybrid microwave
Creating a link aggregation group
NOTE
The procedure for configuring the Ethernet services of the EMS6 board (described in Step 2) is similar to the procedure for configuring the Ethernet services based on the SDH/PDH microwave. In both the configuration scenarios, you need not configure the Ethernet cross-connections. The only difference is that you need to configure the external port during the configuration of the Ethernet services of the EMS6 board, but you need to configure the internal port (VCTRUNK) during the configuration of the Ethernet services based on the SDH/PDH microwave. The configurations in Step 2 do not include the configuration of QinQ-based EVPL services and the configuration of 802.1ad bridge-based EVPLAN services. For details about the QinQ, see the OptiX RTN 600 Radio Transmission System Feature Description. Configuring the Layer 2 switching feature involves setting the entries of the MAC address table manually, configuring the spanning tree protocol, and modifying the aging time in the multicast table. For details about the Layer 2 switching feature, see the OptiX RTN 600 Radio Transmission System Feature Description. Configuring the QoS involves creating the flow, configuring the CAR, configuring the CoS, binding the CAR and CoS, and configuring the traffic shaping. For details about the QoS, see the OptiX RTN 600 Radio Transmission System Feature Description. For details about the link aggregation group, see the OptiX RTN 600 Radio Transmission System Feature Description.
Issue 02 (2009-06-15)
8-3
8.1.2 Configuration Flow (Ethernet Services Accessed Through the IFH2 Board)
The Ethernet services that are accessed through the IFH2 board are scheduled according the CoS. Table 8-2 Flow for configuring the Ethernet services accessed through the IFH2 board Step 1 Operation Configuring the external Ethernet port of an Ethernet board Remarks Required. This task is performed to configure the Ethernet port of the IFH2 board that is used to access the user services. The IFH2 board provides the GE port for accessing Ethernet services. The procedure for configuring the Ethernet port of the IFH2 board is similar to the procedure for configuring the external Ethernet port. The IFH2 board, however, supports the configuration of only the basic attributes and flow control function. 2 Configuring the CoS Optional.
NOTE
For details about the CoS, see the OptiX RTN 600 Radio Transmission System Feature Description.
8.2 Configuration Example

This topic uses an example to describe how to plan the service parameters and how to configure the NE parameters according to the requirements for the services based on the Hybrid microwave. 8.2.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 8.2.2 Service Planning (Ethernet Services Accessed Through the EMS6 Board) According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs. 8.2.3 Service Planning (Ethernet Services Accessed Through the IFH2 Board) According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs.
8.2.4 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board) You can configure the Ethernet services that are accessed through the EMS6 board of NE1 based on the parameters of the service planning, by using the NMS. 8.2.5 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board) You can configure the Ethernet services that are accessed through the EMS6 board of NE2 based on the parameters of the service planning, by using the NMS. 8.2.6 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board) You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board normally, thus meeting the requirement for CoS scheduling. 8.2.7 Configuring NE3 You can configure the data of NE3 based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. In the network shown in Figure 8-1, NE1 and NE2 use the IDU 620 and NE3 uses the IDU 605. The service requirements are as follows:
l
The Ethernet equipment of user A, user B, and user C provides 100 Mbit/s auto-negotiative Ethernet electrical interfaces. The Ethernet equipment of user A does not support VLAN tags. The services of user A are frames that do not carry VLAN tags, namely, untagged framed. The Ethernet equipment of user B and user C supports VLAN tags. Hence, the services of user B and user C are frames that carry VLAN tags, namely, tagged frames. User A has two branches (user A1 and user A2), which are located at NE1 and NE2. There are 4xE1 services and Ethernet services between the two branches. The Ethernet services are Internet services, whose maximum bandwidth is 10 Mbit/s. The bandwidth of the Internet services can be allocated flexibly. After the user services are accessed, the default VLAN ID of 300 is added to the services. User B has two branches (user B1 and B2), which are located at NE1 and NE2. There are 2xE1 services and Ethernet services between the two branches. One part of the Ethernet services are voice over IP (VoIP) services, whose maximum bandwidth is 4 Mbit/s. The transmission of the VoIP services must be stable. The VLAN ID is 100. The other part of the Ethernet services are Internet services, whose maximum bandwidth is 20 Mbit/s. The bandwidth of the Internet services can be allocated flexibly. The VLAN ID is 200. The radio link between NE1 and NE2 uses the 1+1 HSB configuration. User C has two branches, which are located at NE2 and NE3. There are 4xE1 services and Ethernet services between the two branches. One part of the Ethernet services are VoIP services, whose maximum bandwidth is 4 Mbit/s. The transmission of the VoIP services must be stable and the VLAN priority level is 7. The other part of the Ethernet services are Internet services, whose maximum bandwidth is 20 Mbit/s. The bandwidth of the Internet services can be allocated flexibly and the VLAN priority level is 1.
l l
Issue 02 (2009-06-15)
8-5

User A2 User A1 User C2 NE2 (IDU 620) NE1 (IDU 620) User B1 User B2 User C1 NE3 (IDU 605 1F)
8.2.2 Service Planning (Ethernet Services Accessed Through the EMS6 Board)
According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs.
Configuration Information of Ethernet Parameters

Figure 8-2 Configuration information of Ethernet parameters
NE1: 5-IFH2 (main) NE1: NE1: 6-EMS6
PORT3 (main) User A1 User B1 PORT1
15-ODU (main)
PORT1
NE2: 5-IFH2 NE2: (main) 15-ODU (main)

PORT1
PORT3 (main)
NE2: 6-EMS6
PORT1
LAG
PORT2 PORT4 (slave) PORT1
LAG
PORT2
User A2 User B2
NE1: 17-ODU (standby)
NE2: 17-ODU (standby)
PORT4 (slave)
PORT1
NE1: 7-IFH2 (standby) Network cable IF cable
NE2: 7-IFH2 (standby)
8-6
Issue 02 (2009-06-15)
Table 8-3 Parameters of external ports of the EMS6 board Parameter Board Port Enabled/Disabled Working Mode Maximum Frame Length Flow Control TAG NE1 6-EMS6 PORT1PORT4 Enabled Auto-Negotiation 1522 Disabled PORT1: Access (default VLAN ID: 300) PORT2PORT4: Tag Aware Entry Detection Enabled NE2 6-EMS6 PORT1PORT4 Enabled Auto-Negotiation 1522 Disabled PORT1: Access (default VLAN ID: 300) PORT2PORT4: Tag Aware Enabled
Table 8-4 Parameters of external ports of the IFH2 board Parameter Board Enabled/ Disabled Working Mode Flow Control NE1 5-IFH2 Enabled AutoNegotiation Disabled 7-IFH2 Enabled AutoNegotiation Disabled NE2 5-IFH2 Enabled AutoNegotiation Disabled 7-IFH2 Enabled AutoNegotiation Disabled
Table 8-5 Parameters of Ethernet private line services (NE1) Parameter NE1 Private Line Service 1 (User A1) Board Service Type Service Direction Source Port 6-EMS EPL Bidirectional PORT1 EPL Bidirectional PORT2 EPL Bidirectional PORT2 Private Line Service 2 (User B1, VoIP Service) Private Line Service 3 (User B1, Internet Service)
Issue 02 (2009-06-15)
8-7
Parameter
NE1 Private Line Service 1 (User A1) Private Line Service 2 (User B1, VoIP Service) 100 PORT3 100 Private Line Service 3 (User B1, Internet Service) 200 PORT3 200
Source C-VLAN (e.g. 1,3-6) Sink Port Sink C-VLAN (e.g. 1,3-6)
300 PORT3 300
Table 8-6 Parameters of Ethernet private line services (NE2) Parameter NE2 Private Line Service 1 (User A2) Board Service Type Service Direction Source Port Source C-VLAN (e.g. 1,3-6) Sink Port Sink C-VLAN (e.g. 1,3-6) 6-EMS EPL Bidirectional PORT1 300 PORT3 300 EPL Bidirectional PORT2 100 PORT3 100 EPL Bidirectional PORT2 200 PORT3 200 Private Line Service 2 (User B2, VoIP Service) Private Line Service 3 (User B2, Internet Service)
Configuration Information of the QoS

Table 8-7 Flow configuration Paramet er NE1 User A1 User B1, VoIP Service User B1, Internet Service NE2 User A2 User B2, VoIP Service User B2, Internet Service
Board
6-EMS
6-EMS
8-8
Issue 02 (2009-06-15)
Paramet er
NE1 User A1 User B1, VoIP Service PORT +VLAN Flow PORT2 100 1 User B1, Internet Service PORT +VLAN Flow PORT2 200 2 2
NE2 User A2 User B2, VoIP Service PORT +VLAN Flow PORT2 100 1 User B2, Internet Service PORT +VLAN Flow PORT2 200 2 2
Flow Type Port VLAN ID Bound CAR Bound CoS
PORT +VLAN Flow PORT1 300 1 3
PORT +VLAN Flow PORT1 300 1 3
Table 8-8 Parameters of the CARa Parameter Board CAR ID Enabled/Disabled NE1 6-EMS 1 Enabled 2 Enabled 20480 0 40960 0 NE2 6-EMS 1 Enabled 10240 0 20480 0 2 Enabled 20480 0 40960 0
Committed Information Rate (kbit/ 10240 s) Committed Burst Size (kbyte) Peak Information Rate (kbit/s) Maximum Burst Size (kbyte) 0 20480 0
NOTE
a: You can limit the Ethernet service rate on a port of the EMS6 board, by performing the corresponding configuration of the CAR that is bound with the port.
Table 8-9 Parameters of the CoS Parameter Board CoS ID CoS Type
Issue 02 (2009-06-15)
NE1 6-EMS 1 simple 2 simple 3 simple
NE2 6-EMS 1 simple 2 simple 3 simple

8-9
Parameter CoS Priority
NE1 7 3 2
NE2 7 3 2
Configuration Information of the Link Aggregation Group

Table 8-10 Parameters of the link aggregation group Parameter Board LAG No. LAG Name LAG Type Load Sharing Main Port Selected Slave Ports NE1 6-EMS 1 LAG_1 Manual Non-Sharing PORT3 PORT4 NE2 6-EMS 1 LAG_1 Manual Non-Sharing PORT3 PORT4
8.2.3 Service Planning (Ethernet Services Accessed Through the IFH2 Board)
According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs. Figure 8-3 Configuration diagram of the Ethernet services between NE2 and NE3
NE2: 8-IFH2 NE2: 18-ODU
User C2 PORT1
NE3: 8-IFH1 NE3: 18-ODU
NE3: 5-EMS4
PORT1
User C1
Network cable IF cable
8-10
Issue 02 (2009-06-15)
Table 8-11 Parameters of external Ethernet ports Parameter Board Port Enabled/Disabled Working Mode Autonegotiation Flow Control Mode NE2 8-IFH2 PORT1 Enabled Auto-Negotiation Enable Symmetric Flow Control NE3 5-EMS4 PORT1 Enabled Auto-Negotiation Disabled
Table 8-12 Parameters of the CoS of the IFH2 board (NE2) CoS Parameter User Priority 7 in the VLAN Tag User Priority 1 in the VLAN Tag CoS Priority 3 1
Table 8-13 Parameters of Ethernet services (NE3) Parameter Board VB Name VB Type Bridge Switch Mode Mount Port Ethernet LAN Service 5-EMS4 VB1 802.1d SVL/Ingress Filter Disable PORT1, IFUP1
8.2.4 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE1 based on the parameters of the service planning, by using the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. You must be logged in to the NE. The EMS6 board must be added.
The IFH2 board must be added.
Procedure
Step 1 Configure Ethernet external ports of the IFH2 board. 1. In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply. Parameter Port Value Range PORT1 Description
l l
2.
The basic attributes of PORT1 need to be set. The user services use PORT1.
In the case of the port that accesses services, set this parameter to Enabled. In this example, the port works in autonegotiation mode.
3.
Click the Flow Control tab. After setting the flow control mode of the port, click Apply. Parameter Port Value Range PORT1 Description
l
The flow control mode of PORT1 need to be set. The user services use PORT1. In this example, the non-auto-negotiation flow control is disabled. In this example, this parameter adopts the default value. In this example, the auto-negotiation flow control is disabled. In this example, this parameter adopts the default value.
NonAutonegotiatio n Flow Control Mode Autonegotiatio n Flow Control Mode
Disabled
Disabled
Step 2 Configure Ethernet external ports of the EMS6 board. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the basic attributes of the ports, click Apply.
2.
8-12
Issue 02 (2009-06-15)
Parameter Port
Value Range PORT1PORT4
Description
l
The basic attributes of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port.
3.
Click the Flow Control tab. After setting the flow control mode of the ports, click Apply. Parameter Port Value Range PORT1PORT4 Description
l
The flow control mode of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port. In this example, the non-auto-negotiation flow control is disabled. In this example, this parameter adopts the default value. In this example, the auto-negotiation flow control is disabled. In this example, this parameter adopts the default value.
Disabled
Disabled
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1PORT4 Description
l
The tag attributes of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port.
Issue 02 (2009-06-15)
8-13
Parameter TAG
Value Range
l
Description If TAG is set to Access:

l
In this example, TAG is set to Access for PORT1. In this example, TAG is set to Tag Aware for PORT2 PORT4.
The packets that carry VLAN tags are discarded. The packets that do not carry VLAN tags are tagged with Default VLAN ID and are then received. The packets that carry VLAN tags are received. The packets that do not carry VLAN tags are discarded.
If TAG is set to Tag Aware:

l l
Default VLAN ID Entry Detection
300 Enabled
In this example, Default VLAN ID is set to 300 for PORT1.

l
In this example, the incoming packets from the port need to be checked according to the tag attributes. In this example, this parameter adopts the default value.
Step 3 Create Ethernet private line services of the EMS6 board. 1. 2. 3. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click New. Then, the Create Ethernet Line Service dialog box is displayed. Set the attributes of the three Ethernet private line services. Then, click OK.
l
Set the parameters of Ethernet private line service 1 as follows. Parameter Service Type Service Direction Value Range EPL Bidirectional Description When creating the non-QinQ private line service, set this parameter to EPL.
l
Source Port Source VLAN (e.g.1, 3-6) Sink Port
PORT1 300 PORT3
In this example, PORT1 is the service source port. The service that has the VLAN ID of 300 is the source service. In this example, PORT3 is the service sink port.
8-14
Issue 02 (2009-06-15)
Parameter Sink VLAN (e.g.1, 3-6)
Value Range 300
Description The service that has the VLAN ID of 300 is the sink service.
Set the parameters of Ethernet private line service 2 as follows. Parameter Service Type Service Direction Value Range EPL Bidirectional Description When creating the non-QinQ private line service, set this parameter to EPL.
l
Source Port Source VLAN (e.g.1, 3-6) Sink Port Sink VLAN (e.g.1, 3-6)
PORT2 100 PORT3 100
In this example, PORT2 is the service source port. The service that has the VLAN ID of 100 is the source service. In this example, PORT3 is the service sink port. The service that has the VLAN ID of 100 is the sink service.
Set the parameters of Ethernet private line service 3 as follows. Parameter Service Type Direction Value Range EPL Bidirectional Description When creating the non-QinQ private line service, set this parameter to EPL.
l
Issue 02 (2009-06-15)
PORT2 200 PORT3 200
8-15
Step 4 Configure the QoS of the EMS6 board. 1. Create the flow. a. b. c.
l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. Click New. The New Flow dialog box is displayed. Set the parameters of the three flows. Then, click OK. Set the parameters of the Internet service of user A1 as follows: Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT1 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 300.
Port VLAN ID
PORT1 300
Set the parameters of the VoIP service of user B1 as follows. Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT2 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 100.
Port VLAN ID
PORT2 100
Set the parameters of the Internet service of user B1 as follows. Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT2 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 200.
Port VLAN ID
PORT2 200
2.
8-16
Create the CAR.

a. b. c.
l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CAR Configuration tab. Click New. The New CAR dialog box is displayed. Select the parameters of the two CARs. Then, click OK. Set the parameters of user A1 as follows. Parameter CAR ID Enabled/ Disabled Committed Information Rate(kbit/s) Value Range 1 Enabled 10240 Description In this example, CAR 1 is used to bind the flow to an associated CAR operation. In this example, CAR1 is enabled.
l l
In this example, the CIR is 10240 kbit/s. When the rate of the packets is not more than the CIR, these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion.
Committed Burst Size (kbyte) Peak Information Rate(kbit/s)
In this example, the CBS is 0.
20480
l l
In this example, the PIR is 20480 kbit/s. When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When 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 can pass the restriction of the CAR and are marked yellow, which enables these packets to be discarded first in the case of network congestion.
Maximum Burst Size (kbyte)
In this example, the MBS is 0.
Set the parameters of the Internet service of user B1 as follows. Parameter CAR ID Enabled/ Disabled Value Range 2 Enabled Description In this example, CAR 2 is used to bind the flow to an associated CAR operation. In this example, CAR 2 is enabled.
Issue 02 (2009-06-15)
8-17
Parameter Committed Information Rate(kbit/s)
Value Range 20480
Description
l l
40960
l l
Maximum Burst Size (kbyte) 3. Create the CoS. a. b. c.

l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CoS Configuration tab. Click New. The New CoS dialog box is displayed. Set the parameters of the three CoSs. Then, click OK.. Set the parameters of the VoIP service of user B1 as follows. Parameter CoS ID CoS Type Value Range 1 simple Description In this example, CoS 1 is used to bind the flow to an associated CoS operation. 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. The queue whose CoS priority is 7 is an SP queue.
CoS Priority
Set the parameters of the Ethernet service of user B1 as follows.
8-18
Issue 02 (2009-06-15)
Parameter CoS ID CoS Type
Value Range 2 simple
Description In this example, CoS 2 is used to bind the flow to an associated CoS operation. 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. The queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6).
CoS Priority
Set the parameters of the Ethernet service of user A1 as follows. Parameter CoS ID CoS Type Value Range 3 simple Description In this example, CoS 3 is used to bind the flow to an associated CoS operation. 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. The queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6).
CoS Priority
4.
Bind the CAR/CoS. a. b. In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. After setting the parameters, click OK. Value Range PORT1 PORT2 PORT2 Description In this example, PORT1 and PORT2 are the source ports of the Ethernet services associated with the flows. When Flow Type is set to PORT +VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. The source VLAN IDs of the ports are 300, 100, and 200.
Paramet er Port
Flow Type
PORT +VLAN Flow
PORT +VLAN Flow
PORT +VLAN Flow
VLAN ID
300
100
200
Issue 02 (2009-06-15)
8-19
Paramet er Bound CAR Bound CoS
Value Range 1 2
Description The flow is bound with the corresponding CAR, according to the service plan. The flow is bound with the corresponding CoS, according to the service plan.
Step 5 Create an LAG of the EMS6 board. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Click the Link Aggregation Group Management tab. Click New. The Create Link Aggregation Group dialog box is displayed. After setting the parameters, click OK. Then, click OK in the dialog box that is displayed. Value Range 1 LAG_1 Manual Description In this example, LAG No. is set to 1. In this example, LAG Name is set to LAG_1. The user creates the LAG manually. The LACP is not enabled to add or delete a member port. The member ports may be in the UP or DOWN state. The equipment determines whether to perform the aggregation according to the status of the specific port. Only one member link of a link aggregation group carries traffic and the other member links are in the Standby state. In this case, a hot backup scheme is provided. In this example, PORT3 is the main port. In this example, PORT4 is the slave port.
2. 3.
Parameter LAG No. LAG Name LAG Type
Load Sharing
Non-Sharing
Main Port Selected Slave Ports
PORT3 PORT4
----End
8.2.5 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE2 based on the parameters of the service planning, by using the NMS.
8-20
Issue 02 (2009-06-15)
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. You must be logged in to the NE. The EMS6 board must be added. The IFH2 board must be added.
Procedure
Step 1 Configure Ethernet external ports of the IFH2 board. 1. In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply. Parameter Port Value Range PORT1 Description
l l
2.
3.
Click the Flow Control tab. After setting the flow control mode of the port, click Apply. Parameter Port Value Range PORT1 Description
l
The flow control mode of PORT1 need to be set. The user services use PORT1. In this example, the non-auto-negotiation flow control is disabled. In this example, this parameter adopts the default value. In this example, the auto-negotiation flow control is disabled. In this example, this parameter adopts the default value.
Disabled
Disabled
Step 2 Configure Ethernet external ports of the EMS6 board. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port.
Issue 02 (2009-06-15)
2.
Click the Basic Attributes tab. After setting the basic attributes of the ports, click Apply. Parameter Port Value Range PORT1PORT4 Description
l
The basic attributes of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port.
3.
Click the Flow Control tab. After setting the flow control mode of the ports, click Apply. Parameter Port Value Range PORT1PORT4 Description
l
The flow control mode of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port. In this example, the non-auto-negotiation flow control is disabled. In this example, this parameter adopts the default value. In this example, the auto-negotiation flow control is disabled. In this example, this parameter adopts the default value.
Disabled
Disabled
4.
Click the TAG Attributes tab. After setting the parameters, click Apply. Parameter Port Value Range PORT1PORT4 Description
l
The tag attributes of PORT1, PORT2, PORT3, and PORT4 need to be set. The services of user A1 use PORT1 and the services of user B1 use PORT2. PORT3 and PORT4 form an LAG. PORT3 is the main port and PORT4 is the slave port.
8-22
Issue 02 (2009-06-15)
Parameter TAG
Value Range
l
Description If TAG is set to Access:

l
In this example, TAG is set to Access for PORT1. In this example, TAG is set to Tag Aware for PORT2 PORT4.
The packets that carry VLAN tags are discarded. The packets that do not carry VLAN tags are tagged with Default VLAN ID and are then received. The packets that carry VLAN tags are received. The packets that do not carry VLAN tags are discarded.
If TAG is set to Tag Aware:

l l
Default VLAN ID Entry Detection
300 Enabled
In this example, Default VLAN ID is set to 300 for PORT1.

l
In this example, the incoming packets from the port need to be checked according to the tag attributes. In this example, this parameter adopts the default value.
Step 3 Create Ethernet private line services of the EMS6 board. 1. 2. 3. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click New. Then, the Create Ethernet Line Service dialog box is displayed. Set the attributes of the three Ethernet private line services. Then, click OK.
l
l
Source Port Source VLAN (e.g.1, 3-6) Sink Port
PORT1 300 PORT3
In this example, PORT1 is the service source port. The service that has the VLAN ID of 300 is the source service. In this example, PORT3 is the service sink port.
Issue 02 (2009-06-15)
8-23
Parameter Sink VLAN (e.g.1, 3-6)
Value Range 300
Description The service that has the VLAN ID of 300 is the sink service.
l
PORT2 100 PORT3 100
Set the parameters of Ethernet private line service 3 as follows: Parameter Service Type Direction Value Range EPL Bidirectional Description When creating the non-QinQ private line service, set this parameter to EPL.
l
8-24
PORT2 200 PORT3 200
Issue 02 (2009-06-15)
Step 4 Configure the QoS of the EMS6 board. 1. Create the flow. a. b. c.
l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. Click New. The New Flow dialog box is displayed. Select the parameters of the eight flows. Then, click OK. Set the parameters of the Internet service of user A2 as follows: Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT1 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 300.
Port VLAN ID
PORT1 300
Set the parameters of the VoIP service of user B2 as follows. Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT2 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 100.
Port VLAN ID
PORT2 100
Set the parameters of the Internet service of user B2 as follows. Parameter Flow Type Value Range PORT+VLAN Flow Description When Flow Type is set to PORT+VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. In this example, PORT2 is the source port of the Ethernet service associated with the flow. In this example, the source VLAN ID is 200.
Port VLAN ID
PORT2 200
2.
Issue 02 (2009-06-15)
Create the CAR.

a. b. c.
l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CAR Configuration tab. Click New. The New CAR dialog box is displayed. Set the parameters of the two CARs. Then, click OK. Set the parameters of user A1 as follows. Parameter CAR ID Enabled/ Disabled Committed Information Rate(kbit/s) Value Range 1 Enabled 10240 Description In this example, CAR 1 is used to bind the flow to an associated CAR operation. In this example, CAR 1 is enabled.
l l
20480
l l
Set the parameters of the Internet service of user B2 as follows. Parameter CAR ID Enabled/ Disabled Value Range 2 Enabled Description In this example, CAR 2 is used to bind the flow to an associated CAR operation. In this example, CAR 2 is enabled.
8-26
Issue 02 (2009-06-15)
Parameter Committed Information Rate(kbit/s)
Value Range 20480
Description
l l
40960
l l
Maximum Burst Size (kbyte) 3. Create the CoS. a. b. c.

l
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the CoS Configuration tab. Click New. The New CoS dialog box is displayed. Set the parameters of the three CoSs. Then, click OK. Set the parameters of the VoIP service of user B2 as follows. Parameter CoS ID CoS Type Value Range 1 simple Description In this example, CoS 1 is used to bind the flow to an associated CoS operation. 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. The queue whose CoS priority is 7 is an SP queue.
CoS Priority
Set the parameters of the Ethernet service of user B2 as follows.
Issue 02 (2009-06-15)
8-27
Parameter CoS ID CoS Type
Value Range 2 simple
Description In this example, CoS 2 is used to bind the flow to an associated CoS operation. 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. The queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6).
CoS Priority
Set the parameters of the Ethernet service of user A2 as follows. Parameter CoS ID CoS Type Value Range 3 simple Description In this example, CoS 3 is used to bind the flow to an associated CoS operation. 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. The queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6).
CoS Priority
4.
Bind the CAR/CoS. a. b. In the NE Explorer, select the EMS6 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. After setting the parameters, click OK. Value Range PORT1 PORT2 PORT2 Description In this example, PORT1 and PORT2 are the source ports of the Ethernet services associated with the flows. When Flow Type is set to PORT +VLAN Flow, the packets that are from the same port and have the same VLAN ID are classified as a type of flow. The source VLAN IDs of the ports are 300, 100, and 200.
Paramet er Port
Flow Type
PORT +VLAN Flow
PORT +VLAN Flow
PORT +VLAN Flow
VLAN ID
300
100
200
8-28
Issue 02 (2009-06-15)
Paramet er Bound CAR Bound CoS
Value Range 1 2
Description The flow is bound with the corresponding CAR, according to the service plan. The flow is bound with the corresponding CoS, according to the service plan.
Step 5 Create an LAG of the EMS6 board. 1. In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Click the Link Aggregation Group Management tab. Click New. The Create Link Aggregation Group dialog box is displayed. After setting the parameters, click OK. Then, click OK in the dialog box that is displayed. Value Range 1 LAG_1 Manual Description In this example, LAG No. is set to 1. In this example, LAG Name is set to LAG_1. The user creates the LAG manually. The LACP is not enabled to add or delete a member port. The member ports may be in the UP or DOWN state. The equipment determines whether to perform the aggregation according to the status of the specific port. Only one member link of a link aggregation group carries traffic and the other member links are in the Standby state. In this case, a hot backup scheme is provided. In this example, PORT3 is the main port. In this example, PORT4 is the slave port.
2. 3.
Parameter LAG No. LAG Name LAG Type
Load Sharing
Non-Sharing
Main Port Selected Slave Ports
PORT3 PORT4
----End
8.2.6 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)
You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board normally, thus meeting the requirement for CoS scheduling.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. You must be logged in to the NE. The IFH2 board must be added.
Procedure
Step 1 Configure the Ethernet ports of the IFH2 board. 1. In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port. Set the basic attributes of the ports. Click the Basic Attributes tab. After setting the parameters, click Apply. Value Range PORT1 Description
l l
2.
Parameter Port
Enabled/ Disabled Working Mode NonAutonegotiation Flow Control Mode Autonegotiation Flow Control Mode
Enabled Auto-Negotiation Disabled
In the case of the port that accesses services, set this parameter to Enabled. In this example, the port works in auto-negotiation mode.
l
In this example, the non-auto-negotiation flow control is disabled. In this example, this parameter adopts the default value.
Enable Symmetric Flow Control
When this parameter is set to Enable Symmetric Flow Control, PORT1 transmits and processes PAUSE frames.
Step 2 Configure the CoS of the IFH2 board. 1. 2. 3. In the NE Explorer, select the IFH2 board and then choose Configuration > QoS Management > Flow Management from the Function Tree. Click the Flow Configuration tab. Set CoS Parameter and CoS Priority. After setting the parameters, click Apply. Parameter CoS Parameter Value Range Priority 7 in the VLAN Tag Priority 1 in the VLAN Tag Description The data flows correspond to Priority 7 in the VLAN Tag and Priority 7 in the VLAN Tag, respectively.
8-30
Issue 02 (2009-06-15)
Value Range 3 1
Description
l
The data flow of Priority 7 in the VLAN Tag has the CoS priority of 3. The data flow of Priority 1 in the VLAN Tag has the CoS priority of 1. This parameter specifies the queue to which a packet should be scheduled.
----End

You can configure the data of NE3 based on the parameters of the service planning, by using the NMS. NE3 is the OptiX RTN 600 NE that uses the IDU 605 1F. The procedure for configuring an NE that uses the IDU 605 is not provided in this document. For details, see the OptiX RTN 600 Radio Transmission System IDU 605 Configuration Guide.
Issue 02 (2009-06-15)
8-31
9 Task Collection (Configuring Ethernet Services)
Task Collection (Configuring Ethernet Services)
About This Chapter

This task collection contains all the common tasks related to configuring Ethernet services. 9.1 Configuring Ethernet Ports The Ethernet ports contain the internal Ethernet ports and external Ethernet ports. The external Ethernet ports are the physical ports that are used to connect the Ethernet equipment. The internal Ethernet ports (VCTRUNKs) are internal paths that implement Ethernet over SDH. 9.2 Creating Ethernet Services The IDU 610 supports Ethernet private line services. The IDU 620 supports Ethernet private line services and Ethernet LAN services. 9.3 Configuring the Cross-Connections of Ethernet Services In the case of Ethernet over SDH, you need to configure the cross-connections of the Ethernet services. 9.4 Configuring the QoS The QoS provides differentiated services. Hence, you can configure the QoS to ensure the quality of the Ethernet services. 9.5 Creating a LAG Link aggregation allows all the members in a LAG to share the incoming and outgoing service loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to each other dynamically. This increases the availability of the connection. 9.6 Configuring the Layer 2 Switching Feature You can configure the Layer 2 switching feature for Ethernet LAN services according to the actual service requirements. 9.7 LPT Configuration When enabling the LPT function for an Ethernet service, you need to configure the LPT port and the related information.
Issue 02 (2009-06-15)
9-1
9.1 Configuring Ethernet Ports

The Ethernet ports contain the internal Ethernet ports and external Ethernet ports. The external Ethernet ports are the physical ports that are used to connect the Ethernet equipment. The internal Ethernet ports (VCTRUNKs) are internal paths that implement Ethernet over SDH. 9.1.1 Configuring External Ethernet Ports When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet services, the attributes of the external ports need to be configured so that the external ports can work with the data communication equipment on the client side to provide the normal access to the Ethernet services. 9.1.2 Configuring the Internal Port of the Ethernet Board When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board on the opposite side to realize the transmission of the Ethernet services in the network. 9.1.3 Modifying the Type Field of Jumbo Frames By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700". 9.1.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.
9.1.1 Configuring External Ethernet Ports

When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet services, the attributes of the external ports need to be configured so that the external ports can work with the data communication equipment on the client side to provide the normal access to the Ethernet services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet board must be included in the NE Panel.
Precautions
l
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6.
Ethernet ports FE1FE4 of an EFT4 board correspond to PORT1PORT4 respectively. The EFT4 board does not support the setting of TAG attributes, network attributes, and advanced attributes. Ethernet ports FE1FE4 of an EMS6 board correspond to PORT1PORT4 respectively. Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
The following procedures describe how to configure the external port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes, network attributes, and advanced attributes.
9-2
l
The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it supports certain Ethernet service access functions. The procedure for configuring the Ethernet port of the IFH2 board is similar to the procedure for configuring the external Ethernet port. The IFH2 board, however, supports the configuration of only the basic attributes and flow control function.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the NE Explorer.
Step 2 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 3 Set the flow control mode of the port. 1. 2. Click the Flow Control tab. Set the flow control mode of the port.
3.
Click Apply.
Step 4 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.
3.
Click Apply.
Step 5 Optional: Set the network attributes of the port. 1.

Issue 02 (2009-06-15)
Click the Network Attributes tab.

2.
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 6 Optional: Set the advanced attributes of the port.
3.
Click Apply.
----End
Parameters
Parameter Enabled/Disabled Value Range Enabled, Disabled Default Value Disabled Description
l
In the case of the port that accesses services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled. If this parameter is set to Enabled for the port that does not access services, an ETH_LOS alarm may be generated.
9-4
Issue 02 (2009-06-15)
Value Range 10M Full-Duplex, 100M Full-Duplex, Auto-Negotiation (EFT4) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (EMS6) Auto-Negotiation, 10M Full-Duplex, 100M Full-Duplex, 1000M Full-Duplex (IFH2)
Default Value Auto-Negotiation
Description
l
The Ethernet ports of different types support different working modes. When the equipment on the opposite side works in the auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation. When the equipment on the opposite side works in the 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. When the equipment on the opposite side works in the 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. The GE optical interface on the EMS6 board supports the 1000M full-duplex mode only.
Maximum Frame Length
15181535 (EFT4) 15189600 (EMS6)
1522
The value of this parameter should be greater than the maximum length of a frame among all the data frames to be transported. In the case of the EFT4 board, this parameter is invalid for Jumbo frames. In the case of the EMS6 board, this parameter has a restriction on Jumbo frames. If Jumbo frames are not considered and the accessed services are ordinary Ethernet frames that use VLAN tags or do not have VLAN tags, it is recommended that you use the default value. If the access services include services that use double tags such as QinQ services, it is recommended that you set this parameter to 1526.
MAC Loopback
Non-Loopback, Inloop
Non-Loopback
When this parameter is set to Inloop, the Ethernet frame signals that are to be sent to the remote end are looped back. In normal cases, use the default value. When this parameter is set to Inloop, the Ethernet physical signals that are to be sent to the remote end are looped back. In normal cases, use the default value.
9-5
PHY Loopback
Non-Loopback, Inloop
Non-Loopback
Issue 02 (2009-06-15)
Parameter NonAutonegotiation Flow Control Mode
Value Range Disabled, Enable Symmetric Flow Control, Send Only, Receive Only (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2)
Default Value Disabled
Description
l
This parameter is used when Working Mode is not set to Auto-Negotiation. When this parameter is set to Enable Symmetric Flow Control, the port can send PAUSE frames and process received PAUSE frames. When this parameter is set to Send Only, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. When this parameter is set to Receive Only, the port can process received PAUSE frames but cannot send PAUSE frames in the case of congestion. The non-autonegotiation flow control mode of the equipment on the local side must match the non-autonegotiation flow control mode of the equipment on the opposite side. This parameter is used when Working Mode is set to Auto-Negotiation. When this parameter is set to Enable Symmetric Flow Control, the port can send and process PAUSE frames. When this parameter is set to Enable Dissymmetric Flow Control, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. When this parameter is set to Enable Symmetric/Dissymmetric Flow Control, the port can perform as follows:

Autonegotiation Flow Control Mode
Disabled, Enable Symmetric/ Dissymmetric Flow Control, Enable Symmetric Flow Control, Enable Dissymmetric Flow Control (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2)
Disabled
Sends and processes PAUSE frames. Sends but does not process PAUSE frames. Processes but does not send PAUSE frames.
The autonegotiation flow control mode of the equipment on the local side must match the autonegotiation flow control mode of the equipment on the opposite side.
9-6
Issue 02 (2009-06-15)
Parameter Entry Detection
Value Range Enabled, Disabled
Default Value Enabled
Description
l
This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. Set this parameter according to actual situations. When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 9-1. If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. If all the accessed services are frames that do not have the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 9-1. Set this parameter according to actual situations. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 9-1. When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value. When this parameter is set to UNI, the port processes data frames according to the tag attributes. When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.
TAG
Access, Tag Aware, Hybrid
Tag Aware
Default VLAN ID
1 to 4095
l l
VLAN Priority
0 to 7
l l
Port Attributes
UNI, C-Aware, SAware
UNI
Issue 02 (2009-06-15)
9-7
Parameter Enabling Broadcast Packet Suppression
Default Value Disabled
Description This parameter specifies whether to restrict the traffic of broadcast packets according to the ratio of the broadcast packets to the total packets. When a broadcast storm may occur in the equipment on the opposite side, set this parameter to Enabled. The port discards the received broadcast packets when the ratio of the received broadcast packets to the total packets exceeds the value of this parameter. The value of this parameter should be greater than the ratio of the broadcast packets to the total packets when the broadcast storm does not occur. Generally, set this parameter to 30% or a greater value. Sets whether to enable loop detection, which is used to check whether a loop exists at the port.
Broadcast Packet Suppression Threshold
10% to 100%
30%
Loop Detection
Disabled, Enabled
Disabled
Table 9-1 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame How to Process Tag aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.
Ingress
9-8
Issue 02 (2009-06-15)
Direction
Type of Data Frame Tagged frame
How to Process Tag aware The port transmits the frame. Access The port strips the VLAN tag from the frame and then transmits the frame. Hybrid
l
Egress
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. If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
9.1.2 Configuring the Internal Port of the Ethernet Board

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board on the opposite side to realize the transmission of the Ethernet services in the network.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet board must be included in the slot layout.
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6.
l
The EFT4 board supports VCTRUNKs 14, which are bound with PORTs 14 respectively. The EFT4 board does not support the setting of TAG attributes and network attributes. The EMS6 board supports VCTRUNKs 18. VCTRUNKs 18 determine the services to be transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes and network attributes.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Choose Internal Port.
Step 2 Set the encapsulation and mapping protocol used by the port. 1. 2. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters.
3.
Click Apply.
Step 3 Set the VC paths to be bound with the port. 1. 2. 3. 4. 5. 6. 7. Click the Bound Path tab. Click Configuration. The system displays the Bound Path Configuration dialog box. In Configurable Ports, select a VCTRUNK as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click Optional: Repeat Step 3.5 and bind other VCTRUNKs. Click OK. Then, click Yes in the dialog box that is displayed. .
Step 4 Configure the LCAS function for the port. 1. 2. Click the LCAS tab. Set the Enabling LCAS parameter and other LCAS parameters.
3.
9-10
Click Apply.
Step 5 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.
3. 1. 2.
Click Apply. Click the Network Attributes tab. Set the network attributes of the port.
Step 6 Optional: Set the network attributes of the port.
3.
Click Apply.
----End
Parameters
Parameter Mapping Protocol Scramble Value Range GFP, LAPS, HDLC Unscrambled, Scrambling Mode [X43+1], Scrambling Mode [X48+1] Yes, No Default Value GFP Scrambling Mode [X43+1] Description It is recommended that you use the default value.
l
This parameter specifies the scrambling polynomial used by the mapping protocol. It is recommended that you use the default value. This parameter is valid only when Mapping Protocol is set to LAPS or HDLC. When this parameter is set to Yes, the FCS is the result after you perform a negation operation for the CRC. When this parameter is set to No, the FCS is the CRC.
Set Inverse Value for CRC
Yes
Issue 02 (2009-06-15)
9-11
Parameter Check Field Length
Value Range FCS32, FCS16, No
Default Value FCS32
Description
l
When this parameter is set to FCS32, a 32-bit FCS is used. When this parameter is set to FCS16, a 16-bit FCS is used. When the Ethernet board uses the GFP mapping protocol, this parameter can be set to FCS32, FCS16, or No. When the Ethernet board uses the HDLC mapping protocol, this parameter can be set to FCS32 or FCS16. When the Ethernet board uses the LAPS mapping protocol, this parameter can be set to FCS32 or FCS16. It is recommended that you use the default value. When this parameter is set to Big endian, the least significant byte of the FCS is placed first and the most significant byte is placed last. When this parameter is set to Little endian, the most significant byte of the FCS is placed first and the least significant byte is placed last. It is recommended that you use the default value. This parameter specifies whether the GFP payload header contains the extension header and eHEC. It is recommended that you use the default value.
FCS Calculated Bit Sequence
Big endian, Little endian
l l
Big endian (GFP) Little endian (LAPS or HDLC)
Extension Header Option
No, Yes
No
Configurable Ports
VCTRUNKs
VCTRUNK 1
This parameter specifies the VCTRUNK whose VC paths are to be configured.
9-12
Issue 02 (2009-06-15)
Parameter Available Bound Paths
Value Range -
Default Value -
Description Adhere to the following principles to plan and set this parameter:
l
The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. Generally, bidirectional paths are bound. This parameter specifies whether the LCAS function is enabled. The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved.
Enabling LCAS
Enabled, Disabled
Disabled
Issue 02 (2009-06-15)
9-13
Parameter LCAS Mode
Value Range Huawei Mode, Standard Mode
Default Value Huawei Mode
Description
l
This parameter specifies the sequence in which the LCAS sink sends the MST control packet and Rs-Ack control packet. When this parameter is set to Huawei Mode, the LCAS sink first sends the RsAck and then sends the MST. When this parameter is set to Standard Mode, the LCAS sink first sends the MST and then sends the Rs-Ack. If the equipment on the opposite side is the third-party equipment and does not support the Huawei mode, it is recommended that you set this parameter to Standard Mode. Otherwise, set this parameter to Huawei Mode. 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. If the paths of the VCTRUNK are configured with protection, it is recommended that you set this parameter to 2000 ms. Otherwise, set this parameter to 0. When the time after a member link is restored to normal reaches the set value of this parameter, the VCG uses the restored member link. It is recommended that you use the default value. This parameter specifies 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. It is recommended that you use the default value.
Hold Off Time (ms)
0, any integer that ranges from 2000 to 10000 and has a step of 100
2000
WTR Time(s)
0 to 720
300
TSD
Enabled, Disabled
Disabled
9-14
Issue 02 (2009-06-15)
Parameter Entry Detection
Description
l
This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. Set this parameter according to actual situations. When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 9-2. If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. If all the accessed services are frames that do not have the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 9-2. Set this parameter according to actual situations. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 9-2. When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value. When this parameter is set to UNI, the port processes data frames according to the tag attributes. When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.
TAG
Tag Aware
Default VLAN ID
1 to 4095
l l
VLAN Priority
0 to 7
l l
Port Attributes
UNI, C-Aware, SAware
UNI
Issue 02 (2009-06-15)
9-15
Parameter Activation Status
Value Range Activated, Inactivated
Default Value -
Description Displays whether the VCTRUNK is activated.
NOTE
The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other end of the transmission line. The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line.
Table 9-2 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame How to Process Tag Aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.
l
Ingress
Egress
Tagged frame
The port transmits the frame.
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. If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
9-16
Issue 02 (2009-06-15)
9.1.3 Modifying the Type Field of Jumbo Frames

By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".
Prerequisite
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Jumbo Frame from the Function Tree. Step 2 Modify the type field of Jumbo frames.
Parameters
Parameter Jumbo Frame Value Range 00 00 to FF FF Default Value 88 70 Description This parameter specifies the type field of Jumbo frames. Set this parameter according to the type field of the accessed Jumbo frames.
9.1.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.
Prerequisite
The Ethernet board must be included in the slot layout.
Procedure
Step 1 Select the Ethernet board from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Step 2 Click the Bound Path tab. Step 3 Click Configuration. The system displays the Bound Path Configuration dialog box. Step 4 Optional: Dynamically increase the VCTRUNK bandwidth. 1. 2. 3. 4. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select desired items in Available Resources and Available Timeslots and click Optional: Repeat Step 4.3 and bind other VC paths. .
Step 5 Optional: Dynamically decrease the VCTRUNK bandwidth. 1. 2. 3. Do not select the Display in Combination check box. Select the VC paths to be deleted in Selected Bound Paths and click Optional: Repeat Step 5.2 to delete other VC paths. .
Parameters
For specific parameters, see 9.1.2 Configuring the Internal Port of the Ethernet Board.
9-18
Issue 02 (2009-06-15)
9.2 Creating Ethernet Services

The IDU 610 supports Ethernet private line services. The IDU 620 supports Ethernet private line services and Ethernet LAN services. 9.2.1 Creating Ethernet Line Service To enable the Ethernet switching board to transmit the line service, perform certain operations to configure the related information, such as the service source and service sink. 9.2.2 Creating the Ethernet LAN Service To enable the Ethernet switching board to transmit the LAN service, perform certain operations to create the bridge and set the attributes of the bridge and to configure the mounted ports of the bridge. 9.2.3 Modifying the Mounted Port of a Bridge This operation enables the user to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port. 9.2.4 Creating the VLAN Filter Table You need to create the VLAN filter table for the bridge when you create the EVPLAN service. 9.2.5 Deleting an Ethernet Private Line Service When an Ethernet private line service is not used, you can delete the Ethernet private line service to release the corresponding resources. 9.2.6 Deleting an Ethernet LAN Service When an Ethernet LAN service is not used, you can delete the Ethernet LAN service to release the corresponding resources.
9.2.1 Creating Ethernet Line Service

To enable the Ethernet switching board to transmit the line service, perform certain operations to configure the related information, such as the service source and service sink.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be added in the slot layout.
Precautions
l l
This topic does not describe the method for creating the QinQ service. IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet transparent transmission board, and the PORTs of the EFT4 board correspond to the VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click New.
The Create Ethernet Line Service dialog box is displayed. Step 3 Set the attributes of the Ethernet line service.
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the result of directly setting the Ethernet service port attributes.
Step 5 Optional: Set the bound path. 1. 2. 3. 4. 5. Click Configuration. The Bound Path Configuration dialog box is displayed. 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 Optional: Repeat Step 5.4 to bind other VC paths. .
9-20
Issue 02 (2009-06-15)
NOTE
6.
Click OK.
Parameters
Parameter Service Type Direction Value Range EPL, EVPL (QinQ) Unidirectional, Bidirectional Default Value EPL Bidirectional Description When creating the non-QinQ private line service, set this parameter to EPL.
l
When setting this parameter to Unidirectional, create the service only from the service source to the service sink. That is, the service source is forwarded only to the sink port. When setting this parameter to Bidirectional, create the service from the service source to the service sink and the service from the service sink to the service source. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port. Generally, it is recommended that you use the default value.
Issue 02 (2009-06-15)
9-21
Parameter Source Port
Value Range A specific PORT or VCTRUNK
Default Value PORT1
Description
l
This parameter indicates the port where the service source resides. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, use a specific PORT as the source port. You can set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. 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). When you set this parameter to null, all the services of the source port work as the service source. When you set this parameter to a non-null value, only the services of the source port whose VLAN IDs are included in the set value of this parameter work as the service source. This parameter indicates the port where the service sink resides. Do not set the value of this parameter to the same as the value of Source Port. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, use a VCTRUNK as the sink port.
Source VLAN (e.g. 1,3-6)
14095
Sink Port
A specific PORT or VCTRUNK
PORT1
9-22
Issue 02 (2009-06-15)
Parameter Sink VLAN (e.g. 1,3-6)
Value Range 14095
Default Value -
Description
l
You can set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. 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). When you set this parameter to null, all the services of the sink port work as the service sink. When you set this parameter to a non-null value, only the services of the sink port whose VLAN IDs are included in the set value of this parameter work as the service sink.
Port Enabled TAG
Enabled, Disabled Access, Tag Aware, Hybrid
Tag Aware
When the source port or the sink port is set to a PORT, set Port Enabled to Enabled.
l
When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Configurable Ports
VCTRUNKs
VCTRUNK 1
This parameter specifies the VCTRUNK whose VC paths are to be configured.
Issue 02 (2009-06-15)
9-23
Parameter Available Bound Paths
Value Range -
Default Value -
Description Adhere to the following principles to plan and set this parameter:
l
The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. Generally, bidirectional paths are bound.
Activation Status
Activated, Inactivated
Displays whether the VCTRUNK is activated.
9.2.2 Creating the Ethernet LAN Service

To enable the Ethernet switching board to transmit the LAN service, perform certain operations to create the bridge and set the attributes of the bridge and to configure the mounted ports of the bridge.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout.
9-24
Issue 02 (2009-06-15)
Precautions
l
This task describes only how to create the 802.1d bridge and how to create the 802.1q bridge. The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. 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 802.1q bridge.
Set the attributes of the 802.1d bridge.
Issue 02 (2009-06-15)
9-25
Step 4 Configure the mounted ports of the bridge. 1. 2. 3. 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 Optional: Repeat Step 4.2 to select other mounted ports. .
4.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to the VCTRUNK. 1. 2.
9-26
Click Configuration. The Bound Path Configuration dialog box is displayed. In Configurable Ports, select a VCTRUNK as the configurable port.
3. 4. 5.
In Available Bound Paths, set Level and Service Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click Optional: Repeat Step 5.4 to bind other VC paths. .
NOTE
6.
Click OK.
Parameters
Parameter VB Name Value Range Default Value Description This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge.
l
Bridge Type
802.1q, 802.1d, 802.1ad (EMS6)
802.1q
When setting this parameter to 802.1q, create the 802.1q bridge. When setting this parameter to 802.1d, create the 802.1d bridge. Using the 802.1q bridge is a priority. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data among VLANs, you can also use the 802.1d bridge. This task describes only how to create the 802.1d bridge and how to create the 802.1q bridge.
9-27
Issue 02 (2009-06-15)
Parameter Bridge Switch Mode
Value Range IVL/Ingress Filter Enable (802.1q), SVL/Ingress Filter Disable (802.1d)
Default Value IVL/Ingress Filter Enable (802.1q), SVL/Ingress Filter Disable (802.1d)
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. 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. Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. Set this parameter according to actual situations.
Mount Port
Configurable Ports
Mount each VCTRUNK of the port. -
This parameter specifies the VCTRUNK whose VC paths are to be configured. Adhere to the following principles to plan and set this parameter:
l
Available Bound Paths
The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. As the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. Generally, bidirectional paths are bound.
9-28
Issue 02 (2009-06-15)
Parameter Activation Status
Value Range Activated, Inactivated
Default Value -
Description Displays whether the VCTRUNK is activated.
9.2.3 Modifying the Mounted Port of a Bridge

This operation enables the user to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created.
Precautions
CAUTION
Modifying the ports that are mounted to the bridge may interrupt the service. The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the Service Mount tab. Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.
To change the port that is connected to the 802.1d/802.1q bridge, click the corresponding Mount Port. After selecting the corresponding option from the drop-down list, click Apply. To change the port that is connected to the 802.1ad bridge, click Configure Mount. After changing the settings in the dialog box that is displayed, click OK. ----End
Parameters
Parameter VB Port Mount Port Value Range 1 to 14 Unconnected, a specific PORT, a specific VCTRUNK Default Value Description This parameter specifies the ID of the logical port of the bridge.
l
Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. Set this parameter according to actual situations.
Port Enabled Hub/Spoke
Enabled, Disabled Hub, Spoke
Enabled Hub
Set Port Enabled to Enabled. Otherwise, the port cannot forward the service.
l
The Spoke ports cannot access each other. The Hub port and the Spoke port can access each other. The Hub ports can access each other. Set this parameter according to actual situations. When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 9-2. If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. If all the accessed services are frames that do not have the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
TAG
Tag Aware
9-30
Issue 02 (2009-06-15)
Value Range 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (EMS6)
Default Value Auto-Negotiation
Description
l
The Ethernet ports of different types support different working modes. When the equipment on the opposite side works in the auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation. When the equipment on the opposite side works in the 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. When the equipment on the opposite side works in the 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.
Activation Status
Activated, Inactivated
Displays whether the VCTRUNK is activated.
9.2.4 Creating the VLAN Filter Table

You need to create the VLAN filter table for the bridge when you create the EVPLAN service.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The EVPLAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the VLAN Filtering tab. Step 3 Create the VLAN filter table.
1. 2. 3. 4.
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 Optional: Repeat Step 3.3 to select other forwarding ports. .
5.
Click OK.
----End
Parameters
Parameter VLAN ID (e.g: 1,3-6) Value Range 14095 Default Value Description
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, 36" indicates numbers 1, 3, 4, 5, and 6. Set this parameter according to actual situations.
9-32
Issue 02 (2009-06-15)
Parameter selected forwarding ports
Value Range This parameter indicates the ports that are mounted to a bridge.
Default Value -
Description
l
The packets can be forwarded between the selected forwarding ports only. The ports that are in selected forwarding ports can forward only the packet that carries the VLAN ID (e.g:1,3-6) tag. These ports discard the packet that carries other VLAN tags. The broadcast packet that is transmitted by the ports in selected forwarding ports is broadcast only to the ports included in selected forwarding ports.
9.2.5 Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you can delete the Ethernet private line service to release the corresponding resources.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet private line service must be configured and the service is not be used.
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click Query. Click OK in the dialog box that is displayed. Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete. Click OK in the dialog box that is displayed. Step 4 Click Query. Click OK in the dialog box that is displayed. At this time, the Ethernet private line service is already deleted. ----End
9.2.6 Deleting an Ethernet LAN Service

When an Ethernet LAN service is not used, you can delete the Ethernet LAN service to release the corresponding resources.
Issue 02 (2009-06-15)
9-33
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet LAN service must be configured and the service is not used.
Deleting an Ethernet LAN service involves the following tasks: 1. 2. Deleting the VLAN filtering table Deleting the VB mounting relation
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click Query. Then, click OK in the dialog box that is displayed. Step 3 Click the VLAN Filtering tab. Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete. Then, click OK in the dialog box that is displayed. Step 5 Click the Service Mount tab. Step 6 Select the Ethernet LAN service that needs to be deleted and then click Delete. Then, click OK in the dialog box that is displayed. Step 7 Click Query. Then, click OK in the dialog box that is displayed. At this time, the Ethernet private line service is already deleted. ----End
9.3 Configuring the Cross-Connections of Ethernet Services

In the case of Ethernet over SDH, you need to configure the cross-connections of the Ethernet services. 9.3.1 Creating Cross-Connections of Ethernet Services This topic describes how to create the timeslot connections between the bound paths and the line board, thus to ensure that the Ethernet services are transmitted in specified timeslots over the transmission line. 9.3.2 Deleting the Cross-Connections of an Ethernet Service When the cross-connections of an Ethernet service are deleted, the corresponding crossconnection resources are released.
9.3.1 Creating Cross-Connections of Ethernet Services

This topic describes how to create the timeslot connections between the bound paths and the line board, thus to ensure that the Ethernet services are transmitted in specified timeslots over the transmission line. See 5.2 Creating Cross-Connections of Point-to-Point Services to create the crossconnections of the Ethernet services. If SNCP is configured for the Ethernet services, see 5.3 Creating Cross-Connections for SNCP Services to create the cross-connections of the SNCP Ethernet services.
9.3.2 Deleting the Cross-Connections of an Ethernet Service

When the cross-connections of an Ethernet service are deleted, the corresponding crossconnection resources are released.
Prerequisite
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Query the data. 1. Click Query. Then, the Confirm dialog box is displayed, prompting This operation will query service at the NE and update service date at the NM. Are you sure to continue?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
2. 3.
Step 3 Select the cross-connection of the Ethernet service that needs to be deleted in CrossConnection. Step 4 Deactivate the service. 1. Click Deactivate. Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all selected services (only for activated services?). Click OK. Another Confirm dialog box is displayed, prompting This services of the NE will be cleared by this operation. Are you sure to continue?. Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close. Click Delete. Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the selected services (only for inactive services)?.
2. 3. 4. 1.
Step 5 Delete the service.
Issue 02 (2009-06-15)
2. 3.
Click OK. Then, the Operation Result dialog box is displayed, prompting Operation succeeded. Click Close.
Step 6 Click Query. At this time, the cross-connection of the Ethernet service is already deleted. ----End
9.4 Configuring the QoS

The QoS provides differentiated services. Hence, you can configure the QoS to ensure the quality of the Ethernet services. 9.4.1 Creating a Flow In the case of the Ethernet switching board, a flow refers to the collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations. 9.4.2 Creating the CAR CAR is a type of traffic policing technologies. 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 sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network. 9.4.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. 9.4.4 Binding the CAR/CoS To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS. 9.4.5 Configuring the Traffic Shaping The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packets to be transmitted at an even rate. 9.4.6 Configuring the CoS of the IFH2 Board The IFH2 board supports scheduling packets into different queues according to the corresponding user priority levels in the VLAN tags. 9.4.7 Modifying CAR Parameters The committed access rate (CAR) is the traffic policing technology that is used to check the traffic rate within a specific period (a long time or short time) after the flow classification. The CAR allocates the packets whose rates do not exceed the rate limit of the packets of higher priority, and discards or downgrades the packets whose rates exceed the rate limit. In this process, restriction of the service access to the transport network is realized. That is, you can adjust the rate limit by adjusting the parameters such as the committed information rate and the peak information rate. 9.4.8 Modifying CoS Parameters The class of service (CoS) schedules packets into different priority queues and processes the packets according to the priority levels of the specific queues. Modifying the CoS parameters may affect the priority of the egress packets.
9.4.1 Creating a Flow

In the case of the Ethernet switching board, a flow refers to the collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The associated Ethernet service must be created.
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. Step 3 Click New. The New Flow dialog box is displayed. Step 4 Set the flow parameters.
Issue 02 (2009-06-15)
9-37
Parameters
Parameter Flow Type Value Range Port Flow, Port +VLAN Flow, Port +SVLAN Flow, Port+CVLAN +SVLAN Flow Default Value Port Flow Description 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. 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 line service that uses this port+VLAN as the service source. 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 the 802.1ad bridge) that uses this port + S-VLAN as the service source. Port+CVLAN+SVLAN flow: The packets that are from 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 the 802.1ad bridge) that uses this port + C-VLAN + S-VLAN as the service source. Port PORT1PORT6, VCTRUNK1 VCTRUNK8 (EMS6) PORT1
l
When the associated service is the line service, set this parameter to the source port or sink port of the associated Ethernet service. When the associated service is the Layer 2 switching service, set this parameter to a mounted port of the bridge. This parameter is valid only when Flow Type is set to Port+VLAN Flow. Set this parameter to the source VLAN of the associated Ethernet service. This parameter is valid only when Flow Type is set to Port+SVLAN+CVLAN Flow. Set this parameter to the source C-VLAN of the associated Ethernet service.
VLAN ID
14095
C-VLAN
14095
9-38
Issue 02 (2009-06-15)
Parameter S-VLAN
Value Range 14095
Default Value 1
Description
l
This parameter is valid only when Flow Type is set to Port+SVLAN Flow or set to Port+SVLAN+CVLAN Flow Set this parameter to the source S-VLAN of the associated Ethernet service.
Postrequisite
After creating a flow, bind it to the corresponding CAR or CoS operation as required.
9.4.2 Creating the CAR

CAR is a type of traffic policing technologies. 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 sets the packet whose rate does not exceed the specified rate to high priority 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
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CAR Configuration tab. Step 3 Click New. The New Car dialog box is displayed. Step 4 Set the CAR parameters.
Issue 02 (2009-06-15)
9-39
Parameters
Parameter CAR ID Value Range 165535 (EMS6) Default Value Description This parameter identifies a CAR operation, and is used to bind a flow to an associated CAR operation. This parameter determines whether to enable the CAR operation performed on the flow bound to the CAR.
l
Enabled/Disabled
Enabled, Disabled
Disabled
Committed Information Rate (kbit/s)
An integer ranging from 0 to 1048576, with a step of 64
When the rate of the packets is not more than the CIR, these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion. The value of this parameter should not be more than the PIR.
9-40
Issue 02 (2009-06-15)
Parameter Committed Burst Size (kbyte)
Value Range 01024
Default Value 0
Description When the rate of the packets that pass the restriction of the CAR is not more than the CIR in a certain period, certain 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
Peak Information Rate (kbit/s)
When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When 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 can pass the restriction of the CAR and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The value of this parameter should not be more than the bandwidth at the port.
01024
When the rate of the packets that pass the restriction of the CAR is more than the CIR but is not more than the PIR, certain 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 set 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.
Issue 02 (2009-06-15)
9-41
Postrequisite
After creating the CAR, bind the flow to the corresponding CAR operation as required.
9.4.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
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. 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.
9-42
Issue 02 (2009-06-15)
Parameters
Parameter CoS ID Value Range 165535 Default Value 1 Description This parameter identifies a CoS operation, and is used to bind a flow to an associated CoS operation.
l
CoS Type
In the case of the EMS6 board:

l l l
simple VLAN priority DSCP

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. 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. 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.
Issue 02 (2009-06-15)
9-43
Value Range In the case of the EMS6 board: 07
Default Value 0
Description This parameter specified which queue a packet is scheduled to. In the case of the EMS6 board:
l
Each port on the EMS6 board supports eight egress queues, and the CoS priorities of these eight queues are from 0 to 7. If the traffic shaping feature of all the queues is enabled or disabled, the queue whose CoS priority is 7 is an SP queue, and the other queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6). If the traffic shaping feature of certain queues is enabled, the bandwidth is allocated first to the queue whose traffic shaping feature is enabled, according to the set CIR. The remaining bandwidth is allocated to the queues whose traffic shaping is disabled, according to the SP +WRR algorithm.
Postrequisite
After creating the CoS, bind the flow to the corresponding CoS operation as required.
9.4.4 Binding the CAR/CoS

To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The flow and CAR/CoS must be created.
Precautions
9-44
Issue 02 (2009-06-15)
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management . Step 2 Click the Flow Configuration tab. Step 3 Bind the CAR/CoS.
Parameters
Parameter Bound CAR Value Range Default Value Description 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. This parameter indicates the CoS ID corresponding to a CoS operation. In the case of the EMS6 board, different CoS IDs should be bound to different flows, even though the parameters of the CoS operations are the same.
Bound CoS
9.4.5 Configuring the Traffic Shaping

The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packets to be transmitted at an even rate.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 In Port List, select a port. Step 3 Set the traffic shaping information about the port queue.
Parameters
Parameter Port Enabled/Disabled Value Range A specific PORT or VCTRUNK Enabled, Disabled Default Value Disabled Description This parameter indicates the port whose traffic is shaped.
l
This parameter determines whether to enable the traffic shaping of an egress queue. If the traffic shaping feature of certain queues is enabled, the bandwidth is allocated first to the queue whose traffic shaping feature is enabled, according to the set CIR. The remaining bandwidth is allocated to the queues whose traffic shaping is disabled, according to the SP +WRR algorithm. When the rate of the packets is not more than the CIR, these packets directly enter the egress queue. The value of this parameter should not be more than the PIR.
CIR (kbit/s)
9-46
Issue 02 (2009-06-15)
Parameter PIR (kbit/s)
Value Range An integer ranging from 0 to 1048574, with a step of 64
Default Value 0
Description
l
When the rate of the packets is more than the PIR, the packets that exceed the rate restriction are directly discarded. 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 enter the buffer of the CIR. When the buffer overflows, the packets are marked yellow and enter the egress queue, which enables these packets to be discarded first in the case of queue congestion. The value of this parameter should not be more than the bandwidth at the port.
9.4.6 Configuring the CoS of the IFH2 Board

The IFH2 board supports scheduling packets into different queues according to the corresponding user priority levels in the VLAN tags.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IFH2 board must be added in the NE Panel.
Procedure
Step 1 Select the IFH2 board in the NE Explorer. Then, choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Set CoS Priority for User Priority 0 in the VLAN Tag to User Priority 7 in the VLAN Tag.

Parameters
Parameter CoS Parameter Value Range 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 03 Default Value Description This parameter specifies the data flows. The IFH2 boards supports differentiating the data flows according to the user priority levels in the VLAN tags of packets.
CoS Priority
This parameter specifies the queue to which a packet should be scheduled. The IFH2 board supports four queues. The corresponding CoS priority levels that correspond to the four queues are 0 3 and the scheduling scheme is SP. The higher the CoS priority, the higher is the queue priority.
9.4.7 Modifying CAR Parameters

The committed access rate (CAR) is the traffic policing technology that is used to check the traffic rate within a specific period (a long time or short time) after the flow classification. The CAR allocates the packets whose rates do not exceed the rate limit of the packets of higher priority, and discards or downgrades the packets whose rates exceed the rate limit. In this process, restriction of the service access to the transport network is realized. That is, you can adjust the rate limit by adjusting the parameters such as the committed information rate and the peak information rate.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The CAR must be configured.
Precautions
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CAR Configuration tab. Step 3 Click Query. Step 4 Select CAR ID that needs to be changed. Step 5 Modify the other parameters that need to be modified.
Parameters
For details, see 9.4.2 Creating the CAR.
9.4.8 Modifying CoS Parameters

The class of service (CoS) schedules packets into different priority queues and processes the packets according to the priority levels of the specific queues. Modifying the CoS parameters may affect the priority of the egress packets.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The CoS must be configured.
Precautions
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CoS Configuration tab. Step 3 Click Query. Step 4 Select the CoS ID that needs to be changed. Step 5 Select the CoS Parameter that needs to be changed.
Step 6 Modify CoS Priority.
Parameters
For details, see 9.4.3 Creating the CoS.
9.5 Creating a LAG

Link aggregation allows all the members in a LAG to share the incoming and outgoing service loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to each other dynamically. This increases the availability of the connection.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The physical network topology must be established. Ethernet boards must be created.
Procedure
Step 1 In the NE Explorer, select an Ethernet board 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 and the Create Link Aggregation Group dialog box is displayed. Set the parameters.
9-50
Issue 02 (2009-06-15)
Step 4 Click OK. Step 5 Optional: Click the Link Aggregation Parameters tab. Set Port Priority and System Priority.
NOTE
l l
The port ID consists of Port and Port Priority. The port that has the smallest port ID in a LAG has the priority to be aggregated first. The system ID consists of System Priority and System MAC Address. When the system negotiates with the remote system, the system with the smallest ID has the priority to choose the port. In this example, the system refers to the board, and the system MAC address refers to the MAC address of the board. The factory-set MAC address is globally unique and cannot be modified.
----End
Parameters
Field LAG No. LAG Name Value An integer from 1 to 7(EMS6) For example: LAG_1 Default Description Displays the LAG number. Displays the LAG name.
Issue 02 (2009-06-15)
9-51
Field LAG Type
Value Manual, Static
Default Static
Description
l
Static: If this value is selected, you can manually create a LAG with the LACP protocol. You can verify the working status (selected or standby) of ports in the LAG. In a LAG, a port can be in the Selected or Standby state. The convergence information is exchanged among the different equipment through the LACP protocol, so that the convergence information can be consistent. Manual: If this value is selected, you can manually create a LAG with no LACP protocol. The port can be in the UP or DOWN state. According to the physical (UP or DOWN) state of the port, you can determine whether to perform a convergence.
In the case of the LAG that is created for the IF 1+1 protection, this parameter is set to Manual. In other situations, set this parameter according to the requirements of the opposite equipment.
9-52
Issue 02 (2009-06-15)
Field Load Sharing
Value Sharing, NonSharing
Default Sharing
Description
l
Sharing: If this value is selected, each member link of a LAG has traffic at the same time and shares loads together. The load sharing can increase a higher bandwidth for the link. When the LAG members change, or certain links fail, the system automatically reallocates the traffic. Non-Sharing: Only one member link of a LAG has traffic, and other links are standby. In this case, a type of hot backup mechanism is provided. When the active link of a LAG fails, the system chooses one link from the standby links of the LAG and activates it, to suppress the link failure.
In the case of the LAG that is created for the IF 1+1 protection, this parameter is set to Non-Sharing. In other situations, set this parameter according to the requirements of the opposite equipment.
Issue 02 (2009-06-15)
9-53
Field Sharing Mode
Value IP Sharing Mode, MAC Sharing Mode
Default IP Sharing Mode
Description This parameter can be set only when Load Sharing is set to Sharing. This parameter can be set only when Load Sharing is set to Non-Sharing. If the Hybrid microwave is configured with the 1 +1 IF protection, set this parameter to Non-Revertive.
Revertive Mode
Non-Revertive, Revertive
Revertive
9-54
Issue 02 (2009-06-15)
Field Main Port
Value For example: PORT1
Default -
Description The main port in a LAG.

l
In the case of the LAG that is created for the IF 1 +1 protection, you need to select the port that is interconnected with the active IF board IFH2 for this parameter. In other situations, set this parameter according to the requirements of the opposite equipment.
After a LAG is created, you can add Ethernet services to the main port only. Services cannot be added to a slave port. When the Load Sharing parameter is set to Non-Sharing, all services are transmitted on the link to which the main port is connected. The links to which other slave ports are connected function as protection links.
Issue 02 (2009-06-15)
9-55
Field Slave Port
Value -
Default -
Description The slave port in a LAG. The parameter specifies that a link aggregation group is manually created rather than being automatically created by the system. A link aggregation group contains main ports and slave ports. The slave ports in a link aggregation group are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the link aggregation group.
Available Slave Ports
For example: PORT2
In the case of the LAG that is created for the IF 1 +1 protection, you need to select the port that is interconnected with the standby IF board IFH2 for this parameter. In other situations, set this parameter according to the requirements of the opposite equipment.
Selected Slave Ports
For example: PORT2
Displays the port that is selected as a slave port.
9-56
Issue 02 (2009-06-15)
Field Status
Value Unknown, In Service, Out of Service
Default -
Description The parameter specifies the state, which is derived from logical computation, of each member ports in a link aggregation group.
l
If you do not query a LAG, the port status is Unknown. If the port is the actually working port and services are forwarded at the port, the port status is In Service. If the port is the standby port and no service is forwarded at the port, the port status is Out of Service.
Port Priority
0-65535, in step length of 1
32768
This parameter is valid only when the LAG Type of a LAG is set to Static. 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. When ports are added into a LAG, the port with highest priority is preferred to transmit services.
Issue 02 (2009-06-15)
9-57
Field System Priority
Value 0-65535, in step length of 1
Default 32768
Description This parameter is valid only when LAG Type of a LAG is set to Static. This parameter indicates the priority of a LAG. The smaller the value, the higher the priority. When a local LAG negotiates with an opposite LAG through LACP packets, both LAGs can obtain the system priorities of each other. Then, the computation result based on the logic that is selected by the LAG with the higher system priority is considered as the result of both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the computation result based on the logic that is selected by the LAG with lower system MAC address is considered as the result of both LAGs.
System MAC Address
For example: 00-16EC-FA-AC-0A
Displays the system MAC address.
NOTE
For different boards, the value ranges of the port and system priorities are different.
9.6 Configuring the Layer 2 Switching Feature

You can configure the Layer 2 switching feature for Ethernet LAN services according to the actual service requirements.
9.6.1 Creating the Entry of a MAC Address Table Manually The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode. In addition, you can manually add the entry of a MAC address table. The manually created entries of a MAC address table can be classified into two categories: unicast entry (that is, static entry) and disabled entry (that is, blacklist entry). 9.6.2 Modifying the Aging Time of the MAC Address Table Entry In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5 minutes by default. 9.6.3 Configuring the Spanning Tree Protocol In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge and set bridge parameters and port parameters. 9.6.4 Configuring the IGMP Snooping Protocol If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet. 9.6.5 Modifying the Aging Time of the Multicast Table Item In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes by default. 9.6.6 Configuring the Broadcast Packet Suppression Function When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.
9.6.1 Creating the Entry of a MAC Address Table Manually

The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode. In addition, you can manually add the entry of a MAC address table. The manually created entries of a MAC address table can be classified into two categories: unicast entry (that is, static entry) and disabled entry (that is, blacklist entry).
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The VLAN filter table must be created.
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Optional: Create the unicast entry manually. 1.
Issue 02 (2009-06-15)
Select the bridge that is already created, and click the VLAN Unicast tab.
2. 3.
Click New. The Create VLAN Unicast dialog box is displayed. Set the parameters of the unicast entry.
4.
Click OK.
Step 3 Optional: Create the disabled entry manually. 1. 2. 3. Select the bridge that is already created, and click the Disable MAC Address tab. Click New. The Disable MAC Address Creation dialog box is displayed. Set the parameters of the disabled entry.
4.
Click OK.
----End
Parameters
Parameter VLAN ID (e.g. 1,3-6) Value Range 14095 Default Value Description
l
In the case of the 802.1d bridge and the 802.1ad bridge, this parameter is invalid if the SVL mode is used. The set entry applies to all the VLANs. In the case of the 802.1q bridge and the 802.1ad bridge, the set entry applies only to the VLAN whose ID is equal to the set value of this parameter if the IVL mode is used. Set this parameter according to actual situations.
MAC Address Physical Port
Each port that is mounted to a bridge
Set this parameter according to actual situations. This parameter indicates the Ethernet port corresponding to a MAC address. Set this parameter according to actual situations.
9.6.2 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5 minutes by default.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree. Step 2 Modify the aging time of the MAC address table entry. 1. 2. Double-click MAC Address Aging Time corresponding to this Ethernet switching board. The MAC Address Aging Time dialog box is displayed. Set the duration and unit of the aging time.
3.
Click OK.
Issue 02 (2009-06-15)
9-61
Parameters
Parameter MAC Address Aging Time Value Range 1 Min to 120 Day Default Value 5 Min Description
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 relearning of this MAC address, this entry is automatically deleted. This mechanism is called aging, and this period is called aging time. If this parameter is set 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. If this parameter is set to a very small value, the bridge may delete the MAC address table entry that is needed, which reduces the forwarding efficiency. It is recommended that you use the default value.
9.6.3 Configuring the Spanning Tree Protocol

In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge and set bridge parameters and port parameters.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Optional: Set the enabled status of the protocol. 1. 2.
9-62
Click the Protocol Enable tab. Configure parameters of the enabled protocol.
3.
Click Apply.
Step 3 Optional: Set bridge parameters. 1. 2. Click the Bridge Parameter tab. Set bridge parameters.
3.
Click Apply.
Step 4 Optional: Set port parameters. 1. 2. Click the Port Parameter tab. Set port parameters.
3.
Click Apply.
Step 5 Optional: If you are enabling the RSTP, set the point-to-point attribute of the Ethernet port. 1. 2. Click the Point to Point Attribute tab. Set the point-to-point attribute.
3.
Click Apply.
----End
Parameters
Parameter Protocol Enabled Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter determines whether to enable the spanning tree protocol. It is recommended that you do not enable the STP or RSTP in the service networking process, because this can prevent the Layer 2 service from forming the loop. If the loop is already formed in the service networking, you must start the STP or RSTP.
Issue 02 (2009-06-15)
9-63
Parameter Protocol Type
Value Range STP, RSTP
Default Value RSTP
Description
l
This parameter is valid only when Protocol Enabled is set to Enabled. The protocol type should be set according to the requirement of the interconnected Ethernet equipment. Generally, it is recommended that you use the default value. The most significant 16 bits of the bridge ID indicates the priority of the bridge. The smaller the value of this parameter, the higher the priority and the higher the possibility that the bridge is selected as the root bridge. 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. This parameter indicates the maximum age of the CBPDU packet that is recorded by the port. 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. This parameter indicates the interval of transmitting the CBPDU packet of the bridge. The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases. This parameter indicates the holding time of a port in the listening state and in the learning state. The greater the value, the longer the delay time of the network state change. Hence, the topology changes are slower and the recovery in the case of faults is slower.
Priority (Bridge Parameter)
061440
32768
Max Age (s)
640
20
Hello Time (s)
110
Forward Delay (s)
430
15
TxHoldCout (per second)
110
This parameter indicates the number of times the port transmits the CBPDU in every second.
9-64
Issue 02 (2009-06-15)
Parameter Priority (Port Parameters)
Value Range 0240
Default Value 128
Description
l
The most significant eight bits of the port ID indicate the port priority. The smaller the value of this parameter, the higher the priority. This parameter indicates the status of the network that the port is connected to. In the case of the bridges on both ends of the path, set this parameter to the same value. This parameter is valid only when the RSTP is used. This parameter determines 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. This parameter is set to Enabled only when the Ethernet port of the Ethernet board is directly connected to the data communication terminal equipment, such as a computer. In other cases, it is recommended that you use the default value. Specifies whether the STP/RSTP protocol is enabled for the port. When this parameter is set to Disabled, the BPDU cannot be processed and transmitted. It is recommended that this parameter adopts the default value. This parameter is valid only when Admin Edge Attribute is set to Enabled. When this parameter is set to Enabled, if the bridge detects that this port is connected to the port of other bridges, the RSTP considers this port as a non-edge port. If Admin Edge Attribute is set to Enabled, set this parameter to Enabled. In other cases, it is recommended that you use the default value.
Port Path Cost
165535
Admin Edge Attribute
Enabled, Disabled
Disabled
Protocol Enabled
Enabled, Disabled
Enabled
Auto Edge Detection
Enabled, Disabled
Disabled
Issue 02 (2009-06-15)
9-65
Parameter Point-to-Point Attribute
Value Range Adaptive connection, Link connection, Shared media
Default Value Adaptive connection
Description
l
This parameter is valid only when the RSTP is used. 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 actual working mode of the port is full-duplex, the actual point-topoint attribute of the port is "true". If the actual working mode of the port is halfduplex, the actual point-to-point attribute of the port is "false". If this parameter is set to Link connection, the actual point-to-point attribute of the port is "true". If this parameter is set to Shared media, the actual point-to-point attribute of the port is "false". Only the port whose point-to-point attribute is "true" can transmit the rapid transition request and response. It is recommended that you use the default value.
NOTE
l l
In the service networking process, it is recommended that you prevent the loop from forming in the case of the Layer 2 service and thus avoid enabling the STP or RSTP. Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the related parameters as instructed, before enabling the STP or RSTP.
9.6.4 Configuring the IGMP Snooping Protocol

If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The VLAN filter table must be created.
9-66
Issue 02 (2009-06-15)
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Protocol Enable tab. Step 3 Set the information related to the IGMP Snooping protocol.
Parameters
Parameter Protocol Enable Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter determines whether to enable the IGMP Snooping protocol. If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol according to the requirement. This parameter is valid only when Protocol Enabled is set to Enabled. If the 802.1q bridge or the 802.1ad bridge receives a multicast packet whose multicast address has no mapping item in the multicast table (that is, this multicast packet is an unknown multicast packet), this parameter indicates the method for processing this packet. When this parameter is set to Enabled, The unknown multicast packet is discarded. When this parameter is set to Disabled, the unknown multicast packet is broadcast in the VLAN. Set this parameter according to the requirement of the IGMP multicast server.
The Discarded Tag of the Packet Excluded in the Multicast Group
Enabled, Disabled
Enabled
Issue 02 (2009-06-15)
9-67
9.6.5 Modifying the Aging Time of the Multicast Table Item

In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes by default.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The IGMP Snooping protocol of the bridge must be enabled.
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. 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 item.
9-68
Issue 02 (2009-06-15)
Parameters
Parameter Multicast Aging Time (Min) Value Range 1120 Default Value 8 Description
l
When a table item is not updated in a certain period (that is, no IGMP request from this multicast address is received), this table item is automatically deleted. This mechanism is called aging, and this period is called aging time. If this parameter is set to a very large value, the bridge stores excessive multicast table items that are outdated, which exhausts the resources of the multicast table. If this parameter is set to a very small value, the bridge may delete the multicast table item that is needed, which reduces the forwarding efficiency.
9.6.6 Configuring the Broadcast Packet Suppression Function

When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select External Port. Step 2 Click the Advanced Attributes tab. Step 3 Set Enabling Broadcast Packet Suppression and Broadcast Packet Suppression Threshold.
Parameters
Parameter Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Value Range Disabled Enabled 10% to 100% 30% Default Value Disabled Description This parameter specifies whether to enable the broadcast packet suppression function. When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.
9.7 LPT Configuration

When enabling the LPT function for an Ethernet service, you need to configure the LPT port and the related information.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet data board supports the LPT function. The port-based Ethernet private line service must be created and activated. The data service is configured as the pure transparent service.
Precautions
NOTE
l l
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On one board, you can select only one configuration mode to realize the LPT function. The data service of the point-to-point LPT is configured as the pure transparent service.
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 that of the LPT.
9-70
Issue 02 (2009-06-15)
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Step 2 Optional: Configuring Point-to-Point LPT. 1. 2. Click Query. The Operation Result dialog box is displayed. Click Close. Select a PORT and a VCTRUNK port, and then set the following parameters. For parameters of the point-to-point LPT, see Table 9-3.
NOTE
If LPT is enabled, you can set Port-Type Port Hold-Off Time(ms) and VCTRUNK Port HoldOff Time(ms) as required.
3. 4. 5.
Click Apply and a prompt appears telling you the operation was successful. Click Close. Repeat Steps 1 through 2 to configure point-to-point LPT for the opposite NE.
Step 3 Optional: Configuring Point-to-Multipoint LPT. 1. 2. 3. Click Advanced Configuration. In the LPT Management window, click New. In the Create LPT window, select Port from the Convergence Point pane, and set HoldOff Time(ms).
NOTE
If the port at the convergence point is a VCTRUNK port, you need to set Bearer Mode.
Issue 02 (2009-06-15)
9-71
4.
In the Access Point pane, select an appropriate Port and click . Double-click Bearer Mode and select an appropriate bearer mode from the drop-down list.For parameters of the point-to-multipoint LPT, see Table 9-4.
NOTE
l l
If the port at the convergence point is not a VCTRUNK port, do not set Bearer Mode. If you want to modify Bearer Mode, you can modify it in the Modify LPT window.
5. 6.
Click OK. Click Close in the Operation Result dialog box. Repeat Steps 1 and Steps 3 to configure point-to-multipoint LPT for other NEs.
----End
Parameter
Table 9-3 Parameter of the Point-to-Point LPT Field Port Value For example: PORT1 For example: VCTRU NK1 Positive, Reverse Default Description The external port of board.
VCTRUNK Port
The VCTRUNK port where EPL services are transparently transmitted. The direction of the EPL services that are transparently transmitted. The direction is Positive if the source port is a PORT port and the sink port is a VCTRUNK port. The direction is Reverse if the source port is a VCTRUNK port and the sink port is a PORT port.
Direction
LPT Bearer Mode
Yes, No GFP (HUAW EI), Ethernet 0 to 10000
No GFP(HUAWEI)
Sets whether to use LPT. This parameter is valid only when the LPT occurs. The bearer mode of LPT frames.
Port-Type Port Hold-Off Time (ms)
100
This parameter is valid only when the LPT occurs. When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
9-72
Issue 02 (2009-06-15)
Field VCTRUNK Port Hold-Off Time (ms)
Value 0 to 10000
Default 100
Description This parameter is valid only when the LPT occurs. When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
Table 9-4 Parameter of the Point-to-Multipoint LPT Field Convergence Point Port Value PORT1 to PORT6, VCTRUNK1 to VCTRUNK8 GFP (HUAWEI), Ethernet Default PORT1 Description The port where the convergence point resides. The bearer mode of the port where the access point resides. This parameter can be edited only when it is supported by a board. Hold-Off Time (ms) 0 to 10000 0 If LPT switching is enabled, the port notifies the opposite end after the holdoff time. The port where the access point resides. The bearer mode of the port where the access point resides. This parameter can be edited only when it is supported by a board.
Bearer Mode
GFP (HUAWEI)
Access Point
Port
PORT1 to PORT6, VCTRUNK1 to VCTRUNK8 GFP (HUAWEI), Ethernet
Bearer Mode
GFP (HUAWEI)
Issue 02 (2009-06-15)
9-73
10 Configuring the Orderwire and Auxiliary Interfaces
10
About This Chapter
Configuring the Orderwire and Auxiliary Interfaces
This topic describes how to configure the orderwire, synchronous data services, asynchronous data services, and external alarms. 10.1 Configuring the Orderwire This topic describes how to configure the orderwire. When the orderwire is enabled, it can provide a dedicated communication channel for the network maintenance engineers. 10.2 Configuring Synchronous Data Services To configure the synchronous data services, you need set the F1 data port of the OptiX RTN 600. The synchronous data services are transmitted over the F1 overhead bytes in the radio frame or STM-N frame. The transmission rate is 64 kbit/s, that is, E0 level. 10.3 Configuring Asynchronous Data Services To configure the asynchronous data services, you need to set the broadcast data port of the OptiX RTN 600. The Serial byte in the radio overheads or any of the bytes Serial1Serial4 in the normal SDH overheads is used to transparently transmit the asynchronous data services. 10.4 Configuring External Alarms To configure external alarms, you need to configure the environment monitor port on the EOW board of the OptiX RTN 600. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 600 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 600 and then to the processing equipment at the remote end. 10.5 Configuration Example (Synchronous Data Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the synchronous data service requirements. 10.6 Configuration Example (Asynchronous Data Services) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the point-to-point asynchronous data service requirements.
10.7 Configuration Example (External Alarms) This topic uses an example to describe how to plan the parameters of the external alarms and complete the data configuration according to the external alarm requirements.
10-2
Issue 02 (2009-06-15)
10.1 Configuring the Orderwire

This topic describes how to configure the orderwire. When the orderwire is enabled, it can provide a dedicated communication channel for the network maintenance engineers.
Prerequisite
Context
The communication channel must be available for activating the orderwire.
l
When an SDH optical/electrical line exists between two NEs, the overhead byte E1 or E2 in the SDH frames can be used as the orderwire communication channel. When a radio link exists between two NEs, a fixed overhead byte in the radio frames can be used as the orderwire communication channel. When no SDH optical/electrical line and microwave link exists between two NEs, connect the external clock ports or synchronous data ports of the two NEs to provide the orderwire communication channel.
The OptiX RTN 600 supports the group call function of the orderwire. When an OptiX RTN 600 dials the orderwire group call number 888, the orderwire phones of all the OptiX RTN 600s in the orderwire subnet ring. When an OptiX RTN 600 answers the phone call, the other OptiX RTN 600s stop ringing, that is, the group call becomes a point-to-point call between two NEs.
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.
Issue 02 (2009-06-15)
10-3
Step 4 Click Apply. Step 5 Optional: Modify the orderwire occupied overhead bytes. 1. 2. Click the Advanced tab. Configure Orderwire Occupied Bytes.
3.
Click Apply.
----End
10-4
Issue 02 (2009-06-15)
Parameters
Parameter Call Waiting Time (s) Value Range 19 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. If less than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to 5s. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to 9s. Set the same call waiting time for all the NEs. This parameter indicates the orderwire phone number of the local station. The length of the orderwire phone number of each NE should be the same. It is recommended that the phone number consists of three numerics. The orderwire phone number of each NE should be unique. It is recommended that the phone numbers are allocated from 101 for the NEs according to the NE IDs. The orderwire phone number cannot be set to the group call number 888 and cannot start with 888.
Phone 1
10099999999
101
Issue 02 (2009-06-15)
10-5
Parameter Orderwire port
Value Range Line ports, external clock port, F1 port
Default Value -
Description
l
This parameter indicates the ports that can transmit the orderwire information. The OptiX RTN 600 does not support conference calls and thus allows the lines that transmit the orderwire information to form a loop. If the radio link between two nodes is configured with 1+1 protection, only the line port of the main IF board need to be used as the orderwire port. If multiple links (for example, configured with XPIC or N+1 protection) exist between two nodes, the line ports corresponding to all the links need to be used as the orderwire ports. When orderwire communication is implemented by interconnecting the two NEs through the external clock ports, the external clock ports need to be used as the orderwire ports. When orderwire communication is implemented by interconnecting the two NEs through the synchronous data ports, the F1 port need to be used as the orderwire port. This parameter indicates the overhead byte that is used to transmit the orderwire information. Regardless the parameter value, the radio link uses a fixed self-defined overhead byte to transmit the orderwire information. Hence, this parameter should be set according to the occupied SDH overhead bytes in the ordinary SDH.
Orderwire Occupied Bytes
E1, E2
E1
10.2 Configuring Synchronous Data Services

To configure the synchronous data services, you need set the F1 data port of the OptiX RTN 600. The synchronous data services are transmitted over the F1 overhead bytes in the radio frame or STM-N frame. The transmission rate is 64 kbit/s, that is, E0 level.
Prerequisite
The boards that are related to the synchronous data services must be configured.
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 Press the Ctrl key and select two data channels from Available Data Channel. Click .
Parameters
Parameter Data Channel 1, Data Channel 2 Value Range Depending on the board configuration , the following ports can be selected: SDH optical/ electrical port, IF port, F1 port, and external clock port of the PXC board. Default Value Description
l
When the SDH optical/electrical line port is selected, the F1 byte in the SDH frame of this port is used. When the IF port is selected, the self-defined F1 byte in the radio frame of this port is used. When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port conforms to the G.703 and the rate is 64 kbit/s. When the PXC-1 is selected, the external clock port of the PXC board is used. In this case, the external clock port is used as the output port of the overhead bytes.
Issue 02 (2009-06-15)
10-7
10.3 Configuring Asynchronous Data Services

To configure the asynchronous data services, you need to set the broadcast data port of the OptiX RTN 600. The Serial byte in the radio overheads or any of the bytes Serial1Serial4 in the normal SDH overheads is used to transparently transmit the asynchronous data services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards that are related to the asynchronous data services must be configured.
Context
The asynchronous data port of the OptiX RTN 600 is an RS-232 port and can implement the universal asynchronous receiver/transmitter (UART) full-duplex communication. The service transmission is required to be point-to-point transparent transmission. Therefore, the port rate and transmission control protocol need not be configured and the maximum communication rate is 19.2 kbit/s. Hence, the asynchronous data port is also considered as the transparent data port.
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 Set the parameters of the broadcast data port.
10-8
Issue 02 (2009-06-15)
Parameters
Parameter Overhead Byte Value Range SERIAL1 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. In the case of a radio link, a self-defined Serial overhead byte in the radio frame is used to transmit the asynchronous data services. When this parameter is set so that it is the same as the SERIAL byte corresponding to the Overhead Byte, the asynchronous data port on the SCC board is used. When this parameter is set to the SDH optical/electrical line port, the Overhead Byte of this port is used. When this parameter is set to IF port, the self-defined Serial byte in the radio frame of this port is used. When this parameter is set to the external clock port on the PXC board, the external clock port on the PXC board is used. In this case, the external clock port is used as the output port of overhead bytes.
Broadcast Data Source
Depending on the board configuration , the following values can be selected: SERIAL1 SERIAL4, SDH optical/ electrical port, IF port, and external clock port of
No Data
l l l
Issue 02 (2009-06-15)
10-9
Parameter Broadcast Data Sink
Value Range the PXC board.
Default Value
Description
10.4 Configuring External Alarms

To configure external alarms, you need to configure the environment monitor port on the EOW board of the OptiX RTN 600. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 600 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 600 and then to the processing equipment at the remote end.
Prerequisite
Context
The external alarms of the OptiX RTN 600 are also considered as housekeeping alarms. The external alarm port of the OptiX RTN 600 is a relay port. This port can be either in the "on" state or in the "off" state. OptiX RTN 600 IDU 610/620 provides two alarm output ports and six 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 EOW 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.
10-10
Select Input Relay from the drop-down list. Set the parameters of the input alarm.
3. 1. 2.
Click Apply. Select Output Relay from the drop-down list. Set the parameters of the output alarm.
Step 3 Configure the output alarm.
3.
Click Apply.
----End
Parameters
Parameter Using Status Value Range Used, Unused Default Value Unused Description This parameter is valid for the input relay and is used to set the usage status of this alarm port.
Issue 02 (2009-06-15)
10-11
Parameter Alarm Mode
Value Range
l
Default Value
l
Description Input Relay:

l
Input Relay: An Alarm is Generated if the Relay Turns Off and Low Level is Caused, An Alarm is Generated if the Relay Turns On and High Level is Caused
Input Relay: An Alarm is Generated if the Relay Turns Off and Low Level is Caused
Output Relay: Alarm Occurs when Relay Turns Off

l
If this parameter is set to An Alarm is Generated if the Relay Turns On and High Level is Caused, the alarm is generated when the relay is on. If this parameter is set to An Alarm is Generated if the Relay Turns Off and Low Level is Caused, the alarm is generated when the relay is off. If this parameter is set to Alarm Occurs when Relay Turns Off, the alarm is generated when the relay is off. If this parameter is set to Alarm Occurs when Relay Turns On, the alarm is generated when the relay is on.
Output Relay: Alarm Occurs when Relay Turns Off, Alarm Occurs when Relay Turns On
Output Relay:
l
Use or Not
Used, Unused
Unused
This parameter is valid for the output relay and is used to set the usage status of this alarm port. This parameter is valid for the output relay.
l
Working Mode
Automatic, Manual
Automatic
Automatic: Changing the status of the output relay according to Alarm Trigger Conditions and Alarm Mode Manual: Determining the status of the output relay manually
10-12
Issue 02 (2009-06-15)
Parameter Alarm Trigger Conditions
Value Range
l
Default Value
l
Description This parameter is valid for the output relay.

l
Available values when Working Mode is set to Automatic: Input Path 1Input Path 6, Automatically triggered by Critical & Major alarms, Major Alarm Auto Trigger, and Critical Alarm Auto Trigger Available values when Working Mode is set to Manual: Output Low Level in Manual and Output High Level in Manual
Automatic: Automatically triggered by Critical & Major alarms Manual: Output High Level in Manual
Automatic: Automatically changing the status of the relay according to the preset value Manual: Outputting the high level or low level according to the setting
10.5 Configuration Example (Synchronous Data Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the synchronous data service requirements. 10.5.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 10.5.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs. 10.5.3 Configuration Process You can configure the synchronous data services of each NE based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. As shown in Figure 10-1, NE1, NE2, and NE3 are the OptiX RTN 600 NEs configured with the IDU 620. The new service requirements are as follows: the data communication equipment
between NE1 and NE3 must communicate with each other, and the required bandwidth must be 64 kbit/s. Figure 10-1 Networking diagram
NE 1 NE 2 NE 3
64kbit/s
64kbit/s

According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs.

The SCC boards of NE1 and NE3 need to provide the F1 synchronous data ports. In the case of the OptiX RTN 600, the SL61SCC VER.C provides the F1 synchronous data port whereas the SL61SCC VER.B does not provide the F1 synchronous data port.
Configuring the Synchronous Data Port

Table 10-1 Configuration of the synchronous data port Parameter Data Channel 1 Data Channel 2 NE1 6-SL1 F1 NE2 5-IF1A 6-SL1 NE3 5-IF1A F1

Figure 10-2 Timeslot allocation of synchronous data services
Station Timeslot NE1 6-SL1-1 F1 2-SCC: F1 Add/Frop Forward NE2 6-SL1-1 5-IF1A-1 F1 2-SCC: F1 NE3 5-IF1A-1
10-14
Issue 02 (2009-06-15)
The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of NE3 are used to add/drop the synchronous data services. The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1 board in slot 6 of NE2 is used to transmit the synchronous data services. The F1 overhead byte on the radio link between the IF1A board in slot 5 of NE2 and the IF1A board in slot 5 of NE3 is used to transmit the synchronous data services. The synchronous data services are passed through between the SL1 board in slot 6 and the IF1A board in slot 5 of NE2.
10.5.3 Configuration Process

You can configure the synchronous data services of each NE based on the parameters of the service planning, by using the NMS.
Prerequisite
l l
All the required boards must be added. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 Configure the synchronous data services. 1. 2. 3. In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply. Parameter Data Channel 1 Data Channel 2 Value Range 6-SL1-1 F1 Description When the 6-SL1-1 port is selected, the F1 byte in the SDH frame of this port is used. When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port complies with ITU-T G.703 and the rate is 64 kbit/ s.
Step 2 Configure the synchronous data services. 1. 2. 3. In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply.
Issue 02 (2009-06-15)
10-15
Parameter Data Channel 1 Data Channel 2
Value Range 6-SL1-1 5-IF1A-1
Description When the 6-SL1-1 port is selected, the F1 byte in the SDH frame of this port is used. When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is used.
Step 3 Configure the synchronous data services. 1. 2. 3. In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply. Parameter Data Channel 1 Value Range 5-IF1A-1 Description When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is used. When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port complies with ITU-T G.703 and the rate is 64 kbit/ s.
Data Channel 2
F1
----End
10.6 Configuration Example (Asynchronous Data Services)

This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the point-to-point asynchronous data service requirements. 10.6.1 Networking Diagram The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 10.6.2 Service Planning The timeslot allocation can be planned for the asynchronous data services based on the networking diagram. 10.6.3 Configuration Process You can configure the asynchronous data services of each NE based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements.
As shown in Figure 10-3, NE1, NE2, and NE3 are the OptiX RTN 600 NEs configured with the IDU 620. Asynchronous data services need to be activated between NE1 and NE3. The service requirements are as follows:
l l l
NE1 must be connected to the monitor server. NE3 must be connected to the environment monitor. Point-to-point communication must exist between the monitor server and the environment monitor, through services at the asynchronous data ports. The requirements for the environment monitor are as follows:
The level of the port must be RS-232. Logic "1" stands for 5 V to 15 V, and logic "0" stands for +5 V to +15 V. When no data is transmitted, the port must be of high RS-232 level (about 9 V).

NE 1 NE 2 NE 3
RS-232
RS-232

The timeslot allocation can be planned for the asynchronous data services based on the networking diagram.
Configuration of the Asynchronous Data Services

Table 10-2 Configuration of the asynchronous data services Parameter Overhead Byte Broadcast Data Source Broadcast Data Sink NE1 SERIAL1 6-SL1-1 S1 NE2 SERIAL1 5-IF1A-1 6-SL1-1 NE3 SERIAL1 5-IF1A-1 S1
Issue 02 (2009-06-15)
10-17

Figure 10-4 Timeslot allocation diagram
Station Timeslot NE1 6-SL1-1 Serial1 2-SCC: S1 Add/Frop Forward NE2 6-SL1-1 5-IF1A-1 Serial1 2-SCC: S1 NE3 5-IF1A-1
As shown in the timeslot allocation diagram, the asynchronous data services are as follows:
l
The S1 port on the SCC board in slot 2 of NE1 and S1 port on the SCC board in slot 2 of NE3 are used to add and drop the asynchronous data services. The SERIAL1 overhead byte on the SDH optical line between the SL1 board in slot 6 of NE1 and the SL1 board in slot 6 of NE2 is used to transmit the asynchronous data services. The self-defined SERIAL byte on the radio link between the IF1A board in slot 5 of NE2 and the IF1A board in slot 5 of NE3 to transmit the asynchronous data services. The asynchronous data services are passed through between port 1 of the SL1 board in slot 6 and port 1 of the IF1A board in slot 5 of NE2.

You can configure the asynchronous data services of each NE based on the parameters of the service planning, by using the NMS.
Prerequisite
l l
All the required boards must be added. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 Configure the asynchronous data services. 1. 2. In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply. Parameter Overhead Byte Value Range SERIAL1 Description
l
In this example, Overhead Byte is set to SERIAL1. In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services.
Issue 02 (2009-06-15)
10-18
Parameter Broadcast Data Source
Value Range 6-SL1-1
Description
l
In this example, Broadcast Data Source is set to 6-SL1-1. When this parameter is set to the SDH optical/ electrical line port, Overhead Byte of this port is used. In this example, Broadcast Data Sink is set to S1. When this parameter is set so that it is the same as Overhead Byte, the asynchronous data port on the SCC board is used.
Selected Broadcast Data Sink
S1
Step 2 Configure the asynchronous data services. 1. 2. In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply. Parameter Overhead Byte Value Range SERIAL1 Description
l
In this example, Overhead Byte is set to SERIAL1. In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services. In this example, Broadcast Data Source is set to 6-SL1-1. When this parameter is set to the SDH optical/ electrical line port, Overhead Byte of this port is used. In this example, Selected Broadcast Data Sink is set to 5-IF1A-1. When this parameter is set to IF port, the selfdefined SERIAL byte in the radio frame of this port is used.
6-SL1-1
5-IF1A-1
Step 3 Configure the asynchronous data services. 1. 2. In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply.
Issue 02 (2009-06-15)
10-19
Parameter Overhead Byte
Value Range SERIAL1
Description
l
In this example, Overhead Byte is set to SERIAL1. In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services. In this example, Broadcast Data Source is set to 5-IF1A-1. When this parameter is set to IF port, the selfdefined SERIAL byte in the radio frame of this port is used. In this example, Selected Broadcast Data Sink is set to S1. When this parameter is set so that it is the same as Overhead Byte, the asynchronous data port on the SCC board is used.
5-IF1A-1
S1
----End
10.7 Configuration Example (External Alarms)

This topic uses an example to describe how to plan the parameters of the external alarms and complete the data configuration according to the external alarm requirements. 10.7.1 Networking Diagram The networking diagram forms the foundation of service planning. This topic describes the external alarm requirements. 10.7.2 Service Planning The engineering design department plans the external alarm setting based on the networking diagram. 10.7.3 Configuration Process You can configure the external alarm services based on the parameters of the service planning, by using the NMS.

The networking diagram forms the foundation of service planning. This topic describes the external alarm requirements. An OptiX RTN 600 NE must meet the following external alarm requirements:
l
Outputs two external alarms, and reports a critical alarm and a major alarm. The alarm modes are the same, that is, the port enters the "off" state when an alarm is generated. Inputs three external alarms. The alarm modes are the same, that is, an alarm is generated when the port enters the "on" state.
10-20

Alarm In1 Alarm In2 Alarm In3 Alarm Out1 Alarm Out2

The engineering design department plans the external alarm setting based on the networking diagram. Table 10-3 Configuration of the external alarms Port No. Alarm output port 1 Alarm Mode An Alarm is Generated if the Relay Turns Off and Low Level is Caused An Alarm is Generated if the Relay Turns Off and Low Level is Caused An Alarm is Generated if the Relay Turns On and High Level is Caused An Alarm is Generated if the Relay Turns On and High Level is Caused An Alarm is Generated if the Relay Turns On and High Level is Caused Alarm Trigger Condition Critical Alarm Auto Trigger
Alarm output port 2
Major Alarm Auto Trigger
Alarm input port 1
Alarm input port 2
Alarm input port 3

You can configure the external alarm services based on the parameters of the service planning, by using the NMS.
Prerequisite
You must be logged in to the NE. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 Configure external alarms. 1. 2. In the NE Explorer, select the EOW board and then choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Configure the input alarm. Select Input Relay from the drop-down list. Click Apply. Paramet er Using Status Alarm Mode 3. Value Range EOW-1 Used EOW-2 EOW-3 In this example, Using Status of the alarm interface is set to Used. The alarm is generated when the relay is on. Description
An Alarm is Generated if the Relay Turns On and High Level is Caused
Configure the output alarm. Select Output Relay from the drop-down list. Click Apply. Parameter Value Range EOW-1 Use or Not Working Mode Alarm Trigger Conditions Alarm Mode Used Automatic EOW-2 In this example, Use or Not of the alarm interface is set to Used. Changing the status of the output relay according to Alarm Trigger Conditions and Alarm Mode. Major Alarm Auto Trigger The status of the output relay is changed automatically according to the preset value. The alarm is generated when the relay is off. Description
Critical Alarm Auto Trigger
An Alarm is Generated if the Relay Turns Off and Low Level is Caused
----End
10-22
Issue 02 (2009-06-15)
11 Configuring the Parameters of Various Ports
11
Configuring the Parameters of Various Ports
About This Chapter

This topic describes how to set the parameters of various ports. Normally, the default values of the parameters are adopted to meet the relevant requirements. In certain cases, however, the parameters of the ports need to be modified. 11.1 Configuring the Parameters of SDH Interfaces This section describes how to set the parameters of SDH interfaces, including loopback of the SDH interface board and the enabling/disabling of the lasers at the SDH optical ports. 11.2 Configuring the Parameters of PDH Interfaces By performing the operations, you can set the loopback status and service loading indication of the tributary boards. In the case of the E1 interface board, you can also set the tributary retiming function. In the case of the E3/T3 interface board, you can also set the service type and signal equalization. 11.3 Setting the Parameters of IF Ports This topic describes how to configure the parameters of IF ports, including the IF attributes and ATPC attributes of the IF boards. 11.4 Setting the Parameters of ODU Ports This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.
Issue 02 (2009-06-15)
11-1
11.1 Configuring the Parameters of SDH Interfaces

This section describes how to set the parameters of SDH interfaces, including loopback of the SDH interface board and the enabling/disabling of the lasers at the SDH optical ports.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required SDH interface boards must be added.
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explore. Choose Configuration > SDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel) (default option of the system). Step 3 Select Port from the dropdown list and set the parameters of the SDH interface board.
Step 4 Click Apply. A dialog box is displayed and click OK. Step 5 Select VC4 Channel from the dropdown list. Step 6 Configure VC-4 path loopback.
11-2
Issue 02 (2009-06-15)
Parameters
Parameter Laser Switcha Value Open, Close Default Value Open Description
l
This parameter indicates whether the laser is enabled to receive/transmit optical signals. Normally, this parameter takes the default value. Optical (electrical) inloop indicates that loopback occurs in the SDH optical (electrical) signals to be transmitted to the opposite end. Optical (electrical) outloop indicates that loopback occurs in the SDH optical (electrical) signals to be received. Normally, this parameter takes the default value. VC-4 path inloop indicates that loopback occurs in the VC-4 signals to be transmitted to the opposite end. VC-4 path outloop indicates that loopback occurs in the VC-4 signals to be received. Normally, this parameter takes the default value.
Optical (Electrical) Interface Loopback
Non-Loopback, Inloop, Outloop
Non-Loopback
VC4 Loopback
Non-Loopback
NOTE
a: Only SDH optical interface boards support this parameter.
11.2 Configuring the Parameters of PDH Interfaces

By performing the operations, you can set the loopback status and service loading indication of the tributary boards. In the case of the E1 interface board, you can also set the tributary retiming function. In the case of the E3/T3 interface board, you can also set the service type and signal equalization.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required PDH interface boards must be added.
Issue 02 (2009-06-15)
11-3
Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel) (default value). Step 3 Select Port from the drop-down list, Set the parameters of the PDH interfaces according to the types of the PDH interfaces.
l
Set the parameters of the PDH interfaces on the E1 interface board.
Set the parameters of the PDH interface on the E3/T3 interface board.
Parameters
Parameter Tributary Loopback Value Range Non-Loopback, Inloop, Outloop Default Value Non-Loopback Description
l
Tributary inloop indicates that loopback occurs in the tributary signals to be transmitted to the remote end. Tributary outloop indicates that loopback occurs in the tributary signals to be received. Generally, this parameter takes the default value.
11-4
Issue 02 (2009-06-15)
Parameter Service Load Indication
Value Range Load, Non-Loaded
Default Value Load
Description
l
This parameter is valid for the tributary ports that are configured with services. When this parameter is set to Load, the board detects whether alarms exist in this path. When this parameter is set to NonLoaded, the board does not detect whether alarms exist in this path. Generally, this parameter takes the default value. 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. When this parameter is set to Normal, the retiming function is not used. 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. 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. It is recommended that the external clock, instead of the retiming function, is used to provide an external clock for the client equipment. If the retiming function is required, it is recommended that you adopt Retiming Mode of Cross-Connect Clock. This parameter indicates the type of the services the tributary board processes. Set this parameter according to the type of the accessed services.
Retiming Modea
Normal, Retiming Mode of Tributary Clock, Retiming Mode of CrossConnect Clock
Normal
Port Service Typeb
E3, T3
E3
Issue 02 (2009-06-15)
11-5
Parameter Input Signal Equalizationb
Value Range Unequalized, Equalized
Default Value Unequalized
Description
l
This parameter is valid only when Service Type is set to T3. This parameter indicates whether the input signals are equalized. If the trunk cable exceeds 70 m, it is recommended that you set this parameter to Equalized. Otherwise, adopt the default value. This parameter is valid only when Service Type is set to T3. This parameter indicates whether the output signals are equalized. If the trunk cable exceeds 70 m, it is recommended that you set this parameter to Equalized. Otherwise, adopt the default value.
Output Signal Equalizationb
Unequalized, Equalized
Unequalized
NOTE
l l
a: Only E1 interface boards support this parameter. b: Only E3/T3 interface boards support the parameters.
11.3 Setting the Parameters of IF Ports

This topic describes how to configure the parameters of IF ports, including the IF attributes and ATPC attributes of the IF boards.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required IF boards must be added.
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Set each parameter for the IF attributes.
11-6
Issue 02 (2009-06-15)
NOTE
The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode.
Step 4 Click Apply. Step 5 Click the ATPC Attributes tab. Step 6 Set each parameter for the ATPC attributes.
Issue 02 (2009-06-15)
11-7
Parameters
Parameter 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 16,5E1,7MHz,QPS K 17,10E1,14MHz,Q PSK 18,2E1,3.5MHz,QP SK
l
Default Value 1,4E1,7MHz,QPSK (IF1A/B) 5,16E1,28MHz,QP SK (IF0A/B) 7,STM-1,28MHz, 128QAM (IFX)
Description
l
This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format. The IF1A/B board supports radio work modes 1 to 15. The IF0A/B board supports radio work modes 5, 16, 17, and 18. The IFX board supports radio work mode 7 only. The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode. Set this parameter according to the network planning. The radio work modes of the IF boards at both the radio link must be the same.
11-8
Issue 02 (2009-06-15)
Parameter Radio Link ID
Default Value 1
Description
l
As the identifier of a radio link, this parameter is used to avoid misconnection of radio links between sites. If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same. IF port inloop indicates that loopback occurs in the IF signals to be transmitted to the remote end. IF port outloop indicates that loopback occurs in the IF signals to be received. Generally, this parameter takes the default value. In the case of the IFX board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz, 128QAM. In the case of the IF1A/B board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz, 128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM. This parameter indicates whether the radio link transmits the wayside E1 service. The wayside E1 service is a 2.048 kbit/s service that is transmitted by the microwave frame overhead. The IDU 610/620 accesses the wayside E1 service through the external clock interface on the PXC board. This parameter is valid only when 2M Wayside Enable Status is set to Enabled. This parameter indicates the slot in which the PXC board accesses the wayside E1 service through the external clock port.
IF Port Loopbacka
Non-Loopback
2M Wayside Enable Statusb
Enabled, Disabled
Disabled
2M Wayside Input Boardb
1, 3
Issue 02 (2009-06-15)
11-9
Parameter XPIC Enablec
Description
l
This parameter indicates whether the XPIC function is enabled. If the IF board does not use the XPIC function, set this parameter to Disabled. In this case, use the XPIC cable to perform self-loop at the XPIC port. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the TX power of the transmitter automatically traces the changes of the RX level at the receive end, within the ATPC controlled range. It is recommended that you set this parameter to Disabled in areas where fast fading severely affects the radio transmission. To ensure that the TX power does not change during the commissioning process, set this parameter to Disabled. After the commissioning is complete, you can set this parameter to another value. Set the central value of the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB. This parameter sets whether to enable the ATPC. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATP upper and lower thresholds based on the working mode of the IF board. When the function is disabled, the manually set ATPC upper and lower thresholds are used.
ATPC Enable Statusd
Enabled, Disabled
Disabled
ATPC Upper Threshold (dBm)d ATPC Lower Threshold (dBm)d
-20 dBm to -75 dBm -35 dBm to -90 dBm
-45 dBm -70dBm
Enabled, Disabled
Enabled
11-10
Issue 02 (2009-06-15)
NOTE
l l l l
a: The IFH2 and IFX boards do not support the loopback on the IF ports. b: The IFH2 and IF0A/B boards do not support wayside E1 services. c: The IFH2, IF0A/B, and IF1A/B boards do not support the XPIC function. d: The ATPC attributes need to be set to the same values at both ends of a radio link.
11.4 Setting the Parameters of ODU Ports

This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required IF boards must be added. The corresponding ODU must be added in the slot layout diagram.
Context 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 the TX frequency and T/R spacing.
Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Configure the transmit power and receive power of the ODU.
Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status.

Parameters
Parameter Transmit Frequency (MHz) Value Range Default Value Description
l
The parameter specifies the channel center frequency. This parameter cannot be set to a value that is less than the minimum Transmit frequency supported by the ODU + 50% channel spacing or more than the maximum Transmit frequency supported by the ODU - 50% channel spacing. The difference between the Transmit frequencies of both the ends of a radio link is a T/R spacing. Set this parameter according to the planning. This parameter cannot be set to a value that exceeds the rated power range supported by the ODU. Set this parameter to limit the maximum transmit power of the ODU within this preset value. The maximum transmit power adjusted by ATPC should not exceed this value. Set this parameter according to the planning. This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. The Transmit power of the ODU should be set to the same value at both the ends of a radio link. Set this parameter according to the planning.
Maximum Transmit Power (dBm)
Transmit Power (dBm)
11-12
Issue 02 (2009-06-15)
Parameter Receive Power (dBm)
Value Range -
Default Value -
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. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. 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. Set this parameter according to the planning. This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. 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. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link. When this parameter is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. When this parameter is set to unmute, the ODU can normally receive and transmit microwave signals. Generally, this parameter takes the default value.
T/R Spacing (MHz)
04294967.295
Configure Transmission Status
mute, unmute
unmute
Issue 02 (2009-06-15)
11-13
12 Configuring Overhead Bytes
12
About This Chapter
Configuring Overhead Bytes
This topic describes how to configure overhead bytes. Normally, the default values of the overhead bytes to be received or transmitted are adopted to meet the relevant requirements. In certain cases, however, the overhead bytes to be received or transmitted need to be modified. 12.1 Configuring the IEEE 1588 Overhead You need to specify the IEEE 1588 overhead when the Packet microwave is interconnected with the Hybrid microwave. 12.2 Configuring RSOHs This topic describes how to configure the J0 byte in the regenerator section overheads when the J0_MM alarm is reported at the local or remote NE. 12.3 Configuring VC-4 POHs This section describes how to configure the J1 byte or C2 byte in the VC-4 path overheads (POHs) when the HP_TIM or HP_SLM alarm is reported on the line board at the local or remote NE. 12.4 Configuring VC-3 POHs You need to configure the J1 or C2 byte in the VC-3 path overheads, when the E3/T3 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC3 or LP_SLM_VC3 alarm. 12.5 Configuring VC-12 POHs You need to configure the signal indicator of the J2 or V5 byte in the VC-12 path overheads, when the E1 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC12 or LP_SLM_VC12 alarm.
Issue 02 (2009-06-15)
12-1
12.1 Configuring the IEEE 1588 Overhead

You need to specify the IEEE 1588 overhead when the Packet microwave is interconnected with the Hybrid microwave.
Prerequisite
Procedure
Step 1 In the NE Explorer, select the IFH2 board, and choose Configuration > Overhead Management > 1588 Overhead from the Function Tree. Step 2 Set the enable status of 1588 Overhead. Step 3 Click Apply. ----End
Parameter Description
Parameter 1588 Overhead Value Range Enabled, Disabled Default Value Disabled Description
l
When the Hybrid microwave is interconnected with the Packet microwave, this parameter is set to Enabled. When the Hybrid microwave is interconnected with the Hybrid microwave, this parameter is set to Disabled.
12.2 Configuring RSOHs

This topic describes how to configure the J0 byte in the regenerator section overheads when the J0_MM alarm is reported at the local or remote NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required SDH interface boards must be added.
12-2
Issue 02 (2009-06-15)
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree. Step 2 Set the J0 byte. 1. 2. Double-click the parameter to be modified. Then, the Please Input Overhead Byte dialog box is displayed. Set the overhead byte.
3.
Click OK.
Step 3 Click Apply. Then, a prompt box is displayed. Confirm the operations in this prompt box. Step 4 Click OK. ----End
Parameters
Parameter J0 to Be Sent ([Mode]Content) Value Range Default Value [16 Byte]HuaWei SBS Description
l
Two byte modes are supported: single byte mode and 16-byte mode (the first byte is generated automatically). If the remote NE reports the J0_MM alarm, set this parameter according tot he J0 byte to be received at the remote NE.
Issue 02 (2009-06-15)
12-3
Parameter J0 to Be Received ([Mode]Content)
Value Range -
Default Value Disable
Description
l
Three byte modes are supported: single byte mode, 16-byte mode (the first byte is generated automatically), and disable mode. When this parameter is set to Disable Mode, the board does not detect the received J0 byte. It is recommended that this parameter takes the default value.
12.3 Configuring VC-4 POHs

This section describes how to configure the J1 byte or C2 byte in the VC-4 path overheads (POHs) when the HP_TIM or HP_SLM alarm is reported on the line board at the local or remote NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The required line boards must be added.
Procedure
Step 1 Select the line board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Step 2 Optional: Set the J1 byte. 1. 2. 3. Click the Trace Byte J1 tab. Double-click the parameter to be modified. Then, the Please Input Overhead Byte dialog box is displayed. Set the overhead byte.
12-4
Issue 02 (2009-06-15)
4. 5. 6.
Click OK. Click Apply. Then, a prompt box is displayed. Confirm the operations in this prompt box. Click OK.
Step 3 Optional: Set the C2 byte. 1. 2. Click the Signal Flag C2 tab. Set the C2 byte.
Then, a prompt box is displayed. Confirm the operations in this prompt box. 3. 4. Click OK. Click Apply.
Step 4 Optional: Set the termination mode of the VC-4 POHs. 1. 2. Click the Overhead Termination tab. Set the termination mode of the VC-4 POHs.
3. 4.
Click Apply. Then, a prompt box is displayed. Confirm the operations in this prompt box. Click OK.
----End
Issue 02 (2009-06-15)
12-5
Parameters
l
Three byte modes are supported: single byte mode, 16-byte mode (the first byte is generated automatically), and 64-byte mode (synchronization bit 0x0D, 0x0A). If the remote NE reports the HP_TIM alarm, set this parameter according to the J1 byte to be received at the remote NE. Three byte modes are supported: 16-byte mode (the first byte is generated automatically), 64-byte mode (synchronization bit 0x0D, 0x0A), and disable mode. When this parameter is set to Disable Mode, the board does not detect the received J1 byte. It is recommended that this parameter takes the default value.
J1 to Be Received ([Mode]Content)
Disable
C2 to Be Sent
(0x00)Unequipped, (0x01)Reserved, (0x02) TUG Structure, (0x03) Locked TU-n, (0x04)34M/45M into C-3, (0x05) Experimental Mapping, (0x12) 140M into C-4 asynchronization, (0x13)ATM Mapping, (0x14) MAN DQDB Mapping, (0x15) FDDI Mapping, (0x16)HDLC/PPP Mapping, (0x17) Reserved for Special Purpose, (0x18) HDLC/LAPS Mapping, (0x19) Reserved for Special Purpose, (0x1A) 10G Ethernet Frame, (0x1B)GFP Mapping, (0xCF) Reserved, (0xE1) Reserved, (0xFC) Reserved, (0xFE)O.
(0x02) TUG Structure
If the remote NE reports the HP_SLM alarm, set this parameter according to the C2 byte to be received at the remote NE.
12-6
Issue 02 (2009-06-15)
Parameter C2 to Be Received
Value Range 181 Test Signal, (0xFF)VC-AIS
Default Value
Description If the local NE reports the HP_SLM alarm, set this parameter according to the C2 byte to be transmitted from the remote NE.
VC4 Overhead Termination
Auto, PassThrough, Termination
Auto
When this parameter is set to PassThrough, the local NE detects the VC-4 overheads (the C2 byte is not detected) and then forwards the original overheads. When this parameter is set to Termination, the local NE detects the VC-4 overheads (the C2 byte is not detected) and then generates new VC-4 overheads according to the board settings. When this parameter is set to Auto, the VC-4 overhead termination of VC-4 pass-through services is Pass-Through and the overhead termination of the VC-3/VC-12 services is Termination. It is recommended that this parameter takes the default value.
Issue 02 (2009-06-15)
12-7

You need to configure the J1 or C2 byte in the VC-3 path overheads, when the E3/T3 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC3 or LP_SLM_VC3 alarm.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The corresponding E3/T3 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E3/T3 interface board or Ethernet board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC3 Path Overhead from the Function Tree. Step 2 Optional: Set the J1 byte. 1. 2. 3. Click the Trace Byte J1 tab. Double-click the parameter to be modified. Then, the Please Input Overhead Byte dialog box is displayed. Set the overhead byte.
4. 5. 6.
Step 3 Optional: Set the C2 byte. 1. 2.

12-8
Click the Signal Flag C2 tab. Set the C2 byte.

Then, a prompt box is displayed. Confirm the operations in this prompt box. 3. 4. Click OK. Click Apply.
----End
Parameters
l
Three byte modes are supported: single byte mode, 16-byte mode (the first byte is generated automatically), and 64-byte mode (synchronization bit 0x0D, 0x0A). If the remote NE reports the LP_TIM or LP_TIM_VC3 alarm, set this parameter according to the J1 byte to be received at the remote NE. Three byte modes are supported: 16-byte mode (the first byte is generated automatically), 64-byte mode (synchronization bit 0x0D, 0x0A), and disable mode. When this parameter is set to Disable Mode, the board does not detect the received J1 byte. It is recommended that this parameter takes the default value.
J1 to Be Received ([Mode]Content)
Disable
C2 to Be Sent
(0x00)Unequipped, (0x01)Reserved, (0x02) TUG Structure, (0x03) Locked TU-n, (0x04)34M/45M into C-3, (0x05) Experimental Mapping, (0x12) 140M into C-4 asynchronization, (0x13)ATM Mapping, (0x14) MAN DQDB Mapping, (0x15) FDDI Mapping,
(0x04)34M/45M into C-3 (E3/T3 interface boards) (0x02) TUG Structure (Ethernet boards)
If the remote NE reports the LP_TIM or LP_TIM_VC3 alarm, set this parameter according to the C2 byte to be received at the remote NE.
Issue 02 (2009-06-15)
12-9
Parameter C2 to Be Received
Value Range (0x16)HDLC/PPP Mapping, (0x17) Reserved for Special Purpose, (0x18) HDLC/LAPS Mapping, (0x19) Reserved for Special Purpose, (0x1A) 10G Ethernet Frame, (0x1B)GFP Mapping, (0xCF) Reserved, (0xE1) Reserved, (0xFC) Reserved, (0xFE)O. 181 Test Signal, (0xFF)VC-AIS
Default Value
Description If the local NE reports the LP_TIM or LP_TIM_VC3 alarm, set this parameter according to the C2 byte to be transmitted from the remote NE.

You need to configure the signal indicator of the J2 or V5 byte in the VC-12 path overheads, when the E1 interface board on the local or opposite NE reports the LP_TIM or LP_SLM alarm or when the Ethernet board on the local or opposite NE reports the LP_TIM_VC12 or LP_SLM_VC12 alarm.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The corresponding E1 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E1 interface board or Ethernet board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC12 Path Overhead from the Function Tree. Step 2 Optional: Set the J2 byte.
1. 2. 3.
Click the Trace Byte J2 tab. Double-click the parameter to be modified. Then, the Please Input Overhead Byte dialog box is displayed. Set the overhead byte.
4. 5. 6.
Step 3 Optional: Set the signal flag. 1. 2. Click the Signal Flag tab. Set the signal flag in the V5 byte.
3. 4.
Click Apply. Then, a prompt box is displayed. Confirm the operations in this prompt box. Click OK.
----End
Parameters
l
Two byte modes are supported: single byte mode and 16-byte mode (the first byte is generated automatically). If the remote NE reports the LP_TIM or LP_TIM_VC3 alarm, set this parameter according to the J1 byte to be received at the remote NE.
Issue 02 (2009-06-15)
12-11
Parameter J2 to Be Received ([Mode]Content)
Value Range -
Default Value Disable
Description
l
Three byte modes are supported: 16-byte mode (the first byte is generated automatically), 64-byte mode (synchronization bit 0x0D, 0x0A), and disable mode. When this parameter is set to Disable Mode, the board does not detect the received J2 byte. It is recommended that this parameter takes the default value.
V5 to Be Transmitted
V5 to Be Received
(0x00)Unequipped or SupervisoryUnequipped, (0x01) Equipped-NonSpecific Payload, (0x02) Asynchronous, (0x03)Bit Synchronization, (0x04)Byte Synchronization, (0x05)Retained Signal Flag, (0x06) O.181 Test Signal, (0x07)VC_AIS
(0x02) Asynchronous
If the remote NE reports the LP_SLM or LP_SLM_VC3 alarm, set this parameter according to the V5 byte to be received at the remote NE. If the local NE reports the LP_SLM or LP_SLM_VC3 alarm, set this parameter according to the V5 byte to be transmitted from the remote NE.
12-12
Issue 02 (2009-06-15)
13 Adding and Modifying the Configuration Data
13
About This Chapter
Adding and Modifying the Configuration Data
During the equipment commissioning and operating phases, you need to add certain configuration and modify certain configuration data according to the actual requirements. 13.1 Task Collection (Configuring SDH/PDH Services) The task collection for configuring SDH/PDH services includes all the common tasks for configuring the NE attributes, radio link, services, clock, and orderwire. 13.2 Task Collection (Configuring Ethernet Services) This task collection includes all the common tasks that are performed for configuring Ethernet services.
Issue 02 (2009-06-15)
13-1
13.1 Task Collection (Configuring SDH/PDH Services)

The task collection for configuring SDH/PDH services includes all the common tasks for configuring the NE attributes, radio link, services, clock, and orderwire.
NE Attributes
Table 13-1 Task collection (NE attributes) Task Creating NEs Application Scenario To implement the centralized management of NEs by using the NMS, all the icons of the NEs that need to be managed must be created on the Main Topology. Configuration Operation Creating an NE (searching for the NE) or Creating an NE manually Remarks
l
Generally, NEs are created by searching for the NE on the NMS. The manual NE creation method is applicable only when several NEs need to be created on a large microwave network.
Modifying the NE ID
You need to modify 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 modify the IP address of the gateway NE if changes occur in the external DCN between the NMS server and the gateway NE.
Modifying the NE ID
Modifying the IP address of an NE
Modifying the IP address of an NE
Radio Link
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.
13-2
Issue 02 (2009-06-15)
Table 13-2 Task collection (radio link) Task Changing the radio work mode of the SDH/PDH radio link Application Scenario You need to modify the radio work mode of an SDH/PDH radio link, if the SDH/PDH radio link does not meet the service capacity requirements. Configuration Operation 1. Deleting the crossconnections of services Remarks
l
Before you change the radio work mode, you need to delete all the services on the IF ports. If the IF ports are configured with relevant protection, you need to delete the protection first.
2. Configuring the IF/ODU information of a radio link
Before you change a radio work mode, it is recommended that you consult the network planning department to check whether the radio link supports the new radio work mode. -
Configuring the ATPC function
The ATPC function needs to be enabled for the radio link or the values of ATPC parameters need to be changed. You can change the transmit power if the fading margin is insufficient but the transmit power can still be increased. To improve the reliability of a 1+0 radio link, you can upgrade the 1+0 radio link to a 1+1 HSB/SD/FD radio link.
Configuring the ATPC function
Changing the transmit power
Configuring the IF/ODU information of a radio link
Upgrading a 1+0 radio link to a 1+1 HSB/SD/FD radio link
1.Configuring IF 1+1 protection
In the case of IF 1+1 protection, the existing IF board functions as the main IF board. Configuring IF 1+1 protection does not interrupt services.
l
2.Configuring the IF/ODU information of a radio link
Ensure that Actual TX Status of the standby ODU is unmute. In the case of a 1+1 FD radio link, you need to set Transmission Frequency, T/R Spacing, and Transmit Power for the standby ODU.
Issue 02 (2009-06-15)
13-3
Task Setting the Hybrid/ AM attribute
Application Scenario If the Hybrid/AM attribute of the existing Hybrid radio link does not meet the service requirements, for example, if the modulation mode of the assured AM capacity needs to be changed to increase the assured capacity, you need to modify the Hybrid/AM attribute.
Configuration Operation Setting the Hybrid/AM attribute
Remarks
l
Before you modify the Hybrid/AM attribute, it is recommended that you consult the network planning department to check whether the radio link supports the new modulation mode of the assured AM capacity and modulation mode of the full AM capacity. Changing the Modulation Mode of the Assured AM Capacity or Modulation Mode of the Full AM Capacity does not interrupt services. To change E1 Capacity of the Hybrid Network, however, you need to delete all the E1 services on the IF ports.
13-4
Issue 02 (2009-06-15)
Services
Table 13-3 Task collection (services) Task Adding SDH/PDH services Application Scenario More SDH/PDH services need to be accessed on the network. Configuration Operation Creating the crossconnections of point-to-point services or creating the crossconnections of SNCP services Remarks
l
If the services that need to be added on the IF boards require the support of a license, you need to apply for the corresponding license. If the services that are added on the SDH/PDH IF boards exceed the maximum capacity supported by the radio work mode, you need to change the radio work mode. If the services that are added on the SDH/PDH IF boards exceed the maximum access capacity supported by the Hybrid microwave, you need to change the Hybrid/AM attribute.
Deleting SDH/ PDH services
If the line resources are insufficient, you need to delete the SDH/PDH services that are not used to release the corresponding resources. You can upgrade an unprotected chain to a linear MSP chain to improve the service reliability.
Deleting the crossconnections of services
Upgrading an unprotected chain to a linear MSP chain
Configuring linear MSP
In the case of linear MSP, the existing line port functions as the working port. Configuring linear MSP does not interrupt the existing services. In the case of ring MSP. the existing line port functions as the working port. Configuring ring MSP does not interrupt the existing services.
Upgrading an unprotected ring to a two-fiber MSP ring
You can upgrade an unprotected ring to a twofiber MSP ring to improve the service reliability.
Configuring ring MSP
Issue 02 (2009-06-15)
13-5
Task Upgrading normal services to SNCP services
Application Scenario You can upgrade normal services to SNCP services to improve the service reliability.
Configuration Operation Converting normal services to SNCP services
Remarks Only the normal services in the receive direction are converted to SNCP services. Hence, you need to configure the unidirectional crossconnections 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 transmission direction are converted to SNCP services.
Clock
Table 13-4 Task collection (clock) Task Configuring the clock source Application Scenario When the centralized management of the OptiX RTN NEs is implemented by using the NMS, configure the clock source for each NE according to the clock synchronization scheme. If the transport network is a ring network or a network with a more complex topology, configure the SSM or extended SSM protocol according to the requirements. Configuration Operation Configuring the clock source Remarks The clock sources must comply with the networkwide clock synchronization scheme. Hence, all the NEs on the transport network trace the same clock. Generally, the requirements can be met after the SSM protocol is configured.
Configuring protection for the clock source
Configuring protection for the clock source
13-6
Issue 02 (2009-06-15)
Orderwire
Table 13-5 Task collection (orderwire) Task Configuring the orderwire Application Scenario After the centralized management of the OptiX RTN NEs is implemented by using the NMS, configure the orderwire for the NEs. Configuration Operation Configuring the orderwire Remarks
l
The orderwire phone numbers of all the NEs on the network must of the same length. It is recommended that the orderwire phone numbers are three-digit numbers. Each orderwire phone number must be unique and cannot be set to "888". It is recommended that you allocate the three-digit numbers (that start from "101") as the orderwire phone numbers for the NEs one after another, according to the order of NE IDs.
13.2 Task Collection (Configuring Ethernet Services)

This task collection includes all the common tasks that are performed for configuring Ethernet services.
Ethernet Services Transmitted on the SDH Microwave

Table 13-6 Task collection (Ethernet services transmitted on the SDH microwave) Task Creating Ethernet services Application Scenario Create the Ethernet services according to the service planning. Configuration Operation Configuring SDH/PDH microwavebased Ethernet services on a per-NE basis Remarks -
Issue 02 (2009-06-15)
13-7
Task Increasing the line bandwidth of the Ethernet services
Application Scenario You need to increase the line bandwidth for Ethernet services, if the Ethernet traffic volume is increased.
Configuration Operation 1.Creating the cross-connections of Ethernet services
Remarks Create the crossconnections from the idle timeslots of the Ethernet board to the line timeslots. Only the idle timeslots that can be added to the VCTRUNKs occupied by the Ethernet services can be crossconnected to the line timeslots. Add the selected idle timeslots of the Ethernet board to the VCTRUNK. If the LCAS function is enabled for the VCTRUNK, adding the idle timeslots does not interrupt the Ethernet services. -
2.Increasing or decreasing the VCTRUNK bandwidth dynamically
Deleting Ethernet services
You can delete the Ethernet services that are not used to release the corresponding resources.
1.Deleting Ethernet private line services or deleting Ethernet LAN services 2.Increasing or decreasing the VCTRUNK bandwidth dynamically
If the VCTRUNK bandwidth cannot be used or less VCTRUNK bandwidth can be used after the services are deleted, delete partial or all timeslots contained in the VCTRUNK. Delete the crossconnections of the timeslots in the VCTRUNK that are released in Step 2, to release the corresponding line resources.
3.Deleting the cross-connections of Ethernet services
13-8
Issue 02 (2009-06-15)
Task
Application Scenario
Configuration Operation 4.Configuring the external ports of Ethernet boards
Remarks If the Ethernet port cannot be used after the services are deleted, set Enabled/Disabled to Disabled for the Ethernet port, thus preventing the alarms related to the port from being reported. Delete partial timeslots contained in the VCTRUNK. Delete the crossconnections of the timeslots in the VCTRUNK that are released in Step 2, to release the corresponding line resources.
Decreasing the line bandwidth of the Ethernet services
If the Ethernet traffic volume is decreased, you can decrease the line bandwidth occupied by the Ethernet services to release the corresponding line resources.
1.Decreasing or decreasing the VCTRUNK bandwidth dynamically 2.Deleting the cross-connections of Ethernet services
Ethernet Services Transmitted on the Hybrid Microwave

Table 13-7 Task collection (Ethernet services transmitted on the Hybrid microwave) Task Creating Ethernet services Delete the Ethernet services that are accessed through the EMS6 board. Application Scenario Create the Ethernet services according to the service planning. You can delete the Ethernet services that are not used to release the corresponding resources. Configuration Operation 1. Configuring SDH/PDH microwave-based Ethernet services on a per-NE basis 1.Deleting Ethernet private line services or deleting Ethernet LAN services 2.Changing the values of CAR parameters or changing the values of CoS parameters Remarks -
Change the values of QoS parameters to ensure that the QoS control adapts to the service adjustments.
Issue 02 (2009-06-15)
13-9
Task Adjusting the QoS
Application Scenario You need to adjust the QoS if the service type, traffic volume, or Ethernet capacity supported by the Hybrid microwave is changed.
Configuration Operation 1.Changing the values of CAR parameters or changing the values of CoS parameters
Remarks Change the values of QoS parameters to ensure that the QoS controls the situation of the change.
13-10
Issue 02 (2009-06-15)
A Glossary
A
Terms are listed in an alphabetical order. A ACAP ATPC AM
Glossary
The Adjacent Channel Alternate Polarization (ACAP) operation provides orthogonal polarizations between two adjacent communication channels. Automatic Transmit Power Control. A method of automatically adjusting the transmit power at the opposite end based on the transmit signal detected at the receiver. Refers to the adaptive modulation (AM) technology that implements automatic adjustment of the coding scheme and modulation scheme.
C CCDP The co-channel dual polarization (CCDP) operation provides two parallel communication channels over the same link with orthogonal polarizations, thus doubling the link capacity.
E ETH-OAM Being in compliance with the MAC-layer protocol, the ETH-OAM function checks the Ethernet link by transmitting the OAM protocol packet.
F FD Frequency Diversity. Two or more microwave frequencies with certain frequency space are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading.
Issue 02 (2009-06-15)
A-1
A Glossary
Hybrid microwave
Refers to the microwave system that can transmit mixed E1 and Ethernet services, never changes the feature of the E1 and Ethernet services in transmission.
I IDU IGMP Indoor Unit. The indoor unit implements accessing, multiplexing/ demultiplexing, and IF processing for services. Internet Group Management Protocol. The Protocol is used by IPv4 systems (hosts and routers) to report their IP multicast group memberships to any neighboring multicast routers. IGMP Snooping is the process of listening to IGMP traffic. IGMP snooping, as implied by the name, is a feature that allows the switch to "listen in" on the IGMP conversation between hosts and routers by processing the layer 3 IGMP packets sent in a multicast network.
IGMP Snooping
L LCAS Link Capacity Adjustment Scheme. A solution features flexible bandwidth and dynamic adjustment. In addition, it provides a failure tolerance mechanism, which enhances the viability of virtual concatenations and enables the dynamic adjustment to bandwidth (non-service affecting).
M MSP Multiplex section protection. The function performed to provide capability for switching a signal between and including two MST functions, from a "working" to a "protection" channel.
N N+1 protection A microwave link protection system that employs N working channels and one protection channel.
O ODU QoS Outdoor Unit. The outdoor unit implements frequency conversion and amplification for RF signals. Indicates the quality of Ethernet services.
P PDH Plesiosynchronous Digital Hierarchy. 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.
A-2
Issue 02 (2009-06-15)
A Glossary
Q QinQ The QinQ, a Layer 2 tunnel protocol developed based on the IEEE 802.1Q encapsulation, allows for individual VLANs with extra tag information to traverse the backbone networks and thus provides Layer 2 VPN tunnels for users.
R RSTP Rapid Spanning Tree Protocol. The protocol is an evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change.
S SD Space Diversity. Two or more antennas separated by a specific distance 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. Synchronous Digital Hierarchy. A hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over physical transmission networks. Subnetwork connection protection. A working subnetwork connection is replaced by a protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. The Spanning Tree Protocol (STP), defined in the IEEE Standard 802.1D, is an OSI layer-2 protocol that ensures a loop free topology for any bridged LAN.
SDH
SNCP
STP
T T2000 A subnet management system (SNMS). In the telecommunication management network architecture, the T2000 is located between the NE level and network level, which can supports all NE level functions and part of the network level management functions.
Issue 02 (2009-06-15)
A-3
B Acronyms and Abbreviations
B
A AM APS ARP ATPC AU
Acronyms and Abbreviations
Acronyms and abbreviations are listed in alphabetical order.
Adaptive Modulation Automatic Protection Switching Address Resolution Protocol Automatic Transmit Power Control Administrative Unit
B BER BIP BPDU Bit Error Rate Bit-Interleaved Parity Bridge Protocol Data Unit
C CAR CBS CCDP CGMP CIR CLNP CLNS CoS CPU Committed Access Rate Committed Burst Size Co-Channel Dual Polarization Cisco Group Management Protocol committed information rate connectionless network protocol Connectionless Network Service Class of Service Central Processing Unit
Issue 02 (2009-06-15)
B-1
CRC CVLAN C-VLAN
cyclic redundancy check Customer VLAN Customer VLAN
D DC DCC DCN DSCP DVMRP Direct Current Data Communications Channel Data Communication Network differentiated services code point Distance Vector Multicast Routing Protocol
E ECC EPL EPLAN ES-IS EVPL Embedded Control Channel Ethernet Private Line Ethernet Private LAN End System to Intermediate System Ethernet Virtual Private Line
F FCS FD FE FIFO FLP FTP Frame Check Sequence Frequency Diversity Fast Ethernet First In First Out Fast Link Pulse file transfer protocol
G GE GFP GTS GUI Gigabit Ethernet Generic Framing Procedure Generic Traffic Shaping Graphical User Interface
B-2
Issue 02 (2009-06-15)
H HDLC HSB HSM High level Data Link Control procedure Hot Standby Hitless Switch Mode
I ICMP IDU IEEE IETF IF IGMP IP IPv6 IS-IS ISO ITU-T IVL Internet Control Message Protocol Indoor Unit Institute of Electrical and Electronics Engineers The Internet Engineering Task Force Intermediate Frequency Internet Group Management Protocol Internet Protocol Internet Protocol version 6 Intermediate System to Intermediate System International Standard Organization International Telecommunication Union - Telecommunication Standardization Sector Independence VLAN learning
L LAN LAPD LAPS LCAS LCT LMSP Local Area Network Link Access Procedure on the D channel Link Access Procedure-SDH Link Capacity Adjustment Scheme Generation-Local Craft Terminal Linear Multiplex Section Protection
M MAC MBS MDI MIB

Issue 02 (2009-06-15)
Medium Access Control Maximum Burst Size Medium Dependent Interface Management Information Base
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-3
MPLS MSP MTU
multiprotocol label switching Multiplex Section Protection Maximum Transmission Unit
N NE NLP NMS NNI NSAP Network Element Normal Link Pulse Network Management System Network-to-Network Interface or Network Node Interface Network Service Access Point
O ODU OSI OSPF Outdoor Unit Open Systems Interconnection Open Shortest Path First
P PDH PIM-DM PIM-SM PPP Plesiochronous Digital Hierarchy Protocol Independent Multicast-Dense Mode Protocol Independent Multicast-Sparse Mode Point-to-Point Protocol
Q QinQ QoS 802.1Q in 802.1Q Quality of Service
R RF RFC RIP RMON RSL radio frequency Request For Comment Routing Information Protocol Remote Monitoring Received Signal Level
B-4
Issue 02 (2009-06-15)
RSTP RTN
Rapid Spanning Tree Protocol Radio Transmission Node
S SD SDH SNC SNCP SNMP SNR STM STM-1 STM-1e STM-1o STM-4 STM-N STP SVL Space Diversity Synchronous Digital Hierarchy SubNetwork Connection Sub-Network Connection Protection Simple Network Management Protocol Signal-to-Noise Ratio Synchronous Transport Module SDH Transport Module -1 STM-1 Electrical Interface STM-1 Optical Interface SDH Transport Module -4 SDH Transport Module -N Spanning Tree Protocol Shared VLAN Learning
T TCI TCP TU Tag Control Information Transfer Control Protocol Tributary Unit
U UDP UNI User Datagram Protocol user-network interface
V VC VC12 VC-12 Virtual Container Virtual Container -12 Virtual Container -12
Issue 02 (2009-06-15)
B-5
VC3 VC-3 VC4 VC-4 VCG VLAN VoIP VPN
Virtual Container -3 Virtual Container -3 Virtual Container -4 Virtual Container -4 Virtual Concatenation Group Virtual LAN Voice over IP Virtual Private Network
W WAN WRR WTR Wide Area Network Weighted Round Robin Wait to Restore Time
X XPD XPIC Cross-Polarization Discrimination Cross-polarization interference cancellation
B-6
Issue 02 (2009-06-15)

IDU 610620 Configuration Guide (T2000) - (V100R003 - 02) - VNM

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

IDU 610620 Configuration Guide (T2000) - (V100R003 - 02) - VNM

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX RTN 600 Radio Transmission System V100R003

IDU 610/620 Configuration Guide (T2000)

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

Huawei Technologies Co., Ltd.

Trademarks and Permissions

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

3 Configuring Radio Links on the Per-NE Basis.....................................................................3-1

4 Configuring the MSP on the Per-NE Basis........................................................................... 4-1

5 Configuring SDH/PDH Services on the Per-NE Basis........................................................5-1

6 Configuring the Clock on the Per-NE Basis..........................................................................6-1

7 Configuring SDH/PDH Microwave-Based Ethernet Services on the Per-NE Basis ...........................................................................................................................................................7-1

8 Configuring Hybrid Microwave-Based Ethernet Services on the Per-NE Basis...........8-1

9 Task Collection (Configuring Ethernet Services)................................................................9-1

9.7 LPT Configuration........................................................................................................................................9-70

10 Configuring the Orderwire and Auxiliary Interfaces.....................................................10-1

11 Configuring the Parameters of Various Ports ..................................................................11-1

12 Configuring Overhead Bytes...............................................................................................12-1

13 Adding and Modifying the Configuration Data..............................................................13-1

A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-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.

About This Document

About This Document

Installation/Commissioning engineers Data configuration engineers

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

About This Document

This topic describes common Ethernet configuration tasks.

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

About This Document

Topic B Acronyms and Abbreviations

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

About This Document

Updates in Issue 02 (2009-06-15)

Updates in Issue 01 (2009-04-25)

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

1 Starting the T2000

Starting the T2000

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

1 Starting the T2000

1.1 Starting or Shutting Down the T2000

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

1 Starting the T2000

1.1.1 Starting the Computer

1.1.2 Starting the T2000 Server

1 Starting the T2000

Periodically change the password and memorize it.

1.1.3 Viewing the T2000 Process Status

1.1.4 Logging In to the T2000 Client

1 Starting the T2000

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

1.1.5 Exiting a T2000 Client

1 Starting the T2000

1.1.6 Shutting Down the T2000 Server

Shut down the T2000 server only.

1.1.7 Shutting Down the Computer

1 Starting the T2000

1.2 Entering the T2000 Common Views

1.2.1 Opening the Main Topology

1 Starting the T2000

1.2.2 Opening the NE Explorer

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

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