Configuration Guide(V100R002C00 02)

OptiX RTN 910 Radio Transmission SystemV100R002C00

Configuration Guide

Issue 02

Date 2009-10-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009-2009. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2009-10-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes how to configure various services on the equipment. This documentdescribes the basic information and configuration process, and uses configuration examples toshow how to set specific parameters.

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

Product Name Version

OptiX RTN 910 V100R002C00

iManager U2000 V100R001C00

Intended AudienceThe intended audience of this document are:

l Installation and commissioning engineer

l Data configuration engineer

l System maintenance engineer

OrganizationThis document is organized as follows.

Chapter Content

1 ConfigurationPreparations

Before configuring the NE data, you need to make therequired preparations.

OptiX RTN 910Configuration Guide About This Document


iii

Chapter Content

2 Configuring the NetworkTopology

You can manage NEs and fibers by using the U2000 onlyafter creating their topologies on the U2000.

3 Configuring Radio Links Before configuring services on a radio link, you need toconfigure the radio link.

4 Configuring TDM Services The key to configuring a TDM service is configuring thecorresponding service cross-connections.

5 Configuring EthernetServices

Ethernet services are classified into E-Line services and E-LAN services.

6 Configuring the Clock To ensure that clocks of all the nodes on the transmissionnetwork are synchronized, configure the clocks for thesenodes according to a unified clock synchronization policy.

7 Configuring AuxiliaryInterfaces and Functions

The OptiX RTN 910 provides multiple auxiliary interfacesand functions. These functions require certain dataconfiguration.

A Task Collection This task collection contains all the network managementsystem (NMS) tasks related to data configuration.

B Parameters Description This topic describes the parameters used in this document.

C Glossary Terms are listed in an alphabetical order.

D Acronyms andAbbreviations

Acronyms and abbreviations are listed in alphabeticalorder.

Conventions

Symbol Conventions

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

Symbol Description

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

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

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

About This DocumentOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

Symbol Description

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

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

General ConventionsConvention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

GUI ConventionsConvention Description

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

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

Keyboard OperationFormat Description

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

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

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

OptiX RTN 910Configuration Guide About This Document


v

Mouse OperationAction Description

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

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

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

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

Updates in Issue 02 (2009-10-30)This document of the V100R002C00 version is the second release.

l The associated technical specifications are updated.

l The user interfaces and operations related to the NMS are updated.

Updates in Issue 01 (2009-06-30)This document of the V100R002C00 version is the first release.

About This DocumentOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

Contents

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

1 Configuration Preparations......................................................................................................1-11.1 Preparing Documents and Tools.....................................................................................................................1-21.2 Checking Configuration Conditions................................................................................................................1-21.3 Specifying the Configuration Procedure ........................................................................................................1-2

2 Configuring the Network Topology.......................................................................................2-12.1 Basic Concepts................................................................................................................................................2-2

2.1.1 DCN.......................................................................................................................................................2-22.1.2 GNE and Non-GNE...............................................................................................................................2-42.1.3 ID and IP Address of an NE...................................................................................................................2-42.1.4 Physical Boards and Logical Boards......................................................................................................2-52.1.5 Fiber/Cable Types..................................................................................................................................2-62.1.6 Subnet.....................................................................................................................................................2-7

2.2 Configuration Procedure.................................................................................................................................2-72.3 Configuration Example (Chain Network).....................................................................................................2-12

2.3.1 Networking Diagram............................................................................................................................2-122.3.2 Board Configuration.............................................................................................................................2-132.3.3 Service Planning...................................................................................................................................2-142.3.4 Configuration Process..........................................................................................................................2-15

2.4 Configuration Example (Ring Network).......................................................................................................2-182.4.1 Networking Diagram............................................................................................................................2-182.4.2 Board Configuration.............................................................................................................................2-192.4.3 Service Planning...................................................................................................................................2-202.4.4 Configuration Process..........................................................................................................................2-21

3 Configuring Radio Links..........................................................................................................3-13.1 Basic Concepts................................................................................................................................................3-2

3.1.1 Types of Radio Links.............................................................................................................................3-23.1.2 RF Configuration Modes........................................................................................................................3-4

3.2 Configuration Procedure.................................................................................................................................3-53.3 Configuration Example (Radio Links on the TDM Microwave Chain Network)........................................3-11

3.3.1 Networking Diagram............................................................................................................................3-123.3.2 Service Planning...................................................................................................................................3-12

OptiX RTN 910Configuration Guide Contents


vii

3.3.3 Configuration Process..........................................................................................................................3-153.4 Configuration Example (Radio Links on the TDM Microwave Ring Network)..........................................3-19

3.4.1 Networking Diagram............................................................................................................................3-193.4.2 Service Planning...................................................................................................................................3-203.4.3 Configuration Process..........................................................................................................................3-22

3.5 Configuration Example (Radio Links on the Hybrid Microwave Chain Network)......................................3-243.5.1 Networking Diagram............................................................................................................................3-253.5.2 Service Planning...................................................................................................................................3-253.5.3 Configuration Process..........................................................................................................................3-28

3.6 Configuration Example (Radio Links on the Hybrid Microwave Ring Network)........................................3-333.6.1 Networking Diagram............................................................................................................................3-333.6.2 Service Planning...................................................................................................................................3-343.6.3 Configuration Process..........................................................................................................................3-36

4 Configuring TDM Services......................................................................................................4-14.1 Basic Concepts................................................................................................................................................4-2

4.1.1 Protection Modes for TDM Services.....................................................................................................4-24.1.2 Timeslots for TDM Services on IF Boards............................................................................................4-54.1.3 Numbering Schemes for SDH Timeslots ..............................................................................................4-6

4.2 Configuration Procedure.................................................................................................................................4-74.3 Configuration Example (TDM Services on a TDM Microwave Chain Network)..........................................4-8

4.3.1 Networking Diagram..............................................................................................................................4-94.3.2 Service Planning.....................................................................................................................................4-94.3.3 Configuration Process..........................................................................................................................4-12

4.4 Configuration Example (TDM Services on a TDM Microwave Ring Network)..........................................4-154.4.1 Networking Diagram............................................................................................................................4-154.4.2 Service Planning...................................................................................................................................4-164.4.3 Configuration Process..........................................................................................................................4-18

4.5 Configuration Example (TDM Services on a Hybrid Microwave Chain Network).....................................4-224.5.1 Networking Diagram............................................................................................................................4-224.5.2 Service Planning...................................................................................................................................4-224.5.3 Configuration Process..........................................................................................................................4-25

4.6 Configuration Example (TDM Services on a Hybrid Microwave Ring Network).......................................4-284.6.1 Networking Diagram............................................................................................................................4-284.6.2 Service Planning...................................................................................................................................4-294.6.3 Configuration Process..........................................................................................................................4-31

5 Configuring Ethernet Services................................................................................................5-15.1 Basic Concepts................................................................................................................................................5-3

5.1.1 IF_ETH Port...........................................................................................................................................5-45.1.2 Auto-Negotiation....................................................................................................................................5-45.1.3 Flow Control Function...........................................................................................................................5-65.1.4 VLAN.....................................................................................................................................................5-75.1.5 QinQ.......................................................................................................................................................5-9

ContentsOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

5.1.6 E-Line Services....................................................................................................................................5-105.1.7 E-LAN Services...................................................................................................................................5-135.1.8 Managment of the MAC Address Table..............................................................................................5-175.1.9 Protection for Ethernet Services...........................................................................................................5-185.1.10 QoS.....................................................................................................................................................5-21

5.2 Configuration Procedure (E-Line Services)..................................................................................................5-275.3 Configuration Procedure (E-LAN Services).................................................................................................5-445.4 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services).................................5-66


5.5 Configuration Example (VLAN-Based E-Line Service)..............................................................................5-755.5.1 Networking Diagram............................................................................................................................5-755.5.2 Service Planning...................................................................................................................................5-755.5.3 Configuration Process..........................................................................................................................5-84

5.6 Configuration Example (QinQ-Based E-Line Service)...............................................................................5-1025.6.1 Networking Diagram..........................................................................................................................5-1025.6.2 Service Planning.................................................................................................................................5-1035.6.3 Configuration Process........................................................................................................................5-113

5.7 Configuration Example (802.1d-Bridge-Based E-LAN Service)...............................................................5-1365.7.1 Networking Diagram..........................................................................................................................5-1365.7.2 Service Planning.................................................................................................................................5-1375.7.3 Configuration Process........................................................................................................................5-144

5.8 Configuration Example (802.1q-Bridge-Based E-LAN Service)...............................................................5-1535.8.1 Networking Diagram..........................................................................................................................5-1535.8.2 Service Planning.................................................................................................................................5-1545.8.3 Configuration Process........................................................................................................................5-161

5.9 Configuration Example (802.1ad-Bridge-Based E-LAN Service)..............................................................5-1745.9.1 Networking Diagram..........................................................................................................................5-1745.9.2 Service Planning.................................................................................................................................5-1755.9.3 Configuration Process........................................................................................................................5-183

5.10 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)......................5-1965.10.1 Networking Diagram........................................................................................................................5-1965.10.2 Service Planning...............................................................................................................................5-1965.10.3 Configuration Process......................................................................................................................5-206

6 Configuring the Clock...............................................................................................................6-16.1 Basic Concepts................................................................................................................................................6-2

6.1.1 Clock Source..........................................................................................................................................6-26.1.2 Clock Protection Schemes......................................................................................................................6-26.1.3 Clock Synchronization Policy................................................................................................................6-6

6.2 Configuration Procedure...............................................................................................................................6-126.3 Configuration Example (Clock for a TDM Microwave Chain Network).....................................................6-14



ix


6.4 Configuration Example (Clock for a TDM Microwave Ring Network).......................................................6-166.4.1 Networking Diagram............................................................................................................................6-166.4.2 Service Planning...................................................................................................................................6-176.4.3 Configuration Process..........................................................................................................................6-18

6.5 Configuration Example (Clock for a Hybrid Microwave Chain Network)...................................................6-186.5.1 Networking Diagram............................................................................................................................6-196.5.2 Service Planning...................................................................................................................................6-196.5.3 Configuration Process..........................................................................................................................6-20

6.6 Configuration Example (Clock for a Hybrid Microwave Ring Network)....................................................6-216.6.1 Networking Diagram............................................................................................................................6-216.6.2 Service Planning...................................................................................................................................6-226.6.3 Configuration Process..........................................................................................................................6-22

7 Configuring Auxiliary Interfaces and Functions.................................................................7-17.1 Auxiliary Interfaces and Functions.................................................................................................................7-27.2 Configuration Example (Orderwire)...............................................................................................................7-5

7.2.1 Networking Diagram..............................................................................................................................7-57.2.2 Service Planning.....................................................................................................................................7-57.2.3 Configuration Process............................................................................................................................7-7

7.3 Configuration Example (Synchronous Data Services)....................................................................................7-87.3.1 Networking Diagram..............................................................................................................................7-87.3.2 Service Planning.....................................................................................................................................7-87.3.3 Configuration Process............................................................................................................................7-9

7.4 Configuration Example (Asynchronous Data Services)...............................................................................7-107.4.1 Networking Diagram............................................................................................................................7-107.4.2 Service Planning...................................................................................................................................7-107.4.3 Configuration Process..........................................................................................................................7-11

7.5 Configuration Example (Wayside E1 Services)............................................................................................7-127.5.1 Networking Diagram............................................................................................................................7-127.5.2 Service Planning...................................................................................................................................7-127.5.3 Configuration Process..........................................................................................................................7-13

7.6 Configuration Example (External Alarms)...................................................................................................7-137.6.1 Networking Diagram............................................................................................................................7-147.6.2 Service Planning...................................................................................................................................7-147.6.3 Configuration Process..........................................................................................................................7-15

A Task Collection.........................................................................................................................A-1A.1 Managing NEs...............................................................................................................................................A-4

A.1.1 Creating NEs by Using the Search Method..........................................................................................A-4A.1.2 Creating NEs by Using the Manual Method........................................................................................A-6A.1.3 Configuring the Logical Board.............................................................................................................A-7


Configuration Guide

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

Issue 02 (2009-10-30)

A.1.4 Changing the NE ID.............................................................................................................................A-8A.1.5 Changing the NE Name........................................................................................................................A-9A.1.6 Synchronizing the NE Time...............................................................................................................A-10A.1.7 Localizing the NE Time.....................................................................................................................A-13A.1.8 Configuring Standard NTP Keys........................................................................................................A-13

A.2 Configuring the NE Data.............................................................................................................................A-14A.2.1 Uploading the NE Data......................................................................................................................A-15

A.3 Configuring the Performance Monitoring Status of NEs............................................................................A-15A.4 Connecting Fibers or Cables.......................................................................................................................A-16

A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method........................A-17A.4.2 Creating a Radio Link by Using the Manual Method........................................................................A-18A.4.3 Creating an SDH Optical Transmission Link by Using the Manual Method.....................................A-19A.4.4 Creating an Extended ECC.................................................................................................................A-20A.4.5 Creating a Back-to-Back Microwave Connection..............................................................................A-21

A.5 Managing Subnets.......................................................................................................................................A-22A.5.1 Creating a Subnet...............................................................................................................................A-22A.5.2 Copying Topology Objects.................................................................................................................A-23A.5.3 Moving Topology Objects..................................................................................................................A-23

A.6 Managing Communications.........................................................................................................................A-24A.6.1 Setting NE Communication Parameters.............................................................................................A-25A.6.2 Configuring DCCs..............................................................................................................................A-25A.6.3 Configuring the Extended ECC..........................................................................................................A-26A.6.4 Configuring DCC Transparent Transmission.....................................................................................A-27A.6.5 Creating Static IP Routes....................................................................................................................A-28A.6.6 Setting Parameters of the OSPF Protocol...........................................................................................A-29A.6.7 Enabling the ARP Proxy....................................................................................................................A-29A.6.8 Configuring the CLNS Role...............................................................................................................A-30A.6.9 Configuring the OSI Tunnel...............................................................................................................A-30A.6.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN......................................................A-32A.6.11 Configuring the Enable Status of the Inband DCN Function on Ports.............................................A-32A.6.12 Querying ECC Routes......................................................................................................................A-33A.6.13 Querying IP Routes..........................................................................................................................A-34A.6.14 Querying OSI Routes.......................................................................................................................A-34

A.7 Managing Radio Links................................................................................................................................A-35A.7.1 Creating an IF 1+1 Protection Group.................................................................................................A-36A.7.2 Creating an XPIC Protection Group...................................................................................................A-37A.7.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link..................................................A-38A.7.4 Configuring the IF/ODU Information of a Radio Link......................................................................A-39A.7.5 Setting the Hybrid/AM Attribute........................................................................................................A-40A.7.6 Creating an N+1 Protection Group.....................................................................................................A-41A.7.7 Setting IF Attributes...........................................................................................................................A-42A.7.8 Configuring the ATPC Function........................................................................................................A-43



xi

A.7.9 Setting the State of an ODU Transmitter...........................................................................................A-44A.7.10 Querying the ATPC Adjustment Records........................................................................................A-44A.7.11 Querying the History Transmit Power and Receive Power..............................................................A-45A.7.12 Querying the AM Status...................................................................................................................A-46A.7.13 Querying the IF 1+1 Protection Status.............................................................................................A-46A.7.14 Querying the IF N+1 Protection Status............................................................................................A-47A.7.15 IF 1+1 Protection Switching.............................................................................................................A-47A.7.16 IF N+1 Protection Switching............................................................................................................A-48A.7.17 Starting/Stopping the N+1 Protection Protocol................................................................................A-48

A.8 Managing the MSP......................................................................................................................................A-49A.8.1 Configuring Linear MSP....................................................................................................................A-49A.8.2 Querying the Status of the Linear MSP..............................................................................................A-51A.8.3 Performing Linear MSP Switching....................................................................................................A-51A.8.4 Starting/Stopping the Linear MSP Protocol.......................................................................................A-52

A.9 Managing TDM Services............................................................................................................................A-53A.9.1 Creating the Cross-Connections of Point-to-Point Services..............................................................A-53A.9.2 Creating Cross-Connections of SNCP Services.................................................................................A-54A.9.3 Configuring the Automatic Switching of SNCP Services..................................................................A-55A.9.4 Deleting Cross-Connections...............................................................................................................A-56A.9.5 Converting a Normal Service into an SNCP Service.........................................................................A-57A.9.6 Converting an SNCP Service to a Normal Service............................................................................A-58A.9.7 Querying TDM Services.....................................................................................................................A-59A.9.8 Switching SNCP Services..................................................................................................................A-60A.9.9 Querying the Protection Status of SNCP Services.............................................................................A-60A.9.10 Testing the E1 Service Through PRBS............................................................................................A-61

A.10 Managing the Clock..................................................................................................................................A-62A.10.1 Configuring the Clock Sources........................................................................................................A-63A.10.2 Configuring Clock Subnets..............................................................................................................A-64A.10.3 Self-Defined Clock Quality..............................................................................................................A-65A.10.4 Configuring the SSM Output Status.................................................................................................A-66A.10.5 Configuring the Clock ID Output Status..........................................................................................A-67A.10.6 Modifying the Parameters of the Clock Output...............................................................................A-68A.10.7 Changing the Conditions for Clock Source Switching.....................................................................A-68A.10.8 Modifying the Recovery Parameter of the Clock Source.................................................................A-69A.10.9 Querying the Clock Synchronization Status.....................................................................................A-69

A.11 Managing the ERPS .................................................................................................................................A-70A.11.1 Creating Ethernet Ring Protection Instances....................................................................................A-70A.11.2 Setting the Parameters of Ethernet Ring Protocol............................................................................A-71A.11.3 Querying the Status of the Ethernet Ring Protocol..........................................................................A-72

A.12 Managing the MSTP..................................................................................................................................A-72A.12.1 Creating the MSTP Port Group........................................................................................................A-73A.12.2 Setting the Bridge Parameters of the MSTP.....................................................................................A-74


Configuration Guide

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

Issue 02 (2009-10-30)

A.12.3 Setting the Parameters of the CIST..................................................................................................A-75A.12.4 Querying the CIST Running Information.........................................................................................A-76A.12.5 Changing the Spanning Tree Protocol Used by the Port Group.......................................................A-77A.12.6 Enabling/Disabling the MSTP Protocol...........................................................................................A-77A.12.7 Modifying the Configuration Data of the MSTP Port Group...........................................................A-78

A.13 Managing the IGMP Snooping..................................................................................................................A-79A.13.1 Configuring the IGMP Snooping Protocol.......................................................................................A-80A.13.2 Querying the Port Information of the Routers..................................................................................A-80A.13.3 Querying the Information About the Multicast Groups...................................................................A-81A.13.4 Creating Static Router Ports.............................................................................................................A-82A.13.5 Creating a Member of a Static Multicast Group...............................................................................A-83A.13.6 Adding a Quickly Deleted Port........................................................................................................A-84A.13.7 Calculating IGMP Packets...............................................................................................................A-84

A.14 Managing the LAG....................................................................................................................................A-85A.14.1 Creating a LAG................................................................................................................................A-85A.14.2 Setting the Port Priority....................................................................................................................A-87A.14.3 Querying the Protocol Information of the LAG...............................................................................A-87

A.15 LPT Configuration.....................................................................................................................................A-88A.16 Managing the QoS.....................................................................................................................................A-89

A.16.1 Creating a DS Domain......................................................................................................................A-90A.16.2 Changing the Ports That Use the DS Domain..................................................................................A-91A.16.3 Creating a Port Policy.......................................................................................................................A-93A.16.4 Creating the Traffic..........................................................................................................................A-93A.16.5 Setting the Port That Uses the Port Policy.......................................................................................A-95A.16.6 Configuring Port Shaping.................................................................................................................A-96A.16.7 Querying the Port Policy..................................................................................................................A-96A.16.8 Querying the DS Domain of a Port..................................................................................................A-97

A.17 Using the IEEE 802.1ag OAM..................................................................................................................A-98A.17.1 Creating an MD................................................................................................................................A-99A.17.2 Creating an MA................................................................................................................................A-99A.17.3 Creating an MEP Point...................................................................................................................A-100A.17.4 Creating Remote MEPs in an MA..................................................................................................A-101A.17.5 Creating an MIP.............................................................................................................................A-102A.17.6 Performing a CC Test.....................................................................................................................A-103A.17.7 Performing an LB Test...................................................................................................................A-104A.17.8 Performing an LT Test...................................................................................................................A-105

A.18 Using the IEEE 802.3ah OAM ...............................................................................................................A-106A.18.1 Enabling the OAM Auto-Discovery Function...............................................................................A-106A.18.2 Enabling the Link Event Notification ............................................................................................A-107A.18.3 Modifying the OAM Error Frame Monitoring Threshold .............................................................A-108A.18.4 Performing Remote Loopback.......................................................................................................A-109A.18.5 Enabling Self-Loop Detection .......................................................................................................A-110



xiii

A.19 Using the RMON.....................................................................................................................................A-111A.19.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.................................A-111A.19.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-112A.19.3 Configuring a History Control Group............................................................................................A-113A.19.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-113

A.20 Setting the Parameters of Ethernet Interfaces..........................................................................................A-114A.20.1 Setting the General Attributes of Ethernet Interfaces.....................................................................A-114A.20.2 Configuring the Traffic Control of Ethernet Interfaces..................................................................A-115A.20.3 Setting the Layer 2 Attributes of Ethernet Interfaces.....................................................................A-116A.20.4 Setting the Advanced Attributes of Ethernet Interfaces.................................................................A-117

A.21 Setting the General Attributes of the IF_ETH Port.................................................................................A-117A.21.1 Setting the General Attributes of the IF_ETH Port........................................................................A-118A.21.2 Setting the Layer 2 Attributes of the IF_ETH Port........................................................................A-118A.21.3 Setting the Advanced Attributes of the IF_ETH Port....................................................................A-119

A.22 Setting the Parameters of ODU Interfaces..............................................................................................A-119A.22.1 Setting the Transmit Frequency Attribute of the ODU..................................................................A-120A.22.2 Querying the ODU Attribute..........................................................................................................A-120A.22.3 Setting the Power Attributes of the ODU.......................................................................................A-121A.22.4 Setting the Advanced Attributes of the ODU.................................................................................A-122

A.23 Setting the Parameters of SDH Interfaces...............................................................................................A-122A.24 Setting the Parameters of PDH Interfaces...............................................................................................A-123A.25 Configuring Overhead Bytes...................................................................................................................A-124

A.25.1 Configuring RSOHs.......................................................................................................................A-124A.25.2 Configuring VC-4 POHs................................................................................................................A-125A.25.3 Configuring VC-12 POHs..............................................................................................................A-126

A.26 Configure the Ethernet Service...............................................................................................................A-127A.26.1 Configuring the QinQ Link............................................................................................................A-128A.26.2 Configuring the E-Line Service......................................................................................................A-128A.26.3 Creating a VLAN Forwarding Table Item.....................................................................................A-130A.26.4 Configuring the E-LAN Service.....................................................................................................A-131A.26.5 Testing the Ethernet Service...........................................................................................................A-135

A.27 Managing the MAC Address Table.........................................................................................................A-137A.27.1 Creating a Static MAC Address Entry...........................................................................................A-137A.27.2 Creating a Blacklist Entry of MAC Addresses...............................................................................A-138A.27.3 Configuring the Aging Parameters of a MAC Address Table........................................................A-139A.27.4 Querying or Deleting a Dynamic MAC Address...........................................................................A-139

A.28 Setting the Mode for Processing an Unknown Frame of the E-LAN Service.........................................A-140A.29 Configuring Auxiliary Interfaces and Functions.....................................................................................A-141

A.29.1 Configuring the Orderwire.............................................................................................................A-141A.29.2 Configuring the Synchronous Data Service...................................................................................A-142A.29.3 Configuring the Asynchronous Data Service.................................................................................A-143A.29.4 Configuring the Wayside E1 Service.............................................................................................A-143


Configuration Guide

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

Issue 02 (2009-10-30)

A.29.5 Configure External Alarms.............................................................................................................A-144

B Parameters Description............................................................................................................B-1B.1 Parameters for NE Management....................................................................................................................B-3

B.1.1 Parameter Description: NE Searching..................................................................................................B-3B.1.2 Parameter Description: NE Creation....................................................................................................B-7B.1.3 Parameter Description: NE Attribute_NE ID Change........................................................................B-10B.1.4 Parameter Description: NE Time Synchronization.............................................................................B-11B.1.5 Parameter Description: Localization Management of the NE Time...................................................B-13B.1.6 Parameter Description: Automatic Disabling of the Functions of NEs..............................................B-15

B.2 Parameters for Cable Management..............................................................................................................B-15B.2.1 Parameter Description: Fiber Search..................................................................................................B-16B.2.2 Parameter Description: Fiber Creation...............................................................................................B-17B.2.3 Parameter Description: Radio Link Creation......................................................................................B-19

B.3 Parameters for Communications Management............................................................................................B-20B.3.1 Parameter Description: NE Communication Parameter Setting.........................................................B-21B.3.2 Parameter Description: DCC Management_DCC Rate Configuration...............................................B-22B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management..............B-24B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC.........................................B-25B.3.5 Parameter Description: NE ECC Link Management..........................................................................B-26B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management...............................B-28B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation................B-29B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings..........................B-30B.3.9 Parameter Description: OSI Management_Network Layer Parameter...............................................B-33B.3.10 Parameter Description: OSI Management_Routing Table...............................................................B-34B.3.11 Parameter Description: OSI Management_OSI Tunnel....................................................................B-35B.3.12 Parameter Description: DCN Management_Bandwidth Management.............................................B-39B.3.13 Parameter Description: DCN Management_Port Setting.................................................................B-39B.3.14 Parameter Description: Access Control............................................................................................B-40B.3.15 Parameter Description: LCT Access Control...................................................................................B-41

B.4 Radio Link Parameters.................................................................................................................................B-42B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation.........................................B-43B.4.2 Parameter Description: Link Configuration_XPIC............................................................................B-47B.4.3 Parameter Description: N+1 Protection_Create..................................................................................B-54B.4.4 Parameter Description: N+1 Protection..............................................................................................B-55B.4.5 Parameter: IF 1+1 Protection_Create..................................................................................................B-56B.4.6 Parameter Description: IF 1+1 Protection..........................................................................................B-59B.4.7 Parameter: Link Configuration_IF/ODU Configuration....................................................................B-62

B.5 Multiplex Section Protection Parameters.....................................................................................................B-73B.5.1 Parameter Description: Linear MSP_Creation...................................................................................B-73B.5.2 Parameter Description: Linear MSP...................................................................................................B-76

B.6 SDH/PDH Service Parameters.....................................................................................................................B-80B.6.1 Parameter Description: SDH Service Configuration_Creation..........................................................B-80



xv

B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation..................................B-82B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services......................................................................................................................................................................B-85B.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services Into Normal Services......................................................................................................................................................................B-88B.6.5 Parameter Description: SDH Service Configuration..........................................................................B-92B.6.6 Parameter Description: SNCP Service Control..................................................................................B-94

B.7 Clock Parameters.........................................................................................................................................B-97B.7.1 Parameter Description: Clock Source Priority Table..........................................................................B-97B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet.............................................................B-99B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality..........................................................B-103B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control................................................B-106B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status........................................B-107B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters................B-108B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching.....................................B-110B.7.8 Parameter Description: Output Phase-Locked Source of the External Clock Source......................B-111B.7.9 Parameter Description: Clock Synchronization Status.....................................................................B-114

B.8 Parameters for Ethernet Services...............................................................................................................B-116B.8.1 Parameter Description: E-Line Service_Creation.............................................................................B-116B.8.2 Parameter Description: E-Line Service.............................................................................................B-122B.8.3 Parameter Description: VLAN Forwarding Table Item_Creation....................................................B-127B.8.4 Parameter Description: E-LAN Service_Creation............................................................................B-128B.8.5 Parameter Description: E-LAN Service............................................................................................B-132B.8.6 Parameter Description: QinQ Link_Creation...................................................................................B-144

B.9 Ethernet Protocol Parameters.....................................................................................................................B-145B.9.1 Parameter Description: ERPS Management_Creation.....................................................................B-146B.9.2 Parameter Description: ERPS Management.....................................................................................B-148B.9.3 Parameter Description: MSTP Configuration_Port Group Creation................................................B-154B.9.4 Parameter Description: MSTP Configuration_Port Group Configuration.......................................B-156B.9.5 Parameter Description: MSTP Configuration_ Bridge Parameters..................................................B-156B.9.6 Parameter Description: MSTP Configuration_CIST Parameters.....................................................B-161B.9.7 Parameter Description: MSTP Configuration_Running Information About the CIST....................B-163B.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration............................B-171B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted........B-175B.9.10 Parameter Description: IGMP Snooping Configuration_Route Management...............................B-176B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation...................B-177B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management.........B-178B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation....................................................................................................................................................................B-180B.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics........................................B-181B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation.........................B-183B.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority..................................................B-187B.9.17 Parameter Description: LPT Management_Creation......................................................................B-188


Configuration Guide

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

Issue 02 (2009-10-30)

B.9.18 Parameter Description: Port Mirroring_Creation...........................................................................B-189B.10 Parameters for the Ethernet OAM...........................................................................................................B-190

B.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation.....B-191B.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation....................................................................................................................................................................B-192B.10.3 Parameter Description: Ethernet Service OAM Management_MEP Creation...............................B-192B.10.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation.................B-194B.10.5 Parameter Description: Ethernet Service OAM Management_MIP Creation................................B-194B.10.6 Parameter Description: Ethernet Service OAM Management_LB Enabling.................................B-195B.10.7 Parameter Description: Ethernet Service OAM Management_LT Enabling..................................B-197B.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter.................................B-198B.10.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring..........B-201

B.11 QoS Parameters........................................................................................................................................B-202B.11.1 Parameter Description: Diffserv Domain Management..................................................................B-203B.11.2 Parameter Description: DiffServ Domain Management_Create....................................................B-207B.11.3 Parameter Description: DiffServ Domain Applied Port_Modification..........................................B-213B.11.4 Parameter Description: Policy Management..................................................................................B-214B.11.5 Parameter Description: Port Policy.................................................................................................B-220B.11.6 Parameter Description: Port Policy_Traffic Classification Configuration.....................................B-226B.11.7 Parameter Description: Port Shaping Management_Creation........................................................B-236

B.12 RMON Parameters...................................................................................................................................B-238B.12.1 Parameter Description: RMON Performance_Statistics Group......................................................B-238B.12.2 Parameter Description: RMON Performance_History Group........................................................B-239B.12.3 Parameter Description: RMON Performance_History Control Group...........................................B-240B.12.4 Parameter Description: RMON Performance_RMON Setting.......................................................B-241

B.13 Parameters for the Orderwire and Auxiliary Interfaces...........................................................................B-243B.13.1 Parameter Description: Orderwire_General....................................................................................B-244B.13.2 Parameter Description: Orderwire_Advanced................................................................................B-246B.13.3 Parameter Description: Orderwire_F1 Data Port............................................................................B-246B.13.4 Parameter Description: Orderwire_Broadcast Data Port................................................................B-247B.13.5 Parameter Description: Environment Monitoring Interface...........................................................B-248

B.14 Parameters for Board Interfaces...............................................................................................................B-251B.14.1 Parameter Description: IF Interface_IF Attribute...........................................................................B-252B.14.2 Parameter Description: IF Interface_ATPC Attribute....................................................................B-254B.14.3 Parameter Description: Hybrid/AM Configuration........................................................................B-256B.14.4 Parameter Description: ATPC Adjustment Records.......................................................................B-258B.14.5 Parameter Description: PRBS Test.................................................................................................B-259B.14.6 Parameter Description: ODU Interface_Radio Frequency Attribute..............................................B-260B.14.7 Parameter Description: ODU Interface_Power Attributes..............................................................B-262B.14.8 Parameter Description: ODU Interface_Equipment Information...................................................B-264B.14.9 Parameter Description: ODU Interface_Advanced Attributes........................................................B-265B.14.10 Parameter Description: SDH Interfaces........................................................................................B-266B.14.11 Parameter Description: Automatic Laser Shutdown.....................................................................B-268



xvii

B.14.12 Parameter Description: PDH Interfaces........................................................................................B-269B.14.13 Parameter Description: Ethernet Interface_Basic Attributes........................................................B-271B.14.14 Parameter Description: Ethernet Interface_Flow Control............................................................B-274B.14.15 Parameter Description: Ethernet Interface_Layer 2 Attributes.....................................................B-275B.14.16 Parameter Description: Ethernet Interface_Advanced Attributes.................................................B-279B.14.17 Parameter Description: Microwave Interface_Basic Attributes...................................................B-281B.14.18 Parameter Description: Microwave Interface_Layer 2 Attributes................................................B-282B.14.19 Parameter Description: Microwave Interface_Advanced Attributes............................................B-284

B.15 Parameters for Overhead..........................................................................................................................B-286B.15.1 Parameter Description: Regenerator Section Overhead..................................................................B-287B.15.2 Parameter Description: VC-4 POHs...............................................................................................B-288B.15.3 Parameter Description: VC-12 POHs.............................................................................................B-289

C Glossary......................................................................................................................................C-1

D Acronyms and Abbreviations...............................................................................................D-1


Configuration Guide

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

Issue 02 (2009-10-30)

Figures

Figure 2-1 HWECC solution................................................................................................................................2-3Figure 2-2 Inband DCN solution..........................................................................................................................2-4Figure 2-3 Networking diagram (chain network)...............................................................................................2-12Figure 2-4 Board configuration of NEs on a TDM chain microwave network..................................................2-13Figure 2-5 Board configuration of NEs on a Hybrid chain microwave network...............................................2-14Figure 2-6 Allocated IDs and IP addresses (chain network)..............................................................................2-15Figure 2-7 Networking diagram (ring network).................................................................................................2-19Figure 2-8 Board configuration of NEs on the TDM microwave ring network.................................................2-20Figure 2-9 Board configuration of NEs on the Hybrid microwave ring network..............................................2-20Figure 2-10 Allocated IDs and IP addresses (ring network)..............................................................................2-21Figure 3-1 PDH radio link....................................................................................................................................3-2Figure 3-2 SDH radio link....................................................................................................................................3-3Figure 3-3 Hybrid radio link................................................................................................................................3-3Figure 3-4 AM......................................................................................................................................................3-4Figure 3-5 Networking diagram of the TDM microwave chain.........................................................................3-12Figure 3-6 Networking diagram of the TDM microwave ring...........................................................................3-19Figure 3-7 Networking diagram of the Hybrid microwave chain network........................................................3-25Figure 3-8 Networking diagram of the Hybrid microwave ring........................................................................ 3-33Figure 4-1 1+1 linear MSP...................................................................................................................................4-3Figure 4-2 1:N linear MSP...................................................................................................................................4-4Figure 4-3 SNCP..................................................................................................................................................4-5Figure 4-4 Numbering VC-12 timeslots by order ...............................................................................................4-6Figure 4-5 Numbering VC-12 timeslots in the interleaved scheme ....................................................................4-7Figure 4-6 Networking diagram (TDM services on the TDM microwave chain network).................................4-9Figure 4-7 Timeslot allocation diagram (TDM services on the TDM microwave chain network)................... 4-10Figure 4-8 Networking diagram (TDM services on the TDM microwave ring network)..................................4-16Figure 4-9 Timeslot allocation diagram (TDM service on the TDM microwave ring network).......................4-16Figure 4-10 Networking diagram (TDM services on the Hybrid microwave chain network)...........................4-22Figure 4-11 Timeslot allocation diagram (TDM services on the Hybrid chain microwave network)...............4-23Figure 4-12 Networking diagram (TDM services on the Hybrid microwave ring network).............................4-29Figure 4-13 Timeslot allocation diagram (TDM services on the Hybrid microwave ring network).................4-29Figure 5-1 Tagged frame format..........................................................................................................................5-7Figure 5-2 Format of the Ethernet frame with a C-TAG and an S-TAG.............................................................5-9

OptiX RTN 910Configuration Guide Figures


xix

Figure 5-3 Format of the Ethernet frame with only an S-TAG..........................................................................5-10Figure 5-4 802.1d Bridge...................................................................................................................................5-15Figure 5-5 802.1q Bridge...................................................................................................................................5-15Figure 5-6 802.1ad Bridge..................................................................................................................................5-15Figure 5-7 Split horizon group...........................................................................................................................5-17Figure 5-8 Implementation of ERPS..................................................................................................................5-19Figure 5-9 LAG..................................................................................................................................................5-20Figure 5-10 Prevention of network loops on the access side.............................................................................5-21Figure 5-11 CAR processing..............................................................................................................................5-23Figure 5-12 Processing of the traffic shaping....................................................................................................5-24Figure 5-13 SP queue scheduling algorithm......................................................................................................5-25Figure 5-14 WRR scheduling algorithm............................................................................................................5-26Figure 5-15 SP+WRR scheduling algorithm......................................................................................................5-26Figure 5-16 Networking diagram (point-to-point transparently transmitted E-line service).............................5-66Figure 5-17 Networking diagram (VLAN-based E-Line service).....................................................................5-75Figure 5-18 Networking diagram (QinQ-based E-Line service)......................................................................5-102Figure 5-19 Networking diagram (802.1d-bridge-based E-LAN service).......................................................5-137Figure 5-20 Networking diagram (802.1q-bridge-based E-LAN service).......................................................5-153Figure 5-21 Networking diagram (802.1ad-bridge-based E-LAN service).....................................................5-174Figure 5-22 Networking diagram (VLAN-based E-Line services)..................................................................5-196Figure 6-1 Clock source protection based on priorities........................................................................................6-3Figure 6-2 SSM protection...................................................................................................................................6-4Figure 6-3 Extended SSM protection...................................................................................................................6-6Figure 6-4 Clock synchronization policy for a chain network.............................................................................6-7Figure 6-5 Clock synchronization policy for a ring network (on which only the SDH signal is transmitted)...............................................................................................................................................................................6-8Figure 6-6 Clock synchronization policy for a ring network (on which not only the SDH signal is transmitted)...............................................................................................................................................................................6-9Figure 6-7 Clock synchronization policy for a port aggregation network (aggregation only through the tributaryport).....................................................................................................................................................................6-10Figure 6-8 Tributary retiming.............................................................................................................................6-11Figure 6-9 Networking diagram (clock for a TDM microwave chain network)................................................6-14Figure 6-10 Clock source information (TDM microwave chain network)........................................................6-15Figure 6-11 Networking diagram (clock for a TDM microwave ring network)................................................6-16Figure 6-12 Clock source information (TDM microwave ring network)...........................................................6-17Figure 6-13 Networking diagram (clock for a Hybrid microwave chain network)...........................................6-19Figure 6-14 Networking diagram (clock for a Hybrid microwave chain network)...........................................6-20Figure 6-15 Networking diagram (clock for a Hybrid microwave ring network)..............................................6-21Figure 6-16 Clock source information (Hybrid microwave ring network)........................................................6-22Figure 7-1 Circuits for the input external alarms.................................................................................................7-4Figure 7-2 Networking diagram (for orderwire)..................................................................................................7-5Figure 7-3 Networking diagram (for orderwire)..................................................................................................7-6Figure 7-4 Networking diagram (synchronous data services)..............................................................................7-8

FiguresOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

Figure 7-5 Networking diagram (asynchronous data services)..........................................................................7-10Figure 7-6 Networking diagram (wayside E1 services).....................................................................................7-12Figure 7-7 Networking diagram (external alarms).............................................................................................7-14Figure A-1 Networking diagram for testing the Ethernet service...................................................................A-135

OptiX RTN 910Configuration Guide Figures


xxi

Tables

Table 1-1 Procedure for initial configuration.......................................................................................................1-2Table 2-1 Mapping relations between the physical boards and logical boards....................................................2-5Table 2-2 Procedure for configuring the network topology.................................................................................2-7Table 3-1 Configuration procedure of TDM radio links......................................................................................3-6Table 3-2 Configuration procedure of Hybrid radio links (the XPIC is used).....................................................3-8Table 3-3 Configuration procedure of Hybrid radio links (the XPIC is not used)...............................................3-9Table 3-4 Basic information about radio links...................................................................................................3-12Table 3-5 Power and ATPC information............................................................................................................3-13Table 3-6 Information of IF boards....................................................................................................................3-14Table 3-7 Basic information about radio links...................................................................................................3-20Table 3-8 Power and ATPC information............................................................................................................3-21Table 3-9 Information of IF boards....................................................................................................................3-21Table 3-10 Basic information about radio links.................................................................................................3-26Table 3-11 Hybrid/AM attribute information.....................................................................................................3-26Table 3-12 Power and ATPC information..........................................................................................................3-27Table 3-13 Information about IF boards.............................................................................................................3-28Table 3-14 Basic information about radio links.................................................................................................3-34Table 3-15 Hybrid/AM attribute information.....................................................................................................3-34Table 3-16 Power and ATPC information..........................................................................................................3-35Table 3-17 Information about IF boards.............................................................................................................3-36Table 4-1 Procedure for configuring TDM services.............................................................................................4-7Table 4-2 Linear MSP........................................................................................................................................4-11Table 4-3 SNCP..................................................................................................................................................4-17Table 4-4 Linear MSP........................................................................................................................................4-24Table 4-5 SNCP..................................................................................................................................................4-30Table 5-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adopts the auto-negotiationmode).....................................................................................................................................................................5-4Table 5-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adopts the auto-negotiation mode)..................................................................................................................................................5-5Table 5-3 Processing mode of data frames at ports with different VLAN tags...................................................5-8Table 5-4 E-Line Service Model........................................................................................................................5-11Table 5-5 Bridge Type........................................................................................................................................5-14Table 5-6 E-LAN service model........................................................................................................................5-16Table 5-7 Procedure for configuring point-to-point transparently transmitted E-Line services........................5-27

OptiX RTN 910Configuration Guide Tables


xxiii

Table 5-8 Procedures for configuring VLAN-based E-Line services................................................................5-32Table 5-9 Procedures for configuring QinQ-based E-Line services..................................................................5-39Table 5-10 Procedure for configuring 802.1d bridge-based E-LAN services....................................................5-45Table 5-11 Procedure for configuring 802.1q bridge-based E-LAN services....................................................5-52Table 5-12 Procedure for configuring 802.1ad bridge-based E-LAN services..................................................5-59Table 5-13 Ethernet port.....................................................................................................................................5-67Table 5-14 Ethernet port.....................................................................................................................................5-67Table 5-15 Point-to-point transparently transmitted E-line service...................................................................5-68Table 5-16 Service class and PHB service class................................................................................................5-68Table 5-17 Queue scheduling mode...................................................................................................................5-69Table 5-18 Ethernet port (NE1)..........................................................................................................................5-76Table 5-19 Ethernet port (NE2)..........................................................................................................................5-76Table 5-20 Ethernet port (NE3)..........................................................................................................................5-76Table 5-21 Ethernet port (NE4)..........................................................................................................................5-76Table 5-22 Ethernet port (NE5)..........................................................................................................................5-77Table 5-23 Ethernet port (NE6)..........................................................................................................................5-77Table 5-24 IF_ETH port (NE1)..........................................................................................................................5-78Table 5-25 IF_ETH port (NE2)..........................................................................................................................5-78Table 5-26 IF_ETH port (NE3)..........................................................................................................................5-78Table 5-27 IF_ETH port (NE4)..........................................................................................................................5-78Table 5-28 IF_ETH port (NE5)..........................................................................................................................5-78Table 5-29 IF_ETH port (NE6)..........................................................................................................................5-79Table 5-30 LAG..................................................................................................................................................5-79Table 5-31 VLAN-based E-Line service (NE1).................................................................................................5-80Table 5-32 VLAN-based E-Line service (NE2).................................................................................................5-80Table 5-33 VLAN-based E-Line service (NE3).................................................................................................5-80Table 5-34 VLAN-based E-Line service (NE4).................................................................................................5-81Table 5-35 VLAN-based E-Line service (NE5).................................................................................................5-81Table 5-36 VLAN-based E-Line service (NE6).................................................................................................5-82Table 5-37 Service class and PHB service class................................................................................................5-82Table 5-38 Queue scheduling mode...................................................................................................................5-83Table 5-39 CAR parameters...............................................................................................................................5-84Table 5-40 Ethernet port (NE1)........................................................................................................................5-103Table 5-41 Ethernet port (NE2)........................................................................................................................5-103Table 5-42 Ethernet port (NE3)........................................................................................................................5-103Table 5-43 Ethernet port (NE4)........................................................................................................................5-104Table 5-44 Ethernet port (NE5)........................................................................................................................5-104Table 5-45 Ethernet port (NE6)........................................................................................................................5-104Table 5-46 IF_ETH port (NE1)........................................................................................................................5-105Table 5-47 IF_ETH port (NE2)........................................................................................................................5-105Table 5-48 IF_ETH port (NE3)........................................................................................................................5-105Table 5-49 IF_ETH port (NE4)........................................................................................................................5-106

TablesOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

Table 5-50 IF_ETH port (NE5)........................................................................................................................5-106Table 5-51 IF_ETH port (NE6)........................................................................................................................5-106Table 5-52 LAG................................................................................................................................................5-106Table 5-53 QinQ-based E-Line service (NE1).................................................................................................5-107Table 5-54 QinQ-based E-Line service (NE2).................................................................................................5-108Table 5-55 QinQ-based E-Line service (NE3).................................................................................................5-108Table 5-56 QinQ-based E-Line service (NE4).................................................................................................5-109Table 5-57 QinQ-based E-Line service (NE5).................................................................................................5-109Table 5-58 QinQ-based E-Line service (NE6).................................................................................................5-110Table 5-59 Service class and PHB service class..............................................................................................5-111Table 5-60 Queue scheduling mode.................................................................................................................5-111Table 5-61 CAR parameters.............................................................................................................................5-112Table 5-62 Shaping parameters........................................................................................................................5-112Table 5-63 Ethernet port (NE1)........................................................................................................................5-137Table 5-64 Ethernet port (NE2)........................................................................................................................5-138Table 5-65 Ethernet port (NE3)........................................................................................................................5-138Table 5-66 Ethernet port (NE4)........................................................................................................................5-138Table 5-67 IF_ETH port...................................................................................................................................5-139Table 5-68 IF_ETH port...................................................................................................................................5-139Table 5-69 IF_ETH port...................................................................................................................................5-140Table 5-70 IF_ETH port...................................................................................................................................5-140Table 5-71 LAG................................................................................................................................................5-140Table 5-72 ERPS instance................................................................................................................................5-141Table 5-73 802.1d-bridge-based E-LAN service..............................................................................................5-141Table 5-74 Service class and PHB service class..............................................................................................5-142Table 5-75 Queue scheduling mode.................................................................................................................5-143Table 5-76 Ethernet port (NE1)........................................................................................................................5-154Table 5-77 Ethernet port (NE2)........................................................................................................................5-154Table 5-78 Ethernet port (NE3)........................................................................................................................5-155Table 5-79 Ethernet port (NE4)........................................................................................................................5-155Table 5-80 IF_ETH port...................................................................................................................................5-156Table 5-81 IF_ETH port...................................................................................................................................5-156Table 5-82 IF_ETH port...................................................................................................................................5-156Table 5-83 IF_ETH port...................................................................................................................................5-157Table 5-84 LAG................................................................................................................................................5-157Table 5-85 ERPS instance................................................................................................................................5-157Table 5-86 802.1q-bridge-based E-LAN service..............................................................................................5-158Table 5-87 Service class and PHB service class..............................................................................................5-159Table 5-88 Queue scheduling mode.................................................................................................................5-160Table 5-89 CAR parameters.............................................................................................................................5-161Table 5-90 Ethernet port (NE1)........................................................................................................................5-175Table 5-91 Ethernet port (NE2)........................................................................................................................5-175



xxv

Table 5-92 Ethernet port (NE3)........................................................................................................................5-176Table 5-93 Ethernet port (NE4)........................................................................................................................5-176Table 5-94 IF_ETH port...................................................................................................................................5-177Table 5-95 IF_ETH port...................................................................................................................................5-177Table 5-96 IF_ETH port...................................................................................................................................5-177Table 5-97 IF_ETH port...................................................................................................................................5-178Table 5-98 LAG................................................................................................................................................5-178Table 5-99 ERPS instance................................................................................................................................5-179Table 5-100 802.1ad-bridge-based E-LAN service..........................................................................................5-179Table 5-101 Service class and PHB service class............................................................................................ 5-180Table 5-102 Queue scheduling mode...............................................................................................................5-181Table 5-103 CAR parameters...........................................................................................................................5-182Table 5-104 Shaping parameters......................................................................................................................5-182Table 5-105 Ethernet port (NE1)......................................................................................................................5-197Table 5-106 Ethernet port (NE2)......................................................................................................................5-197Table 5-107 Ethernet port (NE3)......................................................................................................................5-197Table 5-108 Ethernet port (NE4)......................................................................................................................5-198Table 5-109 Ethernet port (NE5)......................................................................................................................5-198Table 5-110 Ethernet port (NE6)......................................................................................................................5-198Table 5-111 IF_ETH port (NE1)......................................................................................................................5-199Table 5-112 IF_ETH port (NE2)......................................................................................................................5-199Table 5-113 IF_ETH port (NE3)......................................................................................................................5-199Table 5-114 IF_ETH port (NE4)......................................................................................................................5-200Table 5-115 IF_ETH port (NE5)......................................................................................................................5-200Table 5-116 IF_ETH port (NE6)......................................................................................................................5-200Table 5-117 LAG..............................................................................................................................................5-200Table 5-118 Information about VLAN-based E-Line services (NE1)............................................................. 5-201Table 5-119 Information about VLAN-based E-Line services (NE2)............................................................. 5-201Table 5-120 Information about VLAN-based E-Line services (NE4)............................................................. 5-202Table 5-121 Information about VLAN-based E-Line services (NE5)............................................................. 5-202Table 5-122 Information about VLAN-based E-Line services (NE6)............................................................. 5-203Table 5-123 Information about IEEE 802.1q Bridge-Based E-LAN Services.................................................5-203Table 5-124 Service class and PHB service class............................................................................................ 5-204Table 5-125 Queue scheduling mode...............................................................................................................5-205Table 5-126 CAR parameters...........................................................................................................................5-205Table 5-127 Shaping parameters......................................................................................................................5-206Table 6-1 Procedures for configuring the clock.................................................................................................6-12Table 7-1 Information about orderwire ports.......................................................................................................7-6Table 7-2 Information about the synchronous data service..................................................................................7-9Table 7-3 Information about the asynchronous data service..............................................................................7-11Table 7-4 Information about wayside E1 services.............................................................................................7-13Table 7-5 Information about input alarms..........................................................................................................7-14

TablesOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

Table 7-6 Information about output alarms........................................................................................................7-15Table B-1 Methods used by Ethernet interfaces to process data frames.........................................................B-278Table B-2 Data frame processing....................................................................................................................B-283



xxvii

1 Configuration Preparations

About This Chapter

Before configuring the NE data, you must make the required preparations.

1.1 Preparing Documents and ToolsThe relevant documents and tools must be available to ensure the proper configuration of data.

1.2 Checking Configuration ConditionsBefore the configuration, check whether the configuration conditions meet the requirements.

1.3 Specifying the Configuration ProcedureYou can select the proper configuration procedure according to the actual configurationscenarios.

OptiX RTN 910Configuration Guide 1 Configuration Preparations


1-1

1.1 Preparing Documents and ToolsThe relevant documents and tools must be available to ensure the proper configuration of data.

Documentsl Network planning documents, such as the XXX Network Planning

l OptiX RTN 910 Radio Transmission System Configuration Guide

Toolsl A computer where the U2000 server software is installed

l A computer where the U2000 client software is installed

NOTEFor information about the software and hardware required for the U2000 and the installation method, see thedocuments that accompany the U2000.

1.2 Checking Configuration ConditionsBefore the configuration, check whether the configuration conditions meet the requirements.

Ensure that the following requirements are met:

l All the NEs on the network must be powered on properly.

l The DCN communication between the gateway NE and the non-gateway NEs must benormal.

l The network communication between the U2000 server and the gateway NE must benormal.

l The U2000 client can log in to the U2000 server and has the "network operator" authorityor higher.

1.3 Specifying the Configuration ProcedureYou can select the proper configuration procedure according to the actual configurationscenarios.

Procedure for Initial ConfigurationInitial configuration of a microwave network refers to configuring the network-wide servicedata by using the U2000 for the first time after the NE commissioning is complete. Table 1-1describes the configuration procedure.

Table 1-1 Procedure for initial configuration

Step Operation Description

1 2 Configuring the NetworkTopology

Required.

1 Configuration PreparationsOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)


2 3 Configuring Radio Links Required.

3 4 Configuring TDMServices

Required when the TDMservices need to betransmitted.

4 5 Configuring EthernetServices

Required when the Ethernetservices need to betransmitted.

4 6 Configuring the Clock Required.

6 7 Configuring AuxiliaryInterfaces and Functions

Required when the orderwireinformation, wayside E1service, or synchronous/asynchronous data serviceneeds to be transmitted.

OptiX RTN 910Configuration Guide 1 Configuration Preparations


1-3

2 Configuring the Network Topology

About This Chapter

You can manage NEs and fibers by using the U2000 only after creating their topologies on theU2000.

2.1 Basic ConceptsBefore configuring the network topology, you need to be familiar with the basic concepts.

2.2 Configuration ProcedureThis topic describes the procedure for configuring the four topological objects, namely, NEs,boards, fibers/cables, and subnets.

2.3 Configuration Example (Chain Network)This topic considers a chain microwave network as an example to describe how to configurethe network topology according to the network planning information.

2.4 Configuration Example (Ring Network)This topic considers a microwave ring network as an example to describe how to configure thenetwork topology according to the network planning information.

OptiX RTN 910Configuration Guide 2 Configuring the Network Topology


2-1

2.1 Basic ConceptsBefore configuring the network topology, you need to be familiar with the basic concepts.

2.1.1 DCNTo manage and maintain an NE, the U2000 needs to communicate with the NE through the datacommunication network (DCN).

2.1.2 GNE and Non-GNEThe gateway NE (GNE) refers to the NE whose application layer communicates directly withthe application layer of the U2000. The non-GNE refers to the NE whose application layercommunicates with the application layer of the U2000 by forwarding data through theapplication layer of the GNE.

2.1.3 ID and IP Address of an NEThe ID and IP address are the unique identifiers of an NE on the DCN.

2.1.4 Physical Boards and Logical BoardsThe NE software considers a physical board as one or more logical boards when managing thephysical board. The U2000 also considers a physical board as one or more logical boards whenmanaging the physical board.

2.1.5 Fiber/Cable TypesYou can obtain the clear fiber/cable connection relations between NEs by using the fibermanagement function of the U2000. You can manage the fibers and cables by using theU2000, including SDH fibers, radio links, extended ECC cables, and back-to-back microwaveconnections.

2.1.6 SubnetNEs in a same domain or with similar attributes can be allocated to a same subnet. In this way,they can be displayed as a whole on the U2000, thus facilitating the NE management.

2.1.1 DCNTo manage and maintain an NE, the U2000 needs to communicate with the NE through the datacommunication network (DCN).

On a DCN, the U2000 and all the NEs are considered as nodes on the DCN. The DCN betweenthe U2000 and all the NEs is considered as the external DCN, and the DCN between the NEs isconsidered as the internal DCN. The OptiX RTN 910 supports several DCN solutions, includingHWECC, IP over DCC, and inband DCN. HWECC is the commonest DCN solution.

HWECC is the default DCN solution provided by the OptiX RTN 910. In the case of HWECC,the network management (NM) message is encapsulated in the proprietary HWECC protocolstack. Hence, the HWECC solution is easy to configure. As a proprietary protocol stack,however, HWECC can be used only when there is one isolated OptiX RTN 910 NE or when theOptiX RTN 910 NE networks with other OptiX equipment that supports HWECC.

Figure 2-1 shows how the NM message is transmitted when HWECC is used. The NM messageencapsulated in the HWECC protocol stack can be transmitted on the DCC channels over theoptical fiber or microwave, and can also be transmitted over the Ethernet between the EthernetNM interfaces or between the NE cascade interfaces. If there are no fiber connections ormicrowave links between two NEs, ensure that the Ethernet connection is set up between thecorresponding Ethernet NM interfaces or NE cascade interfaces on the NEs. Otherwise, the

2 Configuring the Network TopologyOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

communication between the two NEs fails. The Ethernet connection between the correspondingEthernet NM interfaces or NE cascade interfaces functions as the extended channel fortransmitting the HWECC protocol stack and is hence considered as the extended ECC. Theextended ECC function is enabled by default.

Figure 2-1 HWECC solution

DCCHWECCMessage

DCCHWECC

Message

DCCHWECCMessage

FiberRadio link Ethernet link

OptiX opticaltransmission equipment

OptiX radiotransmission equipment

NMS

DCCHWECC

Message

DCCHWECC

Message

ETHHWECC

Message

In addition, the inband DCN is enabled by default. In the inband DCN solution, the NMmanagement message occupies part of the Ethernet service bandwidth and is transmitted overHybrid microwave link or through FE/GE ports. The inband DCN solution applies to thescenarios where the OptiX RTN 910 networks OptiX packet switching equipment, as shown inFigure 2-2.



2-3

Figure 2-2 Inband DCN solution

Ethernet linkOptiX PTN equipmentOptiX RTN 910/950

ETHIP stack

OptiX Msg

Inband DCNIP stack

OptiX Msg

Hybrid MWIP stack

OptiX Msg

FE/GEIP stack

OptiX Msg

NMS

In the inband DCN solution, the NM management message occupies part of the Ethernet servicebandwidth. Hence, the DCN function of the ports that are not connected to the OptiX packetswitching equipment must be disabled.

2.1.2 GNE and Non-GNEThe gateway NE (GNE) refers to the NE whose application layer communicates directly withthe application layer of the U2000. The non-GNE refers to the NE whose application layercommunicates with the application layer of the U2000 by forwarding data through theapplication layer of the GNE.

GNEGenerally, the GNE is connected to the U2000 through a LAN/WAN. The application layer ofthe U2000 can directly communicate with the application layer of the GNE. One set of U2000needs to be connected to one or more GNEs.

Disable the extended ECC function of the GNEs, to prevent oversized DCN that is caused dueto the ECC communication between the GNEs.

Non-GNEA non-GNE communicates with the GNE through the DCN channels between NEs. It isrecommended that fewer than 50 GNEs are affiliated to a GNE.

2.1.3 ID and IP Address of an NEThe ID and IP address are the unique identifiers of an NE on the DCN.


Configuration Guide


Issue 02 (2009-10-30)

ID of an NEAt the application layer of each DCN solution, the OptiX NE uses the NE ID as the address ofthe NE. Hence, the ID of each NE on the DCN must be unique and complies with the uniformDCN planning.

The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) andthe lowest 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnetID of the NE is 9 and the basic ID is 1.

IP Address of an NEAn NE uses the IP address as its unique identifier during the TCP/IP communication.

In the HWECC solution, the IP addresses of the NEs on the DCN are used in the followingscenarios:

l The GNE communicates with the U2000 over TCP/IP based on the IP address. The IPaddress must comply with the uniform planning of the external DCN.

l Different NEs communicate with each other over extended ECC channels based on the IPaddresses. The IP addresses of the NEs must be within the same network segment. Bydefault, the IP address of an NE is within the 129.9.0.0 network segment.

In the DCN solutions (for example, inband DCN) where the NM message is transmitted overTCP/IP, the IP address of an NE is used as the NE address at the network layer. Hence, the IPof each NE on the DCN must be unique and complies with the uniform planning of the DCN.

By default, that is, if the IP address of an NE is not changed manually, the IP address and ID ofthe NE interlock each other. That is, when the NE ID is changed, the IP address is automaticallymodified to 0x81000000 + ID. For example, when the NE ID is changed to 0x090001, the IPaddress is automatically changed to 129.9.0.1. After the IP address is changed manually, theinterlocking relation between the ID and IP address fails.

2.1.4 Physical Boards and Logical BoardsThe NE software considers a physical board as one or more logical boards when managing thephysical board. The U2000 also considers a physical board as one or more logical boards whenmanaging the physical board.

Table 2-1 provides the mapping relations between the physical boards and logical boards.

Table 2-1 Mapping relations between the physical boards and logical boards

Physical Board Logical Board

CSTA CSTA in slot 1 + SL1D in slot 8 + SP3S inslot 9 + AUX in slot 10

CSHA CSHA in slot 1 + EM4T in slot 7 + SP3S inslot 9 + AUX in slot 10

CSHB CSHB in slot 1 + EM4T in slot 7 + SP3D inslot 9 + AUX in slot 10

CSHC CSHB in slot 1 + EM4F in slot 7 + SL1D inslot 8 + SP3S in slot 9 + AUX in slot 10



2-5

Physical Board Logical Board

IF1 IF1 in the same slot

IFU2 IFU2 in the same slot

IFX2 IFX2 in the same slot

SL1D SL1D in the same slot

EM6T EM6T in the same slot

EM6F EM6F in the same slot

SP3S SP3S in the same slot

SP3D SP3D in the same slot

PIU PIU in the same slot

FAN FAN in the same slot

ODU ODU in the slot whose number is 20 plus theslot number of the IF board that is connectedto the ODU

2.1.5 Fiber/Cable TypesYou can obtain the clear fiber/cable connection relations between NEs by using the fibermanagement function of the U2000. You can manage the fibers and cables by using theU2000, including SDH fibers, radio links, extended ECC cables, and back-to-back microwaveconnections.

l SDH fibersSDH fibers refer to the fiber connections between different sets of equipment. That is, SDHfibers indicate the connection relations between different SDH optical interfaces.

l Radio linksRadio links refer to the microwave connections between different sets of microwaveequipment. That is, the radio links indicate the connection relations between different IFports.

l Extended ECC cablesExtended ECC cables refer to the extended ECC channels between the NEs. That is, theextended ECC cables indicate the connection relations between the NEs.

l Back-to-back microwave connectionsBack-to-back microwave connections refer to the NE cascading relations. That is, the back-to-back microwave connections indicate the connection relations between the NEs.

NOTE

Fibers and cables are topological objects on the U2000. Hence, operations on the fibers or cables do not affectthe normal running of the NEs.


Configuration Guide


Issue 02 (2009-10-30)

2.1.6 SubnetNEs in a same domain or with similar attributes can be allocated to a same subnet. In this way,they can be displayed as a whole on the U2000, thus facilitating the NE management.

The subnets are topological objects on the U2000. Hence, operations on the subnets do not affectthe normal running of the NEs. In the case of a large number of topological objects, subnets thatcontain multiple NEs simplify the topology view on the U2000.

2.2 Configuration ProcedureThis topic describes the procedure for configuring the four topological objects, namely, NEs,boards, fibers/cables, and subnets.

Table 2-2 Procedure for configuring the network topology


1 CreatingNEs on theU2000

A.1.2CreatingNEs byUsing theManualMethod

It is recommended that you perform this operationto add one or more NEs to a large existing networkon the U2000.

A.1.1CreatingNEs byUsing theSearchMethod

It is recommended that you perform this operationto create NEs on the U2000 in other cases. Thefollowing parameters need to be set:l Search Domain: When the IP address of the GNE

is known, it is recommended that you set the IPaddress range of the GNE as the search domain.In the case of initial configuration, it isrecommended that you set the 129.9.255.255network segment as the search domain.

l Search for NE: It is recommended that you selectSearch for NE, Create device after search NEUser, and Upload after create. By default, NEUser is root and Password is password.

2 A.2.1 Uploading theNE Data

If you select Upload after create during A.1.1Creating NEs by Using the Search Method, skipthis operation.

3 A.1.4 Changing the NEID

Required. Set the parameters as follows:l Change ID to be the NE ID specified during the

planning of the DCN.l If the extended NE ID is required, change

Extended ID.



2-7


4 A.6.1 Setting NECommunicationParameters

Required. Set the parameters as follows:l In the case of the GNE, set IP Address and

Subnet Mask according to the planning of theexternal DCN.

l In the case of the GNE, set Gateway IPAddress if the external DCN requires.

l In the case of non-GNEs, it is recommended thatyou set IP Address to 0x81000000 + NE ID. Thatis, if the NE ID is 0x090001, set IP Address to129.9.0.1. Set Subnet Mask to 255.255.0.0.

NOTEIf the IP address of an NE is not changed manually, the IPaddress changes according to the NE ID and is always0x81000000 + NE ID. In this case, the IP address of a non-GNE does not need to be changed manually.

5 A.1.5 Changing the NEName

Optional.

6 A.1.3 Configuring theLogical Board

Required.

7 A.6.3 Configuring theExtended ECC

Required in the case of the GNE. Set the parametersas follows:l Set Extended Mode to Specified Mode.

l Adopt the default values for the other parameters.NOTE

This operation is performed to disable the automaticextended ECC function of the GNE.

8 A.6.10 Setting theVLAN ID andBandwidth Used by anInband DCN

In the case of an NE interconnecting with packetswitching equipment, perform this operation tochange the VLAN ID and bandwidth of the inbandDCN that are planned for the packet switchingequipment to the default values. The default VLANID is 4094 and the default bandwidth is 512 kbit/s.

9 A.6.11 Configuring theEnable Status of theInband DCN Functionon Ports

Required in the case of the Hybrid microwavenetwork. Set the parameters as follows:l In the case of the Ethernet ports and microwave

ports that interconnect with the packet switchingequipment, set Enabled Status to Enabled.

l In the case of the other ports, set EnabledStatus to Disabled.

10 A.3 Configuring thePerformanceMonitoring Status ofNEs

The 15-minute and 24-hour NE performancemonitoring functions are enabled by default and thusdo not need to be set manually.


Configuration Guide


Issue 02 (2009-10-30)


11 Creatingradio linksor SDHfibers

A.4Connecting Fibersor Cables

It is recommended that you perform this operationto create radio links or SDH fibers on the U2000when the physical radio links or SDH fibers exist.

A.4.1CreatinganOpticalTransmission Lineor RadioLink byUsing theSearchMethod

Perform this operation to create the radio links on theU2000 that do not exist currently.

A.4.2Creatinga RadioLink byUsing theManualMethod

Perform this operation to create the SDH fibers onthe U2000 that do not exist currently.



2-9


12 Synchronizing theNE time

A.1.6Synchronizing theNE Time

Required.l To synchronize the NEs with the NM server, set

the relevant parameters as follows:– Set Synchronous Mode to NM.

– Right-click and choose the operation from theshortcut menu to ensure that the NE aresynchronized with the NM time immediately.

– Set the synchronization parameters accordingto the requirements. It is recommended that theparameters adopt the default values.

l To synchronize the NEs with the NTP server, setthe relevant parameters as follows:– Set Synchronous Mode to Standard NTP.

– Set Standard NTP Authentication accordingto the requirements for the NTP server.

– It is recommended that you set the upper levelNTP server that the NEs trace as follows:– In the case of the GNE, set the external NTP

server to the upper level NTP server. SetStandard NTP Server Identifier to IP andset Standard NTP Server to the IP addressof the external NTP server.

– In the case of a non-GNE, set the GNE to theupper level NTP server. If the non-GNEneeds to communicate with the GNEthrough the HWECC protocol, setStandard NTP Server Identifier to NEID and set Standard NTP Server to the NEID of the GNE. If the non-GNE needs tocommunicate with the GNE through the IPprotocol, set Standard NTP ServerIdentifier to IP and set Standard NTPServer to the IP address of the GNE.

– Set Standard NTP Server Key accordingto the requirements for the NTP server.

A.1.7Localizing the NETime

Required if the DST scheme is used at the local area.Set the parameters according to the planning of theDST at the local area.

A.1.8ConfiguringStandardNTP Keys

Required if the standard NTP authentication is usedto synchronize the NEs with the NTP server.Set the parameters according to the identificationauthentication of the NTP.


Configuration Guide


Issue 02 (2009-10-30)


13 Creatingradio linksor SDHfibers

A.4.1CreatinganOpticalTransmission Lineor RadioLink byUsing theSearchMethod

It is recommended that you perform this operationto create radio links or SDH fibers on the U2000when the physical radio links or SDH fibers exist.

A.4.2Creatinga RadioLink byUsing theManualMethod

Perform this operation to create the radio links on theU2000 that do not exist currently.

A.4.3Creatingan SDHOpticalTransmission Linkby UsingtheManualMethod

Perform this operation to create the SDH fibers onthe U2000 that do not exist currently.

14 A.4.4 Creating anExtended ECC

Optional when NEs are connected through extendedECC channels.

15 A.4.5 Creating a Back-to-Back MicrowaveConnection

Optional when there are cascading NEs on thenetwork.

16 Configuring thesubnet

A.5.1Creatinga Subnet

Optional.

A.5.2CopyingTopologyObjects

Optional.

A.5.3MovingTopologyObjects

Optional.



2-11

NOTE

l If the NE ID and NE name are changed in the NE commissioning process and if the NE communicationparameters, logical boards, VLAN ID and bandwidth of the inband DCN are set during the NEcommissioning, the configuration data is automatically synchronized onto the U2000 in the NE datauploading process. Hence, you need not perform the corresponding operations in the initial configurationprocess.

l The preceding configuration procedure is applicable to the scenarios wherein HWECC is used as the DCNsolution. When a DCN solution other than HWECC is used, the DCN-related operations described in thepreceding configuration procedure may be inapplicable.

2.3 Configuration Example (Chain Network)This topic considers a chain microwave network as an example to describe how to configurethe network topology according to the network planning information.

2.3.1 Networking DiagramThe topic describes the networking information about the NEs.2.3.2 Board ConfigurationBefore performing the networking planning, you need to be familiar with the board configurationof each NE.2.3.3 Service PlanningThe service planning information contains the information about all the parameters required forconfiguring the NE data.2.3.4 Configuration ProcessThis topic describes the procedure for the data configuration.

2.3.1 Networking DiagramThe topic describes the networking information about the NEs.

Figure 2-3 shows a backhaul microwave subnet for a mobile base station. On this network, ifno fiber connections are set up between NE2 and NE3, NE2 and NE3 are connected through anEthernet cable. In this case, the extended ECC communication is implemented through theEthernet NM interfaces or the NE cascading interfaces.

Figure 2-3 Networking diagram (chain network)

BSC

BTS5

BTS3

BTS2

NE1NE2NE3

NE5

NE4

NE6

NMS

BTS4

BTS1


Configuration Guide


Issue 02 (2009-10-30)

2.3.2 Board ConfigurationBefore performing the networking planning, you need to be familiar with the board configurationof each NE.

NOTE

The board configuration information provided in this configuration example also applies to the configurationexamples of radio links, TDM services, and Ethernet services.

Board Configuration of NEs on a TDM Chain Microwave NetworkFigure 2-4 shows the board configuration of each NE on a TDM chain microwave network.

Figure 2-4 Board configuration of NEs on a TDM chain microwave network

BSC

IF1

NE1NE2NE3

BTS1

E1

BTS2

BTS3

E1

E1

E1

BTS4

NE4

NE5NE6

BTS1

E1

CSTA

IF1CSTA

IF1 IF1CSTA

IF1 IF1CSTA

IF1 IF1CSTA

IF1 IF1CSTA

STM-1

STM-1

Board Configuration of NEs on a Hybrid Chain Microwave NetworkFigure 2-5 shows the board configuration of each NE on a Hybrid chain microwave network.



2-13

Figure 2-5 Board configuration of NEs on a Hybrid chain microwave network

BSC

IFU2

NE1NE2NE3

BTS1E1+FE

BTS2

BTS3

BTS4

NE4

NE5NE6

BTS5

E1+FE

CSHA

IFU2CSHA

IFU2 IFU2CSHA

IFU2 IFU2CSHA

IFU2 IFU2CSHB

IFU2 IFU2CSHC

E1+FE

E1+FE

E1+FE

E1+GE+NE cascade

GESTM-1

NOTE

"NE cascade" indicates that an Ethernet cable is used to connect two NEs through the Ethernet NM interfacesor NE cascading interfaces.

2.3.3 Service PlanningThe service planning information contains the information about all the parameters required forconfiguring the NE data.

l The U2000 is connected to NE1 through the LAN. Hence, NE1 is the GNE and the otherNEs are non-GNEs, which access the U2000 through NE1.

l The chain network comprises only OptiX RTN 910. Hence, HWECC is preferred as theDCN solution. In the HWECC solution, NE2 and NE3 communicate with each otherthrough the extended ECC that is enabled by default, because no fiber connections are setup between NE2 and NE3. The other NEs communicate with each other through the DCCchannels over microwave.

l NE1 is the GNE. Hence, the extended ECC function of NE1 needs to be disabled.

l On this chain network, the OptiX RTN 910 does not interconnect with OptiX packetswitching equipment. Hence, the inband DCN function needs to be disabled for all theHybrid microwave ports and FE ports in the case of the Hybrid microwave network.

l Figure 2-6 shows the ID and IP address that are allocated to each NE according to theuniform DCN planning information.


Configuration Guide


Issue 02 (2009-10-30)

Figure 2-6 Allocated IDs and IP addresses (chain network)

NE2NE3

NE5

NE4

NE6

NMS

9-110.0.0.10.0.0.0

10.0.0.100/16

9-5129.9.0.50.0.0.0

9-6129.9.0.60.0.0.0

9-4129.9.0.40.0.0.0

Extended ID-Basic IDIP addressGatew ay

9-2129.9.0.20.0.0.0

9-3129.9.0.30.0.0.0

NOTE

l The subnet mask for the IP address of each NE is 255.255.0.0.

l The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence,if the IP address of an NE (not NE1) is not changed manually, the NE automatically changes the IPaddress to be the planned value after the NE ID is changed.

l In this example, the policy of synchronizing the NE with the NM server is used. Theautomatic synchronization period is one day. The daylight saving time (DST) scheme isnot used at the local area.

l In this configuration example, no subnets need to be configured.

2.3.4 Configuration ProcessThis topic describes the procedure for the data configuration.

PrecautionsIf the NE ID and the values of NE communication parameters are changed and the logical boardsare configured in the NE commissioning process, skip the operations.

Procedure

Step 1 See A.1.1 Creating NEs by Using the Search Method and create the NEs.

The values for the related parameters are provided as follows.

Parameter Value

Search Domain Network Segment 129.9.255.255

Search User root

Search for NE Search for NE Selected

Create device after searchNE User

Selected



2-15

Parameter Value

Upload after create Selected

NE User root

Password password

NOTE

In this configuration example, it is assumed that the IP address of the GNE is not changed manually and is notknown. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as thesearch domain. If the IP address of the GNE is known, it is recommended that you use the IP address of theGNE as the search domain.

The icons of NE1 to NE6 should be displayed on the Main Topology and all the NE data shouldbe uploaded successfully.

Step 2 See A.1.4 Changing the NE ID and change the NE ID.


Parameter

Value

NE1 NE2 NE3 NE4 NE5 NE6

ID 1 2 3 4 5 6

ExtendedID

9 (defaultvalue)

9 (defaultvalue)

9 (defaultvalue)

9 (defaultvalue)

9 (defaultvalue)

9 (defaultvalue)

Step 3 See A.6.1 Setting NE Communication Parameters and set the NE communication parameters.


Parameter Value

NE1

IP Address 10.0.0.1

Gateway IP Address 0.0.0.0 (default value)

Subnet Mask 255.255.0.0 (default value)

NOTE

The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you neednot change the values of the NE communication parameters manually.

Step 4 See A.1.3 Configuring the Logical Board and configure the logical boards.

Configure the logical boards according to the mapping relations between the physical boardsand logical boards.


Configuration Guide


Issue 02 (2009-10-30)

Step 5 See A.6.3 Configuring the Extended ECC and configure the extended ECC.


Parameter Value

NE1

ECC Extended Mode Specified mode

Port (on the server side) 1601 (default value)

Opposite IP (on the client side) 0.0.0.0 (default value)

Port (on the client side) 1601 (default value)

NOTE

This operation is performed to disable the automatic extended ECC function of NE1.

Step 6 In the case of the Hybrid microwave network, see A.6.11 Configuring the Enable Status ofthe Inband DCN Function on Ports and disable the inband DCN function of the port.


Parameter Value

All the Ports on All the NEs

Enabled Status Disabled

Step 7 See A.1.6 Synchronizing the NE Time and synchronize the NE time.


Parameter Value


Synchronous Mode NM

Synchronization Period(days) 1

Step 8 See A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links or SDH fiber connections.Normally, all the radio links or SDH fiber connections should be created successfully on theMain Topology.

Step 9 When an Ethernet cable is used to connect NE2 and NE3 through the Ethernet NM interfacesor NE cascading interfaces, see A.4.4 Creating an Extended ECC and create the extended ECCconnections.




2-17

Parameter Value

Source NE NE2

Sink NE NE3

Step 10 See A.4.5 Creating a Back-to-Back Microwave Connection and create back-to-backmicrowave connections.


Parameter Value

Source NE NE2

Sink NE NE3

----End

2.4 Configuration Example (Ring Network)This topic considers a microwave ring network as an example to describe how to configure thenetwork topology according to the network planning information.






Figure 2-7 shows a backhaul microwave subnet for a mobile base station.


Configuration Guide


Issue 02 (2009-10-30)

Figure 2-7 Networking diagram (ring network)

BTS2

BTS1

NE1

NE3

NE2

NMS

NE4

BSC

BTS3

BTS4


NOTE

The board configuration information provided in this configuration example also applies to the configurationexamples of radio links, TDM services, and Ethernet services.

Board Configuration of NEs on the TDM Microwave Ring NetworkFigure 2-8 shows the board configuration of each NE on the TDM microwave ring network.



2-19

Figure 2-8 Board configuration of NEs on the TDM microwave ring network

BTS3

NE4

BSC

BTS4

NE3

IF1 IF1CSTA

IF1 IF1CSTA

IF1 IF1CSTA

IF1 IF1CSTA

BTS2

BTS3

NE1

NE2E1

E1

E1

E1

E1

Board Configuration of NEs on the Hybrid Microwave Ring NetworkFigure 2-9 shows the board configuration of each NE on the Hybrid microwave ring network.

Figure 2-9 Board configuration of NEs on the Hybrid microwave ring network

BTS3

NE4

BSC

BTS4

NE3

IFU2 IFU2CSHA

IFU2 IFU2CSHA

IFU2 IFU2CSHA

IFU2 IFU2CSHA

BTS2

BTS3

NE1

NE2E1+FE

E1+FE

E1+FE

E1+FE

E1+GE



Configuration Guide


Issue 02 (2009-10-30)

l The OptiX RTN 910 is connected to NE1 through the LAN. Hence, NE1 is the GNE andthe other NEs are non-GNEs, which access the OptiX RTN 910 through NE1.

l The ring network comprises only OptiX RTN 910. Hence, HWECC is preferred as the DCNsolution. In the HWECC solution, the NEs communicate with each other through the DCCchannels over microwave.

l NE1 is the GNE. Hence, the extended ECC function of NE1 should be disabled.

l On this ring network, the OptiX RTN 910 does not interconnect with OptiX packetswitching equipment. Hence, the inband DCN function needs to be disabled for all theHybrid microwave ports and FE ports in the case of the Hybrid microwave network.

l Figure 2-10 shows the ID and IP address that are allocated to each NE according to theuniform DCN planning information.

Figure 2-10 Allocated IDs and IP addresses (ring network)

NE1

NE3

9-110.0.0.10.0.0.0

10.0.0.100/16

9-2129.9.0.20.0.0.0

9-3129.9.0.30.0.0.0

9-4129.9.0.40.0.0.0

NE2 NE4

Extended ID-Basic IDIP addressGatew ay

NOTE

l The subnet mask for the IP address of each NE is 255.255.0.0.

l The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence,if the IP address of an NE (not NE1) is not changed manually, the NE automatically changes the IPaddress to be the planned value after the NE ID is changed.

l In this example, the policy of synchronizing the NE with the NM server is used. Theautomatic synchronization period is one day. The daylight saving time (DST) scheme isnot used at the local area.

l In this configuration example, no subnets need to be configured.


Precautions

If the NE ID and the values of NE communication parameters are changed and the logical boardsare configured in the NE commissioning process, skip the operations.



2-21

Procedure

Step 1 See A.1.1 Creating NEs by Using the Search Method and create the NEs.


Parameter Value

Search Domain Network Segment 129.9.255.255

Search User root

Search for NE Search for NE Selected

Create device after searchNE User

Selected

Upload after create Selected

NE User root

Password password

NOTE

In this configuration example, it is assumed that the IP address of the GNE is not changed manually and the IPaddresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommendedthat you use the IP address of the GNE as the search domain.

The icons of NE1 to NE6 should be displayed on the Main Topology and all the NE data shouldbe uploaded successfully.

Step 2 See A.1.4 Changing the NE ID and change the NE ID.


Parameter Value

NE1 NE2 NE3 NE4

ID 1 2 3 4

Extended ID 9 (default value) 9 (default value) 9 (default value) 9 (default value)

Step 3 See A.6.1 Setting NE Communication Parameters and set the NE communication parameters.


Parameter Value

NE1

IP Address 10.0.0.1

Gateway IP Address 0.0.0.0 (default value)


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE1

Subnet Mask 255.255.0.0 (default value)

NOTE

The IP addresses of all the NEs, except NE1, are in the interlocking relations with the NE IDs. Hence, you neednot change the values of the NE communication parameters manually.

Step 4 See A.1.3 Configuring the Logical Board and configure logical boards.

Configure the logical boards according to the mapping relations between the physical boardsand logical boards.

Step 5 See A.6.3 Configuring the Extended ECC and configure the extended ECC.


Parameter Value

NE1

ECC Extended Mode Specified mode

Port (on the server side) 1601 (default value)

Opposite IP (on the client side) 0.0.0.0 (default value)

Port (on the client side) 1601 (default value)

NOTE

This operation is performed to disable the automatic extended ECC function of NE1.

Step 6 In the case of the Hybrid microwave network, see A.6.11 Configuring the Enable Status ofthe Inband DCN Function on Ports and disable the inband DCN function of the port.


Parameter Value


Enabled Status Disabled

Step 7 See A.1.6 Synchronizing the NE Time and synchronize the NE time.


Parameter Value


Synchronous Mode NM

Synchronization Period(days) 1



2-23

Step 8 See A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links or SDH fiber connections.Normally, all the radio links or SDH fiber connections should be created successfully on theMain Topology.

----End


Configuration Guide


Issue 02 (2009-10-30)

3 Configuring Radio Links

About This Chapter

Before configuring services on a radio link, you need to configure the radio link.

3.1 Basic ConceptsBefore configuring the radio link, you need to be familiar with the basic concepts.

3.2 Configuration ProcedureThe configuration procedures of different radio link configuration methods are different.

3.3 Configuration Example (Radio Links on the TDM Microwave Chain Network)This topic considers radio links on a TDM microwave chain network as examples to describehow to configure radio links according to the planning information.

3.4 Configuration Example (Radio Links on the TDM Microwave Ring Network)This topic considers TDM radio links on a TDM microwave ring network as examples to describehow to configure radio links according to the network planning information.

3.5 Configuration Example (Radio Links on the Hybrid Microwave Chain Network)This topic considers radio links on a Hybrid microwave chain network as examples to describehow to configure radio links according to the network planning information.

3.6 Configuration Example (Radio Links on the Hybrid Microwave Ring Network)This topic considers radio links on a Hybrid microwave ring network as examples to describehow to configure radio links according to the network planning information.

OptiX RTN 910Configuration Guide 3 Configuring Radio Links


3-1

3.1 Basic ConceptsBefore configuring the radio link, you need to be familiar with the basic concepts.

3.1.1 Types of Radio LinksThe OptiX RTN 910 supports two types of radio links, namely, TDM radio link and Hybridradio link. The TDM radio link is classified into SDH radio link and PDH radio link.

3.1.2 RF Configuration ModesThe OptiX RTN 910 supports five RF configuration modes, namely, 1+0 non-protectionconfiguration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protectionconfiguration, and cross-polarization interference cancellation (XPIC) configuration.

3.1.1 Types of Radio LinksThe OptiX RTN 910 supports two types of radio links, namely, TDM radio link and Hybridradio link. The TDM radio link is classified into SDH radio link and PDH radio link.

PDH Radio LinkThe PDH radio link refers to the radio link that transmits only the PDH services (mainly, the E1services). During the transmission, the features of the PDH services are not changed.

The OptiX RTN 910 embeds the MADM, which grooms E1 services to the microwave port fortransmission.

Figure 3-1 PDH radio link

ODU

E1

IDU

OH MADM

PDH radioSDH

……

The PDH radio link supports only a specific modulation mode. That is, in running state, all theequipment on the PDH radio link works in the same modulation mode. You can specify thismodulation mode by using the software.

SDH Radio LinkThe SDH radio link refers to the radio link that transmits SDH services. During the transmission,the features of the SDH services are not changed.

3 Configuring Radio LinksOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

The OptiX RTN 910 embeds the MADM, which cross-connects and grooms services to themicrowave port, maps the services into the STM-1-based microwave frames, and then transmitsthe STM-1-based microwave frames.

Figure 3-2 SDH radio link

ODU

E1

IDU

MADM

SDH radioSDH

OH

……

OH

……

The SDH radio link supports only a specific modulation mode. That is, in running state, all theequipment on the SDH radio link works in the same modulation mode. You can specify thismodulation mode by using the software.

Hybrid Radio LinkThe Hybrid radio link refers to the radio link that transmits Native E1 services and NativeEthernet services at the same time. The Hybrid radio link supports the AM function.

The OptiX RTN 910 embeds the MADM and the packet processing platform. The MADMtransmits E1 services that are accessed locally or extracted from the SDH services to themicrowave port. The packet processing platform processes the accessed Ethernet services in theunified manner and then transmits the Ethernet services to the microwave port. The microwaveport maps the E1 services and the Ethernet services into Hybrid microwave frames and thentransmits the Hybrid microwave frames.

Figure 3-3 Hybrid radio link

ODU

Ethernet

E1IDU

TDMcross-connect

matrix

Packetswitching

Hybrid radio

Native E1 and native Ethernet

The Hybrid radio link supports both the fixed modulation mode and the AM. When the AM isenabled, the equipment adopts a higher modulation mode to transmit as many user services as



3-3

possible if the channel quality is favorable (such as on days when the weather is favorable). Inthis manner, the transmission efficiency and the spectrum utilization of the system are improved.When the channel quality deteriorates (such as on days when the weather is stormy and foggy),the equipment adopts a lower modulation mode to transmit only the services with a higherpriority over the available bandwidth and to discard the services with a lower priority. In thismanner, the anti-interference capability of the radio link is improved and the link availability ofthe services with a higher priority is ensured.

Figure 3-4 shows the service change caused by the AM. The orange part indicates the E1services. The blue part indicates the Ethernet services. The closer to the edge of the blue part,the lower the priority of the Ethernet service. Under all channel conditions, the E1 servicesoccupy the specific bandwidth permanently. In this manner, the availability of the E1 servicesis ensured. The bandwidth for the Ethernet services varies with the channel conditions. Whenthe channel is in poor conditions, the Ethernet services with a lower priority are discarded.

Figure 3-4 AM

Channelcapability

E1 services

256QAM32QAM

QPSK

256QAM

128QAM

32QAM

128QAM

64QAM

64QAM

16QAM16QAM

Ethernetservices

3.1.2 RF Configuration ModesThe OptiX RTN 910 supports five RF configuration modes, namely, 1+0 non-protectionconfiguration, N+0 non-protection configuration, 1+1 protection configuration, N+1 protectionconfiguration, and cross-polarization interference cancellation (XPIC) configuration.

1+0 Non-Protection ConfigurationThe 1+0 non-protection configuration indicates that the radio link has one working channel andno protection channel.

N+0 Non-Protection ConfigurationThe N+0 non-protection configuration indicates that the radio link has N working channels andno protection channel.


Configuration Guide


Issue 02 (2009-10-30)

The OptiX RTN 910 supports N+0 protection (1<N≤2).

1+1 Protection ConfigurationThe 1+1 protection configuration indicates that the radio link has one working channel and oneprotection channel.

The 1+1 protection configuration is classified into 1+1 HSB, 1+1 FD, and 1+1 SD.

l In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configurationfor the IF boards and ODUs at both ends of each hop of radio link, thus realizing theprotection.

l In the 1+1 FD protection mode, the system uses two channels with a specific frequencyinterval to transmit and receive the same service signal. The opposite end selects from thetwo received signals. With the 1+1 FD protection, the impact of the fading on signaltransmission is reduced.The 1+1 FD protection also supports the 1+1 HSB protection.

l In the 1+1 SD protection mode, the system uses two antennas with a space distance toreceive the same RF signal. The equipment selects from the two received signals. With the1+1 SD protection, the impact of the fading on signal transmission is reduced.The 1+1 SD protection also supports the 1+1 HSB protection.

N+1 Protection ConfigurationThe N+1 protection configuration indicates that the radio link has N working channels and oneprotection channel.

The OptiX RTN 910 supports N+1 protection only in the case of STM-1 microwave and Hybridmicrowave. The N+1 protection is implemented through the N+1 MSP similar to l:N linear MSP.

The OptiX RTN 910 supports N+1 protection (N=1).

XPIC ConfigurationThe XPIC adopts both the horizontally polarized wave and the vertically polarized wave overone channel to transmit two channels of signals. The radio link capacity in the case of XPICconfiguration is double the radio link capacity in the case of 1+0 configuration.

The OptiX RTN 910 supports only the XPIC configuration for the Hybrid radio link.

3.2 Configuration ProcedureThe configuration procedures of different radio link configuration methods are different.



3-5

Configuration Procedure of TDM Radio Links

Table 3-1 Configuration procedure of TDM radio links


1 A.7.1Creating anIF 1+1ProtectionGroupa

Required when the radio links are configured with 1+1protection.Parameters are set according to the network planninginformation.


Configuration Guide


Issue 02 (2009-10-30)


2 A.7.4Configuringthe IF/ODUInformationof a RadioLinka

Required. The parameters are set as follows:l Set Work Mode, Link ID, and ATPC Enable Status

according to the network planning information.l During the site commissioning, ATPC Enable Status

must be set to Disabled.l It is recommended that you set ATPC Upper Threshold

(dBm) to the central value plus 10 dB.l It is recommended that you set ATPC Lower Threshold

(dBm) to the central value minus 10 dB.l It is recommended that you set ATPC Automatic

Threshold Enable to Disabled.l Set TX Frequency(MHz), T/R Spacing(MHz), and TX

Power(dBm) according to the network planninginformation.

l Set TX Status to unmute.

l Set Power to Be Received(dBm) to the receive levelspecified in the network planning. Only after thisparameter is set, the antenna non-alignment indicationfunction is enabled. When the antenna non-alignmentindication function is enabled, if the actual receive powerof the ODU is beyond the range of preset receive power (-3dBm to +3 dBm), the ODU indicator on the IF boardconnected to the ODU blinks yellow (300 ms on, 300 msoff), indicating that the antennas are not aligned. After theantennas are aligned for consecutive 30 minutes, the NEautomatically disables the antenna non-alignmentindication function.

l When the maximum transmit power allowed in the ATPCadjustment needs to be set, set Maximum TransmitPower(dBm) as required.

l TX High Threshold(dBm), TX Low Threshold(dBm),RX High Threshold(dBm), and RX Low Threshold(dBm) only affect the performance events related to theATPC and can be set as required.

NOTE

l In the case of radio links configured with 1+1 HSB/SD, you needto configure the IF and ODU information on the main radio linkonly. In the case of radio links configured with 1+1 FD, you needto configure the IF and ODU information on the main radio linkand the ODU information on the standby radio link.

l In the case of TDM radio links configured with N+1 protection,you need to configure the IF and ODU information on each link.Work Mode must be configured as 7, STM-1, 28MHz,128QAM.



3-7


3 A.7.6Creating anN+1ProtectionGroup

Required when the radio links are configured with N+1protection.The N+1 protection groups of the equipment at both ends musthave the same attributes.Parameters are set according to the network planninginformation.

4 A.4.1Creating anOpticalTransmission Line orRadio Linkby Using theSearchMethod

Normally, the main topology should display the previouslycreated radio links.

NOTE

a: Generally, during the site commissioning, the previous two steps are completed. After the site commissioning,however, you need to reset ATPC Enable Status.

Configuration Procedure of Hybrid Radio LinksThe configuration process greatly depends on whether the XPIC is used for configuring Hybridradio.

Table 3-2 Configuration procedure of Hybrid radio links (the XPIC is used)


1 A.7.2Creating anXPICProtectionGroup

Required.Parameters are set according to the network planninginformation.

2 A.7.3Setting theHybrid/AMAttributesof the XPICHybridRadio Link

Required.Parameters are set according to the network planninginformation. The parameters in both polarization directionsshould take the same values.


Configuration Guide


Issue 02 (2009-10-30)


4 A.7.4Configuringthe IF/ODUInformationof a RadioLink

Required. The parameters are set as follows:l When the Packet microwave equipment is interconnected

with radio links, set Enable IEEE-1588 Timeslot toEnabled.


l TX High Threshold(dBm), TX Low Threshold(dBm),RX High Threshold(dBm), and RX Low Threshold(dBm) only affect the performance events related to theATPC and can be set as required.

NOTEThe preceding parameters need to set to the same values, separatelyfor the radio links in the vertical and horizontal polarizationdirections.



NOTE

During the site commissioning, you can configure the two XPIC links as two separate non-XPIC link accordingto Table 3-3.

Table 3-3 Configuration procedure of Hybrid radio links (the XPIC is not used)


1 A.7.1Creating anIF 1+1ProtectionGroupa

Required when the radio links are configured with 1+1protection.Parameters are set according to the network planninginformation.



3-9


2 A.7.4Configuringthe IF/ODUInformationof a RadioLinka

Required. The parameters are set as follows:l Set Enable AM and Channel Space according to the

network planning information.l Set Guaranteed Capacity Modulation and Full

Capacity Modulation according to the network planninginformation when the radio links enable the AM function.

l Set Manually Specified Modulation according to thenetwork planning information when the radio links disablethe AM function.

l During the site commissioning, Enable AM must be set toDisabled, and Manually Specified Modulation is set toGuaranteed Capacity Modulation as planned.

l Set Specified Max E1 Capacity, Link ID, and ATPCEnable Status according to the network planninginformation.

l During the site commissioning, ATPC Enable Statusmust be set to Disabled.

l It is recommended that you set ATPC Upper Threshold(dBm) to the central value plus 10 dB.

l It is recommended that you set ATPC Lower Threshold(dBm) to the central value minus 10 dB.

l It is recommended that you set ATPC AutomaticThreshold Enable to Disabled.

l When the Packet radio equipment is interconnected withradio links, set Enable IEEE-1588 Timeslot to Enabled.

l Set TX Frequency(MHz), T/R Spacing(MHz), and TXPower(dBm) according to the network planninginformation.

l Set TX Status to unmute.


l When the maximum transmit power allowed in the ATPCadjustment needs to be set, set Maximum TransmitPower(dBm) as required.

l TX High Threshold(dBm), TX Low Threshold(dBm),RX High Threshold(dBm), and RX Low Threshold


Configuration Guide


Issue 02 (2009-10-30)


(dBm) only affect the performance events related to theATPC and can be set as required.

NOTE

l In the case of radio links configured with 1+1 HSB/SD, you needto configure the IF and ODU information on the main radio linkonly. In the case of radio links configured with 1+1 FD, you needto configure the IF and ODU information on the main radio linkand the ODU information on the standby radio link.

l To configure Hybrid radio links with N+1 protection, you need toconfigure the IF and ODU information on each link.

3 A.7.6Creating anN+1ProtectionGroup

Required when the radio links are configured with N+1protection.The N+1 protection groups of the equipment at both ends musthave the same attributes.Parameters are set according to the network planninginformation.

4 A.7.7Setting IFAttributes

Required when the XPIC function is not enabled on the IFX2board. In this case, set XPIC Enabled to Disabled.NOTE

To configure 1+1 protection radio links, you need to configure theinformation about the main IF board only.



NOTE

a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,however, you need to reset Enable AM and ATPC Enable Status.

3.3 Configuration Example (Radio Links on the TDMMicrowave Chain Network)

This topic considers radio links on a TDM microwave chain network as examples to describehow to configure radio links according to the planning information.


3.3.2 Service Planning



3-11

The service planning information contains the information about all the parameters required forconfiguring the NE data.



Based on 2.3 Configuration Example (Chain Network), configure the TDM radio linksaccording to the network planning information, as shown in Figure 3-5.

Figure 3-5 Networking diagram of the TDM microwave chain

NE1NE2NE3

NE5

NE4

NE6

14952M14532M

16E1,14M,16QAM1+0

H-polarization

Tx high station Tx Freq.Tx low station Tx Freq.

Radio work modeRF configuarion

Polarization

14930M14510M

8E1,7M,16QAM1+0

H-polarzation

Tx highTx low

Tx low

Tx low

Tx high

Tx high

Tx low

Tx high

Link ID

10114930M14510M

STM-1,28M,128QAM1+1 HSB

V-polarzation

102

14967M14547M

22E1,14M,32QAM1+0

V-polarization

103

104


Basic Information About Radio Links

According to the spectrum allocation on the radio network and the required radio transmissioncapacity, you can obtain the basic information about the radio links, as provided in Table 3-4.

Table 3-4 Basic information about radio links

Parameter Link 1 Link 2 Link 3 Link 4

Link ID 101 102 103 104


Configuration Guide


Issue 02 (2009-10-30)


Tx high site NE1 NE4 NE5 NE5

Tx low site NE2 NE3 NE3 NE6

Tx frequency at theTx high site (MHz)

14930 14952 14967 14930

Tx frequency at theTx low site (MHz)

14510 14532 14547 14510

T/R spacing (MHz) 420 420 420 420

Radio workingmode

STM-1, 28MHz,128QAM

16E1, 14MHz,16QAM

22E1, 14MHz,32QAM

8E1, 7MHz,16QAM

RF configurationmode

1+1 HSB 1+0 1+0 1+0

Polarizationdirection

V (verticalpolarization)

H (horizontalpolarization)



NOTE

The planning information that is not related to the configuration of the IDU (except for the polarizationdirection) is not provided in this example.

Power and ATPC InformationBy using the radio network planning software such as the Pathloss, you can analyze and computethe availability of services and parameters of radio links. Then, you can obtain the power andATPC information of the radio links as provided in Table 3-5.

Table 3-5 Power and ATPC information


Transmit power(dBm)

5 (NE1)5 (NE2)

10 (NE3)10 (NE4)

10 (NE3)10 (NE5)

15 (NE5)15 (NE6)

Receive power(dBm)

-42 (NE1)-42 (NE2)

-44 (NE3)-44 (NE4)

-43 (NE3)-43 (NE5)

-48 (NE5)-48 (NE6)

ATPC enabling Enabled Enabled Enabled Enabled

ATPC automaticthreshold enabling

Disabled Disabled Disabled Disabled

Upper threshold ofATPC adjustment(dBm)

-32 (NE1)-32 (NE2)

-34 (NE3)-34 (NE4)

-33 (NE3)-33 (NE5)

-38 (NE5)-38 (NE6)



3-13


Lower threshold ofATPC adjustment(dBm)

-52 (NE1)-52 (NE2)

-54 (NE3)-54 (NE4)

-53 (NE3)-53 (NE5)

-58 (NE5)-58 (NE6)

Maximum transmitpower (dBm)

- - - -

NOTE

l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled ifthere is no such a requirement.

l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central valuebetween the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upperthreshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receivepower.

l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.When this parameter is not specified, the value of the parameter is the rated maximum transmit power ofthe ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees withthe spectrum configuration profile. Hence, this parameter is not set generally.

Information of IF Boards

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1protection, you can obtain the information of IF boards as provided in Table 3-6.

Table 3-6 Information of IF boards


Main IF board 3-IF1 (NE1)3-IF1 (NE2)

3-IF1 (NE3)3-IF1 (NE4)

4-IF1 (NE3)4-IF1 (NE5)

3-IF1 (NE5)3-IF1 (NE6)

Standby IF board 4-IF1 (NE1)4-IF1 (NE2)

- - -


1+1 HSB 1+0 1+0 1+0

Revertive mode Revertive (defaultvalue)

- - -

WTR time(s) 600 (default value) - - -

Reverse switchingenabling

Enabled (defaultvalue)

- - -

l It is recommended that you configure the IF board in slot 3 as the main IF board whenconfiguring a 1+1 HSB/FD/SD protection group.


Configuration Guide


Issue 02 (2009-10-30)

l If there are no special requirements, the other parameters of the 1+1 HSB/FD/SD all takedefault values.


Procedure

Step 1 See A.7.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups forNE1 and NE2.l The values for the relevant parameters of NE1 are provided as follows.

Parameter Value

NE1

Working Mode HSB

Revertive Mode Revertive mode

WTR Time(s) 600

Enable Reverse Switching Enabled

Working Board 3-IF1

Protection Board 4-IF1

l The values for the relevant parameters of NE2 are provided as follows.

Parameter Value

NE2

Working Mode HSB


WTR Time(s) 600


Working Board 3-IF1

Protection Board 4-IF1

Step 2 See A.7.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODUinformation of the radio link.l The values for the relevant parameters of NE1 are provided as follows.



3-15

Parameter Value

3-IF1 and 23-ODU

Work Mode 7, STM-1, 28MHz, 128QAM

Link ID 101

ATPC Enable Status Enabled

ATPC Upper Threshold(dBm) -32

ATPC Lower Threshold(dBm) -52

ATPC Automatic Threshold Enable Disabled

TX Frequency(MHz) 14930

T/R Spacing(MHz) 420

TX Power(dBm) 5

TX Status unmute

Power to Be Received(dBm) -42


Parameter Value

3-IF1 and 23-ODU

Work Mode 7, STM-1, 28MHz, 128QAM

Link ID 101







TX Power(dBm) 5

TX Status unmute




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

3-IF1 and 23-ODU 4-IF1 and 24-ODU

Work Mode 6, 16E1, 14MHz, 16QAM 8, 22E1, 14MHz, 32QAM

Link ID 102 103

ATPC Enable Status Enabled Enabled

ATPC Upper Threshold(dBm)

-34 -33

ATPC Lower Threshold(dBm)

-54 -53

ATPC AutomaticThreshold Enable

Disabled Disabled

TX Frequency(MHz) 14532 14547

T/R Spacing(MHz) 420 420

TX Power(dBm) 10 10

TX Status unmute unmute

Power to Be Received(dBm)

-44 -43


Parameter Value

3-IF1 and 23-ODU

Work Mode 6, 16E1, 14MHz, 16QAM

Link ID 102







TX Power(dBm) 10

TX Status unmute




3-17


Parameter Value



Link ID 104 103



-38 -33


-58 -53


Disabled Disabled



TX Power(dBm) 15 10



-48 -43


Parameter Value

3-IF1 and 23-ODU

Work Mode 4, 8E1, 7MHz, 16QAM

Link ID 104







TX Power(dBm) 15

TX Status unmute



Configuration Guide


Issue 02 (2009-10-30)

Step 3 See A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links connections.The main topology should display all the created radio links.

----End

3.4 Configuration Example (Radio Links on the TDMMicrowave Ring Network)

This topic considers TDM radio links on a TDM microwave ring network as examples to describehow to configure radio links according to the network planning information.

3.4.1 Networking DiagramThe topic describes the networking information about the NEs.3.4.2 Service PlanningThe service planning information contains the information about all the parameters required forconfiguring the NE data.3.4.3 Configuration ProcessThis topic describes the procedure for the data configuration.


Based on 2.4 Configuration Example (Ring Network), configure the TDM radio linksaccording to the network planning information, as shown in Figure 3-6.

Figure 3-6 Networking diagram of the TDM microwave ring

NE1

NE3

NE2 NE4

10114930M14510M

16E1,14M,16QAM1+0

V-polarzation

14958M14538M

16E1,14M,16QAM1+0

H-polarization

102 10314930M14510M

16E1,14M,16QAM1+0

H-polarzation

14958M14538M

16E1,14M,16QAM1+0

V-polarization

104


Radio work modeRF configuarion

Polarization

Link ID

Tx high Tx high

Tx highTx high

Tx low

Tx low

Tx low

Tx low



3-19


Basic Information About Radio LinksAccording to the spectrum allocation on the radio network and the required radio transmissioncapacity, you can obtain the basic information about the radio links as provided in Table 3-7.



Link ID 101 102 103 104




14930 14958 14930 14958


14510 14538 14510 14538

T/R spacing (MHz) 420 420 420 420

Radio workingmode

16E1, 14MHz,16QAM

16E1, 14MHz,16QAM

16E1, 14MHz,16QAM

16E1, 14MHz,16QAM


1+0 1+0 1+0 1+0






NOTE


Power and ATPC InformationBy using the radio network planning software such as the Pathloss, you can analyze and computethe availability of services and parameters of radio links. Then, you can obtain the power andATPC information about the radio links, as provided in Table 3-8.


Configuration Guide


Issue 02 (2009-10-30)



Transmit power(dBm)

9 (NE1)9 (NE2)

10 (NE3)10 (NE2)

10 (NE3)10 (NE4)

8 (NE1)8 (NE4)

Receive power(dBm)

-46 (NE1)-46 (NE2)

-44 (NE3)-44 (NE2)

-43 (NE3)-43 (NE4)

-47 (NE1)-47 (NE4)

ATPC enabling Enabled Enabled Enabled Enabled


Disabled Disabled Disabled Disabled


-36 (NE1)-36 (NE2)

-34 (NE3)-34 (NE2)

-33 (NE3)-33 (NE4)

-37 (NE1)-37 (NE4)


-56 (NE1)-56 (NE2)

-54 (NE3)-54 (NE2)

-53 (NE3)-53 (NE4)

-57 (NE1)-57 (NE4)


- - - -

NOTE

l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled ifthere is no such a requirement.

l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value ofthe upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper thresholdto 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power.

l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.When this parameter is not specified, the value of the parameter is the rated maximum transmit power ofthe ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees withthe spectrum configuration profile. Hence, this parameter is not set generally.

Information About IF BoardsAccording to the radio type, slot priorities of IF boards, and configuration rules of the 1+1protection, you can obtain the information about IF boards as provided in Table 3-9.

Table 3-9 Information of IF boards


Main IF board 4-IF1 (NE1)3-IF1 (NE2)

4-IF1 (NE2)3-IF1 (NE3)

4-IF1 (NE3)3-IF1 (NE4)

4-IF1 (NE4)3-IF1 (NE1)

Standby IF board - - - -


1+0 1+0 1+0 1+0



3-21


Revertive mode - - - -

WTR time(s) - - - -


- - - -


Procedure

Step 1 See A.7.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODUinformation of the radio link.l The values for the relevant parameters of NE1 are provided as follows.

Parameter Value


Work Mode 6,16E1,14MHz,16QAM 6,16E1,14MHz,16QAM

Link ID 104 101



-37 -36


-57 -56


Disabled Disabled



TX Power(dBm) 8 9



-47 -46



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


Work Mode 6, 16E1,14MHz, 16QAM 6, 16E1, 14MHz, 16QAM

Link ID 101 102



-36 -34


-56 -54


Disabled Disabled



TX Power(dBm) 9 10



-46 -44


Parameter Value



Link ID 102 103



-34 -33


-54 -53


Disabled Disabled



TX Power(dBm) 10 10




3-23

Parameter Value



-44 -43


Parameter Value



Link ID 103 104



-33 -37


-53 -57


Disabled Disabled



TX Power(dBm) 10 8



-43 -47

Step 2 A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links connections.The main topology should display all the created radio links.

----End

3.5 Configuration Example (Radio Links on the HybridMicrowave Chain Network)

This topic considers radio links on a Hybrid microwave chain network as examples to describehow to configure radio links according to the network planning information.



Configuration Guide


Issue 02 (2009-10-30)




Based on 2.3 Configuration Example (Chain Network), configure the Hybrid radio linksaccording to the network planning information, as shown in Figure 3-7. Each Hybrid radio linktransmits E1 services and Ethernet services. The AM function is enabled on each link.

Figure 3-7 Networking diagram of the Hybrid microwave chain network

NE1NE2NE3

NE5

NE4

NE6

14952M14532M

14M1+0

H-polarization


Channel spacingRF configuarion

Polarization

14930M14510M

7M1+0

H-polarzation

Tx highTx low

Tx low

Tx low

Tx high

Tx high

Tx low

Tx high

Link ID

10114930M14510M

28M1+1 HSB

V-polarzation

102

14967M14547M

14M1+0

V-polarization

103

104


Basic Information About Radio LinksAccording to the spectrum allocation on the radio network and the required radio transmissioncapacity, you can obtain the basic information of the radio links, as provided in Table 3-10.



3-25



Link ID 101 102 103 104




14930 14952 14967 14930


14510 14532 14547 14510

T/R spacing (MHz) 420 420 420 420

Channel spacing(MHz)

28 14 14 7


1+1 HSB 1+0 1+0 1+0






NOTE


Hybrid/AM Attribute Information

According to the capacity of E1 and Ethernet services and the availability requirement, you cancalculate the Hybrid/AM attribute information, as provided in Table 3-11.

Table 3-11 Hybrid/AM attribute information


Number of E1services

18 6 8 4

Capacity of Ethernetservices (Mbit/s)

120 35 40 15

AM enabling Enabled Enabled Enabled Enabled

AM guaranteedcapacity mode

QPSK QPSK QPSK QPSK

AM full capacitymode

128QAM 32QAM 64QAM 32QAM


Configuration Guide


Issue 02 (2009-10-30)

NOTE

The Hybrid radio capacity and the AM function require the proper license file.

Power and ATPC InformationBy using the radio network planning software such as the Pathloss, you can analyze and computethe parameters of radio links and obtain the power and ATPC information of the radio links, asprovided in Table 3-12.



Transmit power(dBm)

16.5 (NE1)16.5 (NE2)

16.5 (NE3)16.5 (NE4)

16 (NE3)16 (NE5)

20 (NE5)20 (NE6)

Receive power(dBm)

-46 (NE1)-46 (NE2)

-44 (NE3)-44 (NE4)

-43 (NE3)-43 (NE5)

-48 (NE5)-48 (NE6)

ATPC enabling Disabled Disabled Disabled Disabled


- - - -


- - - -


- - - -


- - - -

NOTE

l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.

l In this example, the ATPC function is disabled.

Information About IF BoardsAccording to the radio type, slot priorities of IF boards, and configuration rules of the 1+1protection, you can obtain the information about IF boards, as provided in Table 3-13.



3-27

Table 3-13 Information about IF boards


Main IF board 3-IFU2 (NE1)3-IFU2 (NE2)

3-IFU2 (NE3)3-IFU2 (NE4)



Standby IF board 4-IFU2 (NE1)4-IFU2 (NE2)

- - -


1+1 HSB 1+0 1+0 1+0

Revertive mode Revertive (defaultvalue)

- - -

WTR time(s) 600 (default value) - - -


Enabled (defaultvalue)

- - -

l It is recommended that you configure the IF board in slot 3 as the main IF board whenconfiguring a 1+1 HSB/FD/SD protection group.

l If there are no special requirements, it is recommended that you plan the other parametersof the 1+1 HSB/FD/SD to be the default values.


Procedure

Step 1 See A.7.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups forNE1 and NE2.l The values for the relevant parameters of NE1 are provided as follows.

Parameter Value

NE1

Working Mode HSB


WTR Time(s) 600


Working Board 3-IFU2

Protection Board 4-IFU2



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE2

Working Mode HSB


WTR Time(s) 600


Working Board 3-IFU2

Protection Board 4-IFU2

Step 2 See A.7.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODUinformation of the radio link.


Parameter Value

3-IFU2 and 23-ODU

Channel Space 28M

Enable AM Enabled

Guaranteed Capacity Modulation QPSK

Full Capacity Modulation 128QAM

Specified Max E1 Capacity 18

Link ID 101

ATPC Enable Status Disabled

Enable IEEE-1588 Timeslot Disabled



TX Power(dBm) 5

TX Status unmute



Parameter Value

3-IFU2 and 23-ODU

Channel Space 28M



3-29

Parameter Value

3-IFU2 and 23-ODU

Enable AM Enabled




Link ID 101





TX Power(dBm) 5

TX Status unmute



Parameter Value

3-IFU2 and 23-ODU 4-IFU2 and 24-ODU

Channel Space 14M 14M

Enable AM Enabled Enabled

Guaranteed CapacityModulation

QPSK QPSK

Full Capacity Modulation 32QAM 64QAM

Specified Max E1Capacity

6 8

Link ID 102 103

ATPC Enable Status Disabled Disabled


Enable IEEE-1588Timeslot

Disabled Disabled


TX Power(dBm) 10 10


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value




-44 -43


Parameter Value

3-IFU2 and 23-ODU

Channel Space 14M

Enable AM Enabled




Link ID 102




TX Power(dBm) 10

TX Status unmute



Parameter Value





QPSK QPSK



4 8

Link ID 104 103



3-31

Parameter Value




Disabled Disabled



TX Power(dBm) 15 10



-48 -43


Parameter Value

3-IFU2 and 23-ODU

Channel Space 7M

Enable AM Enabled




Link ID 104





TX Power(dBm) 15

TX Status unmute


Step 3 A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links connections.The main topology should display all the created radio links.

----End


Configuration Guide


Issue 02 (2009-10-30)

3.6 Configuration Example (Radio Links on the HybridMicrowave Ring Network)

This topic considers radio links on a Hybrid microwave ring network as examples to describehow to configure radio links according to the network planning information.

3.6.1 Networking DiagramThis topic describes the networking information about the NEs.




Based on 2.4 Configuration Example (Ring Network), configure the Hybrid radio linksaccording to the network planning information, as shown in Figure 3-8.

Figure 3-8 Networking diagram of the Hybrid microwave ring

NE1

NE3

NE2 NE4

10114930M14510M

14M1+0

V-polarzation

14958M14538M

14M1+0

H-polarization

102 10314930M14510M

14M1+0

H-polarzation

14958M14538M

14M1+0

V-polarization

104

Tx high Tx high

Tx highTx high

Tx low

Tx low

Tx low

Tx low


Channel spacingRF configuarion

Polarization

Link ID



3-33


Basic Information About Radio LinksAccording to the spectrum allocation on the radio network and the required radio transmissioncapacity, you can obtain the basic information about the radio links, as provided in Table3-14.



Link ID 101 102 103 104




14930 14958 14930 14958


14510 14538 14510 14538

T/R spacing (MHz) 420 420 420 420

Channel spacing(MHz)

14 14 14 14


1+0 1+0 1+0 1+0






NOTE


Hybrid/AM Attribute InformationAccording to the capacity of E1 and Ethernet services and the availability requirement, you cancalculate the Hybrid/AM attribute information as provided in Table 3-15.

Table 3-15 Hybrid/AM attribute information


Number of E1services

16 16 16 16


Configuration Guide


Issue 02 (2009-10-30)


Capacity of Ethernetservices (Mbit/s)

40 40 40 40

AM enabling Enabled Enabled Enabled Enabled

AM guaranteedcapacity mode


AM full capacitymode


NOTE

l According to the Hybrid ring protection scheme, each Hybrid radio link must carry all the services onthe ring.

l The Hybrid radio capacity and the AM function require the appropriate license file.

Power and ATPC InformationBy using the radio network planning software such as the Pathloss, you can analyze and computethe parameters of radio links and obtain the power and ATPC information of the radio links, asprovided in Table 3-16.



Transmit power(dBm)

16.5 (NE1)16.5 (NE2)

16.5 (NE3)16.5 (NE2)

16 (NE3)16 (NE4)

15 (NE1)15 (NE4)

Receive power(dBm)

-42 (NE1)-42 (NE2)

-44 (NE3)-44 (NE2)

-43 (NE3)-43 (NE4)

-45 (NE1)-45 (NE4)

ATPC enabling Disabled Disabled Disabled Disabled


- - - -


- - - -


- - - -


- - - -



3-35

NOTE

l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.

l In this example, the ATPC function is disabled.

Information About IF Boards

According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1protection, you can obtain the information about IF boards, as provided in Table 3-17.

Table 3-17 Information about IF boards


Main IF board 4-IFU2 (NE1)3-IFU2 (NE2)




Standby IF board - - - -


1+0 1+0 1+0 1+0

Revertive mode - - - -

WTR time(s) - - - -


- - - -


Procedure

Step 1 See A.7.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODUinformation of the radio link.


Parameter Value





16QAM 16QAM



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value



16 16

Link ID 104 101



Disabled Disabled



TX Power(dBm) 15 16.5



-45 -42


Parameter Value





16QAM 16QAM



16 16

Link ID 101 102



Disabled Disabled



TX Power(dBm) 16.5 16.5




3-37

Parameter Value



-42 -44


Parameter Value





16QAM 16QAM



16 16

Link ID 102 103



Disabled Disabled



TX Power(dBm) 16.5 16



-44 -43


Parameter Value





16QAM 16QAM



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value



16 16

Link ID 104 103



Disabled Disabled



TX Power(dBm) 16 15



-45 -43

Step 2 See A.4.1 Creating an Optical Transmission Line or Radio Link by Using the SearchMethod and create radio links connections.The main topology should display all the created radio links.

----End



3-39

4 Configuring TDM Services

About This Chapter

The key to configuring TDM services is configuring the corresponding service cross-connections.

4.1 Basic ConceptsBefore configuring the TDM service, you need to be familiar with the basic concepts.

4.2 Configuration ProcedureThis topic describes the procedure for configuring the cross-connections and protection of aTDM service and the procedure for setting the SDH/PDH interface parameters.

4.3 Configuration Example (TDM Services on a TDM Microwave Chain Network)This topic considers a TDM microwave chain network as an example to describe how toconfigure TDM services according to the network planning information.

4.4 Configuration Example (TDM Services on a TDM Microwave Ring Network)This topic considers a TDM microwave ring network as an example to describe how to configureTDM services according to the network planning information.

4.5 Configuration Example (TDM Services on a Hybrid Microwave Chain Network)This topic considers a Hybrid microwave chain network as an example to describe how toconfigure TDM services according to the network planning information.

4.6 Configuration Example (TDM Services on a Hybrid Microwave Ring Network)This topic considers a Hybrid microwave ring network as an example to describe how toconfigure TDM services according to the network planning information.

OptiX RTN 910Configuration Guide 4 Configuring TDM Services


4-1

4.1 Basic ConceptsBefore configuring the TDM service, you need to be familiar with the basic concepts.

4.1.1 Protection Modes for TDM ServicesOptiX RTN 910 supports linear MSP and SNCP for TDM services.

4.1.2 Timeslots for TDM Services on IF BoardsWhen TDM services need to be transmitted on a radio link, you need to configure thecorresponding cross-connections between the service timeslots on the service board and theservice timeslots on the IF board. The timeslots for the TDM services on the IF board are closelyrelated to the type of the microwave services transmitted by the IF board and the microwavecapacity.

4.1.3 Numbering Schemes for SDH TimeslotsTwo numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines orSDH radio links.

4.1.1 Protection Modes for TDM ServicesOptiX RTN 910 supports linear MSP and SNCP for TDM services.

Linear MSPLinear MSP applies to point-to-point physical networks. Linear MSP provides protection for theservices between two multiplex section termination (MST) modules. That is, when a linear MSPswitching occurs, the services are switched from the working section to the protection section.In the case of the OptiX RTN 910, linear MSP provides protection for TDM services that aretransmitted over SDH fibers.

Linear MSP is classified into 1+1 linear MSP and 1:N linear MSP.

l 1+1 linear MSPTo realize the 1+1 linear MSP, one working channel and one protection channel arerequired. The protection channel does not transmit extra services. When the workingchannel becomes unavailable, services are switched to the protection channel fortransmission. Figure 4-1 shows the application of 1+1 linear MSP. According to therevertive mode, 1+1 linear MSP is classified into dual-ended revertive, dual-ended non-revertive, single-ended revertive, and single-ended non-revertive modes. The single-endednon-revertive mode is the most common linear MSP mode.

4 Configuring TDM ServicesOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

Figure 4-1 1+1 linear MSP

Workingchannel

Protectionchannel

NE A NE B

NE A NE BWorkingchannel

Protectionchannel

Protection switching

l 1:N linear MSP

To realize the 1:N linear MSP, N working channels and one protection channel are required.The working channels transmit normal services and the protection channel transmits extraservices. When a working channel becomes unavailable, the services on this channel areswitched to the protection channel for transmission. As a result, the extra servicespreviously transmitted on this protection channel are interrupted. Figure 4-2 shows theapplication of the 1:N linear MSP. The 1:N linear MSP is available only in dual-endedrevertive mode.



4-3

Figure 4-2 1:N linear MSP

Workingchannel 1

Workingchannel 1

Protectionchannel

NE A NE B


Workingchannel N

... ...

Normalservice 1

Normalservice N

Extraservice

Extraservice

Normalservice N

Normalservice1

Protectionchannel

NE A NE B

Workingchannel N

... ...

Normalservice 1

Normalservice N

Extraservice

Extraservice

Normalservice N

Normalservice1

SNCPIn the case of subnetwork connection protection (SNCP), the protection subnetwork connectiontakes over when the working subnetwork connection fails or deteriorates. In the case of theOptiX RTN 910, SNCP provides protection for TDM services that are transmitted on STM-1fiber ring networks, TDM microwave ring networks, Hybrid microwave ring networks, or hybridring networks that comprise optical network equipment and Hybrid microwave equipment.

The SNCP protection scheme, which requires one working subnetwork and one protectionsubnetwork, selects one service from the dually transmitted services. In the case of SNCP, theservices are switched to the protection subnetwork for transmission when the workingsubnetwork connection fails or deteriorates. Figure 4-3 shows the application of SNCP.


Configuration Guide


Issue 02 (2009-10-30)

Figure 4-3 SNCP

Working SNC

Protection SNC

Trail source

NE A NE B

Trail sink

Working SNC

Protection SNC

Trail source

NE A NE B

Trail sink


The OptiX RTN 910 supports the coexistence of SNCP and the 1+1 protection or N+1 protection.In the case of coexistence of the SNCP and the 1+1 protection or N+1 protection, you can setthe hold-off time for SNCP so that the protection switching for the radio link can be performedfirst, thus preventing circular switchings.

4.1.2 Timeslots for TDM Services on IF BoardsWhen TDM services need to be transmitted on a radio link, you need to configure thecorresponding cross-connections between the service timeslots on the service board and theservice timeslots on the IF board. The timeslots for the TDM services on the IF board are closelyrelated to the type of the microwave services transmitted by the IF board and the microwavecapacity.

TDM MicrowaveWhen the IF board works in PDH microwave mode and when the microwave capacity is nxE1,the first to nth VC-12 timeslots on the IF board are available and correspond to first to nth E1sthat are transmitted over microwave. For example, if the microwave capacity is 4xE1, only thefirst to fourth VC-12 timeslots in VC4-1 on the IF board are available. If a cross-connection isconfigured between the E1 port of a service board and the second VC-12 in VC4-1 on the IFboard, the E1 services that are accessed from the E1 port are sent to the second E1 timeslot thatis transmitted over microwave. If the microwave capacity is E3, only the first VC-3 timeslot inVC4-1 on the IF board is available and corresponds to the E3 timeslot that is transmitted overmicrowave.



4-5

When the IF board works in STM-1 microwave mode, all the timeslots in VC4-1 on the IF boardare available and correspond to the timeslots in the VC-4 that is transmitted on microwave.

Hybrid MicrowaveWhen the IF board works in Hybrid microwave mode and when the E1 Capacity is set to n inHybrid/AM Configuration, the first to nth VC-12 timeslots on the IF board are available andcorrespond to the first to nth E1 timeslots that are transmitted over microwave. For example, ifthe E1 capacity is 75xE1, only the first to sixty-third VC-12 timeslots in VC4-1 and the first totwelfth VC-12 timeslots in VC4-2 on the IF board are available. If a cross-connection isconfigured between the E1 port of a service board and the second VC-12 in VC4-2 on the IFboard, the E1 services that are accessed from the E1 port are sent to the sixty-fifth E1 timeslotthat is transmitted over microwave.

4.1.3 Numbering Schemes for SDH TimeslotsTwo numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines orSDH radio links.

VC-12 Timeslot NumberingTwo numbering schemes are applicable to SDH optical/electrical lines or SDH radio links whenyou create cross-connections.

l By orderThis timeslot numbering scheme is also considered as timeslot scheme. The numberingformula is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12number -1) x 21.This scheme is the numbering scheme recommended by ITU-T G.707 and is the defaultscheme adopted by the OptiX equipment.

l Interleaved schemeThis timeslot numbering scheme is also considered as line scheme. The numbering formulais as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1) x 3 + TU-12number.The OptiX equipment can adopt this scheme when it interconnects with the equipment thatadopts the interleaved scheme or when a specific timeslot numbering scheme is required.

Figure 4-4 Numbering VC-12 timeslots by order

1 2 3 4 5 6 7

11 2

31

2 231

3 23

{{

{

TUG-2

TUG-3 TU-12

1 4 7 10 13 16 1922 25 28 31 34 37 4043 46 49 52 55 58 612 5 8 11 14 17 2023 26 29 32 35 38 4144 47 50 53 56 59 623 6 9 12 15 18 2124 27 30 33 36 39 4245 48 51 54 57 60 63


Configuration Guide


Issue 02 (2009-10-30)

Figure 4-5 Numbering VC-12 timeslots in the interleaved scheme

{{

{

TUG-2

TUG-3 TU-12

1 2 3 4 5 6 7

11 2

31

2 231

3 23

1 4 7 10 13 16 192 5 8 11 14 17 203 6 9 12 15 18 2122 25 28 31 34 37 4023 26 29 32 35 38 4124 27 30 33 36 39 4243 46 49 52 55 58 6144 47 50 53 56 59 6245 48 51 54 57 60 63

VC-3 Timeslot NumberingA VC-3 timeslot number corresponds to a TUG-3 number. If you need to configure cross-connections of VC-3s and VC-12s in the same VC-4, note that the timeslots in the TUG-3 thatare occupied by the VC-3 cross-connections cannot be configured for VC-12 cross-connections.

4.2 Configuration ProcedureThis topic describes the procedure for configuring the cross-connections and protection of aTDM service and the procedure for setting the SDH/PDH interface parameters.

Table 4-1 Procedure for configuring TDM services


1 A.8.1 ConfiguringLinear MSP

Required when linear MSP is configured for theoptical transmission line.The parameters need to be set according to theservice planning.

2 Configuring thecross-connections of theTDMservicea

A.9.1Creatingthe Cross-Connections ofPoint-to-PointServices

Required when the TDM service is a point-to-pointservice.The parameters need to be set according to theservice planning.



4-7


A.9.2CreatingCross-Connections ofSNCPServices

Required when the TDM service is an SNCP service.The parameters need to be set according to theservice planning.

3 A.9.3 Configuring theAutomatic Switchingof SNCP Services

Optional when the TDM service is an SNCP service.

4 Configuring theoverheadbytes

A.25.1ConfiguringRSOHs

Required when the J0_MM alarm is generated on thelocal or remote equipment.

A.25.2Configuring VC-4POHs

Required when the TIM or SLM alarm is generatedon the local or remote equipment.

A.25.3Configuring VC-12POHs

Required when the TIM or SLM alarm is generatedon the local or remote equipment.

5 A.23 Setting theParameters of SDHInterfaces

Optional.

6 A.24 Setting theParameters of PDHInterfaces

Optional.

7 A.9.10 Testing the E1Service ThroughPRBS

The test results should show that each E1 servicecontains no bit errors.

NOTE

a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure the TDM service on theworking channel only. In the case of N+1 protection configuration or 1:N linear MSP, you also need to configurethe extra services on the protection channel if required.

4.3 Configuration Example (TDM Services on a TDMMicrowave Chain Network)

This topic considers a TDM microwave chain network as an example to describe how toconfigure TDM services according to the network planning information.


Configuration Guide


Issue 02 (2009-10-30)





Based on 3.3 Configuration Example (Radio Links on the TDM Microwave ChainNetwork), configure the TDM services according to the service requirements, as shown inFigure 4-6. The relative service information about the chain network is as follows:

l To ensure the reliable transmission of the services between NE1 and the BSC, the linearMSP is configured for the optical transmission line.

l The TDM service is transferred between NE2 and NE3 through the STM-1 opticalinterfaces.

Figure 4-6 Networking diagram (TDM services on the TDM microwave chain network)

BSC

BTS5

BTS3

BTS2

NE1NE2NE3

NE5

NE4

NE6

8xE1

8xE1

8xE114xE1

BTS4

STM-1

BTS1

16xE1

STM-1


Timeslot Allocation DiagramFigure 4-7 shows the timeslots that are allocated for the TDM services according to the serviceplanning information.



4-9

Figure 4-7 Timeslot allocation diagram (TDM services on the TDM microwave chain network)

TimeslotNE2Station NE3 NE5NE1

Links-1: NE1 - NE2 - NE3 -NE5

3-IF1 3-IF1 8-SL1D-1

9-SP3S:1-8

VC4-1

Timeslot

Station NE4NE3

Links-2: NE3-NE4

VC12: 1-16VC4-1

8-SL1D-1

VC12: 1-8

BSC

8-SL1D-1 4-IF1

NE6

4-IF1 3-IF1 3-IF1

VC12: 9-229-SP3S:1-14VC12: 23-38

VC12: 39-54

9-SP3S:1-16

VC12: 23-38

3-IF1 3-IF1

8-SL1D-1

9-SP3S:1-16

Add/DropFow ard

Pass through

As shown in Figure 4-7, the information about the timeslots that the TDM services occupy oneach NE is as follows:

l E1 services on NE6:

– The E1 services are added to or dropped from the first to eighth ports on the SP3S boardin slot 9 of NE6.

– The E1 services occupy the first to eighth VC-12 timeslots on the link between the firstoptical interface on the SL1D board in slot 8 of NE1 and the IF1 board in slot 3 of NE6.


– The E1 services are added to or dropped from the first to fourteenth ports on the SP3Sboard in slot 9 of NE5.

– The E1 services occupy the ninth to twenty-second VC-12 timeslots on the link betweenthe first optical interface on the SL1D board in slot 8 of NE1 and the IF1 board in slot3 of NE5.


– The E1 services are added to or dropped from the first to sixteenth ports on the SP3Sboard in slot 9 of NE4.

– The E1 services occupy the twenty-third to thirty-eighth VC-12 timeslots on the linkbetween the first optical interface on the SL1D board in slot 8 of NE1 and the SL1Dboard in slot 8 of NE3.

– The E1 services occupy the first to sixteenth VC-12 timeslots on the link between theIF1 board in slot 3 of NE3 and the IF1 board in slot 3 of NE4.


– The E1 services are added to or dropped from the first to sixteenth ports on the SP3Sboard in slot 9 of NE2.

– The E1 services occupy the thirty-ninth to fifty-fourth VC-12 timeslots on the linkbetween the first optical interface on the SL1D board in slot 8 of NE1 and the IF1 boardin slot 3 of NE2.


Configuration Guide


Issue 02 (2009-10-30)

TIP

On the backhaul network for a mobile base station, the services are accessed from different nodes and thenaggregated to the same node for transmission. In this case, allocate the timeslots on the chain microwavenetwork as follows:

1. Select the chain that contains the maximum of hops as the main chain. Then, divide the chain networkinto several sub-chains by considering the main chain as the reference. Consider the E1 channels orfiber connections that are used for transferring services between NEs as links.

2. Allocate the timeslots for the add/drop or pass-through services on the NEs of the main chain one afteranother, in the descending order of the NE distance.

3. Repeat the previous step to configure the timeslots for the services on all the sub-chains.

This timeslot allocation method ensures that only the numbers of the timeslots that the services on the nodesof the aggregation sub-chain occupy may change.

TIP

The principles for obtaining the timeslot cross-connection configurations from the non-SNCP servicetimeslot allocation diagram are as follows:

l A straight line without any dot at either side represents a pass-through service. A straight line with onedot represents an add/drop service. A straight line with an arrow represents a transferred service. Thevertical line under the NE name is considered as the reference.

l If a straight line representing a pass-through service crosses the vertical line, it indicates that cross-connections are configured between the boards on both sides of the vertical line. The correspondingcross-connected timeslots are marked over the straight line.

l If there is a straight line with one dot on one side of the vertical line, it indicates that cross-connectionsare configured between the board on this side of the vertical line and the board under the straight linewith one dot. The corresponding cross-connected timeslots are marked over the straight line with onedot.

l If there is a straight line with an arrow on both sides of the vertical line, it indicates that cross-connections are configured between the two boards on both sides of the vertical line. The correspondingcross-connected timeslots on each board are marked over the straight line with an arrow on the side ofthis board.

Linear MSP

In this configuration example, no extra services need to be transmitted. Hence, the single-endednon-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE1and BSC. Table 4-2 provides the related planning information.

Table 4-2 Linear MSP

Parameter NE1

Protection Type 1+1 Linear MSP

Switching Mode Single-Ended Switching

Revertive Mode Non-Revertive

SD Enable Enabled (default value)

Protocol Type New Protocol (default value)

West Working Unit 8-SL1D-1

West Protection Unit 8-SL1D-2



4-11

NOTE

Unless otherwise specified, SD Enable and Switching Mode Indication take the default values.


Procedure

Step 1 See A.8.1 Configuring Linear MSP and configure 1+1 linear MSP.


Parameter Value

NE1




WTR Time(s) 600

SD Enable Enabled

Protocol Type New Protocol

Mapped Board l West Working Unit: 8-SL1D-1

l West Protection Unit: 8-SL1D-2

Step 2 See A.9.1 Creating the Cross-Connections of Point-to-Point Services and create the point-to-point service cross-connections.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

NE1

Level VC-12

Direction Bidirectional

Source Slot 8-SL1D-1

Source VC4 VC4-1

Source Timeslot Range(e.g.1,3-6) 1-54

Sink Slot 3-IF1-1

Sink VC4 VC4-1

Sink Timeslot Range(e.g.1,3-6) 1-54


Configuration Guide


Issue 02 (2009-10-30)

l The values for the related parameters of NE2 are provided as follows.

Parameter Value

NE2

Level VC-12 VC-12

Direction Bidirectional Bidirectional

Source Slot 3-IF1-1 3-IF1-1

Source VC4 VC4-1 VC4-1

Source Timeslot Range(e.g.1,3-6)

1-38 39-54

Sink Slot 8-SL1D-1 9-SP3S

Sink VC4 VC4-1 -

Sink Timeslot Range(e.g.1,3-6)

1-38 1-16


Parameter Value

NE3

Level VC-12 VC-12


Source Slot 8-SL1D-1 8-SL1D-1



1-22 23-38

Sink Slot 4-IF1-1 3-IF1-1

Sink VC4 VC4-1 VC4-1


1-22 1-16


Parameter Value

NE4

Level VC-12




4-13

Parameter Value

NE4

Source Slot 3-IF1-1

Source VC4 VC4-1


Sink Slot 9-SP3S

Sink VC4 -



Parameter Value

NE5

Level VC-12 VC-12


Source Slot 4-IF1-1 4-IF1-1



1-8 9-22

Sink Slot 3-IF1-1 9-SP3S

Sink VC4 VC4-1 -


1-8 1-14


Parameter Value

NE6

Level VC-12


Source Slot 3-IF1-1

Source VC4 VC4-1


Sink Slot 9-SP3S


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE6

Sink VC4 -


Step 3 See A.9.10 Testing the E1 Service Through PRBS and test the E1 services.Test two E1 services on each base station. The test results should show that the E1 servicescontain no bit errors.

----End

4.4 Configuration Example (TDM Services on a TDMMicrowave Ring Network)

This topic considers a TDM microwave ring network as an example to describe how to configureTDM services according to the network planning information.





Based on 3.4 Configuration Example (Radio Links on the TDM Microwave RingNetwork), configure the TDM services according to the service requirements, as shown inFigure 4-8. To ensure reliable transmission of the services between the BTS and BSC, SNCPis configured to protect the TDM services on the ring network.



4-15

Figure 4-8 Networking diagram (TDM services on the TDM microwave ring network)

BTS2

BTS1

NE1

NE3

NE2 NE4

BSC

BTS3

BTS4

16xE1

4xE1

4xE1

4xE1

4xE1


Timeslot Allocation Diagram

Figure 4-9 shows the timeslots that are allocated for the TDM services according to the serviceplanning information.

Figure 4-9 Timeslot allocation diagram (TDM service on the TDM microwave ring network)


4-IF1 3-IF1

VC4-1

VC12: 1-84-IF1 3-IF1

VC12: 9-12

9-SP3S:13-16

NE1

4-IF1 3-IF1 4-IF1 3-IF1

9-SP3S:13-16

9-SP3S:1-8 9-SP3S:1-8

9-SP3S:9-12VC12: 13-16

9-SP3S:1-8 9-SP3S:1-8

9-SP3S:9-129-SP3S:1-49-SP3S:1-4VC12: 13-16

VC12: 9-12

VC12: 1-8

9-SP3S:1-4 9-SP3S:1-4

Add/Drop (SNCP w orking path)Add/Drop (SNCP protection path)

Pass through (SNCP w orking path)Pass through (SNCP protection path)

As shown in Figure 4-9, the information about the timeslots that the TDM services occupy oneach NE is as follows:l E1 services on NE2:



Configuration Guide


Issue 02 (2009-10-30)


– The E1 services occupy the first to eighth VC-12 timeslots on the ring.

l E1 services on NE3:– The E1 services are added to or dropped from the first to fourth ports on the SP3S board

in slot 9 of NE3.– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S

board in slot 9 of NE1.– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.


in slot 9 of NE4.– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the

SP3S board in slot 9 of NE1.– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.

TIP

On a backhaul network for a mobile base station, the services are accessed from different nodes and thenaggregated to the same node for transmission. Hence, you can perform the following operations to allocatethe timeslots on the SNCP microwave ring network:

1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate the minimumVC-12 timeslot number to the service on the nearest NE. The number of the timeslot each serviceoccupies does not change on the ring network.


This timeslot allocation method ensures that only the timeslots that the services on the nodes of theaggregation sub-chain occupy change.

TIP

The principles for obtaining the timeslot cross-connection configurations from the SNCP service timeslotallocation diagram are as follows:



l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP cross-connections are configured between the board on this side of the vertical line and the board under thestraight line with one dot. The corresponding cross-connected timeslots are marked over the straightline with one dot.

SNCPTable 4-3 provides the information about SNCP.

Table 4-3 SNCP

Parameter NE1

Working Source See the timeslot allocation diagram.

Protection Source See the timeslot allocation diagram.



4-17

Parameter NE1

Revertive Mode Revertive

WTR Time 600s (default value)

Hold-Off Time 0 (default value)

Switching Condition Necessary conditions for an SNCP switching (defaultvalues)

NOTE

Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.


Procedure

Step 1 See A.9.2 Creating Cross-Connections of SNCP Services and configure the SNCP servicecross-connections.


Parameter Value

NE1


Level VC-12 VC-12

Hold-off Time(100ms) 0 0

Revertive Mode Revertive Revertive

WTR Time(s) 600 600

Source Slot 4-IF1-1 (working service)3-IF1-1 (protection service)

3-IF1-1 (working service)4-IF1-1 (protection service)

Source VC4 VC4-1 (working service)VC4-1 (protection service)

VC4-1 (working service)VC4-1 (protection service)


1-12 13-16

Sink Slot 9-SP3S 9-SP3S

Sink VC4 - -


1-12 13-16


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

NE2


Level VC-12

Hold-off Time(100ms) 0


WTR Time(s) 600




Sink Slot 9-SP3S

Sink VC4 -



Parameter Value

NE3


Level VC-12



WTR Time(s) 600




Sink Slot 9-SP3S

Sink VC4 -



4-19

Parameter Value

NE3



Parameter Value

NE4


Level VC-12



WTR Time(s) 600




Sink Slot 9-SP3S

Sink VC4 -


Step 2 See A.9.1 Creating the Cross-Connections of Point-to-Point Services and configure theservice cross-connections on NE2, NE3, and NE4.l The values for the related parameters of NE2 are provided as follows.

Parameter Value

NE2

Level VC-12


Source Slot 3-IF1-1

Source VC4 VC4-1


Sink Slot 4-IF1-1


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE2

Sink VC4 VC4-1



Parameter Value

NE3

Level VC-12


Source Slot 3-IF1-1

Source VC4 VC4-1

Source Timeslot Range(e.g.1,3-6) 1-8,13-16

Sink Slot 4-IF1-1

Sink VC4 VC4-1

Sink Timeslot Range(e.g.1,3-6) 1-8,13-16


Parameter Value

NE4

Level VC-12


Source Slot 3-IF1-1

Source VC4 1


Sink Slot 4-IF1-1

Sink VC4 VC4-1



----End



4-21

4.5 Configuration Example (TDM Services on a HybridMicrowave Chain Network)

This topic considers a Hybrid microwave chain network as an example to describe how toconfigure TDM services according to the network planning information.





Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure the TDM services on a hybrid microwave chain network according to theservice requirements, as shown in Figure 4-10. The service requirements are as follows:

l To ensure reliable transmission of the services between NE1 and the BSC, the linear MSPmust be configured for the optical transmission line.

l The services are transferred between NE2 and NE3 through E1 channels.

Figure 4-10 Networking diagram (TDM services on the Hybrid microwave chain network)

BSC

BTS5

BTS3

BTS2

NE1NE2NE3

NE5

NE4

NE6

2E1

4E1

4E14E1

BTS4

STM-1

BTS1

4E1

E1



Configuration Guide


Issue 02 (2009-10-30)



Figure 4-11 Timeslot allocation diagram (TDM services on the Hybrid chain microwavenetwork)


Links-1: NE1 - NE2 - NE3 -NE5

3-IFU2 3-IFU2 9-SP3D

9-SP3S:1-4

VC4-1

Timeslot

Station NE4NE3

Links-2: NE3-NE4

VC12: 1-6VC4-1

VC12: 1-4

BSC

4-IFU2

NE6

4-IFU2 3-IFU2 3-IFU2

VC12: 5-89-SP3S:1-4VC12: 9-14

VC12: 15-18

9-SP3S:1-6

VC12: 9-14

3-IFU2 3-IFU2

9-SP3D:15-18

9-SP3S

9-SP3S

8-SL1D

Add/DropFow ard

Pass through

As shown in Figure 4-11, the information about the timeslots that the TDM services occupy oneach NE is as follows:l E1 services of NE6:

– The E1 services are added to or dropped from the first to fourth ports on the SP3S boardin slot 9 of NE6.

– The E1 services occupy the first to fourth VC-12 timeslots on the link between the firstoptical interface on the SL1D board in slot 8 of NE1 and the IFU2 board in slot 3 ofNE6.


in slot 9 of NE5.– The E1 services occupy the fifth to eighth VC-12 timeslots on the link between the first

optical interface on the SL1D board in slot 8 of NE1 and the IFU2 board in slot 4 ofNE5.

l E1 services on NE4:– The E1 services are added to or dropped from the first to sixth ports on the SP3S board

in slot 9 of NE4.– The E1 services occupy the ninth to fourteenth VC-12 timeslots on the link between the

first optical interface on the SL1D board in slot 8 of NE1 and the SP3S board in slot9 of NE3.

– The E1 services occupy the first to sixth VC-12 timeslots on the link between the IFU2board in slot 3 of NE3 and the IFU2 board in slot 3 of NE4.



4-23

l E1 services on NE2:– The E1 services are added to or dropped from the fifteenth to eighteenth ports on the

SP3S board in slot 9 of NE2.– The E1 services occupy the fifteenth to eighteenth VC-12 timeslots on the link between

the first optical interface on the SL1D board in slot 8 of NE1 to the IFU2 board in slot3 of NE2.

TIP

On the backhaul network for a mobile base station, the services are accessed from different nodes and thenaggregated to the same node for transmission. In this case, allocate the timeslots on the chain microwavenetwork as follows:

1. Select the chain that contains the maximum of hops as the main chain. Then, divide the chain networkinto several sub-chains by considering the main chain as the reference. Consider the E1 channels orfiber connections that are used for transferring services between NEs as links.

2. Allocate the timeslots for the add/drop or pass-through services on the NEs of the main chain one afteranother, in the descending order of the NE distance.


This timeslot allocation method ensures that only the numbers of the timeslots that the services on the nodesof the aggregation sub-chain occupy may change.

TIP

The principles for obtaining the timeslot cross-connection configurations from the non-SNCP servicetimeslot allocation diagram are as follows:



l If there is a straight line with one dot on one side of the vertical line, it indicates that cross-connectionsare configured between the board on this side of the vertical line and the board under the straight linewith one dot. The corresponding cross-connected timeslots are marked over the straight line with onedot.

l If there is a straight line with an arrow on both sides of the vertical line, it indicates that cross-connections are configured between the two boards on both sides of the vertical line. The correspondingcross-connected timeslots on each board are marked over the straight line with an arrow on the side ofthis board.

Linear MSPIn this configuration example, no extra services need to be transmitted. Hence, the single-endednon-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE1and BSC. Table 4-4 provides the related planning information.

Table 4-4 Linear MSP

Parameter NE1




SD Enable Enabled (default value)


Configuration Guide


Issue 02 (2009-10-30)

Parameter NE1

West Working Unit 8-SL1D-1

West Protection Unit 8-SL1D-2

NOTE

Unless otherwise specified, SD Enable and Protocol Type take the default values.


Procedure

Step 1 See A.8.1 Configuring Linear MSP and configure the linear MSP.


Parameter Value

NE1




WTR Time(s) 600

SD Enable Enabled

Protocol Type New Protocol

Mapped Board l West Working Unit: 8-SL1D-1

l West Protection Unit: 8-SL1D-2

Step 2 See A.9.1 Creating the Cross-Connections of Point-to-Point Services and create point-to-point service cross-connections.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

NE1

Level VC-12


Source Slot 8-SL1D-1

Source VC4 VC4-1



4-25

Parameter Value

NE1


Sink Slot 3-IFU2-1

Sink VC4 VC4-1



Parameter Value

NE2

Level VC-12


Source Slot 3-IFU2-1

Source VC4 VC4-1


Sink Slot 9-SP3D

Sink VC4 -



Parameter Value

NE3

Level VC-12 VC-12


Source Slot 9-SP3S 9-SP3S

Source VC4 - -


1-8 9-14

Sink Slot 4-IFU2-1 3-IFU2-1

Sink VC4 VC4-1 VC4-1


1-8 1-6


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

NE4

Level VC-12



Source VC4 VC4-1


Sink Slot 9-SP3S

Sink VC4 -



Parameter Value

NE5

Level VC-12 VC-12


Source Slot 4-IFU2-1 4-IFU2-1



1-4 5-8

Sink Slot 3-IFU2-1 9-SP3S

Sink VC4 VC4-1 -


1-4 1-4


Parameter Value

NE6

Level VC-12



Source VC4 VC4-1



4-27

Parameter Value

NE6


Sink Slot 9-SP3S

Sink VC4 -



----End

4.6 Configuration Example (TDM Services on a HybridMicrowave Ring Network)

This topic considers a Hybrid microwave ring network as an example to describe how toconfigure TDM services according to the network planning information.





Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure the TDM services on a Hybrid microwave ring network according to theservice requirements, as shown in Figure 4-12. To ensure the reliable transmission of theservices between NE1 and the BSC, the linear MSP must be configured.


Configuration Guide


Issue 02 (2009-10-30)

Figure 4-12 Networking diagram (TDM services on the Hybrid microwave ring network)

BTS2

BTS1

NE1

NE3

NE2 NE4

BSC

BTS3

BTS4

16xE1

4xE1

4xE1

4xE1

4xE1




Figure 4-13 Timeslot allocation diagram (TDM services on the Hybrid microwave ring network)


4-IFU2 3-IFU2

VC4-1

VC12: 1-84-IFU2 3-IFU2

VC12: 9-12

9-SP3S:13-16

NE1

4-IFU2 3-IFU2 4-IFU2 3-IFU2

9-SP3S:13-16

9-SP3S:1-8 9-SP3S:1-8

9-SP3S:9-12VC12: 13-16

9-SP3S:1-8 9-SP3S:1-8

9-SP3S:9-129-SP3S:1-49-SP3S:1-4VC12: 13-16

VC12: 9-12

VC12: 1-8

9-SP3S:1-4 9-SP3S:1-4

Add/Drop (SNCP w orking path)Add/Drop (SNCP protection path)

Pass through (SNCP w orking path)Pass through (SNCP protection path)

As shown in Figure 4-13, the information about the timeslots that the TDM services occupy oneach NE is as follows:





4-29


– The E1 services occupy the first to eighth VC-12 timeslots on the ring.


in slot 9 of NE3.– The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S

board in slot 9 of NE1.– The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.


in slot 9 of NE4.– The E1 services are added to or dropped from the thirteenth to sixteenth ports on the

SP3S board in slot 9 of NE1.– The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.

TIP

On a backhaul network for a mobile base station, the services are accessed from different nodes and thenaggregated to the same node for transmission. Hence, you can perform the following operations to allocatethe timeslots on the SNCP microwave ring network:

1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate the minimumVC-12 timeslot number to the service on the nearest NE. The number of the timeslot each serviceoccupies does not change on the ring network.


This timeslot allocation method ensures that only the timeslots that the services on the nodes of theaggregation sub-chain occupy change.

TIP

The principles for obtaining the timeslot cross-connection configurations from the SNCP service timeslotallocation diagram are as follows:



l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP cross-connections are configured between the board on this side of the vertical line and the board under thestraight line with one dot. The corresponding cross-connected timeslots are marked over the straightline with one dot.

SNCPTable 4-5 provides the information about SNCP.

Table 4-5 SNCP

Parameter NE1

Working Source See the timeslot allocation diagram.

Protection Source See the timeslot allocation diagram.


Configuration Guide


Issue 02 (2009-10-30)

Parameter NE1


WTR Time 600s (default value)

Hold-Off Time 0 (default value)

Switching Condition Necessary conditions for an SNCP switching (defaultvalues)

NOTE

Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.


Procedure

Step 1 See A.9.2 Creating Cross-Connections of SNCP Services and configure the SNCP servicecross-connections.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

NE1


Level VC-12 VC-12

Hold-off Time(100ms) 0 0

Revertive Mode Revertive Revertive

WTR Time(s) 600 600

Source Slot 3-IFU2-1 (working service)4-IFU2-1 (protectionservice)

4-IFU2-1 (working service)3-IFU2-1 (protectionservice)


VC4-1 (working service)VC4-1 (protection service)


1-12 13-16

Sink Slot 9-SP3S 9-SP3S

Sink VC4 - -


1-12 13-16



4-31


Parameter Value

NE2


Level VC-12



WTR Time(s) 600

Source Slot 3-IFU2-1 (working service)4-IFU2-1 (protection service)



Sink Slot 9-SP3S

Sink VC4 -



Parameter Value

NE3


Level VC-12



WTR Time(s) 600




Sink Slot 9-SP3S

Sink VC4 -


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE3



Parameter Value

NE4


Level VC-12



WTR Time(s) 600




Sink Slot 9-SP3S

Sink VC4 -


Step 2 See A.9.1 Creating the Cross-Connections of Point-to-Point Services and configure theservice cross-connections on NE2, NE3, and NE4.l The values for the related parameters of NE2 are provided as follows.

Parameter Value

NE2

Level VC-12



Source VC4 VC4-1


Sink Slot 4-IFU2-1



4-33

Parameter Value

NE2

Sink VC4 VC4-1



Parameter Value

NE3

Level VC-12



Source VC4 VC4-1

Source Timeslot Range(e.g.1,3-6) 1-8,13-16

Sink Slot 4-IFU2-1

Sink VC4 VC4-1

Sink Timeslot Range(e.g.1,3-6) 1-8,13-16


Parameter Value

NE4

Level VC-12



Source VC4 1


Sink Slot 4-IFU2-1

Sink VC4 VC4-1


Step 3 See A.9.10 Testing the E1 Service Through PRBS and test the E1 services.


Configuration Guide


Issue 02 (2009-10-30)

Test two E1 services on each base station. The test results should show that the E1 servicescontain no bit errors.

----End



4-35

5 Configuring Ethernet Services

About This Chapter

Ethernet services are classified into E-Line services and E-LAN services.

5.1 Basic ConceptsBefore configuring the Ethernet services, you need to be familiar with the basic concepts.

5.2 Configuration Procedure (E-Line Services)The configuration procedure varies according to the type of the E-Line services.

5.3 Configuration Procedure (E-LAN Services)The configuration procedure varies according to the type of the E-LAN services.

5.4 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)This topic considers a point-to-point transparently transmitted E-Line service as an example todescribe how to configure the Ethernet service according to the network planning information.

5.5 Configuration Example (VLAN-Based E-Line Service)This topic considers a VLAN-based E-line service as an example to describe how to configurethe Ethernet service according to the network planning information.

5.6 Configuration Example (QinQ-Based E-Line Service)This topic considers a QinQ-based E-line service as an example to describe how to configurethe Ethernet service according to the network planning information.

5.7 Configuration Example (802.1d-Bridge-Based E-LAN Service)This topic considers an 802.1d-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.

5.8 Configuration Example (802.1q-Bridge-Based E-LAN Service)This topic considers an 802.1q-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.

5.9 Configuration Example (802.1ad-Bridge-Based E-LAN Service)This topic considers an 802.1ad-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.

5.10 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)

OptiX RTN 910Configuration Guide 5 Configuring Ethernet Services


5-1

This topic describes how to configure a radio network that transmit E-Line services and E-LANservices at the same time according to the network planning information.

5 Configuring Ethernet ServicesOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

5.1 Basic ConceptsBefore configuring the Ethernet services, you need to be familiar with the basic concepts.

5.1.1 IF_ETH PortWhen Ethernet services need to be transmitted over Hybrid microwave, you need to configurethe Ethernet services between the FE/GE port on the Ethernet interface board and the IF_ETHport on the Hybrid IF board.

5.1.2 Auto-NegotiationThe auto-negotiation function allows the network equipment to send information of its supportedworking mode to the opposite end on the network and to receive the corresponding informationthat the opposite end may transfer.

5.1.3 Flow Control FunctionWhen the equipment fails to handle the flow received at the port due to poor data processing/transferring capability, congestion occurs on the line. To reduce the number of discarded packetscaused by buffer overflow, proper flow control measures must be taken.

5.1.4 VLANAccording to specific rules, a real network topology can be divided into several logicalsubnetworks, which are referred to as VLANs. The broadcast packets of a VLAN can betransmitted only within this VLAN. That is, one VLAN corresponds to a specific broadcastdomain.

5.1.5 QinQQinQ is a Layer 2 tunnel protocol based on IEEE 802.1q. The QinQ technology encapsulatescustomer VLAN tags into supplier VLAN tags. Hence, QinQ frames traverse the backbonenetwork of the network supplier when carrying two layers of VLAN tags. In this manner, twoVPN tunnels are provided for user services. The inner VLAN tag is called the CVLAN tag,representing the customer VLAN tag. The outer VLAN tag is called SVLAN tag, representingthe service provider VLAN tag.

5.1.6 E-Line ServicesE-Line services refer to the fixed transmission of point-to-point Ethernet services. E-Lineservices include EPL and EVPL services defined in ITU-T.

5.1.7 E-LAN ServicesE-LAN services refer to the dynamic point-to-multipoint transmission of Ethernet services basedon MAC addresses. E-LAN services include EPLAN and EVPLAN services defined in ITU-T.

5.1.8 Managment of the MAC Address TableThe OptiX RTN 910 supports setting the static MAC address entries, blacklist, and the agingparameters of the MAC address table manually.

5.1.9 Protection for Ethernet ServicesThe OptiX RTN 910 supports three protection modes for Ethernet services, namely, Ethernetring protection switching (ERPS), link aggregation (LAG), and multiple spanning tree protocol(MSTP).

5.1.10 QoSThe quality of service (QoS) refers to the ability of a communication network to ensure theexpected service quality in the aspects of the bandwidth, delay, delay jitter, and packet loss ratio,and thus to ensure that the request and response from the user or the request and response fromthe application meet the requirements of an expected service class. The OptiX RTN 910 supports



5-3

the following QoS functions, namely, differentiated service (DiffServ), flow classification,CAR, traffic shaping, and queue scheduling.

5.1.1 IF_ETH PortWhen Ethernet services need to be transmitted over Hybrid microwave, you need to configurethe Ethernet services between the FE/GE port on the Ethernet interface board and the IF_ETHport on the Hybrid IF board.

The IF_ETH port is an internal Ethernet port on the Hybrid IF board. In the transmit directionof Hybrid microwave, the Ethernet services transmitted to the MUX/DEMUX unit of the HybridIF board through the IF_ETH port and are then mapped into the Hybrid microwave frames. Inthe receive direction of Hybrid microwave, the Ethernet services are demapped from the Hybridmicrowave frames and then transmitted to the packet switching unit through the IF_ETH port.

The main differences between the IF_ETH port and the GE/FE port are as follows:

l The IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames anddoes not have PHY-layer functions.

l The bandwidth over the IF_ETH port is equal to the Ethernet service bandwidth that theHybrid microwave supports. Hence, when the AM function is enabled in the case of Hybridmicrowave, the bandwidth over the IF_ETH port changes according to the modulationmode.

5.1.2 Auto-NegotiationThe auto-negotiation function allows the network equipment to send information of its supportedworking mode to the opposite end on the network and to receive the corresponding informationthat the opposite end may transfer.

Auto-Negotiation Function of FE Electrical PortsIn the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10Mfull-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of the local FEelectrical port does not match the working mode of the opposite FE electrical port, the two portscannot communicate with each other. With the auto-negotiation function, however, the two portscan communicate with each other. The auto-negotiation function uses fast link pulses and normallink pulses to transfer the negotiation information of the working mode so that the working modeof the local FE electrical port matches the working mode of the opposite FE electrical port.

Table 5-1 lists the FE auto-negotiation rules.

Table 5-1 Auto-negotiation rules of FE electrical ports (when the local FE electrical port adoptsthe auto-negotiation mode)

Working Mode of the Opposite FEElectrical Port

Auto-Negotiation Result

Auto-negotiation 100M full-duplex

10M half-duplex 10M half-duplex

10M full-duplex 10M half-duplex



Configuration Guide


Issue 02 (2009-10-30)

Working Mode of the Opposite FEElectrical Port



NOTE

As provided in Table 5-1, when the working mode of the opposite FE electrical port is 10M full-duplex or 100Mfull-duplex, the auto-negotiation result cannot realize the matching between the working modes of the FEelectrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of the oppositeFE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of the local FEelectrical port to 10M full-duplex or 100M full-duplex.

When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at bothends can negotiate the flow control function through the auto-negotiation function.

Auto-Negotiation Function of GE Electrical PortsIn the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M full-duplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiationfunction of GE electrical ports is similar to the auto-negotiation function of FE electrical ports.Table 5-2 lists the auto-negotiation rules of GE electrical ports.

Table 5-2 Auto-negotiation rules of GE electrical ports (when the local GE electrical port adoptsthe auto-negotiation mode)

Working Mode of the Opposite GEElectrical Port


Auto-negotiation (GE electrical port) 1000M full-duplex

Auto-negotiation (FE electrical port) 100M full-duplex





1000M full-duplex 1000M full-duplex

NOTE

As provided in Table 5-2, when the working mode of the opposite GE electrical port is 10M full-duplex or100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of theGE electrical ports at both ends. As a result, certain packets are lost. Hence, when the working mode of theopposite GE electrical port is 10M full-duplex or 100M full-duplex, you need to set the working mode of thelocal GE electrical port to 10M full-duplex or 100M full-duplex.

When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at bothends can negotiate the flow control function through the auto-negotiation function.



5-5

Auto-Negotiation Function of GE Optical Ports

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

5.1.3 Flow Control FunctionWhen the equipment fails to handle the flow received at the port due to poor data processing/transferring capability, congestion occurs on the line. To reduce the number of discarded packetscaused by buffer overflow, proper flow control measures must be taken.

The half-duplex Ethernet port applies the back-pressure mechanism to control the flow. The full-duplex Ethernet port applies PAUSE frames to control the flow. Currently, the half-duplexEthernet function is not widely applied. Hence, the flow control function realized by Ethernetservice boards is used for the full-duplex Ethernet ports.

The flow control function realized by Ethernet service boards is classified into two types: auto-negotiation flow control and non-auto-negotiation flow control.

Auto-Negotiation Flow Control

When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiationflow control function. The auto-negotiation flow control modes include the following:

l Asymmetric PAUSE toward the link partnerThe port can transmit PAUSE frames in the case of congestion but cannot process thereceived PAUSE frames.

l Symmetric PAUSEThe port can transmit PAUSE frames and process the received PAUSE frames.

l Both asymmetric and symmetric PAUSEThe port has the following capabilities:– Transmits and processes PAUSE frames.

– Transmits PAUSE frames but cannot process the received PAUSE frames.

– Processes the received PAUSE frames but cannot transmit PAUSE frames.

l DisabledThe port does not transmit or process PAUSE frames.

NOTE

The OptiX RTN 910 supports only two auto-negotiation flow control modes, namely, disabled mode andsymmetric PAUSE mode.

Non-Auto-Negotiation Flow Control

When the Ethernet port works in a fixed working mode, you can adopt the non-auto-negotiationflow control function. The non-auto-negotiation flow control modes include the following:

l Send onlyThe port can transmit PAUSE frames in the case of congestion but cannot process thereceived PAUSE frames.

l Receive only


Configuration Guide


Issue 02 (2009-10-30)

The port can process the received PAUSE frames but cannot transmit PAUSE frames inthe case of congestion.

l Symmetric

The port can transmit PAUSE frames and can also process received PAUSE frames.

l Disabled

The port does not transmit or process PAUSE frames.

NOTE

The OptiX RTN 910 supports only two non-auto-negotiation flow control modes, namely, disabled mode andsymmetric mode.

5.1.4 VLANAccording to specific rules, a real network topology can be divided into several logicalsubnetworks, which are referred to as VLANs. The broadcast packets of a VLAN can betransmitted only within this VLAN. That is, one VLAN corresponds to a specific broadcastdomain.

Frame Format

To realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLANinformation, namely, the tagged frame. The tagged frame is also called the 802.1q frame.Compared with the common Ethernet frame, this type of frame is added with a 4-byte 802.1qheader. See Figure 5-1.

Figure 5-1 Tagged frame format

Destinationaddress

Sourceaddress

802.1qheader Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

CFIPCPTPID

1 bit3 bits16 bits

TCI

The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag controlinformation (TCI). The TCI is divided into three parts: user_priority, canonical format indicator(CFI), and VLAN identifier (VID).

l TPID

The TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The valueis always 0x8100. When the network equipment that cannot identify the tagged framereceives the tagged frame, the equipment discards this frame.

l PCP

The priority code point (PCP) identifies the priority of an Ethernet frame. This field can beused to provide the requirement for the service quality.

l CFI



5-7

The CFI is a 1-bit filed, and it is used in certain physical networks that adopt the ringtopology. This field is not processed in the Ethernet.

l VIDThe VLAN ID is a 12-bit field, and it indicates the VLAN to which the frame belongs.

Tag AttributesWhen data frames enter or exit a port on an Ethernet board, the processing mode of the dataframes is determined by the tag attributes of this port. The tags for ports on Ethernet boards areavailable in three types: tag aware, access, and hybrid. Table 5-3 provides the processing modeof data frames at ports with different VLAN tags.

Table 5-3 Processing mode of data frames at ports with different VLAN tags

Direction Type of DataFrame

Processing Mode

Tag Aware Access Hybrid

Ingress port Tagged frame Receives theframe.

Discards theframe.

Receives theframe.

Untagged frame Discards theframe.

Receives theframe after theuntagged frameis added with theport VID(PVID).

Receives theframe after theuntagged frameis added with thePVID.

Egress port Tagged frame Transmits theframe.

Transmits theframe after theVID of thetagged frame isstripped.

Transmits theframe after thePVID of thetagged frame isstripped if theVID equals thePVID.Directlytransmits theframe if the VIDdoes not equalthe PVID.

NOTE

The untagged frame cannot be transmitted through the port.

In the case of OptiX RTN 910, the VLAN tag is closely related to Encapsulation Type.

l When Encapsulation Type is set to Null or QinQ, the VLAN tag is invalid.

l When Encapsulation Type is set to 802.1Q, the VLAN tag can be set to Tag Aware,Access, or Hybrid.


Configuration Guide


Issue 02 (2009-10-30)

5.1.5 QinQQinQ is a Layer 2 tunnel protocol based on IEEE 802.1q. The QinQ technology encapsulatescustomer VLAN tags into supplier VLAN tags. Hence, QinQ frames traverse the backbonenetwork of the network supplier when carrying two layers of VLAN tags. In this manner, twoVPN tunnels are provided for user services. The inner VLAN tag is called the CVLAN tag,representing the customer VLAN tag. The outer VLAN tag is called SVLAN tag, representingthe service provider VLAN tag.

Frame Format

The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a C-TAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG.

l Ethernet frame with only a C-TAGThe Ethernet frame with only a C-TAG has the same format as the tagged frame definedin IEEE 802.1Q. Hence, the tagged frame defined in IEEE 802.1Q is an Ethernet framethat contains a C-VLAN tag.

l Format of the Ethernet frame with a C-TAG and an S-TAGIn the case of an Ethernet frame that contains a C-TAG and an S-TAG, the S-TAG is addedbefore the C-TAG. The differences between the S-TAG and the C-TAG are as follows:– The TPID is different.

As defined in IEEE 802.1ad, the value of the TPID in the S-TAG is 0x88a8, whereasthe value of the TPID in the C-TAG is 0x8100.

NOTE

The default TPID in the S-TAG is also 0x88a8. The TPID in the S-TAG can be set by using the NMS.

– The drop eligible indicator (DEI) replaces the CFI.The DEI works with the PCP to indicate the priority of the S-TAG.

NOTE

The equipment does not support the processing of the DEI.

Figure 5-2 Format of the Ethernet frame with a C-TAG and an S-TAG

Destinationaddress

Sourceaddress S-TAG Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

DEIPCPTPID

1 bit3 bits16 bits

TCI

C-TAG

l Format of the Ethernet frame with only an S-TAG

The Ethernet frame with only an S-TAG contains only an S-TAG and does not contain aC-TAG. See Figure 5-2.



5-9

Figure 5-3 Format of the Ethernet frame with only an S-TAG

Destinationaddress

Sourceaddress S-TAG Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

DEIPCPTPID

1 bit3 bits16 bits

TCI

Network Attributes

The network attribute of each port can be set to UNI and NNI depending on how the portprocesses the C-TAG and S-TAG.

l UNI

By default, the UNI considers that the received frames do not carry any S-TAG. Accordingto Encapsulation Type of Ethernet ports, the UNI is classified into two types:

– Ports whose Encapsulation Type is Null

This port does not check the VLAN tags. Hence, all types of Ethernet frames can enterthis port. This port supports the creation of PORT-based QinQ services and does notsupport the creation of PORT+CVLAN-based QinQ services.

– Ports whose Encapsulation Type is 802.1Q

In the case of QinQ services, when Encapsulation Type is 802.1Q, Tag must be set toTag Aware. In this case, the port checks the outer VLAN tag that the Ethernet framescarry, and processes the outer VLAN tag as the C-VLAN tag. Hence, untagged framescannot enter this port. This port supports the creation of both PORT-based QinQ servicesand PORT+CVLAN-based QinQ services.

l NNI

By default, the NNI considers that the received frames carry the S-TAG. WhenEncapsulation Type is QinQ, the Ethernet port is an NNI. Only the NNI can be used toconfigure the QinQ link.

5.1.6 E-Line ServicesE-Line services refer to the fixed transmission of point-to-point Ethernet services. E-Lineservices include EPL and EVPL services defined in ITU-T.

Service Model

E-Line services are classified into point-to-point transparently transmitted E-Line services,VLAN-based E-Line services, and QinQ-based E-Line services. Table 5-4 describes the E-Lineservice models.


Configuration Guide


Issue 02 (2009-10-30)

Table 5-4 E-Line Service Model

Service Type EncapsulationType

Service Direction Traffic Flow Description

Point-to-pointtransparentlytransmitted E-Lineservice

Null (source)Null (sink)

UNI-UNI PORT (source)PORT (sink)

The source porttransparentlytransmits all thereceived Ethernetframes to the sinkport.

VLAN-based E-Line service

802.1Q (source)802.1Q (sink)

UNI-UNI PORT (source)PORT (sink)

The source portprocesses thereceived Ethernetframes according tothe tag attributes ofthe Ethernet framesand then transmitsthe Ethernet framesto the sink port. Thesink port processesthe receivedEthernet framesaccording to the tagattributes of theEthernet frames andthen sends theEthernet frames out.

PORT+VLAN(source)PORT+VLAN(sink)

The source portprocesses thereceived Ethernetframes according tothe tag attributes ofthe Ethernet framesand then transmitsthe Ethernet framesthat carry thespecific VLAN tagto the sink port. Thesink port processesthe receivedEthernet framesaccording to the tagattributes of theEthernet frames andthen sends theEthernet frames out.



5-11



QinQ-based E-Lineservice

Null (source)QinQ (sink)

UNI-NNI PORT (source)QinQ link (sink)

The source port addsthe SVLAN tag thatcorresponds to theQinQ link into all theEthernet frames andthen transmits theEthernet frames tothe sink port wherethe QinQ linkconfigured.

802.1Q (source)a

QinQ (sink)

UNI-NNI PORT (source)QinQ link (sink)

The source portaccesses only theEthernet frames thatcarry VLAN tags. Itadds the SVLAN tagthat corresponds tothe QinQ link into allthe Ethernet framesand then transmitsthe Ethernet framesto the sink portwhere the QinQ linkconfigured.

PORT+CVLAN(source)QinQ link (sink)

The source port addsthe SVLAN tag thatcorresponds to theQinQ link into all theEthernet frames thatcarry the specificCVLAN tag andthen transmits theEthernet frames tothe sink port wherethe QinQ linkconfigured.


Configuration Guide


Issue 02 (2009-10-30)



QinQ (source)QinQ (sink)

NNI-NNI QinQ link (source)QinQ link (sink)

The source porttransmits theEthernet frames thatcarry the SVLANtags that correspondto the source QinQlink to the sink portwhere the sink QinQlink is configured. Ifthe source and sinkQinQ linkscorrespond todifferent SVLANtags, the SVLANtags carried in theEthernet frames areexchanged.

NOTE

a: TAG must be set to Tag Aware.

VLAN Forwarding Table

In the case of VLAN-based E-Line service models, the same VLAN tag generally needs to beconfigured for the source and sink. That is, the VLAN tag carried in the frames transmitted fromthe source should be the same as the VLAN tag carried in the frames received at the sink. If theframes need to carry different VLAN tags at the source and sink, you need to configure theVLAN forwarding table except in the case of an E-Line service wherein different VLAN tagsare configured for the service source and sink. After the VLAN forwarding table is configured,the VLAN tags of the service source and sink are switched.

5.1.7 E-LAN ServicesE-LAN services refer to the dynamic point-to-multipoint transmission of Ethernet services basedon MAC addresses. E-LAN services include EPLAN and EVPLAN services defined in ITU-T.

Bridge

The bridge is the core to realizing an E-LAN service. The bridge uses the self learning functionto establish the corresponding relation between an Ethernet port and the source MAC addresscontained in the Ethernet frames that enter the bridge through the Ethernet port. Thiscorresponding relation is one entry in the MAC address table. The bridge supports the followingself learning modes:

l Shared VLAN learning (SVL)When the bridge uses the SVL mode, it creates an entry according to the source MACaddress and the source port of a packet. This entry is valid to all VLAN tags.



5-13

l Independent VLAN learning (IVL)When the bridge uses the IVL mode, it creates an entry according to the source MACaddress, VLAN ID, and source port of a packet. This entry is valid to only this VLAN tag.

After receiving an Ethernet frame, the bridge processes the Ethernet frame as follows:

l If the bridge uses the SVL self learning mode, it searches the MAC address table accordingto the sink MAC address of the Ethernet frame. If the bridge uses the IVL self learningmode, it searches the MAC address table according to the VLAN tag and sink MAC addresscarried in the Ethernet frame.

l If the MAC address table contains the corresponding entry, the bridge forwards the Ethernetframe to the Ethernet port as specified in the entry. If the MAC address table does notcontain the corresponding entry, the bridge broadcasts the Ethernet frame in the broadcastdomain.

l The bridge adds or updates the entry to the MAC address table according to the sourceMAC address contained in the Ethernet frame.

The bridge is available in three types, namely, 802.1d bridge, 802.1q bridge, and 802.1ad bridge.The switching domain of the bridge can be divided into several independent sub switchingdomains in different domain switching modes. To process the services over the bridge incentralized mode, the concept of logical port is introduced in the OptiX RTN 910. The OptiXRTN 910 considers all the ports mounted to the bridge are logical ports, each of which exists inonly one sub switching domain. The logical port may be based on PORT, PORT+VLAN, PORT+CVLAN, or PORT+SVLAN. That is, a physical port can be mapped into several logical ports,which can be in the same sub switching domain or in different sub switching domains.

Table 5-5 describes the differences between the bridge types.

Table 5-5 Bridge Type

Item 802.1d Bridge 802.1q Bridge IEEE 802.1adBridge

Type of logical port PORT PORT+VLAN PORT or PORT+CVLAN (UNI)a

PORT+SVLAN(NNI)

Learning mode SVL IVL IVL

Broadcast domain Entire bridge All the logical portswhose VLAN tag isthe same as theVLAN tag carried inthe Ethernet frame

All the logical portswhose SVLAN tag isthe same as theSVLAN tag carriedin the Ethernet frame

Sub switchingdomain

Figure 5-4 shows thebridge whoseswitching domain isnot divided.

Figure 5-5 shows thebridge whoseswitching domain isdivided into severalsub switchingdomains according tothe VLAN tag.

Figure 5-6 shows thebridge whoseswitching domain isdivided into severalsub switchingdomains according tothe SVLAN tag.


Configuration Guide


Issue 02 (2009-10-30)

NOTE

a: When an Ethernet frame enters the 802.1ad bridge through a logical port whose network attribute is UNI, thespecific SVLAN tag is added to the Ethernet frame. When an Ethernet frame exits the 802.1ad bridge througha logical port whose network attribute is UNI, the specific SVLAN tag is stripped from the Ethernet frame.

Figure 5-4 802.1d Bridge

LP1

LP2

LP3

802.1d bridge

LP4LP5

LP6LP7

LP8LP9

LP: Logic Port

SVL

Figure 5-5 802.1q Bridge

LP1

LP2

LP3

VLAN1

VLAN2

VLAN3

802.1q bridge

LP4LP5

LP6LP7

LP8LP9

LP: Logic Port

IVL

Figure 5-6 802.1ad Bridge

LP1

LP2

LP3

S-VLAN1

S-VLAN2

S-VLAN3

802.1ad bridge

LP4LP5

LP6LP7

LP8LP9

LP: Logic Port

IVL



5-15

Service ModelAccording to the corresponding bridge types, E-LAN services can be classified into the IEEE802.1d bridge-based E-LAN services, IEEE 802.1q bridge-based E-LAN services, and IEEE802.1ad bridge-based E-LAN services. Table 5-6 describes the E-LAN service models.

Table 5-6 E-LAN service model

Item IEEE 802.1dBridge-Based E-LAN Service

IEEE 802.1qBridge-Based E-LAN Service

IEEE 802.1adBridge-Based E-LAN Service

Tag type Tag-Transparent C-Awared S-Awared

Encapsulation type Null Null or 802.1Q Null or 802.1Q(UNI)a

QinQ (NNI)

Type of logical port PORT PORT+VLAN PORT(EncapsulationType of the UNI isNull.)PORT or PORT+CVLAN(EncapsulationType of the UNI is802.1Q.) a

PORT+SVLAN(NNI)

Learning mode SVL IVL IVL

Sub switchingdomain

The switchingdomain of the bridgeis not divided.

The switchingdomain of the bridgeis divided accordingto the VLAN tag.

The switchingdomain of the bridgeis divided accordingto the SVLAN tag.

NOTE

a: When Encapsulation Type of the port is 802.1Q, Tag must be set to Tag Aware.

Split Horizon GroupTo isolate services and to prevent broadcast storms due to a service loop, you can configure theE-LAN services on specific nodes in the same split horizon group. The logical ports that areassigned in the same split horizon group cannot forward frames to each other. Figure 5-7provides an example wherein the split horizon group is configured. E-LAN services areconfigured on each NE on the network. The west and east IF_ETH ports and service access portsare configured as bridge-mounted ports. In this example, the IF_ETH ports can forward framesto each other. Hence, if no split horizon group is configured on NE1, a network loop is generatedand results in a broadcast storm. If a split horizon group is configured on NE1 and the west andeast IF_ETH ports are configured as the split horizon group members, frames are not forwardedbetween the west and east IF_ETH ports on NE1. In this case, no service loop is generated.


Configuration Guide


Issue 02 (2009-10-30)

Figure 5-7 Split horizon group

BTS

BTS

NE1

NE3

NE2 NE4

BSC

BTS

BTS

Split horizon group

NOTE

l When the ERPS protection is enabled for the ring network, the ERPS protocol ensures that no service loopis generated. If the split horizon group is configured in this case, it affects the ERPS protection.

l The OptiX RTN 910 supports only the split horizon group that is configured according the physical ports.Hence, if one of the logical ports that correspond to a physical port is configured as a member of a splithorizon group, the other logical ports are automatically added to the split horizon group.

5.1.8 Managment of the MAC Address TableThe OptiX RTN 910 supports setting the static MAC address entries, blacklist, and the agingparameters of the MAC address table manually.

Entries of a MAC address table provide the mapping relations between MAC addresses andports. The entries can be classified into the following categories:

l Dynamic entry

A dynamic entry is obtained by a bridge through the SVL/IVL mode. The dynamic entrymay age and may also be lost after the packet switching unit is reset.

l Static entry

A static entry, which corresponds to a specific MAC address and port, is manually addedby the network administrator into the MAC address table by using the NMS. The staticentry does not age, and is also not lost after the packet switching unit is reset. Generally,you need to configure the static MAC address entry for the equipment that is connected tothe port, whose MAC address is known, and on which there is large volume of traffic fora long time.

l Blacklist entry

A blacklist entry is used to discard the data frame that contains the specified MAC address,namely, the MAC disabled entry. A blacklist entry is also called a blackhole entry. Theblackhole entry is configured by the network administrator. The blackhole entry does notage, and is also not lost after the packet switching unit is reset.



5-17

NOTE

If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is receivedto enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism iscalled aging, and this period is called aging time. The aging time of a MAC address table is five minutes bydefault.

The OptiX RTN 910 supports enabling/disabling the aging function and setting the aging time for the MACaddress table.

5.1.9 Protection for Ethernet ServicesThe OptiX RTN 910 supports three protection modes for Ethernet services, namely, Ethernetring protection switching (ERPS), link aggregation (LAG), and multiple spanning tree protocol(MSTP).

ERPSERPS is applicable to ring physical networks and can provide protection for the E-LAN servicesbetween all the nodes on the ring network. Generally, when a ring network is configured withERPS, the RPL node blocks the RPL port on one side so that all the services are transmittedthrough the ports on the other side. In this manner, service loops are prevented. If a section oflink fails or an NE becomes faulty, the RPL node unblocks its RPL port so that the services areswitched from the faulty point to the RPL port for transmission. In this manner, protection forthe ring network is realized.

The Ethernet ring network shown in Figure 5-8 is configured with ERPS. Generally, the RPLnode (NE D) blocks its RPL port that is connected to NE A, and all the services are transmittedover the link NE A <-> NE B <-> NE C <-> NE D. When the link between NE A <-> NE Bbecomes faulty, NE D unblocks the blocked port so that the services can be transmitted over thelink NE A <-> NE D <-> NE C <-> NE B.


Configuration Guide


Issue 02 (2009-10-30)

Figure 5-8 Implementation of ERPS


Link

NE B

NE A

NE C

NE D

NE B

NE A

NE C

NE D

Failure

Ethernet service direction

Blocked port

LAG

Link aggregation allows multiple links that are attached to the same equipment to be aggregatedto form a link aggregation group (LAG) so that the bandwidths and availability of the linksincrease. The aggregated links can be considered as a single logical link.

As shown in Figure 5-9, the LAG provides the following functions:

l Increases the link capacity.



5-19

The LAG provides the telecom operators with a cost-effective method of increasing thelink bandwidth. The operators obtain data links with higher bandwidths by combiningmultiple physical links into one logical link without upgrading the existing equipment. Thebandwidth of the logical link is equal to the sum of the bandwidths of the physical links.The aggregation module distributes the traffic to different members by using the loadsharing algorithm, thus realizing the load sharing function at the link level.

l Improves the link availability.The links in a LAG provide backup to each other dynamically. When a link fails, anotherlink in the LAG quickly takes over. The process in which link aggregation starts the backuplink is related only to the links in the same LAG and is not related to the links that are notin the LAG.

Figure 5-9 LAG

Ethernetpacket

Link 1

Link aggregationgroup

Ethernetpacket

Link 2

Link 3

MSTPThe OptiX RTN 910 supports only the MSTP protocol that uses the common and internalspanning tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree protocol(RSTP). The RSTP is applicable in the case of a network loop. This protocol adopts certainalgorithms to reconstruct a loop network into a loop-free tree network and thus prevents Ethernetframes from increasing and cycling in an endless manner on the loop network.

In the case of the OptiX RTN 910, the MSTP is used to prevent a network loop on the accessside.

See Figure 5-10. When the user equipment accesses the OptiX RTN 910 through two differenttrails, you can configure the ports on the OptiX RTN 910 that are connected to the user networkinto a port group. This port group, together with the switch on the user network, can run theMSTP. Hence, if a service access link becomes faulty, the MSTP enables a re-configuration togenerate the spanning tree topology, thus providing protection for the user network that isconfigured with multiple access points.


Configuration Guide


Issue 02 (2009-10-30)

Figure 5-10 Prevention of network loops on the access side

CIST

Root Root

Port group

Blocked Port

5.1.10 QoSThe quality of service (QoS) refers to the ability of a communication network to ensure theexpected service quality in the aspects of the bandwidth, delay, delay jitter, and packet loss ratio,and thus to ensure that the request and response from the user or the request and response fromthe application meet the requirements of an expected service class. The OptiX RTN 910 supportsthe following QoS functions, namely, differentiated service (DiffServ), flow classification,CAR, traffic shaping, and queue scheduling.

DiffServDiffServ (DS) is an end-to-end QoS control model and performs the QoS processing functionas follows:

1. The DS edge node checks the QoS information carried by the packets that enter the DSdomain. Then, the DS edge node aggregates the packets that are at the same QoS levelsinto the same behavior aggregates (BAs) and maps the BAs into corresponding per-hopbehavior (PHB) service class.

2. The DS edge node controls the traffic of the BAs according to the PHB service class, andforwards the BAs to the DS interior node.

3. The DS internal node controls the traffic of the BAs according to the PHB service class,and forwards the BAs to the DS edge node of the next hop.

The OptiX RTN 910 supports eight PHB service class, namely, BE, AF1, AF2, AF3, AF4, EF,CS6, and CS7. Packets can be mapped into the corresponding PHB level according to theCVLAN priority, SVLAN priority, or DSCP value.

NOTE

l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which isvalid. It is the same case with the AF2, AF3, and AF4.

l In the case of a point-to-point transparently transmitted E-Line service, the OptiX RTN 910 supports onlymapping the PHB service classes according to the DSCP values in the Ethernet frames.



5-21

Flow Classification

The OptiX RTN 910 supports two flow classification methods, namely, simple flowclassification and complex flow classification. In the case of the simple flow classification,different services on specified ports are mapped into different PHB service classes according tothe C-VLAN priority, S-VLAN priority, or DSCP value. In the case of the complex flowclassification, specified services mapped into different PHB service classes according to theCVLAN/SVLAN ID, CVLAN/SVLAN priority, or DSCP value.

The OptiX RTN 910 supports the following complex flow types:

l Flow classified according to the specified CVLAN ID

The packets that carry the specified CVLAN ID are classified as a flow.

l Flow classified according to the CVLAN priority

The packets that are from a certain port and have a specified CVLAN priority are classifiedas a flow.

l Flow classified according to the specified SVLAN ID

The packets that are from a certain port and have a specified SVLAN ID are classified asa flow.

l Flow classified according to the specified SVLAN priority

The packets that are from a certain port and have a specified SVLAN priority are classifiedas a flow.

l Flow classified according to the DSCP value

The packets that are from a certain port and have a specified DSCP value are classified asa flow.

The flow can be further classified according to the combination of CVLAN ID+CVLAN priorityor SVLAN ID+SVLAN priority.

In the case of complex flows, the following QoS processing operations can be performed:

l Passes or discards the flow according the access control list (ACL).

l Maps the flow into a new PHB service class.

l In the ingress direction, restrict the rate of the flow by using the CAR.

l In the egress direction, perform the flow shaping.

CAR

The CAR is a type of traffic policing technology. When the CAR is used, the rate of the trafficafter flow classification is assessed in a certain period (including in the long term and in the shortterm); the packet rate of which does not exceed the specified value is set to a high priority andthe packet rate of which exceeds the specified value is discarded or downgraded. In this manner,the CAR restricts the traffic into the transmission network.

The OptiX RTN 910 supports the CAR processing for a complex flow in the ingress direction.The CAR processing operations are as follows:

l When the rate of packets is lower than or equal to the preset committed information rate(CIR), these packets are marked green and pass the policing of the CAR. These packets arealways forwarded first in the case of network congestion.


Configuration Guide


Issue 02 (2009-10-30)

l When the rate of packets exceeds the preset peak information rate (PIR), these packets ata rate higher than the PIR are marked red and directly discarded.

l When the rate of packets is higher than the CIR but is lower than the PIR, the packets at arate higher than the CIR can pass the restriction but are marked yellow. Yellow packetscan be set to "discard", "pass", or "remark". If packets are set to "remark", these packetsare mapped to another specified queue with a certain priority (that is, the priority of thesepackets is changed) and then forwarded.

l When the rate of packets that pass the restriction of the CAR is lower than or equal to theCIR in a certain period, certain packets can burst and these packets are always forwardedfirst in the case of network congestion. The maximum traffic of the burst packets isdetermined by the committed burst size (CBS).

l When the rate of packets that pass the restriction of the CAR is higher than the CIR but islower than or equal to the PIR, certain packets can burst and these packets are markedyellow. The maximum traffic of the burst packets is determined by the peak burst size(PBS).

Figure 5-11 shows the traffic change after the CAR processing. The packets that are markedred are directly discarded, and the packets that are marked yellow and green pass the policingof the CAR. In addition, the packets that are marked yellow are processed according to the presetvalue.

Figure 5-11 CAR processing

PIR

CIR

MBS

CBS

PIR

CIR CAR

PIR

CIR

MBS

CBS

Traffic ShapingWhen the traffic shaping function is used, the traffic and burst size of an outgoing connectionof a network can be restricted. In this manner, the packet can be transmitted at an even rate.

The OptiX RTN 910 supports the shaping of a complex flow, the PHB service class, or the portin the egress direction.

After the traffic shaping function is enabled, the OptiX RTN 910 processes the packets as followsif packets are not available in the buffer queue:

l If the rate of the packets is lower than or equal to the preset CIR, the packets are directlyforwarded.

l If the rate of the packets is higher than the CIR but is lower than or equal to the PIR, thepackets at a rate higher than the CIR enter the buffer queue and the buffer queue forwardsthe packets at a rate equal to the CIR.



5-23

l If the rate of the packets is higher than the PIR, these packets are directly discarded.

l If the rate of the packets in a certain period is lower than or equal to the CIR, certain packetscan burst and be directly forwarded. The maximum traffic of the burst packets is determinedby the CBS.

l If the rate of the packets in a certain period is higher than the CIR but is lower than or equalto the PIR, certain packets can burst and enter the buffer queue. The maximum traffic ofthe burst packets is determined by the PBS.

When packets are available in the buffer queue, the packets rate of which passes the restrictionof the PIR enter the buffer queue and the buffer queue forwards these packets at a rate equal tothe CIR.

As is evident from the preceding processing mechanism, the differences of the traffic shapingfrom the CAR are as follows:

l In the processing of the CAR, the packet that does not conform to the traffic features isdowngraded or directly discarded.

l In the processing of the traffic shaping, the packet that does not conform to the trafficfeatures is stored in the buffer. The packet is directly discarded only when the bufferoverflows.

l The traffic shaping increases the delay of services, but the CAR does not.

Figure 5-12 shows the traffic change after the traffic shaping. During the traffic shaping, thegreen part indicates the traffic that is directly forwarded without traversing the buffer queue, theyellow part indicates the traffic that is forwarded after traversing the buffer queue, and the redpart indicates the traffic that is discarded.

Figure 5-12 Processing of the traffic shaping

PIR

CIR

PBS

CBS

PIR

CIR Shaping

PIR

CIR

Queue SchedulingIn the case of the OptiX RTN 910, each Ethernet port has eight egress queues, which correspondto eight PHB service classes. The OptiX RTN 910 supports three queue scheduling methods,namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR.

l SP Scheduling AlgorithmFigure 5-13 shows the SP scheduling algorithm. During the SP queue scheduling, packetsare transmitted in a descending order of priority. When a queue with a higher priority isempty, the packets in the queue with a lower priority can be transmitted. In this manner,packets of key services are placed into the queues with higher priorities and packets of non-


Configuration Guide


Issue 02 (2009-10-30)

key services (such as email services) are placed into queues with lower priorities. Hence,the packets of key services can be always transmitted first, and the packets of non-keyservices are transmitted when the data of key services is not processed.When the SP queue scheduling algorithm is used, all the resources are used to ensure theQoS of the services of the highest priority. If there are packets in the queues with higherpriorities when congestion occurs, the packets in the queues with lower priorities cannotbe transmitted all the time.

Figure 5-13 SP queue scheduling algorithm

Queue 8

Queue 7

Queue 2

Queue 1

...

Higher

Normal

Lowest

PrioritiesQueues

HighestPackets to be transmitted

through this interface

Queue in which the priorities of packets arein a descending order from left to right

Classification

Egressqueue

scheduling

Packets transmitted out ofthe interface

l WRR Scheduling Algorithm

Figure 5-14 shows the WRR scheduling algorithm. The WRR scheduling algorithm divideseach port into several egress queues and schedules the packets in these queues in turn. Thisensures that each queue obtains a certain service period. In addition, the WRR allocates aweight value for each queue and then allocates the service time period for each queueaccording to the weight value. The port transmits the Ethernet frames of the correspondingqueue in the corresponding service period. If the queue to which the service periodcorresponds contains no Ethernet frames, a time period is extracted to transmit the Ethernetframes that correspond to the subsequent time periods. That is, the WRR ensures thebandwidth resource allocation based on the weight values of the queues in the case of alink congestion and full bandwidth utilization in the case of no link congestion. Forexample, a port provides four queues. The weight proportion of the four queues is 5:3:1:1.Hence, when congestions occur in all the queues, the four queues are allocated with the 50Mbit/s, 30 Mbit/s, 10 Mbit/s, and 10 Mbit/s bandwidths respectively. If the first queuecontains no Ethernet frames and congestions occur in the other three queues, the other threequeues are allocated with the 60 Mbit/s, 20 Mbit/s, and 20 Mbit/s bandwidths respectively.Compared with the SP scheduling algorithm, the WRR scheduling algorithm prevents thedisadvantage that packets in the queues with lower priorities may fail to obtain service fora long time. In the case of the WRR algorithm, however, all the bandwidth resources cannotbe used when congestions occur in the services of higher priorities.



5-25

Figure 5-14 WRR scheduling algorithm

Queue 4

Queue 3

Queue 2

Queue 1

30

10

10

WeightsQueues

50

Packets to be transmittedthrough this interface

Queue in which the priorities of packets arein a descending order from left to right

Egressqueue

scheduling

Packets transmitted out ofthe interface

Classification

l SP+WRR Scheduling Algorithm

Figure 5-15 shows the SP+WRR scheduling algorithm. In the case of SP+WRR schedulingalgorithm, a group of WRR queues must be allocated with the same queue priority. The SP+WRR scheduling algorithm is described as follows:– If the queues that have higher priorities than the WRR queues contain Ethernet frames,

the Ethernet frames are transmitted according to the SP scheduling algorithm. In thiscase, the Ethernet frames in the WRR queues are not transmitted.

– If the queues that has higher priorities than the WRR queues do not contain Ethernetframes, the Ethernet frames in the WRR queues are transmitted according to the WRRscheduling algorithm.

– If the WRR queues and the queues that has higher priorities than the WRR queues donot contain Ethernet frames, the Ethernet frames in the queues that has lower prioritiesthan the WRR queues are transmitted according to the SP algorithm.

Figure 5-15 SP+WRR scheduling algorithm

Queue 8

Queue 1

Weights

SP Queues

Packets to be transmittedthrough this interface

Classification

Egress queuescheduling

Queue in which the priorities of packets are in adescending order from left to right

Packets transmittedout of the interfaceWRR

Queues

WRR Queue

Lowest

Priorities

Highest

Queue 5

Queue 4

Queue 3

Queue 2

25

25

25

25

Queue 6

Higher

Normal

Queue 8

Queue 7

lower

In the case of the OptiX RTN 910, the SP+WRR scheduling algorithm is the default queuescheduling mode for each Ethernet port. The queue priority levels are CS7, CS6, EF, AF1, AF2,AF3, AF4, and BE in the descending order or priority. AF1 to AF4 are WRR queues. Exceptfor the default settings, the WRR queues and SP queues cannot be interleaved if you set the SP+WRR scheduling algorithm manually.


Configuration Guide


Issue 02 (2009-10-30)

5.2 Configuration Procedure (E-Line Services)The configuration procedure varies according to the type of the E-Line services.

Procedure for Configuring Point-to-Point Transparently Transmitted E-LineServices

Table 5-7 Procedure for configuring point-to-point transparently transmitted E-Line services


1 Configuring theparameters ofEthernetports

A.20.1SettingtheGeneralAttributes ofEthernetInterfaces

Required. Set the parameters as follows:l In the case of used ports, set Enable Port to

Enabled. In the case of unused ports, set EnablePort to Disabled.

l Set Encapsulation Type to Null.

l In the case of the Ethernet port that is connectedto the external equipment, set Working Mode tobe the same value as the external equipment(generally, the working mode of the externalequipment is auto-negotiation). In the case of theEthernet ports within the network, set WorkingMode to Auto-Negotiation.

l When JUMBO frames are transmitted, set MaxFrame Length(byte) according to the actuallength of the JUMBO frames. Otherwise, it isrecommended that you set Max Frame Length(byte) to 1536.

A.20.2Configuring theTrafficControlofEthernetInterfaces

Required when the flow control function is enabledon the external equipment to which the Ethernet portis connected. Set the parameters as follows:l When the external equipment uses the non-auto-

negotiation flow control function, set Non-Autonegotiation Flow Control Mode to EnableSymmetric Flow Control.

l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to EnableSymmetric Flow Control.

A.20.4SettingtheAdvancedAttributes ofEthernetInterfaces

Optional.



5-27


2 Configuring theparameters ofIF_ETHports

A.21.1SettingtheGeneralAttributes of theIF_ETHPort

Required.Set Encapsulation Type to Null.

A.21.3SettingtheAdvancedAttributes of theIF_ETHPort

Optional.When the IF_ETH port transmits an Ethernet servicethat permits bit errors, such as a voice service or avideo service, you can set Error Frame DiscardEnabled to Disabled.


Configuration Guide


Issue 02 (2009-10-30)


3 Configuring theLAG

A.14.1Creatinga LAG

Required if the LAG is configured to protect the FE/GE ports or if the Hybrid microwave uses the N+0/XPIC configuration mode. Set the parameters asfollows:l Set LAG Type to the same value as the opposite

equipment. Generally, set LAG Type to Static forthe equipment at both ends.

l The Hybrid/AM attribute must be set to the samevalue for the IF ports in a LAG.

l In the case of FE/GE ports, set Load Sharing tothe same value as the opposite equipment. If theLAG is configured only to realize protection, it isrecommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If theLAG is configured to increase the bandwidth, it isrecommended that you set Load Sharing toSharing for the equipment at both ends.

l When the Hybrid microwave uses the N+0/XPICconfiguration mode, set Load Sharing toSharing for the equipment at both ends.

l Set Revertive Mode to the same value as theopposite equipment. Generally, set RevertiveMode to Revertive for the equipment at bothends. This parameter is valid only to the non-sharing LAG.

l Set Load Sharing Hash Algorithm to the samevalue as the opposite equipment. Unless otherwisespecified, this parameter adopts the default value.This parameter is valid only to the sharing LAG.

l It is recommended that you set this parameter tothe same values for the main and slave ports. Inthis case, you can set System Priority accordingto the requirements. It is recommended that thisparameter adopts the default value. Thisparameter is valid only to the static LAG.

l Set Main Board, Main Port, and Selected SlavePorts according to the planning information. It isrecommended that you set this parameter to thesame values for the main and slave ports.

A.14.2Settingthe PortPriority

Optional.



5-29


4 Configuring the E-Lineservice

A.26.2Configuring the E-LineService

Required. Set the parameters as follows:l Set Direction to UNI-UNI.

l Set Source Port and Sink Port according to theplanning information.

l Source VLANs and Sink VLANs remain null.

A.26.3Creatinga VLANForwarding TableItem

Required when the VLAN tags of the Ethernetservice need to be switched at the source and sink.The parameters need to be set according to thenetwork planning information.NOTE

The corresponding VLAN forwarding table items need tobe configured for the source port and sink port.

5 Configuring theQoS

A.16.1Creatinga DSDomain

Required.Set the parameters according to the network planninginformation.NOTE

Point-to-point transparently transmitted services supportmapping the PHB service classes based on the DSCP typeonly. The default DS, however, maps the PHB serviceclasses according to the CLAN priorities. Hence, you needto configure a new DS.

A.16.3Creatinga PortPolicy

Required when the QoS processing operationsexcept the DS and port shaping need to be performedfor a specific port.Set the parameters according to the network planninginformation.

A.16.4CreatingtheTraffic

Required when the CAR or shaping operation needsto be performed for a specific flow over the port.Set the parameters according to the network planninginformation.

A.16.5Settingthe PortThat Usesthe PortPolicy

Required when the port policy is already created.

A.16.6Configuring PortShaping

Required when the bandwidth over the egress port ofthe Ethernet service needs to be limited.The parameters need to be set according to thenetwork planning information.


Configuration Guide


Issue 02 (2009-10-30)


6 VerifyingtheEthernetserviceconfiguration

A.17.1Creatingan MD

Required in the case of the NE where the twoEthernet ports involved in the service test are located.Set the parameters as follows:l Set Maintenance Domain Name and

Maintenance Domain Level to the same valuesfor the two NEs.

l In the test of Ethernet services between two edgenodes on the transport network, it is recommendedthat Maintenance Domain Level adopts thedefault value, namely, 4. In the test of Ethernetservices between two NEs within the transportnetwork, set Maintenance Domain Level to avalue smaller than 4. In the test of Ethernetservices between two Ethernet ports on the sameNE, set Maintenance Domain Level to a valuesmaller than the value that is set in the test ofEthernet services between two NEs within thetransport network.

A.17.2Creatingan MA

Required in the case of the NE where the twoEthernet ports involved in the service test are located.Set the parameters as follows:l Set Maintenance Domain Name to the value of

Maintenance Domain Name that is set in theprevious step.

l Set Maintenance Association Name to the samevalue for the two NEs.

l Set Relevant Service to the same service for thetwo NEs.

l It is recommended that you set CC Test TransmitPeriod(ms) to 1s.

A.17.3Creatingan MEPPoint

Required in the case of the NE where the twoEthernet ports involved in the service test are located.Set the parameters as follows:l Set Maintenance Association Name to the value

of Maintenance Association Name that is set inthe previous step.

l Set Board and Port to the Ethernet ports that areinvolved in the service test.

l Set MP ID to different values for MEPs in thesame MD.

l In this example, Ethernet services between twoNEs within the transport network are tested.Hence, set Direction to Ingress for the MEPs.

l In this example, the MP ID is used to identify theMEP during the loopback test. Hence, set CCStatus to Active.



5-31


A.17.4CreatingRemoteMEPs inan MA

Required in the case of the NE where the Ethernetports involved in the OAM operation are located. Setthe parameters as follows:l Set Maintenance Domain Name to the value of


l Set Maintenance Association Name to the valueof Maintenance Association Name that is set inthe previous step.

l If other MEPs may initiate OAM operations to anMEP in the same MA, set the other MEPs to bethe remote MEPs.

A.26.5TestingtheEthernetService

Required.There should be no packets lost during the test ofEthernet services by performing loopbackoperations.

Procedures for Configuring VLAN-Based E-Line Services

Table 5-8 Procedures for configuring VLAN-based E-Line services






l Set Encapsulation Type to 802.1Q.




Configuration Guide


Issue 02 (2009-10-30)


A.20.2Configuring theTrafficControl ofEthernetInterfaces




A.20.3Settingthe Layer2Attributes ofEthernetInterfaces

Required. Set the parameters as follows:l If all the accessed services carry VLAN tags

(tagged frames), set TAG to Tag Aware.l If none of the accessed services carries VLAN

tags (untagged frames), set TAG to Access, andset Default VLAN ID and VLAN Priorityaccording to the network planning information.

l When the accessed services contain taggedframes and untagged frames, set TAG toHybrid, and set Default VLAN ID and VLANPriority according to the network planninginformation.


Optional.



Required.Set Encapsulation Type to 802.1Q.



5-33


A.21.2Settingthe Layer2Attributes of theIF_ETHPort


(tagged frames), set Tag to Tag Aware.l If none of the accessed services carries VLAN

tags (untagged frames), set Tag to Access, and setDefault VLAN ID and VLAN Priorityaccording to the network planning information.

l When the accessed services contain taggedframes and untagged frames, set Tag to Hybrid,and set Default VLAN ID and VLAN Priorityaccording to the network planning information.




Configuration Guide


Issue 02 (2009-10-30)



A.14.1Creatinga LAG


equipment. Generally, set LAG Type to Staticfor the equipment at both ends.


l In the case of FE/GE ports, set Load Sharing tothe same value as the opposite equipment. If theLAG is configured only to realize protection, it isrecommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If theLAG is configured to increase the bandwidth, itis recommended that you set Load Sharing toSharing for the equipment at both ends.



l Set Load Sharing Hash Algorithm to the samevalue as the opposite equipment. Unlessotherwise specified, this parameter adopts thedefault value. This parameter is valid only to thesharing LAG.




Optional.



5-35


4 Configuring the E-LineService

A.26.2Configuring the E-LineService

Required. Set the parameters as follows:l Set Direction to UNI-UNI.

l Set Source Port and Sink Port according to theplanning information.

l Set Source VLANs and Sink VLANs accordingto the network planning information. The twoparameters should be set to the same value.

A.26.3Creatinga VLANForwarding TableItem

Required when the VLAN tags of the Ethernetservice need to be switched at the source and sink.The parameters need to be set according to thenetwork planning information.NOTE

The corresponding VLAN forwarding table items need tobe configured for the source port and sink port.

5 Configuring the QoS


Required when the default DS domain does not meetthe requirements.Set the parameters according to the networkplanning information.

A.16.2Changingthe PortsThat Usethe DSDomain

Optional.When several applied ports in the same DS domainneed to map with PHB service classes based on thepacket type, you can set Packet Type to differentvalues for the applied ports.


Required when the QoS processing operationsexcept the DS and port shaping need to be performedfor a specific port.Set the parameters according to the networkplanning information.


Required when the CAR or shaping operation needsto be performed for a specific flow over the port.Set the parameters according to the networkplanning information.




Required when the bandwidth over the egress portof the Ethernet service needs to be limited.The parameters need to be set according to thenetwork planning information.


Configuration Guide


Issue 02 (2009-10-30)


6 VerifyingtheEthernetServiceConfiguration

A.17.1Creatingan MD

Required in the case of the NE where the twoEthernet ports involved in the service test arelocated. Set the parameters as follows:l Set Maintenance Domain Name and


l In the test of Ethernet services between two edgenodes on the transport network, it isrecommended that Maintenance Domain Leveladopts the default value, namely, 4. In the test ofEthernet services between two NEs within thetransport network, set Maintenance DomainLevel to a value smaller than 4. In the test ofEthernet services between two Ethernet ports onthe same NE, set Maintenance Domain Level toa value smaller than the value that is set in the testof Ethernet services between two NEs within thetransport network.

A.17.2Creatingan MA

Required in the case of the NE where the twoEthernet ports involved in the service test arelocated. Set the parameters as follows:l Set Maintenance Domain Name to the value of




l It is recommended that you set CC TestTransmit Period(ms) to 1s.



5-37



Required in the case of the NE where the twoEthernet ports involved in the service test arelocated. Set the parameters as follows:l Set Maintenance Association Name to the value



l Set VLAN to a VLAN that is configured for theEthernet services. Set VLAN of the two MEPs incompliance with the configuration of the Ethernetservices.

l Set MP ID to different values for MPs in the sameMD.

l In the test of Ethernet services between two NEswithin the transport network, set Direction toIngress for the MEPs.

l The MP ID is used to identify the MEP during theloopback test. Hence, set CC Status to Active.









Configuration Guide


Issue 02 (2009-10-30)

Procedures for Configuring QinQ-Based E-Line Services

Table 5-9 Procedures for configuring QinQ-based E-Line services






l If a UNI can access untagged frames, setEncapsulation Type to Null. If a UNI can accesstagged frames only, set Encapsulation Type to802.1Q.

l In the case of an NNI port, set EncapsulationType to QinQ.









5-39



Required. Set the parameters as follows:l In the case of a UNI, if Encapsulation Type is

set to 802.1Q, set TAG to Tag Aware (defaultvalue).

l In the case of an NNI that is connected to theexternal equipment, set QinQ Type Domainaccording to the T-PID of the SVLAN that issupported by the external equipment. In the caseof NNI ports within the network, QinQ TypeDomain takes the default value.


Optional.



Required.l If a UNI can access untagged frames, set

Encapsulation Type to Null. If a UNI can accesstagged frames only, set Encapsulation Type to802.1Q.




set to 802.1Q, set Tag to Tag Aware (defaultvalue).

l In the case of an NNI that is connected to theexternal equipment, set QinQ Type Domainaccording to the T-PID of the SVLAN that issupported by the external equipment. In the caseof NNI ports within the network, QinQ TypeDomain takes the default value.




Configuration Guide


Issue 02 (2009-10-30)



A.14.1Creatinga LAG











Optional.



5-41


4 A.26.1 Configuring theQinQ Link

Required.Set the parameters according to the networkplanning information.

5 A.26.2 Configuring theE-Line Service

Required.Set the parameters according to the networkplanning information.















Configuration Guide


Issue 02 (2009-10-30)



A.17.1Creatingan MD

Required in the case of the NE where the Ethernetports involved in the service test are located. Set theparameters as follows:l Set Maintenance Domain Name and



A.17.2Creatingan MA

Required in the case of the NE where the Ethernetports involved in the service test are located. Set theparameters as follows:l Set Maintenance Domain Name to the value of







5-43



Required in the case of the NE where the Ethernetports involved in the service test are located. Set theparameters as follows:l Set Maintenance Association Name to the value



l Set VLAN to a VLAN that is configured for theEthernet service. Set VLAN of the two MEPs incompliance with the service configuration. IfEncapsulation Type of a port is Null, VLANneed not be set.


l In the test of Ethernet services between two NEswithin the transport network, set Direction toIngress for the MEPs.









5.3 Configuration Procedure (E-LAN Services)The configuration procedure varies according to the type of the E-LAN services.


Configuration Guide


Issue 02 (2009-10-30)

Procedure for Configuring 802.1d Bridge-Based E-LAN Services

Table 5-10 Procedure for configuring 802.1d bridge-based E-LAN services






l Set Encapsulation Type to Null.








Required when you need to enable the port self-looptest and automatic loopback shutdown functions orto enable the broadcast packet suppression function.Set Loopback Check, Loopback Port Shutdown,Enabling Broadcast Packet Suppression, andBroadcast Packet Suppression Thresholdaccording to the requirements.



5-45


2 Setting theparameters of theIF_ETHports


Required.Set Encapsulation Type to Null.




Configuration Guide


Issue 02 (2009-10-30)



A.14.1Creatinga LAG











Optional.



5-47


4 Configuring ERPS

A.11.1CreatingEthernetRingProtectionInstances

Required if the Ethernet services are configured withERPS.

A.11.2SettingtheParameters ofEthernetRingProtocol

Required when the values of the default parametersof the timers of the ERPS need to be changed.Set Hold-Off Time(ms), Guard Time(ms), WTRTime(min), and Packet Transmit Interval(s)according to the requirements. Set these parametersto the same values for all the NEs on the network.

5 A.26.4 Configuring theE-LAN Service

Required. Set the parameters as follows:l Set Tag Type to Tag-Transparent.

l Set Self-Learning MAC Address to Enabledaccording to the planning information.

l In the UNI tab page, set Port according to theplanning information and set VLANs/CVLAN tonull.

l To disable the packet forwarding between certainE-LAN service ports, add the ports to SplitHorizon Group Member.

6 Managingthe MACaddresstable

A.27.2CreatingaBlacklistEntry ofMACAddresses

Required when usage of E-LAN services needs to bedisabled on certain MAC address host.Set the parameters according to the networkplanning information.

A.27.1Creatinga StaticMACAddressEntry

Required if you need to set certain MAC addressentries not to age.Set the parameters according to the networkplanning information.


Configuration Guide


Issue 02 (2009-10-30)


A.27.3Configuring theAgingParameters of aMACAddressTable

Required if the aging function needs to be disabledor if the default aging time (five minutes) needs tobe changed.Set the parameters according to the networkplanning information.

7 A.28 Setting the Modefor Processing anUnknown Frame of theE-LAN Service

Optional.
















5-49



A.17.1Creatingan MD




A.17.2Creatingan MA







Configuration Guide


Issue 02 (2009-10-30)







l Set Direction according to the direction of theEthernet services between the MEPs. If theEthernet services flow towards the packetswitching unit, set Direction to Ingress.Otherwise, set Direction to Egress.









NOTE

If the MSTP or IGMP Snooping protocol is required for configuring the E-LAN services, see the OptiX RTN910 Feature Description.



5-51

Procedure for Configuring 802.1q Bridge-Based E-LAN Services

Table 5-11 Procedure for configuring 802.1q bridge-based E-LAN services

Step Operation Remarks





l Set Encapsulation Type to 802.1Q.









(tagged frames), set TAG to Tag Aware.l If none of the accessed services carries VLAN

tags (untagged frames), set TAG to Access, andset Default VLAN ID and VLAN Priorityaccording to the network planning information.

l When the accessed services contain taggedframes and untagged frames, set TAG toHybrid, and set Default VLAN ID and VLANPriority according to the network planninginformation.


Configuration Guide


Issue 02 (2009-10-30)






Required.Set Encapsulation Type to 802.1Q.



(tagged frames), set Tag to Tag Aware.l If none of the accessed services carries VLAN

tags (untagged frames), set Tag to Access, and setDefault VLAN ID and VLAN Priorityaccording to the network planning information.

l When the accessed services contain taggedframes and untagged frames, set Tag to Hybrid,and set Default VLAN ID and VLAN Priorityaccording to the network planning information.





5-53



A.14.1Creatinga LAG











Optional.


Configuration Guide


Issue 02 (2009-10-30)


4 Configuring ERPS






Required. Set the parameters as follows:l Set Tag Type to C-Awared.


l In the UNI tab page, set Port and VLANs/CVLAN according to the planning information.











5-55



Optional.















Configuration Guide


Issue 02 (2009-10-30)


9 VerifyingtheEthernetServiceConfiguration

A.17.1Creatingan MD




A.17.2Creatingan MA








5-57






l Set VLAN to a VLAN. The settings of the twoMEPs must be the same.












Configuration Guide


Issue 02 (2009-10-30)

Procedure for Configuring 802.1ad Bridge-Based E-LAN Services

Table 5-12 Procedure for configuring 802.1ad bridge-based E-LAN services






l If a UNI can access untagged frames, setEncapsulation Type to Null. If a UNI can accesstagged frames only, set Encapsulation Type to802.1Q.










set to 802.1Q, set TAG to Tag Aware (defaultvalue).

l In the case of an NNI that is connected to theexternal equipment, set QinQ Type Domainaccording to the T-PID of the SVLAN that issupported by the external equipment.



5-59






Required.l If a UNI can access untagged frames, set

Encapsulation Type to Null. If a UNI can accesstagged frames only, set Encapsulation Type to802.1Q.



Required. Set the parameters as follows:l In the case of a UNI port, if Encapsulation

Type is set to 802.1Q, set Tag to Tag Aware(default value).

l In the case of an NNI port that is connected to theexternal equipment, set QinQ Type Domainaccording to the T-PID of the SVLAN that issupported by the external equipment. In the caseof an NNI port within the network, QinQ TypeDomain takes the default value.




Configuration Guide


Issue 02 (2009-10-30)



A.14.1Creatinga LAG











Optional.



5-61


4 Configuring ERPS






Required. Set the parameters as follows:l Set Tag Type to S-Awared.


l In the UNI and NNI tab pages, set the parametersaccording to the planning information.










Configuration Guide


Issue 02 (2009-10-30)



Optional.







Required when the QoS processing operationsexcept the DS need to be performed for a specificport.Set the parameters according to the networkplanning information.









5-63



A.17.1Creatingan MD




A.17.2Creatingan MA







Configuration Guide


Issue 02 (2009-10-30)






l Set VLAN to a VLAN. The settings of the twoMEPs must be the same.











NOTE

If the MSTP or IGMP Snooping protocol is required for configuring the E-LAN services, see the OptiX RTN910 Feature Description.



5-65

5.4 Configuration Example (Point-to-Point TransparentlyTransmitted E-Line Services)

This topic considers a point-to-point transparently transmitted E-Line service as an example todescribe how to configure the Ethernet service according to the network planning information.





As shown in Figure 5-16, NE1 is the terminal station of a backhaul network. NE1 transparentlytransmits the Ethernet services from the BTS to NE2 in point-to-point manner. DSCP flags areused to identify the priorities of the Ethernet services from the BTS. Therefore, the point-to-point transparently transmitted E-line service can be configured on NE1.

Figure 5-16 Networking diagram (point-to-point transparently transmitted E-line service)

NE2NE1

Tranparent transmissionE-LINE service

Backhaul network

BTSBSC

The networking information about NE1 is as follows:

l The IFU2 board in slot 3 of NE1 and the IFU2 in slot 3 of NE2 construct a Hybrid radiolink. This Hybrid radio link adopts the 1+0 non-protection mode.

l The AM function is enabled for this Hybrid radio link.

l The 7-EM4T-1 on NE1 accesses the Ethernet services from the BTS.



Configuration Guide


Issue 02 (2009-10-30)

Ethernet Port

Table 5-13 provides the information about the Ethernet port involved in the service.

Table 5-13 Ethernet port

Parameter 7-EM4T-1

Encapsulation Type Null

Working Mode Auto-Negotiation

Maximum Frame Length (byte) 1536

Flow Control Disabled

NOTE

l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the FE port that accessesthe BTS must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the localEthernet port must work in the same mode. The working modes of the Ethernet ports inside the network areplanned as auto-negotiation.

l In this example, to ensure that the Ethernet frames that carry more than one tag such as QinQ can traversethe equipment, the maximum frame length is set to 1536 (bytes). If the equipment needs to transmit JUMBOframes with a greater length, set the maximum frame length according to the actual length of a JUMBOframe.

l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate forQoS processing. The flow control planning on the NE must match the flowing control planning on the peerequipment.

Information About the IF_ETH Ports

Table 5-14 provides the information about the IF_ETH ports that carry services.

Table 5-14 Ethernet port

Parameter 3-IFU2-1


Error Frame Discard Enabled Enabled

NOTE

The majority of the backhaul services on the base station are Internet services. Hence, the error frame discardingfunction needs to be enabled.

LAG

In this example, the LAG is not required.



5-67

Point-to-Point Transparently Transmitted E-Line Service

Table 5-15 provides the detailed service planning information.

Table 5-15 Point-to-point transparently transmitted E-line service

Parameter NE1

Service ID 1

Service Name BTStoNE2_Tline

Direction UNI-UNI

BPDU Not Transparently Transmitted

Source Port 7-EM4T-1

Source C-VLANs Blank

Sink Port 3-IFU2-1

Sink C-VLANs Blank

QoS (Diffserv)

DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTSservices be allocated according to the service type. Then, the transmission network creates thecorresponding DS domain according to the allocated VLAN priority or DSCP value. EachEthernet port involved in the service must use the same DS configuration.

In this example, the BTS services are allocated with corresponding DSCP values according tothe service type, and the NEs allocate the PHB service classes according to the DSCP value, asshown in Table 5-16. Each Ethernet port involved in the service uses the same DS configuration.

Table 5-16 Service class and PHB service class

PHB Service Class DSCP Corresponding ServiceType

CS7 56 -

CS6 48 -

EF 40 Real-time voice service andsignaling service (R99conversational and R99streaming services)

AF4 32 -

AF3 24 Real-time OM and HSDPAservices (OM streaming andHSPA streaming services)


Configuration Guide


Issue 02 (2009-10-30)

PHB Service Class DSCP Corresponding ServiceType

AF2 16 Non-real-time R99 service(R99 interactive and R99background services)

AF1 8 -

BE 0 HSDPA data service (HSPAinteractive and backgroundservices)

NOTE

During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmitEthernet protocol packets or inband DCN packets on the NE.

QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode.

Table 5-17 lists the queue scheduling mode used by each Ethernet port involved in the servicein this example.

Table 5-17 Queue scheduling mode

PHB Service Class Queue Scheduling Mode

CS7 SP

CS6 SP

EF SP

AF4 WRR (weight = 5)




BE SP

QoS (CAR or Shaping For a Specified Service)

To perform the CAR or shaping processing for a specified service, you need to configure theDS edge node accordingly.

In this example, no CAR or shaping processing needs to be performed on the services transmittedfrom the BTS.



5-69

QoS (Port Shaping)If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth ofthe aggregation services, you can perform port shaping at the edge node to limit the Ethernetservice traffic that travels to the aggregation node, thus preventing congestion at the aggregationnode.

In this example, you do not need to perform port shaping.

NOTE

When port shaping is not configured, the OptiX RTN 910 automatically performs port shaping according to thebandwidth over the IF_ETH ports.


ContextNOTE

This topic describes how to configure the point-to-point transparently transmitted Ethernet service on NE1 andhow to configure the ETH OAM data on NE2 for testing the Ethernet service.

Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the general attributesof the Ethernet port.

The values for the relevant parameters are provided as follows.

Parameter Value

7-EM4T-1

Enable Port Enabled



Max Frame Length(byte) 1536

Step 2 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the general attributesof the IF_ETH port.


Parameter Value

3-IFU2-1


Step 3 See A.26.2 Configuring the E-Line Service and configure the E-Line services.


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

Service ID 1

Service Name BTStoNE2_Tline

Direction UNI-UNI



Source VLANs Blank

Sink Port 3-IFU2-1

Sink VLANs Blank

Step 4 See A.16.1 Creating a DS Domain and create a DS domain.

The values for the relevant parameters that need to be set in the main interface are provided asfollows.

Parameter Value

Mapping Relation ID 2

Mapping Relation Name DiffservForBackhaul

Packet Type ip-dscp

The values for the relevant parameters that need to be set in the Ingress Mapping Relation tabpage are provided as follows.

CVLAN SVLAN IP DSCP PHB

0 BE

8 AF11

16 AF21

24 AF31

32 AF41

40 EF

48 CS6

56 CS7



5-71

The values for the relevant parameters that need to be set in the Egress Mapping Relation tabpage are provided as follows.

PHB CVLAN SVLAN IP DSCP

BE 0

AF11 8

AF21 16

AF31 24

AF41 32

EF 40

CS6 48

CS7 56

NOTE

The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.

The values for the relevant parameters that need to be set in the Application Port tab page areprovided as follows.

Parameter Value

Selected Port 7-EM4T-13-IFU2-1

Step 5 See A.16.3 Creating a Port Policy to create the port policy.


Parameter Value

Policy ID 1

Policy Name Port_Comm

Grooming Police After Reloading SP (CS7, CS6, and EF)WRR (AF4-AF1)SP (BE)

Policy Weight(%) 5 (AF4)60 (AF3)30 (AF2)5 (AF1)


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

Bandwidth Limit Disabled (for all PHB service classes)

Step 6 See A.16.5 Setting the Port That Uses the Port Policy and set the ports that use the port policy.


Parameter Value

Port_Comm

Port 7-EM4F-33-IFU2-1

Step 7 See A.17.1 Creating an MD and create an MD.


Parameter Value

NE1 NE2

Maintenance DomainName

InterNE InterNE

Maintenance DomainLevel

3 3

Step 8 See A.17.2 Creating an MA and create an MA.


Parameter Value

NE1 NE2


InterNE InterNE

Maintenance AssociationName

BTS_Tline BTS_Tline

Relevant Service 1-BTStoNE2_Tline 1-BSCtoBTS_TlineA

CC Test Transmit Period(ms)

1s 1s



5-73

NOTE

a: BSCtoBTS_Tline is the name of the point-to-point Ethernet service that is transparently transmitted from NE2to NE1. The service ID is 1.

Step 9 See A.17.3 Creating an MEP Point and create MEP points.


Parameter Value

NE1 NE2


InterNE InterNE


BTS_Tline BTS_Tline

Board 7-EM4T 3-IFU2

Port 7-EM4T-1 3-IFU2-1

VLAN - -

MP ID 101 102

Direction Ingress Egress

CC Status Active Active

Step 10 A.17.4 Creating Remote MEPs in an MA.

Parameter Value

NE1 NE2


InterNE InterNE


BTS_Tline BTS_Tline

Remote Maintenance PointID(_e.g:1,3-6)

102 101

Step 11 See A.26.5 Testing the Ethernet Service and test the E-Line service.

Use MP 101 as the source maintenance point and MP 102 as the sink maintenance point toperform the LB test.

No packet loss occurs.

----End


Configuration Guide


Issue 02 (2009-10-30)

5.5 Configuration Example (VLAN-Based E-Line Service)This topic considers a VLAN-based E-line service as an example to describe how to configurethe Ethernet service according to the network planning information.





Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure the Ethernet services according to the actual requirements. As shown inFigure 5-17, the services transmitted by each BTS carry VLAN tags, and VLAN IDs on theentire network are planned in a unified manner. Hence, the VLAN-based E-Line service can beadopted for service transmission.

Figure 5-17 Networking diagram (VLAN-based E-Line service)

BTS3VLAN 120-129

BSCNE1NE2NE3

NE5

NE4

NE6

FE

FE

FEFE

FE

GE GE

BTS5VLAN 140-149

BTS1VLAN 100-109

BTS2VLAN 110-119

BTS4VLAN 130-139


Ethernet PortTable 5-18 to Table 5-23 provide the information about each Ethernet port involved in theservice.



5-75

Table 5-18 Ethernet port (NE1)

Parameter 7-EM4F-3 7-EM4F-4

Encapsulation Type 802.1Q 802.1Q

Working Mode Auto-Negotiation Auto-Negotiation

Maximum Frame Length(byte)

1536 1536

Flow Control Disabled Disabled

Tag Tag Aware Tag Aware


Parameter 7-EM4T-1 7-EM4T-3




1536 1536




Parameter 7-EM4T-3

Encapsulation Type 802.1Q




Tag Tag Aware






Configuration Guide


Issue 02 (2009-10-30)



1536 1536




Parameter 7-EM4T-1





Tag Tag Aware


Parameter 7-EM4T-1





Tag Tag Aware

NOTE

l In this example, the FE ports on all the BTSs work in the auto-negotiation mode. Hence, the FE port of eachNE that accesses services must work in the auto-negotiation mode. If the peer Ethernet port works in anothermode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports insidethe network are planned as auto-negotiation.



l In this example, all the services carry VLAN tags. Therefore, the tag attributes of all the ports are tag-aware.



5-77

Information About the IF_ETH Port

Table 5-24 to Table 5-29 provide the information about the IF_ETH ports that carry services.

Table 5-24 IF_ETH port (NE1)

Parameter 3-IFU2-1 4-IFU2-1



Error Frame Discard Enabled Enabled Enabled












Parameter 3-IFU2-1


Tag Tag Aware






Configuration Guide


Issue 02 (2009-10-30)





Parameter 3-IFU2-1


Tag Tag Aware


NOTE

The majority of the backhaul services on the base station are the Internet services. Hence, the error framediscarding function needs to be enabled.

LAGTo improve the reliability of service transmission, NE1 and the BSC are interconnected throughthe LAG formed by two GE links. Table 5-30 provides the planning information.

Table 5-30 LAG

Parameter NE1

LAG Type Static (default value)

Revertive Mode Non-Revertive (default value)

Load Sharing Non-Sharing (default value)

System Priority 32768 (default value)

Main Port 7-EM4F-3

Slave Port 7-EM4F-4

NOTE

In this example, the bandwidth of the Ethernet service to be transmitted is 120 Mbit/s, much smaller than thebandwidth of a GE port. Therefore, you need not configure the link aggregation group to the load sharing modeto increase the bandwidth.

VLAN-Based E-Line ServiceTable 5-31 to Table 5-36 provide the detailed service planning information.



5-79

Table 5-31 VLAN-based E-Line service (NE1)

Parameter NE1

NE2 to BSC

Service ID 1

Service Name NE2toBSC_Vline

Direction UNI-UNI


Source Port 3-IFU2-1

Source C-VLANs 100-149

Sink Port 7-EM4F-3

Sink C-VLANs 100-149


Parameter NE2

NE3 to NE1 BTS1 to NE1

Service ID 1 2

Service Name NE3toNE1_Vline BTS1toNE1_Vline

Direction UNI-UNI UNI-UNI

BPDU Not TransparentlyTransmitted

Not TransparentlyTransmitted

Source Port 7-EM4T-3 7-EM4T-1

Source C-VLANs 110-149 100-109

Sink Port 3-IFU2-1 3-IFU2-1

Sink C-VLANs 110-149 100-109


Parameter NE3

NE4 to NE2 NE5 to NE2

Service ID 1 2

Service Name NE4toNE2_Vline NE5toNE2_Vline



Configuration Guide


Issue 02 (2009-10-30)

Parameter NE3




Source Port 3-IFU2-1 4-IFU2-1


Sink Port 7-EM4T-3 7-EM4T-3

Sink C-VLANs 110-129 130-149


Parameter NE4

BTS2 to NE3 BTS3 to NE3

Service ID 1 2

Service Name BTS2toNE3_Vline BTS3toNE3_Vline







Sink C-VLANs 110-119 120-129


Parameter NE5


Service ID 1 2





Source Port 3-IFU2-1 7-EM4T-1



5-81

Parameter NE5




Sink C-VLANs 140-149 130-139


Parameter NE6

BTS5 to NE5

Service ID 1

Service Name BTS5toNE5_Vline

Direction UNI-UNI



Source C-VLANs 140-149

Sink Port 3-IFU2-1

Sink C-VLANs 140-149

QoS (DiffServ)

DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTSservices be allocated by the service type. Then, the transmission network creates thecorresponding DS domain according to the allocated VLAN priority or DSCP value. EachEthernet port involved in the service must use the same DS configuration.

In this example, the BTS services are allocated with corresponding VLAN priorities accordingto the service type, and the NEs allocate the PHB service classes according to the VLAN priority,as provided in Table 5-37. Each Ethernet port involved in the service uses the same DSconfiguration.


PHB Service Class VLAN Priority Corresponding ServiceType

CS7 7 -

CS6 6 -


Configuration Guide


Issue 02 (2009-10-30)



AF4 4 -



AF1 1 -


NOTE


QoS (Queue Scheduling Mode)Generally, each Ethernet port involved in the service uses the same queue scheduling mode.




CS7 SP

CS6 SP

EF SP





BE SP



5-83

QoS (CAR or Shaping for a Specified Service)


In this example, the CAR processing needs to be performed on the DS edge node in the uplinkdirection (from the BTS to the BSC) of the non-real-time R99 service on each base station (thatis, the service with VLAN priority 2). Table 5-39 lists the CAR parameters.

Table 5-39 CAR parameters

Parameter Value

CIR 4096 kbit/s

CBS 5120 bytes

PIR 8192 kbit/s

PBS 10240 bytes

"Yellow" Packet Processing Mode Mapped to the EF queue

NOTEThe CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more theburst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytesthat are transmitted at CIR and PIR during a 10 ms period.

QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth ofthe aggregation services, you can perform port shaping at the edge node to limit the Ethernetservice traffic that travels to the aggregation node, thus preventing congestion at the aggregationnode.


NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the general attributesof Ethernet ports.



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

7-EM4F-3 7-EM4F-4

Enable Port Enabled Enabled



Max Frame Length(byte) 1536 1536


Parameter Value

7-EM4T-1 7-EM4T-3






Parameter Value

7-EM4T-3

Enable Port Enabled





Parameter Value

7-EM4T-1 7-EM4T-2








5-85

Parameter Value

7-EM4T-1

Enable Port Enabled





Parameter Value

7-EM4T-1

Enable Port Enabled




Step 2 See A.20.3 Setting the Layer 2 Attributes of Ethernet Interfaces and set the Layer 2 attributesof Ethernet ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

7-EM4F-3 7-EM4F-4

TAG Tag Aware Tag Aware


Parameter Value Range

7-EM4T-1 7-EM4T-3



Parameter Value

7-EM4T-3

TAG Tag Aware



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

7-EM4T-1 7-EM4T-2



Parameter Value

7-EM4T-1

TAG Tag Aware


Parameter Value

7-EM4T-1

TAG Tag Aware

Step 3 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the general attributesof IF_ETH ports.


Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1





5-87

Parameter Value

3-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1


Step 4 See A.21.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributesof IF_ETH ports.


Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

3-IFU2-1

Tag Tag Aware


Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1

Tag Tag Aware

Step 5 See A.14.1 Creating a LAG and create the LAG for NE1.The values for the relevant parameters that need to be set in the main interface are provided asfollows.

Parameter Value

LAG No. Select Automatically Assign

LAG Name ToBSC

LAG Type Static


Load Sharing Non-Sharing

System Priority 32768

The values for the relevant parameters that need to be set in the Port Settings tab page areprovided as follows.

Parameter Value

Main Board 7-EM4F

Main Port 3

Selected Slave Ports 7-EM4F-4



5-89

Step 6 See A.26.2 Configuring the E-Line Service and configure the E-Line services.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

NE2 to BTS

Service ID 1


Direction UNI-UNI



Source VLANs 100-149

Sink Port 7-EM4F-3

Sink VLANs 100-149


Parameter Value


Service ID 1 2






Source VLANs 110-149 100-109


Sink VLANs 110-149 100-109


Parameter Value


Service ID 1 2

Service Name NE4toNE2_Vline NE5toNE2_Vline



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value




Source Port 3-IFU2-1 4-IFU2-1

Source VLANs 110-129 130-149

Sink Port 7-EM4T-3 7-EM4T-3

Sink VLANs 110-129 130-149


Parameter Value


Service ID 1 2






Source VLANs 110-119 120-129


Sink VLANs 110-119 120-129


Parameter Value


Service ID 1 2






Source VLANs 140-149 130-139




5-91

Parameter Value


Sink VLANs 140-149 130-139


Parameter Value

BTS5 to NE5

Service ID 1


Direction UNI-UNI



Source VLANs 140-149

Sink Port 3-IFU2-1

Sink VLANs 140-149


The values for the related parameters that need to be set in the main interface are provided asfollows.

Parameter Value



Packet Type cvlan

The values for the related parameters that need to be set in the Ingress Mapping Relation tabpage are provided as follows.


0 BE

1 AF11

2 AF21

3 AF31


Configuration Guide


Issue 02 (2009-10-30)


4 AF41

5 EF

6 CS6

7 CS7

The values for the related parameters that need to be set in the Egress Mapping Relation tabpage are provided as follows.


BE 0

AF11 1

AF21 2

AF31 3

AF41 4

EF 5

CS6 6

CS7 7

NOTE


The values for the related parameters that need to be set in the Application Port tab page areprovided as follows.

Parameter

Value


SelectedPort

3-IFU2-17-EM4F-3

7-EM4T-17-EM4T-33-IFU2-1

3-IFU2-14-IFU2-17-EM4T-3

3-IFU2-17-EM4T-17-EM4T-2

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-1

NOTE

The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DSdomain that is created in this step. Therefore, you can skip this step.



5-93

Step 8 See A.16.3 Creating a Port Policy and create the port policy.l The values for the related parameters of NE2, NE4, NE5, and NE6 are provided as follows.

Parameter Value

Policy ID 1 2

Policy Name Port_Comm Port_Car

Grooming Police AfterReloading

SP (CS7, CS6, and EF)WRR (AF4 to AF1)SP (BE)



5 (AF4)60 (AF3)30 (AF2)5 (AF1)

Bandwidth Limit Disabled (for all PHBservice classes)

Disabled (for all PHBservice classes)

l The values for the related parameters of NE1 and NE3 are provided as follows.

Parameter Value

Policy ID 1


Grooming Police After Reloading SP (CS7, CS6, and EF)WRR (AF4 to AF1)SP (BE)



Step 9 See A.16.4 Creating the Traffic and create the traffic on NE2, NE4, NE5, and NE6.


Parameter Value

Port_Car

Traffic Classification ID 1

ACL Action Permit


Configuration Guide


Issue 02 (2009-10-30)

The values for the related parameters that need to be set in the INGRESS tab page are providedas follows.

Parameter Value

Port_Car

Match Type CVlan priority

Match Value 2

CoS -

Bandwidth Limit Enabled

CIR(kbit/s) 4096

PIR(kbit/s) 8192

CBS(byte) 5120

PBS(byte) 10240

Handling Mode Discard (red)Remark (yellow)Pass (green)

Relabeled CoS - (red)EF (yellow)- (green)

The values for the related parameters that need to be set in the EGRESS tab page are providedas follows.

Parameter Value

Port_Car

Bandwidth Limit Disabled



Parameter Value

Port_Comm

Port 3-IFU2-17-EM4F-3



5-95


Parameter Value

Port_Comm Port_Car

Port 7-EM4T-33-IFU2-1

7-EM4T-1


Parameter Value

Port_Comm

Port 3-IFU2-14-IFU2-17-EM4T-3


Parameter Value

Port_Comm Port_Car

Port 3-IFU2-1 7-EM4T-17-EM4T-2


Parameter Value

Port_Comm Port_Car

Port 3-IFU2-14-IFU2-1

7-EM4T-1


Parameter Value

Port_Comm Port_Car

Port 3-IFU2-1 7-EM4T-1

Step 11 See A.17.1 Creating an MD and configure the MD for NE1, NE2, NE4, NE5, and NE6.



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE1 NE2 NE4 NE5 NE6


EdgeNE EdgeNE EdgeNE EdgeNE EdgeNE


4 4 4 4 4

Step 12 See A.17.2 Creating an MA and create the maintenance association (MA) for NE1, NE2, NE4,NE5, and NE6.


Parameter Value



MaintenanceAssociationName

BTS1_Vline

BTS2_Vline

BTS3_Vline

BTS4_Vline

BTS5_Vline

RelevantService

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline

CC TestTransmitPeriod(ms)

1s 1s 1s 1s 1s


Parameter Value

Maintenance Domain Name EdgeNE

Maintenance Association Name BTS1_Vline

Relevant Service 2-BTS1toNE1_Vline

CC Test Transmit Period(ms) 1s


Parameter Value


EdgeNE EdgeNE



5-97

Parameter Value


BTS2_Vline BTS3_Vline

Relevant Service 1-BTS2toNE3_Vline 2-BTS3toNE3_Vline


1s 1s


Parameter Value






Parameter Value





Step 13 See A.17.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.l The values for the related parameters of NE1 are provided as follows.

Parameter Value




BTS1_Vline

BTS2_Vline

BTS3_Vline

BTS4_Vline

BTS5_Vline

Board 7-EM4F 7-EM4F 7-EM4F 7-EM4F 7-EM4F

Port 7-EM4F-3 7-EM4F-3 7-EM4F-3 7-EM4F-3 7-EM4F-3

VLAN 100 110 120 130 140

MP ID 101 102 103 104 105


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

Direction Ingress Ingress Ingress Ingress Ingress

CC Status Active Active Active Active Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN 100

MP ID 201

Direction Ingress

CC Status Active


Parameter Value


EdgeNE EdgeNE



Board 7-EM4T 7-EM4T

Port 7-EM4T-1 7-EM4T-2

VLAN 110 120

MP ID 401 402

Direction Ingress Ingress



Parameter Value



Board 7-EM4T



5-99

Parameter Value

Port 7-EM4T-1

VLAN 130

MP ID 501

Direction Ingress

CC Status Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN 140

MP ID 601

Direction Ingress

CC Status Active

Step 14 See A.17.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,NE2, NE4, NE5, and NE6.

The values for the related parameters of NE1 are provided as follows.

Parameter Value




BTS1_Vline BTS2_Vline BTS3_Vline BTS4_Vline BTS5_Vline

RemoteMaintenance Point ID(_e.g:1,3-6)

201 401 402 501 601



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value



Remote Maintenance Point ID(_e.g:1,3-6) 101


Parameter Value


EdgeNE EdgeNE




102 103


Parameter Value





Parameter Value




Step 15 See A.26.5 Testing the Ethernet Service and test the E-Line services on NE1.

l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP andthe MEP whose MP ID is 201 as the sink MEP.




5-101




There should be no packets lost during the LB tests.

----End

5.6 Configuration Example (QinQ-Based E-Line Service)This topic considers a QinQ-based E-line service as an example to describe how to configurethe Ethernet service according to the network planning information.





Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure the Ethernet services according to the actual requirements. The VLANsused by the services on a BTS is allocated by the BTS. Hence, the VLANs of services on differentBTSs may be the same. To solve this problem, the BSC allocates an S-VLAN for each BTS,and the S-VLANs on the entire network are planned in a unified manner, as shown in Figure5-18. Hence, the QinQ-based E-Line service can be adopted for service transmission.

Figure 5-18 Networking diagram (QinQ-based E-Line service)

BTS3SVLAN 120

BSCNE1NE2NE3

NE5

NE4

NE6

FE

FE

FEFE

FE

GE GE

BTS5SVLAN 140

BTS1(SVLAN 100)

BTS2SVLAN 110

BTS4SVLAN 130


Configuration Guide


Issue 02 (2009-10-30)

NOTE

In this example, the BSC needs to be capable of processing the S-VLAN tag.


Ethernet Port

Table 5-40 to Table 5-45 provide the information about each Ethernet port involved in theservice.



Encapsulation Type QinQ QinQ



1536 1536


QinQ Type Domain 0x8100 0x8100



Encapsulation Type Null QinQ



1536 1536


QinQ Type Domain - 0x88a8


Parameter 7-EM4T-3

Encapsulation Type QinQ




5-103

Parameter 7-EM4T-3



QinQ Type Domain 0x88a8



Encapsulation Type Null Null



1536 1536


QinQ Type Domain - -


Parameter 7-EM4T-1





QinQ Type Domain -


Parameter 7-EM4T-1





QinQ Type Domain -


Configuration Guide


Issue 02 (2009-10-30)

NOTE

l If the Ethernet services on each BTS do not contain any untagged frames, you can set EncapsulationType to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.




l In this example, the SVLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ TypeDomain to 0x8100 for the two GE ports connecting to the BSC. The other NNI ports connect to internalequipment. Hence, you need to set QinQ Type Domain to 0x88a8 for the other NNI ports.

Information About the IF_ETH PortsTable 5-46 to Table 5-51 provide the information about the IF_ETH ports that carry services.




Tag 0x88a8 0x88a8





Tag 0x88a8 0x88a8





Tag 0x88a8 0x88a8




5-105


Parameter 3-IFU2-1


Tag 0x88a8





Tag 0x88a8 0x88a8



Parameter 3-IFU2-1


Tag 0x88a8


NOTE

l The IF_ETH ports connect to internal equipment. Hence, you need to set QinQ Type Domain to 0x88a8for the IF_ETH ports.

l The majority of the backhaul services on the base station are Internet services. Hence, the error framediscarding function needs to be enabled.

LAGTo improve the reliability of service transmission, NE1 and the BSC are interconnected throughthe LAG formed by two GE links. Table 5-52 provides the planning information.

Table 5-52 LAG

Parameter NE1





Configuration Guide


Issue 02 (2009-10-30)

Parameter NE1


Main Port 7-EM4F-3

Slave Port 7-EM4F-4

NOTE


QinQ-Based E-Line ServiceTable 5-53 to Table 5-58 provide the detailed service planning information.

Table 5-53 QinQ-based E-Line service (NE1)

Parameter NE1

BTS1 toBSC

BTS2 toBSC

BTS3 toBSC

BTS4 toBSC

BTS5 toBSC

Service ID 1 2 3 4 5

ServiceName

BTS1_Qline BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI NNI-NNI

BPDU NotTransparentlyTransmitted

NotTransparentlyTransmitted




Source Port - - - - -

Source C-VLANs

- - - - -

Source QinQlink

ID: 6Port: 3-IFU2-1S-VLAN:100





Sink QinQlink

ID: 1Port: 7-EM4F-3S-VLAN:100







5-107


Parameter NE2

BTS1 toNE1

BTS2 toNE1

BTS3 toNE1

BTS4 toNE1

BTS5 toNE1


ServiceName


Direction UNI-NNI NNI-NNI NNI-NNI NNI-NNI NNI-NNI






Source Port 7-EM4T-1 - - - -

Source C-VLANs

Blank - - - -

Source QinQlink

- ID: 6Port: 7-EM4T-3S-VLAN:110

ID: 7Port: 7-EM4T-3S-VLAN:120



Sink QinQlink







Parameter NE3

BTS2 to NE1 BTS3 to NE1 BTS4 to NE1 BTS5 to NE1

Service ID 1 2 3 4

Service Name BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI





Source Port - - - -


Configuration Guide


Issue 02 (2009-10-30)

Parameter NE3


Source C-VLANs

- - - -

Source QinQlink

ID: 5Port: 3-IFU2-1S-VLAN: 110




Sink QinQ link ID: 1Port: 7-EM4T-3S-VLAN: 110

ID: 2Port: 7-EM4T-3S-VLAN: 120




Parameter NE4


Service ID 1 2

Service Name BTS2_Qline BTS3_Qline

Direction UNI-NNI UNI-NNI




Source C-VLANs Blank Blank

Source QinQ link - -

Sink QinQ link ID: 1Port: 3-IFU2-1S-VLAN: 110



Parameter NE5


Service ID 1 2


Direction UNI-NNI NNI-NNI



5-109

Parameter NE5




Source Port 7-EM4T-1 -

Source C-VLANs Blank -

Source QinQ link - ID: 3Port: 3-IFU2-1S-VLAN: 140




Parameter NE6

BTS5 to NE5

Service ID 1

Service Name BTS5_Qline

Direction UNI-NNI



Source C-VLANs Blank

Source QinQ link -


QoS (DiffServ)DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTSservices be allocated by the service type. Then, the transmission network creates thecorresponding DS domain according to the allocated VLAN priority or DSCP value. EachEthernet port involved in the service must use the same DS configuration.

In this example, the BTS services are allocated with corresponding VLAN priorities accordingto the service type, and the NEs allocate the PHB service classes according to the VLAN priority,


Configuration Guide


Issue 02 (2009-10-30)

as provided in Table 5-59. Each Ethernet port involved in the service uses the same DSconfiguration.



CS7 7 -

CS6 6 -


AF4 4 -



AF1 1 -


NOTE







CS7 SP

CS6 SP

EF SP



5-111






BE SP





Parameter Value

CIR 4096 kbit/s

CBS 5120 bytes

PIR 8192 kbit/s

PBS 10240 bytes


In this example, the shaping processing needs to be performed in the uplink direction (from theBTS to the BSC) of the real-time OM and HSDPA services on each base station. Table 5-62lists the shaping parameters.

Table 5-62 Shaping parameters

Parameter Value

CIR 2048 kbit/s

CBS 2560 bytes

PIR 4096 kbit/s

PBS 5120 bytes


Configuration Guide


Issue 02 (2009-10-30)




NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the general attributesof Ethernet ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

7-EM4F-3 7-EM4F-4






Parameter Value

7-EM4T-1 7-EM4T-3


Encapsulation Type Null QinQ






5-113

Parameter Value

7-EM4T-3

Enable Port Enabled





Parameter Value

7-EM4T-1 7-EM4T-2






Parameter Value

7-EM4T-1

Enable Port Enabled





Parameter Value

7-EM4T-1

Enable Port Enabled




Step 2 See A.20.3 Setting the Layer 2 Attributes of Ethernet Interfaces and set Layer 2 attributesof Ethernet ports for NE1.


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

7-EM4F-3 7-EM4F-4

QinQ Type Domain 81 00 81 00

Step 3 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the general attributesof IF_ETH ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1





5-115

Parameter Value

3-IFU2-1



Parameter Value


LAG Name ToBSC

LAG Type Static





Parameter Value

Main Board 7-EM4F

Main Port 3


Step 5 See A.26.1 Configuring the QinQ Link and configure a QinQ link.l The values for the related parameters of NE1 are provided as follows.

QinQ Link ID Board Port S-Vlan ID

1 7-EM4F 3 100

2 7-EM4F 3 110

3 7-EM4F 3 120

4 7-EM4F 3 130

5 7-EM4F 3 140

6 3-IFU2 1 100

7 3-IFU2 1 110


Configuration Guide


Issue 02 (2009-10-30)


8 3-IFU2 1 120

9 3-IFU2 1 130

10 3-IFU2 1 140



1 3-IFU2 1 100

2 3-IFU2 1 110

3 3-IFU2 1 120

4 3-IFU2 1 130

5 3-IFU2 1 140

6 7-EM4T 3 110

7 7-EM4T 3 120

8 7-EM4T 3 130

9 7-EM4T 3 140



1 7-EM4T 3 110

2 7-EM4T 3 120

3 7-EM4T 3 130

4 7-EM4T 3 140

5 3-IFU2 1 110

6 3-IFU2 1 120

7 4-IFU2 1 130

8 4-IFU2 1 140



1 3-IFU2 1 110

2 3-IFU2 1 120



5-117



1 4-IFU2 1 130

2 4-IFU2 1 140

3 3-IFU2 1 140



1 3-IFU2 1 140

Step 6 See A.26.2 Configuring the E-Line Service and configure the E-Line services.


Parameter Value

BTS1 toBSC

BTS2 toBSC

BTS3 toBSC

BTS4 toBSC

BTS5 toBSC


ServiceName

BTS1_Qline

BTS2_Qline

BTS3_Qline

BTS4_Qline

BTS5_Qline







QinQ LinkID 1

6 7 8 9 10

QinQ LinkID 2

1 2 3 4 5


Parameter Value

BTS1 toNE1

BTS2 toNE1

BTS3 toNE1

BTS4 toNE1

BTS5 toNE1


ServiceName

BTS1_Qline

BTS2_Qline

BTS3_Qline

BTS4_Qline

BTS5_Qline


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

BTS1 toNE1

BTS2 toNE1

BTS3 toNE1

BTS4 toNE1

BTS5 toNE1







Source Port 7-EM4T-1 - - - -

SourceVLANs

Blank - - - -

QinQ LinkID

1 - - - -

QinQ LinkID 1

- 6 7 8 9

QinQ LinkID 2

- 2 3 4 5


Parameter Value


Service ID 1 2 3 4

Service Name BTS2_Qline BTS3_Qline BTS4_Qline BTS5_Qline

Direction NNI-NNI NNI-NNI NNI-NNI NNI-NNI





QinQ Link ID1

5 6 7 8

QinQ Link ID2

1 2 3 4


Parameter Value


Service ID 1 2



5-119

Parameter Value



Direction UNI-NNI UNI-NNI




Source VLANs Blank Blank

QinQ Link ID 1 2


Parameter Value


Service ID 1 2


Direction UNI-NNI NNI-NNI



Source Port 7-EM4T-1 -

Source VLANs Blank -

QinQ Link ID 1 -

QinQ Link ID 1 - 3

QinQ Link ID 2 - 2


Parameter Value

BTS5 to NE5

Service ID 1

Service Name BTS5_Qline

Direction UNI-NNI




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

BTS5 to NE5

Source VLANs Blank

QinQ Link ID 1



Parameter Value



Packet Type cvlan



0 0 BE

1 1 AF11

2 2 AF21

3 3 AF31

4 4 AF41

5 5 EF

6 6 CS6

7 7 CS7



BE 0 0

AF11 1 1

AF21 2 2



5-121


AF31 3 3

AF41 4 4

EF 5 5

CS6 6 6

CS7 7 7

NOTE



Parameter

Value


SelectedPort

3-IFU2-17-EM4F-3

7-EM4T-17-EM4T-33-IFU2-1

3-IFU2-14-IFU2-17-EM4T-3

3-IFU2-17-EM4T-17-EM4T-2

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-1

Step 8 See A.16.2 Changing the Ports That Use the DS Domain and change the ports that use theDS domain.


Selected Port Packet Type

3-IFU2-1 svlan

7-EM4F-3 svlan

svlan



7-EM4T-1 cvlan

7-EM4T-3 svlan

3-IFU2-1 svlan



Configuration Guide


Issue 02 (2009-10-30)


3-IFU2-1 svlan

4-IFU2-1 svlan

7-EM4T-3 svlan



7-EM4T-1 cvlan

7-EM4T-2 cvlan

3-IFU2-1 svlan



3-IFU2-1 svlan

4-IFU2-1 svlan

7-EM4T-1 cvlan



3-IFU2-1 svlan

7-EM4T-1 cvlan

Step 9 See A.16.3 Creating a Port Policy and create the port policy.l The values for the related parameters of NE1 and NE3 are provided as follows.

Parameter Value

Policy ID 1





5-123

Parameter Value




Parameter Value

Policy ID 1 2 3

Policy Name Port_Comm Port_Car Port_Shaping

Grooming PoliceAfter Reloading

SP (CS7, CS6, andEF)WRR (AF4 to AF1)SP (BE)




5 (AF4)60 (AF3)30 (AF2)5 (AF1)

5 (AF4)60 (AF3)30 (AF2)5 (AF1)

Bandwidth Limit Disabled (for allPHB serviceclasses)

Disabled (for allPHB serviceclasses)



Parameter Value

Policy ID 1 2

Policy Name Port_Car Port_Shaping





5 (AF4)60 (AF3)30 (AF2)5 (AF1)




Configuration Guide


Issue 02 (2009-10-30)

Step 10 See A.16.4 Creating the Traffic and create the traffic for NE2, NE4, NE5, and NE6.l Parameters of NE2

The values for the related parameters that need to be set in the main interface are providedas follows.

Parameter Value

Port_Car Port_Shaping

Traffic Classification ID 1 1

ACL Action Permit Permit

The values for the related parameters that need to be set in the INGRESS tab page areprovided as follows.

Parameter Value


Match Type CVlan priority SVlan ID SVlan priority

Match Value 2 100 3

CoS - -

Bandwidth Limit Enabled Disabled

CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-


-




5-125

Parameter Value


Bandwidth Limit Disabled Enabled

CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560

PBS(byte) - 5120

l Parameters of NE4


Parameter Value


TrafficClassification ID

1 1 2

ACL Action Permit Permit Permit


Parameter Value

Port_Car Port_Shaping (TrafficClassification ID=1)

Port_Shaping (TrafficClassification ID=2)

MatchType

CVlanpriority

SVlan ID SVlanpriority

SVlan ID SVlanpriority

MatchValue

2 110 3 120 3

CoS - - -

BandwidthLimit

Enabled Disabled Disabled

CIR(kbit/s) 4096 - -

PIR(kbit/s) 8192 - -

CBS(byte) 5120 - -

PBS(byte) 10240 - -


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value



HandlingMode

Discard(red)Remark(yellow)Pass (green)

- -

RelabeledCoS

- (red)EF (yellow)- (green)

- -


Parameter Value

Port_Car Port_Shaping(TrafficClassificationID=1)

Port_Shaping(TrafficClassificationID=2)

Bandwidth Limit Disabled Enabled Enabled

CIR(kbit/s) - 2048 2048

PIR(kbit/s) - 4096 4096

CBS(byte) - 2560 2560

PBS(byte) - 5120 5120

l Parameters of NE5


Parameter Value







5-127

Parameter Value



Match Value 2 130 3

CoS - -


CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-


-


Parameter Value



CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560

PBS(byte) - 5120

l Parameters of NE6:


Parameter Value




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value




Parameter Value



Match Value 2 140 3

CoS - -


CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-


-


Parameter Value



CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560

PBS(byte) - 5120



5-129

Step 11 See A.16.5 Setting the Port That Uses the Port Policy and set the ports that use the port policy.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

Port_Comm



Parameter Value

Port_Comm Port_Car Port_Shaping

Port 7-EM4T-3 7-EM4T-1 3-IFU2-1


Parameter Value

Port_Comm



Parameter Value


Port 7-EM4T-17-EM4T-2

3-IFU2-1


Parameter Value


Port 3-IFU2-1 7-EM4T-1 4-IFU2-1


Parameter Value




Configuration Guide


Issue 02 (2009-10-30)



Parameter Value

NE1 NE2 NE4 NE5 NE6




4 4 4 4 4

Step 13 See A.17.2 Creating an MA and create the MA for NE1, NE2, NE4, NE5, and NE6.


Parameter Value




BTS1_Qline

BTS2_Qline

BTS3_Qline

BTS4_Qline

BTS5_Qline

RelevantService

1-BTS1_Qline

2-BTS2_Qline

3-BTS3_Qline

4-BTS4_Qline

5-BTS5_Qline


1s 1s 1s 1s 1s


Parameter Value


Maintenance Association Name BTS1_Qline

Relevant Service 1-BTS1_Qline





5-131

Parameter Value


EdgeNE EdgeNE


BTS2_Qline BTS3_Qline

Relevant Service 1-BTS2_Qline 2-BTS3_Qline


1s 1s


Parameter Value






Parameter Value





Step 14 See A.17.3 Creating an MEP Point and create the MEP for NE1, NE2, NE4, NE5, and NE6.


Parameter Value




BTS1_Qline

BTS2_Qline

BTS3_Qline

BTS4_Qline

BTS5_Qline

Board 7-EM4F 7-EM4F 7-EM4F 7-EM4F 7-EM4F

Port 7-EM4F-3 7-EM4F-3 7-EM4F-3 7-EM4F-3 7-EM4F-3


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

VLAN 100 110 120 130 140

MP ID 101 102 103 104 105




Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN -

MP ID 201

Direction Ingress

CC Status Active


Parameter Value


EdgeNE EdgeNE



Board 7-EM4T 7-EM4T


VLAN - -

MP ID 401 402




Parameter Value




5-133

Parameter Value


Board 7-EM4T

Port 7-EM4T-1

VLAN -

MP ID 501

Direction Ingress

CC Status Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN -

MP ID 601

Direction Ingress

CC Status Active

Step 15 See A.17.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1,NE2, NE4, NE5, and NE6.


Parameter Value






201 401 402 501 601


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value





Parameter Value


EdgeNE EdgeNE




102 103


Parameter Value





Parameter Value




Step 16 See A.26.5 Testing the Ethernet Service and test the E-Line services on NE1.l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and

the MEP whose MP ID is 201 as the sink MEP.



5-135





There should be no packets lost during the LB tests.

----End

5.7 Configuration Example (802.1d-Bridge-Based E-LANService)

This topic considers an 802.1d-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.





Based on 5.7.1 Networking Diagram, configure the Ethernet services according to the actualrequirements. The service requirements are as follows:

l The BTS services need to be transparently transmitted.

l The Ethernet services on the ring network need to be protected.

To meet the preceding requirements, the 802.1d-bridge-based E-LAN service is adopted totransmit the BTS services, and ERPS is adopted to protect services on the ring network, as shownin Figure 5-19.


Configuration Guide


Issue 02 (2009-10-30)

Figure 5-19 Networking diagram (802.1d-bridge-based E-LAN service)

BTS

BTS NE1

NE3

NE2 NE4

BSC

BTS

BTS

GE

FE

FE

FE

FE

802.1d bridge

802.1d bridge

802.1d bridge

802.1d bridge

ERPS


Ethernet Port







1536 1536


Loopback Check Disabled Disabled

Loopback Port Shutdown Disabled Disabled

Enabling Broadcast PacketSuppression

Disabled Disabled

Broadcast PacketSuppression Threshold

- -



5-137






1536 1536





Disabled Disabled


- -


Parameter 7-EM4T-1





Loopback Check Disabled

Loopback Port Shutdown Disabled (default value)

Enabling Broadcast Packet Suppression Disabled (default value)

Broadcast Packet Suppression Threshold -


Parameter 7-EM4T-1






Configuration Guide


Issue 02 (2009-10-30)

Parameter 7-EM4T-1

Loopback Check Disabled (default value)

Loopback Port Shutdown Disabled (default value)

Enabling Broadcast Packet Suppression Disabled (default value)


NOTE

l In this example, the FE/GE port on the BTS/BSC works in the auto-negotiation mode. Hence, the FE/GEport of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet portworks in another mode, the local Ethernet port must work in the same mode. The working modes of theEthernet ports inside the network are planned as auto-negotiation.



l In this example, the loopback check, loopback port shutdown, and broadcast packet suppression functionsneed not be enabled.

Information About the IF_ETH PortsTable 5-67 to Table 5-70 provide the information about the IF_ETH ports that carry services.

Table 5-67 IF_ETH port










5-139









NOTE


LAG

To improve the reliability of service transmission, NE1 and the BSC are interconnected throughthe LAG formed by two GE links. Table 5-71 provides the planning information.

Table 5-71 LAG

Parameter NE1





Main Port 7-EM4T-3

Slave Port 7-EM4T-4

NOTE


ERPS Instance

Table 5-72 provides the information about ERPS.


Configuration Guide


Issue 02 (2009-10-30)

Table 5-72 ERPS instance

Parameter NE1 NE2 NE3 NE4

East Port 4-IFU2-1 4-IFU2-1 4-IFU2-1 4-IFU2-1

West Port 3-IFU2-1 3-IFU2-1 3-IFU2-1 3-IFU2-1

RPLOwnerRing Node Flag

No No Yes No

RPL Port - - 4-IFU2-1 -

Control VLAN 4093 4093 4093 4093

Packet TransmitInterval

5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)

Entity Level 4 (default value) 4 (default value) 4 (default value) 4 (default value)

WTR Time 600s (defaultvalue)

600s (defaultvalue)

600s (defaultvalue)

600s (defaultvalue)

Guard Time 500 ms (defaultvalue)

500 ms (defaultvalue)



Hold-Off Time 0s (defaultvalue)

0s (defaultvalue)

0s (defaultvalue)

0s (defaultvalue)

NOTE

l In this example, all the services are aggregated on NE1. Hence, the NE that is farthest from NE1 needs tofunction as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link isrelatively even.

l The control VLAN needs to use a VLAN that is not used by any service. Considering that the inband DCNuses VLAN 4094, it is recommended that the control VLAN use VLAN 4093.

l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally use the defaultvalues.

l

802.1d-Bridge-Based E-LAN Service


Table 5-73 802.1d-bridge-based E-LAN service


Service ID 1 1 1 1

Service Name Dlan Dlan Dlan Dlan

Tag Type Tag-Transparent

Tag-Transparent

Tag-Transparent

Tag-Transparent



5-141


Self-LearningMAC Address

Enabled Enabled Enabled Enabled

MAC AddressLearning Mode

SVL SVL SVL SVL

Mounted UNIPort

7-EM4T-33-IFU2-14-IFU2-1

7-EM4T-17-EM4T-23-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

NOTE

In this example, ERPS is adopted to prevent network loop. Therefore, the split horizon group cannot be used.

QoS (DiffServ)

DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTSservices be allocated by the service type. Then, the transmission network creates thecorresponding DS domain according to the allocated VLAN priority or DSCP value. EachEthernet port involved in the service must use the same DS configuration.




CS7 7 -

CS6 6 -


AF4 4 -




Configuration Guide


Issue 02 (2009-10-30)


AF1 1 -


NOTE






CS7 SP

CS6 SP

EF SP





BE SP

QoS (CAR or Shaping For a Specified Service)To perform the CAR or shaping processing for a specified service, you need to configure theDS edge node accordingly.

In this example, no CAR or shaping processing needs to be performed on the services transmittedfrom the BTS.

QoS (Port Shaping)If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth ofthe aggregation services, you can perform port shaping at the edge node to limit the Ethernet



5-143

service traffic that travels to the aggregation node, thus preventing congestion at the aggregationnode.


NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the basic attributesof Ethernet ports.l The values for the related parameters of NE1 are provided as follows.


7-EM4T-3 7-EM4T-4







7-EM4T-1 7-EM4T-2







7-EM4T-1

Enable Port Enabled




Configuration Guide


Issue 02 (2009-10-30)


7-EM4T-1


Step 2 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the basic attributes ofthe IF_ETH ports.

The values for the related parameters of each NE are provided as follows.


3-IFU2-1 4-IFU2-1


Step 3 See A.14.1 Creating a LAG and create the LAG on NE1.



LAG No. Select Automatically Assign.

LAG Name ToBSC

LAG Type Static




The values for the related parameters that need to be set in Port Settings are provided as follows.


Main Board 7-EM4T

Main Port 3

Selected Slave Ports 7-EM4T-4

Step 4 See A.11.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.




5-145


NE1 NE2 NE3 NE4

ERPS ID 1 1 1 1




No No Yes No


Control VLAN 4093 4093 4093 4093

Step 5 See A.26.4 Configuring the E-LAN Service and configure the E-LAN services.

l Parameters of NE1



Service ID 1

Service Name Dlan


Self-Learning MAC Address Enabled

The values for the related parameters that need to be set in the UNI tab page are provided asfollows.

Port SVLAN VLANs/CVLAN

7-EM4T-3 - Blank

3-IFU2-1 - Blank

4-IFU2-1 - Blank

l Parameters of NE2



Service ID 1

Service Name Dlan


Configuration Guide


Issue 02 (2009-10-30)






7-EM4T-1 - Blank

7-EM4T-2 - Blank

3-IFU2-1 - Blank

4-IFU2-1 - Blank

l Parameters of NE3 and NE4



Service ID 1

Service Name Dlan





7-EM4T-1 - Blank

3-IFU2-1 - Blank

4-IFU2-1 - Blank






Packet Type ip-dscp



5-147



0 BE

1 AF11

2 AF21

3 AF31

4 AF41

5 EF

6 CS6

7 CS7



BE 0

AF11 1

AF21 2

AF31 3

AF41 4

EF 5

CS6 6

CS7 7

NOTE


The values for the related parameters that need to be set in the Apply Port tab page are providedas follows.


Configuration Guide


Issue 02 (2009-10-30)


NE1 NE2 NE3 NE4

Selected Port 7-EM4T-33-IFU2-14-IFU2-1

7-EM4T-17-EM4T-23-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

Step 7 See A.16.3 Creating a Port Policy and create the port policy.



Policy ID 1





Step 8 See A.16.5 Setting the Port That Uses the Port Policy and set the port that uses the port policy.l The values for the related parameters of NE1 are provided as follows.


Port_Comm

Port 7-EM4T-33-IFU2-14-IFU2-1




5-149


Port_Comm

Port 7-EM4T-17-EM4T-23-IFU2-14-IFU2-1



Port_Comm


Step 9 See A.17.1 Creating an MD and create the MDs.



NE1 NE2 NE3 NE4

MaintenanceDomain Name

EdgeNE EdgeNE EdgeNE EdgeNE

MaintenanceDomain Level

4 4 4 4

Step 10 See A.17.2 Creating an MA and create the MA.



NE1 NE2 NE3 NE4




Dlan Dlan Dlan Dlan

RelevantService

1-Dlan 1-Dlan 1-Dlan 1-Dlan


Configuration Guide


Issue 02 (2009-10-30)


NE1 NE2 NE3 NE4


1s 1s 1s 1s

Step 11 See A.17.3 Creating an MEP Point and create the MEP points.



NE1 NE2 NE3 NE4




Dlan Dlan Dlan Dlan Dlan

Board 7-EM4T 7-EM4T 7-EM4T 7-EM4T 7-EM4T

Port 7-EM4T-3 7-EM4T-1 7-EM4T-2 7-EM4T-1 7-EM4T-1

VLAN - - - - -

MP ID 101 201 202 301 401



Step 12 See A.17.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1 toNE4.


Parameter Value




Dlan Dlan Dlan Dlan

RemoteMaintenancePoint ID(_e.g:1,3-6)

201 202 301 401



5-151


Parameter Value


Maintenance Association Name Dlan



Parameter Value





Parameter Value




Step 13 See A.26.5 Testing the Ethernet Service and test the E-LAN services.l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and

the MEP whose MP ID is 201 as the sink MEP.l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and



the MEP whose MP ID is 401 as the sink MEP.There should be no packets lost during the LB tests.

----End


Configuration Guide


Issue 02 (2009-10-30)

5.8 Configuration Example (802.1q-Bridge-Based E-LANService)

This topic considers an 802.1q-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.





Based on 3.6 Configuration Example (Radio Links on the Hybrid Microwave RingNetwork), configure the Ethernet services according to the actual requirements. The servicerequirements are as follows:

l On the network, services transmitted by each BTS carry VLAN tags, and the VLAN IDson the entire network are planned in a unified manner. In addition, services need to beisolated by VLAN.


To meet the preceding requirements, the 802.1q-bridge-based E-LAN service is adopted totransmit the BTS services, and ERPS is adopted to protect services on the ring network, as shownin Figure 5-20.

Figure 5-20 Networking diagram (802.1q-bridge-based E-LAN service)

BTS1(VLAN 100-109)

NE1

NE3

NE2 NE4

BSC

GE

FE

FE

FE

FE

802.1q bridge

802.1q bridge

802.1q bridge

802.1q bridge

ERPS

BTS2(VLAN 110-119)

BTS3(VLAN 120-129)

BTS4(VLAN 130-139)



5-153








1536 1536






Disabled Disabled


- -






1536 1536






Disabled Disabled


Configuration Guide


Issue 02 (2009-10-30)



- -


Parameter 7-EM4T-1





TAG Tag Aware


Loopback Port Shutdown Disabled

Enabling Broadcast Packet Suppression Disabled



Parameter 7-EM4T-1





TAG Tag Aware







5-155

NOTE







Table 5-80 provides the information about the IF_ETH ports that carry services.

















Configuration Guide


Issue 02 (2009-10-30)






NOTE


LAG


Table 5-84 LAG

Parameter NE1





Main Port 7-EM4T-3

Slave Port 7-EM4T-4

NOTE


ERPS Instance








5-157



No No Yes No


Control VLAN 4093 4093 4093 4093


5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)



600s (defaultvalue)

600s (defaultvalue)

600s (defaultvalue)






0s (defaultvalue)

0s (defaultvalue)

0s (defaultvalue)

NOTE




l

802.1q-Bridge-Based E-LAN Service


Table 5-86 802.1q-bridge-based E-LAN service


Service ID 1 1 1 1

Service Name Qlan Qlan Qlan Qlan

Tag Type C-Awared C-Awared C-Awared C-Awared




IVL IVL IVL IVL


Configuration Guide


Issue 02 (2009-10-30)


Mounted UNIPort

7-EM4T-3(VLAN ID:100-139)3-IFU2-1(VLAN ID:100-139)4-IFU2-1(VLAN ID:100-139)

7-EM4T-1(VLAN ID:100-109)7-EM4T-2(VLAN ID:110-119)3-IFU2-1(VLAN ID:100-139)4-IFU2-1(VLAN ID:100-139)



NOTE

In this example, ERPS is adopted to prevent network loop. Therefore, the split horizon group cannot be used.





CS7 7 -

CS6 6 -


AF4 4 -




5-159



AF1 1 -


NOTE






CS7 SP

CS6 SP

EF SP





BE SP

QoS (CAR or Shaping for a Specified Service)To perform the CAR or shaping processing for a specified service, you need to configure theDS edge node accordingly.



Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

CIR 4096 kbit/s

CBS 5120 bytes

PIR 8192 kbit/s

PBS 10240 bytes





NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the basic attributesof Ethernet ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

7-EM4T-3 7-EM4T-4







5-161


Parameter Value

7-EM4T-1 7-EM4T-2






Parameter Value

7-EM4T-1

Enable Port Enabled





Parameter Value

7-EM4T-3 7-EM4T-4



Parameter Value

7-EM4T-1 7-EM4T-2



Parameter Value

7-EM4T-1

TAG Tag Aware


Configuration Guide


Issue 02 (2009-10-30)

Step 3 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the attributes of theIF_ETH ports.


Parameter Value

3-IFU2-1 4-IFU2-1


Step 4 See A.21.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributes.


Parameter Value

3-IFU2-1 4-IFU2-1






LAG Name ToBSC

LAG Type Static






Main Board 7-EM4T

Main Port 3






5-163


NE1 NE2 NE3 NE4

ERPS ID 1 1 1 1




No No Yes No


Control VLAN 4093 4093 4093 4093

Step 7 See A.26.4 Configuring the E-LAN Service and create the E-LAN services.

l Parameters of NE1


Parameter Value

Service ID 1

Service Name Qlan

Tag Type C-Awared




7-EM4T-3 - 100-139

3-IFU2-1 - 100-139

4-IFU2-1 - 100-139

l Parameters of NE2


Parameter Value

Service ID 1

Service Name Qlan


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

Tag Type C-Awared




7-EM4T-1 - 100-109

7-EM4T-2 - 110-119

3-IFU2-1 - 100-139

4-IFU2-1 - 100-139

l Parameters of NE3


Parameter Value

Service ID 1

Service Name Qlan

Tag Type C-Awared




7-EM4T-1 - 120-129

3-IFU2-1 - 100-139

4-IFU2-1 - 100-139

l Parameters of NE4


Parameter Value

Service ID 1



5-165

Parameter Value

Service Name Qlan

Tag Type C-Awared




7-EM4T-1 - 130-139

3-IFU2-1 - 100-139

4-IFU2-1 - 100-139






Packet Type ip-dscp



0 BE

1 AF11

2 AF21

3 AF31

4 AF41

5 EF

6 CS6

7 CS7


Configuration Guide


Issue 02 (2009-10-30)



BE 0

AF11 1

AF21 2

AF31 3

AF41 4

EF 5

CS6 6

CS7 7

NOTE


The values for the related parameters that need to be set in the Apply Port tab page are providedas follows.


NE1 NE2 NE3 NE4


7-EM4T-17-EM4T-23-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1


l Parameters of NE1


Parameter Value

Policy ID 1





5-167

Parameter Value



l Parameters of NE2, NE3, and NE4

The values for the related parameters of NE2, NE3, and NE4 are provided as follows.

Parameter Value

Policy ID 1 2






5 (AF4)60 (AF3)30 (AF2)5 (AF1)



Step 10 See A.16.4 Creating the Traffic and create the traffic for NE2, NE3, and NE4.


Parameter Value

Port_Car


ACL Action Permit



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

Port_Car


Match Value 2

CoS -


CIR(kbit/s) 4096

PIR(kbit/s) 8192

CBS(byte) 5120

PBS(byte) 10240




Parameter Value

Port_Car


Step 11 See A.16.5 Setting the Port That Uses the Port Policy and set the port that uses the port policy.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

Port_Comm





5-169

Parameter Value

Port_Comm Port_Car


7-EM4T-17-EM4T-2


Parameter Value

Port_Comm Port_Car


7-EM4T-1




NE1 NE2 NE3 NE4




4 4 4 4

Step 13 See A.17.2 Creating an MA and create the MA.


Parameter Value

NE1 NE2 NE3 NE4




Qlan Qlan Qlan Qlan

RelevantService

1-Qlan 1-Qlan 1-Qlan 1-Qlan


1s 1s 1s 1s


Configuration Guide


Issue 02 (2009-10-30)



Parameter Value




Qlan Qlan Qlan Qlan

Board 7-EM4T 7-EM4T 7-EM4T 7-EM4T

Port 7-EM4T-3 7-EM4T-3 7-EM4T-3 7-EM4T-3

VLAN 100 110 120 130

MP ID 101 102 103 104

Direction Ingress Ingress Ingress Ingress

CC Status Active Active Active Active


Parameter Value


EdgeNE EdgeNE


Qlan Qlan

Board 7-EM4T 7-EM4T


VLAN 100 110

MP ID 201 202




Parameter Value


Maintenance Association Name Qlan

Board 7-EM4T

Port 7-EM4T-1



5-171

Parameter Value

VLAN 120

MP ID 301

Direction Ingress

CC Status Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN 130

MP ID 401

Direction Ingress

CC Status Active



Parameter Value




Qlan Qlan Qlan Qlan


201 202 301 401



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


EdgeNE EdgeNE


Qlan Qlan


101 102


Parameter Value





Parameter Value









----End



5-173

5.9 Configuration Example (802.1ad-Bridge-Based E-LANService)

This topic considers an 802.1ad-bridge-based E-LAN service as an example to describe how toconfigure the Ethernet service according to the network planning information.





Based on 3.6 Configuration Example (Radio Links on the Hybrid Microwave RingNetwork), configure the Ethernet services according to the actual requirements. The servicerequirements are as follows:

l Each BTS independently plans VLANs for its services.

l The BSC needs to be capable of processing the S-VLAN tag.

l The BSC allocates an S-VLAN to each BTS, and the S-VLANs on the entire network areplanned in a unified manner.


To meet the preceding requirements, the 802.1ad-bridge-based E-LAN service is adopted totransmit the BTS services, and ERPS is adopted to protect services on the ring network, as shownin Figure 5-21.

Figure 5-21 Networking diagram (802.1ad-bridge-based E-LAN service)

BTS1(SVLAN 100)

NE1

NE3

NE2 NE4

BSC

GE

FE

FE

FE

FE

802.1ad bridge

802.1ad bridge

802.1ad bridge

802.1ad bridge

ERPS

BTS2(SVLAN 110)

BTS3(SVLAN 120)

BTS4(SVLAN 130)


Configuration Guide


Issue 02 (2009-10-30)


Ethernet Port







1536 1536


QinQ Type Domain 0x8100 0x8100




Disabled Disabled


- -






1536 1536


QinQ Type Domain - -





5-175



Disabled Disabled


- -


Parameter 7-EM4T-1





QinQ Type Domain -






Parameter 7-EM4T-1





QinQ Type Domain -






Configuration Guide


Issue 02 (2009-10-30)

NOTE

l If the Ethernet services on each BTS do not contain any untagged frames, you can set EncapsulationType to 802.1Q and set Tag to Tag Aware for the FE port that accesses the Ethernet services on each BTS.





l In this example, the SVLAN T-PID that the BSC can identify is 0x8100. Hence, you need to set QinQ TypeDomain to 0x8100 for the two GE ports connecting to the BSC.


Table 5-94 to Table 5-97 provide the information about the IF_ETH ports that carry services.



Tag 802.1Q 802.1Q

QinQ Type Domain 0x88a8 0x88a8




Tag 802.1Q 802.1Q





Tag 802.1Q 802.1Q




5-177





Tag 802.1Q 802.1Q



l The IF_ETH ports connect to internal equipment. Hence, you need to set QinQ TypeDomain to 0x88a8 for the IF_ETH ports.

l The majority of the backhaul services on the base station are Internet services. Hence, theerror frame discarding function needs to be enabled.

LAG


Table 5-98 LAG

Parameter NE1





Main Port 7-EM4T-3

Slave Port 7-EM4T-4

NOTE


ERPS Instance



Configuration Guide


Issue 02 (2009-10-30)






No No Yes No


Control VLAN 4093 4093 4093 4093


5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)

5s (defaultvalue)



600s (defaultvalue)

600s (defaultvalue)

600s (defaultvalue)






0s (defaultvalue)

0s (defaultvalue)

0s (defaultvalue)

NOTE




l

802.1ad-Bridge-Based E-LAN Service


Table 5-100 802.1ad-bridge-based E-LAN service


Service ID 1 1 1 1

Service Name ADlan ADlan ADlan ADlan

Tag Type S-Awared S-Awared S-Awared S-Awared



5-179





IVL IVL IVL IVL

Mounted UNIPort

- 7-EM4T-1 (C-VLAN ID:blank, S-VLANID: 100)7-EM4T-2 (C-VLAN ID:blank, S-VLANID: 110)

7-EM4T-1 (C-VLAN ID:blank, S-VLANID: 120)

7-EM4T-1 (C-VLAN ID:blank, S-VLANID: 130)

Mounted NNIPort

3-IFU2-1 (S-VLAN ID:100,110,120,130)4-IFU2-1 (S-VLAN ID:100,110,120,130)7-EM4T-3 (S-VLAN ID:100,110,120,130)

3-IFU2-1 (S-VLAN ID:100,110,120,130)4-IFU2-1 (S-VLAN ID:100,110,120,130)







CS7 7 -

CS6 6 -


Configuration Guide


Issue 02 (2009-10-30)



AF4 4 -



AF1 1 -


NOTE






CS7 SP

CS6 SP

EF SP





BE SP



5-181





Parameter Value

CIR 4096 kbit/s

CBS 5120 bytes

PIR 8192 kbit/s

PBS 10240 bytes




Parameter Value

CIR 2048 kbit/s

CBS 2560 bytes

PIR 4096 kbit/s

PBS 5120 bytes


QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth ofthe aggregation services, you can perform port shaping at the edge node to limit the Ethernetservice traffic that travels to the aggregation node, thus preventing congestion at the aggregationnode.



Configuration Guide


Issue 02 (2009-10-30)

NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the basic attributesof Ethernet ports.


Parameter Value

7-EM4T-3 7-EM4T-4






Parameter Value

7-EM4T-1 7-EM4T-2






Parameter Value

7-EM4T-1

Enable Port Enabled






5-183

Step 2 See A.20.3 Setting the Layer 2 Attributes of Ethernet Interfaces and set the Layer 2 attributesof Ethernet ports for NE1.


Parameter Value

7-EM4T-3 7-EM4T-4

QinQ Type Domain 81 00 81 00

Step 3 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the attributes of theIF_ETH ports.


Parameter Value

3-IFU2-1 4-IFU2-1






LAG Name ToBSC

LAG Type Static






Main Board 7-EM4T

Main Port 3




Configuration Guide


Issue 02 (2009-10-30)



NE1 NE2 NE3 NE4

ERPS ID 1 1 1 1




No No Yes No


Control VLAN 4093 4093 4093 4093

Step 6 See A.26.4 Configuring the E-LAN Service and configure the E-LAN services.

l Parameters of NE1

The values for the relevant parameters that need to be set in the main interface are providedas follows.

Parameter Value

Service ID 1

Service Name ADlan

Tag Type S-Awared


The values for the relevant parameters that need to be set in the NNI tab page are providedas follows.

Port SVLANs

3-IFU2-1 100,110,120,130

4-IFU2-1 100,110,120,130

7-EM4T-3 100,110,120,130

l Parameters of NE2


Parameter Value

Service ID 1



5-185

Parameter Value

Service Name ADlan

Tag Type S-Awared


The values for the relevant parameters that need to be set on the UNI tab page are providedas follows.


7-EM4T-1 100 Blank

7-EM4T-2 110 Blank

The values for the relevant parameters that need to be set on the NNI tab page are providedas follows.

Port SVLANs

3-IFU2-1 100,110,120,130

4-IFU2-1 100,110,120,130

l Parameters of NE3


Parameter Value

Service ID 1

Service Name ADlan

Tag Type S-Awared




7-EM4T-1 120 Blank


Configuration Guide


Issue 02 (2009-10-30)


Port SVLANs

3-IFU2-1 100,110,120,130

4-IFU2-1 100,110,120,130

l Parameters of NE4


Parameter Value

Service ID 1

Service Name ADlan

Tag Type S-Awared




7-EM4T-1 130 Blank


Port SVLANs

3-IFU2-1 100,110,120,130

4-IFU2-1 100,110,120,130



Parameter Value



Packet Type cvlan



5-187



0 0 BE

1 1 AF11

2 2 AF21

3 3 AF31

4 4 AF41

5 5 EF

6 6 CS6

7 7 CS7



BE 0 0

AF11 1 1

AF21 2 2

AF31 3 3

AF41 4 4

EF 5 5

CS6 6 6

CS7 7 7

NOTE




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

NE1 NE2 NE3 NE4


7-EM4T-17-EM4T-23-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-14-IFU2-1

Step 8 See A.16.2 Changing the Ports That Use the DS Domain and change the ports that use theDS domain.



3-IFU2-1 svlan

4-IFU2-1 svlan

7-EM4T-3 svlan



7-EM4T-1 cvlan

7-EM4T-2 cvlan

3-IFU2-1 svlan

4-IFU2-1 svlan



7-EM4T-1 cvlan

3-IFU2-1 svlan

4-IFU2-1 svlan


l Parameters of NE1


Parameter Value

Policy ID 1



5-189

Parameter Value





l Parameters of NE2, NE3, and NE4

The values for the related parameters of NE2, NE3, and NE4 are provided as follows.

Parameter Value

Policy ID 1 2






5 (AF4)60 (AF3)30 (AF2)5 (AF1)



Step 10 See A.16.4 Creating the Traffic and create the traffic for NE2, NE3, and NE4.


Parameter Value

Port_Car


ACL Action Permit


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

Port_Car


Match Value 2

CoS -


CIR(kbit/s) 4096

PIR(kbit/s) 8192

CBS(byte) 5120

PBS(byte) 10240




Parameter Value

Port_Car


Step 11 See A.16.5 Setting the Port That Uses the Port Policy and set the port that uses the port policy.


Parameter Value

Port_Comm




5-191


Parameter Value

Port_Comm Port_Car


7-EM4T-17-EM4T-2


Parameter Value

Port_Comm Port_Car


7-EM4T-1




NE1 NE2 NE3 NE4




4 4 4 4

Step 13 See A.17.2 Creating an MA and create an MA.


Parameter Value

NE1 NE2 NE3 NE4




ADlan ADlan ADlan ADlan

RelevantService

1-ADlan 1-ADlan 1-ADlan 1-ADlan


1s 1s 1s 1s


Configuration Guide


Issue 02 (2009-10-30)


l The values for the relevant parameters of NE1 are provided as follows,

Parameter Value





Board 7-EM4T 7-EM4T 7-EM4T 7-EM4T

Port 7-EM4T-3 7-EM4T-3 7-EM4T-3 7-EM4T-3

VLAN 100 110 120 130

MP ID 101 102 103 104

Direction Ingress Ingress Ingress Ingress

CC Status Active Active Active Active


Parameter Value


EdgeNE EdgeNE


ADlan ADlan

Board 7-EM4T 7-EM4T


VLAN - -

MP ID 201 202




Parameter Value


Maintenance Association Name ADlan

Board 7-EM4T



5-193

Parameter Value

Port 7-EM4T-1

VLAN -

MP ID 301

Direction Ingress

CC Status Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN -

MP ID 401

Direction Ingress

CC Status Active



Parameter Value






201 202 301 401



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


EdgeNE EdgeNE


ADlan ADlan


101 102


Parameter Value





Parameter Value









----End



5-195

5.10 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)

This topic describes how to configure a radio network that transmit E-Line services and E-LANservices at the same time according to the network planning information.


5.10.2 Service PlanningThe service planning information contains all the parameter information required for configuringthe NE data.



Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure Ethernet services according to the actual requirements. On this network,the Ethernet services on each BTS carry VLAN IDs. The allocation information of VLAN IDsis shown in Figure 5-22. Certain VLAN IDs conflict with each other on this network. Hence,E-Line services cannot be configured on all the NEs. To realize service aggregation, you needto configure the Ethernet services as E-LAN services on the aggregation node where certainVLAN IDs conflict with each other.

Figure 5-22 Networking diagram (VLAN-based E-Line services)

BTS3VLAN 120

BSCNE1NE2NE3

NE5

NE4

NE6

FE

FE

FEFE

FE

GE GE

BTS5VLAN 120

BTS1VLAN 100

BTS2VLAN 110

BTS4VLAN 110

5.10.2 Service PlanningThe service planning information contains all the parameter information required for configuringthe NE data.


Configuration Guide


Issue 02 (2009-10-30)







1536 1536








1536 1536




Parameter 7-EM4T-3





Tag Tag Aware



5-197






1536 1536




Parameter 7-EM4T-1





Tag Tag Aware


Parameter 7-EM4T-1





Tag Tag Aware


Configuration Guide


Issue 02 (2009-10-30)

NOTE





Information About the IF_ETH PortTable 5-111 to Table 5-116 provide the information about the IF_ETH ports that carry services.


















5-199


Parameter 3-IFU2-1


Tag Tag Aware








Parameter 3-IFU2-1


Tag Tag Aware


NOTE

The majority of the backhaul services on the base station are the Internet services. Hence, the error framediscarding function needs to be enabled.

LAG


Table 5-117 LAG

Parameter NE1






Configuration Guide


Issue 02 (2009-10-30)

Parameter NE1

Main Port 7-EM4F-3

Slave Port 7-EM4F-4

NOTE


Information About VLAN-Based E-Line ServicesAll the Ethernet services on the network carry VLAN IDs. Hence, VLAN-based E-Line servicesare configured on NE1, NE2, NE4, NE5, and NE6. Table 5-118 to Table 5-122 provide theservice planning information.

Table 5-118 Information about VLAN-based E-Line services (NE1)

Parameter NE1

NE2 to BSC

Service ID 1


Direction UNI-UNI



Source CVLANs 100, 110, 120

Sink Port 7-EM4F-3

Sink CVLANs 100, 110, 120


Parameter NE2


Service ID 1 2







5-201

Parameter NE2



Source CVLANs 110,120 100


Sink CVLANs 110,120 100


Parameter NE4


Service ID 1 2






Source CVLANs 110 120


Sink CVLANs 110 120


Parameter NE5


Service ID 1 2






Source CVLANs 120 110



Configuration Guide


Issue 02 (2009-10-30)

Parameter NE5


Sink CVLANs 120 110


Parameter NE6

BTS5 to NE5

Service ID 1


Direction UNI-UNI



Source CVLANs 120

Sink Port 3-IFU2-1

Sink CVLANs 120

Information About IEEE 802.1q Bridge-Based E-LAN ServicesOn the aggregation node NE3 where certain VLAN IDs conflict with each other, configure IEEE802.1q bridge-based E-LAN services. Table 5-123 provides the service planning information.

Table 5-123 Information about IEEE 802.1q Bridge-Based E-LAN Services

Item NE3

Service ID 1

Service Name Qlan

Tag C-Awared

MAC Address Learning Mode Enabled

MAC Address Learning Mode IVL

Mounted UNI port 7-EM4T-1 (VLAN ID: 110, 120)3-IFU2-1 (VLAN ID: 110, 120)4-IFU2-1 (VLAN ID: 110, 120)

Split Horizon Group 3-IFU2-1 (VLAN ID: 110, 120)4-IFU2-1 (VLAN ID: 110, 120)



5-203

NOTEIn this example, the split horizon group is planned to enhance the isolation of each E-LAN service. In the actualconfiguration scenario, you can select not to configure the split horizon group.





CS7 7 -

CS6 6 -


AF4 4 -



AF1 1 -


NOTE



Configuration Guide


Issue 02 (2009-10-30)






CS7 SP

CS6 SP

EF SP





BE SP





Parameter Value

CIR 4096 kbit/s

CBS 5120 bytes

PIR 8192 kbit/s

PBS 10240 bytes





5-205


Parameter Value

CIR 2048 kbit/s

CBS 2560 bytes

PIR 4096 kbit/s

PBS 5120 bytes




NOTE



Procedure

Step 1 See A.20.1 Setting the General Attributes of Ethernet Interfaces and set the general attributesof Ethernet ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

7-EM4F-3 7-EM4F-4







Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

7-EM4T-1 7-EM4T-3






Parameter Value

7-EM4T-3

Enable Port Enabled





Parameter Value

7-EM4T-1 7-EM4T-2






Parameter Value

7-EM4T-1

Enable Port Enabled







5-207

Parameter Value

7-EM4T-1

Enable Port Enabled





Parameter Value

7-EM4F-3 7-EM4F-4




7-EM4T-1 7-EM4T-3



Parameter Value

7-EM4T-3

TAG Tag Aware


Parameter Value

7-EM4T-1 7-EM4T-2



Parameter Value

7-EM4T-1

TAG Tag Aware


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value

7-EM4T-1

TAG Tag Aware

Step 3 See A.21.1 Setting the General Attributes of the IF_ETH Port and set the general attributesof IF_ETH ports.l The values for the related parameters of NE1 are provided as follows.

Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1





5-209

Parameter Value

3-IFU2-1


Step 4 See A.21.2 Setting the Layer 2 Attributes of the IF_ETH Port and set the Layer 2 attributesof IF_ETH ports.


Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1 4-IFU2-1



Parameter Value

3-IFU2-1

Tag Tag Aware


Parameter Value

3-IFU2-1 4-IFU2-1




Configuration Guide


Issue 02 (2009-10-30)

Parameter Value

3-IFU2-1

Tag Tag Aware


Parameter Value


LAG Name ToBSC

LAG Type Static





Parameter Value

Main Board 7-EM4F

Main Port 3


Step 6 See A.26.2 Configuring the E-Line Service and configure the E-Line services on NE1, NE2,NE4, NE5, and NE6.


Parameter Value

NE2 to BSC

Service ID 1


Direction UNI-UNI


Source Port 7-EM4F-3



5-211

Parameter Value

NE2 to BSC

Source VLANs 100,110,120

Sink Port 3-IFU2-1

Sink VLANs 100,110,120


Parameter Value


Service ID 1 2






Source VLANs 110,120 100


Sink VLANs 110,120 100


Parameter Value


Service ID 1 2






Source VLANs 110 120


Sink VLANs 110 120



Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


Service ID 1 2






Source VLANs 120 110


Sink VLANs 120 110


Parameter Value

BTS5 to NE5

Service ID 1


Direction UNI-UNI



Source VLANs 120

Sink Port 3-IFU2-1

Sink VLANs 120

Step 7 See A.26.4 Configuring the E-LAN Service and configure the E-LAN service on NE3.

The values for the related parameters that need to be set in the main interface are as follows.

Parameter Value

Service ID 1

Service Name Qlan

Tag Type C-Awared




5-213

The values for the related parameters that need to be set in the UNI tab page are as follows.


7-EM4T-1 - 110,120

3-IFU2-1 - 110,120

4-IFU2-1 - 110,120

The values for the related parameters that need to be set in the Split Horizon Group tab pageare as follows.

Split Horizon Group ID Split Horizon Group Member

1 3-IFU2-1[110,120], 4-IFU2-1[110,120]



Parameter Value



Packet Type cvlan



0 BE

1 AF11

2 AF21

3 AF31

4 AF41

5 EF

6 CS6

7 CS7


Configuration Guide


Issue 02 (2009-10-30)



BE 0

AF11 1

AF21 2

AF31 3

AF41 4

EF 5

CS6 6

CS7 7

NOTE



Parameter

Value


SelectedPort

3-IFU2-17-EM4F-3

7-EM4T-17-EM4T-33-IFU2-1

3-IFU2-14-IFU2-17-EM4T-3

3-IFU2-17-EM4T-17-EM4T-2

7-EM4T-13-IFU2-14-IFU2-1

7-EM4T-13-IFU2-1

NOTE

The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DSdomain that is created in this step. Therefore, you can skip this step.

Step 9 See A.16.3 Creating a Port Policy and create the port policy.l The values for the relevant parameters of NE1 and NE3 are provided as follows.

Parameter Value

Policy ID 1




5-215

Parameter Value




l The values for the relevant parameters of NE2 and NE5 are provided as follows.

Parameter Value

Policy ID 1 2 3

Policy Name Port_Comm Port_Car Port_Shaping

Grooming PoliceAfter Reloading





5 (AF4)60 (AF3)30 (AF2)5 (AF1)

5 (AF4)60 (AF3)30 (AF2)5 (AF1)

Bandwidth Limit Disabled (for allPHB serviceclasses)




Parameter Value

Policy ID 1 2

Policy Name Port_Car Port_Shaping





Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


5 (AF4)60 (AF3)30 (AF2)5 (AF1)



Step 10 See A.16.4 Creating the Traffic and create the flows for NE2, NE4, NE5, and NE6.l Parameters of NE2:


Parameter Value




The values for the related parameters that need to be set in the INGRESS tab page are asfollows.

Parameter Value


Match Type CVlan priority CVlan ID CVlan priority

Match Value 2 100 3

CoS - -


CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-



5-217

Parameter Value



-

The values for the related parameters that need to be set in the EGRESS tab page are asfollows.

Parameter Value



CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560

PBS(byte) - 5120



Parameter Value


TrafficClassification ID

1 1 2

ACL Action Permit Permit Permit


Parameter Value



MatchType

CVlanpriority

CVlan ID CVlanpriority

CVlan ID CVlanpriority

MatchValue

2 110 3 120 3


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value



CoS - - -

BandwidthLimit

Enabled Disabled Disabled

CIR(kbit/s) 4096 - -

PIR(kbit/s) 8192 - -

CBS(byte) 5120 - -

PBS(byte) 10240 - -

HandlingMode

Discard(red)Remark(yellow)Pass (green)

- -

RelabeledCoS

- (red)EF (yellow)- (green)

- -


Parameter Value

Port_Car Port_Shaping(TrafficClassificationID=1)

Port_Shaping(TrafficClassificationID=2)

Bandwidth Limit Disabled Enabled Enabled

CIR(kbit/s) - 2048 2048

PIR(kbit/s) - 4096 4096

CBS(byte) - 2560 2560

PBS(byte) - 5120 5120





5-219

Parameter Value





Parameter Value



Match Value 2 130 3

CoS - -


CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-


-


Parameter Value



CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


PBS(byte) - 5120



Parameter Value





Parameter Value



Match Value 2 140 3

CoS - -


CIR(kbit/s) 4096 -

PIR(kbit/s) 8192 -

CBS(byte) 5120 -

PBS(byte) 10240 -


-


-




5-221

Parameter Value



CIR(kbit/s) - 2048

PIR(kbit/s) - 4096

CBS(byte) - 2560

PBS(byte) - 5120



Parameter Value

Port_Comm



Parameter Value


Port 7-EM4T-3 7-EM4T-1 3-IFU2-1


Parameter Value

Port_Comm



Parameter Value


Port 7-EM4T-17-EM4T-2

3-IFU2-1


Configuration Guide


Issue 02 (2009-10-30)


Parameter Value


Port 3-IFU2-1 7-EM4T-1 4-IFU2-1


Parameter Value





Parameter Value

NE1 NE2 NE4 NE5 NE6




4 4 4 4 4

Step 13 See A.17.2 Creating an MA and create the maintenance association (MA) for NE1, NE2, NE4,NE5, and NE6.l The values for the relevant parameters of NE1 are provided as follows.

Parameter Value




BTS1_Vline

BTS2_Vline

BTS3_Vline

BTS4_Vline

BTS5_Vline

RelevantService

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline

1-NE2toBSC_Vline



5-223

Parameter Value


1s 1s 1s 1s 1s


Parameter Value






Parameter Value


EdgeNE EdgeNE



Relevant Service 1-BTS2toNE3_Vline 2-BTS3toNE3_Vline


1s 1s


Parameter Value






Parameter Value





Configuration Guide


Issue 02 (2009-10-30)

Parameter Value


Step 14 See A.17.3 Creating an MEP Point and create the MEP points.l The values for the relevant parameters of NE1 are provided as follows.

Parameter


EdgeNE EdgeNE EdgeNE

MaintenanceAssociation Name

BTS1_Qline BTS2_BTS4_Qline BTS3_BTS5_Qline

Board 7-EM4F 7-EM4F 7-EM4F

Port 7-EM4F-3 7-EM4F-3 7-EM4F-3

VLAN 100 110 120

MP ID 101 102 103

Direction Ingress Ingress Ingress

CC Status Active Active Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN 100

MP ID 201

Direction Ingress

CC Status Active


Parameter Value


EdgeNE EdgeNE



5-225

Parameter Value


BTS2_BTS4_Qline BTS3_BTS5_Qline

Board 7-EM4T 7-EM4T


VLAN 110 120

MP ID 401 402




Parameter Value


Maintenance Association Name BTS2_BTS4_Qline

Board 7-EM4T

Port 7-EM4T-1

VLAN 110

MP ID 501

Direction Ingress

CC Status Active


Parameter Value



Board 7-EM4T

Port 7-EM4T-1

VLAN 120

MP ID 601

Direction Ingress

CC Status Active


Configuration Guide


Issue 02 (2009-10-30)

Step 15 A.17.4 Creating Remote MEPs in an MA and create the remote MEP points for NE1, NE2,NE4, NE5 to NE6.

The values for the relevant parameters of NE1 are provided as follows.

Parameter Value




BTS1_Qline BTS2_BTS4_Qline

BTS3_BTS5_Qline

BTS2_BTS4_Qline

BTS3_BTS5_Qline


201 401 402 501 601


Parameter Value





Parameter Value


EdgeNE EdgeNE


BTS2_BTS4_Qline BTS3_BTS5_Qline


102 103


Parameter Value




5-227

Parameter Value




Parameter Value




Step 16 See A.26.5 Testing the Ethernet Service and test the Ethernet services on NE1.l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and






----End


Configuration Guide


Issue 02 (2009-10-30)

6 Configuring the Clock

About This Chapter

To ensure that clocks of all the nodes on the transmission network are synchronized, configurethe clocks for these nodes according to a unified clock synchronization policy.

6.1 Basic ConceptsBefore configuring the clock, you need to be familiar with the basic concepts.

6.2 Configuration ProcedureThis topic describes the procedures for configuring the clock source, clock protection, and outputclock.

6.3 Configuration Example (Clock for a TDM Microwave Chain Network)This topic considers a TDM microwave chain network as an example to describe how toconfigure the clock according to the network planning information.

6.4 Configuration Example (Clock for a TDM Microwave Ring Network)This topic considers a TDM microwave ring network as an example to describe how to configurethe clock according to the network planning information.

6.5 Configuration Example (Clock for a Hybrid Microwave Chain Network)This topic considers a Hybrid microwave chain network as an example to describe how toconfigure clocks according to the network planning information.

6.6 Configuration Example (Clock for a Hybrid Microwave Ring Network)This topic considers a Hybrid microwave ring network as an example to describe how toconfigure the clock according to the network planning information.

OptiX RTN 910Configuration Guide 6 Configuring the Clock


6-1

6.1 Basic ConceptsBefore configuring the clock, you need to be familiar with the basic concepts.

6.1.1 Clock SourceThe clock source is used to synchronize parts of an NE, or upstream and downstream NEs, andto provide stable and accurate operating frequency for the functional module and chip of an NE.In this manner, the service can be transmitted correctly and in strict order.

6.1.2 Clock Protection SchemesThe OptiX RTN 910 supports the clock source protection based on priorities, synchronizationstatus message (SSM) protection, and extended SSM protection.

6.1.3 Clock Synchronization PolicyUsers should plan a proper clock synchronization policy according to the network topology.

6.1.1 Clock SourceThe clock source is used to synchronize parts of an NE, or upstream and downstream NEs, andto provide stable and accurate operating frequency for the functional module and chip of an NE.In this manner, the service can be transmitted correctly and in strict order.

The OptiX RTN 910 supports the following clock sources:

l Line clock sourceRefers to a clock source that is extracted from the received SDH signal.

l Radio clock sourceRefers to a clock source that is extracted from the received radio signal.

l Tributary clock sourceRefers to a clock source that is extracted from the received PDH signal.

l Ethernet clock sourceRefers to a clock source that is extracted from the FE/GE signal by using the synchronousEthernet function.

l External clock sourceRefers to a clock source that is extracted from the 2 Mbit/s or 2 MHz signal that is receivedat the external clock interface.

l Internal clock sourceRefers to a clock source that is generated through the free-run oscillation of the built-inclock of an NE.

6.1.2 Clock Protection SchemesThe OptiX RTN 910 supports the clock source protection based on priorities, synchronizationstatus message (SSM) protection, and extended SSM protection.

Clock Source Protection Based on PrioritiesThe clock source protection is provided based on the priorities specified in the clock sourcepriority list. When the clock source of a higher priority fails, the clock source of a lower priorityis used.

6 Configuring the ClockOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

As shown in Figure 6-1, the radio links between NE1 and NE2 adopt the 1+1 protection. NE2needs to trace the clock on the radio links to keep synchronous with NE1. In this case, the clocksources extracted by the main and standby IF boards can be configured in the clock sourcepriority list. The clock source extracted by the main IF board, however, has a higher priority.Thus, if the 1+1 IF protection switching occurs on the radio links, the clock can be switched atthe same time.

Figure 6-1 Clock source protection based on priorities

NE2NE1BITS

1+1 protectionconfiguration

Clock

SSM Protection

The SSM protection uses the SSM protocol specified in ITU-T G.781 to realize the clockprotection. According to the SSM protocol, the SDH NE transmits the SSM protocol throughbits 5-8 of the S1 byte, realizes the automatic protection switching of clock sources, and preventsthe timing loop. The OptiX RTN 910 supports the SSM protection on the SDH opticaltransmission lines and STM-1 radio links. After the SSM protection is enabled on an NE, theautomatic protection switching of clock sources conforms to the following rules:

l According to the clock source priority list, the NE selects the clock source of the best qualityas the synchronization source.

l If multiple clock sources have the best quality, the NE selects the one of the highest priorityas the synchronization source.

l By using the S1 byte, the NE broadcasts the information of the synchronization sourcequality to the downstream NEs, and also notifies the upstream NE that the clock sourcefrom the NE cannot be used for synchronization.

Figure 6-2 is an STM-1 microwave ring where the SSM protection is enabled.

When the network operates normally, the NEs on the ring select the clock source as follows:

1. NE1 selects the external clock source as the synchronization source and notify NE2 andNE4 of the external clock quality.

2. NE2 and NE4 select the clock source from NE1 as the synchronization source and notifiesNE1 that the clock sources from NE2 and NE4 are unusable.

3. NE3 detects that the clock sources from NE2 and NE4 have the same quality and selectsthe clock source of a higher priority (the clock source from NE2) as the synchronizationsource. In addition, NE3 transmits the information of the synchronization source quality toNE4 and notifies NE2 that the clock source from NE3 is unusable.

4. NE4 detects that the clock sources from NE1 and NE3 have the same quality and selectsthe clock source of a higher priority (the clock source from NE3) as the synchronization



6-3

source. In addition, NE4 transmits the information of the synchronization source quality toNE1 and notifies NE3 that the clock source from NE4 is unusable.

5. According to the clock quality in west and east directions and the configured clock sourcepriorities, NE2, NE3, and NE4 determine that the synchronization source requires nomodifications. Thus, the clock source selection is finished.

When the radio links between NE1 and NE2 become faulty, the NEs on the ring select the clocksource as follows:

1. NE2 selects the internal source as the synchronization source and transmits the informationof the synchronization source quality to NE1 and NE3.

2. NE3 selects NE2 as the clock source and informs NE4 of the clock quality.

3. After detecting that the quality of the clock from NE1 is higher than the quality of the clockfrom NE3, NE4 transmits the clock quality information to NE3 and informs NE1 that theclock from NE4 is unavailable.

4. After detecting that the quality of the clock from NE4 is higher than the quality of the clockfrom NE2, NE3 selects the clock source from NE4 as the synchronization source, transmitsthe information of the synchronization source quality to NE2, and notifies NE4 that theclock source from NE3 is unusable.

5. After detecting that the quality of the clock from NE3 is higher than the quality of theinternal clock source, NE2 selects the clock source from NE3 as the synchronization source,transmits the information of the synchronization source quality to NE1, and notifies NE3that the clock source from NE2 is unusable.

6. According to the clock quality in west and east directions and the configured clock sourcepriorities, NE2, NE3, and NE4 determine that the synchronization source requires nomodifications. Thus, the clock source selection is finished.

NOTE

The SSM protection does not provide a complete solution to the timing loop. Thus, when you configure clocksources, the clocks cannot form a loop as on NE1 in this example.

Figure 6-2 SSM protection

NE1

NE3

NE2 NE4

BITSExtenal/Internal

West/East/Internal

West/East/Internal

West/East/Internal

E

W

E

E

W

WE

W

Master clock


Configuration Guide


Issue 02 (2009-10-30)

Extended SSM ProtectionThe extended SSM protection uses the extended SSM protocol to provide the clock protection.The extended SSM protocol, developed by Huawei on the basis of the SSM protocol, introducesthe concept of clock ID. Through the extended SSM protocol, you can define a clock ID for anyclock source. The clock ID of the synchronization source can be transmitted together with theSSM protocol and be used for the automatic clock switching. The extended SSM protection isavailable on the SDH optical transmission lines and the STM-1 radio links.

After the extended SSM protection is enabled on an NE, the automatic clock switching conformsto the following rules:

l According to the clock source priority list, the NE selects the clock source of the best qualityas the synchronization source.

l If the clock ID of a certain clock source indicates that the clock source is from the NE itself,the clock source is not processed.

l If multiple clock sources have the best quality, the NE selects the one of the highest priorityas the synchronization source.

l By using the S1 byte, the NE broadcasts the information of the synchronization sourcequality to the downstream NEs, and also notifies the upstream NE that the clock sourcefrom the NE cannot be used for synchronization.

The clock ID takes a value from 0 to 15. 0 is the default value, indicating that the clock ID isinvalid. After the extended SSM protocol is enabled on the NE, the NE does not select clocksource 0 as the current clock source.

Clock IDs are allocated as follows:

l All the external clock sources should have a clock ID.

l At all the nodes that access external clock sources, the internal clock sources should havea clock ID.

l At all the intersection nodes of a ring/chain and a ring, the internal clock sources shouldhave a clock ID.

l At all the intersection nodes of a ring/chain and a ring, the line clock sources that areaccessed into the ring should have a clock ID.

l The clock sources other than the preceding four types should have a default clock ID of 0.

l Clock IDs are used for timing reference only. They do not indicate any priority difference.Thus, the clock source has the same priority regardless of whether the clock ID is 1 or 15.

Figure 6-3 is an STM-1 microwave ring where the extended SSM protection is enabled.

On the ring, the following clock sources require a clock ID:

l External clock source 1

l External clock source 2

l Internal clock source on NE1

l Internal clock source on NE3



6-5

Figure 6-3 Extended SSM protection

NE1

NE3

NE2 NE4

Master BITS

West/East/Internal

West/East/

Extenal/Internal

West/East/Internal

W E

W

E

E

W

Slave BITS

Extenal/ West/East/Internal

WE

Master clock

NOTE

l The extended SSM protection provides a complete solution to the timing loop. Thus, when you configureclock sources, the clocks can form a loop.

l The extended SSM protection is advantageous in the complex networking of clock protection, for example,the dual external clocks. Hence, the extended SSM protection is used in only a few cases.

6.1.3 Clock Synchronization PolicyUsers should plan a proper clock synchronization policy according to the network topology.

Clock Synchronization Policy for a Chain Network

In the case of a chain network consisting of radio links, the clock synchronization policy shouldbe planned according to the following principles:

l The master (source) node accesses one clock source (which can be an external clock, a lineclock, or an Ethernet clock). On this node, the accessed clock source should be configured.

l In the case of the other nodes, the clock sources for their upper level radio links should beconfigured.

l If the upper level radio link is configured with 1+1 protection, a node should be configuredwith two radio clock sources, and the clock source for the main radio link should have ahigher priority than the clock source for the standby radio link.

l If a node has multiple upper level radio links (for example, the upper level radio links areconfigured with XPIC or N+1 protection), each radio link should be configured with oneradio clock source on this node. In addition, these radio clock sources should be configuredwith different priorities according to the actual condition.

l The SSM or extended SSM protection need not be configured.

Figure 6-4 shows the clock synchronization policy for a chain network.


Configuration Guide


Issue 02 (2009-10-30)

l The master node (NE1) accesses one external clock source. In this case, the clock sourcepriorities for NE1 in a descending order are as follows: external clock source > internalclock source.

l The radio link between NE1 and NE2 comprises the IF1 board in slot 3 on NE2, and thusthe clock source priorities for NE2 in a descending order are as follows: 3-IF1-1 > internalclock source.

l The radio link between NE3 and NE2 comprises the IF1 board in slot 3 on NE3, and thusthe clock source priorities for NE3 in a descending order are as follows: 3-IF-1 > internalclock source.


Figure 6-4 Clock synchronization policy for a chain network

3-IF1-1/Internal

NE1 NE2

clock

Enternal /Internal

BITS NE3

3-IF1-1/Internal

Clock Synchronization Policy for a Ring NetworkIf a ring network comprises only radio links or comprises radio links and optical transmissionlines, plan the clock synchronization policy according to the following principles:

l If only the SDH signal is transmitted on the ring, configure the SSM or extended SSMprotection according to the clock policy for an optical transmission network.

l If the PDH radio or Hybrid radio is used on certain segments of the ring, equally divide thering into two chains, and then plan the clock synchronization policy according to therelevant policy for a chain network.

Figure 6-5 shows the clock synchronization policy for a ring on which only the SDH signal istransmitted.

l Configure the SSM or extended SSM protection for all the nodes on the ring.

l The master node (NE1) accesses one external clock source. In this case, the clock sourcepriorities in a descending order for NE1 are as follows: external clock source > internalclock source.

l The clock source priorities for the other nodes in a descending order are as follows: westclock source > east clock source > internal clock source.



6-7

Figure 6-5 Clock synchronization policy for a ring network (on which only the SDH signal istransmitted)

NE1NE2

NE3NE4

NE5

NE6

West/East/Internal

West/East/Internal

Master clockWest/East/

Internal

West/East/Internal

West/East/InternalExtenal/

Internal

WE

W

E

EW

W

WE

EE

W

BITS

Figure 6-6 shows the clock synchronization policy for a ring on which not only the SDH signalis transmitted.

l The ring uses the Hybrid radio for transmission. Thus, divide the ring into the followingchains at the master node (NE1): NE1-NE2-NE3 and NE1-NE4.

l In the case of the master node (NE1), the port 1 on the EM6T board in slot 2 accesses theEthernet link, which functions as a clock source. Hence, the clock source priorities for NE1in a descending order are as follows: 2-EMT6-1 > internal clock source.

l NE2 traces the clock of the master node, and thus the clock source priorities for NE2 in adescending order are as follows: west clock source > internal clock source.

l NE3 traces the clock of NE2, and thus the clock source priorities for NE3 in a descendingorder are as follows: west clock source > internal clock source.

l NE4 traces the clock of the master node (NE1), and thus the clock source priorities for NE4in a descending order are as follows: east clock source > internal clock source.



Configuration Guide


Issue 02 (2009-10-30)

Figure 6-6 Clock synchronization policy for a ring network (on which not only the SDH signalis transmitted)

NE1

NE3

NE2 NE4

West/Internal

West/Internal

East/Internal

E

W

E

E

W

WE

W

BSC2-EM6T-1/

Internal

Clock

Clock Synchronization Policy for a Port Aggregation Network

On a port aggregation network, services of several OptiX RTN NEs are aggregated to the upperlevel RTN NE through the optical transmission line, tributary, or Ethernet. Plan the clocksynchronization policy for a port aggregation network according to the following principles:

l The upper level NE accesses a clock source (which can be an external clock source, a lineclock source, or an Ethernet clock source).

l If the service of a lower-level NE is aggregated to the upper level NE through the opticaltransmission line or Ethernet, the lower-level NE should trace the upper level line clock orEthernet clock.

l If the service of a lower-level NE is aggregated to the upper level NE only through the E1signal, the lower-level NE should trace the tributary clock source (E1 ports 1 and 5 on theE1 tributary board/system control, cross-connect, and timing board support the tributaryclock source).

l If the service of a lower-level NE is aggregated to the upper level NE only through the E1signal and the lower-level NE is connected to many hops of downstream radio links, tracingthe tributary clock source causes anomalies such as pointer justifications. In this case, thelower-level NE should trace the external clock source output by the upper level NE.


Figure 6-7 shows the clock synchronization policy for a tributary port aggregation network.

l The master node (NE1) accesses one external clock source. In this case, the clock sourcepriorities for NE1 in a descending order are as follows: external clock source > internalclock source.

l The IF1 boards in slots 3 and 4 on NE2 form a 1+1 IF protection, where the IF1 board inslot 3 functions as the main board. In addition, the radio links between NE1 and NE2comprise the two IF1 boards. Hence, the clock source priorities for NE2 in a descendingorder are as follows: 3-IF1-1 > 4-IF1-1 > internal clock source.



6-9

l The service of NE3 is aggregate to NE2 through ports 1 to 4 on the SP3S board in slot 9.Hence, the clock source priorities for NE3 in a descending order are as follows: 9-SP3S-1> internal clock source.

l NE4 is connected to many hops of downstream radio links. In this case, if it traces thetributary clock source, pointer justifications occur on the downstream nodes. Hence, NE4traces the external clock source output by NE2.

l The SSM protection or extended SSM protection need not be configured.

Figure 6-7 Clock synchronization policy for a port aggregation network (aggregation onlythrough the tributary port)

3-IF1-1/4-IF1-1/Internal

NE1 NE2

Clock

External/Internal

NE3

9-SP3S-1/Internal

NE4

External/Internal

Precautions of Planning a Clock Synchronization PolicyWhen planning a clock synchronization policy, pay attention to the following points:

l The number of NEs on a long clock chain should not be more than 20. A number smallerthan 10 is recommended. If a large number of NEs exist on a long clock chain, add onemore clock source for signal compensation in the middle of the chain.

l It is recommended that the SDH optical interface should be used at a convergence node toconverge the TDM service. In this manner, the clock signal can be transmitted over theSDH signal rather than over the PDH signal, which ensures the quality of the clock signal.

Clock Synchronization Policy for a Base StationIf a synchronization signal is transmitted to a base station through the radio transmission network,plan the synchronization policy according to the following principles:

If the base station can access the transmission network through an SDH optical interface orEthernet interface, use the SDH optical interface or Ethernet interface to provide the timingreference signal for the base station.

If the base station can access the transmission network only through the E1 signal, the externalclock interface is preferred to transmit the timing reference signal to the base station.

If the base station can access the transmission network only through the E1 signal and the externalclock interface cannot be used, use the E1 interface to transmit the timing reference signal to thebase station. If the output clock does not meet the requirement of the base station, the NE thatis connected to the base station can use the tributary retiming function.


Configuration Guide


Issue 02 (2009-10-30)

If the BTS can be accessed to the transmission network through Ethernet only and does notsupport the synchronous Ethernet function, you can provide the timing reference signal to theBTS through the external clock interface.

Tributary RetimingWhen being transmitted by the OptiX RTN 910, the PDH signal must undergo mapping anddemapping processes, during which the jitter occurs. In addition, pointer justifications duringthe network transmission process cause the jitter of the PDH signal.

Tributary retiming helps to reduce the jitter of the PDH signal when it is transmitted on atransmission network. Tributary retiming realizes the transmission of the signal that combinesthe timing reference signal and the PDH service signal. Hence, the transmitted PDH signal carriesthe timing information that is synchronized with the timing reference signal.

Figure 6-8 shows how a BSC transmits the synchronization information to a base station throughthe radio transmission network after the tributary retiming function is enabled. The radiotransmission network extracts the tributary clock from the E1 signal that is transmitted from theBSC. This tributary clock functions as the synchronization reference clock for the radiotransmission network to be synchronized with the clock of the BSC. The tributary retimingfunction is enabled on NE3. In this manner, NE3 transmits the E1 signal that carries the retimingclock information to the BTS (NE3 selects the system clock as the retiming clock). In addition,NE3 is synchronized with the BSC. Hence, the base station can extract the clock signal of theBSC from the tributary signal.

The basic working principle of tributary retiming is as follows: The tributary signal is writteninto a large-capacity first in first output (FIFO), and then the tributary signal is read from theFIFO through the retiming clock. In this manner, the output signal contains the retiming clockinformation, and FIFO eliminates the jitter and wander in the original tributary signal. The OptiXRTN 910 can select the system clock or the line clock in the uplink E1 signal as the retimingclock, depending on the specific networking. In general cases, the system clock is selected asthe retiming clock.

Figure 6-8 Tributary retiming

NE1 NE2

Clock

BSC

NE3

Write clk(downlink E1 clk)

FIFOE1 E1

Read clk(retiming clk)

NE3

E1 E1

When using the tributary retiming function, pay attention to the following points:



6-11

l The retiming clock should be synchronized with the clock of the BSC, and the retimingclock should not undergo mapping and demapping processes.

l The tributary retiming function uses the FIFO, which causes a delay of 125 us or more. Usethis function when it is necessary.

l The retiming function requires that the entire transmission network should be synchronizedwith the service network that requires retiming. If certain NEs on the transmission networkare not synchronized, slips occur.

l The transmission network can meet the retiming requirement of only one service network.

6.2 Configuration ProcedureThis topic describes the procedures for configuring the clock source, clock protection, and outputclock.

Table 6-1 Procedures for configuring the clock


1 A.10.1 Configuring theClock Sources

Required. The parameters are set as follows:l According to the clock source that is planned, set

Clock Source.l The External Clock Source Mode and

Synchronous Status Byte parameters are validonly for the external clock source. Set the twoparameters according to the actual condition ofthe external clock. In general cases, the twoparameters take the default values.

2 Configuring theSSM orextendedSSMprotection

A.10.2Configuring ClockSubnets

Required when the SSM or extended SSMprotection is used. Set the parameters as follows:l Set Protection Status according to the used

protocol type.l If the clock uses the extended SSM protection, set

Clock Source ID for the following clock sources:– External clock source

– Internal clock source of the NE that accessesthe external clock source

– Internal clock source of the NE that connectsthe intersecting ring and chain or connects theintersecting rings

– Line clock source that is accessed to the ringthrough the NE that connects the intersectingring and chain or connects the intersectingrings and is configured with the line clocksource on the ring

The values of Clock Source ID for these clocksources should be different.


Configuration Guide


Issue 02 (2009-10-30)


A.10.4Configuring theSSMOutputStatus

Required when the SSM or extended SSMprotection.When a line port is connected to the NE on the sameclock subnet, set Control Status to Enabled. Inother cases, set Control Status to Disabled.

A.10.5Configuring theClock IDOutputStatus

Required when the SSM or extended SSMprotection is used.When a line port is connected to the NE on the sameclock subnet, set Enabled Status to Enabled. Inother cases, set Enabled Status to Disabled.

A.10.3Self-DefinedClockQuality

Optional.

3 A.10.7 Changing theConditions for ClockSource Switching

Optional.

4 A.10.8 Modifying theRecovery Parameter ofthe Clock Source

Optional.

5 A.10.6 Modifying theParameters of theClock Output

Optional when the external clock interface is used totransmit the clock reference signal for the customerequipment.Set the parameters according to the requirement ofthe customer equipment. In general cases, theseparameters take the default values.

6 A.24 Setting theParameters of PDHInterfaces

Optional when the output tributary clock requiresretiming.Set Retiming Mode to Retiming Mode of Cross-Connect Clock for the tributary port.

7 A.10.9 Querying theClock SynchronizationStatus

l When a clock subnet uses the internal clocksource of an NE as the reference clock, set NEClock Working Mode to Free-Run Mode forthis NE; set NE Clock Working Mode toTracing Mode for the other NEs.

l When a clock subnet uses the clock out of thesubnet as the reference clock, set NE ClockWorking Mode to Tracing Mode for all the NEs.



6-13

6.3 Configuration Example (Clock for a TDM MicrowaveChain Network)

This topic considers a TDM microwave chain network as an example to describe how toconfigure the clock according to the network planning information.





Based on 3.3 Configuration Example (Radio Links on the TDM Microwave ChainNetwork), configure clocks for a network as shown in Figure 6-9 according to the clocksynchronization requirements.

l The radio transmission network is directly synchronized with the clock of the BSC.

l The clock synchronization signal is transmitted to the BTS through the E1 signal.

Figure 6-9 Networking diagram (clock for a TDM microwave chain network)

BTS3

BSC

BTS5

BTS2

NE1NE2NE3

NE5

NE4

NE6

E1

E1

E1E1

BTS4

STM-1

BTS1

E1

STM-1



Configuration Guide


Issue 02 (2009-10-30)

Clock Source InformationAccording to 6.1.3 Clock Synchronization Policy, Figure 6-10 shows the clock sourceinformation.

Figure 6-10 Clock source information (TDM microwave chain network)

BSCNE1NE2NE3

NE5

NE4

NE6

STM-1STM-1

Clock

8-SL1D-1/8-SL1D-2/

Internal

3-IF1-1/4-IF1-1/Internal

8-SL1D-1/Internal

3-IF1-1/Internal

4-IF1-1/Internal

3-IF1-1/Internal

Clock ProtectionIn this example, a chain network is set up. Thus, only the clock source protection based onpriorities is needed, whereas the SSM or extended SSM protection need not be configured.

Clock Synchronization Policy for a Base StationIn this example, the radio network is synchronized with the BSC through the SDH opticalinterface and transmits the timing reference signal through the E1 port. Hence, the E1 retimingfunction need not be enabled.


ProcedureStep 1 See A.10.1 Configuring the Clock Sources and configure the clock sources.


Parameter

Value


ClockSource

8-SL1D-18-SL1D-2InternalClockSource

3-IF1-14-IF1-1InternalClockSource

8-SL1D-1InternalClockSource

3-IF1-1InternalClockSource





6-15

Step 2 See A.10.9 Querying the Clock Synchronization Status and query the clock synchronizationstatus of the NEs.NE Working Mode of all the NEs should be Tracing Mode.

----End

6.4 Configuration Example (Clock for a TDM MicrowaveRing Network)

This topic considers a TDM microwave ring network as an example to describe how to configurethe clock according to the network planning information.





Based on 3.4 Configuration Example (Radio Links on the TDM Microwave RingNetwork), configure clocks for a network as shown in Figure 6-11 according to the clocksynchronization requirements.

l The radio transmission network is directly synchronized with the clock of the BSC.

l The clock synchronization signal is transmitted to the BTS through the E1 signal.

Figure 6-11 Networking diagram (clock for a TDM microwave ring network)

BTS2

BTS1

NE1

NE3

NE2 NE4

BSC

BTS3

BTS4

E1

E1

E1

E1

E1


Configuration Guide


Issue 02 (2009-10-30)



Figure 6-12 Clock source information (TDM microwave ring network)

NE1

NE3

NE2 NE4

BSC

E1

9-SP3S-1/Internal

3-IF1-1/Internal

4-IF1-1/Internal

3-IF1-1/Internal

Clock

Clock ProtectionIn this example, a PDH microwave ring network is set up. Thus, only the clock source protectionbased on priorities is needed, whereas the SSM or extended SSM protection need not beconfigured.

Clock Synchronization Policy for a Base StationIn this example, the radio network is synchronized with the BSC through the E1 port andtransmits the timing reference signal through the E1 port. Hence, the E1 retiming function needsto be enabled. The retiming function needs to be enabled for the following ports:

l NE2: 9-SP3S-1, 9-SP3S-5

l NE3: 9-SP3S-1

l NE4: 9-SP3S-1

NOTE

In application, the external clock interface, rather than the E1 port, is preferred to transmit the timing referencesignal to a base station.



6-17


Procedure

Step 1 See A.10.1 Configuring the Clock Sources and configure the clock sources.


Parameter Value

NE1 NE2 NE3 NE4

Clock Source 9-SP3S-1Internal ClockSource

3-IF1-1Internal ClockSource



Step 2 See A.24 Setting the Parameters of PDH Interfaces and set the PDH interface parameters.


Parameter Value

NE2 NE3 NE4

Retiming Mode Retiming Mode ofTributary Clock (9-SP3S-1)Retiming Mode ofTributary Clock (9-SP3S-5)Normal (other ports)

Retiming Mode ofTributary Clock (9-SP3S-1)Normal (other ports)

Retiming Mode ofTributary Clock (9-SP3S-1)Normal (other ports)


----End

6.5 Configuration Example (Clock for a Hybrid MicrowaveChain Network)

This topic considers a Hybrid microwave chain network as an example to describe how toconfigure clocks according to the network planning information.


6.5.2 Service Planning


Configuration Guide


Issue 02 (2009-10-30)

The service planning information contains the information about all the parameters required forconfiguring the NE data.



Based on 3.5 Configuration Example (Radio Links on the Hybrid Microwave ChainNetwork), configure clocks for a network as shown in Figure 6-13 according to the clocksynchronization requirements.

l The radio transmission network is synchronized with the clock of the BSC through a linkaggregation group (LAG) consisting of two GE links.

l The clock synchronization signal is transmitted to the BTS through the FE signal.

Figure 6-13 Networking diagram (clock for a Hybrid microwave chain network)

BSC

BTS5

BTS3

BTS2

NE1NE2NE3

NE5

NE4

NE6

FE

FE

FEFE

BTS4

BTS1

FE

GE GE





6-19

Figure 6-14 Networking diagram (clock for a Hybrid microwave chain network)

BSCNE1NE2NE3

NE5

NE4

NE6

GE GE

3-IFU2-1/4-IFU2-1Internal

7-EM4F-3/7-EM4F-4/

Internal

7-EM4T-3/Internal

3-IFU2-1/Internal

4-IFU2-1/Internal

Clock

3-IFU2-1/Internal

NOTE

Separately configure the Ethernet clock source for each link in the LAG.

Clock Protection

In this example, a chain network is set up. Thus, only the clock source protection based onpriorities is needed, whereas the SSM or extended SSM protection need not be configured.

Clock Synchronization Policy for a Base Station

In this example, the radio transmission network is synchronized with the BSC through the GEinterface, and transmits the timing reference signal to the base station through the FE interface.


Procedure



Parameter

Value


ClockSource

7-EM4F-37-EM4F-4InternalClockSource

3-IFU2-14-IFU2-1InternalClockSource

7-EM4F-3InternalClockSource

3-IFU2-1InternalClockSource




Configuration Guide


Issue 02 (2009-10-30)


----End

6.6 Configuration Example (Clock for a Hybrid MicrowaveRing Network)

This topic considers a Hybrid microwave ring network as an example to describe how toconfigure the clock according to the network planning information.





Based on 3.6 Configuration Example (Radio Links on the Hybrid Microwave RingNetwork), configure clocks for a network as shown in Figure 6-15 according to the clocksynchronization requirements.

l The radio transmission network is synchronized with the clock of the BSC through a LAGconsisting of two GE links.

l The clock synchronization signal is transmitted to the BTS through the FE signal.

Figure 6-15 Networking diagram (clock for a Hybrid microwave ring network)

BTS2

BTS1

NE1

NE3

NE2 NE4

BSC

BTS3

BTS4

GE

FE

FE

FE

FE



6-21


Clock Source Information

According to 6.1.3 Clock Synchronization Policy, Figure 6-16 shows the clock sourceinformation.

Figure 6-16 Clock source information (Hybrid microwave ring network)

NE1

NE3

NE2 NE4

BSC

FE

7-EM4T-3/7-EM4T-4/

Internal

3-IFU2-1/Internal

4-IFU2-1/Internal

3-IFU2-1/Internal

Clock

NOTE

Separately configure the Ethernet clock source for each link in the LAG.

Clock Protection

In this example, a Hybrid microwave ring network is set up. Thus, only the clock sourceprotection based on priorities is needed, whereas the SSM or extended SSM protection need notbe configured.

Clock Synchronization Policy for a Base Station

In this example, the radio transmission network is synchronized with the BSC through the FEinterface, and transmits the timing reference signal to the base station through the FE interface.



Configuration Guide


Issue 02 (2009-10-30)

Procedure



Parameter Value

NE1 NE2 NE3 NE4

Clock Source 9-SP3S-1Internal ClockSource

3-IFU2-1Internal ClockSource




----End



6-23

7 Configuring Auxiliary Interfaces andFunctions

About This Chapter

The OptiX RTN 910 provides multiple auxiliary interfaces and functions. These functionsrequire certain data configuration.

7.1 Auxiliary Interfaces and FunctionsThis topic describes the auxiliary interfaces and functions supported by the OptiX RTN 910,namely, the orderwire, synchronous data services, asynchronous data services, and waysideservices, and external alarms.

7.2 Configuration Example (Orderwire)This topic considers the orderwire on a microwave network as an example to describe how toplan the orderwire according to network planning information.

7.3 Configuration Example (Synchronous Data Services)This topic considers a synchronous data service that transmits the network managementinformation as an example to describe how to configure a synchronous data service accordingto the network planning information.

7.4 Configuration Example (Asynchronous Data Services)This topic considers an asynchronous data service that transmits the NM messages as an exampleto describe how to configure an asynchronous data service according to the network planninginformation.

7.5 Configuration Example (Wayside E1 Services)This topic considers a wayside E1 service that transmits the NM messages as an example todescribe how to configure a wayside E1 service according to the network planning planning.

7.6 Configuration Example (External Alarms)This topic considers the centralized control of environment monitoring and equipment alarmsthrough external alarms as an example to describe how to configure external alarms accordingto the network planning information.

OptiX RTN 910Configuration Guide 7 Configuring Auxiliary Interfaces and Functions


7-1

7.1 Auxiliary Interfaces and FunctionsThis topic describes the auxiliary interfaces and functions supported by the OptiX RTN 910,namely, the orderwire, synchronous data services, asynchronous data services, and waysideservices, and external alarms.

OrderwireThe OptiX RTN 910 supports one orderwire phone so that the operation or maintenanceengineers at different workstations can perform voice communication through microwave orSDH overhead bytes.

When using the orderwire phone, take the following precautions:

l The orderwire phone numbers of all the NEs on the network must be of the same length.It is recommended that the orderwire telephone number is a 3-digit number and all orderwiretelephone numbers on the entire network are unique.

l The dialing method of the orderwire phone of each node is dual-tone multifrequency.

l The call waiting time of each node should be set to the same value. If less than 30 nodesexist in the orderwire subnet, it is recommended that you set the call waiting time to fiveseconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that youset the call waiting time to nine seconds.

l The equipment supports the orderwire group call function. When one set of the OptiX RTNequipment dials the orderwire group call number "888", the orderwire phones of all theOptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call,the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-to-multipoint group call changes to a point-to-point ordinary orderwire call.

l When the orderwire signals are transmitted over a radio link, they are always transmittedthrough one customized overhead byte. When the orderwire signals are transmitted overSDH fibers, they are transmitted through the E1 or E2 byte.

l By default, all the line ports, IF ports, and unconfigured synchronous data ports on theequipment function as the orderwire ports. Therefore, in normal cases, the orderwire portsneeds to be configured only at the edge of the orderwire subnet.

l The equipment supports the transmission of orderwire overhead bytes through the 64 kbit/s synchronous data ports or external clock interfaces.

l If multiple radio links or optical transmission lines exist between two NEs, the portscorresponding to these links should be configured as the orderwire ports. In this case, exceptfor the hybrid radio links in N+1 protection, if one radio link is available between two NEs,the orderwire transmission between two NEs is normal. When the orderwire signals aretransmitted over the hybrid radio links in N+1 protection, the protection link cannot transmitthe orderwire signals.

l The equipment provides the orderwire interfaces on the SCC, cross-connect and clockboard. For definitions of the pins on the interfaces, see the OptiX RTN 910 IDU HardwareDescription.

Synchronous Data ServicesThe synchronous data service is also called the F1 data service. The OptiX RTN 910 supportsone synchronous data service. The microwave/SDH overhead bytes transmitted between twoNEs can be used for transmitting one 64 kbit/s synchronous data service.

7 Configuring Auxiliary Interfaces and FunctionsOptiX RTN 910

Configuration Guide


Issue 02 (2009-10-30)

When using the synchronous data service, take the following precautions:

l The synchronous data service is fully transparently transmitted, and the transmission rateat the interface is 64 kbit/s.

l The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errorsoccur.

l The interfaces on the equipment comply with ITU-T G.703.l When the orderwire signals are transmitted over a radio link, they are always transmitted

through one customized overhead byte. When the orderwire signals are transmitted overSDH fibers, they are always transmitted through the F1 byte.

l The equipment supports the transmission of the overhead bytes in the synchronous dataservice through the external clock interfaces to realize the service spanning function.

l When the synchronous data service is transmitted over the protected radio links or opticaltransmission lines, the synchronous data service is also protected.

l The equipment provides the synchronous data service interfaces on the SCC, cross-connectand clock board. For definitions of the pins on the interfaces, see the OptiX RTN 910 IDUHardware Description.

Asynchronous Data ServicesThe asynchronous data service is also called a transparent data service or a broadcast datainterface service. The OptiX RTN 910 supports one asynchronous data service. The microwave/SDH overhead bytes transmitted between two sites can be used for realizing full-duplexcommunication between the universal asynchronous receiver/transmitter (UART).

When using the asynchronous data service, take the following precautions:

l The asynchronous data service is fully transparently transmitted. The transmission rate andtransmission control protocol need not be configured. The transmission rate at the interfaceis 19.2 kbit/s.

l The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errorsoccur.

l The equipment provides the RS-232 electrical interface that complies with ITU-T V.24/V.28.

l The equipment supports only point-to-point communications.l When the orderwire signals are transmitted over radio links, they are always transmitted

through one customized overhead byte. When the orderwire signals are transmitted overSDH fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes.

l The equipment supports the transmission of the overhead bytes in the asynchronous dataservice through the external clock interfaces to realize the service spanning function.

l When the asynchronous data service is transmitted over the protected radio links or opticaltransmission lines, the asynchronous data service is also protected.

l The equipment provides the asynchronous data interfaces on the SCC, cross-connect andclock board. For definitions of the pins on the interfaces, see the OptiX RTN 910 IDUHardware Description.

Wayside E1 ServicesThe OptiX RTN 910 supports one wayside E1 service. The transmitted overhead bytes in theSTM-1 microwave signals can be used for transmitting one wayside E1 service between twosites in one hop of STM-1 radio link.



7-3

When using the wayside E1 service, take the following precautions:

l The wayside E1 service is supported by only STM-1 radio links or E1 radio links.

l The wayside E1 service is fully and transparently transmitted, and the transmission rate atthe interface is 2048 kbit/s.

l The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur.

l The equipment does not support the pass-through of the wayside E1 service. Therefore, thewayside E1 service is transmitted only between two sites on one hop of radio link.

l When the wayside E1 service is transmitted over the radio links in 1+1 or N+1 protectionmode, the wayside E1 service is also protected.

l The equipment adds or drops the wayside E1 service through the external clock interfaceon the SCC, cross-connect and clock board. The external clock interface complies withITU-T G.703, and the impedance on the path is 120 ohms. For definitions of the pins onthe external clock interfaces, see the OptiX RTN 910DU Hardware Description.

External Alarms

External alarms are also called Boolean alarms or relay alarms. The OptiX RTN 910 provides4-input 2-output3-input 1-output external alarms.

Figure 7-1 shows the interface circuits of the input external alarms. When the external relay isswitched off, the interface circuit generates a high-level signal. When the external relay isswitched on, the interface circuit generates a low-level signal. The board generates thecorresponding alarm based on the level that is generated by the interface circuit. Input externalalarms are mainly used for accessing the relay alarms generated by the environmental alarmgenerator.

Figure 7-1 Circuits for the input external alarms

Circuit for externalalarm input Pull-up

resistance

+3.3 V/+5 V

Output levelRelay

Externalsystem

The interface circuits for the output external alarms function the same as the external systemshown in Figure 7-1. When the external alarm output conditions specified for the NE are met,the NE drives the relay to turn on or off the switch according to the conditions that result thealarm. Otherwise, the NE drives the relay to change the switch to the reverse status that resultsin the alarm. Output external alarms are mainly used for indicating the alarm status of theequipment that is contained by the centralized alarming devices.

The equipment provides the external alarm interfaces on the SCC, cross-connect and clockboard. For definitions of the pins on the interfaces, see the OptiX RTN 910 IDU HardwareDescription.


Configuration Guide


Issue 02 (2009-10-30)

7.2 Configuration Example (Orderwire)This topic considers the orderwire on a microwave network as an example to describe how toplan the orderwire according to network planning information.





In the networking diagram shown in Figure 7-2, each NE needs to be configured with theorderwire. Except that the radio link between NE1 and NE2 is configured with 1+1 protection,all the other radio links are configured with 1+0 protection.

Figure 7-2 Networking diagram (for orderwire)

NE1NE2NE3

NE5

NE4

NE6

E1

1+11+0

1+0

1+0


Information About Orderwire Phone NumbersIn this example, the number of NEs is very small. Therefore, the orderwire phone numbers areallocated in the format of 100+NE ID, as shown in Figure 7-3.



7-5

Figure 7-3 Networking diagram (for orderwire)

NE1NE2NE3

NE5

NE4

NE6

E1

1+11+0

1+0

1+0101

102103

104

105106

Information About Orderwire Portsl In this example, the service between NE2 and NE3 is forwarded through the E1 line.

Therefore, service spanning is required. The 64 kbit/s synchronous data service interfaceis used for service spanning.

l NE2 to NE6 are located on the orderwire subnet. Hence, they use the default orderwireports (all the IF ports, line ports, and unconfigured synchronous data ports) that areautomatically mapped by the equipment.

l NE1 is not located at the edge of the orderwire subnet. Hence, it is configured accordingto the situation of NE2 to NE6. If NE1 is located at the edge of the orderwire subnet andif it is connected to an IF ports or line ports on the other orderwire subnets, the IF ports orline ports are deleted from the orderwire ports through the NMS.

l The information about orderwire ports of each NE is provided in Table 7-1.

Table 7-1 Information about orderwire ports

NE Orderwire Port

NE1 3-IFU2-14-IFU2-1F1



NE4 3-IFU2-1F1


Configuration Guide


Issue 02 (2009-10-30)

NE Orderwire Port


NE6 3-IFU2-1F1

NOTE

l An external clock interface can also be used to realize service spanning between NE2 and NE3. In this case,the external clock interface needs to be added to the orderwire port through the NMS.

l Certain orderwire ports are unnecessary. These ports do not, however, affect the orderwire phones if theydo not receive orderwire signaling.

Information About Orderwire Parametersl Fewer than 30 NEs exist on the orderwire subnet. Hence, the call waiting time needs to be

set to five seconds for these NEs.

l In this example, the SDH optical transmission equipment is not involved on the orderwiresubnet. Therefore, the overhead byte is set to E1 by default.


Procedure

Step 1 See A.29.1 Configuring the Orderwire and configure the orderwire.


Parameter

Value


CallWaitingTime(s)

5 5 5 5 5 5

Phone 1 101 102 103 104 105 106

SelectedOrderwire Port

3-IFU2-14-IFU2-1F1

3-IFU2-14-IFU2-1F1

3-IFU2-14-IFU2-1F1

3-IFU2-1F1

3-IFU2-14-IFU2-1F1

3-IFU2-1F1

----End



7-7

7.3 Configuration Example (Synchronous Data Services)This topic considers a synchronous data service that transmits the network managementinformation as an example to describe how to configure a synchronous data service accordingto the network planning information.





In the networking diagram shown in Figure 7-4, the microwave network transmits the NMmessages of the third-party equipment. The third-party equipment and the NMS use the protocolconverter to convert the NM messages carried by the Ethernet network into the NM messagescarried by the 64 kbit/s synchronous data service. Hence, the microwave network needs totransparently transmit the corresponding synchronous data only. On the network:

l NE1 and NE6 add or drop the 64 kbit/s synchronous data service. NE2, NE3, and NE5 passthrough the 64 kbit/s synchronous data service.

l Except that the radio link between NE1 and NE2 is configured with 1+1 protection, all theother radio links are configured with 1+0 protection.

Figure 7-4 Networking diagram (synchronous data services)

NE1NE2NE3

NE5

NE4

NE6

E1

1+11+0

1+0

1+0

ETH64kbps

64k/ETHConverter

64k/ETHConverter

ETH

3rd partyequipment

3rd party NM

64kbps



Configuration Guide


Issue 02 (2009-10-30)

l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.Therefore, service spanning is required. The two synchronous data interfaces between NE2and NE3 are interconnected with each other to realize the service spanning function.

l According to the service path, you can obtain the synchronous data service informationprovided in Table 7-2.

Table 7-2 Information about the synchronous data service

NE Data Channel 1 Data Channel 2

NE1 F1 3-IFU2-1

NE2 3-IFU2-1 F1

NE3 F1 4-IFU2-1

NE5 4-IFU2-1 3-IFU2-1

NE6 3-IFU2-1 F1

NOTE

l The external clock interface can also be used to realize service spanning between NE2 and NE3.

l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the activelink is configured with the synchronous data service.


Procedure

Step 1 See A.29.2 Configuring the Synchronous Data Service and configure the synchronous dataservices.


Parameter Value

NE1 NE2 NE3 NE5 NE6

DataChannel 1

F1 3-IFU2-1 F1 4-IFU2-1 3-IFU2-1

DataChannel 2

3-IFU2-1 F1 4-IFU2-1 3-IFU2-1 F1

----End



7-9

7.4 Configuration Example (Asynchronous Data Services)This topic considers an asynchronous data service that transmits the NM messages as an exampleto describe how to configure an asynchronous data service according to the network planninginformation.





In the networking diagram shown in Figure 7-5, the microwave network transmits the networkmanagement information of the third-party equipment. The third-party equipment and the NMSuse the protocol converter to convert the network management information carried by theEthernet network into the network management information carried by the RS-232 synchronousdata service. Hence, the microwave network needs to transparently transmit the correspondingsynchronous data only. On the network:

l NE1 and NE6 add or drop the asynchronous data service. NE2, NE3, and NE5 pass throughthe asynchronous data service.

l Except that the radio link between NE1 and NE2 is configured with 1+1 protection, all theother radio links are configured with 1+0 protection.

Figure 7-5 Networking diagram (asynchronous data services)

NE1NE2NE3

NE5

NE4

NE6

E1

1+11+0

1+0

1+0

ETHRS-232

RS-232/ETHConverter

RS-232/ETHConverter

ETH

3rd partyequipment

3rd party NM

RS-232



Configuration Guide


Issue 02 (2009-10-30)

l In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.Therefore, service spanning is required. The two synchronous data interfaces between NE2and NE3 are interconnected with each other to realize the service spanning function.

l In this example, the SDH equipment is not required to jointly transmit the asynchronousdata service. Hence, the overhead byte is set to SERIAL1 by default.

l According to the service path, you can obtain the asynchronous data service informationprovided in Table 7-3.

Table 7-3 Information about the asynchronous data service

NE Broadcast Data Source Broadcast Data Sink

NE1 SERIAL1 3-IFU2-1

NE2 3-IFU2-1 SERIAL1

NE3 SERIAL1 4-IFU2-1

NE5 4-IFU2-1 3-IFU2-1

NE6 3-IFU2-1 SERIAL1

NOTE

l The external clock interface can also be used to realize service spanning between NE2 and NE3.

l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the activelink is configured with the asynchronous data service.


Procedure

Step 1 See A.29.3 Configuring the Asynchronous Data Service and configure the asynchronous dataservices.


Parameter Value

NE1 NE2 NE3 NE5 NE6

OverheadByte

SERIAL3 SERIAL3 SERIAL3 SERIAL3 SERIAL3

BroadcastData Source

SERIAL1 3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1

SelectedBroadcastData Sink

3-IFU2-1 SERIAL1 4-IFU2-1 3-IFU2-1 SERIAL1

----End



7-11

7.5 Configuration Example (Wayside E1 Services)This topic considers a wayside E1 service that transmits the NM messages as an example todescribe how to configure a wayside E1 service according to the network planning planning.





In the networking shown in Figure 7-6, the STM-1 microwave network transmits the networkmanagement information of the third-party equipment. The third-party equipment and the NMSuse the protocol converter to convert the network management information carried by theEthernet network into the network management information carried by the wayside E1 service.To maximize the bandwidth utilization, the NEs transmit the service over the wayside E1channel.

Figure 7-6 Networking diagram (wayside E1 services)

NE1NE2

STM-1ETH

E1

E1/ETHConverter

3rd party NM

E1/ETHConverter

ETH

3rd partyequipment

E1


According to the service path, you can obtain the wayside E1 service information provided inTable 7-4.


Configuration Guide


Issue 02 (2009-10-30)

Table 7-4 Information about wayside E1 services

NE IF Board Whether to Enablethe Wayside E1Service

Input Slot of theWayside E1Service

NE1 3-IF1 Enabled 1

NE2 3-IF1 Enabled 1

NOTE

In the case of radio links configured with 1+1 or N+1 protection, only the active link is configured with thewayside E1 service.


Procedure

Step 1 See A.29.4 Configuring the Wayside E1 Service and configure the wayside E1 service.


Parameter Value

NE1 NE2

Port NE1-3-IF1-1 NE2-3-IF1-1

2M Wayside Enable Status Enabled Enabled

2M Wayside Input Board 1 1

----End

7.6 Configuration Example (External Alarms)This topic considers the centralized control of environment monitoring and equipment alarmsthrough external alarms as an example to describe how to configure external alarms accordingto the network planning information.






7-13


In the networking diagram shown in Figure 7-7, the external alarms on NE1 are required asfollows:

l External alarm input interface 1 is used for connecting the alarm interface on the smokesensor. When the alarm interface on the smoke sensor is closed, NE1 should report an alarm.

l External alarm input interface 2 is used for connecting the alarm interface on the watersensor. When the alarm interface on the water sensor is closed, NE1 should report an alarm.

l External alarm input interface 2 is used for connecting the alarm interface on the magneticdoor switch sensor. When the alarm interface on the magnetic door switch sensor is closed,NE1 should report an alarm, indicating that the cabinet door is open.

l External alarm output interface 1 is used for connecting the centralized alarming boxes.When a major or critical alarm is generated on NE1, the alarm output interface is closed.

Figure 7-7 Networking diagram (external alarms)

NE1

Smoke sensor

Water sensor

Magnetic doorswitch sensor

Input 1

Input 2

Input 3Output 1

Centralizedalarming box


Information About Input Alarms

According to the requirements, you can obtain the input alarm information provided in Table7-5.

Table 7-5 Information about input alarms

Input ExternalAlarm

Usage Status Alarm Mode Alarm Name Severity

Interface 1 Used An alarm isgenerated whenthe interface isclosed.

Fire alarm Major


Configuration Guide


Issue 02 (2009-10-30)

Input ExternalAlarm

Usage Status Alarm Mode Alarm Name Severity


Water alarm Major


Open cabinetdoor

Major

Information About Output AlarmsAccording to the requirements, you can obtain the output alarm information provided in Table7-6.

Table 7-6 Information about output alarms

Output External Alarm Usage Status Working Mode

Interface 1 Used Automatic Mode

NOTE

The OptiX RTN 910 supports the automatic mode and the manual mode. The manual mode is used forcommissioning the output alarms.


Procedure

Step 1 See A.29.5 Configure External Alarms and configure the external alarms.l The values for the the input alarm parameters are provided as follows.

Parameter Value

NE1

Operation Object NE1-10-AUX-CSK-1

NE1-10-AUX-CSK-2

NE1-10-AUX-CSK-3

Path Name Fire alarm Water alarm Open cabinet door

Using Status Unused Unused Unused

Alarm Mode Relay Turns On/Low Level

Relay Turns On/Low Level

Relay Turns On/Low Level



7-15

Parameter Value

NE1

Alarm Severity Major Alarm Major Alarm Major Alarm

l The values for the the output alarm parameters are provided as follows.

Parameter Value

NE1

Operation Object NE1-10-AUX-CSK-1

Use or Not Used

----End


Configuration Guide


Issue 02 (2009-10-30)

A Task Collection

This task collection contains all NMS operation tasks related to data configuration.

A.1 Managing NEsBefore you configure NEs, ensure that the NEs can be managed on the NMS.

A.2 Configuring the NE DataIf an NE is not configured after being created successfully, you need to configure the NE dataso that the NMS can manage this NE.

A.3 Configuring the Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.

A.4 Connecting Fibers or CablesTo implement the end-to-end management on the NMS, you need to connect fibers or cables.

A.5 Managing SubnetsTo facilitate NE management, you can allocate the NEs that are in the same domain or havesimilar attributes into the same subnet.

A.6 Managing CommunicationsTo manage the NE by the NMS, ensure that the DCN communication is normal.

A.7 Managing Radio LinksBefore you configure the radio link between two microwave sites, you need to configure thecorresponding information about the radio link.

A.8 Managing the MSPThe OptiX RTN 910 supports the linear MSP.

A.9 Managing TDM ServicesThe TDM services involve the SDH service and the PDH service.

A.10 Managing the ClockTo ensure the clock synchronization between transmission nodes on a transport network, youneed to manage the NE clock.

A.11 Managing the ERPSThe Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can beconfigured to protect the Ethernet service.

A.12 Managing the MSTP

OptiX RTN 910Configuration Guide A Task Collection


A-1

The OptiX RTN 910 supports only the MSTP that generates the CIST.

A.13 Managing the IGMP SnoopingIf the multicast router exists on a network, the bridge can enable the IGMP Snooping protocolto realize the multicast function with the operation of the router.

A.14 Managing the LAGLink aggregation allows one or multiple links that are attached to the same equipment to beaggregated together to form a LAG. The aggregated links can be considered as a single logicallink by the MAC address. In this manner, the bandwidth is increased and the availability of thelinks is improved.

A.15 LPT ConfigurationIf a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automaticallydisabled through the LPT function.

A.16 Managing the QoSBy managing the QoS, you can provide the services of different levels for different service types.

A.17 Using the IEEE 802.1ag OAMBy using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.

A.18 Using the IEEE 802.3ah OAMBy using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links.

A.19 Using the RMONThe remote monitoring (RMON) is mainly used to monitor the data traffic on a network segmentor on the entire network. Currently, it is one of the widely used network management standards.

A.20 Setting the Parameters of Ethernet InterfacesThis topic describes how to configure the parameters of Ethernet interfaces, including generalattributes, traffic control, layer 2 (L2) attributes, and advanced attributes.

A.21 Setting the General Attributes of the IF_ETH PortThe IF_ETH port is the internal Ethernet port in a Hybrid IF board, which is used to accessEthernet services over Hybrid microwave.

A.22 Setting the Parameters of ODU InterfacesThis topic describes how to configure the parameters of ODU interfaces, including the transmitfrequency attribute, power attribute, ODU attribute, and advanced attributes.

A.23 Setting the Parameters of SDH InterfacesThe parameters of SDH interfaces are used to configure the loopback on the SDH interface boardand the laser status.

A.24 Setting the Parameters of PDH InterfacesThe parameters of PDH interfaces are used to configure the tributary loopback, service loadindication, and tributary retiming.

A.25 Configuring Overhead BytesGenerally, the default overload bytes can meet the requirements of the device. In certain specialapplication scenarios, however, such as device interconnection, you need to change the overloadbytes according to the requirements of the interconnected device.

A.26 Configure the Ethernet ServiceThe Ethernet service is classified into two types, namely, E-Line service and E-LAN service.

A.27 Managing the MAC Address Table

A Task CollectionOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

The MAC address table is the core of the E-LAN service. The OptiX RTN 910 provides variousfunctions for managing the MAC address table.

A.28 Setting the Mode for Processing an Unknown Frame of the E-LAN ServiceAn unknown frame is a unicast frame whose destination MAC address is not listed in the MACaddress table or a broadcast frame whose destination MAC address is not listed in the multicastgroup. By default, the NE broadcasts the unknown frame. By setting the mode for processingan unknown frame of the E-LAN service, you can change the processing mode so that unknownframe can be discarded.

A.29 Configuring Auxiliary Interfaces and FunctionsThe auxiliary interfaces and functions supported by the OptiX RTN 910 include the orderwire,synchronous data service, asynchronous data service, wayside E1 service, and external alarm.



A-3

A.1 Managing NEsBefore you configure NEs, ensure that the NEs can be managed on the NMS.

A.1.1 Creating NEs by Using the Search MethodThe U2000 can find all NEs that communicate with a specific gateway NE by using the IP addressof the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition,the U2000 can create the NEs that are found in batches. Compared with the method of manuallycreating NEs, this method is faster and more reliable.

A.1.2 Creating NEs by Using the Manual MethodYou can only create NEs one by one by using the manual method. The manual method, unlikethe search method, does not allow creating NEs in batches.

A.1.3 Configuring the Logical BoardIf the logical board corresponding to the physical board is not added in the slot layout, add thelogical board in the slot layout. If the physical board is inconsistent with the logical board in theslot layout, delete the inconsistent logical board and add the correct logical board.

A.1.4 Changing the NE IDModify the NE ID according to the engineering planning to guarantee that each NE ID is unique.Modifying the NE ID does not interrupt services.

A.1.5 Changing the NE NameTo better identify the NE in the Main Topology, name the NE according to the NE geographicallocation or the device connected to the NE.

A.1.6 Synchronizing the NE TimeBy setting the NE time to be synchronous with the time on the NMS or standard NTP server,you can record the exact time when alarms and abnormal events occur.

A.1.7 Localizing the NE TimeWhen the daylight saving time (DST) is used in the area where the NE is located, you need tolocalize the NE time to synchronize the NE time with the local time.

A.1.8 Configuring Standard NTP KeysWhen the NE time is synchronized with the time on the NTP server and the identityauthentication is required, you need to configure NTP keys.

A.1.1 Creating NEs by Using the Search MethodThe U2000 can find all NEs that communicate with a specific gateway NE by using the IP addressof the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition,the U2000 can create the NEs that are found in batches. Compared with the method of manuallycreating NEs, this method is faster and more reliable.

Prerequisitel The communication between the NMS and the NE must be normal.

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

Tools, Equipment, and MaterialsU2000


Configuration Guide


Issue 02 (2009-10-30)

Procedure

Step 1 On the Main Topology, choose File > Discovery > NE.

Step 2 Optional: Add a search domain.1. Click Add, and then the Input Search Domain dialog box is displayed.2. Select an address type and enter the search address.

NOTE

l When Address Type is set to NSAP Address, ensure that the U2000 is installed with the OSI protocolstack software.

l When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000server and gateway NE are not in the same network segment, ensure that the IP routes of the networksegments to which the U2000 server and gateway NE belong are configured on the U2000 and relatedrouters.

3. Click OK.

Step 3 Optional: Repeat Step 2 to add several search domains.

Step 4 Select Search for NE in the Search for NE dialog box.

NOTE

l You can select either Create NE after search or Upload after Create or both Create NE after search andUpload after Create. In this manner, after the NE searching is complete, the system automatically createsan NE and uploads the NE.

l If Create NE after search is selected, you need to specify NE User and Password.

Step 5 Click Start Search, and then the Auto Discovery dialog box is displayed.After the search is complete, all the NEs that are found are displayed in the Result list.

Step 6 Create NEs.1. Select an NE that is not created from the Result list.2. Optional: Select the GNE ID of the NE.3. Click Create.

The Create dialog box is displayed.4. Specify User Name and Password.5. Click OK.

The icon of the created NE is displayed in the Main Topology.

Step 7 Optional: Repeat Step 6 to create other NEs that are not created.

----End



A-5

Related ReferencesB.1.1 Parameter Description: NE Searching

A.1.2 Creating NEs by Using the Manual MethodYou can only create NEs one by one by using the manual method. The manual method, unlikethe search method, does not allow creating NEs in batches.

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

l The communication between the NMS and the NE to be created must be normal.

l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be createdbelongs must be created.

Procedure

Step 1 In the Physical View, right-click New > NE.The Add Object dialog box is displayed.

Step 2 Choose RTN Series > OptiX RTN 910 from the Object Tree.

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

Step 4 Set Gateway Type for the NE.

If ... Then ...

The Gateway Type parameter is set toGateway

Proceed to the next step.

The Gateway Type parameter is set to Non-Gateway

Select the gateway to which the NE belongs,and go to Step 6.

Step 5 Specify the protocol and IP address that the NE uses.

If ... Then ...

If the Protocol parameter is set to IP Enter the IP Address of the NE.

If the Protocol parameter is set to OSI Enter the NSAP Address of the NE.


Configuration Guide


Issue 02 (2009-10-30)

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

Related ReferencesB.1.2 Parameter Description: NE Creation

A.1.3 Configuring the Logical BoardIf the logical board corresponding to the physical board is not added in the slot layout, add thelogical board in the slot layout. If the physical board is inconsistent with the logical board in theslot layout, delete the inconsistent logical board and add the correct logical board.



A-7

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


Procedure

Step 1 Double-click the NE icon to open the NE layout diagram.

Step 2 Optional: On the slot to which the board is to be added, right-click, and then select AddXXX. XXX is the name of the board to be added.

Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then select Delete.

1. A dialog box is displayed for confirmation, click OK.2. A dialog box is displayed again for confirmation, click OK.

NOTE

Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on theboard.

----End

A.1.4 Changing the NE IDModify the NE ID according to the engineering planning to guarantee that each NE ID is unique.Modifying the NE ID does not interrupt services.



Procedure

Step 1 In the Main Topology, right-click the NE whose ID needs to be modified.

Step 2 Choose Object Attributes, and then the Object Attributes dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)

Step 3 Click the NE Attribute[xxx] tab.

NOTE

xxx indicates the current name of the NE.

Step 4 Click Modify NE ID, and then the Modify NE ID dialog box is displayed.

Step 5 Specify New ID and New Extended ID.

Step 6 Click OK.A dialog box is displayed for confirmation, click OK.

Step 7 Click OK.

----End

Related ReferencesB.1.3 Parameter Description: NE Attribute_NE ID Change

A.1.5 Changing the NE NameTo better identify the NE in the Main Topology, name the NE according to the NE geographicallocation or the device connected to the NE.



Procedure

Step 1 In the Main Topology, select the NE whose name is to be modified, and then right-click.

Step 2 Select the Object Attributes, then, the Object Attributes dialog box is displayed.

Step 3 Click the NE Attribute [xxx] tab.

NOTE

xxx is the current name of the NE.

Step 4 Enter the name of the NE in Name.



A-9

Step 5 Click OK, and then close the dialog box that is displayed indicating the operation result.The new name of the NE is displayed below the NE icon in the Main Topology.

----End

A.1.6 Synchronizing the NE TimeBy setting the NE time to be synchronous with the time on the NMS or standard NTP server,you can record the exact time when alarms and abnormal events occur.


l When you need to synchronize the NE time with the time on the NMS server, the time zoneand time must be set correctly on the PC or server that is installed with the NMS software.

l When you need to synchronize the NE time with the time on the NTP server, the time onthe NTP server must be set correctly and the NTP protocol must be normal.

Tools, Equipment, and Materials

U2000

Procedure

Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from theMain Menu.

Step 2 Click the NE Time Synchronization tab.

Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click

.

Step 4 When you need to synchronize the NE time with the NMS time, set the time synchronizationmode and the related parameters.

1. Set Synchronous Mode to NM.

2. Optional: The NE time is synchronized with the NMS time immediately.

a. Right-click the NE whose time needs to be synchronized, and then chooseSynchronize with NM Time from the short-cut menu.


Configuration Guide


Issue 02 (2009-10-30)

b. In the dialog box that is displayed for confirmation, click Yes.c. Close the dialog box that is displayed indicating the operation result.

3. Click Apply.4. Optional: Set auto synchronization parameters.

a. Set auto synchronization parameters.

b. Click Apply.c. In the dialog box that is displayed for confirmation, click Yes.d. Close the dialog box that is displayed indicating the operation result.

NOTE

l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.

l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode toStandard NTP. Configure Standard NTP Authentication according to the requirements of the NTP server.

Step 5 When you need to synchronize the NE time with the time on the NTP server, set the timesynchronization mode and the related parameters.1. Set Synchronous Mode to Standard NTP.2. Configure Standard NTP Authentication according to the requirements of the NTP

server.3. Click Apply.4. Click Close, and then close the dialog box that is displayed indicating the operation result.5. Configure the upper-layer NTP server.

a. Select the NE, right-click in the configuration box where the standard NTP server isconfigured, and then choose New.



A-11

b. Configure the parameters related to the NTP server.

c. Click Apply.d. Close the dialog box that is displayed indicating the operation result.

6. Optional: Copy the configuration of the upper-layer NTP server.

a. Select the NE to be copied, right-click, and then choose Copy Standard NTPServer.

b. Select the NE to be pasted, right-click, and then choose Paste Standard NTPServer.

c. In the dialog box that is displayed for confirmation, click Yes.d. Close the dialog box that is displayed indicating the operation result.

----End

Related ReferencesB.1.4 Parameter Description: NE Time Synchronization


Configuration Guide


Issue 02 (2009-10-30)

A.1.7 Localizing the NE TimeWhen the daylight saving time (DST) is used in the area where the NE is located, you need tolocalize the NE time to synchronize the NE time with the local time.

Prerequisite

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


U2000

Procedure

Step 1 On the Main Topology, choose Configuration > NE Batch Configuration > NE TimeLocalization Management.

Step 2 Select the NE for time localization management from the Object Tree, and then click

.

Step 3 Click the Time Zone drop-down list, and then set the time zone of the NE.

Step 4 Optional: Click DST, and then configure the related parameters.

Step 5 Click Apply, and then close the dialog box that is displayed.

----End

Related ReferencesB.1.5 Parameter Description: Localization Management of the NE Time

A.1.8 Configuring Standard NTP KeysWhen the NE time is synchronized with the time on the NTP server and the identityauthentication is required, you need to configure NTP keys.


l Set Synchronous Mode used by the NE to Standard NTP and Standard NTPAuthentication to Enabled.

l The NTP protocol is normal and the NTP identity authentication is enabled on the NTPserver.


U2000



A-13

Procedure

Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from theMain Menu.

Step 2 Click the Standard NTP Key Management tab.

Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click

.

Step 4 Click Add.The Add Key and Password dialog box is displayed.

Step 5 After the related parameters are configured, click OK.

----End

A.2 Configuring the NE DataIf an NE is not configured after being created successfully, you need to configure the NE dataso that the NMS can manage this NE.

A.2.1 Uploading the NE DataUploading the NE data is commonly used for configuring the NE data. By uploading the NEdata, the data such as the configuration, alarm, and performance data of the NE is uploaded tothe NMS.


Configuration Guide


Issue 02 (2009-10-30)

A.2.1 Uploading the NE DataUploading the NE data is commonly used for configuring the NE data. By uploading the NEdata, the data such as the configuration, alarm, and performance data of the NE is uploaded tothe NMS.

Prerequisitel An NE must be logged in to successfully.



ProcedureStep 1 Select the corresponding operation steps according to the status of the NE.

If ... Then ...

An NE is not configured and the NE dataneeds to be uploaded.

In the Main Topology, double-click the NEthat is not configured, and then refer to Step2-Step 4.

An NE is configured with data and NE dataneeds to be uploaded.

Refer to Step 5-Step 8.

Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next.A dialog box is displayed for confirmation.

Step 3 Click OK.

Step 4 Click Close.

Step 5 In the Main Topology, choose Configuration > NE Configuration Data Management.

Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click .

Step 7 Select the NE, click Upload, a dialog box is displayed for confirmation, and then click OK.The uploading is started. After the uploading is complete, the Operation Result dialog box isdisplayed.

Step 8 Click Close.

----End

A.3 Configuring the Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.




A-15


Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NEPerformance Monitoring Time from the Function Tree.

Step 2 Configure the parameters of the performance monitoring of NEs.1. Select 15-Minute or 24-Hour.2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.3. Set the start time and end time of the performance monitoring of NEs.

NOTE

Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.

4. Click Apply, and then close the dialog box that is displayed.

----End

A.4 Connecting Fibers or CablesTo implement the end-to-end management on the NMS, you need to connect fibers or cables.

A.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search MethodThrough the search method, the NMS can check the information about the radio link that isconnected to a specified IF port. In this manner, a radio link can be created rapidly. The searchmethod is commonly used for creating a radio link.

A.4.2 Creating a Radio Link by Using the Manual MethodAfter you manually fill in the table, the NMS can create a radio link according to the configuredlink information. This method is used when the actual radio link is not formed.

A.4.3 Creating an SDH Optical Transmission Link by Using the Manual MethodAfter you manually fill in the table, the NMS can create a radio link according to the configuredlink information.


Configuration Guide


Issue 02 (2009-10-30)

A.4.4 Creating an Extended ECCAn NE can communicate with the NMS through the Ethernet interface or serial port. In addition,the NEs can communicate with each other through the extended embedded control channel(ECC). You can create different communication cables on the NMS according to differentcommunication modes.

A.4.5 Creating a Back-to-Back Microwave ConnectionThe back-to-back microwave connection refers to the NE cascading relation.

A.4.1 Creating an Optical Transmission Line or Radio Link byUsing the Search Method

Through the search method, the NMS can check the information about the radio link that isconnected to a specified IF port. In this manner, a radio link can be created rapidly. The searchmethod is commonly used for creating a radio link.


l The IF boards of various NEs must be created on the NMS.


Procedure

Step 1 Choose File > Discovery > Fiber from the Main Menu.

Step 2 Select the board of the NE on which the fiber needs to be searched for or the IF board of the NE

on which radio links need to be searched for from the Subject Tree, and the click .

Step 3 Click Search.

NOTE

l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whose radio linkis created is not searched on the NMS.

l If you need to check whether the connection of a created radio link is the same as the actual connectionof the radio link, do not select Do not search the ports with Fiber/Cable created on NMS.

l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected portsare created with radio links, a dialog box is displayed after the search, indicating that the search domainis null.

Step 4 After the operation is complete, a dialog box is displayed indicating that the operation issuccessful. Then, click Close.

Step 5 In Physical Fiber/Cable Link List, select one or multiple optical transmission lines or radiolinks, and then click Create Fiber/Cable.



A-17

NOTE

l When you select one or multiple optical transmission lines or radio links from Physical Fiber/CableLink List, the conflicting optical transmission lines or radio links are automatically displayed inLogical Fiber/Cable Link List. In this manner, you need to delete such conflicting optical transmissionlines or radio links by referring to Step 5, and then create the links.

l When you create an optical transmission line or radio link, if the selected optical transmission line orradio link is in the Already created state, No fiber to create is displayed.

Step 6 When you select one or multiple conflicting optical transmission lines or radio links fromLogical Fiber/Cable Link List, click Delete Fiber/Cable.

----End

Subsequent HandlingIf the information about the optical transmission line or radio link that is created through thesearch method, you can supplement the information by changing the information about theoptical transmission line or cable.

Related ReferencesB.2.1 Parameter Description: Fiber Search

A.4.2 Creating a Radio Link by Using the Manual MethodAfter you manually fill in the table, the NMS can create a radio link according to the configuredlink information. This method is used when the actual radio link is not formed.


l The IF boards of various NEs must be created on the NMS.


Procedure

Step 1 Choose File > Create > Link from the Main Menu. The Add Object dialog box is displayed.

Step 2 Choose Link > Microwave Link from the Object Tree.

Step 3 Configure the attributes of the created radio link according to the data plan.


Configuration Guide


Issue 02 (2009-10-30)

Step 4 Click OK.In the Main Topology, the created radio link is displayed between the source NE and the sinkNE.

----End

Related ReferencesB.2.3 Parameter Description: Radio Link Creation

A.4.3 Creating an SDH Optical Transmission Link by Using theManual Method

After you manually fill in the table, the NMS can create a radio link according to the configuredlink information.


l The board to be connected with the optical transmission line or cable must be created.


Procedure




A-19

Step 2 Choose Link > Fiber from the Object Tree.

Step 3 Configure the attributes of the created SDH optical transmission link according to the data plan.

Step 4 Click OK.In the Main Topology, the created SDH optical transmission link is displayed between the sourceNE and the sink NE.

----End

Related ReferencesB.2.2 Parameter Description: Fiber Creation

A.4.4 Creating an Extended ECCAn NE can communicate with the NMS through the Ethernet interface or serial port. In addition,the NEs can communicate with each other through the extended embedded control channel(ECC). You can create different communication cables on the NMS according to differentcommunication modes.

Prerequisite



U2000


Configuration Guide


Issue 02 (2009-10-30)

Procedure


Step 2 Choose Link > Extended ECC.

Step 3 Configure the attributes of the created extended ECC according to the data plan.

Step 4 Click OK.In the Main Topology, the created extended ECC is displayed between the source NE and thesink NE.

----End

A.4.5 Creating a Back-to-Back Microwave ConnectionThe back-to-back microwave connection refers to the NE cascading relation.


l The corresponding IF board must be added on the NE Panel.


Procedure

Step 1 In the Main Topology, choose File > Create > Link.The Add Object dialog box is displayed.

Step 2 Select Microwave Back to Back.

Step 3 Select the source NE from the drop-down list of Source NE.

Step 4 Select the sink NE from the drop-down list of Sink NE.

Step 5 Configure the attributes of the back-to-back microwave connection.



A-21

Step 6 Click OK.The created back-to-back microwave connection is displayed in the Main Topology.

----End

A.5 Managing SubnetsTo facilitate NE management, you can allocate the NEs that are in the same domain or havesimilar attributes into the same subnet.

A.5.1 Creating a SubnetIn the Main Topology, you can create a subnet object and allocate an NE to this subnet.

A.5.2 Copying Topology ObjectsIn the current topology, you can copy topology objects from one subnet to another subnet.

A.5.3 Moving Topology ObjectsIn the current topology, you can move topology objects from one subnet to another subnet.

A.5.1 Creating a SubnetIn the Main Topology, you can create a subnet object and allocate an NE to this subnet.



ProcedureStep 1 In the Main Topology, right-click, and then choose New > Subnet.

The Add Object dialog box is displayed.

Step 2 Click the Properties tab.

Step 3 Enter the attributes of the subnet.

Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click

to add the NE to Selected Objects.


Configuration Guide


Issue 02 (2009-10-30)

NOTE

l Click to add the selected object in the left pane to the right pane.

l Click to add all the objects in the left pane to the right pane.

Step 5 Click OK.

Step 6 In the Main Topology, click in a blank area, and then the created subnet is displayed in theposition where you click.

----End

A.5.2 Copying Topology ObjectsIn the current topology, you can copy topology objects from one subnet to another subnet.



Procedure

Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied.

Step 2 Choose Edit > Copy to.The Copy Object dialog box is displayed.

Step 3 Select the subnet that the NE or subnet needs to be pasted.

Step 4 Click OK.

----End

A.5.3 Moving Topology ObjectsIn the current topology, you can move topology objects from one subnet to another subnet.



Procedure

Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.

Step 2 Choose Edit > Move to.



A-23

The Move Object dialog box is displayed.

Step 3 Select the subnet that the NE or subnet needs to be moved to.

Step 4 Click OK.

----End

A.6 Managing CommunicationsTo manage the NE by the NMS, ensure that the DCN communication is normal.

A.6.1 Setting NE Communication ParametersThe communication parameters of an NE include the IP address of the NE, the gateway IPaddress, and the subnet mask.

A.6.2 Configuring DCCsTo meet the requirements for managing a complex network, you need to set the channel type,protocol type, or enable status of the DCCs according to the network planning information.

A.6.3 Configuring the Extended ECCWhen there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascadingports on the system control unit of the NEs to realize communication through the extended ECC.

A.6.4 Configuring DCC Transparent TransmissionThe OptiX equipment supports the DCC transparent transmission function. With this function,the equipment can transparently transmit NM messages when the OptiX equipment is usedtogether with other equipment to form a network and can also transparently transmit the NMmessages between ECC subnets.

A.6.5 Creating Static IP RoutesWhen dynamic routes fail to meet the planning requirements, you need to create thecorresponding static IP routes manually.

A.6.6 Setting Parameters of the OSPF ProtocolWhen the IP over DCC solution is used to realize the interconnection between the OptiXequipment and the third-party equipment, you need to set the parameters of the OSPF protocolaccording to the requirements of the third-party equipment, thus implementing the route protocolinterworking between the OptiX equipment and the third-party equipment.

A.6.7 Enabling the ARP ProxyThe proxy ARP enables the NEs in the same network segment but different domains tocommunicate with each other.

A.6.8 Configuring the CLNS RoleWhen the CLNS role of an NE is L1, the NE is involved in the routes in the area. When theCLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNSrole of the OptiX RTN 910 is L1.

A.6.9 Configuring the OSI TunnelThe OSI tunnel function involves the creation of a virtual LAPD channel between the NEs onthe IP network. In this manner, the NM message encapsulated in compliance with the OSIprotocol can be transparently transmitted.

A.6.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN


Configuration Guide


Issue 02 (2009-10-30)

The VLAN ID used by an inband DCN must be different from the VLAN ID used by servicesand the bandwidth by an inband DCN must meet the requirements of the transmission networkfor managing messages.

A.6.11 Configuring the Enable Status of the Inband DCN Function on PortsThe network management information can be transmitted over a link by the inband DCN onlywhen the inband DCN function is enabled on the ports at both ends of the link.

A.6.12 Querying ECC RoutesBy querying ECC routes, you can check whether the correct HWECC solution is configured andwhether the communication between NEs is normal.

A.6.13 Querying IP RoutesBy querying IP routes, you can check whether the IP over DCC solution and inband DCNsolution is configured correctly and whether the communication between NEs is normal.

A.6.14 Querying OSI RoutesBy querying OSI routes, you can check whether the OSI over DCC solution is configuredcorrectly and whether the communication between NEs is normal.

A.6.1 Setting NE Communication ParametersThe communication parameters of an NE include the IP address of the NE, the gateway IPaddress, and the subnet mask.

Prerequisite



U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >Communication Parameters from the Function Tree.

Step 2 Configure the communication parameters of the NE.

Step 3 Click Apply, and then close the dialog box that is displayed.When you configure multiple parameters, click Apply respectively.

----End

Related ReferencesB.3.1 Parameter Description: NE Communication Parameter Setting

A.6.2 Configuring DCCsTo meet the requirements for managing a complex network, you need to set the channel type,protocol type, or enable status of the DCCs according to the network planning information.



A-25



ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC

Management from the Function Tree.

Step 2 Click the DCC Rate Configuration tab.

Step 3 Optional: Set the attributes of the DCC.1. Click Create.

Then, the Create dialog box is displayed.2. Set the attributes of the DCC.

3. Click OK.

Step 4 Optional: Change the enable status of the DCC.1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.

Select the required state from the drop-down list.2. Click Apply.

Step 5 Optional: Change the protocol type of the DCC.1. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select

the required protocol type from the drop-down list.2. Click Apply.

----End

Related ReferencesB.3.2 Parameter Description: DCC Management_DCC Rate Configuration

A.6.3 Configuring the Extended ECCWhen there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascadingports on the system control unit of the NEs to realize communication through the extended ECC.



Configuration Guide


Issue 02 (2009-10-30)


U2000

Procedure

Step 1 In the NE Explorer, select the NE, and then choose Communication > ECC Management fromthe Function Tree.

Step 2 Set the ECC Extended Mode.

Step 3 Set other parameters when the ECC extended mode is set to the specified mode.

Step 4 Click Apply. A dialog box is displayed indicating that this operation will reset thecommunication between NEs.

Step 5 Click OK.

----End

Related ReferencesB.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC

A.6.4 Configuring DCC Transparent TransmissionThe OptiX equipment supports the DCC transparent transmission function. With this function,the equipment can transparently transmit NM messages when the OptiX equipment is usedtogether with other equipment to form a network and can also transparently transmit the NMmessages between ECC subnets.

Prerequisite


The DCC bytes required by the transparent transmission function must not be used.


U2000



A-27

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCCManagement from the Function Tree.

Step 2 Click the DCC Transparent Transmission Management tab.

Step 3 Click Create.Then, the Create DCC Transparent Transmission Byte dialog box is displayed.

Step 4 Set the parameters of the DCC transparent transmission byte.

Step 5 Click OK.

----End

Related ReferencesB.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management

A.6.5 Creating Static IP RoutesWhen dynamic routes fail to meet the planning requirements, you need to create thecorresponding static IP routes manually.

Prerequisite



U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP ProtocolStack Management from the Function Tree.

Step 2 Click the IP Route Management tab.

Step 3 Click New.Then, the Create an IP Route dialog box is displayed.

Step 4 Set the parameters of the static IP route.


Configuration Guide


Issue 02 (2009-10-30)

NOTE

The created static route has a lower priority than a dynamic route.

Step 5 Click OK. Close the dialog box that is displayed.

----End

Related ReferencesB.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

A.6.6 Setting Parameters of the OSPF ProtocolWhen the IP over DCC solution is used to realize the interconnection between the OptiXequipment and the third-party equipment, you need to set the parameters of the OSPF protocolaccording to the requirements of the third-party equipment, thus implementing the route protocolinterworking between the OptiX equipment and the third-party equipment.



ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol

Stack Management from the Function Tree.

Step 2 Click the OSPF Parameter Settings tab.

Step 3 Set the parameters of the OSPF protocol.

Step 4 Click Apply. Then, close the dialog box that is displayed.

----End

Related ReferencesB.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings

A.6.7 Enabling the ARP ProxyThe proxy ARP enables the NEs in the same network segment but different domains tocommunicate with each other.




A-29

Procedure


Step 2 Click the Proxy ARP tab.

Step 3 Set the enable status of the proxy ARP.

Step 4 Click Apply.

----End

A.6.8 Configuring the CLNS RoleWhen the CLNS role of an NE is L1, the NE is involved in the routes in the area. When theCLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNSrole of the OptiX RTN 910 is L1.

Prerequisite


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSIManagement from the Function Tree.

Step 2 Click the Network Layer Parameters tab.

Step 3 Set the CLNS role of the NE.

NOTE

When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.

Step 4 Click Apply.The system displays the prompt.

Step 5 Click Yes.

----End

Related ReferencesB.3.9 Parameter Description: OSI Management_Network Layer Parameter

A.6.9 Configuring the OSI TunnelThe OSI tunnel function involves the creation of a virtual LAPD channel between the NEs onthe IP network. In this manner, the NM message encapsulated in compliance with the OSIprotocol can be transparently transmitted.


Configuration Guide


Issue 02 (2009-10-30)

Prerequisite



U2000

Procedure


Step 2 Click the OSI Tunnel tab.

Step 3 Click New.Then, the Create OSI Tunnel dialog box is displayed.

Step 4 Set Remote IP Address and LAPD Actor.

Step 5 Click OK.

Step 6 Configure the attributes of the OSI tunnel according to the network planning.

Step 7 Click Apply.

----End

Related ReferencesB.3.11 Parameter Description: OSI Management_OSI Tunnel



A-31

A.6.10 Setting the VLAN ID and Bandwidth Used by an InbandDCN

The VLAN ID used by an inband DCN must be different from the VLAN ID used by servicesand the bandwidth by an inband DCN must meet the requirements of the transmission networkfor managing messages.

Prerequisite

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


U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCNManagement from the Function Tree.

Step 2 Click the Bandwidth Management tab.

Step 3 Set the VLAN ID and bandwidth used by an inband DCN.

Step 4 Click Apply.

----End

Related ReferencesB.3.12 Parameter Description: DCN Management_Bandwidth Management

A.6.11 Configuring the Enable Status of the Inband DCN Functionon Ports

The network management information can be transmitted over a link by the inband DCN onlywhen the inband DCN function is enabled on the ports at both ends of the link.

Prerequisite



U2000


Configuration Guide


Issue 02 (2009-10-30)

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCNManagement from the Function Tree.

Step 2 Click the Port Settings tab.

Step 3 Select FE/GE.

Step 4 Configure the enable status of the inband DCN function on ports.

Step 5 Click Apply.

Step 6 Select IF.

Step 7 Configure the enable status of the inband DCN function on ports.

Step 8 Click Apply.

----End

Related ReferencesB.3.13 Parameter Description: DCN Management_Port Setting

A.6.12 Querying ECC RoutesBy querying ECC routes, you can check whether the correct HWECC solution is configured andwhether the communication between NEs is normal.

Prerequisite



U2000



A-33

Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > NEECC Link Management from the Function Tree.

Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC LinkManagement List.

----End

Related ReferencesB.3.5 Parameter Description: NE ECC Link Management

A.6.13 Querying IP RoutesBy querying IP routes, you can check whether the IP over DCC solution and inband DCNsolution is configured correctly and whether the communication between NEs is normal.

Prerequisite



U2000

Procedure


Step 2 Click the IP Route Management tab.

Step 3 Click Query. Then, close the dialog box that is displayed.

Step 4 Check whether the IP routes and related parameters in the routing table are in accordance withthe planning information.

----End

Related ReferencesB.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management

A.6.14 Querying OSI RoutesBy querying OSI routes, you can check whether the OSI over DCC solution is configuredcorrectly and whether the communication between NEs is normal.

Prerequisite



Configuration Guide


Issue 02 (2009-10-30)


Procedure


Step 2 Click the Routing Table tab.

Step 3 Check whether the information in Link Adjacency Table meets the planning requirements.

Step 4 Click the L1 Routing tab to check whether the information about the L1 routes is correct.

Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct.

----End

Related ReferencesB.3.10 Parameter Description: OSI Management_Routing Table

A.7 Managing Radio LinksBefore you configure the radio link between two microwave sites, you need to configure thecorresponding information about the radio link.

A.7.1 Creating an IF 1+1 Protection GroupIf the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.

A.7.2 Creating an XPIC Protection GroupIf you configure two XPIC radio links after binding the two radio links as an XPIC workgroup,the parameter settings including the channel bandwidth, transmit frequency, transmit power, andATPC attribute are ensured to be the same for the two radio links.

A.7.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio LinkAfter the XPIC protection group is created, you need to configure the Hybrid/AM attributes ofthe XPIC Hybrid radio link according to the planned values.

A.7.4 Configuring the IF/ODU Information of a Radio LinkBy configuring the IF/ODU information of a radio link, you can configure the IF/ODUinformation that is frequently used by the SDH/PDH radio link based on each radio link.

A.7.5 Setting the Hybrid/AM AttributeBy configuring the Hybrid/AM attribute, you can set the working mode of the Hybrid IF boards.

A.7.6 Creating an N+1 Protection GroupWhen multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode,you can adopt the N+1 protection configuration.

A.7.7 Setting IF AttributesIn the case of different IF boards, different parameters need to be set.

A.7.8 Configuring the ATPC FunctionTo configure the ATPC function, set the ATPC attributes of the IF board.



A-35

A.7.9 Setting the State of an ODU TransmitterThe state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in theunmute state, the ODU transmits and receives microwave signals normally. When the ODUtransmitter is in the mute state, the ODU transmitter does not work, but the ODU can receivemicrowave signals.

A.7.10 Querying the ATPC Adjustment RecordsBy querying the ATPC adjustment records, you can be familiar with the running status of theATPC function.

A.7.11 Querying the History Transmit Power and Receive PowerQuerying the change trend of the history transmit power and receive power can provide referencefor radio link troubleshooting.

A.7.12 Querying the AM StatusBy querying the AM status, you can trace the change of the modulation mode when the AMfunction is used.

A.7.13 Querying the IF 1+1 Protection StatusYou can learn about the current information of the IF 1+1 protection by querying the IF 1+1protection status.

A.7.14 Querying the IF N+1 Protection StatusYou can learn about the current information of the IF N+1 protection by querying the IF N+1protection status.

A.7.15 IF 1+1 Protection SwitchingYou can perform external switching on the IF 1+1 protection by performing IF 1+1 protectionswitching.

A.7.16 IF N+1 Protection SwitchingYou can perform external switching on the IF N+1 protection by performing IF N+1 protectionswitching.

A.7.17 Starting/Stopping the N+1 Protection ProtocolIf you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can berestored to the initial state.

A.7.1 Creating an IF 1+1 Protection GroupIf the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.


l The IF boards and the ODUs to which the IF boards are connected must be added on theNE Panel.

l The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.



Configuration Guide


Issue 02 (2009-10-30)

Background InformationWhen a 1+0 service is converted into a 1+1 service through the configuration of the IF 1+1protection group, the original service is not interrupted. The board where the original serviceexists, however, needs to be set to the working board.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1Protection from the Function Tree.

Step 2 Click Create.The Create IF 1+1 Protection dialog box is displayed.

Step 3 Configure the parameters of the IF 1+1 protection group.

Step 4 Click Apply, and then close the dialog box that is displayed indicating the operation result.

----End

Related ReferencesB.4.5 Parameter: IF 1+1 Protection_Create

A.7.2 Creating an XPIC Protection GroupIf you configure two XPIC radio links after binding the two radio links as an XPIC workgroup,the parameter settings including the channel bandwidth, transmit frequency, transmit power, andATPC attribute are ensured to be the same for the two radio links.


l The IFX2 boards and the ODUs to which the IFX2 boards are connected must be added onthe NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LinkConfiguration from the Function Tree.



A-37

Step 2 Click the XPIC tab.

Step 3 Click New.The Create XPIC Protection Group dialog box is displayed.

Step 4 Configure the parameters for the XPIC protection group.

Step 5 Click OK.

----End

Related ReferencesB.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation

A.7.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid RadioLink

After the XPIC protection group is created, you need to configure the Hybrid/AM attributes ofthe XPIC Hybrid radio link according to the planned values.


l The XPIC protection group must be created.


Background InformationThe IFX2 board supports the Hybrid/AM function.


Configuration Guide


Issue 02 (2009-10-30)

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LinkConfiguration from the Function Tree.

Step 2 Click the XPIC tab.

Step 3 Click the Hybrid/AM Configuration tab.

Step 4 Configure the Hybrid/AM attributes of the XPIC Hybrid radio link.

Step 5 Click Apply.

----End

Related ReferencesB.4.2 Parameter Description: Link Configuration_XPIC

A.7.4 Configuring the IF/ODU Information of a Radio LinkBy configuring the IF/ODU information of a radio link, you can configure the IF/ODUinformation that is frequently used by the SDH/PDH radio link based on each radio link.




U2000

Precautionsl 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 active device.

l In 1+1 FD protection mode, one protection group corresponds to one radio link. In thiscase, you need configure the IF/ODU information of the active device and the ODUinformation of the standby device.



A-39

l In the case of one XPIC radio link, one XPIC workgroup corresponds to two radio links.The IF/ODU information of the two radio links in different polarization directions shouldbe separately configured.

Procedure

Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration fromthe Function Tree.

Step 2 Click the IF/ODU Configuration tab.

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 orODU to which the IF board is connected belongs.

Step 4 Configure the corresponding IF information of the radio link.

Step 5 Click Apply.

Step 6 Configure the corresponding ODU information of the radio link.

Step 7 Click Apply.

----End

Related ReferencesB.4.7 Parameter: Link Configuration_IF/ODU Configuration

A.7.5 Setting the Hybrid/AM AttributeBy configuring the Hybrid/AM attribute, you can set the working mode of the Hybrid IF boards.




U2000

Background Information

The OptiX RTN 910 supports the Hybrid/AM function and the corresponding IF boards areIFU2 and IFX2.

Procedure

Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then chooseConfiguration > Hybrid/AM Configuration from the Function Tree.

Step 2 Configure the parameters of the Hybrid/AM attribute.


Configuration Guide


Issue 02 (2009-10-30)

Step 3 Click Apply.

----End

Related ReferencesB.14.3 Parameter Description: Hybrid/AM Configuration

A.7.6 Creating an N+1 Protection GroupWhen multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode,you can adopt the N+1 protection configuration.



l The IF1 boards must work in the STM-1 mode.


Background InformationWhen an N+0 service is converted into an N+1 service through the configuration of the N+1protection group, the original service is not interrupted.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1Protection from the Function Tree.

Step 2 Click Create.The Create N+1 Protection dialog box is displayed.



A-41

Step 3 Configure the attributes of the N+1 protection group.

Step 4 Configure the mapping relation between the board and the slot.1. Select Work Unit from Select Mapping Direction.2. Select an IF port to which a working channel corresponds from Select Mapping Way, and

then click .3. Repeat 4b to select the IF ports to which other working channels correspond. Click

.4. Select Protection Unit from Select Mapping Direction.5. Select an IF port to which a protection channel corresponds from Select Mapping Way,

and then click .

Step 5 Click OK. Close the dialog box that is displayed indicating the operation result.

----End

Related ReferencesB.4.3 Parameter Description: N+1 Protection_Create

A.7.7 Setting IF AttributesIn the case of different IF boards, different parameters need to be set.





Configuration Guide


Issue 02 (2009-10-30)

Contextl The IF1 board is used for TDM microwave.

l The IFU2 board is used for Hybrid.

l The IFX2 board is used for XPIC Hybrid.

Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > IF Interface from the Function Tree.

Step 2 Click the IF Attributes tab.

Step 3 Configure the parameters of IF attributes.

Step 4 Click Apply.

----End

Related ReferencesB.14.1 Parameter Description: IF Interface_IF Attribute

A.7.8 Configuring the ATPC FunctionTo configure the ATPC function, set the ATPC attributes of the IF board.



Precautionsl For the IF boards that are configured with 1+1 protection, configure only the ATPC

attributes of the active IF board.l The following procedure describes the configuration of ATPC parameters in the IF interface

configuration dialog box of the IF board. You can also configure ATPC parameters in thefollowing 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 changed.


Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > IF Interface from the Function Tree.



A-43

Step 2 Click the ATPC Attributes tab.

Step 3 Configure the parameters of ATPC attributes.

Step 4 Click Apply.

----End

Related ReferencesB.14.2 Parameter Description: IF Interface_ATPC Attribute

A.7.9 Setting the State of an ODU TransmitterThe state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in theunmute state, the ODU transmits and receives microwave signals normally. When the ODUtransmitter is in the mute state, the ODU transmitter does not work, but the ODU can receivemicrowave signals.


l The corresponding IF boards and the ODUs connected to the IF boards must be added tothe NE Panel.


U2000

Procedure

Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODUInterface from the Function Tree.

Step 2 Click the Advanced Attributes tab.

Step 3 Set Configure Transmission Status for the ODU.

Step 4 Click Apply.

----End

A.7.10 Querying the ATPC Adjustment RecordsBy querying the ATPC adjustment records, you can be familiar with the running status of theATPC function.


Configuration Guide


Issue 02 (2009-10-30)


l The corresponding IF board must be added.


U2000

Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > ATPC Adjustment Records from the Function Tree.

Step 2 Click Query to query the running information of the ATPC function.

----End

Related ReferencesB.14.4 Parameter Description: ATPC Adjustment Records

A.7.11 Querying the History Transmit Power and Receive PowerQuerying the change trend of the history transmit power and receive power can provide referencefor radio link troubleshooting.


l The corresponding IF boards and the ODUs connected to the IF boards must be added tothe NE Panel.


U2000

Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > Performance Graph Analyze from the Function Tree.

Step 2 Specify the start time and end time of a specific time span.

NOTE

The time span starts from the last routine maintenance time to the current time.

Step 3 Set Monitoring Period and Power.

Step 4 Click Draw. The history transmit and receive power curve of the ODU in the specified timespan is displayed.

----End



A-45

A.7.12 Querying the AM StatusBy querying the AM status, you can trace the change of the modulation mode when the AMfunction is used.


l The IF 1+1 protection must be configured.


U2000

Procedure

Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then chooseConfiguration > Hybrid/AM Configuration from the Function Tree.

Step 2 Click Query.

Step 3 Query the AM status.

----End

Related ReferencesB.14.3 Parameter Description: Hybrid/AM Configuration

A.7.13 Querying the IF 1+1 Protection StatusYou can learn about the current information of the IF 1+1 protection by querying the IF 1+1protection status.

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



U2000

Procedure


Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check theIF 1+1 protection groups.

Step 3 Select the IF 1+1 protection group whose protection status needs to be queried.


Configuration Guide


Issue 02 (2009-10-30)

Step 4 Click Query Switch Status, and then close the displayed prompt dialog box. In Slot MappingRelation, check the protection status of the IF 1+1 protection group.

----End

Related ReferencesB.4.6 Parameter Description: IF 1+1 Protection

A.7.14 Querying the IF N+1 Protection StatusYou can learn about the current information of the IF N+1 protection by querying the IF N+1protection status.


l The IF N+1 protection must be configured.


Procedure


Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check theIF N+1 protection groups.

Step 3 Select the IF N+1 protection group whose protection status needs to be queried.

Step 4 Click Query Switch Status, and then close the displayed prompt dialog box. In Slot MappingRelation, check the IF N+1 protection status.

----End

Related ReferencesB.4.4 Parameter Description: N+1 Protection

A.7.15 IF 1+1 Protection SwitchingYou can perform external switching on the IF 1+1 protection by performing IF 1+1 protectionswitching.






A-47

Procedure


Step 2 In Protection Group, select the protection group for protection switching.

Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group,and then right-click the selected unit.

Step 4 Choose the required switching mode from the shortcut menu, and then close the displayed dialogbox.

Step 5 Click Query Switch Status to check whether the switching operation is successful.

----End

A.7.16 IF N+1 Protection SwitchingYou can perform external switching on the IF N+1 protection by performing IF N+1 protectionswitching.




Procedure


Step 2 In Protection Group, select the protection group for protection switching.

Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group,and then right-click the selected unit.

Step 4 Choose the required switching mode from the shortcut menu, and then close the displayed dialogbox.

Step 5 Click Query Switch Status to check whether the switching operation is successful.

----End

A.7.17 Starting/Stopping the N+1 Protection ProtocolIf you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can berestored to the initial state.



Configuration Guide


Issue 02 (2009-10-30)



Precautionsl Stopping the N+1 protection protocol causes a failure of the N+1 protection.

l When services are switched onto the protection channel, stopping the N+1 protectionprotocol causes switchover of the services back to the working tunnel. At this time, if theworking channel is normal, the services are transiently interrupted. If the working channelis faulty, the services are interrupted until the working channel is restored to normal or theN+1 protection protocol is started.

Procedure


Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to bestarted.

Step 3 Click Start Protocol or Stop Protocol. Close the displayed prompt dialog box.

Step 4 Click Query to check the protocol status.

----End

A.8 Managing the MSPThe OptiX RTN 910 supports the linear MSP.

A.8.1 Configuring Linear MSPYou can configure linear MSP to protect services over the optical fibers between two nodes.

A.8.2 Querying the Status of the Linear MSPBy using this operation, you can know the current information about the linear MSP.

A.8.3 Performing Linear MSP SwitchingBy using this operation, you can perform the external switching on the linear MSP.

A.8.4 Starting/Stopping the Linear MSP ProtocolIf you first stop the linear MSP protocol and then start it, the linear MSP status can be restoredto the initial state.

A.8.1 Configuring Linear MSPYou can configure linear MSP to protect services over the optical fibers between two nodes.


l The corresponding board must be added on the NE Panel.



A-49


U2000


When an unprotected service is converted into a linear MSP service by configuring the linearMSP, the original services are not interrupted.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MSfrom the Function Tree.

Step 2 Click Create.The system displays the Create a Linear Multiplex Section dialog box.

Step 3 Set the parameters of the linear MSP group.

Step 4 Click OK, and then close the dialog box that is displayed.

----End


Configuration Guide


Issue 02 (2009-10-30)

Postrequisitel 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 andthe protection channels.

l In the case of the 1+1 linear MSP, you need to configure unidirectional cross-connectionsbetween the services and the protection channels, in addition to configuring thebidirectional cross-connections between the services and the working channels.

Related ReferencesB.5.1 Parameter Description: Linear MSP_Creation

A.8.2 Querying the Status of the Linear MSPBy using this operation, you can know the current information about the linear MSP.


l The linear MSP must be configured.


U2000

Procedure


Step 2 Click Query > Query Protection Group to query the current linear MSP group.

Step 3 In Protection Group, click the linear MSP group to be queried.

Step 4 Click Query > Query Switching Status, and then close the dialog box that is displayed. In SlotMapping Relation, query the status of the linear MSP.

----End

Related ReferencesB.5.2 Parameter Description: Linear MSP

A.8.3 Performing Linear MSP SwitchingBy using this operation, you can perform the external switching on the linear MSP.





A-51


U2000

Procedure


Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Relation, selectthe working unit or protection unit, and then right-click.

Step 3 Right-click and select the required switching mode, and then close the dialog box that isdisplayed.

----End

A.8.4 Starting/Stopping the Linear MSP ProtocolIf you first stop the linear MSP protocol and then start it, the linear MSP status can be restoredto the initial state.




U2000

Precautionsl Stopping the ring MSP protocol causes failure of ring MSP.

l When services are switched onto the protection channel, stopping the ring MSP protocolcauses the services to switch back to the working channel. At this time, if the workingchannel is normal, the services are transiently interrupted; if the working channel is faulty,the services are interrupted until the working channel is restored to normal or the protocolis started.

Procedure


Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be stopped.

Step 3 Click Start Protocol or Stop Protocol. Close the prompt dialog box that is displayed.

Step 4 Click Query to query the protocol status.

----End


Configuration Guide


Issue 02 (2009-10-30)

A.9 Managing TDM ServicesThe TDM services involve the SDH service and the PDH service.

A.9.1 Creating the Cross-Connections of Point-to-Point ServicesIn a cross-connection of point-to-point services, one service source corresponds to one servicesink.

A.9.2 Creating Cross-Connections of SNCP ServicesThe cross-connection of SNCP services is a cross-connection that a working source and aprotection source correspond to a service sink.

A.9.3 Configuring the Automatic Switching of SNCP ServicesYou can manually add certain alarms for the automatic switching of SNCP services.

A.9.4 Deleting Cross-ConnectionsWhen a service is not used, you can delete the cross-connections of this service to release thecorresponding resources.

A.9.5 Converting a Normal Service into an SNCP ServiceBy converting a normal service into an SNCP service, you can convert the unidirectional cross-connections of a normal service into the unidirectional cross-connection in the receive directionof the SNCP service.

A.9.6 Converting an SNCP Service to a Normal ServiceBy converting an SNCP service to a normal service, you can convert the SNCP cross-connectionin the receive direction into the unidirectional cross-connection of the normal service.

A.9.7 Querying TDM ServicesYou can learn about the TDM services that are configured for an NE by querying TDM services.

A.9.8 Switching SNCP ServicesYou can perform external switching on SNCP services by performing this operation.

A.9.9 Querying the Protection Status of SNCP ServicesYou can know the current information of an SNCP service by querying the protection status ofSNCP services.

A.9.10 Testing the E1 Service Through PRBSIf no BER tester is available, you can test the E1 service by using the PRBS test system embeddedin the equipment.

A.9.1 Creating the Cross-Connections of Point-to-Point ServicesIn a cross-connection of point-to-point services, one service source corresponds to one servicesink.


l The corresponding source and sink boards must be added on NE Panel.




A-53

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH ServiceConfiguration from the Function Tree.

Step 2 Click Create.The Create SDH Service dialog box is displayed.

Step 3 Configure the parameters of a new SDH service.


----End

Related ReferencesB.6.1 Parameter Description: SDH Service Configuration_Creation

A.9.2 Creating Cross-Connections of SNCP ServicesThe cross-connection of SNCP services is a cross-connection that a working source and aprotection source correspond to a service sink.


l The corresponding source and sink boards must be added on NE Panel.


Procedure


Step 2 Click Create SNCP Service.The Create SNCP Service dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)

Step 3 Configure the parameters of a new SNCP service.


----End

Related ReferencesB.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation

A.9.3 Configuring the Automatic Switching of SNCP ServicesYou can manually add certain alarms for the automatic switching of SNCP services.


l The SNCP protection group must be configured.


U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP ServiceControl from the Function Tree.



A-55

Step 2 Select the SNCP protection group, and then right-click Initiation Condition to which theworking service corresponds.

Step 3 Set the initiation condition for the working service. Click OK.

Step 4 Right-click Initiation Condition to which the protection service corresponds.

Step 5 Set the initiation condition for the protection service. Click OK.

NOTE

It is recommended that you set Initiation Condition of the working service to be the same as InitiationCondition of the protection service.


----End

Related ReferencesB.6.6 Parameter Description: SNCP Service Control

A.9.4 Deleting Cross-ConnectionsWhen a service is not used, you can delete the cross-connections of this service to release thecorresponding resources.


l The cross-connections of the service must be configured and the service must not be used.


Procedure


Step 2 Query the related data.1. Click Query.

Then, a dialog box is displayed, indicating that this operation will update the service datasaved on the NMS.


Configuration Guide


Issue 02 (2009-10-30)

2. Click OK. Then, close the dialog box that is displayed.

Step 3 Select the cross-connection that needs to be deleted in Cross-Connection.

Step 4 Deactivate the service.1. Right-click the service and choose Deactivate from the shortcut menu.

Then, a dialog box is displayed, querying whether you need to deactivate the selectedservice.

2. Click OK.Then, a dialog box is displayed, indicating that this operation will clear the correspondingservice data on the NE side.

3. Click OK. Then, close the dialog box that is displayed.

Step 5 Delete the service.1. Right-click the service and choose Delete from the shortcut menu.

Then, a dialog box is displayed, querying whether you need to delete the selected service.2. Click OK. Then, close the dialog box that is displayed.

Step 6 Click Query. The queried information should show that the cross-connection is already deleted.

----End

A.9.5 Converting a Normal Service into an SNCP ServiceBy converting a normal service into an SNCP service, you can convert the unidirectional cross-connections of a normal service into the unidirectional cross-connection in the receive directionof the SNCP service.


l The unidirectional cross-connection of the normal service must be configured and thesource of the cross-connection must be a line board.


Background InformationWhen this task is performed to convert a normal service into an SNCP service, the originalservices are not interrupted.

Procedure


Step 2 In Cross-Connection, select the configured SDH service. Right-click and choose Expand toUnidirectional from the shortcut menu.

Step 3 Select the expanded unidirectional service. Right-click and choose Convert to SNCP Servicefrom the shortcut menu.



A-57

Then, a dialog box is displayed, querying whether you need to perform this operation.

Step 4 Click OK.Then, the Create SNCP Service dialog box is displayed.

Step 5 Set the parameters of the SNCP service.

Step 6 Click OK.

----End

Related ReferencesB.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services IntoSNCP Services

A.9.6 Converting an SNCP Service to a Normal ServiceBy converting an SNCP service to a normal service, you can convert the SNCP cross-connectionin the receive direction into the unidirectional cross-connection of the normal service.


l The SNCP cross-connection in the receive direction must be configured.

l The current service must be transmitted on the working path.


U2000


Configuration Guide


Issue 02 (2009-10-30)

Background InformationWhen this task is performed to convert an SNCP service into a normal service, the originalservices are not interrupted.

Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > SDH Service Configuration from the Function Tree.

Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and chooseConvert to Non-Protection Service from the shortcut menu.Then, a dialog box is displayed, querying whether you need to perform this operation.

Step 3 Click OK.

----End

PostrequisiteYou also need to delete the unidirectional cross-connection between the service source and theworking path or the unidirectional cross-connection between the service source and theprotection path. The SNCP service can be converted into the normal service both in the receivedirection and the transmit direction only after the deletion.

Related ReferencesB.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services IntoNormal Services

A.9.7 Querying TDM ServicesYou can learn about the TDM services that are configured for an NE by querying TDM services.


l TDM services must be configured.


Procedure


Step 2 Click Query.

Step 3 In the displayed dialog box for confirmation, click OK.

Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services.

----End



A-59

Related ReferencesB.6.5 Parameter Description: SDH Service Configuration

A.9.8 Switching SNCP ServicesYou can perform external switching on SNCP services by performing this operation.




Procedure


Step 2 Select the SNCP protection group for SNCP service switching.

Step 3 Click Function. Select the required switching mode from the displayed menu.

Step 4 In the displayed dialog box for confirmation, click OK.

Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, closethe displayed prompt dialog box.

Step 6 Choose Function > Query Switch Status to check whether the switching operation issuccessful.

----End

A.9.9 Querying the Protection Status of SNCP ServicesYou can know the current information of an SNCP service by querying the protection status ofSNCP services.




Procedure



Configuration Guide


Issue 02 (2009-10-30)

Step 2 Select the SNCP protection group whose service protection status needs to be queried.

Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.

----End

Related ReferencesB.6.6 Parameter Description: SNCP Service Control

A.9.10 Testing the E1 Service Through PRBSIf no BER tester is available, you can test the E1 service by using the PRBS test system embeddedin the equipment.

Prerequisitel The NE equipment must be configured with E1 services, and the E1 services must be

transmitted through the DDF.l The communication between the NMS and the NE must be normal.


Precautions

CAUTIONl When a PRBS test is performed, the services carried on the tested path are interrupted.

l The PRBS test can be performed only in a unidirectional manner and on one path at a time.

Procedure

Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site.1. Select the PDH interface board in the Object Tree.2. In the Function Tree, choose Configuration > PDH Interface.3. Select By Function and select Tributary Loopback from the drop-down menu.4. In Tributary Loopback, select Inloop.5. Click Apply.

The Confirm dialog box is displayed.6. Click OK.

The Prompt dialog box is displayed.7. Click OK.

The Operation Result dialog box is displayed.8. Click Close.



A-61

Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree.

Step 3 In the Function Tree, choose Configuration > PRBS Test.

Step 4 Select the first E1 port, and then set the following PRBS-related parameters:l Direction: Cross

l Duration: a value from 120 to 180

l Measured in Time: seconds

Step 5 Click Start to Test.The system displays a dialog box indicating The operation may interrupt the service, Areyou sure to continue?

Step 6 Click OK.

Step 7 When the Progress column is 100%, click Query to check the test result.The curve diagram should be green.

Step 8 Release the inloop set in Step 1.1. Select the PDH interface board in the Object Tree.2. In the Function Tree, choose Configuration > PDH Interface.3. Select By Function and select Tributary Loopback from the drop-down menu.4. In Tributary Loopback, select Non-Loopback.5. Click Apply.

The Confirm dialog box is displayed.6. Click OK.

The Prompt dialog box is displayed.7. Click OK.

The Operation Result dialog box is displayed.8. Click Close.

Step 9 Repeat Step 1 through Step 8 to test all other E1 ports.

----End

A.10 Managing the ClockTo ensure the clock synchronization between transmission nodes on a transport network, youneed to manage the NE clock.


Configuration Guide


Issue 02 (2009-10-30)

A.10.1 Configuring the Clock SourcesThis topic describes how to configure the clock source according to the planned clocksynchronization scheme to ensure that all the NEs on the network trace the same clock.

A.10.2 Configuring Clock SubnetsFor simple networks, such as chain networks, you need not configure the clock source protectionor you only need to configure the clock priority to implement the clock source protection. Forcomplex networks, such as ring networks or intersecting and tangent rings that are derived fromring networks, you need to configure clock subnets and enable the standard SSM protocol orextended SSM protocol to implement the clock source protection.

A.10.3 Self-Defined Clock QualityBy default, the NE considers the clock quality extracted from the clock source as the clockquality. If the clock quality is zero (the synchronization quality is unknown), the clock isconsidered as unavailable clock. In the case of any special requirements, the user can define theclock quality for which the source clock quality and clock quality are zero.

A.10.4 Configuring the SSM Output StatusAfter the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs throughthe SDH radio link or optical line by default. To prevent two clock subnets from affecting eachother, the NE needs to forbid the clock ID from being transmitted on the link that is connectedto other clock subnets.

A.10.5 Configuring the Clock ID Output StatusAfter the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEsthrough the SDH radio link or optical line by default. To prevent two clock subnets from affectingeach other, the NE needs to forbid the clock ID from being transmitted on the link that isconnected to other clock subnets.

A.10.6 Modifying the Parameters of the Clock OutputThe NE outputs the 2-Mbit/s external clock regardless of the clock quality.

A.10.7 Changing the Conditions for Clock Source SwitchingYou can change the default conditions for clock source switching of the NE for special purposes.

A.10.8 Modifying the Recovery Parameter of the Clock SourceIn the case of the special requirements, you can modify the recovery parameter of the clocksource.

A.10.9 Querying the Clock Synchronization StatusYou can know the current clock synchronization status of an NE by querying the clocksynchronization status.

A.10.1 Configuring the Clock SourcesThis topic describes how to configure the clock source according to the planned clocksynchronization scheme to ensure that all the NEs on the network trace the same clock.

Prerequisite



U2000



A-63

ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock

Source Priority.

Step 2 Click the System Clock Source Priority List tab.

Step 3 Click Create.The Add Clock Source dialog box is displayed.

Step 4 Select the clock sources.TIP

By pressing the Ctrl key on the keyboard, you can select multiple clock sources at one time.

Step 5 Click OK.

Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources.

Step 7 Optional: Select a clock source and click or to adjust the priority of thisclock source.

NOTE

The clock priorities levels are arranged in a descending order from the first row to the last row. The internalclock source is always of the lowest priority.

Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the externalclock sources.

----End

Related ReferencesB.7.1 Parameter Description: Clock Source Priority Table

A.10.2 Configuring Clock SubnetsFor simple networks, such as chain networks, you need not configure the clock source protectionor you only need to configure the clock priority to implement the clock source protection. For


Configuration Guide


Issue 02 (2009-10-30)

complex networks, such as ring networks or intersecting and tangent rings that are derived fromring networks, you need to configure clock subnets and enable the standard SSM protocol orextended SSM protocol to implement the clock source protection.


l The priority list of the clock source must be configured.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > ClockSubnet Configuration.

Step 2 Click the Clock Subnet tab.

Step 3 Start the clock protection protocol and configure its parameters.

Step 4 Click Apply.

----End

Related ReferencesB.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet

A.10.3 Self-Defined Clock QualityBy default, the NE considers the clock quality extracted from the clock source as the clockquality. If the clock quality is zero (the synchronization quality is unknown), the clock isconsidered as unavailable clock. In the case of any special requirements, the user can define theclock quality for which the source clock quality and clock quality are zero.


l The priority level of a clock source must be set.




A-65

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > ClockSubnet Configuration.

Step 2 Click the Clock Quality tab.

Step 3 Click the Clock Source Quality tab.

Step 4 Set the self-defined clock quality.

NOTE

Generally, it is recommended that you use the default value.

Step 5 Click Apply.

Step 6 Click the Manual Setting of 0 Quality Level tab.

Step 7 Set the clock quality for which the quality level is zero.

NOTE

Generally, it is recommended that you use the default value.

Step 8 Click Apply.

----End

Related ReferencesB.7.3 Parameter Description: Clock Subnet Setting_Clock Quality

A.10.4 Configuring the SSM Output StatusAfter the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs throughthe SDH radio link or optical line by default. To prevent two clock subnets from affecting eachother, the NE needs to forbid the clock ID from being transmitted on the link that is connectedto other clock subnets.



l The SSM protocol must be enabled or extended.


U2000


Configuration Guide


Issue 02 (2009-10-30)


Subnet Configuration.

Step 2 Click the SSM Output Control tab.

Step 3 Set the SSM control status.

Step 4 Click Apply.

----End

Related ReferencesB.7.4 Parameter Description: Clock Subset Setting_SSM Output Control

A.10.5 Configuring the Clock ID Output StatusAfter the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEsthrough the SDH radio link or optical line by default. To prevent two clock subnets from affectingeach other, the NE needs to forbid the clock ID from being transmitted on the link that isconnected to other clock subnets.



l The extended SSM protocol must be enabled.



Subnet Configuration.

Step 2 Click the Clock ID Status tab.

Step 3 Set the clock ID control status.

Step 4 Click Apply.

----End

Related ReferencesB.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status



A-67

A.10.6 Modifying the Parameters of the Clock OutputThe NE outputs the 2-Mbit/s external clock regardless of the clock quality.



ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >

Phase-Locked Source Output by External Clock.

Step 2 Modify the parameters of the clock output.

Step 3 Click Apply.

----End

Related ReferencesB.7.8 Parameter Description: Output Phase-Locked Source of the External Clock Source

A.10.7 Changing the Conditions for Clock Source SwitchingYou can change the default conditions for clock source switching of the NE for special purposes.




Source Switching.

Step 2 Click the Clock Source Switching Conditiontab.

Step 3 Change the conditions for clock source switching.

Step 4 Click Apply.

----End


Configuration Guide


Issue 02 (2009-10-30)

Related ReferencesB.7.7 Parameter Description: Clock Source Switching_Clock Source Switching

A.10.8 Modifying the Recovery Parameter of the Clock SourceIn the case of the special requirements, you can modify the recovery parameter of the clocksource.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > ClockSource Switching.

Step 2 Click the Clock Source Reversion Parameter tab.

Step 3 Set the recovery parameter of the clock source.

Step 4 Click Apply.

----End

Related ReferencesB.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

A.10.9 Querying the Clock Synchronization StatusYou can know the current clock synchronization status of an NE by querying the clocksynchronization status.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > ClockSynchronization Status.



A-69

Step 2 Query the clock synchronization status.

----End

Related ReferencesB.7.9 Parameter Description: Clock Synchronization Status

A.11 Managing the ERPSThe Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can beconfigured to protect the Ethernet service.

A.11.1 Creating Ethernet Ring Protection InstancesThe Ethernet ring protection switching (ERPS) protection is configured through creation ofEthernet ring protection instances.

A.11.2 Setting the Parameters of Ethernet Ring ProtocolThe parameters to be set include the hold-off time, WTR time, and guard time.

A.11.3 Querying the Status of the Ethernet Ring ProtocolBy using this operation, you can know the current status of the Ethernet ring protection switching(ERPS).

A.11.1 Creating Ethernet Ring Protection InstancesThe Ethernet ring protection switching (ERPS) protection is configured through creation ofEthernet ring protection instances.


l The Ethernet boards or hybrid IF boards must be added to the NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtection > ERPS Management.

Step 2 Click New.The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.

Step 3 Set the parameters for the ERPS protection instance.


Configuration Guide


Issue 02 (2009-10-30)

Step 4 Click OK.

----End

Related ReferencesB.9.1 Parameter Description: ERPS Management_Creation

A.11.2 Setting the Parameters of Ethernet Ring ProtocolThe parameters to be set include the hold-off time, WTR time, and guard time.


l The protection instance of the ERPS must be created.


U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtection > ERPS Management from the Function Tree.

Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.

Step 3 Set the parameters of Ethernet ring protocol.



A-71

Step 4 Click Apply.

----End

Related ReferencesB.9.2 Parameter Description: ERPS Management

A.11.3 Querying the Status of the Ethernet Ring ProtocolBy using this operation, you can know the current status of the Ethernet ring protection switching(ERPS).



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtection > ERPS Management from the Function Tree.

Step 2 Click Query.

Step 3 Query the status of the Ethernet ring protocol.

----End

Related ReferencesB.9.2 Parameter Description: ERPS Management

A.12 Managing the MSTPThe OptiX RTN 910 supports only the MSTP that generates the CIST.

A.12.1 Creating the MSTP Port GroupWhen the NE needs to run the MSTP protocol together with the user network, the ports on theNE that are connected to the user network need to be configured as a port group. All the membersin the port group are involved in the spanning tree algorithm of the user network.

A.12.2 Setting the Bridge Parameters of the MSTPThis topic describes how to set the bridge parameters and port parameters of the MSTP.

A.12.3 Setting the Parameters of the CISTThis topic describes how to set the CIST parameters, including the bridge priority, port priority,and path overheads.

A.12.4 Querying the CIST Running InformationBy querying the CIST running information, you can be familiar with the current information ofthe CIST.


Configuration Guide


Issue 02 (2009-10-30)

A.12.5 Changing the Spanning Tree Protocol Used by the Port GroupWhen the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTPprotocol) for the equipment that runs the spanning tree together with the local NE, you need tochange the spanning tree protocol used by the port group on the local NE to be the same.

A.12.6 Enabling/Disabling the MSTP ProtocolThis topic describes how to enable or disable the MSTP protocol of a port group or members ofthe port group.

A.12.7 Modifying the Configuration Data of the MSTP Port GroupThis topic describes how to modify the configuration data of the MSTP port group.

A.12.1 Creating the MSTP Port GroupWhen the NE needs to run the MSTP protocol together with the user network, the ports on theNE that are connected to the user network need to be configured as a port group. All the membersin the port group are involved in the spanning tree algorithm of the user network.


l The boards where the member ports are located must be added in NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtocol Configuration > MSTP Configuration from the Function Tree.

Step 2 Click the Port Group Parameters tab.

Step 3 Click Create. The Create Port Group dialog box is displayed.Then, the Create Port Group dialog box is displayed.

Step 4 Set the attributes of the port group.1. Set Protocol Type and Enable Protocol.1. Select the board where the member port is located from the drop-down list of Board under

Apply Port.

2. Select the member port from Available Port List. Then, click .TIP

To select more than one port at a time, press and hold the Ctrl key when selecting the ports.



A-73

3. Click OK.

----End

Related ReferencesB.9.3 Parameter Description: MSTP Configuration_Port Group Creation

A.12.2 Setting the Bridge Parameters of the MSTPThis topic describes how to set the bridge parameters and port parameters of the MSTP.


l The port group must be created.


Procedure


Step 2 Click the Bridge Parameters tab.

Step 3 Select the port group ID.

Step 4 Click the Bridge Parameters tab.

Step 5 Set the attributes of the bridge.

Step 6 Click Apply.

Step 7 Click the Port Parameter tab.


Configuration Guide


Issue 02 (2009-10-30)

Step 8 Set the parameters of each member of the port group.

Step 9 Click Apply.

----End

Related ReferencesB.9.5 Parameter Description: MSTP Configuration_ Bridge Parameters

A.12.3 Setting the Parameters of the CISTThis topic describes how to set the CIST parameters, including the bridge priority, port priority,and path overheads.


l The port group must be created.


Procedure


Step 2 Click the CIST&MSTI Parameters tab.

Step 3 Select the port group from the drop-down list of Port Group.

Step 4 Set the parameters of the port group.



A-75

Step 5 Click Apply.

----End

Related ReferencesB.9.6 Parameter Description: MSTP Configuration_CIST Parameters

A.12.4 Querying the CIST Running InformationBy querying the CIST running information, you can be familiar with the current information ofthe CIST.


l The MSTP port group must be created.


Procedure


Step 2 Click the CIST Running Information tab.

Step 3 Click Query.

Step 4 Query the CIST running information.

----End


Configuration Guide


Issue 02 (2009-10-30)

Related ReferencesB.9.7 Parameter Description: MSTP Configuration_Running Information About the CIST

A.12.5 Changing the Spanning Tree Protocol Used by the PortGroup

When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTPprotocol) for the equipment that runs the spanning tree together with the local NE, you need tochange the spanning tree protocol used by the port group on the local NE to be the same.



Procedure



Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whosespanning tree protocol needs to be changed.

Step 4 Click Apply.

----End

A.12.6 Enabling/Disabling the MSTP ProtocolThis topic describes how to enable or disable the MSTP protocol of a port group or members ofthe port group.



Procedure




A-77


Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group forwhich the MSTP protocol needs to be enabled or disabled.

Step 4 Click Apply.

Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to enableor disable the MSTP protocol of a port.

Step 6 Click Apply.

----End

A.12.7 Modifying the Configuration Data of the MSTP Port GroupThis topic describes how to modify the configuration data of the MSTP port group.

Prerequisite



U2000

Procedure



Step 3 Click Configuration.Then, the Configure Port Group dialog box is displayed.

Step 4 Modify the configuration data of the MSTP port group.

Option Description

If ... Then ...


Configuration Guide


Issue 02 (2009-10-30)

Option Description

A member port needs to be added 1. Select the board where the member ports are locatedfrom the drop-down list of Board.

2. Select the port to be added from Available PortList.

3. Click .

A member port needs to be deleted 1. Select the board where the member ports are locatedfrom the drop-down list of Board.

2. Select the port to be deleted from Selected PortList.

3. Click .

TIP


Step 5 Click OK.

----End

Related ReferencesB.9.4 Parameter Description: MSTP Configuration_Port Group Configuration

A.13 Managing the IGMP SnoopingIf the multicast router exists on a network, the bridge can enable the IGMP Snooping protocolto realize the multicast function with the operation of the router.

A.13.1 Configuring the IGMP Snooping ProtocolThis topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.

A.13.2 Querying the Port Information of the Routers



A-79

By querying the port information of the router, you can be familiar with the port information ofeach router that runs the IGMP Snooping protocol.

A.13.3 Querying the Information About the Multicast GroupsThis topic describes how to query the information about each multicast group in the IGMPSnooping protocol.

A.13.4 Creating Static Router PortsStatic router ports are not aged.

A.13.5 Creating a Member of a Static Multicast GroupThe members of a static multicast group are not aged.

A.13.6 Adding a Quickly Deleted PortIf an Ethernet port is connected to only one host, you can set this Ethernet port as a quicklydeleted port.

A.13.7 Calculating IGMP PacketsBy calculating IGMP packets, you can be familiar with the information about the IGMP packetsreceived and transmitted through the IGMP Snooping protocol.

A.13.1 Configuring the IGMP Snooping ProtocolThis topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.


l The E-LAN service must be created.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtocol Configuration > IGMP Snooping Configuration from the Function Tree.

Step 2 Click the Protocol Configuration tab.

Step 3 Set the attributes of the IGMP Snooping protocol.

Step 4 Click Apply.

----End

Related ReferencesB.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration

A.13.2 Querying the Port Information of the RoutersBy querying the port information of the router, you can be familiar with the port information ofeach router that runs the IGMP Snooping protocol.


Configuration Guide


Issue 02 (2009-10-30)

Prerequisite



U2000

Procedure


Step 2 Click the Router Port Management tab.

Step 3 Click Query.

Step 4 Query the port information of the routers.

----End

Related ReferencesB.9.10 Parameter Description: IGMP Snooping Configuration_Route Management

A.13.3 Querying the Information About the Multicast GroupsThis topic describes how to query the information about each multicast group in the IGMPSnooping protocol.



l The NNI port must be configured for the E-LAN service.


U2000

Procedure


Step 2 Click the Route Member Port Management tab.

Step 3 Click Query.

Step 4 Query the information about the multicast groups.

----End



A-81

Related ReferencesB.9.12 Parameter Description: IGMP Snooping Configuration_Route Member PortManagement

A.13.4 Creating Static Router PortsStatic router ports are not aged.



l The UNI port must be configured for the E-LAN service.


U2000

Procedure


Step 2 Click the Router Port Management tab.

Step 3 Click New.

Step 4 Set the attributes of the static router ports.

1. Set Service ID and VLAN ID.

1. Select the static router port from the drop-down list of Available Port. Click .TIP


2. Click OK.

----End


Configuration Guide


Issue 02 (2009-10-30)

Related ReferencesB.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation

A.13.5 Creating a Member of a Static Multicast GroupThe members of a static multicast group are not aged.



l The NNI port must be configured for the E-LAN service.


U2000

Procedure


Step 2 Click the Route Member Port Management tab.

Step 3 Click New.

Step 4 Set the attributes of members in the static multicast group.

1. Set Service ID and VLAN ID.

1. Select the member ports from the drop-down list of Available Port. Click .TIP


2. Click OK.

----End



A-83

Related ReferencesB.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group MemberCreation

A.13.6 Adding a Quickly Deleted PortIf an Ethernet port is connected to only one host, you can set this Ethernet port as a quicklydeleted port.



Procedure


Step 2 Click the Protocol Configuration tab.

Step 3 Click Add.

Step 4 Set the attributes of the quickly deleted port.

Step 5 Click Apply.

----End

Related ReferencesB.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be QuicklyDeleted

A.13.7 Calculating IGMP PacketsBy calculating IGMP packets, you can be familiar with the information about the IGMP packetsreceived and transmitted through the IGMP Snooping protocol.



Procedure



Configuration Guide


Issue 02 (2009-10-30)

Step 2 Click the Packet Statistics tab.

Step 3 Click Query.

Step 4 Calculate the IGMP packets.

----End

Related ReferencesB.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics

A.14 Managing the LAGLink aggregation allows one or multiple links that are attached to the same equipment to beaggregated together to form a LAG. The aggregated links can be considered as a single logicallink by the MAC address. In this manner, the bandwidth is increased and the availability of thelinks is improved.

A.14.1 Creating a LAGBetween two NEs, if the bandwidth and availability of the Ethernet links need to be improved,the new LAG must be created.

A.14.2 Setting the Port PriorityIn a LAG that uses the static aggregation mode, a port with higher priority is first selected totransmit services.

A.14.3 Querying the Protocol Information of the LAGThrough this operation, you can learn about the running information of the LACP used for theLAG.

A.14.1 Creating a LAGBetween two NEs, if the bandwidth and availability of the Ethernet links need to be improved,the new LAG must be created.


l The board on which the LAG port to be created must be added to the NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > InterfaceManagement > Link Aggregation Group Management from the Function Tree.

Step 2 Click the Link Aggregation Group Management tab.

Step 3 Click New. The Create Link Aggregation Group dialog box is displayed.The system displays the Create Link Aggregation Group dialog box.



A-85

Step 4 Set the attributes of the LAG in Attribute Settings.

Step 5 Set the LAG port in Port Settings.1. Set Main Board and Main Port.2. In Available Slave Ports, select Board of the slave port.

3. In Port, select the slave port, and then click .TIP

Hold on the Ctrl key on the keyboard to select multiple ports.

4. Click OK, a dialog box is displayed for confirmation, and then click OK to close the dialogbox.

----End

Related ReferencesB.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation


Configuration Guide


Issue 02 (2009-10-30)

A.14.2 Setting the Port PriorityIn a LAG that uses the static aggregation mode, a port with higher priority is first selected totransmit services.


l The board on which the LAG to be created must be added to NE Panel.


Procedure


Step 2 Click the Port Priority tab.

Step 3 Set the port priority.


----End

Related ReferencesB.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority

A.14.3 Querying the Protocol Information of the LAGThrough this operation, you can learn about the running information of the LACP used for theLAG.



Procedure


Step 2 Click the Link Aggregation Group Management tab.

Step 3 Click Query, and then close the displayed prompt dialog box.

Step 4 In the Main Interface, select the LAG to be queried and then query the information about theLAG.



A-87

The system displays the information about the slave port in the lower part of the Main Interface.

Step 5 Click the Port Priority tab.

Step 6 Click Query, and then close the displayed prompt dialog box.

Step 7 Query the port priority of the LAG.

----End

A.15 LPT ConfigurationIf a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automaticallydisabled through the LPT function.


l The corresponding board must be added to the NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPTManagement from the Function Tree.

Step 2 Click New.The Create LPT dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)

Step 3 Configure the board and port of the Convergence Point.

Step 4 Set Access Point.1. In the Board list, select the board of the access point.

2. In Port, select the required port, and then click .

Step 5 Click OK.

----End

Related ReferencesB.9.17 Parameter Description: LPT Management_Creation

A.16 Managing the QoSBy managing the QoS, you can provide the services of different levels for different service types.

A.16.1 Creating a DS DomainBy creating a DS domain, you can create the mapping relation of a new DS domain and configurethe ports that use this mapping relationship.

A.16.2 Changing the Ports That Use the DS DomainThis topic describes how to add or delete a port that uses the DS domain and set the packet typeover the port.

A.16.3 Creating a Port PolicyBy creating a port policy, you can create a new port policy.



A-89

A.16.4 Creating the TrafficBy creating the traffic, you can configure ACL and CAR for a specified traffic stream on aspecified port.

A.16.5 Setting the Port That Uses the Port PolicyThis topic describes how to set the port that uses the port policy.

A.16.6 Configuring Port ShapingThis topic describes how to configure the traffic shaping for a port or an egress port.

A.16.7 Querying the Port PolicyThis topic describes how to query the port policy of a port.

A.16.8 Querying the DS Domain of a PortThis topic describes how to query the mapping relation between a port and a DS domain.

A.16.1 Creating a DS DomainBy creating a DS domain, you can create the mapping relation of a new DS domain and configurethe ports that use this mapping relationship.


l The board of the Ethernet ports must be added on NE Panel.


Background InformationThe OptiX RTN 910 has a default DS domain, whose Mapping Relation ID is 1 and MappingRelation Name is default map. Before another DS domain is created, all the ports belong to thisdefault DS domain. The default DS domain cannot be modified or deleted.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Diffserv Domain Management from the Function Tree.

Step 2 Click Create. The Create DS Mapping Relation dialog box is displayed.The Create DS Mapping Relation dialog box is displayed.

Step 3 On the main interface, configure the attributes of the DS domain.

Step 4 Click the Ingress Mapping Relation tab.

Step 5 Configure the mapping relations between the priorities of ingress packets and PHB serviceclasses.

Step 6 Click the Egress Mapping Relation tab.

Step 7 Configure the mapping relations between the priorities of egress packets and PHB serviceclasses.


Configuration Guide


Issue 02 (2009-10-30)

Step 8 Select Board where the application ports exist from Application Port.

Step 9 Select a port from Available Port, and then click .TIP


Step 10 Click OK.

----End

Related ReferencesB.11.2 Parameter Description: DiffServ Domain Management_Create

A.16.2 Changing the Ports That Use the DS DomainThis topic describes how to add or delete a port that uses the DS domain and set the packet typeover the port.


l The DS domain must be created.



A-91


Background InformationThe OptiX RTN 910 has a default DS domain, for which Mapping Relation ID is 1 andMapping Relation Name is Default Map. Before another DS domain is created, all the portsbelong to this default DS domain. You cannot add or delete a port that uses the default DSdomain.

ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS

Management > Diffserv Domain Management from the Function Tree.

Step 2 Select the DS domain for which you need to add or delete an application port on the maininterface.

Step 3 Click the Apply Port tab.

Step 4 Click Modify.

Step 5 Add or delete a port that uses the DS domain.

Option Description

If ... Then ...

You need to add a port that uses the DSdomain

1. Select the board where the application port islocated from the drop-down list of Board.

2. Select the port to be added from the drop-down list of Available Port.

3. Click .

You need to delete a port that uses the DSdomain

1. Select the board where the application port islocated from the drop-down list of Board.

2. Select the port to be deleted from the drop-down list of Available Port.

3. Click .

You need to change the packet typeidentified by the port

Select a new packet type from the drop-down listof Packet Type.

TIP


Step 6 Click OK.

----End

Related ReferencesB.11.3 Parameter Description: DiffServ Domain Applied Port_Modification


Configuration Guide


Issue 02 (2009-10-30)

A.16.3 Creating a Port PolicyBy creating a port policy, you can create a new port policy.


l The board of the Ethernet ports must be added on NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Policy Management from the Function Tree.

Step 2 Click New. The Create Port Policy dialog box is displayed.

Step 3 Set the ID and name of the port policy.

Step 4 Configure the scheduling, weight, and shaping of the egress queue.

Step 5 Click OK.

----End

Related ReferencesB.11.5 Parameter Description: Port Policy

A.16.4 Creating the TrafficBy creating the traffic, you can configure ACL and CAR for a specified traffic stream on aspecified port.


l The Ethernet board must be added on the NE Panel.



A-93

l The port policy must be created.


U2000

Procedure


Step 2 Click the Traffic Classification Configuration tab.

Step 3 Click New. The Create Traffic Classification dialog box is displayed.The Create Traffic Classification dialog box is displayed.

Step 4 Configure the attributes of a new traffic.

Step 5 Click OK.

----End

Related ReferencesB.11.6 Parameter Description: Port Policy_Traffic Classification Configuration


Configuration Guide


Issue 02 (2009-10-30)

A.16.5 Setting the Port That Uses the Port PolicyThis topic describes how to set the port that uses the port policy.


Tools, Instruments, and MaterialsU2000

Procedure


Step 2 Click the Applied Object tab.

Step 3 Click Modify.Then, the Configure Port dialog box is displayed.

Step 4 Set the port that uses the port policy.1. Select Board where the port that needs to use the port policy from Applied Port.

2. Select a port from Available Port, and then click .TIP


Step 5 Click OK.

----End

Related ReferencesB.11.4 Parameter Description: Policy Management



A-95

A.16.6 Configuring Port ShapingThis topic describes how to configure the traffic shaping for a port or an egress port.


l The Ethernet board must be created on the NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Port Shaping Management from the Function Tree.

Step 2 Click New.The New dialog box is displayed.

Step 3 Set the parameters for the shaping of a port.

Step 4 Click OK.

----End

Related ReferencesB.11.7 Parameter Description: Port Shaping Management_Creation

A.16.7 Querying the Port PolicyThis topic describes how to query the port policy of a port.




Configuration Guide


Issue 02 (2009-10-30)

Procedure


Step 2 Click the CoS Queue Configuration tab.

Step 3 Click Query.

Step 4 Query the CoS configuration of the port policy.

Step 5 Click the Traffic Classification Configuration tab.

Step 6 Click Query.

Step 7 Query the traffic classification of the port policy.

Step 8 Click the Applied Object tab.

Step 9 Click Query.

Step 10 Query the ports that use the port policy.

----End

Related ReferencesB.11.4 Parameter Description: Policy Management

A.16.8 Querying the DS Domain of a PortThis topic describes how to query the mapping relation between a port and a DS domain.

Prerequisite



U2000


The OptiX RTN 910 has a default DS domain, for which Mapping Relation ID is 1 andMapping Relation Name is Default Map. Before another DS domain is created, all the portsbelong to this default DS domain. The default DS domain cannot be modified or deleted.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Diffserv Domain Management from the Function Tree.

Step 2 Click the Ingress Mapping Relation tab.

Step 3 Click Query.



A-97

Step 4 Query the attributes of the DS domain and the mapping relation between the priority level ofthe packets in the ingress direction and the PHB service class.

Step 5 Click the Egress Mapping Relation tab.

Step 6 Click Query.

Step 7 Query the attributes of the DS domain and the mapping relation between the priority level ofthe packets in the egress direction and the PHB service class.

Step 8 Click the Apply Port tab.

Step 9 Click Query.

Step 10 Query the ports that use the DS domain.

----End

Related ReferencesB.11.1 Parameter Description: Diffserv Domain Management

A.17 Using the IEEE 802.1ag OAMBy using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.

A.17.1 Creating an MDA maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of differentranges and levels can provide users with differentiated OAM services.

A.17.2 Creating an MAAn MD can be divided into several independent maintenance associations (MAs). By creatingMAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAMoperations.

A.17.3 Creating an MEP PointAn MEP is the starting and end positions of all the OAM packets. By creating an MEP, you cancheck the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.

A.17.4 Creating Remote MEPs in an MATo ensure that an MEP can respond to the OAM operations initiated by the other MEPs in thesame MA, you need to set the other MEPs to be the remote MEPs of this MEP.

A.17.5 Creating an MIPThe maintenance association intermediate points (MIPs) can respond to specific OAM packets.By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA intoseveral segments, thus facilitating the detection of the Ethernet link.

A.17.6 Performing a CC TestAfter the continuity check (CC) test, the unidirectional link status can be checked automaticallyand periodically. If the link is fault after the CC test is started at the source end, the sink equipmentreports the corresponding alarm.

A.17.7 Performing an LB TestDuring a loopback (LB) test, you can check the bidirectional connectivity between the sourceMEP and any MEP in the same maintenance association (MA).

A.17.8 Performing an LT Test


Configuration Guide


Issue 02 (2009-10-30)

Based on the LB test, the link trace (LT) test further improves the capability to locate faults.That is, the faulty network segment can be located according to the MIP through only one test.

A.17.1 Creating an MDA maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of differentranges and levels can provide users with differentiated OAM services.




Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetOAM Management > Ethernet Service OAM Management from the Function Tree.

Step 2 Click the Maintenance Association tab.

Step 3 Choose New > New Maintenance Domain.The system displays the New Maintenance Domain dialog box.

Step 4 Set the parameters of the MD.


----End

Related ReferencesB.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance DomainCreation

A.17.2 Creating an MAAn MD can be divided into several independent maintenance associations (MAs). By creatingMAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAMoperations.


l The MD must be created.



A-99

l The Ethernet service must be created.


Procedure



Step 3 Select the maintenance domain in which a maintenance association needs to be created. ChooseNew > New Maintenance Association.The system displays the New Maintenance Association dialog box.

Step 4 Set the parameters of the MA.

NOTE

Click in Relevant Service. Select the corresponding services in the Select Service dialog boxthat is displayed.


----End

Related ReferencesB.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance AssociationCreation

A.17.3 Creating an MEP PointAn MEP is the starting and end positions of all the OAM packets. By creating an MEP, you cancheck the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.


l The MA must be created.



Configuration Guide


Issue 02 (2009-10-30)

Procedure



Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > NewMEP Point.The system displays the New MEP Point dialog box.

Step 4 Set the parameters of the MEP point.


----End

Related ReferencesB.10.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

A.17.4 Creating Remote MEPs in an MATo ensure that an MEP can respond to the OAM operations initiated by the other MEPs in thesame MA, you need to set the other MEPs to be the remote MEPs of this MEP.




Procedure





A-101

Step 3 Choose OAM > Manage Remote MEP Point. Then, the Maintenance Domain Name dialogbox is displayed.

Step 4 Click New.Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed.

Step 5 Set the parameters of the new remote MEPs.

----End

Related ReferencesB.10.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation

A.17.5 Creating an MIPThe maintenance association intermediate points (MIPs) can respond to specific OAM packets.By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA intoseveral segments, thus facilitating the detection of the Ethernet link.




U2000

Procedure


Step 2 Click the MIP Point tab.

Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.Then, the New MIP Maintenance Point dialog box is displayed.

Step 4 Set the parameters of the new MIP.


Configuration Guide


Issue 02 (2009-10-30)

Step 5 Click OK. Then, close the dialog box that is displayed.

----End

Related ReferencesB.10.5 Parameter Description: Ethernet Service OAM Management_MIP Creation

A.17.6 Performing a CC TestAfter the continuity check (CC) test, the unidirectional link status can be checked automaticallyand periodically. If the link is fault after the CC test is started at the source end, the sink equipmentreports the corresponding alarm.


l The MEP must be created.

l The remote MEPs must be created.


Background Informationl Only the MEP can enable the CC test and function as the receiving and responding end in

the test.l During the CC check, the source MEP constructs and transmits continuity check message

(CCM) packets periodically. After receiving the CCM packets from the source MEP, thesink MEP directly enables the CC function for this source MEP. If the sink MEP fails toreceive the CCM packets from the source MEP within the check period (that is, 3.5 timesof the transmit period), it reports the alarm automatically.

l Performing a CC test does not affect the services.

Procedure



Step 3 Select the MEP where you need to perform the CC test and then choose OAM > ActivateCC.Then, a dialog box is displayed, indicating that the operation is successful.

NOTE

Before the CC test, you can set CC Test Transmit Period(ms) according to the actual requirements.TIP

l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC fromthe shortcut menu.

l To disable a CC test, right-click the MEP where the CC test is performed and then choose DeactivateCC from the shortcut menu.



A-103

Step 4 Click Close.

----End

A.17.7 Performing an LB TestDuring a loopback (LB) test, you can check the bidirectional connectivity between the sourceMEP and any MEP in the same maintenance association (MA).


l The source and sink MEPs in the same maintenance domain must be created.


l The CC function must be enabled.


Background Informationl Only MEPs can initiate the LB test, and the MEP can work as the receive end in the test.

l During the LB test, the source MEP constructs and transmits the LBM frames and startsthe timer. If the sink MP receives the LBM frames, it sends the LBR frames back to thesource MEP. This indicates that the loopback is successful. If the source MEP timer timesout, it indicates that the loopback fails.

l Performing a LB test does not affect the services.

Procedure



Step 3 Select the maintenance domain and maintenance association for the LB test.

Step 4 Choose OAM > Start LB. The LB Test dialog box is displayed.Then, the LB Test dialog box is displayed.

TIP

To enable a LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.

Step 5 Set the parameters involved in the LB test.


Configuration Guide


Issue 02 (2009-10-30)

Step 6 Click Start Test. Then, the LB test result is displayed in the Test Result window.

----End

Related ReferencesB.10.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

A.17.8 Performing an LT TestBased on the LB test, the link trace (LT) test further improves the capability to locate faults.That is, the faulty network segment can be located according to the MIP through only one test.


l The source and sink MEPs in the same MD must be created.


l The CC function must be enabled.


Background Informationl Only MEPs can initiate the LT test and work as the termination point in the test.

l During the LT test, the source MEP constructs and transmits the LTM frames and startsthe timer. All the MPs that receive the LTM frames send the LTR frame response.According to the LTR frame response, you can verify all the MIPs that pass from the sourceMEP to the sink MEP.

l Performing a LT test does not affect the services.

Procedure



Step 3 Select the maintenance domain and maintenance association for the LT test.

Step 4 Choose OAM > Start LT. The LT Test dialog box is displayed.Then, the LT Test dialog box is displayed.



A-105

TIP

To enable a LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.

Step 5 Set the parameters involved in the LT test.

Step 6 Click Start Test. Then, the LT test result is displayed in the Test Result window.

----End

Related ReferencesB.10.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

A.18 Using the IEEE 802.3ah OAMBy using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links.

A.18.1 Enabling the OAM Auto-Discovery FunctionThe IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link.

A.18.2 Enabling the Link Event NotificationAfter the link event notification is enabled on the local equipment, if the OAM detects a linkfault and link performance event, the opposite equipment is informed.

A.18.3 Modifying the OAM Error Frame Monitoring ThresholdThe threshold for the OAM error frame monitoring is a standard for the OAM to detect the linkperformance. Generally, the default value is used. You can modify the value according to thesituation of the link.

A.18.4 Performing Remote LoopbackAfter the Ethernet port on the local equipment sends data to the port on the interconnectedequipment, the local end can request the opposite end to return the data.

A.18.5 Enabling Self-Loop DetectionAfter enabling the self-loop detection on an Ethernet port, you can check the loopback of theport and the loopback between the port and other Ethernet ports on the board.

A.18.1 Enabling the OAM Auto-Discovery FunctionThe IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link.




Configuration Guide


Issue 02 (2009-10-30)


The OAM auto-discovery is realized through the auto-negotiation between the local equipmentand the opposite equipment. If the negotiation fails, the local equipment reports an alarm. Afterthe OAM auto-discovery succeeds, the link performance is monitored according to the errorframe threshold. You can set the error frame threshold on the NMS.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetOAM Management > Ethernet Port OAM Management from the Function Tree.

Step 2 Click the OAM Parameter tab.

Step 3 Select the port, and set OAM Working Mode.

NOTE

l The OAM mode includes the active mode and the passive mode. For two interconnected systems, theOAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discoveryfails.

l If the OAM modes of the two systems are both passive modes, a fault occurs on the line, or one systemfails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-discovery fails.

Step 4 Set Enable OAM Protocol to Enabled.

Step 5 Click Apply, and then close the displayed prompt dialog box.

Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of theopposite end, and then close the displayed prompt dialog box.

----End

Related ReferencesB.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter

A.18.2 Enabling the Link Event NotificationAfter the link event notification is enabled on the local equipment, if the OAM detects a linkfault and link performance event, the opposite equipment is informed.


l The OAM auto-discovery operation must successful on the equipment at both ends.



A-107


U2000


After the OAM auto-discovery operation is successful at both ends, the link fault detection andperformance detection are automatically started.

l To report the detected link fault event to the opposite equipment, you need to set RemoteAlarm Support for Link Event to Enabled for the local equipment.

l To report the detected link fault event to the opposite equipment, you need to set RemoteAlarm Support for Link Event to Enabled and set Error Frame Period Window(Frame) and Error Frame Monitor Threshold for the local equipment.

l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, ifthe opposite end detects link performance degradation, you can query theETH_EFM_Event alarm, which is reported on the local end, by using the NMS. Accordingto the alarm, you can determine the type of the link performance event.

l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, ifthe opposite equipment detects a link fault event, you can query the ETH_EFM_Faultalarm, which is reported at the local end, by using the NMS. According to the alarm, youcan determine the fault type.

Procedure



Step 3 Select the corresponding port and set Link Event Notification to Enabled.


----End

Related ReferencesB.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter

A.18.3 Modifying the OAM Error Frame Monitoring ThresholdThe threshold for the OAM error frame monitoring is a standard for the OAM to detect the linkperformance. Generally, the default value is used. You can modify the value according to thesituation of the link.


Configuration Guide


Issue 02 (2009-10-30)


l The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAMauto-discovery operation must be successful on the equipment at both ends.


U2000


After the OAM auto-discovery operation is successful, set Error Frame Period Window(Frame) and Error Frame Monitor Threshold, and set Remote Alarm Support for LinkEvent to Enabled for the local equipment. If the local equipment detects a link event in thereceive direction, it informs the opposite equipment of the link event. If the remote alarm forthe link event is also supported at the opposite end, the opposite equipment can also inform thelocal equipment of the link event that is detected at the opposite end. Then, the correspondingalarm is reported at the local end.

Procedure


Step 2 Click the OAM Error Frame Monitor tab.

Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.


----End

Related ReferencesB.10.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring

A.18.4 Performing Remote LoopbackAfter the Ethernet port on the local equipment sends data to the port on the interconnectedequipment, the local end can request the opposite end to return the data.


l The OAM auto-discovery operation must be successful at both ends of the link.



A-109

l On the equipment that initiates the loopback, OAM Working Mode must be set toActive.

l The equipment that responds to the loopback must support the remote loopback.


Background Informationl If a port is capable of responding to loopbacks, it enters the loopback responding state and

reports the loopback responding alarm after receiving the command of enabling the remoteloopback function sent from the opposite OAM port. In this case, the equipment thatinitiates the loopback enters the loopback initiating state and reports the loopback initiatingalarm.

l Generally, after the remote loopback function is enabled, service packets, except theOAMPDU, are looped back at the remote end.

l After using the remote loopback function to complete the fault locating and the linkperformance detection, you need to disable the remote loopback function at the end wherethe loopback is initiated and then restore the services. At this time, the alarm is automaticallycleared.

Procedure



Step 3 Select the port and choose Enable Remote Loopback from the drop-down menu of OAM.

Step 4 Set Remote Side Loopback Response to Enabled.


----End

A.18.5 Enabling Self-Loop DetectionAfter enabling the self-loop detection on an Ethernet port, you can check the loopback of theport and the loopback between the port and other Ethernet ports on the board.


l All the external physical ports on the Ethernet service processing board must be enabled.


Configuration Guide


Issue 02 (2009-10-30)


Background InformationWhen the self-loop detection is enabled for an external physical port, if the self-loop situationoccurs at the port, the ETHOAM_SELF_LOOP alarm is reported

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > InterfaceManagement > Ethernet Interface from the Function Tree.


Step 3 Set Loopback Check to Enabled.


----End

A.19 Using the RMONThe remote monitoring (RMON) is mainly used to monitor the data traffic on a network segmentor on the entire network. Currently, it is one of the widely used network management standards.

A.19.1 Browsing the Performance Data in the Statistics Group of an Ethernet PortAfter you configure an RMON statistics group for an Ethernet port, you can browse the real-time statistical performance data of the port.

A.19.2 Configuring an Alarm Group for an Ethernet PortAfter you configure an RMON alarm group for an Ethernet port, you can monitor whether theperformance value of the port crosses the configured thresholds in the long term.

A.19.3 Configuring a History Control GroupWhen configuring a history control group for an Ethernet port, you configure how the historyperformance data of the port is monitored. The Ethernet board monitors the history performancedata of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50history performance data items.

A.19.4 Browsing the Performance Data in the History Group of an Ethernet PortAfter you configure an RMON history group for an Ethernet port, you can browse the statisticalhistory performance data of the port.

A.19.1 Browsing the Performance Data in the Statistics Group of anEthernet Port

After you configure an RMON statistics group for an Ethernet port, you can browse the real-time statistical performance data of the port.




A-111

l The corresponding board must be added in the NE Panel.


U2000

Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChoosePerformance > RMON Performance from the Function Tree.

Step 2 Click the Statistics Group tab.

Step 3 Set the required parameters for the statistics group.

Step 4 Click Resetting begins.

NOTE

If you click Start, the register of the statistics group is not reset to clear the existing data.

----End

Related ReferencesB.12.1 Parameter Description: RMON Performance_Statistics Group

A.19.2 Configuring an Alarm Group for an Ethernet PortAfter you configure an RMON alarm group for an Ethernet port, you can monitor whether theperformance value of the port crosses the configured thresholds in the long term.


l The corresponding boards must be added in the NE Panel.


U2000

Procedure


Step 2 Click the RMON Setting tab.

Step 3 Click the Object tab and set the corresponding parameters.

Step 4 Click the Event tab and set the corresponding parameters.


----End


Configuration Guide


Issue 02 (2009-10-30)

Related ReferencesB.12.4 Parameter Description: RMON Performance_RMON Setting

A.19.3 Configuring a History Control GroupWhen configuring a history control group for an Ethernet port, you configure how the historyperformance data of the port is monitored. The Ethernet board monitors the history performancedata of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50history performance data items.




U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON HistoryControl.

Step 2 Set the parameters of the history control group.


----End

Related ReferencesB.12.3 Parameter Description: RMON Performance_History Control Group

A.19.4 Browsing the Performance Data in the History Group of anEthernet Port

After you configure an RMON history group for an Ethernet port, you can browse the statisticalhistory performance data of the port.



l The objects and performance events to be monitored must be set.


U2000



A-113

Procedure


Step 2 Click the History Group tab.

Step 3 Set the parameters of the history group.

Step 4 Click Apply.

----End

Related ReferencesB.12.4 Parameter Description: RMON Performance_RMON Setting

A.20 Setting the Parameters of Ethernet InterfacesThis topic describes how to configure the parameters of Ethernet interfaces, including generalattributes, traffic control, layer 2 (L2) attributes, and advanced attributes.

A.20.1 Setting the General Attributes of Ethernet InterfacesThe general attributes of Ethernet interfaces define the physical-layer information, such as theinterface mode, encapsulation type, and maximum frame length.

A.20.2 Configuring the Traffic Control of Ethernet InterfacesAfter the traffic control is enabled, the Ethernet interface sends the pause frame to notify thepeer end of stop sending Ethernet packets for a period if the link is congested, thus eliminatinglink congestion.

A.20.3 Setting the Layer 2 Attributes of Ethernet InterfacesThe L2 attributes of Ethernet interfaces define the link-layer information.

A.20.4 Setting the Advanced Attributes of Ethernet InterfacesThe advanced attributes of Ethernet interfaces are used to configure the MAC/PHY loopbackand query the traffic rate on the interface.

A.20.1 Setting the General Attributes of Ethernet InterfacesThe general attributes of Ethernet interfaces define the physical-layer information, such as theinterface mode, encapsulation type, and maximum frame length.




U2000


Configuration Guide


Issue 02 (2009-10-30)

Procedure


Step 2 Click the General Attributes tab.

Step 3 Configure the general attributes of Ethernet interfaces.


----End

Related ReferencesB.14.13 Parameter Description: Ethernet Interface_Basic Attributes

A.20.2 Configuring the Traffic Control of Ethernet InterfacesAfter the traffic control is enabled, the Ethernet interface sends the pause frame to notify thepeer end of stop sending Ethernet packets for a period if the link is congested, thus eliminatinglink congestion.




Procedure


Step 2 Click the Flow Control tab.

Step 3 Configure the traffic control of Ethernet interfaces.



A-115


----End

Related ReferencesB.14.14 Parameter Description: Ethernet Interface_Flow Control

A.20.3 Setting the Layer 2 Attributes of Ethernet InterfacesThe L2 attributes of Ethernet interfaces define the link-layer information.




ProcedureStep 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface

Management > Ethernet Interface from the Function Tree.

Step 2 Click the Layer 2 Attributes tab.

Step 3 Configure the L2 attributes of Ethernet interfaces.


----End

Related ReferencesB.14.15 Parameter Description: Ethernet Interface_Layer 2 Attributes


Configuration Guide


Issue 02 (2009-10-30)

A.20.4 Setting the Advanced Attributes of Ethernet InterfacesThe advanced attributes of Ethernet interfaces are used to configure the MAC/PHY loopbackand query the traffic rate on the interface.




U2000

Procedure



Step 3 Configure the advanced attributes of Ethernet interfaces.


----End

Related ReferencesB.14.16 Parameter Description: Ethernet Interface_Advanced Attributes

A.21 Setting the General Attributes of the IF_ETH PortThe IF_ETH port is the internal Ethernet port in a Hybrid IF board, which is used to accessEthernet services over Hybrid microwave.

A.21.1 Setting the General Attributes of the IF_ETH PortThe general attributes of the IF_ETH port specify the basic information, including the port modeand encapsulation mode.

A.21.2 Setting the Layer 2 Attributes of the IF_ETH PortThe Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer,including the tag attribute and QinQ type domain.

A.21.3 Setting the Advanced Attributes of the IF_ETH PortThe advanced attributes of the IF_ETH port are used to specify whether to discard the errorframes, specify whether to perform loopback at the MAC layer, and to check the port rate.



A-117

A.21.1 Setting the General Attributes of the IF_ETH PortThe general attributes of the IF_ETH port specify the basic information, including the port modeand encapsulation mode.


l The corresponding IF board must be added to NE Panel.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > InterfaceManagement > Microwave Interface from the Function Tree.

Step 2 Click the Basic Attributes tab.

Step 3 Set the general attributes of the IF_ETH port.


----End

Related ReferencesB.14.17 Parameter Description: Microwave Interface_Basic Attributes

A.21.2 Setting the Layer 2 Attributes of the IF_ETH PortThe Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer,including the tag attribute and QinQ type domain.




Procedure


Step 2 Click the Layer 2 Attributes tab.


Configuration Guide


Issue 02 (2009-10-30)

Step 3 Setting the Layer 2 attributes of the IF_ETH port.


----End

Related ReferencesB.14.18 Parameter Description: Microwave Interface_Layer 2 Attributes

A.21.3 Setting the Advanced Attributes of the IF_ETH PortThe advanced attributes of the IF_ETH port are used to specify whether to discard the errorframes, specify whether to perform loopback at the MAC layer, and to check the port rate.




Procedure



Step 3 Setting the advanced attributes of the IF_ETH port.


----End

Related ReferencesB.14.19 Parameter Description: Microwave Interface_Advanced Attributes

A.22 Setting the Parameters of ODU InterfacesThis topic describes how to configure the parameters of ODU interfaces, including the transmitfrequency attribute, power attribute, ODU attribute, and advanced attributes.

A.22.1 Setting the Transmit Frequency Attribute of the ODUThe transmit frequency attribute of the ODU is used to configure the transmit frequency of theODU and T/R spacing.



A-119

A.22.2 Querying the ODU AttributeThe ODU attribute is used to query the information about the ODU.

A.22.3 Setting the Power Attributes of the ODUThe power attribute of the ODU is used to configure the transmit power and receive power ofthe ODU.

A.22.4 Setting the Advanced Attributes of the ODUThe advanced attributes of the ODU are used to configure the transmit status of the ODU.

A.22.1 Setting the Transmit Frequency Attribute of the ODUThe transmit frequency attribute of the ODU is used to configure the transmit frequency of theODU and T/R spacing.




U2000

Procedure


Step 2 Click the Radio Frequency Attributes tab.

Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.

Step 4 Click Apply.

----End

Related ReferencesB.14.6 Parameter Description: ODU Interface_Radio Frequency Attribute

A.22.2 Querying the ODU AttributeThe ODU attribute is used to query the information about the ODU.




Configuration Guide


Issue 02 (2009-10-30)


Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > ODU Interface from the Function Tree.

Step 2 Click the Equipment Information tab.

Step 3 Click Query to obtain the information about the ODU.

----End

Related ReferencesB.14.8 Parameter Description: ODU Interface_Equipment Information

A.22.3 Setting the Power Attributes of the ODUThe power attribute of the ODU is used to configure the transmit power and receive power ofthe ODU.


l The related IF board must be added.



Procedure


Step 2 Click the Power Attributes tab.

Step 3 Configure the power attribute parameters of the ODU.

Step 4 Click Apply.

----End

Related ReferencesB.14.7 Parameter Description: ODU Interface_Power Attributes



A-121

A.22.4 Setting the Advanced Attributes of the ODUThe advanced attributes of the ODU are used to configure the transmit status of the ODU.




Procedure



Step 3 Configure the parameters of the ODU, such as Configure Transmission Status.

Step 4 Click Apply.

----End

Related ReferencesB.14.9 Parameter Description: ODU Interface_Advanced Attributes

A.23 Setting the Parameters of SDH InterfacesThe parameters of SDH interfaces are used to configure the loopback on the SDH interface boardand the laser status.




Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > SDH Interface from the Function Tree.


Configuration Guide


Issue 02 (2009-10-30)

Step 2 Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.

Step 3 Configure the parameters of SDH interfaces.1. Choose Port from the drop-down list, and then configure the parameters of SDH interfaces.

Click Apply.A dialog box is displayed for confirmation.

2. Click OK.The dialog box is displayed again for confirmation.

3. Click Close.

Step 4 Configure the parameters of VC-4 paths.1. Choose VC4 Channel from the drop-down list, and then configure the parameters of VC-4

paths. Click Apply.A dialog box is displayed for confirmation.

2. Click OK.A dialog box is displayed again for confirmation.

3. Click Close.

----End

Related ReferencesB.14.10 Parameter Description: SDH Interfaces

A.24 Setting the Parameters of PDH InterfacesThe parameters of PDH interfaces are used to configure the tributary loopback, service loadindication, and tributary retiming.




Procedure

Step 1 Select the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > PDH Interface from the Function Tree.

Step 2 Select By Board/Port(Channel).

Step 3 Select Port from the list box.

Step 4 Configure the parameters of PDH interfaces.

Step 5 Click Apply, and then close the dialog box that is displayed indicating the operation result.

----End



A-123

Related ReferencesB.14.12 Parameter Description: PDH Interfaces

A.25 Configuring Overhead BytesGenerally, the default overload bytes can meet the requirements of the device. In certain specialapplication scenarios, however, such as device interconnection, you need to change the overloadbytes according to the requirements of the interconnected device.

A.25.1 Configuring RSOHsWhen the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte inregenerator section overheads (RSOHs).

A.25.2 Configuring VC-4 POHsWhen the HP_TIM or HP_SLM alarm is reported by the line board of the local or peer NE, youneed to configure the J1 or C2 byte in VC-4 path overheads (POHs).

A.25.3 Configuring VC-12 POHsWhen the E1 interface board of the local or remote NE reports the LP_TIM or LP_SLM alarmor the Ethernet board of the local or remote NE reports the LP_TIM_VC12 or LP_SLM_VC12alarm, you need to configure the signal flag in the J2 or V5 byte in VC-12 path overheads (POHs).

A.25.1 Configuring RSOHsWhen the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte inregenerator section overheads (RSOHs).



Procedure

Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > OverheadManagement > Regenerator Section Overhead from the Function Tree.

Step 2 Configure the J0 byte.1. Double-click the parameter whose value needs to be changed.

The Please input the overhead byte dialog box is displayed.2. Configure overhead bytes.


Configuration Guide


Issue 02 (2009-10-30)

3. Click OK.

Step 3 Click Apply.A dialog box is displayed for confirmation.

Step 4 Click OK. Close the dialog box that is displayed indicating the operation result.

----End

Related ReferencesB.15.1 Parameter Description: Regenerator Section Overhead

A.25.2 Configuring VC-4 POHsWhen the HP_TIM or HP_SLM alarm is reported by the line board of the local or peer NE, youneed to configure the J1 or C2 byte in VC-4 path overheads (POHs).



Procedure

Step 1 In the NE Explorer, select the SDH interface board, and then choose Configuration > OverheadManagement > VC4 Overhead from the Function Tree.

Step 2 Optional: Configure the J1 byte.1. Click the Trace Byte J1 tab.2. Double-click the parameter whose value needs to be changed.

The Please Input Overhead Byte dialog box is displayed.3. Configure overhead bytes.4. Click OK.



A-125

5. Click Apply.A dialog box is displayed for confirmation.

6. Click OK. Close the dialog box that is displayed indicating the operation result.

Step 3 Optional: Configure the C2 byte.

1. Click the Signal Flag C2 tab.

2. Configure the required parameters.



Step 4 Configure the termination mode of the VC-4 overhead.

1. Click the Overhead Termination tab.

2. Configure VC4 Overhead Termination.



----End

Related ReferencesB.15.2 Parameter Description: VC-4 POHs

A.25.3 Configuring VC-12 POHsWhen the E1 interface board of the local or remote NE reports the LP_TIM or LP_SLM alarmor the Ethernet board of the local or remote NE reports the LP_TIM_VC12 or LP_SLM_VC12alarm, you need to configure the signal flag in the J2 or V5 byte in VC-12 path overheads (POHs).



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > OverheadManagement > VC12 Path Overhead from the Function Tree.

Step 2 Configure the J2 byte.

1. Click the Trace Byte J2 tab.

2. Double-click the parameter whose value needs to be changed.The Please input the overhead byte dialog box is displayed.

3. Configure overhead bytes.


Configuration Guide


Issue 02 (2009-10-30)

4. Click OK.5. Click Apply.

A dialog box is displayed for confirmation.6. Click OK, and then close the dialog box that is displayed.

Step 3 Configure the signal flag.1. Click the Signal Flag tab.2. Configure the signal flag in the V5 byte.3. Click Apply.

A dialog box is displayed for confirmation.4. Click OK, and then close the dialog box that is displayed.

----End

Related ReferencesB.15.3 Parameter Description: VC-12 POHs

A.26 Configure the Ethernet ServiceThe Ethernet service is classified into two types, namely, E-Line service and E-LAN service.

A.26.1 Configuring the QinQ LinkConfiguring the QinQ link is the prerequisite for configuring QinQ private line services and802.1ad bridge services.

A.26.2 Configuring the E-Line ServiceThe E-Line service refers to the static transmission of the Ethernet service in the point-to-pointmode.

A.26.3 Creating a VLAN Forwarding Table ItemAfter the corresponding VLAN forwarding table item is created, the VLAN IDs of the servicepackets can be switched at the source or sink end of the E-Line service.



A-127

A.26.4 Configuring the E-LAN ServiceThe E-LAN service refers to the dynamic transmission of the Ethernet service in the multipoint-to-multipoint mode through MAC address.

A.26.5 Testing the Ethernet ServiceBy testing the Ethernet service, you can check whether the Ethernet service is available overradio links. The Ethernet service can be tested through the ETH OAM function. Thus, no testeris required.

A.26.1 Configuring the QinQ LinkConfiguring the QinQ link is the prerequisite for configuring QinQ private line services and802.1ad bridge services.




U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > QinQ Link from the Function Tree.

Step 2 Click New. The New QinQ Link dialog box is displayed.

Step 3 Configure the basic attributes of the QinQ link.

Step 4 Click OK.

----End

Related ReferencesB.8.6 Parameter Description: QinQ Link_Creation

A.26.2 Configuring the E-Line ServiceThe E-Line service refers to the static transmission of the Ethernet service in the point-to-pointmode.


Configuration Guide


Issue 02 (2009-10-30)




U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > E-Line Service from the Function Tree.

Step 2 Click New. The New E-Line Service dialog box is displayed.

Step 3 Configure Direction of the E-Line service.

Step 4 Configure the attributes of the E-Line service.

NOTE

The interface parameter varies according to Direction.



A-129

Step 5 Click OK.

----End

Related ReferencesB.8.1 Parameter Description: E-Line Service_Creation

A.26.3 Creating a VLAN Forwarding Table ItemAfter the corresponding VLAN forwarding table item is created, the VLAN IDs of the servicepackets can be switched at the source or sink end of the E-Line service.


l The corresponding Ethernet board must be added to NE Panel.

l The UNI-UNI E-Line service must be created.


U2000

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > E-Line Service from the Function Tree.

Step 2 Click the VLAN Forwarding Table Item tab.

Step 3 Click New.

Step 4 Set the attributes of the new VLAN forwarding table item.

Step 5 Click OK. Then, close the dialog box that is displayed.

----End


Configuration Guide


Issue 02 (2009-10-30)

Related ReferencesB.8.3 Parameter Description: VLAN Forwarding Table Item_Creation

A.26.4 Configuring the E-LAN ServiceThe E-LAN service refers to the dynamic transmission of the Ethernet service in the multipoint-to-multipoint mode through MAC address.




Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > E-LAN Service from the Function Tree.

Step 2 Click New. The New E-LAN Service dialog box is displayed.

Step 3 Configure the attributes of the bridge.

NOTE

l The interface parameter varies according to Tag Type.



A-131


Configuration Guide


Issue 02 (2009-10-30)



A-133

Step 4 Configure the port that is mounted to the bridge on the UNI side of the E-LAN service.1. Click the UNI tab.2. Click Configuration, and then select the port that needs to be mounted to the bridge in the

Configure Port dialog box that is displayed.TIP


3. Click .4. Optional: Configure the attributes of the port that needs to be mounted to the bridge in the

Selected Ports dialog box.

NOTE

The parameter that can be configured varies according to Tag Type.

5. Click OK.

Step 5 Optional: Configure the logical interface on the NNI side.

NOTE

This step takes effect only when Tag Type is set to S-Awared.

Step 6 Configure the split horizon group.1. Click the Split Horizon Group tab.


Configuration Guide


Issue 02 (2009-10-30)

2. Click New, then the New Split Horizon Group dialog box is displayed.

3. Select a port from Available Interfaces, and then click .TIP


4. Click OK.

Step 7 Click OK.

----End

Related ReferencesB.8.4 Parameter Description: E-LAN Service_Creation

A.26.5 Testing the Ethernet ServiceBy testing the Ethernet service, you can check whether the Ethernet service is available overradio links. The Ethernet service can be tested through the ETH OAM function. Thus, no testeris required.

Prerequisite

Ethernet services must be configured. Creating the Maintenance Domain (MD), Creating theMaintenance Association (MA), Creating the Maintenance Association End Point (MEP)and Creating the Maintenance Association End Point (MEP) must be complete.


U2000

Test Connection Diagram

The following test procedure considers the Ethernet service between NE 1 and NE 2 as anexample, as shown in Figure A-1.

Figure A-1 Networking diagram for testing the Ethernet service

NE 1 NE 2

PORT 1 PORT 2

Microwave networking



A-135

An Ethernet link is available from Port1 on NE1 to Port2 on NE2. In addition, the relevant MD,MA, and MEP are configured.

Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer of the NE1, and then chooseConfiguration > Ethernet OAM Management > Ethernet Service OAM Management.

Step 2 Select the MD, MA, and MEP that correspond to Port 1, click OAM.

Step 3 Select Start LB.The LB Test window is displayed.

Step 4 Select MP ID, and set the parameters in Test Node.l Source Maintenance Point ID: MD ID of Port1

l Destination Maintenance Point ID: MD ID of Port2

l Transmitted Packet Count: 20 (recommended)

l Transmitted Packet Length: 64 (64 is a recommended value, and the parameter can alsobe set to 128, 256, 512, 1024, and 1280 for testing the Ethernet services of different packetlengths.)

NOTE

The maximum Packet Length is 1400.

l Transmitted Packet Priority: 7 (recommended)

Step 5 Click Start Test.

Step 6 Check Detection Result.The LossRate in the Detection Result should be 0.

----End


Configuration Guide


Issue 02 (2009-10-30)

A.27 Managing the MAC Address TableThe MAC address table is the core of the E-LAN service. The OptiX RTN 910 provides variousfunctions for managing the MAC address table.

A.27.1 Creating a Static MAC Address EntryThrough the creation of a static MAC address entry, the host with a specified MAC address canbe prohibited from using the E-LAN service.

A.27.2 Creating a Blacklist Entry of MAC AddressesThrough the creation of a blacklist entry of MAC addresses, the host with a specified MACaddress is not affected by MAC address aging. In addition, the E-LAN service can be supportedby the host that receives packets only.

A.27.3 Configuring the Aging Parameters of a MAC Address TableBy default, the aging function of a MAC address table is enabled and the aging time is fiveminutes. By configuring the aging parameters of a MAC address table, you can modify suchparameters.

A.27.4 Querying or Deleting a Dynamic MAC AddressBy querying or deleting a dynamic MAC address, you can query or delete all the MAC addressentries that are learned by the E-LAN service.

A.27.1 Creating a Static MAC Address EntryThrough the creation of a static MAC address entry, the host with a specified MAC address canbe prohibited from using the E-LAN service.

Prerequisitel The E-LAN service must be created.



U2000

Procedure


Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to becreated.

Step 3 Click the Static MAC Address tab.

Step 4 Click New.The New Static MAC Address dialog box is displayed.

Step 5 Configure the parameters of the static MAC address entry.



A-137


----End

Related ReferencesB.8.5 Parameter Description: E-LAN Service

A.27.2 Creating a Blacklist Entry of MAC AddressesThrough the creation of a blacklist entry of MAC addresses, the host with a specified MACaddress is not affected by MAC address aging. In addition, the E-LAN service can be supportedby the host that receives packets only.




U2000

Procedure


Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needsto be created.

Step 3 Click the Disabled MAC Address tab.

Step 4 Configure the blacklist entry of MAC addresses.


----End



Configuration Guide


Issue 02 (2009-10-30)

A.27.3 Configuring the Aging Parameters of a MAC Address TableBy default, the aging function of a MAC address table is enabled and the aging time is fiveminutes. By configuring the aging parameters of a MAC address table, you can modify suchparameters.




U2000

Procedure


Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC addresstable need to be configured.

Step 3 Click the MAC Address Learning Parameters tab.

Step 4 Configure the status of the aging function and set the aging time.


----End


A.27.4 Querying or Deleting a Dynamic MAC AddressBy querying or deleting a dynamic MAC address, you can query or delete all the MAC addressentries that are learned by the E-LAN service.




U2000



A-139

Procedure


Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to bequeried or cleared.

Step 3 Click the Self-Learning MAC Address tab.

Step 4 Select the board whose dynamic MAC address needs to be queried or cleared.

Step 5 Optional: Click Clear MAC Address, and then click OK in the dialog box that is displayedfor confirmation.

----End


A.28 Setting the Mode for Processing an Unknown Frameof the E-LAN Service

An unknown frame is a unicast frame whose destination MAC address is not listed in the MACaddress table or a broadcast frame whose destination MAC address is not listed in the multicastgroup. By default, the NE broadcasts the unknown frame. By setting the mode for processingan unknown frame of the E-LAN service, you can change the processing mode so that unknownframe can be discarded.




U2000

Procedure


Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frameneeds to be set.

Step 3 Click the Unknown Frame Processing tab.

Step 4 Set the mode for processing an unknown frame of the E-LAN service.


Configuration Guide


Issue 02 (2009-10-30)


----End


A.29 Configuring Auxiliary Interfaces and FunctionsThe auxiliary interfaces and functions supported by the OptiX RTN 910 include the orderwire,synchronous data service, asynchronous data service, wayside E1 service, and external alarm.

A.29.1 Configuring the OrderwireThe orderwire for an NE provides a dedicated communication channel that the networkmaintenance personnel can use.

A.29.2 Configuring the Synchronous Data ServiceThe OptiX RTN 910 supports the transmission of a channel of 64-kbit/s synchronous data servicethrough a user-defined byte in the microwave frame or the F1 overhead byte in the STM-Nframe. Such a service is also called F1 data port service.

A.29.3 Configuring the Asynchronous Data ServiceThe OptiX RTN 910 supports the transmission of a channel of asynchronous data service witha maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any bytewithin the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also calledbroadcast data port service.

A.29.4 Configuring the Wayside E1 ServiceThe OptiX RTN 910 supports the transmission of a channel of 2.048-Mbit/s wayside E1 servicethrough 32 user-defined bytes in the SDH microwave frame.

A.29.5 Configure External AlarmsAfter the outputting of external alarms is configured, the alarm information of the OptiX RTN910 can be output to other equipment. After the inputting of external alarms is configured, thealarm information of other equipment can be input to the OptiX RTN 910.

A.29.1 Configuring the OrderwireThe orderwire for an NE provides a dedicated communication channel that the networkmaintenance personnel can use.





A-141

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwirefrom the Function Tree.

Step 2 Click the General tab.

Step 3 Configure the orderwire information.

Step 4 Click Apply.

Step 5 Optional: Change the overhead bytes occupied by the orderwire.1. Click the Advanced tab.2. Configure Orderwire Occupied Bytes.

3. Click Apply.

----End

Related ReferencesB.13.1 Parameter Description: Orderwire_GeneralB.13.2 Parameter Description: Orderwire_Advanced

A.29.2 Configuring the Synchronous Data ServiceThe OptiX RTN 910 supports the transmission of a channel of 64-kbit/s synchronous data servicethrough a user-defined byte in the microwave frame or the F1 overhead byte in the STM-Nframe. Such a service is also called F1 data port service.


l The board involved in the synchronous data service must be configured.


Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Configuration >Orderwire from the Function Tree.

Step 2 Click the F1 Data Port tab.

Step 3 Hold on the Ctrl key, select two data channels from Available Date Channel, and then click

.


Configuration Guide


Issue 02 (2009-10-30)

Step 4 Click Apply.

----End

Related ReferencesB.13.3 Parameter Description: Orderwire_F1 Data Port

A.29.3 Configuring the Asynchronous Data ServiceThe OptiX RTN 910 supports the transmission of a channel of asynchronous data service witha maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any bytewithin the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also calledbroadcast data port service.


l The board involved in the asynchronous data service must be configured.


Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Configuration >Orderwire from the Function Tree.

Step 2 Click the Broadcast Data Port tab.

Step 3 Configure the parameters of the broadcast data port.

Step 4 Click Apply.

----End

Related ReferencesB.13.4 Parameter Description: Orderwire_Broadcast Data Port

A.29.4 Configuring the Wayside E1 ServiceThe OptiX RTN 910 supports the transmission of a channel of 2.048-Mbit/s wayside E1 servicethrough 32 user-defined bytes in the SDH microwave frame.


l The IF1 board must be added on the NE Panel.




A-143


The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM,8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM mode.

Procedure

Step 1 In the NE Explorer, select the IF1 board from the Object Tree, and then chooseConfiguration > IF Interface from the Function Tree.

Step 2 Click the IF Attributes tab.

Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.

Step 4 Click Apply.

----End

Related ReferencesB.14.1 Parameter Description: IF Interface_IF Attribute

A.29.5 Configure External AlarmsAfter the outputting of external alarms is configured, the alarm information of the OptiX RTN910 can be output to other equipment. After the inputting of external alarms is configured, thealarm information of other equipment can be input to the OptiX RTN 910.


l The AUX board must be added on the NE Panel.


U2000

Context

The external alarms of the OptiX RTN 910 are also considered as housekeeping alarms. Theexternal alarm port of the OptiX RTN 910 is a relay port. This port can be either in the "on" stateor in the "off" state.

The OptiX RTN 910 provides one alarm output port and three alarm input ports. The alarm inputports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of theinput alarm) after the external alarm is triggered. To ensure that the external alarm port worksnormally, the external alarm cables must be correctly connected.


Configuration Guide


Issue 02 (2009-10-30)

Procedure

Step 1 In the NE Explorer, select the AUX board from the Object Tree, and then chooseConfiguration > Environment Monitor Configuration > Environment Monitor Interfacefrom the Function Tree.

Step 2 Configure the input alarm.1. Select Input Relay from the drop-down list.2. Configure the parameters of the input alarm.


Step 3 Configure the output alarm.1. Select Output Relay from the drop-down list.2. Configure the parameters of the output alarm.


----End

Related ReferencesB.13.5 Parameter Description: Environment Monitoring Interface



A-145

B Parameters Description

This topic describes the parameters used in this document.

B.1 Parameters for NE ManagementThis topic describes the parameters that are used for managing network elements (NEs).

B.2 Parameters for Cable ManagementThis topic describes the parameters that are used for managing cables.

B.3 Parameters for Communications ManagementThis topic describes the parameters that are used for communications management.

B.4 Radio Link ParametersThis topic describes the parameters that are related to radio links.

B.5 Multiplex Section Protection ParametersThis topic describes the parameters that are related to multiplex section protection (MSP).

B.6 SDH/PDH Service ParametersThis topic describes the parameters that are related to SDH/PDH services.

B.7 Clock ParametersThis topic describes the parameters that are related to clocks.

B.8 Parameters for Ethernet ServicesThis topic describes the parameters that are related to Ethernet services.

B.9 Ethernet Protocol ParametersThis topic describes the parameters that are related to the Ethernet protocol.

B.10 Parameters for the Ethernet OAMThis topic describes the parameters that are related to the Ethernet operation, administration andmaintenance (OAM).

B.11 QoS ParametersThis topic describes the parameters that are related to QoS.

B.12 RMON ParametersThis topic describes the parameters that are related to RMON performances.

B.13 Parameters for the Orderwire and Auxiliary InterfacesThis topic describes the parameters that are related to the orderwire and auxiliary interfaces.

B.14 Parameters for Board Interfaces

OptiX RTN 910Configuration Guide B Parameters Description


B-1

This topic describes the parameters that are related to board interfaces.

B.15 Parameters for OverheadThis topic describes the parameters that are related to overhead.

B Parameters DescriptionOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

B.1 Parameters for NE ManagementThis topic describes the parameters that are used for managing network elements (NEs).

B.1.1 Parameter Description: NE SearchingThis topic describes the parameters that are used for searching for NEs.

B.1.2 Parameter Description: NE CreationThis topic describes the parameters that are related to NE creation.

B.1.3 Parameter Description: NE Attribute_NE ID ChangeThis topic describes the parameters that are used for changing NE IDs.

B.1.4 Parameter Description: NE Time SynchronizationThis topic describes the parameters that are used for synchronizing the time of NEs.

B.1.5 Parameter Description: Localization Management of the NE TimeThis parameter describes the parameters that are used for localization management of the NEtime.

B.1.6 Parameter Description: Automatic Disabling of the Functions of NEsThis parameter describes the parameters that are used for automatically disabling the functionsof an NE.

B.1.1 Parameter Description: NE SearchingThis topic describes the parameters that are used for searching for NEs.

Navigation PathOn the Main Topology, choose File > Discovery > NE.



B-3

Parameters for the Search FieldParameter Value Range Default Value Description

Address Type IP Address of GNENSAP AddressIP Address Range of GNE

IP Address Range of GNE l If the OSI protocol isused on the DCN, youcan search for an NEbased on NSAPAddress only.

l If the IP protocol isused on the DCN, youcan search for an NEbased on IP Address ofGNE or IP AddressRange of GNE.

l To search for all theNEs that communicatewith the gateway NE,select IP AddressRange of GNE.

l To select the gatewayNE only, select IPAddress of GNE.

NOTEIf Address Type is set to IPAddress of GNE or IPAddress Range of GNE,and if the U2000 (server)and the gateway NE arelocated in different networksegments, ensure that theU2000 and relevant routersare configured with the IProutes for the networksegment in which theU2000 and gateway NE arelocated.

If Address Type is set toNSAP Address, ensure thatthe OSI protocol stack isinstalled.


Configuration Guide


Issue 02 (2009-10-30)

Parameter Value Range Default Value Description

Search Address - - l If Address Type is setto IP Address ofGNE, enter the IPaddress of the gatewayNE, such as 129.9.x.x.

l If Address Type is setto IP Address Rangeof GNE, enter thenumber of the IPnetwork segment inwhich the gateway NEis located, such as129.9.255.255.

l If Address Type is setto NSAP Address,enter the NSAP addressof the gateway NE.

User Name - - This parameter specifiesthe user name of thegateway NE.

Password - - This parameter specifiesthe password of thegateway NE.

Parameter for Searching for NEsParameter Value Range Default Value Description

Search for NE SelectedDeselected

Selected This parameter specifieswhether to search for allthe NEs in the specifieddomain.



B-5


Create NE after search SelectedDeselected

Deselected l To create NEs inbatches, it isrecommended that youselect Create NE aftersearch. The NEs areautomatically createdafter they are found.

l After Create NE aftersearch is selected,enter NE User andPassword that are usedfor creating an NE.

NOTEIf only Create NE aftersearch is selected, Searchfor NE is selectedautomatically.

NE User - - l This parameterspecifies the user nameto be entered when anNE is created.

l This parameter is validonly when Create NEafter search isselected.

Password - - l This parameterspecifies the passwordto be entered when anNE is created.


Upload after create SelectedDeselected

Deselected l This parameterspecifies whether toautomatically uploadthe NE data after theNE is found andcreated.

l If only Upload aftercreate is selected,Search for NE andCreate NE aftersearch are selectedautomatically.


Configuration Guide


Issue 02 (2009-10-30)

Parameter for the Found NEs


NE ID - - This parameter indicatesthe ID of the found NE,which consists ofextended ID and NE ID.For example, in the case ofNE9-25, the value 9indicates the extended ID,and the value 25 indicatesthe NE ID.

GNE Address - - This parameter indicatesthe address of the gatewayNE that is connected to thefound NE.

GNE ID - - This parameter indicatesthe ID of the gateway NEthat is connected to thefound NE.

Created As GNE YesNo

Yes l This parameterspecifies the passwordto be entered when anNE is created.


Connection Mode CommonSecurity SSL

Common The communicationbetween the client and theserver is encrypted if thisparameter is set toSecurity SSL.

Port - 1400 This parameter specifiesthe communication port.

NE Status CreatedUncreated

- This parameter indicateswhether the found NE iscreated.

Related TasksA.1.1 Creating NEs by Using the Search Method

B.1.2 Parameter Description: NE CreationThis topic describes the parameters that are related to NE creation.



B-7

Navigation Path1. In the Physical View, right-click New > NE.2. Choose RTN Series > OptiX RTN 910 from the Object Tree.

Parameters on the Main InterfaceParameter Value Range Default Value Description

Type - - This parameter indicatesthe type of the NE to becreated.

ID - - l The ID refers to thebasic ID. If theextended ID is notused, the basic ID of anNE must be unique onthe networks that aremanaged by the sameNMS.

l This parameter is setaccording to theplanning information.

NOTEThe NE ID consisting of thebasic ID and extended IDidentifies an NE on theNMS.

Extended ID 1 to 254 9 If the number of existingNEs does not exceed therange represented by thebasic ID, do not changethe extended ID.

Name - - l This parameterspecifies the name ofthe NE.

l After you specifies thename of the NE, thename is displayedunder the icon of theNE.

Remarks - - This parameter specifiesthe remarks of the NE.


Configuration Guide


Issue 02 (2009-10-30)


Gateway Type Non-GatewayGateway

Non-Gateway l This parameter is set toGateway if the new NEis a gateway NE.

l This parameter is set toNon-Gateway if thenew NE is a non-gateway NE.

l This parameter is setaccording to the DCNplanning if the new NEcan function as agateway NE or a non-gateway NE.

Affiliated Gateway - - This parameter indicatesthe gateway NE of the newNE when Gateway Typeis set to Non-Gateway.

Affiliated GatewayProtocol

IPOSI

IP l This parameter needs tobe set when GatewayType is set toGateway.

l When the OSI overDCC solution is used,this parameter is set toOSI.

l In other cases, thisparameter is set to IP.

IP Address - - This parameter indicatesthe IP address of the newNE. This parameter needsto be set when AffiliatedGateway Protocol is setto IP.

Connection Mode CommonSecurity SSL

Common The communicationbetween the client and theserver is encrypted if thisparameter is set toSecurity SSL.

Port - 1400 This parameter specifiesthe communication port.

NE User - - This parameter specifiesthe user name to beentered when an NE iscreated.



B-9


Password - - This parameter specifiesthe password to be enteredwhen an NE is created.

NSAP Address - - This parameter indicatesthe NSAP address of thenew NE. This parameterneeds to be set whenAffiliated GatewayProtocol is set to OSI.You need to set the area IDonly, and the other partsare automaticallygenerated by the NE.

Related TasksA.1.2 Creating NEs by Using the Manual Method

B.1.3 Parameter Description: NE Attribute_NE ID ChangeThis topic describes the parameters that are used for changing NE IDs.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > NE

Attribute from the Function Tree.2. Click Modify NE ID. The Modify NE ID dialog box is displayed.

Parameters for Changing NE IDs


New ID - - l The new ID refers tothe basic ID. If theextended ID is notused, the basic ID of anNE must be unique onthe networks that aremanaged by the sameNMS.


NOTEThe NE ID consisting of thebasic ID and extended IDidentifies an NE on theNMS.


Configuration Guide


Issue 02 (2009-10-30)


New Extended ID 1 to 254 9 If the number of existingNEs does not exceed therange represented by thebasic ID, do not changethe extended ID.

Related TasksA.1.4 Changing the NE ID

B.1.4 Parameter Description: NE Time SynchronizationThis topic describes the parameters that are used for synchronizing the time of NEs.

Navigation Path1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from

the Main Menu.

2. Click the NE Time Synchronization tab.

Parameters for NE Time Synchronization


NE Name - - This parameter indicatesthe name of the NE.

NE ID - - This parameter indicatesthe ID of the NE.

Synchronous Mode Standard NTPNMNull

Null l If this parameter is setto NM, the NEsynchronizes the timeof the NMS server.

l If this parameter is setto Standard NTP, theNE synchronizes theNetwork TimeProtocol (NTP) serverthrough the standardNTP.

Standard NTPAuthentication

EnabledDisabled

Disabled This parameter is validonly when SynchronousMode is set to StandardNTP.



B-11

Parameters for the Standard NTP ServerParameter Value Range Default Value Description

Standard NTP ServerIdentifier

NE IDIP

NE ID l If the NE functions asthe gateway NE, thisparameter is set to IP.

l If the NE functions as anon-gateway NE andcommunicates with thegateway NE throughthe HWECC protocol,this parameter is set toNE ID.

l If the NE functions as anon-gateway NE andcommunicates with thegateway NE throughthe IP protocol, thisparameter is set to IP.

Standard NTP Server - - l If the NE functions asthe gateway NE, thisparameter is set to theIP address of theexternal NTP server.

l If the NE functions as anon-gateway NE, thisparameter is set to theID or IP address of thegateway NE.

Standard NTP ServerKey

0 to 1024 0 l If the NTP server doesnot need toauthenticated, thisparameter is set to thevalue "0".

l If the NTP server needsto be authenticated, theauthentication isperformed according tothe allocated key of theNTP server. In thiscase, the NEauthenticates the NTPserver based on the keyand the correspondingpassword (specified inthe management of thestandard NTP key).


Configuration Guide


Issue 02 (2009-10-30)

Parameters for Setting Automatic Synchronization


SynchronizationStarting Time

- - l This parameterspecifies the start timeof the synchronizationperiod. After thisparameter is specified,the NMS and the NEsynchronize the timeonce at the intervals ofSynchronizationPeriod(days).

l It is recommended thatyou use the defaultvalue.

DST SelectedDeselected

Deselected l This parameterindicates whetherSynchronizationStarting Time is thedaylight saving time.

l This parameter is setaccording to the actualsituation.

Synchronization Period(days)

1 to 300 1 l This parameterindicates the period ofsynchronizing the timeof the NE with the timeof the NMS.


Related TasksA.1.6 Synchronizing the NE Time

B.1.5 Parameter Description: Localization Management of the NETime

This parameter describes the parameters that are used for localization management of the NEtime.

Navigation Path1. On the Main Topology, choose Configuration > NE Batch Configuration > NE Time

Localization Management.



B-13

2. Select the NE for time localization management from the Object Tree, and then click

.

Parameters for Localization Management of the NE TimeParameter Value Range Default Value Description

NE - - This parameter indicates the name of theNE.

TimeZone - - This parameter indicates the time zone.

DST - - This parameter indicates whether DST isenabled.

Parameters for Time ZoneParameter Value Range Default Value Description

Time Zone - - l After the time zone is changed, thecurrent time of the NE is changedaccordingly.

l This parameter is set according to theplace where the NE is located.

DST SelectedDeselected

Deselected l The parameters related to daylight savingtime can be valid only when thisparameter is selected.

l This parameter is set according to thesituation whether daylight saving time isused in the place where the NE is located.

Offset 1 to 120Unit: minute(s)

- This parameter specifies the offset value ofthe daylight saving time.

Start Rule DATEWEEKDATE-WEEK

WEEK This parameter specifies the method ofadjusting the daylight saving time.

Start Time - - This parameter specifies the start daylightsaving time.

End Rule DATEWEEKDATE-WEEK

WEEK This parameter specifies the method ofadjusting the daylight saving time.

End Time - - This parameter specifies the end daylightsaving time.


Configuration Guide


Issue 02 (2009-10-30)

Related TasksA.1.7 Localizing the NE Time

B.1.6 Parameter Description: Automatic Disabling of the Functionsof NEs

This parameter describes the parameters that are used for automatically disabling the functionsof an NE.

Navigation Path1. On the Main Topology, choose Configuration > NE Batch Configuration > Automatic

Disabling of NE Function.

2. Select the NE whose functions need to be automatically disabled from the Object Tree, and

then click .

Parameters for Automatically Disabling the Functions of NEs


NE Name - - This parameter indicates the name of theNE.

NE Type OptiX RTN 910 - This parameter indicates the type of the NE.

Operation Type - - This parameter indicates the type of theoperation, such as loopback, and shutdownof the laser.

Auto Disabling DisabledEnabled

Enabled This parameter specifies whether toautomatically disable the operations such asloopback, and shutdown of the laser.

Auto DisablingTime(min)

1 to 2880 5 This parameter specifies the time ofautomatically disabling the operations suchas loopback, and shutdown of the laser.

B.2 Parameters for Cable ManagementThis topic describes the parameters that are used for managing cables.

B.2.1 Parameter Description: Fiber SearchThis topic describes the parameters that are used for searching for fibers.

B.2.2 Parameter Description: Fiber CreationThis parameter describes the parameters that are used for creating fibers.

B.2.3 Parameter Description: Radio Link CreationThis topic describes the parameters that are used for creating radio links.



B-15

B.2.1 Parameter Description: Fiber SearchThis topic describes the parameters that are used for searching for fibers.

Navigation Path1. Choose File > Discovery > Fiber from the Main Menu.

2. Select the board of the NE on which the fiber needs to be searched for or the IF board ofthe NE on which radio links need to be searched for from the Subject Tree, and the click

.

3. Click Search.

Parameters for Searching For Fibers


Source NE - - This parameter indicatesthe name of the source NEon which fibers or radiolinks are found.

Source Board - - This parameter indicatesthe board and slot of thesource NE on which fibersor radio links are found.

Source Port - - This parameter indicatesthe number of the port onthe board of the source NEon which fibers or radiolinks are found.

Sink NE - - This parameter indicatesthe name of the sink NE onwhich fibers or radio linksare found.

Sink Board - - This parameter indicatesthe board and slot of thesink NE on which fibers orradio links are found.

Sink Port - - This parameter indicatesthe number of the port onthe board of the sink NEon which fibers or radiolinks are found.

Level - - This parameter indicatesthe level of the found fiberor the working mode ofthe found radio link.


Configuration Guide


Issue 02 (2009-10-30)


Name - - This parameter indicatesthe name of the foundfiber or radio link.

Direction Two-Fiber BidirectionalSingle-FiberUnidirectional

- This parameter indicatesthe direction of the foundfiber.

Conflict with logical link(Y/N)

YesNo

- This parameter indicateswhether the found fiber orradio link conflicts withthe fiber or radio linkdisplayed on the NMS.

Operation Result SucceededFailed

- This parameter indicateswhether the cable iscreated successfully.

Fiber/Cable Type - - This parameter indicatesthe type of the found fiberor cable.

Related TasksA.4.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method

B.2.2 Parameter Description: Fiber CreationThis parameter describes the parameters that are used for creating fibers.

Navigation Path1. Choose File > Create > Link from the Main Menu. The Add Object dialog box is

displayed.2. Choose Link > Fiber from the Object Tree.

Parameters for FibersParameter Value Range Default Value Description

Create Ways Common WaysBatch Ways

Common Ways l If Common Ways isselected, fibers need tocreated one by one.

l If Batch Ways isselected, fibers can becreated in batches.

Fiber/Cable Type Fiber Fiber This parameter indicatesthat Fiber/Cable Type tobe created is a fiber.



B-17


Name - - This parameter specifiesthe name of the fiber to becreated. The nameconsists of up to 255characters, excludingcertain special marks suchas | * ? " < >.

Remarks - - This parameter specifiesthe remark informationcustomized by the user.

Source NE - - This parameter specifiesthe source NE on whichthe fiber needs to becreated.

Source NE Slot-BoardType-Port

- - This parameter specifiesthe board, slot, and port ofthe source NE on whichthe fiber needs to becreated.

Rate Level - - This parameter indicatesthe level that correspondsto the port on the board.

Medium Type G.652G.653G.654G.655

G.652 This parameter specifiesthe medium type of thefiber.

Sink NE - - This parameter specifiesthe sink NE on which thefiber needs to be created.

Sink NE Slot-BoardType-Port

- - This parameter specifiesthe board, slot, and port ofthe sink NE on which thefiber needs to be created.

Direction Two-Fiber BidirectionalSingle-FiberUnidirectional

- This parameter specifiesthe direction of the fiber tobe created.

Length(km) - - This parameter specifiesthe length of the fiber to becreated.

Attenuation(dB) - - This parameter specifiesthe attenuation of the fiberto be created.


Configuration Guide


Issue 02 (2009-10-30)


Created On - - This parameter specifiesthe time when the fiber iscreated.

Creator - - This parameter specifiesthe name of the personwho creates the fiber.

Maintainer - - This parameter specifiesthe name of the personwho maintains the fiber.

Related TasksA.4.3 Creating an SDH Optical Transmission Link by Using the Manual Method

B.2.3 Parameter Description: Radio Link CreationThis topic describes the parameters that are used for creating radio links.

Navigation Path1. Choose File > Create > Link from the Main Menu. The Add Object dialog box is

displayed.2. Choose Link > Microwave Link from the Object Tree.

Parameters for Microwave LinksParameter Value Range Default Value Description

Fiber/Cable Type Radio Link Radio Link This parameter indicatesthat a radio link needs tobe created is Fiber/CableType.

Name - - This parameter specifiesthe name of the radio linkto be created. The nameconsists of up to 255characters, excludingcertain special marks suchas | * ? " < >.

Remarks - - This parameter specifiesthe remark informationcustomized by the user.



B-19


Source NE - - The parameter specifiesthe source NE on whichthe radio link needs to becreated.

Source NE Slot-BoardType-Port

- - This parameter specifiesthe board, slot, and port ofthe source NE on whichthe radio link needs to becreated.

Rate Level - - This parameter indicatesthe level that correspondsto the port on the IF board.

Sink NE - - The parameter specifiesthe sink NE on which theradio link needs to becreated.

Sink NE Slot-BoardType-Port

- - This parameter specifiesthe board, slot, and port ofthe sink NE on which theradio link needs to becreated.

Length(km) - - This parameter specifiesthe length of the radio linkto be created.

Created On - - This parameter indicatesthe time when the radiolink is created.

Creator - - This parameter specifiesthe name of the personwho creates the radio link.

Maintainer - - This parameter specifiesthe name of the personwho maintains the radiolink.

Related TasksA.4.2 Creating a Radio Link by Using the Manual Method

B.3 Parameters for Communications ManagementThis topic describes the parameters that are used for communications management.


Configuration Guide


Issue 02 (2009-10-30)

B.3.1 Parameter Description: NE Communication Parameter SettingThis topic describes the parameters that are used for NE communication setting.

B.3.2 Parameter Description: DCC Management_DCC Rate ConfigurationThis topic describes the parameters that are used for configuring the DCC rate.

B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission ManagementThis topic describes the parameters that are used for DCC transparent transmission management.

B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECCThis topic describes the parameters that are related to the extended ECCs of Ethernet ports.

B.3.5 Parameter Description: NE ECC Link ManagementThis topic describes the parameters that are used for NE ECC link management.

B.3.6 Parameter Description: IP Protocol Stack Management_IP Route ManagementThis topic describes the parameters that are used for IP route management.

B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management CreationThis topic describes the parameters that are used for new static IP routes.

B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter SettingsThis topic describes the parameters that are used for OSPF settings.

B.3.9 Parameter Description: OSI Management_Network Layer ParameterThis topic describes the parameters that are related to the network layer of the OSI protocolmodel.

B.3.10 Parameter Description: OSI Management_Routing TableThis topic describes the parameters that are related to OSI routing tables.

B.3.11 Parameter Description: OSI Management_OSI TunnelThis topic describes the parameters that are related to the OSI tunnels.

B.3.12 Parameter Description: DCN Management_Bandwidth ManagementThis topic describes the parameters that are used for bandwidth management of the inband DCN.

B.3.13 Parameter Description: DCN Management_Port SettingThis topic describes the parameters that are used for setting ports of the inband DCN.

B.3.14 Parameter Description: Access ControlThis topic describes the parameters that are used for access control of the NMS.

B.3.15 Parameter Description: LCT Access ControlThis topic describes the parameters that are used for LCT access control.

B.3.1 Parameter Description: NE Communication Parameter SettingThis topic describes the parameters that are used for NE communication setting.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Communication >Communication Parameters from the Function Tree.



B-21

Parameters for NE Communication SettingParameter Value Range Default Value Description

IP Address - Before delivery, theIP address of the NEis set to 129.9.0.x.The letter x indicatesthe basic ID.

In the HWECC solution, an IP address is setaccording to the following rules:l The IP address, subnet mask, and default

gateway of the gateway NE should meetthe planning requirements of the externalDCN.

l If an NE uses the extended ECC, the IPaddress must be in the same networksegment.

l The IP address of other NEs should be setaccording to the NE ID. In this case, theIP address of an NE should be set in theformat of 0x81000000+ID. That is, if theID is 0x090001, the IP address should beset to 129.9.0.1.

Gateway IPAddress

- 0.0.0.0

Related TasksA.6.1 Setting NE Communication Parameters

B.3.2 Parameter Description: DCC Management_DCC RateConfiguration

This topic describes the parameters that are used for configuring the DCC rate.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC

Management from the Function Tree.2. Click the DCC Rate Configuration tab.

Parameters for DCC Rate ConfigurationParameter Value Range Default Value Description

Port - - This parameter indicates the port that isconnected to the DCC channel.


Configuration Guide


Issue 02 (2009-10-30)


Enabled/Disabled EnabledDisabled

Enabled (for lineports)Disabled (forexternal clockinterfaces)

It is recommended that you use the defaultvalue, except for the following cases:l If the port is connected to the other ECC

subnet, Enabled/Disabled is set toDisabled.

l If the port is connected to a third-partynetwork and does not exchange thenetwork management information withother ports, Enabled/Disabled is set toDisabled.

l If external clock interfaces are used totransparently transmit the DCC solution,Enabled/Disabled is set to Enabled forthe external clock interfaces.

Channel Type D1-D3D4-D12D1-D12D1-D1

D1-D1 (for the PDHradio whosetransmissioncapacity is less than16xE1)D1-D3 (for othercases)

It is recommended that you use the defaultvalue, except for the following cases:l If the IP over DCC or OSI over DCC

solution is adopted, Channel Type forthe SDH line ports is set to a value that isthe same as the value for third-partynetwork.

l If the DCC transparent transmissionsolution is adopted, the value of ChannelType for the SDH line ports should notconflict with the value that is set for thethird-party network.

DCC Resources - - This parameter indicates the DCCresources.

CommunicationStatus

- - This parameter indicates thecommunication status.

Protocol Type HWECCTCP/IPOSI

HWECC It is recommended that you use the defaultvalue, except for the following cases:l If the IP over DCC solution is adopted,

Protocol Type is set to TCP/IP.l If the OSI over DCC solution is adopted,

Protocol Type is set to OSI.

LAPD Role UserNetwork

User l This parameter is valid only whenProtocol Type is set to OSI.

l In the case of a DCC channel, LAPDRole must be set to User for one end andmust be set to Network for the other end.



B-23

Related TasksA.6.2 Configuring DCCs

B.3.3 Parameter Description: DCC Management_DCC TransparentTransmission Management

This topic describes the parameters that are used for DCC transparent transmission management.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC


2. Click the DCC Transparent Transmission Management tab.

Parameters for DCC Transparent Transmission Management


Source Timeslot/Porta

- - This parameter indicates the source timeslotor port.

TransparentTransmission ofOverhead Bytes atSource Port

D1D2D3D4D5D6D7D8D9D10D11D12E1E2F1K1K2X1X2X3X4

- l Only one overhead byte can be selectedeach time.

l X1, X2, X3, and X4 indicate thecustomized overhead bytes that are usedfor transmitting asynchronous dataservices.

l An overhead byte cannot be a byte that isused. For example, an overhead bytecannot be a byte in the used DCC channel.

Sink Timeslot/Porta

- - This parameter indicates the sink timeslot orport.


Configuration Guide


Issue 02 (2009-10-30)


TransparentTransmission ofOverhead Bytes atSink Port

D1D2D3D4D5D6D7D8D9D10D11D12E1E2F1K1K2X1X2X3X4

- l Only one overhead byte can be selectedeach time.

l An overhead byte cannot be a byte that isused. For example, an overhead bytecannot be a byte in the used DCC channel.

l Generally, Transparent Transmissionof Overhead Bytes at Sink Port can beset to a value that is the same as ordifferent from the value in the case ofSource Timeslot/Port.

NOTE

a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functionsthe same regardless of the source port or sink port.

Related TasksA.6.4 Configuring DCC Transparent Transmission

B.3.4 Parameter Description: ECC Management_Ethernet PortExtended ECC

This topic describes the parameters that are related to the extended ECCs of Ethernet ports.

Navigation PathClick an NE in the NE Explorer. Choose Communication > ECC Management from theFunction Tree.



B-25

Parameters for the ECC Extended ModeParameter Value Range Default Value Description

ECC ExtendedMode

Auto modeSpecified mode

Specified mode It is recommended that you use the defaultvalue.

Parameters for Setting the ServerParameter Value Range Default Value Description

IP - 0.0.0.0 This parameter indicates the IP address ofthe server.

Port 1601 to 1699 1601 l This parameter is valid only when ECCExtended Mode is set to Specifiedmode.

l This parameter can be set only when theNE functions as the server of theextended ECC. In normal cases, the NEthat is close to the U2000 functions as theserver.

l This parameter can be set to any valuefrom 1601 to 1699.

Parameters for Setting the ClientParameter Value Range Default Value Description

Opposite IP - 0.0.0.0 l This parameter is valid only when ECCExtended Mode is set to Specifiedmode.

l This parameter can be set only when theNE functions as the client of the extendedECC. Except for the NE that functions asthe server, all other NEs that use theextended ECC can function as the client.

l Opposite IP and Port are respectively setto the IP address of the server NE and thespecified pot number.

Port 1601 to 1699 1601

Related TasksA.6.3 Configuring the Extended ECC

B.3.5 Parameter Description: NE ECC Link ManagementThis topic describes the parameters that are used for NE ECC link management.


Configuration Guide


Issue 02 (2009-10-30)

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECCLink Management from the Function Tree.

Parameter for NE ECC Link ManagementParameter Value Range Default Value Description

Destination NE - - This parameter specifies the sink NE of theECC connection.

Transfer NE - - This parameter specifies the next transferNE and the direction of the ECC route.

Distance 0 to 64 0 l This parameter specifies the number ofNEs (excluding the source NE and sinkNE) through which the ECC route passes,namely, the number of ECC packetforwarding attempts. The value can be setto a value that is greater than the numberof actual ECC packet forwardingattempts. If the value is set to a value thatis less than the number of actual ECCpacket forwarding attempts, however, thedestination NE fails to be accessed.

l If the value is set to 0, it indicates that thesource NE is adjacent to the destinationNE.

Level 45

- l This parameter indicates that multipleECC routes from the source NE to thedestination NE may be available. AnECC route of a higher priority is selectedto transmit the packets to the destinationNE.

l If the ECC route is generatedautomatically, the priority is 4.

l If the ECC route is added manually, thepriority is 5.

Mode ManualAutomatic

- This parameter indicates the ECC routingmode.

SCC No. - - This parameter specifies the physical portthrough which the ECC route passes. Thevalue of this parameter is automaticallyassigned the NE.

Related TasksA.6.12 Querying ECC Routes



B-27

B.3.6 Parameter Description: IP Protocol Stack Management_IPRoute Management

This topic describes the parameters that are used for IP route management.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP

Protocol Stack Management from the Function Tree.

2. Click the IP Route Management tab.

Parameters for IP Route Management


DestinationAddress

- - This parameter specifies the destinationaddress of the packets. This parameter canbe set to a valid IP address of class A, B, orC only, but cannot be set to the IP addressof the local host or the loopback addresswith the 127 field.

Mask - - This parameter indicates the subnet mask ofthe destination address of the packets.

Gateway IPAddress

- - This parameter specifies the IP address ofthe gateway on the subnetwork where theNE is located, namely, the IP address of thenext hop of the packets.

Protocol DIRECTSTATICOSPFRIPOSPF_ASEOSPF_NSSA

- l DIRECT: indicates the route betweenthe local NE and an adjacent NE.

l STATIC: indicates the route that iscreated manually.

l OSPF: indicates the route between thelocal NE and a non-adjacent NE.

l RIP: indicates the route that is discoveredby the routing information protocol.

l OSPF_ASE: indicates the route whoseDestination Address is beyond theOSPF domain.

l OSPF_NSSA: indicates the route whoseDestination Address is in a not so stubbyarea (NSSA).

l A route can be deleted in the case ofSTATIC only, but cannot be edited in theother cases.

l Compared with a dynamic route, a staticroute has a higher priority. If any conflictoccurs, the static route is preferred.


Configuration Guide


Issue 02 (2009-10-30)


Interface - - This parameter indicates the interface that isused on the route. Interface is a conceptspecified in the TCP/IP protocol stack. Inthe TCP/IP protocol stack, you can createmultiple types of interface, such as aloopback interface (namely, the interfacewhose IP address is 127.0.0.1), an Ethernetinterface, and PPP interface. Each interfacemust have a unique interface name.

Hop Count 0 to 65535 - This parameter indicates the maximumnumber of routers through which thepackets are transmitted. Hop Count is usedto indicate the overhead bytes that aretransmitted to the destination address. Thesmaller the value, the less the overheadbytes. If multiple routes can reach the samedestination address, a route whose overheadis less is preferred to transmit the packets.

Working Status WorkingUnworking

- This parameter indicates whether thecurrent IP route is available.

Related TasksA.6.13 Querying IP Routes

B.3.7 Parameter Description: IP Protocol Stack Management_IPRoute Management Creation

This topic describes the parameters that are used for new static IP routes.


Protocol Stack Management from the Function Tree.2. Click the IP Route Management tab.3. Click New.



B-29

Parameters for Creating IP RoutesParameter Value Range Default Value Description

DestinationAddress

- - This parameter specifies the destinationaddress of the packets. This parameter canbe set to a valid IP address of class A, B, orC only, but cannot be set to the IP addressof the local host or the loopback addresswith the 127 field.

Mask - - This parameter indicates the subnet mask ofthe destination address of the packets.

Gateway IPAddress

- - This parameter specifies the IP address ofthe gateway on the subnetwork where theNE is located, namely, the IP address of thenext hop of the packets.

Related TasksA.6.5 Creating Static IP Routes

B.3.8 Parameter Description: IP Protocol Stack Management_OSPFParameter Settings

This topic describes the parameters that are used for OSPF settings.


Protocol Stack Management from the Function Tree.2. Click the OSPF Parameter Settings tab.

OSPF ParametersParameter Value Range Default Value Description

Area - - l The OSPF protocol supports the divisionof NEs into multiple areas. Only the NEsin the same area can transmit the OSPFpackets to each other to generate theroute.

l When setting the area for the NEs, youneed to set the NEs that run the OSPFprotocol to the same area.


Configuration Guide


Issue 02 (2009-10-30)


DCC Hello Timer(s)

1 to 255 1 l DCC Hello Timer(s) specifies the Hellopacket timer at the DCC interface.

l The Hello packets are used for detectingthe neighbor router on the network that isconnected to the router. By periodicallytransmitting the hello packets, you candetermine whether the interface on theneighbor router is still in the active status.

l DCC Hello Timer(s) determines theinterval for the hello packet timer totransmit the hello packets.

l In the case of two interconnected NEs,DCC Hello Timer(s) must be set to thesame value.

DCC NeighborDead Time(s)

1 to 65535 6 l DCC Neighbor Dead Time(s) specifiesthe dead time of a neighbor router at theDCC interface.

l If the local router fails to receive the hellopackets from the connected neighborrouter within the time specified in DCCNeighbor Dead Time(s), it considersthat the neighbor router is unavailable.

l DCC Neighbor Dead Time(s) should beset to a value that is a minimum of twicethe value of DCC Hello Timer(s).

l In the case of adjacent NEs, DCCNeighbor Dead Time(s) must be set tothe same value. Otherwise, the OSPFprotocol fails to operate normally.

DCCRetransmissionTimer(s)

1 to 65535 5 DCC Retransmission Timer(s) specifiesthe interval for transmitting a requestthrough the DCC interface to retransmit thelink state advertisement (LSA) packets.

DCC Delay(s) 1 to 3600 1 l DCC Delay(s) specifies the delay time totransmit the LSA packets through theDCC interface.

l The LSA packets in the LSA database ofthe local router are aged as the timeelapses, but are not aged when they arebeing transmitted on the network. Hence,before the LSA packets are transmitted,you need to increase the age of the LSApackets based on the value of DCC Delay(s).



B-31


LAN Hello Timer(s)

0 to 65535 - l DCC Hello Timer(s) specifies the hellopacket timer at the LAN interfaces.

l The hello packets are used for detectingthe neighbor router on the network that isconnected to the router. By periodicallytransmitting the hello packets, you candetermine whether the interface on theneighbor router is still in the active status.

l LAN Hello Timer(s) determines theinterval for the hello packet timer of theNE to transmit the hello packets.

l In the case of two interconnected NEs,LAN Hello Timer(s) must be set to thesame value.

LAN NeighborDead Time(s)

l LAN Neighbor Dead Time(s) specifiesthe dead time of a neighbor router at theLAN interface.

l If the local router fails to receive the hellopackets from the connected neighborrouter within the time specified in LANNeighbor Dead Time(s), it considersthat the neighbor router is unavailable.

l LAN Neighbor Dead Time(s) should beset to a value that is a minimum of twotimes the value of LAN Neighbor DeadTime(s).

l In the case of adjacent NEs, DCCNeighbor Dead Time(s) must be set tothe same value. Otherwise, the OSPFprotocol fails to operate normally.

LANRetransmissionTimer(s)

1 to 65535 5 LAN Retransmission Timer(s) specifiesthe time for transmitting a request forretransmission of the LSA packets throughthe LAN interface.

LAN Delay(s) 1 to 3600 1 l LAN Delay(s) specifies the delay time totransmit the LSA packets through theLAN interface.

l The LSA packets in the LSA database ofthe local router are aged as the timeelapses, but are not aged when they arebeing transmitted on the network. Hence,before the LSA packets are transmitted,you need to increase the age of the LSApackets based on the value of LAN Delay(s).


Configuration Guide


Issue 02 (2009-10-30)


Port Type lan lan This parameter specifies the port type of theOSPF protocol.

Used Flag EnabledDisabled

Enabled This parameter specifies Used Flag of theOSPF protocol.

Related TasksA.6.6 Setting Parameters of the OSPF Protocol

B.3.9 Parameter Description: OSI Management_Network LayerParameter

This topic describes the parameters that are related to the network layer of the OSI protocolmodel.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI

Management from the Function Tree.2. Click the Network Layer Parameters tab.

Network Layer ParametersParameter Value Range Default Value Description


Configuration Role L1L2

L1 l An NE whose Configuration Role is setto L1 cannot function as a neighbor of anNE in the other area. It uses a route in thelocal area only and access the other areaby distributing the default route of thenearest L2 NE.

l An NE whose Configuration Role is setto L2 can function as a neighbor of an NEin the other area and can use a route in thebackbone area. The backbone area is acollection that is formed by consecutiveL2 NEs. That is, the L2 NE of all the rolesmust be consecutive (connected to eachother).

Current Role - - This parameter indicates the current role.



B-33

Related TasksA.6.8 Configuring the CLNS Role

B.3.10 Parameter Description: OSI Management_Routing TableThis topic describes the parameters that are related to OSI routing tables.


Management from the Function Tree.2. Click the Routing Table tab.

Parameters for Routing TablesParameter Value Range Default Value Description

Port - - This parameter indicates the port used forOSI communication.

Data Link Layer - - This parameter indicates the protocol that isused at the data link layer.

Adjacency No. - - l This parameter specifies the identifier ofthe adjacency that is set up by two NEsthrough the OSI protocol. One adjacencynumber corresponds to an OSI adjacency.

l The value is dynamically allocated by theNE.

Adjacency Type - - This parameter indicates the type of theadjacency.

Adjacency State - - This parameter indicates the state of theadjacency.

Peer End Area ID - - This parameter indicates the area ID that iscontained in the NSAP address of theopposite NE.

Peer End SystemID

- - This parameter indicates the system ID ofthe opposite NE. Generally, the system IDis the MAC address.

Destination SYSID - - This parameter indicates the system ID ofthe destination NE. Generally, the systemID is the MAC address.

Metric - - This parameter indicates the number of hopsthat reach the destination NE or destinationarea.


Configuration Guide


Issue 02 (2009-10-30)


Adjacency No.1 - - This parameter indicates the number of theadjacent link that is connected to thedestination NE.

Adjacency No.2 - - This parameter indicates the number of theadjacent link that is connected to thedestination NE.

Related TasksA.6.14 Querying OSI Routes

B.3.11 Parameter Description: OSI Management_OSI TunnelThis topic describes the parameters that are related to the OSI tunnels.


Management from the Function Tree.2. Click the OSI Tunnel tab.

Parameters for OSI Tunnel AttributesParameter Value Range Default Value Description

Remote IP Address - - This parameter indicates the IP address ofthe opposite end of the OSI tunnel.

LAPD Actor UserNetwork

User l This parameter specifies the LAPD actor.

l If the adjacent NEs run the OSI protocol,they can perform the LAPD negotiationonly when the LAPD actor is set toUser at one end and is set to Network atthe other end.

Efficient LAPDEnable

- - This parameter indicates whether thecurrent LAPD is enabled.

Configure LAPDEnable

EnabledDisabled

Enabled This parameter specifies whether the LAPDis enabled.



B-35

LAPD ParametersParameter Value Range Default Value Description

Remote IP Address - - This parameter indicates the IP address ofthe opposite end of the OSI tunnel.

L2 Wait Time toRetry(s)

1 to 20 1 l This parameter specifies L2 Wait Timeto Retry(s).

l L2 Wait Time to Retry(s) indicates theinterval for retransmitting packets at theLAPD link layer.

l L2 Wait Time to Retry(s) needs to beset according to the network situation. Ifthe network is in good situation, L2 WaitTime to Retry(s) can be set to a smallervalue. Otherwise, it is recommended thatyou set L2 Wait Time to Retry(s) to agreater value.

l This parameter needs to be set accordingto the planning information. In normalcases, it is recommended that you use thedefault value.

L2 Retry Times 2 to 6 3 l This parameter specifies L2 RetryTimes.

l L2 Retry Times indicates the maximumnumber of packet retransmissionattempts at the LAPD link layer.

l L2 Retry Times needs to be setaccording to the network situation. If thenetwork is in good situation, L2 RetryTimes can be set to a smaller value.Otherwise, it is recommended that youset L2 Retry Times to a greater value.



Configuration Guide


Issue 02 (2009-10-30)


L3 Hello Timer(s) 1 to 100 3 l This parameter specifies L3 Hello Timer(s).

l L3 Hello Timer(s) indicates the Hellopacket timer at the LAPD link networklayer. It is used for periodicaltransmission of the Hello packets.

l The Hello timer determines the intervalfor transmitting the Hello packets once.L3 Hello Timer(s) needs to be setaccording to the network situation. If thenetwork is in good situation, L3 HelloTimer(s) can be set to a greater value.Otherwise, it is recommended that youset L3 Hello Timer(s) to a smaller value.


L3 E3 Timer(s) 1 to 200 50 l This parameter specifies L3 E3 Timer(s).

l L3 E3 Timer(s) indicates the ESconfiguration timer at the LAPD linknetwork layer. It is used for setting thetime to transmit the configurationinformation on the ES route.

l L3 E3 Timer(s) needs to be set accordingto the network situation. If the network isin good situation, L3 E3 Timer(s) can beset to a greater value. Otherwise, it isrecommended that you set L3 HelloTimer(s) to a smaller value.




B-37


L3 IS Timer(s) 1 to 200 10 l This parameter specifies L3 IS Timer(s).

l L3 IS Timer(s) indicates the ISconfiguration timer at the LAPD linknetwork layer. It is used for setting thetime to transmit the configurationinformation through the L1/L2 router.

l L3 IS Timer(s) needs to be set accordingto the network situation. If the network isin good situation, L3 IS Timer(s) can beset to a greater value. Otherwise, it isrecommended that you set L3 IS Timer(s) to a smaller value.


L3 Hold Timer(s) 2 to 63 5 l This parameter specifies L3 Hold Timer(s).

l L3 Hold Timer(s) indicates the holdtimer at the LAPD link network layer.

l L3 Hold Timer(s) needs to be setaccording to the network situation. If thenetwork is in good situation, L3 HoldTimer(s) can be set to a smaller value.Otherwise, it is recommended that youset L3 IS Timer(s) to a greater value.


COST 1 to 63 20 l This parameter specifies COST.

l COST indicates the overhead value ofthe virtual LAPD that corresponds to theOSI tunnel.

l The overhead value determines whetherthis link is perverted. If the overheadvalue is smaller, this link has a higherpriority to be selected.

l This parameter needs to set according tothe planning information.

Related TasksA.6.9 Configuring the OSI Tunnel


Configuration Guide


Issue 02 (2009-10-30)

B.3.12 Parameter Description: DCN Management_BandwidthManagement

This topic describes the parameters that are used for bandwidth management of the inband DCN.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN

Management from the Function Tree.2. Click the Bandwidth Management tab.

Parameters for Bandwidth Management


Ethernet BoardVLAN ID

1 to 4094 4094 l The equipment on the traditional DCNcan be connected to the NMS through theSCC board, but the OptiX RTN 910 canalso be connected to the NMS through anEthernet interface. If an Ethernet port isused to carry the network managementinformation, the NE differentiates thenetwork management information andEthernet service information accordingto the VLAN ID.

l If the default VLAN ID of the inbandDCN conflicts with the VLAN ID in theservice, the VLAN ID of the inband DCNcan be changed manually. The sameVLAN ID must be, however, is used onthe network-wide inband DCN.

Bandwidth(kbps) - - This parameter specifies the bandwidth ofthe inband DCN.

E1 Port Bandwidth(kbps)

- - The OptiX RTN 910 does not support thisparameter.

Tunnel Bandwidth(kbps)


IF Port Bandwidth(kbps)


Related TasksA.6.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN

B.3.13 Parameter Description: DCN Management_Port SettingThis topic describes the parameters that are used for setting ports of the inband DCN.



B-39

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN


2. Click the Port Settings tab.

Parameters for Setting FE or GE Ports


Port Name - - This parameter indicates the name of the FEor GE port.

Enable Status EnabledDisabled

Enabled l This parameter specifies whether the FEor GE port is enabled.

l The inband DCN can transmit thenetwork management information overthe link only after the inband DCNfunction is enabled at the FE or GE portsat both ends of a link.

Parameters for Setting IF Ports


Port Name - - This parameter indicates the name of the IFport.

Enable Status EnabledDisabled

Enabled l This parameter specifies whether the IFport is enabled.

l The inband DCN can transmit thenetwork management information overthe link only after the IF ports at both endsof a link are enabled on the inband DCN.

Related TasksA.6.11 Configuring the Enable Status of the Inband DCN Function on Ports

B.3.14 Parameter Description: Access ControlThis topic describes the parameters that are used for access control of the NMS.

Navigation Path

Select the NE from the Object Tree in the NE Explorer. Choose Communication > AccessControl from the Function Tree.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for Ethernet Access ControlParameter Value Range Default Value Description

The First NetworkPort

EnabledDisabled

Enabled After The First Network Port is set toEnabled for Ethernet access, the NE canaccess the NMS through the Ethernet port.

Parameters for Access Control over Serial PortsParameter Value Range Default Value Description

Enable Serial PortAccess

SelectedDeselected

Selected After Enable Serial Port Access isselected, the NE can access the NMS orcommand lines through the serial port.

Baud Rate 1200240048009600192003840057600115200

9600 l This parameter specifies the datatransmission rate in the communicationsthrough serial ports.

l This parameter is set according to the rateof the serial port at the opposite end, andthe rates at both ends must be the same.

B.3.15 Parameter Description: LCT Access ControlThis topic describes the parameters that are used for LCT access control.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Security > LCT AccessControl from the Function Tree.

Parameters for LCT Access ControlParameter Value Range Default Value Description




B-41


LCT AccessControl Switch

Enable AccessDisable Access

Enable Access l No NMS user logs in to the NE. In thiscase, when the LCT requests an LCT userto log in to the NE, the NE does not checkthe status of LCT Access ControlSwitch, and directly allows the LCT userto log in to the NE.

l An NMS user first logs in to the NE. Inthis case, when the LCT requests an LCTuser to log in to the NE, the NEdetermines whether to allow the LCTuser to log in to the NE through the LCTaccording to the status of LCT AccessControl Switch.

l An LCT user first logs in to the NE. Inthis case, when the NMS requests anNMS user to log in to the NE, the NMSuser can directly log in to the NE. Afterthe NMS user successfully logs in to theNE, the online LCT user is not affected.

l When both the LCT user and NMS userlog in to the NE, the online LCT user isnot affected after LCT Access ControlSwitch is set to Disable Access.

B.4 Radio Link ParametersThis topic describes the parameters that are related to radio links.

B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_CreationThis topic describes the parameters that are related to the XPIC function.

B.4.2 Parameter Description: Link Configuration_XPICThis topic describes the parameters that are related to the XPIC function.

B.4.3 Parameter Description: N+1 Protection_CreateThis topic describes the parameters that are used for creating an IF N+1 protection group.

B.4.4 Parameter Description: N+1 ProtectionThis topic describes the parameters that are related to IF N+1 protection.

B.4.5 Parameter: IF 1+1 Protection_CreateThis topic describes the parameters that are used for creating an IF 1+1 protection group.

B.4.6 Parameter Description: IF 1+1 ProtectionThis topic describes the parameters that are related to IF 1+1 protection.

B.4.7 Parameter: Link Configuration_IF/ODU ConfigurationThis topic describes the parameters that are used for configuring the IF/ODU.


Configuration Guide


Issue 02 (2009-10-30)

B.4.1 Parameter Description: Link Configuration_XPICWorkgroup_Creation

This topic describes the parameters that are related to the XPIC function.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link

Configuration from the Function Tree.2. Click the XPIC tab.3. Click New.

ParametersParameter Value Range Default Value Description

IF ChannelBandwidth

7M14M28M56M

7M l This parameter specifies the workingbandwidth of the radio link.

l When this parameter is set to 56M, thehigh-power ODU must be used.

Polarizationdirection-V

- - l This parameter indicates the polarizationdirection of a radio link.

l It is recommended that you set the IF porton the IFX2 board that has a smaller slotnumber to Link ID-V and the IF port onthe other IFX2 board to Link ID-H.

Polarizationdirection-H

Link ID-V 1 to 4094 1 l Set Link ID-V and Link ID-H.l A link ID is an identifier of a radio link

and is used to prevent the radio linksbetween sites from being wronglyconnected.

l When the link ID received by an NE isdifferent from the link ID set for the NE,the NE reports an MW_LIM alarm andinserts the AIS.

l These two parameters are set accordingto the planning information. These twoparameters must be set to differentvalues, but Link ID-V must be set to thesame value at both ends of a link and LinkID-H must also be set to the same valueat both ends of a link.

Link ID-H 2



B-43


Transmit Power(dBm)

- - l This parameter specifies the transmitpower of an ODU. The value of thisparameter must not exceed the ratedpower range supported by the ODU.

l The transmit power of the ODU must beset to the same value at both ends of aradio link.

l Consider the receive power of the ODUat the opposite end when you set thisparameter. Ensure that the receive powerof the ODU at the opposite end can ensurestable radio services.

l This parameter is set according to theplanning information.

MaximumTransmit Power(dBm)

- - l This parameter specifies the maximumtransmit power of the ODU. Thisparameter cannot be set to a value thatexceeds the nominal power rang of theODU in the guaranteed capacitymodulation module..

l This parameter is set to limit themaximum transmit power of the ODUwithin this preset range.

l The maximum transmit power adjustedby using the ATPC function should notexceed this value.


TransmissionFrequency(MHz)

- - l This parameter indicates the channelcentral frequency.

l The value of this parameter must not beless than the sum of the lower transmitfrequency limit supported by the ODUand a half of the channel spacing, andmust not be more than the differencebetween the upper transmit frequencylimit supported by the ODU and a half ofthe channel spacing.



Configuration Guide


Issue 02 (2009-10-30)


T/R Spacing(MHz) - - l This parameter specifies the spacingbetween the transmit frequency and thereceive frequency of an ODU to preventmutual interference between thetransmitter and the receiver.

l If Station Type of the ODU is TX high,the transmit frequency is one T/R spacinghigher than the receive frequency. IfStation Type of the ODU is TX low, thetransmit frequency is one T/R spacinglower than the receive frequency.

l If the ODU supports only one T/Rspacing, set this parameter to 0,indicating that the T/R spacing supportedby the ODU is used.

l A valid T/R spacing value is determinedby the ODU itself, and the T/R spacingshould be set according to the technicalspecifications of the ODU.

l The T/R spacing of the ODU should beset to the same value at both the ends ofa radio link.

TransmissionStatus

unmutemute

unmute l When this parameter is set to mute, theODU does not work but can normallyreceive microwave signals.

l When this parameter is set to unmute, theODU normally transmits and receivesmicrowave signals.

l In normal cases, this parameter is set tounmute.



B-45


ATPC Enabled DisabledEnabled

Disabled l This parameter specifies whether theATPC function is enabled.

l When this parameter is set to Enabledand if the RSL at the receive end is 2 dBhigher or lower than the central valuebetween the ATPC upper threshold andthe ATPC lower threshold at the receiveend, the receiver notifies the transmitterto decrease or increase the transmit poweruntil the RSL is within the range that is 2dB higher or lower than the central valuebetween the ATPC upper threshold andthe ATPC lower threshold.

l The settings of the ATPC attributes mustbe consistent at both ends of a radio link.

l In the case of areas where fast fadingseverely affects the radio transmission, itis recommended that you set thisparameter to Disabled.

l During the commissioning process, setthis parameter to Disabled to ensure thatthe transmit power is not changed. Afterthe commissioning, re-set the ATPCattributes.

ATPC UpperThreshold(dBm)

-75.0 to -20.0 -45.0 l The central value between the ATPCupper threshold and the ATPC lowerthreshold is set as the expected receivepower.

l It is recommended that you set ATPCUpper Threshold(dBm) to the sum ofthe planned central value between theATPC upper threshold and the ATPClower threshold and 10 dB, and ATPCLower Threshold(dBm) to thedifference between the planned centralvalue between the ATPC upper thresholdand the ATPC lower threshold and 10 dB.

l You can set the ATPC upper thresholdonly when ATPC Automatic ThresholdEnable Status is set to Disabled.

ATPC LowerThreshold(dBm)

-35.0 to -90.0 -70.0

ATPC AutomaticThreshold EnableStatus

DisabledEnabled

Disabled l This parameter specifies whether theautomatic threshold function is enabled.

l If this parameter is set to Enabled, theequipment automatically uses the presetATPC upper and lower thresholdsaccording to the work mode of the radiolink.


Configuration Guide


Issue 02 (2009-10-30)

Related TasksA.7.2 Creating an XPIC Protection Group

B.4.2 Parameter Description: Link Configuration_XPICThis topic describes the parameters that are related to the XPIC function.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link

Configuration from the Function Tree.2. Click the XPIC tab.


Group ID - - This parameter indicates the ID of the workgroup.

Polarizationdirection-V

- - This parameter indicates the IF port to whichthe polarization direction V corresponds.

Link ID-V - - This parameter indicates the link ID towhich the polarization direction Vcorresponds.

Polarizationdirection-H

- - This parameter indicates the IF port to whichthe polarization direction H corresponds.

Link ID-H - - This parameter indicates the link ID towhich the polarization direction Hcorresponds.

IF ChannelBandwidth

7M

14M

28M

56M

7M l IF Channel Bandwidth refers to thechannel spacing of the correspondingradio links.




B-47


Power to BeReceived -V(dBm)

- - l This parameter is used to set the expectedreceive power of the ODU and is mainlyused in the antenna alignment stage.After this parameter is set, the NEautomatically enables the antennamisalignment indicating function.

l When the antenna misalignmentindicating function is enabled, if theactual receive power of the ODU exceedsthe range of receive power±3 dB, theODU LED of the IF board connected tothe ODU is on (yellow) for 300 ms andoff for 300 ms repeatedly, indicating thatthe antenna is not aligned.

l After the antenna alignment, after thestate that the antenna is aligned lasts for30 minutes, the NE automaticallydisables the antenna misalignmentindicating function.


Power to BeReceived -H(dBm)

- - l This parameter is used to set the expectedreceive power of the ODU and is mainlyused in the antenna alignment stage.After this parameter is set, the NEautomatically enables the antennamisalignment indicating function.





Configuration Guide


Issue 02 (2009-10-30)







Transmit Power(dBm)

- - l This parameter indicates or specifies thetransmit power of the ODU. Thisparameter cannot be set to a value thatexceeds the nominal power range of theODU.

l The transmit power of the ODU shouldbe set to the same value at both ends of aradio link.



TransmissionFrequency(MHz)

- - l This parameter indicates or specifies thetransmit frequency of the ODU, namely,the channel central frequency.

l The value of this parameter must not beless than the sum of the lower TXfrequency limit supported by the ODUand a half of the channel spacing, andmust not be more than the differencebetween the upper TX frequency limitsupported by the ODU and a half of thechannel spacing.

l The difference between the transmitfrequencies of both the ends of a radiolink should be one T/R spacing.

l This parameter needs to be set accordingto the planning information.



B-49


T/R Spacing(MHz) - - l This parameter indicates or specifies thespacing between the transmit frequencyand receive frequency of the ODU toprevent mutual interference between thetransmitter and receiver.

l If the ODU is a Tx high station, thetransmit frequency is one T/R spacinghigher than the receive frequency. If theODU is a Tx low station, the transmitfrequency is one T/R spacing lower thanthe receive frequency.

l If the ODU supports only one T/Rspacing, this parameter is set to 0,indicating that the T/R spacing supportedby the ODU is used.


l The T/R spacing of the ODU should beset to the same value at both ends of aradio link.

TransmissionStatus

unmutemute

unmute l This parameter indicates or specifies thetransmit status of the ODU.

l If this parameter is set to mute, thetransmitter of the ODU does not work butcan normally receive microwave signals.

l If this parameter is set to unmute, theODU can normally transmit and receivemicrowave signals.


Parameters for Hybrid/AM ConfigurationParameter Value Range Default Value Description

Group ID - - This parameter indicates the ID of the workgroup.


- - This parameter indicates the IF port to whichthe polarization direction H or thepolarization direction V corresponds.


Configuration Guide


Issue 02 (2009-10-30)


AM Mode Asymmetric Asymmetric If AM Mode is set to Asymmetric, the AMswitching in one direction of the radio linkdoes not trigger the AM switching in theother direction of the radio link.NOTE

The Optix RTN equipment supportsonlyAsymmetric.

AM Enable Status DisabledEnabled

Disabled l When this parameter is set to Disabled,the radio link uses only the specifiedmodulation scheme. In this case, youneed to select Manually SpecifiedModulation Mode.

l When this parameter is set to Enabled,the radio link uses the correspondingmodulation scheme according to thechannel conditions.

Hence, the Hybrid radio can ensure thereliable transmission of the E1 services andprovide bandwidth adaptively for theEthernet services when the AM function isenabled.

Modulation Modeof the GuaranteedAM Capacity

QPSK16QAM32QAM64QAM128QAM256QAM

- This parameter specifies the highest-gainmodulation scheme that the AM functionsupports. This parameter is set according tothe planning information. Generally, thevalue of this parameter is determined by thebandwidth of the services that need to betransmitted over the Hybrid radio and theavailability of the radio link thatcorresponds to this modulation scheme.NOTE

Modulation Mode of the Full AM Capacitymust be higher than Modulation Mode of theGuaranteed AM Capacity.

This parameter is valid only when AMEnable Status is set to Enabled.



B-51


Modulation Modeof the Full AMCapacity




This parameter is valid only when AMEnable Status is set to Enabled.

Manually SpecifiedModulation Mode


QPSK This parameter specifies the modulationscheme that the radio link uses for signaltransmission.This parameter is valid only when AMEnable Status is set to Disabled.

Guaranteed E1Capacity

- - l When AM Enable Status is set toEnabled, this parameter depends on IFChannel Bandwidth and ModulationMode of the Guaranteed AMCapacity and cannot be set.

l When AM Enable Status is set toDisabled, this parameter depends on IFChannel Bandwidth and ManuallySpecified Modulation Mode and cannotbe set.

E1 Capacity 1 to 75 - This parameter specifies the number of E1services that can be transmitted in Hybridwork mode.

Parameters for ATPC ManagementParameter Value Range Default Value Description

Group ID - - This parameter indicates the object to be set.


Configuration Guide


Issue 02 (2009-10-30)


ATPC EnableStatus

DisabledEnabled

Enabled l This parameter specifies whether theATPC function is enabled.

l If this parameter is set to Enabled and ifthe RSL at the receive end is 2 dB higheror lower than the central value betweenthe ATPC upper threshold and the ATPClower threshold at the receive end, thereceiver notifies the transmitter todecrease or increase the transmit poweruntil the RSL is within the range that is 2dB higher or lower than the central valuebetween the ATPC upper threshold andthe ATPC lower threshold.





-75.0 to -20.0 -45.0 l Set the central value between the ATPCupper threshold and the ATPC lowerthreshold to a value for the expectedreceive power.

l It is recommended that you set ATPCUpper Threshold(dBm) to the sum ofthe planned central value between theATPC upper threshold and the ATPClower threshold and 10 dB, and ATPCLower Threshold(dBm) o the differencebetween the planned central valuebetween the ATPC upper threshold andthe ATPC lower threshold and 10 dB.

l You can set this parameter only whenATPC Automatic Threshold EnableStatus is set to Disabled.


-35.0 to -90.0 -70.0



B-53



DisabledEnabled

Disabled l This parameter specifies whether theATPC automatic threshold function isenabled.


l If this parameter is set to Disabled, youneed to manually set ATPC UpperThreshold(dBm) and ATPC LowerThreshold(dBm).

Related TasksA.7.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link

B.4.3 Parameter Description: N+1 Protection_CreateThis topic describes the parameters that are used for creating an IF N+1 protection group.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1

Protection from the Function Tree.2. Click Create.


WTR time(s) 300 to 720 600 l This parameter specifies the wait-to-restore (WTR) time.

l When the time after the former workingchannel is restored to normal reaches theset WTR time, a revertive switchingoccurs.

l It is recommended that you use thedefault value.


Configuration Guide


Issue 02 (2009-10-30)


Enabled EnabledDisabled

Enabled l This parameter specifies whether the SDswitching function of N+1 protection isenabled.

l When this parameter is set to Enabled,the SD condition is considered as atrigger condition of protection switching.

l It is recommended that you set thisparameter to Enabled.

Slot Mapping Relation Parameters


Select MappingDirection

Work UnitProtection Unit

Work Unit l This parameter specifies the mappingdirection of N+1 protection.


Select MappingWay

- - l In the case of N+1 protection, map N IFports as Work Unit and map theremaining IF port as Protection Unit.


Mapped Board - - This parameter indicates the working unitand protection unit that have been set.

Related TasksA.7.6 Creating an N+1 Protection Group

B.4.4 Parameter Description: N+1 ProtectionThis topic describes the parameters that are related to IF N+1 protection.

Navigation Path

Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1Protection from the Function Tree.

Protection Group Parameters


Protection GroupID

- - This parameter indicates the ID of theprotection group.



B-55


WTR Time(s) 300 to 720 - l This parameter indicates or specifies theWTR time.



SD Enable EnabledDisabled

- l This parameter indicates or specifieswhether the SD switching function of N+1 protection is enabled.

l When this parameter is set to Enabled,the SD condition is considered as atrigger condition of protection switching.


Protocol Status - - This parameter indicates the status of theswitching control protocol.

Protection Unit ParametersParameter Value Range Default Value Description

Protection Unit - - This parameter indicates the protection unit.

Line - - This parameter indicates the informationabout the working board or protectionboard.

Switching Status - - This parameter indicates the switching state.

Protection Unit - - This parameter indicates the protected unit.

Remote/Local EndIndication

- - This parameter indicates the local end orremote end.

Related TasksA.7.14 Querying the IF N+1 Protection Status

B.4.5 Parameter: IF 1+1 Protection_CreateThis topic describes the parameters that are used for creating an IF 1+1 protection group.


Configuration Guide


Issue 02 (2009-10-30)

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1

Protection from the Function Tree.2. Click Create.


Working Mode HSBFDSD

HSB l This parameter specifies the workingmode of the IF 1+1 protection.

l In HSB mode, the equipment provides a1+1 hot standby configuration for the IFboard and ODU at both ends of each hopof a radio link to realize the protection.

l In FD mode, the system uses twochannels that have a frequency spacingbetween them, to transmit and receive thesame signal. The remote end selectssignals from the two received signals.With FD protection, the impact of thefading on signal transmission is reduced.

l In SD mode, the system uses twoantennas that have a space distancebetween them, to receive the same signal.The equipment selects signals from thetwo received signals. With SD protection,the impact of the fading on signaltransmission is reduced.

l The FD mode and SD mode arecompatible with the HSB switchingfunction.




B-57


Revertive Mode Revertive ModeNon-RevertiveMode

Revertive Mode l This parameter specifies the revertivemode of the IF 1+1 protection.

l When this parameter is set to RevertiveMode, the NE that is in the switchingstate releases the switching and enablesthe former working channel to return tothe normal state some time after theformer working channel is restored tonormal.

l When this parameter is set to Non-Revertive Mode, the NE that is in theswitching state keeps the current stateunchanged unless another switchingoccurs even though the former workingchannel is restored to normal.

l It is recommended that you set thisparameter to Revertive Mode.

WTR Time(s) 300 to 720 600 l This parameter specifies the wait-to-restore (WTR) time.


l You can set WTR Time(s) only whenRevertive Mode is set to RevertiveMode.


Enable ReverseSwitching

EnabledDisabled

Enabled l This parameter indicates whether thereverse switching function is enabled.

l When both the main IF board and thestandby IF board at the sink end reportservice alarms, they send the alarms to thesource end by using the MWRDIoverhead in the microwave frame. Whenthis parameter at the source end is set toEnabled and the reverse switchingconditions are met, the IF 1+1 protectionswitching occurs at the source end.

l This parameter is valid only whenWorking Mode is set to HSB or SD.

l In normal cases, it is recommended thatyou set this parameter to Enabled.

Working Board - - This parameter specifies the working boardof the protection group.


Configuration Guide


Issue 02 (2009-10-30)


Protection Board - - This parameter specifies the protectionboard of the protection group.

NOTE

Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable ReverseSwitching must be set to the same value at both ends of a radio hop.

Related TasksA.7.1 Creating an IF 1+1 Protection Group

B.4.6 Parameter Description: IF 1+1 ProtectionThis topic describes the parameters that are related to IF 1+1 protection.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1Protection from the Function Tree.

Protection Group ParametersParameter Value Range Default Value Description

Protection GroupID




B-59


Working Mode HSBFDSD

HSB l This parameter indicates the workingmode of the created IF 1+1 protectiongroup.

l In HSB mode, the equipment provides a1+1 hot standby configuration for the IFboard and ODU at both ends of each hopof a radio link to realize the protection.

l In FD mode, the system uses twochannels that have a frequency spacingbetween them, to transmit and receive thesame signal. The remote end selectssignals from the two received signals.With FD protection, the impact of thefading on signal transmission is reduced.

l In SD mode, the system uses twoantennas that have a space distancebetween them, to receive the same signal.The equipment selects signals from thetwo received signals. With SD protection,the impact of the fading on signaltransmission is reduced.

l The FD mode and SD mode arecompatible with the HSB switchingfunction.


Revertive Mode Revertive ModeNon-RevertiveMode

Revertive Mode l This parameter indicates or specifies therevertive mode of the protection group.

l When this parameter is set to RevertiveMode, the NE that is in the switching statereleases the switching and enables theformer working channel to return to thenormal state some time after the formerworking channel is restored to normal.

l When this parameter is set to Non-Revertive Mode, the NE that is in theswitching state keeps the current stateunchanged unless another switchingoccurs even though the former workingchannel is restored to normal.

l It is recommended that you set thisparameter to Revertive Mode.


Configuration Guide


Issue 02 (2009-10-30)


WTR Time(s) 300 to 720 600 l This parameter indicates or specifies theWTR time.


l You can set WTR Time(s) only whenRevertive Mode is set to RevertiveMode.

l It is recommended that you use the defaultvalue.

Enable ReverseSwitching

EnabledDisabled

Enabled l This parameter indicates or specifieswhether the reverse switching function isenabled.

l When both the main IF board and thestandby IF board at the sink end reportservice alarms, they send the alarms to thesource end by using the MWRDIoverhead in the microwave frame. Whenthis parameter at the source end is set toEnabled and the reverse switchingconditions are met, the IF 1+1 protectionswitching occurs at the source end.

l This parameter is valid only whenWorking Mode is set to HSB or SD.

Switching Status ofDevice

- - l This parameter indicates the switchingstate on the equipment side.

l Unknown is displayed when theswitching state on the channel side is notqueried or not obtained after a query.

Switching Status ofChannel

- - l This parameter indicates the switchingstate on the channel side.

l Unknown is displayed when theswitching state on the channel side is notqueried or not obtained after a query.

Active Board ofDevice

- - This parameter indicates the currentworking board on the equipment side.

Active Board ofChannel

- - This parameter indicates the currentworking board on the channel side.

NOTE

Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable ReverseSwitching must be set to the same value at both ends of a radio hop.



B-61

Slot Mapping Relation ParametersParameter Value Range Default Value Description

Unit - - This parameter indicates the working boardand protection board.

Slot MappingRelation

- - This parameter indicates the names andports of the working board and protectionboard.

Working Status ofDevice

- - This parameter indicates the working stateon the equipment side.

Signal Status ofChannel

- - This parameter indicates the status of thelink signal.

Related TasksA.7.13 Querying the IF 1+1 Protection Status

B.4.7 Parameter: Link Configuration_IF/ODU ConfigurationThis topic describes the parameters that are used for configuring the IF/ODU.

Navigation Path1. In the NE Explorer, select the NE and then choose Configuration > Link

Configuration from the Function Tree.2. Click the IF/ODU Configuration tab.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for Configuring the IFParameter Value Range Default Value Description

Work Mode 1,4E1,7MHz,QPSK2,4E1,3.5MHz,16QAM3,8E1,14MHz,QPSK4,8E1,7MHz,16QAM5,16E1,28MHz,QPSK6,16E1,14MHz,16QAM7,STM-1,28MHz,128QAM8,E3,28MHz,QPSK9,E3,14MHz,16QAM10,22E1,14MHz,32QAM11,26E1,14MHz,64QAM12,32E1,14MHz,128QAM13,35E1,28MHz,16QAM14,44E1,28MHz,32QAM15,53E1,28MHz,64QAM

- l This parameter indicates or specifies thework mode of the radio link in "workmode number, service capacity, channelspacing, modulation mode" format.

l This parameter is set according to theplanning information. The work modesof the IF boards at the two ends of a radiolink must be the same.

NOTEThis parameter is not applicable to the IFU2board and the IFX2 board.



B-63


Enable AM DisabledEnabled

Disable l When this parameter is set to Disabled,the radio link uses only the specifiedmodulation scheme. In this case, youneed to select Manually SpecifiedModulation Mode.

l When this parameter is set to Enabled,the radio link uses the correspondingmodulation scheme according to thechannel conditions.

Hence, the Hybrid radio can ensure thereliable transmission of the E1 services andprovide bandwidth adaptively for theEthernet services when the AM function isenabled.NOTE

This parameter is not applicable to the IF1 board.

Channel Space 7M14M28M56M

7M Channel Space indicates the channelspacing of the corresponding radio link.This parameter is set according to theplanning information.NOTE


GuaranteedCapacityModulation


QPSK This parameter specifies the lowest-gainmodulation scheme that the AM functionsupports. This parameter is set according tothe planning information. Generally, thevalue of this parameter is determined by theservice transmission bandwidth that theHybrid radio must ensure and theavailability of the radio link thatcorresponds to this modulation scheme.This parameter is valid only when EnableAM is set to Enabled.NOTE



Configuration Guide


Issue 02 (2009-10-30)


Full CapacityModulation



Full Capacity Modulation must be higher thanGuaranteed E1 Capacity.

This parameter is valid only when EnableAM is set to Enabled.NOTE


Manually SpecifiedModulation


QPSK This parameter specifies the modulationscheme that the radio link uses for signaltransmission.

This parameter is valid only when EnableAM is set to Disabled.NOTE



- - l When Enable AM is set to Enabled, thisparameter depends on Channel Spaceand Guaranteed E1 Capacity and is notconfigurable.

l When Enable AM is set to Disabled, thisparameter depends on Channel Spaceand Manually Specified ModulationMode and is not configurable.

NOTEThis parameter is not applicable to the IF1 board.


- - This parameter specifies the number of E1services that can be transmitted in theHybrid work mode.NOTE




B-65


Link ID 1 to 4094 1 l This parameter indicates or specifies theID of a radio link. As the identifier of aradio link, this parameter is used toprevent incorrect connections of radiolinks between sites.

l If the value of Received Radio Link IDdoes not match the preset value of LinkID at the local end, the local end insertsthe AIS signal to the downstreamdirection of the service. At the same time,the local end reports MW_LIM alarm tothe NMS, indicating that the link IDs donot match.

l Each radio link of an NE should have aunique link ID, and the link IDs at bothends of a radio link should be the same.

Received Link ID 1 to 4094 - This parameter indicates the received ID ofthe radio link.NOTE

When the radio link becomes faulty, thisparameter is displayed as an invalid value.

ATPC EnableStatus

DisabledEnabled

Disabled l This parameter specifies whether theATPC function is enabled. If the APTCfunction is enabled, the transmit power ofthe transmitter automatically varieswithin the specified ATPC rangeaccording to the change of the RSL at thereceive end.





l It is recommended that you set ATPCUpper Threshold(dBm) to the sum ofthe planned central value between theATPC upper threshold and the ATPClower threshold and 10 dB, and ATPC


Configuration Guide


Issue 02 (2009-10-30)



-35.0 to -90.0 -70.0 Lower Threshold(dBm) to thedifference between the planned centralvalue between the ATPC upper thresholdand the ATPC lower threshold and 10 dB.

l You can set the ATPC upper thresholdonly when ATPC Automatic Threshold(dBm) is set to Disabled.


EnabledDisabled





EnabledDisabled

Disabled If the OptiX RTN 910 is interconnected withthe packet radio equipment, this parameteris set to Enabled. Otherwise, this parameteris set to Disabled.NOTE




B-67

Parameters for Configuring the ODUParameter Value Range Default Value Description

TX Frequency(MHz)

- - l This parameter indicates or specifies thetransmit frequency of the ODU, namely,the channel central frequency.

l The value of this parameter must not beless than the sum of the lower TXfrequency limit supported by the ODUand a half of the channel spacing, andmust not be more than the differencebetween the upper TX frequency limitsupported by the ODU and a half of thechannel spacing.

l The difference between the transmitfrequencies of both the ends of a radiolink should be one T/R spacing.


Range of TXFrequency(MHz)

- - l This parameter indicates the range of thetransmit frequency of the ODU.

l The Range of Frequency(MHz)depends on the specifications of theODU.

Actual TXFrequency(MHz)

- - This parameter indicates the actual transmitfrequency of the ODU.

Actual RXFrequency(MHz)

- - This parameter indicates the actual receivefrequency of the ODU.


Configuration Guide


Issue 02 (2009-10-30)


T/R Spacing(MHz) - - l This parameter specifies the spacingbetween the transmit frequency and thereceive frequency of an ODU to preventinterference between them.

l If Station Type of the ODU is TX high,the TX frequency is one T/R spacinghigher than the receive frequency. IfStation Type of the ODU is TX low, theTX frequency is one T/R spacing lowerthan the receive frequency.

l If the ODU supports only one T/Rspacing, set this parameter to 0, indicatingthat the T/R spacing supported by theODU is used.


l The T/R spacing of the ODU should beset to the same value at both the ends ofa radio link.

Actual T/RSpacing(MHz)

- - This parameter indicates the actual T/Rspacing of the ODU.

TX Power(dBm) - - l This parameter indicates or specifies thetransmit power of the ODU. Thisparameter cannot be set to a value thatexceeds the nominal power range of theODU.

l This parameter cannot take a valuegreater than the preset value ofMaximum Transmit Power(dBm).




TX HighThreshold(dBm)

- - l If the value of the actual transmit powerof the ODU is greater than the presetvalue of TX High Threshold(dBm), thesystem separately records the duration



B-69


TX Low Threshold(dBm)

- - when the value of the actual transmitpower of the ODU is greater than thepreset value of TX High Threshold(dBm) and the duration when the valueof the actual transmit power of the ODUis greater than the preset value of TX LowThreshold(dBm) in the performanceevents.

l If the value of the actual transmit powerof the ODU is greater than the presetvalue of TX Low Threshold(dBm) andis lower than the preset value of TX HighThreshold(dBm), the system records theduration when the value of the actualtransmit power of the ODU is greater thanthe preset value of TX Low Threshold(dBm) in the performance events.

l If the value of the actual transmit powerof the ODU is lower than the preset valueof TX Low Threshold(dBm), the systemdoes not record it.

l TX High Threshold(dBm) and TX LowThreshold(dBm) are valid only when theATPC function is enabled.

RX HighThreshold(dBm)

- - l If the value of the actual receive power ofthe ODU is lower than the preset value ofRX Low Threshold(dBm), the systemrecords the duration when the value of theactual receive power of the ODU is lowerthan the preset value of RX LowThreshold(dBm) and duration when thevalue of the actual transmit power of theODU is lower than the preset value of RXHigh Threshold(dBm)in theperformance events.

l If the value of the actual receive power ofthe ODU is greater than the preset valueof RX Low Threshold(dBm) and islower than the preset value of RX HighThreshold(dBm), the system records theduration when the value of the actualreceive power of the ODU is Lower thanthe preset value of RX High Threshold(dBm) in the performance events.

l If the value of the actual receive power ofthe ODU is greater than the preset value


Configuration Guide


Issue 02 (2009-10-30)


RX Low Threshold(dBm)

- - of RX High Threshold(dBm), thesystem does not record it.

Power to BeReceived(dBm)

- - l This parameter is used to set the expectedreceive power of the ODU and is mainlyused in the antenna alignment stage. Afterthis parameter is set, the NEautomatically enables the antennamisalignment indicating function.



l This parameter needs to be according tothe planning.



B-71



- - l This parameter specifies the maximumtransmit power of the ODU. Thisparameter cannot be set to a value thatexceeds the nominal power rang of theODU in the guaranteed capacitymodulation module.




Range of TXPower(dBm)

- - This parameter indicates the range of thetransmit power of the ODU.

Actual TX Power(dBm)

- - l This parameter indicates the actualtransmit power of the ODU.

l If the ATPC function is enabled, thequeried actual transmit power may bedifferent from the preset value.

Actual RX Power(dBm)

- - This parameter indicates the actual receivepower of the ODU.

TX Status UnmuteMute

Unmute l This parameter indicates or specifies thetransmit status of the ODU.

l When this parameter is set to Mute, thetransmitter of the ODU does not work butcan normally receive microwave signals.

l When this parameter is set to Unmute,the ODU can normally transmit andreceive microwave signals.

l In normal cases, it is recommended thatyou set this parameter to unmute.

Actual TX Status UnmuteMute

- This parameter indicates the actual transmitstatus of the ODU.

Equipment InformationParameter Value Range Default Value Description

Frequency(GHz) - - This parameter indicates the frequency bandwhere the ODU operates.


Configuration Guide


Issue 02 (2009-10-30)


Equipment Type - - l This parameter indicates the equipmenttype of the ODU.

l PDH and SDH indicate the transmissioncapacity only and is irrelevant to the typeof transmitted service.

Station Type - - l This parameter indicates whether theODU is a Tx high station or a Tx lowstation.

l The transmit frequency of a Tx highstation is one T/R spacing higher than thetransmit frequency of a Tx low station.

Produce SN - - This parameter indicates the manufacturingserial number and the manufacturer code ofthe ODU.

TransmissionPower Type

- - This parameter indicates the level of theoutput power of the ODU.

Related TasksA.7.4 Configuring the IF/ODU Information of a Radio Link

B.5 Multiplex Section Protection ParametersThis topic describes the parameters that are related to multiplex section protection (MSP).

B.5.1 Parameter Description: Linear MSP_CreationThis topic describes the parameters that are used for creating linear MSP groups.

B.5.2 Parameter Description: Linear MSPThis topic describes the parameters that are related to linear MSP groups.

B.5.1 Parameter Description: Linear MSP_CreationThis topic describes the parameters that are used for creating linear MSP groups.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear

MS from the Function Tree.2. Click Create.



B-73


Protection Type 1+1 Protection1:N Protection

1+1 Protection l This parameter specifies the protectiontype of the linear MSP group.

l In the case of 1+1 linear MSP, oneworking channel and one protectionchannel are required. When the workingchannel fails, the service is switched fromthe working channel to the protectionchannel.

l In the case of 1:N linear MSP, N workingchannels and one protection channel arerequired. Normal services are transmittedon the working channels and extraservices are transmitted on the protectionchannel. When one working channelfails, the services are switched from thisworking channel to the protectionchannel, and the extra services areinterrupted.

l If extra services need to be transmitted orseveral working channels are required,select 1:N Protection.


Switching Mode Single-EndedSwitchingDual-EndedSwitching

Single-EndedSwitching (1+1Protection)Dual-EndedSwitching (1:NProtection)

l This parameter specifies the switchingmode of the linear MSP.

l In single-ended mode, the switchingoccurs only at one end and the state of theother end remains unchanged.

l In dual-ended mode, the switching occursat both ends at the same time.

l If the linear MSP type is set to 1:NProtection, Switching Mode can be setto Dual-Ended Switching only.


Configuration Guide


Issue 02 (2009-10-30)


Revertive Mode Non-RevertiveRevertive

Non-Revertive (1+1Protection)Revertive (1:NProtection)

l This parameter specifies the revertivemode of the linear MSP.

l When this parameter is set to Revertive,the NE that is in the switching statereleases the switching and enables theformer working channel to return to thenormal state some time after the formerworking channel is restored to normal.

l When this parameter is set to Non-Revertive, the NE that is in the switchingstate keeps the current state unchangedunless another switching occurs eventhough the former working channel isrestored to normal.

l It is recommended that you set thisparameter to Revertive.

l If the linear MSP type is set to 1:NProtection, Revertive Mode can be setto Revertive only.

WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.

l When the time after the former workingchannel is restored to normal reaches thepreset WTR time, a revertive switchingoccurs.

l You can set WTR Time(s) only whenRevertive Mode is set to Revertive.


Protocol Type New ProtocolRestructure Protocol

New Protocol l The new protocol is supported at the earlystage, and the mainstream protocolversion is used currently.

l The restructure protocol optimizes thenew protocol and provides bettermeasures to protect the new protocol,thus ensuring that the new protocol runsin a better manner.

l The new protocol is more mature, and therestructure protocol complies with thestandard. It is recommended that you usethe new protocol.

l You must ensure that the interconnectedNEs run the protocols of the same type.



B-75



Enabled l This parameter indicates or specifieswhether the switching at the SD alarm ofthe linear MSP is enabled.

l When this parameter is set to Enabled,the B2_SD alarm is considered as aswitching condition.



Select MappingMode

West Working UnitWest ProtectionUnit

West Working Unit This parameter specifies the mappingdirection of the linear MSP.

Select MappingMode

- - l This parameter specifies the mappingboard and port in the mapping direction.

l If the protection type is set to 1+1Protection, only one line port can bemapped as West Working Unit.

l Only one line port can be mapped as WestProtection Unit.

l The line port mapped as West ProtectionUnit and the line port mapped as WestWorking Unit should be configured fordifferent boards if possible.

Mapped Board - - This parameter indicates the preset slotmapping relations, including the mappingdirection and the corresponding mappingmode.

Related TasksA.8.1 Configuring Linear MSP

B.5.2 Parameter Description: Linear MSPThis topic describes the parameters that are related to linear MSP groups.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MSfrom the Function Tree.


Configuration Guide


Issue 02 (2009-10-30)


Protection GroupID


Protection Type 1+1 Protection1:N Protection

- l This parameter indicates the protectiontype of the linear MSP group.

l In the case of 1+1 linear MSP, oneworking channel and one protectionchannel are required. When the workingchannel fails, the service is switched fromthe working channel to the protectionchannel.

l In the case of 1:N linear MSP, N workingchannels and one protection channel arerequired. Normal services are transmittedon the working channels and extraservices are transmitted on the protectionchannel. When one working channelfails, the services are switched from thisworking channel to the protectionchannel, and the extra services areinterrupted.

l If extra services need to be transmitted orseveral working channels are required,select 1:N Protection.

Switching Mode Single-EndedSwitchingDual-EndedSwitching

Single-EndedSwitching (1+1Protection)Dual-EndedSwitching (1:NProtection)

l This parameter indicates or specifies theswitching mode of the linear MSP.

l In single-ended mode, the switchingoccurs only at one end and the state of theother end remains unchanged.

l In dual-ended mode, the switching occursat both ends at the same time.

l If the linear MSP type is set to 1:NProtection, Switching Mode can be setto Dual-Ended Switching only.



B-77



Non-Revertive (1+1Protection)Revertive (1:NProtection)

l This parameter indicates or specifies therevertive mode of the linear MSP.

l When this parameter is set to Revertive,the NE that is in the switching statereleases the switching and enables theformer working channel to return to thenormal state some time after the formerworking channel is restored to normal.

l When this parameter is set to Non-Revertive, the NE that is in the switchingstate keeps the current state unchangedunless another switching occurs eventhough the former working channel isrestored to normal.


l If the linear MSP type is set to 1:NProtection, Revertive Mode can be setto Revertive only.

WTR Time(s) 300 to 720 600 l This parameter indicates or specifies theWTR time.





Enabled l This parameter indicates or specifieswhether the reverse switching function isenabled.

l When this parameter is set to Enabled,the B2_SD alarm is considered as aswitching condition.



Configuration Guide


Issue 02 (2009-10-30)


Protocol Type New ProtocolRestructure Protocol

New Protocol l The new protocol is supported at the earlystage, and the mainstream protocolversion is used currently.

l The restructure protocol optimizes thenew protocol and provides bettermeasures to protect the new protocol,thus ensuring that the new protocol runsin a better manner.

l You must ensure that the interconnectedNEs run the protocols of the same type.

l The new protocol is more mature, and therestructure protocol complies with thestandard. It is recommended that you usethe new protocol.

Protocol Status - - This parameter indicates the protocol statusof the linear MSP.


Protection Unit - - This parameter indicates that which of theunits, namely, the west protection unit or thewest working unit, is currently in theprotection status.

West Line --

- This parameter indicates the west protectionunit and the west working unit of the linearMSP.

West SwitchingStatus

- - This parameter indicates the switchingstatus of the line.

Protected Unit - - This parameter indicates the workingchannel protected by the current protectionchannel.

Remote/Local EndIndication

LocalRemote

- When Switching Mode is set to Dual-Ended Switching, the central office endthat issues the switching command isdisplayed.

Related TasksA.8.2 Querying the Status of the Linear MSP



B-79

B.6 SDH/PDH Service ParametersThis topic describes the parameters that are related to SDH/PDH services.

B.6.1 Parameter Description: SDH Service Configuration_CreationThis parameter describes the parameters that are used for creating point-to-point cross-connections.

B.6.2 Parameter Description: SDH Service Configuration_SNCP Service CreationThis topic describes the parameters that are used for creating SNCP services.

B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services IntoSNCP ServicesThis topic describes the parameters that are used for converting normal services into SNCPservices.

B.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services IntoNormal ServicesThis topic describes the parameters that are used for converting SNCP services into normalservices.

B.6.5 Parameter Description: SDH Service ConfigurationThis topic describes the parameters that are used for configuring SDH services (namely,configuring cross-connections).

B.6.6 Parameter Description: SNCP Service ControlThis topic describes the parameters that are used for controlling SNCP services.

B.6.1 Parameter Description: SDH Service Configuration_CreationThis parameter describes the parameters that are used for creating point-to-point cross-connections.

Navigation Pathl Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH

Service Configuration from the Function Tree.l Click Create.


Configuration Guide


Issue 02 (2009-10-30)


Level VC12VC3VC4

VC12 l This parameter specifies the level of theservice to be created.

l If the service is an E1 service or a dataservice that is bound with VC-12channels, set this parameter to VC12.

l If the service is a data service that isbound with VC-3 channels, set thisparameter to VC3.

l If all the services on a VC-4 channel passthrough the NE, set this parameter toVC4.

Direction BidirectionalUnidirectional

Bidirectional l When this parameter is set toUnidirectional, create only the cross-connections from the service source to theservice sink.

l When this parameter is set toBidirectional, create the cross-connections from the service source to theservice sink and the cross-connectionsfrom the service sink to the servicesource.

l In normal cases, it is recommended thatyou set this parameter to Bidirectional.

Source Slot - - This parameter specifies the slot of theservice source.

Source VC4 - - l This parameter specifies the number ofthe VC-4 channel where the servicesource is located.

l This parameter cannot be set whenSource Slot is set to the slot of thetributary board.

Source TimeslotRange(e.g.1,3-6)

- - l This parameter indicates the timeslotrange of the service source.

l This parameter can be set to a number orseveral numbers. When setting thisparameter to several numbers, use thecomma (,) to separate the discretenumbers, or use the endash (-) torepresent a consecutive number. Forexample, the numbers 1, and 3-6 indicate1, 3, 4, 5, and 6.




B-81


Sink Slot - - This parameter specifies the slot of theservice sink.

Sink VC4 - - l This parameter specifies the number ofthe VC-4 channel where the service sinkis located.

l This parameter cannot be set when SinkSlot is set to the slot of the tributary board.

Sink TimeslotRange(e.g.1,3-6)

- - l This parameter specifies the timeslotrange of the service sink.



ActivateImmediately

YesNo

Yes l This parameter specifies whether toimmediately activate the configuredservice.

l To immediately deliver the configuredSDH service to the NE, set this parameterto Yes.

Related TasksA.9.1 Creating the Cross-Connections of Point-to-Point Services

B.6.2 Parameter Description: SDH Service Configuration_SNCPService Creation

This topic describes the parameters that are used for creating SNCP services.

Navigation Pathl Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH

Service Configuration from the Function Tree.l Click Create SNCP Service.


Configuration Guide


Issue 02 (2009-10-30)


Service Type SNCP SNCP This parameter indicates that the type of theservice to be created is SNCP.

Direction BidirectionalUnidirectional

Bidirectional l When this parameter is set toUnidirectional, create only the cross-connections from the SNCP servicesource to the SNCP service sink.

l When this parameter is set toBidirectional, create the cross-connections from the SNCP servicesource to the service sink and the cross-connections from the SNCP service sinkto the service source.

l In normal cases, it is recommended thatyou set this parameter to Bidirectional.

Level VC12VC3VC4

VC12 l This parameter specifies the level of theSCNP service to be created.




Hold-off Time(100ms)

0 to 100 0 l This parameter specifies the duration ofthe hold-off time.

l When a line is faulty, SNCP switchingcan be performed on the NE after a delayof time to prevent the situation where theNE performs SNCP switching and otherprotection switching at the same time.

l If multiple link-based protectionschemes, such as SNCP, 1+1 protection,and N+1 protection, are available at thesame time, the hold-off time needs to beset to a duration that is longer than theswitching duration for the multiple link-based protection schemes.

l If only the SNCP scheme is available, itis recommended that you set the hold-offtime to 0.



B-83



Non-Revertive l This parameter specifies whether toswitch the service to the original workingchannel after the fault is rectified.

l If this parameter is set to Revertive, theservice is switched from the protectionchannel to the original working channel.If this parameter is set to Non-Revertive, the service is not switchedfrom the protection channel to theoriginal working channel.















Configuration Guide


Issue 02 (2009-10-30)








Configure SNCPTangent Ring

SelectedDeselected

Deselected l After the Configure SNCP TangentRing checkbox is selected, you canquickly configure the SNCP service forthe SNCP ring tangent point.

l In normal cases, it is recommended thatyou do not select this checkbox.

ActivateImmediately

SelectedDeselected

Selected l This parameter specifies whether toimmediately activate the configuredSNCP service.

l After the Activate Immediatelycheckbox is selected, you canimmediately activate the created SNCPservice.

Related TasksA.9.2 Creating Cross-Connections of SNCP Services

B.6.3 Parameter Description: SDH ServiceConfiguration_Converting Normal Services Into SNCP Services

This topic describes the parameters that are used for converting normal services into SNCPservices.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH

Service Configuration from the Function Tree.



B-85

2. In Cross-Connection, select the configured SDH service. Right-click and choose Expandto Unidirectional from the shortcut menu.

3. Select the expanded unidirectional service. Right-click and choose Convert to SNCPService from the shortcut menu.


Service Type SNCP SNCP This parameter indicates that the type of theservice to be created is SNCP.

Direction Unidirectional Unidirectional This parameter indicates the direction of theSNCP service.

Level VC12VC3VC4

VC12 l This parameter indicates the level of theSNCP service.










Configuration Guide


Issue 02 (2009-10-30)



Non-Revertive l This parameter specifies whether toswitch the service to the original workingchannel after the fault is rectified. If thisparameter is set to "Revertive", theservice is switched from the protectionchannel to the original working channel.
















B-87










SelectedDeselected



ActivateImmediately

SelectedDeselected


l After the Activate Immediatelycheckbox is selected, you canimmediately activate the created SNCPservice.

Related TasksA.9.5 Converting a Normal Service into an SNCP Service

B.6.4 Parameter Description: SDH ServiceConfiguration_Converting SNCP Services Into Normal Services

This topic describes the parameters that are used for converting SNCP services into normalservices.


Configuration Guide


Issue 02 (2009-10-30)

Navigation Path1. Select the corresponding board from the Object Tree in the NE Explorer. Choose

Configuration > SDH Service Configuration from the Function Tree.2. In Auto-Created Cross-Connection, select the configured service. Right-click and choose

Convert to Non-Protection Service from the shortcut menu.


Service Type SNCP SNCP l This parameter specifies the SNCPservice to be created.




Direction Unidirecitonal Unidirecitonal This parameter indicates the direction of theSNCP service.

Level VC12VC3VC4

VC12 l This parameter indicates the level of theSNCP service.






B-89







Revertive Mode RevertiveNon-Revertive

Non-Revertive l This parameter specifies whether toswitch the service to the original workingchannel after the fault is rectified. If thisparameter is set to "Revertive", theservice is switched from the protectionchannel to the original working channel.



WTR Time(ms) - - l This parameter specifies the WTR time.


l WTR Time(ms) can be set only whenRevertive Mode is set to Revertive.


Source Slot - - This parameter specifies the slot of theservice sink.


Configuration Guide


Issue 02 (2009-10-30)
















SelectedDeselected





B-91


ActivateImmediately

SelectedDeselected


l After the Activate Immediatelycheckbox is selected, the SNCP service isactivated immediately.

Related TasksA.9.6 Converting an SNCP Service to a Normal Service

B.6.5 Parameter Description: SDH Service ConfigurationThis topic describes the parameters that are used for configuring SDH services (namely,configuring cross-connections).

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH ServiceConfiguration from the Function Tree.

Cross-Connection ParametersParameter Value Range Default Value Description

Level VC12VC3VC4

- l This parameter indicates the level of theservice.

l If the service is an E1 service or a dataservice that is bound with VC-12channels, VC12 is displayed.

l If the service is a data service that isbound with VC-3 channels, VC3 isdisplayed.

l If all the services on a VC-4 channel passthrough the NE, VC4 is displayed.

Source Slot - - This parameter indicates the slot of theservice source.

Source Timeslot/Path

- - This parameter indicates the timeslot ortimeslot range of the service source.

Sink Slot - - This parameter indicates the slot of thesource sink.

Sink Timeslot/Path

- - This parameter indicates the timeslot ortimeslot range of the service sink.


Configuration Guide


Issue 02 (2009-10-30)


Activation Status YesNo

- This parameter indicates whether to activatethe service.

Bound GroupNumber


Lockout Status - - The OptiX RTN 910 does not support thisparameter.

Trail Name - - The OptiX RTN 910 does not support thisparameter.

Schedule No. - - The OptiX RTN 910 does not support thisparameter.

Parameters for Automatically Generated Cross-ConnectionsParameter Value Range Default Value Description

Level VC12VC3VC4





Source Slot - - This parameter indicates the slot of theservice source.

Source Timeslot/Path

- - This parameter indicates the timeslot ortimeslot range of the service source.

Sink Slot - - This parameter indicates the slot of thesource sink.

Sink Timeslot/Path

- - This parameter indicates the timeslot ortimeslot range of the service sink.

Lockout Status - - The OptiX RTN 910 does not support thisparameter.

Trail Name - - The OptiX RTN 910 does not support thisparameter.

Schedule No. - - The OptiX RTN 910 does not support thisparameter.



B-93

Related TasksA.9.7 Querying TDM Services

B.6.6 Parameter Description: SNCP Service ControlThis topic describes the parameters that are used for controlling SNCP services.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP ServiceControl from the Function Tree.


Service Type SNCP - This parameter indicates the serviceprotection type of the protection group.

Source - - This parameter indicates the timeslots wherethe working service source and protectionservice source of the protection group arelocated.

Sink - - This parameter indicates the timeslots wherethe working service sink and protectionservice sink of the protection group arelocated.

Level VC12VC3VC4





Current Status - - This parameter indicates the currentswitching mode and switching status of theservices of the protection group.


Configuration Guide


Issue 02 (2009-10-30)



- l This parameter indicates or specifies therevertive mode of the service.

l This parameter determines whether toswitch the service from the protectionchannel to the original working channelafter the fault is rectified.



WTR Time(s) 300 to 720 - l This parameter indicates or specifies theWTR time.





0 to 100 - l This parameter indicates or specifies theduration of the hold-off time.






B-95


InitiationCondition

TIMEXCSDUNEQ

NULL l This parameter indicates or specifies theconditions that trigger the protectionswitching of the service.

l If TIM is selected, the SNCP serviceconsiders the HP_TIM or LP_TIM alarmas an automatic switching condition.

l If EXC is selected, the SNCP serviceconsiders the B3_EXC or BIP_EXCalarm as an automatic switchingcondition.

l If SD is selected, the SNCP serviceconsiders the B3_SD or BIP_SD alarm asan automatic switching condition.

l If UNEQ is selected, the SNCP serviceconsiders the HP_UNEQ or LP_UNEQalarm as an automatic switchingcondition.

l It is recommended that you set InitiationCondition to the same condition forWorking Service and ProtectionService.

l The protection switching conditions inInitiation Condition are optional valuesnot included in the default values, andthey are set according to the planninginformation.

Trail Status - - This parameter indicates the status of theworking service and protection service ofthe protection group.

Service Grouping - - The OptiX RTN 910 does not support thisparameter.

Group Type - - The OptiX RTN 910 does not support thisparameter.

Active Channel - - This parameter indicates whether theworking service or protection service iscurrently received by the protection group.

Related TasksA.9.3 Configuring the Automatic Switching of SNCP ServicesA.9.9 Querying the Protection Status of SNCP Services


Configuration Guide


Issue 02 (2009-10-30)

B.7 Clock ParametersThis topic describes the parameters that are related to clocks.

B.7.1 Parameter Description: Clock Source Priority TableThis topic describes the parameters that are related to the priority table of a clock source.

B.7.2 Parameter Description: Clock Subnet Setting_Clock SubnetThis topic describes the parameters that are related to a clock subnet.

B.7.3 Parameter Description: Clock Subnet Setting_Clock QualityThis topic describes the parameters that are related clock quality.

B.7.4 Parameter Description: Clock Subset Setting_SSM Output ControlThis topic describes the parameters that are related to SSM output control.

B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling StatusThis topic describes the parameters that are used for enabling the clock ID function.

B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration ParametersThis topic describes the parameters that are related to clock source restoration.

B.7.7 Parameter Description: Clock Source Switching_Clock Source SwitchingThis topic describes the parameters that are related to the switching conditions of a clock source.

B.7.8 Parameter Description: Output Phase-Locked Source of the External Clock SourceThis topic describes the parameters of the output phase-locked source of the external clocksource.

B.7.9 Parameter Description: Clock Synchronization StatusThis topic describes the parameters that are related to the clock synchronization status.

B.7.1 Parameter Description: Clock Source Priority TableThis topic describes the parameters that are related to the priority table of a clock source.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >

Clock Source Priority.2. Click the System Clock Source Priority List tab.



B-97


Clock Source - - l External clock source 1indicates the externalclock source at theCLK or TIME port onthe CSTA, CSHA,CSHB, or CSHC boardin physical slot 1.

l The internal clocksource is always at thelowest priority andindicates that the NEworks in the free-runmode.

l The clock sources andthe correspondingclock source prioritylevels are determinedaccording to the clocksynchronizationschemes.

External Clock SourceMode

2Mbit/s2MHz

2Mbit/s l This parameterindicates the type of theexternal clock sourcesignal.

l This parameter is setaccording to theexternal clock signal.In normal cases, theexternal clock signal isa 2 Mbit/s signal.


Configuration Guide


Issue 02 (2009-10-30)


Synchronous Status Byte SA4 to SA8 SA4 l This parameter is validonly when ExternalClock Source Mode isset to 2Mbit/s.

l This parameterindicates which bit ofthe TS0 in odd framesof the external clocksignal is used totransmit the SSM.

l This parameter needs tobe set only when theSSM or extended SSMis enabled. In normalcases, the externalclock sources use theSA4 to transmit theSSM.

Clock Source PrioritySequence (1 is thehighest)

- - Displays the prioritysequence of clock sources.1 indicates the highestclock source priority.

Related TasksA.10.1 Configuring the Clock Sources

B.7.2 Parameter Description: Clock Subnet Setting_Clock SubnetThis topic describes the parameters that are related to a clock subnet.


Clock Subnet Configuration.2. Click the Clock Subnet tab.



B-99

Parameters for Setting a Clock SubnetParameter Value Range Default Value Description

Affiliated Subnet 0 to 255 0 l This parameter is usedwhen the clock subnetneeds to be created onthe NMS.

l The NEs that trace thesame clock sourceshould be allocatedwith the same clocksubnet ID.


Configuration Guide


Issue 02 (2009-10-30)


Protection Status Start Extended SSMProtocolStart Standard SSMProtocolStop SSM Protocol

Stop SSM Protocol l The SSM protocol is ascheme used forsynchronousmanagement on anSDH network andindicates that the SSMis passed by the lowerfour bits of the S1 byteand can be exchangedbetween the nodes. TheSSM protocol ensuresthat the equipmentautomatically selectsthe clock source of thehighest quality andhighest priority, thuspreventing mutualclock tracing.

l After the standard SSMprotocol is started, theNE first performs theprotection switching onthe clock sourceaccording to the clockquality levelinformation providedby the S1 byte. If thequality level of theclock source is thesame, the NE thenperforms the protectionswitching according tothe clock priority table.That is, the NE selectsan unlocked clocksource that is of thehighest quality andhighest priority from allthe current availableclock sources as theclock source to besynchronized andtraced by the localstation.

l If the SSM protocol isstopped, it indicatesthat the S1 byte is notused. The NE selectsand switches a clock



B-101


source only accordingto the sequencespecified in the prioritytable. The clock sourceof the highest priority isused as the clock sourceto be traced.

l After the SSM protocolis stopped, each NEperforms the protectionswitching on the clockaccording to the presetpriority table of theclock source only whenthe clock source of ahigher priority is lost.

Clock Source - - This parameter indicatesthe clock source that isconfigured for an NE. InClock Source Priority,you can set whether to addor delete a clock source.


Configuration Guide


Issue 02 (2009-10-30)


Clock Source ID (None)1 to 15

(None) l This parameter is validonly when the extendedSSM protocol isstarted.

l Clock source IDs areallocated for thefollowing clocksources only:– External clock

source– Internal clock source

of the node thataccesses the externalclock sources

– Internal clock sourceof the joint node of aring and a chain orthe joint node of tworings

– Line clock sourcethat enters the ringwhen the intra-ringline clock source isconfigured at thejoint node of a ringand a chain or thejoint node of tworings

Related TasksA.10.2 Configuring Clock Subnets

B.7.3 Parameter Description: Clock Subnet Setting_Clock QualityThis topic describes the parameters that are related clock quality.


Clock Subnet Configuration.2. Click the Clock Quality tab.



B-103

Parameters for Clock Source QualityParameter Value Range Default Value Description

Clock Source - - This parameter indicatesthe name of theconfigured clock source.In Clock SourcePriority, you can setwhether to add or delete aclock source.

Configuration Quality UnknownSynchronization QualityG.811 Clock SignalG.812 Transit ClockSignalG.812 Local Clock SignalG.813 SDH EquipmentTiming Source (SETS)SignalDo Not Use ForSynchronizationAutomatic Extraction

Automatic Extraction This parameter specifiesthe quality level that isconfigured for the clocksource. This function isrequired only in a specialscenario or in a test.Generally, this parameterneed not be set.

Clock Quality - - This parameter indicatesthe clock source qualitysignal received by the NE.The NE extracts the clocksource quality signal fromthe S1 byte of each clocksource.

Parameters for Manual Setting of 0 Quality LevelParameter Value Range Default Value Description



Configuration Guide


Issue 02 (2009-10-30)


Manual Setting of 0Quality Level

Do Not Use ForSynchronizationG.811 Reference ClockBetween G.811 ReferenceClock and G.812 TransitClockG.812 Transit ClockBetween G.812 TransitClock and G.812 LocalClockG.812 Local ClockBetween G.812 LocalClock and synchronousequipment timing source(SETS)SETS ClockBetween synchronousequipment timing source(SETS) and qualityunavailable

Do Not Use ForSynchronization

This parameter specifiesthe clock quality whoselevel is manually set tozero.l Do Not Use For

Synchronization: thenotificationinformation in thereverse direction of theselectedsynchronization clocksource to avoid directmutual locking ofadjacent NEs.

l G.811 ReferenceClock: the clock signalspecified in ITU-T G.811.

l Between G.811Reference Clock andG.812 Transit Clock:lower than the qualitylevel of the clock signalspecified in ITU-T G.811 but higher than thequality level of thetransit exchange clocksignal specified in ITU-T G.812.

l G.812 Transit Clock:the transit exchangeclock signal specifiedin ITU-T G.812.

l Between G.812 TransitClock and G.812 LocalClock: lower than thequality level of thetransit exchange clocksignal specified in ITU-T G.812 but higher thanthe quality level of thelocal exchange clocksignal specified in ITU-T G.812.

l G.812 Local Clock: thelocal exchange clocksignal specified in ITU-T G.812.



B-105


l Between G.812 LocalClock and synchronousequipment timingsource (SETS): lowerthan the quality level ofthe local exchangeclock signal specifiedin ITU-T G.812 buthigher than the qualitylevel of the clock signalof the SETS.

l SETS Clock: the clocksignal of the SETS.

l Between synchronousequipment timingsource (SETS) andquality unavailable:lower than the qualitylevel of the clock signalof the SETS but higherthan the quality levelunavailable in thesynchronous timingsource.

Related TasksA.10.3 Self-Defined Clock Quality

B.7.4 Parameter Description: Clock Subset Setting_SSM OutputControl

This topic describes the parameters that are related to SSM output control.


Clock Subnet Configuration.2. Click the SSM Output Control tab.


Configuration Guide


Issue 02 (2009-10-30)

Parameters


Line Port - - l This parameterindicates the name ofthe line clock port.

l Line Port: indicatesthe SSM qualityinformation output portof the current availableline clock source andthe external clocksource. This output portcan transmit the qualityinformation of theclock source byoutputting the S1 byteto the downstream NE.

Control Status EnabledDisabled

Enabled l This parameter is validonly when the SSMprotocol or theextended SSM protocolis started.

l This parameterindicates whether theSSM is output at theline port.

l When the line port isconnected to an NE inthe same clock subnet,set this parameter toEnabled. Otherwise,set this parameter toDisabled.

Related TasksA.10.4 Configuring the SSM Output Status

B.7.5 Parameter Description: Clock Subset Setting_Clock IDEnabling Status

This topic describes the parameters that are used for enabling the clock ID function.


Clock Subnet Configuration.



B-107

2. Click the Clock ID Status tab.


Line Port - - l This parameterindicates the name ofthe line clock port.

l Line Port: indicatesthe SSM qualityinformation output portof the current availableline clock source andthe external clocksource. This output portcan transmit the qualityinformation of theclock source byoutputting the S1 byteto the downstream NE.

Enabled Status EnabledDisabled

Enabled l This parameter is validonly when the extendedSSM protocol isstarted.

l This parameterindicates whether theclock source ID isoutput at the line port.

l If the line ports areconnected to the NEs inthe same clock subnetand if the extendedSSM protocol is startedon the opposite NE, thisparameter is set toEnabled. Otherwise,this parameter is set toDisabled.

Related TasksA.10.5 Configuring the Clock ID Output Status

B.7.6 Parameter Description: Clock Source Switching_Clock SourceRestoration Parameters

This topic describes the parameters that are related to clock source restoration.


Configuration Guide


Issue 02 (2009-10-30)


Clock Source Switching.2. Click the Clock Source Reversion Parameter tab.



Higher Priority ClockSource Reversion Mode

Auto-RevertiveNon-Revertive

Auto-Revertive l When the quality of ahigher-priority clocksource degrades, theNE automaticallyswitches the clocksource to a lower-priority clock source. Ifthis parameter is set toAuto-Revertive, theNE automaticallyswitches the clocksource to the higher-priority clock sourcewhen this higher-priority clock sourcerestores. If thisparameter is set to Non-Revertive, the NE doesnot automaticallyswitch the clock sourceto the higher-priorityclock source when thishigher-priority clocksource restores.

l Correct setting ofClock SourceSwitching Conditionensures the reliabilityof the clock sourceswitching. To improvethe clock quality, selectAuto-Revertive.Otherwise, to preventjitter of the clock,generally, it isrecommended that youset this parameter toNon-Revertive.



B-109


Clock Source WTRTime(min.)

0 to 12 5 l This parameterspecifies the durationfrom the time when theclock sourcerestoration is detectedto the time when theclock source switchingis triggered. Thisparameter is used toavoid frequentswitching of the clocksource due tounstability of the clocksource state within ashort time.

l This parameter is validonly when HigherPriority Clock SourceReversion Mode is setto Auto-Revertive.

Related TasksA.10.8 Modifying the Recovery Parameter of the Clock Source

B.7.7 Parameter Description: Clock Source Switching_Clock SourceSwitching

This topic describes the parameters that are related to the switching conditions of a clock source.


Clock Source Switching.

2. Click the Clock Source Switching tab.

Parameters


Clock Source - - This parameter indicatesthe name of the clocksource.

Effective Status ValidInvalid

- This parameter indicateswhether the clock sourceis valid.


Configuration Guide


Issue 02 (2009-10-30)


Lock Status LockUnlock

- l This parameterspecifies the lockingstatus of the clocksource in the prioritytable.

l Lock: A clock source inthe priority table is inthe locked state. Theclock source in thelocked state cannot beswitched.

l Unlock: A clock sourcein the priority table is inthe unlocked state. Theclock source in theunlocked state can beswitched.

Switching Source - - This parameter indicatesthe clock source to betraced by the NE after theswitching.

Switching Status NormalManual SwitchingForced Switching

- This parameter indicatesthe switching status of thecurrent clock source.

Related TasksA.10.7 Changing the Conditions for Clock Source Switching

B.7.8 Parameter Description: Output Phase-Locked Source of theExternal Clock Source

This topic describes the parameters of the output phase-locked source of the external clocksource.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >Phase-Locked Source Output by External Clock.



B-111


2M Phase-LockedSource Number

External Clock Source 1 - This parameter indicatesthe number of the externalclock source output of theNE.

External Clock OutputMode

2Mbit/s2MHz

2Mbit/s l This parameterspecifies the mode ofthe output clock.

l This parameter needs tobe set according to therequirements of theinterconnectedequipment. Generally,the output externalclock signal is a 2 Mbit/s signal.

External Clock OutputTimeslot

SA4 to SA8ALL

ALL l This parameter is validonly when ExternalClock Output Mode isset to 2Mbit/s.

l This parameterindicates which bit ofthe TS0 in odd framesof the output clocksignal is used totransmit the SSM.

l If this parameter is setto ALL, it indicatesthat all the bits of theTS0 are used totransmit the SSM.



Configuration Guide


Issue 02 (2009-10-30)


External Source OutputThreshold

Threshold DisabledNot Inferior to G.813SETS SignalNot Inferior to G.812Local SignalNot Inferior to G.812Transit Clock SignalNot Inferior to G.811Clock Signal

Threshold Disabled l This parameterspecifies the lowestquality of the outputclock. If the clockquality is lower than thevalue of this parameter,it indicates that theexternal clock sourcedoes not output anyclock signal.

l If this parameter is setto ThresholdDisabled, it indicatesthat the external clocksource always outputsthe clock signal.


2M Phase-LockedSource Fail Condition

No Failure ConditionAISLOFAIS OR LOF

No Failure Condition l This parameterspecifies the failurecondition of the 2 Mbit/s phase-locked clocksource.


2M Phase-LockedSource Fail Action

Shut Down Output2M Output S1 ByteUnavailableSend AIS

Shut Down Output l This parameter is validonly when 2M Phase-Locked Source FailCondition is not set toNo Failure Condition.

l This parameterspecifies the operationof the 2 Mbit/s phase-locked loop (PLL)when the 2 Mbit/sphase-locked clocksource meets the failureconditions.


Related TasksA.10.6 Modifying the Parameters of the Clock Output



B-113

B.7.9 Parameter Description: Clock Synchronization StatusThis topic describes the parameters that are related to the clock synchronization status.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > ClockSynchronization Status.



NE Clock WorkingMode

- - This parameter indicatesthe working mode of theNE clock.

S1 Byte SynchronizationQuality Information

- - This parameter indicatesthe synchronizationquality information of theS1 byte.

S1 Byte SynchronousSource

- - This parameter indicatesthe clock synchronizationsource of the S1 byte.

Synchronous Source - - This parameter indicatesthe synchronizationsource.


Configuration Guide


Issue 02 (2009-10-30)


Data Output Method inHoldover Mode

Normal Data OutputModeKeep the Latest Data

Normal Data OutputMode

l When all the referencetiming signals are lost,the slave clock changesto the holdover mode.At this time, the slaveclock works based onthe latest frequencyinformation storedbefore the referencetiming signals are lost.Then, the frequency ofthe oscillator driftsslowly to ensure thatthe offset between thefrequency of the slaveclock and the referencefrequency is verysmall. As a result, theimpact caused by thedrift is limited withinthe specifiedrequirement.

l Normal Data OutputMode: The slave clockworks based on thelatest frequencyinformation storedbefore the referencetiming signals are lost,and the holdoverduration depends on thesize of the phase-locked clock register onthe equipment. Theholdover duration canbe up to 24 hours.

l Keep the Latest Data:The slave clock worksin holdover mode allthe time based on thelatest frequencyinformation storedbefore the referencetiming signals are lost.

Related TasksA.10.9 Querying the Clock Synchronization Status



B-115

B.8 Parameters for Ethernet ServicesThis topic describes the parameters that are related to Ethernet services.

B.8.1 Parameter Description: E-Line Service_CreationThis topic describes the interface parameters that are used for creating an Ethernet line (E-Line)service.

B.8.2 Parameter Description: E-Line ServiceThis topic describes the parameters that are related to E-Line services.

B.8.3 Parameter Description: VLAN Forwarding Table Item_CreationThis topic describes the parameters that are used for creating VLAN forwarding table items.

B.8.4 Parameter Description: E-LAN Service_CreationThis topic describes the parameters that are used for creating an Ethernet local area network (E-LAN) service.

B.8.5 Parameter Description: E-LAN ServiceThis topic describes the parameters that are related to E-LAN services.

B.8.6 Parameter Description: QinQ Link_CreationThis topic describes the parameters that are used for creating a QinQ link.

B.8.1 Parameter Description: E-Line Service_CreationThis topic describes the interface parameters that are used for creating an Ethernet line (E-Line)service.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet

Service Management > E-Line Service from the Function Tree.

2. Click New. The New E-Line Service dialog box is displayed.

Parameters on the Main Interface


Service ID 1 to 4294967294 - This parameter specifiesthe ID of the E-Lineservice.

Service Name - - This parameter specifiesthe name of the E-Lineservice.


Configuration Guide


Issue 02 (2009-10-30)


Direction UNI-UNIUNI-NNINNI-NNI

UNI-UNI l This parameterspecifies the directionof the E-Line service.


BPDU Not TransparentlyTransmittedTransparentlyTransmitted


l This parameterspecifies thetransparenttransmission ID of thebridge protocol dataunit (BPDU) packets. Itis used to indicatewhether the E-Lineservice transparentlytransmits the BPDUpackets.

l If the BPDU packetsare used as the servicepackets andtransparentlytransmitted to theopposite end, set thisparameter toTransparentlyTransmitted.

l In other cases, set thisparameter to NotTransparentlyTransmitted.


MTU(byte) - - The OptiX RTN 910 doesnot support thisparameter.

Service Tag Role - - The OptiX RTN 910 doesnot support thisparameter.



B-117


Source Port - - l This parameterspecifies the port of theservice source.

l This parameter is validonly when Direction isset to UNI-UNI orUNI-NNI.

l Before setting thisparameter, check andensure that theattributes in EthernetInterface of the portare set correctly and arethe same as theplanning information.

l The value of thisparameter cannot be thesame as the value ofSink Port.

l The value of thisparameter cannot beused for the E-LANport.



Configuration Guide


Issue 02 (2009-10-30)


Source VLANs 1 to 4094 - l This parameter can beset to null, a number, orseveral numbers. Whensetting this parameterto several numbers, usethe comma (,) toseparate the discretenumbers, or use theendash (-) to representa consecutive number.For example, thenumbers 1, and 3-6indicate 1, 3, 4, 5, and6.

l This parameter is validonly when Direction isset to UNI-UNI orUNI-NNI.

l The number of VLANsmust be the same valueof Sink VLANs.

l If this parameter is setto null, all the servicesat the source port areused as the servicesource.

l If this parameter is notset to null, only theservice that containsthe VLAN ID at thesource port can be usedas the service source.

Bearer Type QinQ Link QinQ Link l Uses the QinQ link tocarry the E-Lineservice.

l This parameter is validonly when Direction isset to UNI-NNI.

QinQ Link ID - - l Selects the QinQ linkID.

l A QinQ link ID ispreset in QinQ Link.

l This parameter is validonly when Direction isset to UNI-NNI.



B-119


Bearer Type 1 QinQ Link QinQ Link l Uses the QinQ link tocarry the E-Lineservice.

l This parameter is validonly when Direction isset to NNI-NNI.

QinQ Link ID 1 - - l Selects the QinQ linkID of the first QinQlink.


l The QinQ link ID ispreset in QinQ Link.

Bearer Type 2 QinQ Link QinQ Link l Uses the QinQ link tocarry the E-Lineservice.


QinQ Link ID 2 - - l Selects the QinQ linkID of the second QinQlink.


l The QinQ link ID ispreset in QinQ Link.


Configuration Guide


Issue 02 (2009-10-30)


Sink Port - - l This parameterspecifies the port of theservice sink.

l Before setting thisparameter, check andensure that theattributes in EthernetInterface of the portare set correctly and arethe same as theplanning information.

l The value of thisparameter cannot be thesame as the value ofSource Port.

l The value of thisparameter cannot beused for the E-LANport.




B-121


Sink VLANs 1 to 4094 - l This parameter can beset to null, a number, orseveral numbers. Whensetting this parameterto several numbers, usethe comma (,) toseparate the discretenumbers, or use theendash (-) to representa consecutive number.For example, thenumbers 1, and 3-6indicate 1, 3, 4, 5, and6.

l The number of VLANsmust be the same valueof Source VLANs.

l If this parameter is setto null, all the servicesat the sink port are usedas the service sink.

l If this parameter is notset to null, only theservice that containsthe VLAN ID at thesink port can be used asthe service sink.

Related TasksA.26.2 Configuring the E-Line Service

B.8.2 Parameter Description: E-Line ServiceThis topic describes the parameters that are related to E-Line services.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > E-Line Service from the Function Tree.


Service ID 1 to 4294967294 - This parameter indicatesthe ID of the E-Lineservice.


Configuration Guide


Issue 02 (2009-10-30)


Service Name - - This parameter indicatesor specifies the name ofthe E-Line service.

Source Node - - This parameter indicatesthe source node.

Sink Node - - This parameter indicatesthe sink node.


MTU(byte) 1518 to 9600 - The OptiX RTN 910 doesnot support thisparameter.

BPDU Not TransparentlyTransmittedTransparentlyTransmitted

- l This parameterindicates thetransparenttransmission tag of thebridge protocol dataunit (BPDU) packets.This parameter is usedto indicate whether theEthernet linetransparently transmitsthe BPDU packets.

l If the BPDU packetsare used as the servicepackets andtransparentlytransmitted to theopposite end, set thisparameter toTransparentlyTransmitted.

l If the BPDU packetsare used as the protocolpackets to compute thespanning tree topologyof the network, set thisparameter to NotTransparentlyTransmitted.

Active ActiveInactive

- This parameter indicateswhether E-Line service isactive.



B-123

Parameters for the User Network Interface (UNI)Parameter Value Range Default Value Description

Port - - This parameter indicatesthe UNI port.

VLANs 1 to 4094 - This parameter indicatesor specifies the VLAN IDof the UNI port.l This parameter can be

set to null, a number, orseveral numbers. Whensetting this parameterto several numbers, usethe comma (,) toseparate the discretenumbers, or use theendash (-) to representa consecutive number.For example, thenumbers 1, and 3-6indicate 1, 3, 4, 5, and6.

l This parameter is validonly when Direction isset to UNI-UNI orUNI-NNI in theprocess of creating anE-Line service.

l If this parameter is setto null, all the servicesof the UNI work as theservice source orservice sink.

l If this parameter is notset to null, only theservices of the UNI portwhose VLAN IDs areincluded in the setvalue of this parameterwork as the servicesource or service sink.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for the Network Node Interface (NNI)Parameter Value Range Default Value Description

QinQ Link ID 1 to 4294967295 - l This parameterindicates the QinQ linkID of the QinQ linkconnected to the NNIport.


Port - - l This parameterindicates the NNI port.


S-VLAN ID - - l This parameterindicates or specifiesthe VLAN ID of theNNI port.

l This parameter is validonly when Direction isset to UNI-NNI orNNI-NNI in theprocess of creating anE-Line service.

l This parameter is presetin QinQ Link.

Parameters for the Port AttributesParameter Value Range Default Value Description

Port - - This parameter indicatesthe QinQ link ID of theQinQ link connected tothe port.



B-125


Enable Port - - l This parameterindicates whether toenable the port.

l This parameter is presetin General Attributesof Ethernet Interface.

Encapsulation Type Null802.1QQinQ

- l This parameterindicates theencapsulation type ofthe port.


l If this parameter is setto Null, the porttransparently transmitsthe received packets.

l If this parameter is setto 802.1Q, the portidentifies the packetsthat comply with theIEEE 802.1Q standard.

l If this parameter is setto QinQ, the portidentifies the packetsthat comply with theIEEE 802.1 QinQstandard.

l This parameter is presetin General Attributesof Ethernet Interface.

TAG Tag AwareAccessHybrid

l This parameterindicates the tag of theport.

l This parameter is presetin Layer 2 Attributesof EthernetInterface .


Configuration Guide


Issue 02 (2009-10-30)

B.8.3 Parameter Description: VLAN Forwarding TableItem_Creation

This topic describes the parameters that are used for creating VLAN forwarding table items.


Service Management > E-Line Service from the Function Tree.2. Click the VLAN Forwarding Table Item tab.3. Click New.

Parameters for VLAN Forwarding Table ItemParameter Value Range Default Value Description

Source Interface Type V-UNI V-UNI This parameter specifiesthe network attribute ofthe source interface.

Source Interface - - This parameter specifiesthe source interface.

Source VLAN ID 1 to 4094 - This parameter specifiesthe VLAN ID of thesource service.

Sink Interface Type V-UNI V-UNI This parameter specifiesthe network attribute ofthe sink interface.

Sink Interface - - This parameter specifiesthe sink interface.

Sink VLAN ID 1 to 4094 - This parameter specifiesthe VLAN ID of the sinkservice.

NOTE

l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item iscreated. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified inSink VLAN ID when the service is transmitted from Sink Interface.

l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted fromSource VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when theother VLAN forwarding table item is configured reversely.

l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion ofVLAN IDs.

Related TasksA.26.3 Creating a VLAN Forwarding Table Item



B-127

B.8.4 Parameter Description: E-LAN Service_CreationThis topic describes the parameters that are used for creating an Ethernet local area network (E-LAN) service.


Service Management > E-LAN Service from the Function Tree.2. Click New. The New E-LAN Service dialog box is displayed.


Service ID 1 to 4294967294 - l This parameterspecifies the ID of theE-LAN service.

l The OptiX RTN 910supports simultaneouscreation of an E-LANservice only.

Service Name - - This parameter specifiesthe name of the E-LANservice.

BPDU - - l This parameterindicates thetransparenttransmission tag of theBPDU packets.

l In the case of an E-LAN service, thisparameter supportsonly transparenttransmission of theBPDU packets andcannot be set manually.

l Not TransparentlyTransmitted indicatesthat the BPDU packetsare used as the protocolpackets to compute thespanning tree topologyof the network.


Configuration Guide


Issue 02 (2009-10-30)


Tag Type C-AwaredS-AwaredTag-Transparent

C-Awared l C-Awared indicatesthat the packets arelearnt according to C-Tag (the VLAN tag onthe client-side). Tocreate the 802.1qbridge, set thisparameter to C-Awared.

l S-Awared indicatesthat the packets arelearnt according to S-Tag (the VLAN tag atthe carrier servicelayer). To create the802.1ad bridge, set thisparameter to S-Awared.

l Tag-Transparentindicates that only theEthernet packets thatdo not contain VLANtags are accessed. Tocreate the 802.1dbridge, set thisparameter to Tag-Transparent.


Self-Learning MACAddress

Enabled Enabled l This parameterspecifies whether toenable the MACaddress self-learningfunction.

l If the MAC self-learning function of anEthernet LAN isenabled, the EthernetLAN learns an MACaddress according tothe original MACaddress in the packetand automaticallyrefreshes the MACaddress forwardingtable.



B-129


MAC Address LearningMode

- - l This parameterindicates the mode usedto learn an MACaddress.

l When the bridge usesthe SVL mode, all theVLANs share oneMAC address table. Ifthe bridge uses the IVLmode, each VLAN hasan MAC address table.



Parameters for UNIsParameter Value Range Default Value Description


SVLAN 1 to 4094 - l This parameterspecifies the S-VLANID of the UNI port.

l This parameter is validonly when Tag Type isset to S-Awared.



Configuration Guide


Issue 02 (2009-10-30)


VLANs/CVLAN 1 to 4094 - l This parameterspecifies the VLAN IDof the UNI port.

l This parameter can beset to null, a number, orseveral numbers. Whensetting this parameterto several numbers, usethe comma (,) toseparate the discretenumbers, or use theendash (-) to representa consecutive number.For example, thenumbers 1, and 3-6indicate 1, 3, 4, 5, and6.

l If this parameter is setto null, all the servicesof the UNI work as theservice source orservice sink.

l If this parameter is notset to null, only theservices of the UNI portwhose VLAN IDs areincluded in the setvalue of this parameterwork as the servicesource or service sink.

Parameters of NNIsParameter Value Range Default Value Description



SVLANs - - l This parameterspecifies the S-VLANID of the NNI port.




B-131

Parameters for the Split Horizon GroupParameter Value Range Default Value Description

Split Horizon Group ID - 1 l This parameterindicates the ID of thesplit horizon group.

l The default splithorizon group ID is 1and cannot be setmanually.

Split Horizon GroupMember

- - l A split horizon groupmember indicates thelogical port member inthe split horizon group.

l The port members thatare added to the samesplit horizon groupcannot communicatewith each other.

l The OptiX RTN 910supports only thedivision of the splithorizon groupmembers according tothe Ethernet physicalport.

l If a UNI or NNI logicalport of the 802.1adbridge is added to asplit horizon groupmember, the physicalport that is mountedwith the logical port isautomatically added tothe split horizon groupmember.

Related TasksA.26.4 Configuring the E-LAN Service

B.8.5 Parameter Description: E-LAN ServiceThis topic describes the parameters that are related to E-LAN services.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetService Management > E-LAN Service from the Function Tree.


Configuration Guide


Issue 02 (2009-10-30)


Service ID 1 to 4294967294 - l This parameterindicates the ID of theE-LAN service.

l The supportssimultaneous creationof an E-LAN serviceonly.

Service Name - - This parameter specifiesthe name of the E-LANservice.

BPDU - - l This parameterindicates thetransparenttransmission tag of theBPDU packets.

l In the case of an E-LAN service, thisparameter supportsonly transparenttransmission of theBPDU packets andcannot be set manually.

l Not TransparentlyTransmitted indicatesthat the BPDU packetsare used as the protocolpackets to compute thespanning tree topologyof the network.



B-133


Tag Type C-AwaredS-AwaredTag-Transparent

C-Awared l C-Awared indicatesthat the packets arelearnt according to C-Tag (the VLAN tag onthe client-side). Tocreate the 802.1qbridge, set thisparameter to C-Awared.

l S-Awared indicatesthat the packets arelearnt according to S-Tag (the VLAN tag atthe carrier servicelayer). To create the802.1ad bridge, set thisparameter to S-Awared.

l Tag-Transparentindicates that only theEthernet packets thatdo not contain VLANtags are accessed. Tocreate the 802.1dbridge, set thisparameter to S-Awared.

Self-Learning MACAddress

Enabled Enabled l This parameterindicates whether toenable the MACaddress self-learningfunction.

l If the MAC self-learning function of anEthernet LAN isenabled, the EthernetLAN learns an MACaddress according tothe original MACaddress in the packetand automaticallyrefreshes the MACaddress forwardingtable.


Configuration Guide


Issue 02 (2009-10-30)


MAC Address LearningMode

- - l This parameterindicates the mode usedto learn an MACaddress.

l When the bridge usesthe SVL mode, all theVLANs share oneMAC address table. Ifthe bridge uses the IVLmode, each VLAN hasan MAC address table.



Parameters for UNIsParameter Value Range Default Value Description


SVLAN 1 to 4094 - l This parameterspecifies the S-VLANID of the UNI port.





B-135


VLANs/CVLAN 1 to 4094 - l This parameterspecifies the VLAN IDof the UNI port.


l If this parameter is setto null, the E-LANservice exclusivelyuses the correspondingUNI physical port. Thatis, the entire port ismounted to the bridge.

l If this parameter is setto a non-null value,only the correspondingUNI port whose servicepackets contain thisVLAN ID works as thelogical port and ismounted to the bridge.

Parameters for NNIsParameter Value Range Default Value Description




Configuration Guide


Issue 02 (2009-10-30)


SVLANs - - l This parameterspecifies the S-VLANID of the UNI port.



Parameters for the Port AttributesParameter Value Range Default Value Description

Port - - This parameter indicatesthe bound port.

Enable Port EnabledDisabled

- The corresponding portcan normally carry theservices only when thisparameter is set toEnabled.



B-137



l This parameterspecifies the method ofthe port to process thereceived packets.

l If this parameter is setto Null, the porttransparently transmitsthe received packets.

l If this parameter is setto 802.1Q, the portidentifies the packetsthat comply with theIEEE 802.1Q standard.

l If this parameter is setto QinQ, the portidentifies the packetsthat comply with theIEEE 802.1 QinQstandard.


Tag Aware l If all the accessedservices are frameswith the VLAN tag(tagged frames), setthis parameter to "TagAware".

l If all the accessedservices are frameswithout the VLAN tag(untagged frames), setthis parameter to"Access".

l If the accessed servicescontain tagged framesand untagged frames,set this parameter to"Hybrid".


Configuration Guide


Issue 02 (2009-10-30)

Parameters for the Split Horizon GroupParameter Value Range Default Value Description

Split Horizon Group ID - 1 l This parameterindicates the ID of thesplit horizon group.

l The default splithorizon group ID is 1and cannot be setmanually.

Split Horizon GroupMember

- - l A split horizon groupmember indicates thelogical port member inthe split horizon group.

l The port members thatare added to differentsplit horizon groupscannot communicatewith each other.

l The supports only thedivision of the splithorizon groupmembers according tothe Ethernet physicalport.

l If a UNI or NNI logicalport of the 802.1adbridge is added to asplit horizon groupmember, the physicalport that is mountedwith the logical port isautomatically added tothe split horizon groupmember.



B-139

Parameters for Static MAC AddressesParameter Value Range Default Value Description

VLAN ID - 1 l This parameter isinvalid if MACAddress LearningMode is SVL. That is,the preset static MACaddress entries arevalid for all VLANs.

l If MAC AddressLearning Mode is setto IVL, the preset staticMAC address entriesare valid for only theVLANs whose VLANID is equal to the presetVLAN ID.


MAC Address - - l This parameterindicates or specifiesthe static MACaddress.

l A static MAC addressis an address that is setmanually. It is not agedautomatically andneeds to be deletedmanually.

l Generally, a staticMAC address is usedfor the port thatreceives but does notforward Ethernetservice packets or theport whose MACaddress need not beaged automatically.

Egress Interface - - l This parameterspecifies the Ethernetport that corresponds tothe MAC address.



Configuration Guide


Issue 02 (2009-10-30)

Parameters for Self-Learning MAC AddressParameter Value Range Default Value Description

VLAN ID - 1 l This parameter isinvalid if MACAddress LearningMode is SVL. That is,the preset self-learningMAC address entriesare valid for allVLANs.

l If MAC AddressLearning Mode is setto IVL, the preset self-learning MAC addressentries are valid foronly the VLANs whoseVLAN ID is equal tothe preset VLAN ID.


MAC Address - - l This parameterindicates or specifiesthe self-learning MACaddress. A self-learning MAC addressis also called a dynamicMAC address.

l The bridge uses theSVL or IVL mode toobtain the entries. Aself-learning MACaddress can be aged.

Egress Interface - - l This parameterspecifies the Ethernetport that corresponds tothe MAC address.




B-141

Parameters for Disabled MAC AddressesParameter Value Range Default Value Description

VLAN ID - 1 This parameter indicatesor specifies the VLAN IDof the service. A disabledMAC address is valid forthe VLAN whose VLANID is equal to the presetVLAN ID.

MAC Address - - l This parameterspecifies or indicatesthe disabled MACaddress. A disabledMAC address is alsocalled a blacklistedMAC address.

l This parameter is usedfor discarding an entry,also called a black holeentry, whose dataframe that contains aspecific destinationMAC address. Adisabled MAC addressneeds to be setmanually and cannot beaged.

Parameters for Unknown Frame ProcessingParameter Value Range Default Value Description

Frame Type UnicastMulticast

1 This parameter indicatesthe type of the receivedunknown frame.

Handing Mode DiscardBroadcast

Broadcast Selects the method ofprocessing the unknownframe. If this parameter isset to Discard, theunknown frame is directlydiscarded. If thisparameter is set toBroadcast, the unknownframe is broadcast at theforwarding port.


Configuration Guide


Issue 02 (2009-10-30)

Maintenance Association ParametersParameter Value Range Default Value Description


- - This parameter indicates the maintenancedomain of the created maintenanceassociation.


- - l This parameter specifies the name of themaintenance association, which is adomain related to a service. Throughmaintenance association division, theconnectivity check (CC) can beperformed on the network that transmitsa service instance.

l This parameter can contain a maximumof eight bytes.

CC Test TransmitPeriod(ms)

1s10s1m10m

1s l This parameter specifies the interval fortransmitting packets in the CC test.

l The CC is performed to check theavailability of the service.

Parameters for the MEPParameter Value Range Default Value Description


- - This parameter indicates the maintenancedomain of the created MEP.


- - This parameter indicates the maintenanceassociation of the created MEP.

Node - - This parameter indicates the MEP node.

VLAN - - This parameter indicates the VLAN ID ofthe current service.

MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured withan MEP ID, which is unique in themaintenance association. The MEP ID isrequired in the OAM operation.

Direction IngressEgress

Ingress l This parameter specifies the direction ofthe MEP.

l "Ingress" indicates the direction in whichthe packets are transmitted to the port,and "Egress" indicates the direction inwhich the packets are transmitted fromthe port.



B-143


CC Status ActiveInactive

Active l This parameter specifies whether toenable the CC function of the MEP.

l In the case of the tests based on the MPIDs, CC Status must be set to Active.

Related TasksA.27.1 Creating a Static MAC Address EntryA.27.2 Creating a Blacklist Entry of MAC AddressesA.27.3 Configuring the Aging Parameters of a MAC Address TableA.27.4 Querying or Deleting a Dynamic MAC AddressA.28 Setting the Mode for Processing an Unknown Frame of the E-LAN Service

B.8.6 Parameter Description: QinQ Link_CreationThis topic describes the parameters that are used for creating a QinQ link.


Service Management > QinQ Link from the Function Tree.

2. Click New. The New QinQ Link dialog box is displayed.

Parameters for the General Attributes


QinQ Link ID 1 to 4294967295 - This parameter specifiesthe ID of the QinQ link.

Board - - This parameter specifiesthe board where the QinQlink is located.

Port - - This parameter specifiesthe port where the QinQlink is located.

S-Vlan ID 1 to 4094 - l This parameterspecifies the VLAN ID(at the networkoperator side) for theQinQ link.



Configuration Guide


Issue 02 (2009-10-30)

Related TasksA.26.1 Configuring the QinQ Link

B.9 Ethernet Protocol ParametersThis topic describes the parameters that are related to the Ethernet protocol.

B.9.1 Parameter Description: ERPS Management_CreationThis topic describes the parameters that are used for creating ERPS management tasks.

B.9.2 Parameter Description: ERPS ManagementThis topic describes the parameters that are used for Ethernet ring protection switching (ERPS)management.

B.9.3 Parameter Description: MSTP Configuration_Port Group CreationThis topic describes the parameters that are used for creating MSTP port groups.

B.9.4 Parameter Description: MSTP Configuration_Port Group ConfigurationThis topic describes the parameters that are used for creating MSTP port groups.

B.9.5 Parameter Description: MSTP Configuration_ Bridge ParametersThis topic describes the parameters that are related to MSTP bridges.

B.9.6 Parameter Description: MSTP Configuration_CIST ParametersThis topic describes the parameters that are related to the MSTP CIST.

B.9.7 Parameter Description: MSTP Configuration_Running Information About the CISTThis topic describes the parameters that are related to the running information about the MSTPCIST.

B.9.8 Parameter Description: IGMP Snooping Configuration_Protocol ConfigurationThis topic describes the parameters that are used for configuring the IGMP snooping protocol.

B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be QuicklyDeletedThis topic describes the parameters that are used for adding a port to be quickly deleted.

B.9.10 Parameter Description: IGMP Snooping Configuration_Route ManagementThis topic describes the parameters that are used for IGMP Snooping protocol routemanagement.

B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port CreationThis topic describes the parameters that are used for adding static router ports.

B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member PortManagementThis topic describes the parameters that are used for managing the route member ports of theIGMP Snooping protocol.

B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group MemberCreationThis topic describes the parameters that are used for adding static multicast groups.



B-145

B.9.14 Parameter Description: IGMP Snooping Configuration_Data StatisticsThis topic describes the parameters that are used for collecting the data statistics of the IGMPSnooping protocol.

B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG CreationThis topic describes the parameters that are used for creating a link aggregation group (LAG).

B.9.16 Parameter Description: Ethernet Link Aggregation_Port PriorityThis topic describes the parameters that are related to the port priority of a LAG.

B.9.17 Parameter Description: LPT Management_CreationThis parameter describes the parameters that are used for creating LPT management.

B.9.18 Parameter Description: Port Mirroring_CreationThis topic describes the parameters that are used for creating port mirroring tasks.

B.9.1 Parameter Description: ERPS Management_CreationThis topic describes the parameters that are used for creating ERPS management tasks.


Protection > ERPS Management.2. Click New.


ERPS ID 1 to 8 - l This parameterspecifies the ID of theEthernet ringprotection switching(ERPS) instance.

l The ERPS ID must beunique.

East Port - - This parameter specifiesthe east port of the ERPSinstance.

West Port - - This parameter specifiesthe west port of the ERPSinstance.


Configuration Guide


Issue 02 (2009-10-30)


RPLOwner Ring NodeFlag

YesNo

No l This parameterspecifies whether thenode on the ring is thering protection link(RPL) owner.

l Only one node on thering can be set as theRPL owner for eachEthernet ring.

RPL Port - - This parameter specifiesthe RPL port.

Control VLAN 1 to 4094 - l This parameterspecifies the VLAN IDof Control VLAN.

l Each node on theEthernet ring transmitsthe R-APS packets onthe dedicated ring APS(R-APS) channel toensure consistencybetween the nodeswhen the ERPSswitching is performed.Control VLAN is usedfor isolating thededicated R-APSchannel. Therefore, theVLAN ID in ControlVLAN cannot beduplicate with theVLAN IDs that arecontained in the servicepackets or inband DCNpackets.

Destination Node 01-19-A7-00-00-01 01-19-A7-00-00-01 This parameter indicatesthe MAC address of thedestination node. Thedefault destination MACaddress in the R-APSpackets is always 01-19-A7-00-00-01.

Related TasksA.11.1 Creating Ethernet Ring Protection Instances



B-147

B.9.2 Parameter Description: ERPS ManagementThis topic describes the parameters that are used for Ethernet ring protection switching (ERPS)management.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > EthernetProtection > ERPS Management from the Function Tree.


ERPS ID 1 to 8 - l This parameterspecifies the ID of theERPS instance.

l The ERPS ID must beunique.

East Port - - This parameter specifiesthe east port of the ERPSinstance.

West Port - - This parameter specifiesthe west port of the ERPSinstance.

RPL Owner Ring NodeFlag

YesNo

No l This parameterspecifies whether anode on the ring is thering protection link(RPL) owner.

l Only one node on theEthernet ring can be setas the RPL owner.

RPL Port - - This parameter specifiesthe RPL port.


Configuration Guide


Issue 02 (2009-10-30)


Control VLAN 1 to 4094 - l This parameterspecifies the VLAN IDof Control VLAN.

l Each node on theEthernet ring transmitsthe Ring-APS (R-APS)packets on thededicated R-APSchannel to ensureconsistency betweenthe nodes when theERPS switching isperformed. ControlVLAN is used forisolating the dedicatedR-APS channel.Therefore, the VLANID in Control VLANcannot be the same asthe VLAN IDs that arecontained in the servicepackets or inband DCNpackets.

Destination Node 01-19-A7-00-00-01 01-19-A7-00-00-01 This parameter indicatesthe MAC address of thedestination node. Thedefault destination MACaddress in the R-APSpackets is always 01-19-A7-00-00-01.



B-149


Hold-Off Time(ms) 0 to 10000, in step of 100 0 l This parameterspecifies the hold-offtime of the ERPS hold-off timer.

l The hold-off timer isused for negotiating theprotection switchingsequence when theERPS coexists withother protectionschemes so that thefault can be rectified inthe case of otherprotection switching(such as LAGprotection) before theERPS occurs. When anode on the ring detectsone or more new faults,it starts up the hold-offtimer if the preset hold-off time is set to a valuethat is not 0. During thehold-off time, the faultis not reported totrigger an ERPS. Whenthe hold-off timer timesout, the node checks thelink status regardlesswhether the fault thattriggers the startup ofthe timer exists. If thefault exists, the nodereports it to trigger anERPS. This fault can bethe same as or differentfrom the fault thattriggers the initialstartup of the hold-offtimer.


Configuration Guide


Issue 02 (2009-10-30)


Guard Time(ms) 10 to 2000, in step of 10 500 l This parameterspecifies the guard timeof the ERPS guardtimer.

l The nodes on the ringcontinuously forwardthe R-APS packets tothe Ethernet ring. As aresult, the outdated R-APS packets may existon the ring network.After a node on the ringreceives the outdatedR-APS packets, anincorrect ERPS mayoccur. The ERPS guardtimer is an R-APS timerused for preventing anode on the ring fromreceiving outdated R-APS packets. When afaulty node on the ringdetects that theswitching condition iscleared, the node startsup the guard timer andstarts to forward the R-APS (NR) packets.During this period, theR-APS packetsreceived by the nodeare discarded. Thereceived R-APSpackets are forwardedonly after the time ofthe guard timer expires.



B-151


WTR Time(min) 5 to 12, in step of 1 5 l This parameterspecifies the WTR timeof the WRT timer in thecase of ERPSprotection.

l The WTR time refers tothe duration from thetime when the workingchannel is restored tothe time when theswitching is released.When the workingchannel is restored, theWTR timer of the RPLowner starts up. Inaddition, a signal thatindicates the operationof the WTR timer iscontinuously output inthe timing process.When the WTR timertimes out and noswitching request of ahigher priority isreceived, the signalindicating theoperation of the WTRtimer is not transmitted.In addition, the WTRrelease signal iscontinuously output.

l The WTR timer is usedto prevent frequentswitching caused by theunstable workingchannel.

Packet TransmitInterval(s)

1 to 10 5 This parameter specifiesthe interval fortransmitting the R-APSpackets.

Entity Level 0 to 7 0 This parameter specifiesthe level of themaintenance entity.

Last Switching Request - - This parameter indicatesthe last switching request.


Configuration Guide


Issue 02 (2009-10-30)


RB Status - - This parameter indicatesthe RB status of thepackets received by theworking node.l noRB: The RPL is not

blocked.l RB (RPL Blocked):

The RPL is blocked.

DNF Status - - This parameter indicatesthe DNF status of thepackets received by theworking node.l noDNF: The R-APS

packets do not containthe DNF flag. In thiscase, the packets areforwarded by the nodethat detects the fault ona non-RPL link, and thenode that receives thepackets is requested toclear the forwardingaddress table.

l DNF: The R-APSpackets contain theDNF flags. In this case,the packets areforwarded by the nodethat detects the fault onan RPL link, and thenode that receives thepackets is informed notto clear the forwardingaddress table.



B-153


Status of State Machine - - This parameter indicatesthe status of the statemachine at the workingnode.l Idle: The Ethernet ring

is in normal state. Forexample, no node onthe Ethernet ringdetects any faults orreceive the R_APS(NR, RB) packets.

l Protection: TheEthernet ring is inprotected state. Forexample, a node on thering is in the WTRperiod, because thefault on the nodetriggers the ERPS orthe fault is rectified.

Node Carried withCurrent Packet

- - This parameter indicatesthe MAC address carriedin the R-APS packetsreceived by the currentnode. The MAC addressrefers to the MAC addressof the source node thatinitiates the switchingrequest.

Related TasksA.11.2 Setting the Parameters of Ethernet Ring ProtocolA.11.3 Querying the Status of the Ethernet Ring Protocol

B.9.3 Parameter Description: MSTP Configuration_Port GroupCreation

This topic describes the parameters that are used for creating MSTP port groups.


Protocol Configuration > MSTP Configuration from the Function Tree.

2. Click the Port Group Parameters tab.

3. Click Create. The Create Port Group dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)


Protocol Type MSTPSTP

MSTP This parameter specifiesthe protocol type.l MSTP: stands for

Multiple SpanningTree Protocol. TheOptiX RTN 910supports the CISTMSTP only.

l STP: stands forSpanning TreeProtocol.

Enable Protocol EnabledDisabled

Disabled l This parameterspecifies whether toenable the protocol ofthe port group or amember port in the portgroup.

l If the STP or MSTP isenabled, the spanningtree topology isautomatically re-configured. As a result,the services areinterrupted.

Parameters for Application PortsParameter Value Range Default Value Description

Board - - This parameter specifiesthe board where the portgroup is located.

Available Port List - - This parameter indicatesthe available port list inwhich a port needs to beadded to the port group.

Selected Port List - - This parameter indicatesthe selected ports thatneed to be added to theport group.

Related TasksA.12.1 Creating the MSTP Port Group



B-155

B.9.4 Parameter Description: MSTP Configuration_Port GroupConfiguration

This topic describes the parameters that are used for creating MSTP port groups.


Protocol Configuration > MSTP Configuration from the Function Tree.2. Click the Port Group Parameters tab.3. On the main interface, select the port group to be configured.4. Click Config. The Configure Port Group dialog box is displayed.

Parameters for the Added PortParameter Value Range Default Value Description

Board - - This parameter specifiesthe board where the portgroup is located.

Available Port List - - This parameter indicatesthe available port list inwhich a port needs to beadded to the port group.

Selected Port List - - This parameter indicatesthe selected ports thatneed to be added to theport group.

Related TasksA.12.7 Modifying the Configuration Data of the MSTP Port Group

B.9.5 Parameter Description: MSTP Configuration_ BridgeParameters

This topic describes the parameters that are related to MSTP bridges.


Protocol Configuration > MSTP Configuration from the Function Tree.2. Click the Bridge Parameters tab.


Configuration Guide


Issue 02 (2009-10-30)


Port Group ID - - l This parameterindicates the ID of theport group.

l This parameter can beset to only the portgroup ID that isautomaticallyallocated.

MST Domain Name - - The OptiX RTN 910 doesnot support thisparameter.

Redaction Level - - The OptiX RTN 910 doesnot support thisparameter.

Mapping List - - The OptiX RTN 910 doesnot support thisparameter.

Bridge ParametersParameter Value Range Default Value Description

Port Group ID - - l This parameterindicates the ID of theport group.

l This parameter can beset to only the portGroup ID that isautomaticallyallocated.

Hello Time(s) 1 to 10 2 l This parameterspecifies the intervalfor transmitting theCBPDU packetsthrough the bridge.

l The greater the value ofthis parameter, the lessthe network resourcesthat are occupied by thespanning tree. Thetopology stability,however, decreases.



B-157


Max Age(s) 6 to 40 20 l This parameterspecifies the maximumage of the CBPDUpacket that is recordedby the port.

l The greater the value,the longer thetransmission distanceof the CBPDU, whichindicates that thenetwork diameter isgreater. When the valueof this parameter isgreater, it is lesspossible that the bridgedetects the link fault ina timely manner andthus the networkadaptation ability isreduced.

Forward Delay(s) 4 to 30 15 l This parameterspecifies the holdofftime of a port in thelistening state and inthe learning state.

l The greater the value,the longer the delay ofthe network statechange. Hence, thetopology changes areslower and the recoveryin the case of faults isslower.

Port ParametersParameter Value Range Default Value Description

Port - - This parameter indicatesthe port in the port group.


Configuration Guide


Issue 02 (2009-10-30)


Enable Edge Attribute DisabledEnabled

Disabled l This parameterspecifies themanagement edgeattributes of the port.

l This parameterspecifies whether to setthe port as an edge port.The edge port refers tothe bridge port that isconnected to the LAN.An edge port onlyreceives BPDUpackets.

l This parameter can beset to Enabled onlywhen the port isdirectly connected tothe datacommunicationsterminal equipment,such as a computer. Inother cases, it isrecommended that youuse the default value.

Actual Edge Attribute - - This parameter indicatesthe actual managementedge attributes of the port.



B-159


Point-to-Point Attribute falsetrueauto

auto l This parameterspecifies the point-to-point attribute of theport.

l false: forced non-point-to-point linkattribute

l true: forced point-to-point link attribute

l auto: automaticallydetected point-to-pointlink attribute

l If this parameter is setto auto, the bridgedetermines ActualPoint-to-PointAttribute of the portaccording to the actualworking mode. If theactual working mode isfull-duplex, the actualpoint-to-point attributeis true. If the actualworking mode is half-duplex, Actual Point-to-Point Attribute isfalse.

l Only the root port ordesignated port whoseActual Point-to-PointAttribute is "True" cantransmit the rapid statemigration request andresponse.


Actual Point-to-PointAttribute

- - This parameter indicatesthe actual point-to-pointattribute of the port.


Configuration Guide


Issue 02 (2009-10-30)


Max Transmit PacketCount

1 to 255 3 l This parameterspecifies the maximumnumber of packets to betransmitted.

l The maximum numberof packets to betransmitted by the portrefers to the maximumnumber of MSTPpackets that the portcan transmit within theinterval time oftransmitting the hellopackets.

l This parameter needs tobe set according to theplanning information.

Related TasksA.12.2 Setting the Bridge Parameters of the MSTP

B.9.6 Parameter Description: MSTP Configuration_CISTParameters

This topic describes the parameters that are related to the MSTP CIST.


Protocol Configuration > MSTP Configuration from the Function Tree.

2. Click the CIST&MSTI Parameters tab.



Port Group - - This parameter specifiesthe port group.

MSTI ID 0 0 This parameter indicatesthe MSTI ID. The value 0indicates that the OptiXRTN 910 supports onlythe MSTP that usescommon and internalspanning tree (CIST).



B-161


Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant 16bits of the bridge IDindicates the priority ofthe bridge.

l When the value issmaller, the priority ishigher. As a result, thebridge is more possibleto be selected as theroot bridge.

l If the priorities of allthe bridges in the STPnetwork use the samevalue, the bridge whoseMAC address is thesmallest is selected asthe root bridge.



Priority 0 to 240, in step of 16 128 l The most significanteight bits of the port IDindicate the portpriority.

l When the value issmaller, the priority ishigher.

Path Cost 1 to 200000000 200000 l This parameterindicates the status ofthe network that theport is connected to.

l In the case of thebridges on both ends ofthe path, set thisparameter to the samevalue.

Related TasksA.12.3 Setting the Parameters of the CIST


Configuration Guide


Issue 02 (2009-10-30)

B.9.7 Parameter Description: MSTP Configuration_RunningInformation About the CIST

This topic describes the parameters that are related to the running information about the MSTPCIST.


Protocol Configuration > MSTP Configuration from the Function Tree.2. Click the CIST Running Information tab.


Port Group ID - - This parameter indicatesthe ID of the port group.

Protocol Running Mode MSTPSTP

Disabled l This parameterindicates the runningmode of the protocol.

l MSTP: stands forMultiple SpanningTree Protocol. TheOptiX RTN 910supports only theCIST-based MSTP.




B-163


Bridge Priority 0 to 61440, in step of 4096 32768 l This parameterindicates the priority ofthe bridge.

l The most significant 16bits of the bridge IDindicates the priority ofthe bridge.



Bridge MAC Address - - This parameter indicatesthe MAC address of thebridge.

Root Bridge MACAddress

- - This parameter indicatesthe MAC address of theroot bridge.

External Path CostERPC

- - The OptiX RTN 910 doesnot support thisparameter.

Domain Root BridgePriority


Domain Root BridgeMAC Address


Internal Path Cost IRPC - - The OptiX RTN 910 doesnot support thisparameter.


Configuration Guide


Issue 02 (2009-10-30)


Root Port Priority 0 to 240, in step of 16 128 l This parameterindicates the priority ofthe root port.

l The most significanteight bits of the ID ofthe root port indicatethe priority of the rootport.


Root Port - - This parameter indicatesthe root port.

Hello Time(s) 1 to 10 2 l This parameterindicates the intervalfor transmittingCBPDU packetsthrough the bridge.






B-165


Forward Delay(s) 4 to 30 15 l This parameterspecifies the holdofftime of a port in thelistening state and inthe learning state.


MST Domain Max HopCount


Topology Change Count - - This parameter indicatesthe identifier of thetopology change.

Last Topology ChangeTime(s)

- - This parameter indicatesthe duration of the lasttopology change.

Topology Change Count - - This parameter indicatesthe count of the topologychanges.



Enable Protocol EnabledDisabled

Disabled This parameter indicateswhether the protocol ofthe port group or amember of the port groupis enabled.

Port Role - - This parameter indicatesthe role of a port.


Configuration Guide


Issue 02 (2009-10-30)


Port Status DiscardingLearningForwarding

Discarding This parameter indicatesthe state of a port.l Discarding: receives

only BPDU packetsl Learning: only receives

or transmits BPDUpackets

l Forwarding: forwardsuser traffic, andtransmits/receivesBPDU packets

Priority 0 to 240, in step of 16 128 l The most significanteight bits of the port IDindicate the portpriority.


Path Cost 1 to 200000000 200000 l This parameterindicates the status ofthe network that theport is connected to.

l In the case of thebridges on both ends ofthe path, set thisparameter to the samevalue.

Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant 16bits of the bridge IDindicates the priority ofthe bridge.





B-167


Bridge MAC Address - - This parameter indicatesthe MAC address of thebridge.

Designated Port Priority 0 to 240, in step of 16 128 l The most significanteight bits of the port IDindicate the portpriority.


Design Port - - This parameter indicatesthe designated port.

Edge Port Attribute DisabledEnabled

Enabled l This parameterspecifies themanagement edgeattributes of the port.

l This parameterspecifies whether to setthe port as an edge port.The edge port refers tothe bridge port that isconnected to the LAN.An edge port onlyreceives BPDUpackets.

l This parameter can beset to Enabled onlywhen the port isdirectly connected tothe datacommunicationsterminal equipment,such as a computer. Inother cases, it isrecommended that youuse the default value.

Actual Edge PortAttribute

- - This parameter indicatesthe actual managementedge attributes of the port.


Configuration Guide


Issue 02 (2009-10-30)


Point to Point falsetrueauto

auto l This parameterspecifies the point-to-point attribute of theport.

l false: forced non-point-to-point linkattribute

l true: forced point-to-point link attribute

l auto: automaticallydetected point-to-pointlink attribute

l If this parameter is setto auto, the bridgedetermines ActualPoint to PointAttribute of the portaccording to the actualworking mode. If theactual working mode isfull-duplex, the actualpoint-to-point attributeis true. If the actualworking mode is half-duplex, Actual Pointto Point Attribute isfalse.

l Only the root port ordesignated port whoseActual Point-to-PointAttribute is "True" cantransmit the rapid statemigration request andresponse.


Actual Point to Point - - This parameter indicatesthe actual point-to-pointattribute of the port.



B-169


Max Count ofTransmitting Message

1 to 255 3 l This parameterindicates the maximumnumber of packets to betransmitted.

l The maximum numberof packets to betransmitted by the portrefers to the maximumnumber of MSTPpackets that the portcan transmit withineach hello time.

Protocol Running Mode STPMSTP

- l This parameterindicates the runningmode of the protocol.

l MSTP: stands forMultiple SpanningTree Protocol. TheOptiX RTN 910supports only theCIST-based MSTP.


Hello Time(s) 1 to 10 2 l This parameterindicates the intervalfor transmitting theCBPDU packetsthrough the bridge.



Configuration Guide


Issue 02 (2009-10-30)




Forward Delay(s) 4 to 30 15 l This parameterspecifies the holdingtime of a port in thelistening state and inthe learning state.


Remain Hop - - The OptiX RTN 910 doesnot support thisparameter.

Related TasksA.12.4 Querying the CIST Running Information

B.9.8 Parameter Description: IGMP SnoopingConfiguration_Protocol Configuration

This topic describes the parameters that are used for configuring the IGMP snooping protocol.



B-171


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Protocol Configuration tab.


Service ID - - This parameter indicatesthe service ID.

Enabled Protocol EnabledDisabled

Disabled l This parameterspecifies whether toenable the IGMPSnooping protocol.

l If the bridge accesses aLAN where the IGMPmulticast server exists,you can enable theIGMP Snoopingprotocol according tothe requirement.


Configuration Guide


Issue 02 (2009-10-30)


Router Port Aging Time(min)

1 to 120 8 l If an entry is notupdated in a certainperiod (that is, noIGMP query packetfrom this multicastaddress is received),this entry isautomatically deleted.This mechanism iscalled aging, and thisperiod is called agingtime.

l If this parameter is setto a very large value,the bridge storesexcessive multicastentries that areoutdated.Consequently, theresources of themulticast table areexhausted.

l If this parameter is setto a very small value,the bridge may deletethe multicast entry thatis required.Consequently, theforwarding efficiencydecreases.



B-173


Maximum Times of NoResponse from MulticastMembers

1 to 4 3 l This parameterspecifies the maximumnumber of multicastgroup members who donot respond.

l If the IEEE 802.1qbridge transmits anIGMP group querypacket to the multicastmember ports, theIEEE 802.1q bridgestarts the timer for thequery of the maximumnumber of responses. Ifno IGMP reportpackets are receivedwithin the query time,the IEEE 802.1q bridgeadds one to the numberof no responses at theport. When the numberof no responsesexceeds the presetvalue of MaximumTimes of No Responsefrom MulticastMembers, the IEEE802.1q bridge deletesthe additional multicastmembers from themulticast group.

Maximum Number ofMulticast Groups

- - l This parameterspecifies the maximumnumber of allowablemulticast groups.

l The multicast grouprecords the mappingrelations between theports on the router,MAC multicastaddresses, and memberports in the multicastgroup.


Configuration Guide


Issue 02 (2009-10-30)


Maximum Number ofMulticast GroupMembers

- - l This parameterspecifies the maximumnumber of allowablemulticast groupmembers.

l A multicast groupmember refers to theNE that is added to amulticast group.

Actual Multicast Count - - This parameter indicatesthe number of actuallyused multicast groups.

Actual MulticastMembers Count

- - This parameter indicatesthe number of actuallyused multicast groupmembers.

Related TasksA.13.1 Configuring the IGMP Snooping Protocol

B.9.9 Parameter Description: IGMP SnoopingConfiguration_Adding Port to Be Quickly Deleted

This topic describes the parameters that are used for adding a port to be quickly deleted.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Protocol Configuration tab.3. Click Add.

Parameters for Fast Leave PortsParameter Value Range Default Value Description




B-175


VLAN ID 1 to 4094 1 l This parameterspecifies the VLANwhere the port to bequickly deleted islocated.


Port Type V-UNIV-NNI

V-UNI l This parameterspecifies the type of theport to be quicklydeleted.


Port - - This parameter specifiesthe port to be quicklydeleted.

Related TasksA.13.6 Adding a Quickly Deleted Port

B.9.10 Parameter Description: IGMP SnoopingConfiguration_Route Management

This topic describes the parameters that are used for IGMP Snooping protocol routemanagement.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Router Port Management tab.

Parameters for Router Port ManagementParameter Value Range Default Value Description

Service ID - - This parameter specifiesthe ID of the created E-LAN service.


Configuration Guide


Issue 02 (2009-10-30)


VLAN ID 1 1 to 4094 l This parameterindicates the VLAN IDof the router port.

l The value of thisVLAN ID should be thesame as the value ofVLANs/CVLAN forthe V-UNI port in theE-LAN service.

Port Type - - This parameter indicatesthe type of the router port.

Port - - This parameter indicatesthe router port.

Port Status - - This parameter indicatesthe status of the routerport.

Port Creating Time - - This parameter indicatesthe time when the routerport is created.

Port Remainder AgingTime(min)

- - This parameter indicatesthe remaining aging timeof the router port.

Related TasksA.13.2 Querying the Port Information of the Routers

B.9.11 Parameter Description: IGMP SnoopingConfiguraiton_Static Router Port Creation

This topic describes the parameters that are used for adding static router ports.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Router Port Management tab.3. Click New.



B-177

Parameters for Router Port Creation




l The value of thisVLAN ID should be thesame as the value ofVLANs/CVLAN forthe V-UNI port in theE-LAN service.

Available Port - - This parameter indicatesthe available ports.

Selected Port - - l This parameterindicates the specifiedrouter port.

l A router port refers tothe port that isconnected to themulticast router. Itfunctions as the V-UNIport in the E-LANservice.


Related TasksA.13.4 Creating Static Router Ports

B.9.12 Parameter Description: IGMP SnoopingConfiguration_Route Member Port Management

This topic describes the parameters that are used for managing the route member ports of theIGMP Snooping protocol.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.

2. Click the Route Member Port Management tab.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for Multicast Groups InformationParameter Value Range Default Value Description



l The value of thisVLAN ID should be thesame as the value ofSVLAN for the V-NNIport in the E-LANservice.

Multicast MAC Address - - This parameter indicatesthe multicast MACaddress.

Multicast Groups Type - - This parameter indicatesthe type of the multicastgroup.

Multicast GroupCreating Time

- - This parameter indicatesthe time when themulticast group is set up.

Parameters for Multicast Group Members InformationParameter Value Range Default Value Description


VLAN ID 1 1 to 4094 l This parameterindicates the VLAN IDof the multicast groupmember.

l The value of thisVLAN ID should be thesame as the value ofSVLAN for the V- NNIport in the E-LANservice.

Port Type - - This parameter indicatesthe type of the multicastgroup member.



B-179


Port - - This parameter indicatesthe multicast groupmember port.

Port Remainder AgingTimes

- - This parameter indicatesthe remaining aging timesof the multicast groupmember port.

Related TasksA.13.3 Querying the Information About the Multicast Groups

B.9.13 Parameter Description: IGMP SnoopingConfiguration_Static Multicast Group Member Creation

This topic describes the parameters that are used for adding static multicast groups.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Route Member Port Management tab.3. Click New.

Parameters for Router Port CreationParameter Value Range Default Value Description


VLAN ID 1 1 to 4094 l This parameterspecifies the VLAN IDof the router port.

l The value of thisVLAN ID should be thesame as the value ofSVLANs for the V-UNI port in the E-LANservice.

Multicast MAC Address - - This parameter specifiesthe multicast MACaddress.

Available Port - - This parameter indicatesthe available interfaces.


Configuration Guide


Issue 02 (2009-10-30)


Selected Port - - l This parameterindicates the preset portof the multicast groupmembers

l The multicast groupmember port refers to aport that is connected tothe multicast groupmember. This port is aV-NNI port in the E-LAN service.

l This parameter needs toset according to theplanning information.

Related TasksA.13.5 Creating a Member of a Static Multicast Group

B.9.14 Parameter Description: IGMP Snooping Configuration_DataStatistics

This topic describes the parameters that are used for collecting the data statistics of the IGMPSnooping protocol.


Protocol Configuration > IGMP Snooping Configuration from the Function Tree.2. Click the Packet Statistics tab.

Parameters for Routing Member Interface ManagementParameter Value Range Default Value Description


VLAN ID - - This parameter indicatesthe VLAN ID of theservice.

Port Type - -

Port - - This parameter indicatesthe port.



B-181


Packet Statistics Status - - This parameter indicatesor specifies the status ofcollecting the packetstatistics.

IGMPv1 Query PacketCount

- - This parameter indicatesthe number of receivedIGMPv1 query packets.





IGMP Leaving PacketCount

- - This parameter indicatesthe number of receivedpackets showing that theIGMP is transmitted fromthe multicast group.

IGMPv1 MemberReport Packet Count

- - This parameter indicatesthe number of receivedpackets that are reportedby the IGMPv1 members.





Unrecognized orUnprocessed PacketCount

- - This parameter indicatesthe number of packets thatcannot be recognized orprocessed.

Discarded IncorrectPacket Count

- - This parameter indicatesthe number of discardederror packets.

Related TasksA.13.7 Calculating IGMP Packets


Configuration Guide


Issue 02 (2009-10-30)

B.9.15 Parameter Description: Ethernet Link AggregationManagement_LAG Creation

This topic describes the parameters that are used for creating a link aggregation group (LAG).

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface

Management > Link Aggregation Group Management from the Function Tree.2. Click the Link Aggregation Group Management tab.3. Click New. The Create Link Aggregation Group dialog box is displayed.


LAG No. 1 to 65535 1 l This parameterspecifies the LAGnumber to be setmanually.

l This parameter is validonly whenAutomatically Assignis not selected.

Automatically Assign SelectedDeselected

Selected l This parameterindicates whether LAGNo. is allocatedautomatically.

l When AutomaticallyAssign is selected,LAG No. cannot be set.

LAG Name - - This parameter specifiesthe LAG name.



B-183


LAG Type StaticManual

Static l Static: You can create aLAG. When you add ordelete a member port toor from the LAG, theLink AggregationControl Protocol(LACP) protocol isrequired. In a LAG, aport can be in theSelected or Standbystate. The aggregationinformation isexchanged amongdifferent equipmentthrough the LACPprotocol to ensure thatthe aggregationinformation is the sameamong all the nodes.

l Manual: You canmanually create a LAG.When you add or deletea member port, theLACP protocol is notrequired. The port canbe in the up or downstate. According to thephysical up or downstate, you candetermine whether toperform anaggregation.


Non-Revertive This parameter can be setonly when Load Sharingis set to Non-Sharing.


Configuration Guide


Issue 02 (2009-10-30)


Load Sharing SharingNon-Sharing

Non-Sharing l Sharing: Each memberlink of a LAGprocesses traffic at thesame time and sharesthe traffic load. Thesharing mode canincrease a bandwidthutilization for the link.When the LAGmembers change, orcertain links fail, thesystem automaticallyre-allocates the traffic.

l Non-Sharing: Only onemember link of a LAGcarries traffic, and theother link is in thestandby state. In thiscase, a hot backupmechanism isprovided. When theactive link of a LAG isfaulty, the systemactivates the standbylink, thus preventinglink failure.

Load Sharing HashAlgorithm

Source MACDestination MACSource and DestinationMACSource IPDestination IPSource and Destination IP

Source MAC l This parameter is validonly when LoadSharing of a LAG is setto Sharing.

l The load sharingcomputation methodsinclude: MAC addressspecific allocation(based on the sourceMAC address,destination MACaddress, and XORbetween source MACaddress and sourceMAC address), IPaddress specificallocation (based on thesource IP address,destination IP address,and XOR betweensource IP address andsource IP address).



B-185


System Priority 0 to 65535 32768 l This parameterindicates the priority ofa LAG. The smaller thevalue of SystemPriority, the higher thepriority.

l When a local LAGnegotiates with anopposite LAG throughLACP packets, bothLAGs can obtain thesystem priorities ofeach other. Then, theLAG of the highersystem priority isconsidered as thecomparison result ofboth LAGs so that theaggregationinformation isconsistent at bothLAGs. If the prioritiesof both LAGs are thesame, the system MACaddresses arecompared. Then, thecomparison resultbased on the LAG withsmaller system MACaddress is considered asthe result of both LAGsand is used to ensurethat the aggregationinformation isconsistent at bothLAGs.

Port Settings ParametersParameter Value Range Default Value Description

Main Board - - l This parameterspecifies the mainboard in a LAG.



Configuration Guide


Issue 02 (2009-10-30)


Main Port - - l This parameterspecifies the main portin a LAG.

l After a LAG is created,you can add Ethernetservices to the mainport only. Servicescannot be added to aslave port. When LoadSharing is set to Non-Sharing, the linkconnected to the mainport is used to transmitthe services, and thelink connected to theslave port is used forprotection.

Board (Available SlavePorts)

- - l This parameterspecifies the slaveboard in a LAG.


Port (Available SlavePorts)

- - l This parameterspecifies the salve portin a LAG.

l The slave ports in aLAG are fixed. Unlessthey are manuallymodified, the systemdoes not automaticallyadd them to or deletethem from the LAG.

Selected Slave Ports - - This parameter indicatesthe selected slave ports.

Related TasksA.14.1 Creating a LAG

B.9.16 Parameter Description: Ethernet Link Aggregation_PortPriority

This topic describes the parameters that are related to the port priority of a LAG.



B-187


Management > Link Aggregation Group Management from the Function Tree.2. Click the Port Priority tab.


Port - - This parameter indicatesthe port whose priority canbe set.

Port Priority 0 to 65535 32768 l This parameterindicates the prioritiesof the ports in a LAG asdefined in the LACPprotocol. The smallerthe value, the higher thepriority.

l When ports are addedinto a LAG, the port ofthe highest priority ispreferred for servicetransmission.

Related TasksA.14.2 Setting the Port Priority

B.9.17 Parameter Description: LPT Management_CreationThis parameter describes the parameters that are used for creating LPT management.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT

Management from the Function Tree.2. Click New.

Parameters for Convergence PointsParameter Value Range Default Value Description

Board - - This parameter specifies the board at theconvergence point.


Configuration Guide


Issue 02 (2009-10-30)


Port - - This parameter specifies the port on theboard of the convergence point.NOTE

One port can be in an LPT only.

Parameters for Access PointsParameter Value Range Default Value Description

Board - - This parameter specifies the board at theaccess point.

Port - - This parameter specifies the port on theboard of the access point.NOTE

The access point supports selection of multipleports on different boards.

Related TasksA.15 LPT Configuration

B.9.18 Parameter Description: Port Mirroring_CreationThis topic describes the parameters that are used for creating port mirroring tasks.


Configuration > Port Mirroring from the Function Tree.2. Click New. The Port Mirror Management dialog box is displayed.


Mirror Name - - l This parameter specifies the name of themirroring task.

l After the mirroring function of the port isenabled, you can monitor all the mirroredports by analyzing the packets at themirroring port only. As a result, you caneasily manage the ports.



B-189



Ingress l This parameter specifies the direction inwhich the service to be monitored.

l Ingress indicates that the uplink directionof the service to be monitored.

l Egress indicates that the downlinkdirection of the service to be monitored.

Mirror ListenerPort

- - l This parameter specifies the mirroringlistener port and the listened port.

l Mirror Listener Port: The port whereservices are available cannot be selected.Otherwise, the creation fails.

Listened Port - -

B.10 Parameters for the Ethernet OAMThis topic describes the parameters that are related to the Ethernet operation, administration andmaintenance (OAM).

B.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance DomainCreationThis topic describes the parameters that are used for creating maintenance domains.

B.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance AssociationCreationThis topic describes the parameters that are used for creating maintenance associations.

B.10.3 Parameter Description: Ethernet Service OAM Management_MEP CreationThis topic describes the parameters that are used for creating a maintenance association endpoint (MEP).

B.10.4 Parameter Description: Ethernet Service OAM Management_Remote MEP CreationThis topic describes the parameters that are used for creating a remote MEP.

B.10.5 Parameter Description: Ethernet Service OAM Management_MIP CreationThis topic describes the parameters that are used for creating a maintenance associationintermediate point (MIP).

B.10.6 Parameter Description: Ethernet Service OAM Management_LB EnablingThis topic describes the parameters that are used for enabling the LB.

B.10.7 Parameter Description: Ethernet Service OAM Management_LT EnablingThis topic describes the parameters that are used for enabling the LT.

B.10.8 Parameter Description: Ethernet Port OAM Management_OAM ParameterThis topic describes the OAM parameters that are related to Ethernet ports.

B.10.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame MonitoringThis topic describes the parameters that are used for monitoring the OAM error frames at theEthernet port.


Configuration Guide


Issue 02 (2009-10-30)

B.10.1 Parameter Description: Ethernet Service OAMManagement_Maintenance Domain Creation

This topic describes the parameters that are used for creating maintenance domains.


OAM Management > Ethernet Service OAM Management from the Function Tree.2. Click the Maintenance Association tab.3. Choose New > New Maintenance Domain.



- - l This parameter specifies the name of themaintenance domain.

l The maintenance domain refers to thenetwork for the Ethernet OAM.



01234567

4 l This parameter specifies the level of themaintenance domain.

l The values 0-2 indicate the carrier level,the values 3-4 indicate the supplier level,and the values 5-7 indicates the user level.

l When the value is set to 0, themaintenance domain is at the lowestlevel. The values 1-7 indicate that thelevel increases in a sequential order.

l The OAM packets whose level is higherthan the preset value are transparentlytransmitted by the MEPs. The OAMpackets whose level is lower than thepreset value are directly discarded by theMEPs. The OAM packets whose level isthe same as the preset value are respondedto or terminated by the MEPs accordingto the message type.

Related TasksA.17.1 Creating an MD



B-191

B.10.2 Parameter Description: Ethernet Service OAMManagement_Maintenance Association Creation

This topic describes the parameters that are used for creating maintenance associations.


OAM Management > Ethernet Service OAM Management from the Function Tree.2. Click the Maintenance Association tab.3. Select the maintenance domain in which a maintenance association needs to be created.

Choose New > New Maintenance Association.




- - This parameter indicates the maintenancedomain of the created maintenanceassociation.


- - l This parameter specifies the name of themaintenance association, which is adomain related to a service. Throughmaintenance association division, theconnectivity check (CC) can beperformed on the network that transmitsa service instance.


Relevant Service - - This parameter specifies the serviceinstance that is related to the maintenanceassociation.

CC Test TransmitPeriod(ms)

1s10s1 min10 min

1s l This parameter specifies the interval fortransmitting packets in the CC.

l The CC is performed to check theavailability of the service.

Related TasksA.17.2 Creating an MA

B.10.3 Parameter Description: Ethernet Service OAMManagement_MEP Creation

This topic describes the parameters that are used for creating a maintenance association endpoint (MEP).


Configuration Guide


Issue 02 (2009-10-30)


OAM Management > Ethernet Service OAM Management from the Function Tree.2. Click the Maintenance Association tab.3. Select the maintenance association in which an MEP needs to be created. Choose New >

New MEP Point.



- - This parameter indicates the maintenancedomain of the created MEP.



Board - - This parameter specifies the board wherethe MEP is located.

Port - - This parameter specifies the port where theMEP is located.

VLAN - - This parameter indicates the VLAN ID ofthe current service.

MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured withan MEP ID, which is unique in themaintenance association. The MEP ID isrequired in the OAM operation.


Ingress l This parameter specifies the direction ofthe MEP.

l Ingress indicates the direction in whichthe packets are transmitted to the port,and Egress indicates the direction inwhich the packets are transmitted fromthe port.

CC Status ActiveInactive

Active l This parameter specifies whether toenable the CC function of the MEP.

l In the case of the tests based on the MPIDs, CC Status must be set to Active.

Related TasksA.17.3 Creating an MEP Point



B-193

B.10.4 Parameter Description: Ethernet Service OAMManagement_Remote MEP Creation

This topic describes the parameters that are used for creating a remote MEP.


OAM Management > Ethernet Service OAM Management from the Function Tree.

2. Click the Maintenance Association tab.

3. Choose OAM > Manage Remote MEP Point. Then, the Maintenance Domain Namedialog box is displayed.

4. Click New.




- - This parameter indicates the maintenancedomain of the MEP.



RemoteMaintenance PointID(_e.g:1,3-6)

1 to 2048 1 l This parameter specifies the ID of theremote MEP.

l If other MEPs may initiate OAMoperations to an MEP in the same MA,set the other MEPs to be the remoteMEPs.

Related TasksA.17.4 Creating Remote MEPs in an MA

B.10.5 Parameter Description: Ethernet Service OAMManagement_MIP Creation

This topic describes the parameters that are used for creating a maintenance associationintermediate point (MIP).


OAM Management > Ethernet Service OAM Management from the Function Tree.

2. Click the MIP Point tab.

3. Select the maintenance domain in which an MIP needs to be created, and then click New.


Configuration Guide


Issue 02 (2009-10-30)



- - This parameter indicates the maintenancedomain of the MIP.

Board - - This parameter specifies the board wherethe MIP is located.

Port - - This parameter specifies the port where theMIP is located.

MP ID 1 to 2048 1 l This parameter specifies the MIP ID.

l Each MIP needs to be configured with anMIP ID, which is unique in themaintenance domain. The MIP ID isrequired in the OAM operation.NOTE

To create MEPs and MIPs in a service at aport, ensure that only one MIP can be createdand the level of the MIP must be higher thanthe level of the MEP.

Related TasksA.17.5 Creating an MIP

B.10.6 Parameter Description: Ethernet Service OAMManagement_LB Enabling

This topic describes the parameters that are used for enabling the LB.


OAM Management > Ethernet Service OAM Management from the Function Tree.2. Click the Maintenance Association tab.3. Select the maintenance domain and maintenance association for the LB test.4. Choose OAM > Start LB. The LB Test dialog box is displayed.


MP ID SelectedDeselected

Deselected This parameter needs to be selected if theLB test is performed on the basis of MP IDs.

Sink MaintenancePoint MACAddress

SelectedDeselected

Selected This parameter needs to be selected if theLB test is performed on the basis of MACaddresses.



B-195



- - This parameter indicates the name of themaintenance domain for the LB test.


- - This parameter indicates the name of themaintenance association for the LB test.

SourceMaintenance PointID

- - l This parameter specifies the sourcemaintenance point in the LB test.

l Only the MEP can be set to the sourcemaintenance point.

DestinationMaintenance PointID

- - l This parameter specifies the destinationmaintenance point in the LB test.

l Only the MEP can be set to thedestination maintenance point.

l Destination Maintenance Point ID canbe set only when MP ID is selected.

DestinationMaintenance PointMAC Address

- 00-00-00-00-00-00 l This parameter specifies the MACaddress of the port where the destinationmaintenance point is located in the LBtest.

l Only the MAC address of the MEP canbe set to the MAC address of thedestination maintenance point.

l Destination Maintenance Point MACAddress can be set only when SinkMaintenance Point MAC Address.

TransmittedPacket Count

1 to 255 3 l This parameter specifies the number ofpackets transmitted each time in the LBtest.

l When the value is greater, the requiredduration is longer.

TransmittedPacket Length

64 to 1400 64 l This parameter specifies the length of atransmitted LBM packet.

l If the packet length is different, the testresult may be different. In normal cases,it is recommended that you use thedefault value.

TransmittedPacket Priority

0 to 7 7 l This parameter specifies the priority oftransmitting packets.

l 0 indicates the lowest priority, and 7indicates the highest priority. In normalcases, this parameter is set to the highestpriority.


Configuration Guide


Issue 02 (2009-10-30)


Detection Result - - This parameter indicates the relevantinformation and result of the LB test.

Related TasksA.17.7 Performing an LB Test

B.10.7 Parameter Description: Ethernet Service OAMManagement_LT Enabling

This topic describes the parameters that are used for enabling the LT.


OAM Management > Ethernet Service OAM Management from the Function Tree.2. Click the Maintenance Association tab.3. Select the maintenance domain and maintenance association for the LT test.4. Choose OAM > Start LT. The LT Test dialog box is displayed.

Test Node ParametersParameter Value Range Default Value Description


- - This parameter indicates the name of themaintenance domain for the LT test.


- - This parameter indicates the name of themaintenance association for the LT test.

SourceMaintenance PointID

- - l This parameter specifies the sourcemaintenance point in the LT test.

l Only the MEP can be set to the sourcemaintenance point.

DestinationMaintenance PointMAC Address

- 00-00-00-00-00-00 l This parameter specifies the MACaddress of the board where thedestination maintenance point is located.

l Only the MAC address of the MEP canbe set to the MAC address of thedestination maintenance point.



B-197

Parameters for the Test ResultParameter Value Range Default Value Description

SourceMaintenance Point

- - This parameter indicates the sourcemaintenance point in the LT test.

DestinationMaintenance PointID/MAC

- - This parameter indicates the MAC addressof the port where the destinationmaintenance point is located in the LT test.

ResponseMaintenance PointID/MAC

- - This parameter indicates the MAC addressof the port where the respondingmaintenance point is located in the LT test.

Hop Count 1 to 64 - l This parameter indicates the number ofhops from the source maintenance pointto the responding maintenance point or tothe destination maintenance point in theLT test.

l The number of hops indicates theadjacent relation between the respondingmaintenance point to the sourcemaintenance point. The number of hopsincreases by one when a responding pointoccurs on the link from the sourcemaintenance point to the destinationmaintenance point.

Test Result --

- This parameter indicates the result of the LTtest.

Related TasksA.17.8 Performing an LT Test

B.10.8 Parameter Description: Ethernet Port OAMManagement_OAM Parameter

This topic describes the OAM parameters that are related to Ethernet ports.


OAM Management > Ethernet Port OAM Management from the Function Tree.2. Click the OAM Parameter tab.


Configuration Guide


Issue 02 (2009-10-30)


Port - - This parameter indicates the correspondingport.

Enable OAMProtocol

EnabledDisabled

Disabled l This parameter indicates or specifieswhether to enable the OAM protocol.

l After the OAM protocol is enabled, thecurrent Ethernet port starts to use thepreset mode to create the OAMconnection with the opposite end.

OAM WorkingMode

ActivePassive

Active l This parameter indicates or specifies theworking mode of the OAM.

l The port whose OAM working mode isset to Active can initiate the OAMconnection.

l The port whose OAM working mode isset to Passive can only wait for theopposite end to send the OAMconnection request.

l The OAM working mode of theequipment at only one end can bePassive.

Link EventNotification

EnabledDisabled

Enabled l This parameter indicates or specifieswhether the local link events can benotified to the opposite end.

l If the alarms caused by link events can bereported, that is, if the number ofperformance events (for example, errorframe period, error frame, error framesecond, and error frame signal cycle) atthe local end exceeds the presetthreshold, these performance events arenotified to the port at the opposite endthrough the link event notificationfunction.




B-199


Remote SideLoopbackResponse

DisabledEnabled

Disabled l This parameter indicates or specifieswhether the port responds to the remoteloopback.

l Remote loopback indicates that the localOAM entity transmits packets to theremote OAM entity for loopback. Thelocal OAM entity can locate the fault andtest the link performance throughloopback data analysis.

l If a port does not support remoteloopback response, this port does notrespond to the loopback request from theremote port regardless of the OAM portstatus.

Loopback Status Non-LoopbackInitiate Loopback atLocalRespond Loopbackof Remote

- This parameter indicates the loopback statusat the local end.NOTE

Loopback Status is valid only after you chooseOAM > Enable Remote Loopback.

OAM DiscoveryStatus

FAULTACTIVE_SEND_LOCALPASSIVE_WAITSEND_LOCAL_REMOTESEND_LOCAL_REMOTE_OKSEND_ANY

- This parameter indicates the OAMdiscovery status at the local end.

Port TransmitStatus

FWDDISCARD

- l This parameter indicates the status oftransmitting packets at the local end.

l When a port is in the FWD state, the portforwards the non-OAM packets. When aport is in the DISCARD state, the portdiscards the non-OAM packets.

Port Receive Status FWDDISCARDLB

- l This parameter indicates the status ofreceiving packets at the local end.

l In the FWD state, the port forwards thenon-OAM packets. In the LB state, theport loopback the non-OAM packets. Inthe DISCARD state, the port discards thenon-OAM packets.


Configuration Guide


Issue 02 (2009-10-30)

Related TasksA.18.1 Enabling the OAM Auto-Discovery FunctionA.18.2 Enabling the Link Event Notification

B.10.9 Parameter Description: Ethernet Port OAMManagement_OAM Error Frame Monitoring

This topic describes the parameters that are used for monitoring the OAM error frames at theEthernet port.


OAM Management > Ethernet Port OAM Management from the Function Tree.

2. Click the OAM Error Frame Monitor tab.




Error FrameMonitor Window(ms)

1000 to 60000, instep of 100

1000 This parameter specifies the duration ofmonitoring error frames.

Error FrameMonitor Threshold(frame)

1 to 4294967295, instep of 1

1 l This parameter specifies the threshold ofmonitoring error frames.

l Within the specified value of ErrorFrame Monitor Window(ms), if thenumber of error frames on the linkexceeds the preset value of Error FrameMonitor Threshold(frame), an alarm isreported.

Error FramePeriod Window(frame)

1488 to 892800000,in step of 1

892800000 This parameter specifies the window ofmonitoring the error frame period.

Error FramePeriod Threshold(frame)

- 1 l This parameter specifies the threshold ofmonitoring the error frame period.

l Within the specified value of ErrorFrame Period Window(frame), if thenumber of error frames on the linkexceeds the preset value of Error FramePeriod Threshold(frame), an alarm isreported.

Error FrameSecond Window(s)

10 to 900, in step of1

60 This parameter specifies the time window ofmonitoring the error frame second.



B-201


Error FrameSecond Threshold(s)

10 to 900, in step of1

1 l This parameter specifies the threshold ofmonitoring error frame seconds.

l If any error frame occurs in one second,this second is called an errored framesecond. Within the specified value ofError Frame Second Window(s), if thenumber of error frames on the linkexceeds the preset value of Error FrameSecond Threshold(s), an alarm isreported.

Error FrameSignal PeriodicMonitor Window(Entries)

1 to 60, in step of 1 1 This parameter specifies the window ofmonitoring the error frame signal period.

Error FrameSignal PeriodicMonitor Threshold(Entries)

1 to 7500000000, instep of 1

1 l This parameter specifies the threshold ofmonitoring the error frame signal period.

l Within the specified value of ErrorFrame Signal Periodic MonitorWindow(Entries), if the number of errorsignals exceeds the preset value of ErrorFrame Signal Periodic MonitorThreshold(Entries), an alarm isreported.

Related TasksA.18.3 Modifying the OAM Error Frame Monitoring Threshold

B.11 QoS ParametersThis topic describes the parameters that are related to QoS.

B.11.1 Parameter Description: Diffserv Domain ManagementThis topic describes the parameters that are used for managing DiffServ domains.

B.11.2 Parameter Description: DiffServ Domain Management_CreateThis parameter describes the parameters that are used for creating DiffServ (DS) domains.

B.11.3 Parameter Description: DiffServ Domain Applied Port_ModificationThis topic describes the parameters that are used for changing DiffServ (DS) domain appliedports.

B.11.4 Parameter Description: Policy ManagementThis topic describes the parameters that are related to port policies.

B.11.5 Parameter Description: Port PolicyThis topic describes the parameters that are used for creating port policies.

B.11.6 Parameter Description: Port Policy_Traffic Classification Configuration


Configuration Guide


Issue 02 (2009-10-30)

This parameter describes the parameters that are used for creating traffic classification.

B.11.7 Parameter Description: Port Shaping Management_CreationThis topic describes the parameters that are used for creating port shaping management tasks.

B.11.1 Parameter Description: Diffserv Domain ManagementThis topic describes the parameters that are used for managing DiffServ domains.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Diffserv Domain Management from the Function Tree.


Mapping Relation ID 1 to 8 1 This parameter indicatesthe ID of the mappingrelation between DiffServdomains.

Mapping Relation Name - Default Map This parameter indicatesthe name of the mappingrelation between DiffServdomains.

NOTE

If one default DiffServ domain exists on the OptiX RTN equipment, Mapping Relation ID is set to 1, andMapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain.The default Diffserv domain cannot be modified and deleted.

Parameters for Ingress Mapping RelationParameter Value Range Default Value Description

CVLAN 0 to 7 - l This parameterindicates the priority ofthe C-VLAN of theingress packets.

l C-VLAN indicates theclient-side VLAN, andthe value 7 indicates thehighest priority.



B-203


SVLAN 0 to 7 - l This parameterindicates the priority ofthe S-VLAN of theingress packets.

l S-VLAN indicates theserver-side VLAN, andthe value 7 indicates thehighest priority.

IP DSCP 0 to 63 - l This parameterindicates the DSCPpriority of the IPaddresses of the ingresspackets.

l The differentiatedservices code point(DSCP) refers to bits0-5 of the differentiatedservices (DS) field inthe packet and indicatesthe service class anddiscarding priority ofthe packet.


Configuration Guide


Issue 02 (2009-10-30)


PHB BEAF1AF2AF3AF4EFCS6CS7

- l This parameterindicates the per-hopbehavior (PHB) serviceclass of the DiffServdomain.

l The PHB service classrefers to the forwardingbehavior of theDiffServ node on thebehavior aggregate(BA) operation. Theforwarding behaviorcan meet the specificrequirements.

l The PHB serviceclasses are BE, AF1,AF2, AF3, AF4, EF,CS6, and CS7. Thepriorities (C_VLANpriority, S_VLANpriority, and DSCPvalue) contained in thepackets of the DiffServdomain and the eightPDB service classesmeet the requirementsof the specified ordefault mappingrelation.

NOTEThe AF1 is classified intothree sub service classes,namely, AF11, AF12, andAF13, only one of which isvalid. It is the same casewith the AF2, AF3, andAF4.



B-205

Parameters for Egress Mapping RelationParameter Value Range Default Value Description


- l This parameterindicates the PHBservice class of theDiffServ domain.

l The PHB service classrefers to the forwardingbehavior of theDiffServ node on thebehavior aggregate(BA) operation. Theforwarding behaviorcan meet the specificrequirements.

l The PHB serviceclasses are BE, AF1,AF2, AF3, AF4, EF,CS6, and CS7. Thepriorities (C_VLANpriority, S_VLANpriority, and DSCPvalue) contained in thepackets of the DiffServdomain and the eightPDB service classesmeet the requirementsof the specified ordefault mappingrelation.


CVLAN 0 to 7 - l This parameterindicates the priority ofthe C-VLAN of theegress packets.



Configuration Guide


Issue 02 (2009-10-30)


SVLAN 0 to 7 - l This parameterindicates the priority ofthe S-VLAN of theegress packets.


IP DSCP 0 to 63 - l This parameterindicates the DSCPpriority of the IPaddresses of the ingresspackets.

l The DSCP refers to bits0-5 of the DS field inthe packet and indicatesthe service class anddiscarding priority ofthe packet.


Port - - This parameter indicatesthe port that uses theDiffServ domain.

Related TasksA.16.8 Querying the DS Domain of a Port

B.11.2 Parameter Description: DiffServ DomainManagement_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS

Management > Diffserv Domain Management from the Function Tree.2. Click Create. The Create DS Mapping Relation dialog box is displayed.



B-207


Mapping Relation ID 2 to 8 2 This parameter specifiesthe ID of the mappingrelation of a DS domain.

Mapping Relation Name - - This parameter specifiesthe name of the mappingrelation of a DS domain.

Packet Type cvlansvlanip-dscp

cvlan l This parameterspecifies the type of thepacket.

l The packets trusted bythe OptiX RTN 910 arethe C_VLAN,S_VLAN and IP DSCPpackets that contain theC_VLAN priority,S_VLAN priority, orDSCP value. Bydefault, the untrustedpackets are mapped tothe BE service class forbest-effort forwarding.

NOTEThe E-Line point-to-pointtransparent transmissionservice supports only themapping from DSCPpackets to the PHB serviceclass.

NOTE

If one default DS domain exists on the OptiX RTN equipment, Mapping Relation ID is set to 1, MappingRelation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain. Thedefault DS domain cannot be modified and deleted.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for Ingress Mapping RelationParameter Value Range Default Value Description

CVLAN 0 to 7 - l This parameterspecifies the C-VLANpriority of the ingresspackets.


SVLAN 0 to 7 - l This parameterspecifies the S-VLANpriority of the ingresspackets.


IP DSCP 0 to 63 - l This parameterspecifies the DSCPpriority of the IPaddresses of the ingresspackets.




B-209



- l This parameterindicates the PHBservice class of the DSdomain.

l The PHB service classrefers to the forwardingbehavior of the DSnode on the behavioraggregate (BA)operation. Theforwarding behaviorcan meet the specificrequirements.

l The PHB serviceclasses are BE, AF1,AF2, AF3, AF4, EF,CS6, and CS7. Thepriorities (C_VLANpriority, S_VLANpriority, and DSCPvalue) contained in thepackets of the DSdomain and the eightPDB service classesmeet the requirementsof the specified ordefault mappingrelation.



Configuration Guide


Issue 02 (2009-10-30)

Parameters for Egress Mapping RelationParameter Value Range Default Value Description


- l This parameterindicates the PHBservice class of the DSdomain.

l The PHB service classrefers to the forwardingbehavior of the DSnode on the behavioraggregate (BA)operation. Theforwarding behaviorcan meet the specificrequirements.

l The PHB serviceclasses are BE, AF1,AF2, AF3, AF4, EF,CS6, and CS7. Thepriorities (C_VLANpriority, S_VLANpriority, and DSCPvalue) contained in thepackets of the DSdomain and the eightPDB service classesmeet the requirementsof the specified ordefault mappingrelation.


CVLAN 0 to 7 - l This parameterspecifies the C-VLANpriority of the egresspackets.




B-211


SVLAN 0 to 7 - l This parameterspecifies the S-VLANpriority of the egresspackets.


IP DSCP 0 to 63 - l This parameterspecifies the DSCPpriority of the IPaddresses of the egresspackets.



Board - - This parameter specifiesthe board that uses themapping relationsbetween DS domains.

Available Port - - This parameter displaysthe available port list fromwhich you can select theport that uses the mappingrelations between DSdomains.


Configuration Guide


Issue 02 (2009-10-30)


Selected Port - - l This parameterdisplays the selectedport list. The ports inthe list use the mappingrelations between DSdomains.

l Encapsulation Typedetermines the packettypes that the porttrusts. In the case of aUNI port, set PacketType to cvlan or ip-dscp. In the case of anNNI port, set PacketType to svlan.

Related TasksA.16.1 Creating a DS Domain

B.11.3 Parameter Description: DiffServ Domain AppliedPort_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain appliedports.


Management > Diffserv Domain Management from the Function Tree.2. Select the DS domain to be changed in the main interface.3. Click the Apply Port tab.4. Click Modify.

Parameters for Configuring the Applied PortsParameter Value Range Default Value Description

Mapping Relation Name - - This parameter indicatesthe name of the mappingrelation of a DS domain.



B-213


Packet Type cvlansvlanip-dscp

cvlan l This parameterspecifies the type of thepacket.

l The packets trusted bythe OptiX RTN 910 arethe C_VLAN,S_VLAN and IP DSCPpackets that contain theC_VLAN priority,S_VLAN priority, orDSCP value. Bydefault, the untrustedpackets are mapped tothe BE service class forbest-effort forwarding.

NOTEThe E-Line point-to-pointtransparent transmissionservice supports only themapping from DSCPpackets to the PHB serviceclass.

Board - - This parameter specifiesthe board where the port islocated.

Available Port - - This parameter indicatesthe available port.

Selected Port - - This parameter indicatesthe selected port.The selected port isapplied to the DS domain.

NOTE

If one default DS domain exists on the OptiX RTN 910, Mapping Relation ID is set to 1, and Mapping RelationName is set to Default Map. If these parameters are not set, all the ports belong to the domain. The port appliedto the default DS domain cannot be modified.

Related TasksA.16.2 Changing the Ports That Use the DS Domain

B.11.4 Parameter Description: Policy ManagementThis topic describes the parameters that are related to port policies.


Configuration Guide


Issue 02 (2009-10-30)

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Configuration > QoSManagement > Policy Management from the Function Tree.


Policy ID 1 to 36 - l This parameterindicates the policy IDof the port.

l The OptiX RTN 910supports a maximumnumber of 36 policies.

Policy Name - - This parameter indicatesor specifies the policyname of the port.



B-215


CoS CS7CS6EFAF4AF3AF2AF1BE

- l The BE, AF1, AF2,AF3, AF4, EF, CS6,and CS7 service classesrespectively map eightqueuing entities. TheOptiX RTN 910provides different QoSpolicies for the queuesat different serviceclasses.

l CS6-CS7: indicates thehighest service grade,which is mainlyinvolved in signalingtransmission.

l EF: indicates fastforwarding. Thisservice class isapplicable to the trafficwhose delay is smalland packet loss ratio islow, for example, voiceand video services.

l AF1-AF4: indicatesassured forwarding.This service class isapplicable to the trafficthat requires rateguarantee but does notrequire delay or jitterlimit.

l BE: indicates that thetraffic is forwarded inbest-effort mannerwithout specialprocessing.


Configuration Guide


Issue 02 (2009-10-30)



SPWRR

CS7, CS6, EF, BE: SPAF4, AF3, AF2, AF1:WRR

l The strict priority (SP)scheduling algorithm isdesigned for the keyservices. Oneimportantcharacteristic of the keyservices is that higherpriorities are requiredto minimize theresponse delay in thecase of congestionevents.

l The weighted roundrobin (WRR)scheduling algorithmdivides each port intomultiple output sub-queues. The pollingscheduling isperformed among theoutput sub-queues toensure that each sub-queue has a certainperiod of service time.

l The OptiX RTN 910supports the setting ofthe SP+WRRscheduling algorithmof the CoS queueaccording to therequirement, andprovides one or morequeues that complywith the SP algorithm.Except for the defaultvalue, however, thevalue of the WRRscheduling algorithmand the value of the SPscheduling algorithmcannot be interleaved.That is, except for thedefault value,Grooming PoliceAfter Reloading canbe changed from SP toWRR according to thequeue priorities in adescending order(CS7-BE).



B-217



Policy Weight(%) 1 to 100 25 l This parameterspecifies the weight ofthe policy in the WRRqueue. The weightindicates thepercentage of thebandwidth resourcesobtained by the WRRqueue.

l This parameter can beset only whenGrooming PoliceAfter Reloading is setto WRR.


Bandwidth Limit DisabledEnabled

Disabled l This parameterindicates or specifieswhether the trafficshaping function isenabled for the PHBservice class queues inthe egress direction.

l CIR (kbit/s), PIR(kbit/s), CBS (byte),and PBS (byte) can beset only whenBandwidth Limit isset to Enabled.



Configuration Guide


Issue 02 (2009-10-30)


CIR(kbit/s) - - l In the case that nopackets exist in theegress queue: When therate of the packets is notmore than the CIR,these packets directlyenter the egress queue.

l In the case that certainpackets exist in theegress queue: Thepackets whose ratepasses the restriction ofthe PIR directly enterthe egress queue, whichforwards the packets tothe next port at the CIR.


PIR(kbit/s) - - l In the case that nopackets exist in theegress queue: If the rateof the packets is morethan the CIR but is notmore than the PIR, thepackets whose rate ismore than the CIR enterthe egress queue, whichforwards the packets tothe next port at the CIR.If the rate of the packetsis more than the PIR,the packets are directlydiscarded.





B-219


CBS(byte) - - l If the rate of the packetsis not more than theCIR during a certainperiod, the burstpackets are directlytransmitted. Themaximum traffic of theburst packets isdetermined by theCBS.


PBS(byte) - - l If the rate of the packetsis more than the CIRbut is not more than thePIR during a certainperiod, the burstpackets enter the egressqueue. The maximumtraffic of the burstpackets is determinedby the PBS.


Related TasksA.16.5 Setting the Port That Uses the Port PolicyA.16.7 Querying the Port Policy

B.11.5 Parameter Description: Port PolicyThis topic describes the parameters that are used for creating port policies.


Management > Policy Management from the Function Tree.2. Click the CoS Queue Configuration tab.3. Click New. The Create Port Policy dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)


Policy ID 1 to 36 - l This parameterspecifies the policy IDof the port.

l The OptiX RTN 910supports a maximumnumber of 36 policies.

Automatically Assign SelectedDeselected

Deselected This parameter specifieswhether to automaticallyallocate the policy ID ofthe port policy. After thisparameter is selected, thesystem automaticallyallocates the policy ID,and then the policy IDcannot be set manually.

Policy Name - - This parameter specifiesthe policy name of theport.



B-221


CoS CS7CS6EFAF4AF3AF2AF1BE

- l The BE, AF1, AF2,AF3, AF4, EF, CS6,and CS7 service classesrespectively map eightqueuing entities. TheOptiX RTN 910provides different QoSpolicies for the queuesat different serviceclass.

l CS6-CS7: indicates thehighest service grade,which is mainlyinvolved in signalingtransmission.

l EF: indicates fastforwarding. Thisservice class isapplicable to the trafficwhose delay is smalland packet loss ratio islow, for example, voiceand video services.

l AF1-AF4: indicatesassured forwarding.This service class isapplicable to the trafficthat requires rateguarantee but does notrequire delay or jitterlimit.

l BE: indicates that thetraffic is forwarded inbest-effort mannerwithout specialprocessing.


Configuration Guide


Issue 02 (2009-10-30)



SPWRR

CS7, CS6, EF, BE: SPAF4, AF3, AF2, AF1:WRR

l The strict priority (SP)scheduling algorithm isdesigned for the keyservices. Oneimportantcharacteristic of the keyservices is that higherpriorities are requiredto minimize theresponse delay in thecase of congestionevents.

l The weighted roundrobin (WRR)scheduling algorithmdivides each port intomultiple output sub-queues. The pollingscheduling isperformed among theoutput sub-queues toensure that each sub-queue has a certainperiod of service time.

l The OptiX RTN 910supports the setting ofthe SP+WRRscheduling algorithmof the CoS queueaccording to therequirement, andprovides one or morequeues that complywith the SP algorithm.Except for the defaultvalue, however, thevalue of the WRRscheduling algorithmand the value of the SPscheduling algorithmcannot be interleaved.That is, except for thedefault value,Grooming PoliceAfter Reloading canbe changed from SP toWRR according to thequeue priorities in adescending order(CS7-BE).



B-223



Policy Weight(%) 1 to 100 25 l This parameterspecifies the weight ofthe policy in the WRRqueue. The weightindicates thepercentage of thebandwidth resourcesobtained by the WRRqueue.

l This parameter can beset only whenGrooming PoliceAfter Reloading is setto WRR.



Disabled l This parameterindicates or specifieswhether the trafficshaping function isenabled for the PHBservice class queues.




Configuration Guide


Issue 02 (2009-10-30)










B-225






Related TasksA.16.3 Creating a Port Policy

B.11.6 Parameter Description: Port Policy_Traffic ClassificationConfiguration

This parameter describes the parameters that are used for creating traffic classification.


Management > Policy Management from the Function Tree.2. Click the Traffic Classification Configuration tab.3. Click New. The Create Traffic Classification dialog box is displayed.


Configuration Guide


Issue 02 (2009-10-30)


Traffic Classification ID 1 to 1024 - This parameter specifiesthe ID of the trafficclassification.

ACL Action PermitDeny

Permit l The access control list(ACL) determineswhether to forward ordiscard the packets thatenter the port accordingto the specifiedmatching rules.

l When this parameter isset to Permit, the ACLon the ingress sidefilters the packets thatenter the port. Only thepackets that match thespecified rules can bereceived by the port.

l When this parameter isset to Deny, ACLprocessing is notperformed for thepackets over the ingressport.

Ingress ParametersParameter Value Range Default Value Description

Logical RelationBetween Matched Rules

And And l This parameterspecifies the logicalrelationship betweenthe traffic classificationmatching rules.

l The OptiX RTN 910supports the setting ofthe logical ANDbetween multiplematching rules.



B-227


Match Type DSCP ValueCVlan IDCVlan prioritySVlan IDSVlan priority

- l After you click Add orDelete, complex trafficclassification can beperformed on the trafficthat enters the ingressport according to thepreset matching rules.

l In the case a specificservice, complex trafficclassification can bedivided into basictraffic types accordingto the DSCP value,C_VLAN ID,C_VLAN priority,S_VLAN ID, orS_VLAN priority.Traffic type is based onthe associated Ethernetpackets. Therefore, thisparameter is setaccording to the packettype and the planninginformation.

Match Value DSCP Value: 0 to 63CVlan ID: 1 to 4094CVlan priority: 0 to 7SVlan ID: 1 to 4094SVlan priority: 0 to 7

- l If the matching value ofthe packets is the sameas the preset MatchValue, the packetsmatch the rules ofcomplex trafficclassification.



Configuration Guide


Issue 02 (2009-10-30)


CoS -CS7CS6EFAF4AF3AF2AF1BE

- l This parameterspecifies the PHBservice class queuemapped by the trafficclassification packets.

l If this parameter is setto empty (-), the trafficclassification packetsmap the PHB serviceclass queue accordingthe mapping relationspecified in the topicabout Diffserv domainmanagement.



Enabled l This parameterindicates or specifieswhether the CARoperation is performedfor the flow in theingress direction.





B-229


CIR(kbit/s) - - l When the rate of thepackets is not morethan the CIR, thepackets are markedblue and pass the CARpolicing. These packetsare first forwarded inthe case of networkcongestion.

l When the rate of thepackets is more than theCIR but not more thanthe PIR, the packetswhose rate is more thanthe CIR can pass therestriction of the CARand are marked yellow.The processing methodof the packets markedyellow can be set to"Pass" or "Remark"."Remark" indicatesthat the packets aremapped into anotherspecified queue of ahigher priority (this isequal to changing thepriority of the packets)and then forwarded tothe next port. If anetwork congestionevent occurs again, thepackets marked yellowcan be processedaccording to the newpriority.



Configuration Guide


Issue 02 (2009-10-30)


PIR(kbit/s) - - l When the rate of thepackets is more than thePIR, the packets thatexceed the raterestriction are markedred and directlydiscarded.

l When the rate of thepackets is more than theCIR but not more thanthe PIR, the packetswhose rate is more thanthe CIR can pass therestriction of the CARand are marked yellow.The processing methodof the packets markedyellow can be set to"Pass" or "Remark"."Remark" indicatesthat the packets aremapped into anotherspecified queue of ahigher priority (this isequal to changing thepriority of the packets)and then forwarded tothe next port. If anetwork congestionevent occurs again, thepackets marked yellowcan be processedaccording to the newpriority.




B-231


CBS(byte) - - l During a certain period,if the rate of the packetswhose processingmethod is marked"Pass" is not more thanthe CIR, certain burstpackets are allowed andcan be first forwardedin the case of networkcongestion. Themaximum traffic of theburst packets isdetermined by theCBS.


PBS(byte) - - l During a certain period,if the rate of the packetswhose processingmethod is marked"Pass" is more than theCIR but not more thanthe PIR, certain burstpackets are allowed andmarked yellow. Themaximum traffic of theburst packets isdetermined by the PBS.


Coloration Mode Color Blindness Color Blindness l This parameterspecifies the CARoperation performed bythe equipment on thepackets. The packetsare dyed according tothe result of the CARoperation. The dyingrule is determined bythe comparisonbetween the rate of thepackets and the presetCAR value.

l The OptiX RTN 910supports ColorBlindness only.


Configuration Guide


Issue 02 (2009-10-30)


Packet Color RedYellowGreen

- Packets can be dyed inthree colors: red, yellow,and green. The packets inred are first discarded.

Handling Mode DiscardPassRemark

- l This parameterspecifies the method ofhandling the packets.

l Discard: The packetsare discarded.

l Pass: The packets areforwarded.

l Remark: The packetsare remarked."Remark" indicatesthat the packets aremapped into anotherspecified queue of ahigher priority (this isequal to changing thepriority of the packets)and then forwarded tothe next port.

Relabeled CoS CS7CS6EFAF4AF3AF2AF1BE

- If the handling method isset to "Remark", you canreset the CoS of thepackets.



B-233

Egress ParametersParameter Value Range Default Value Description

Bandwidth Limit DisabledEnable

Enable l This parameterindicates or specifieswhether the trafficshaping is performed inthe egress function.







Configuration Guide


Issue 02 (2009-10-30)









B-235




Related TasksA.16.4 Creating the Traffic

B.11.7 Parameter Description: Port Shaping Management_CreationThis topic describes the parameters that are used for creating port shaping management tasks.


Management > Port Shaping Management from the Function Tree.

2. Click New.

Parameters for Port Shaping Management


Slot No. - - This parameter specifiesthe slot ID.

Port - - This parameter specifiesthe port.

CIR (kbit/s) - - If the traffic shapingfunction is enabled, OptiXRTN 910 processes thepackets in the bufferqueue through thefollowing methods whenno packets are available inthe queue.l If the rate of the packets

is not higher than the

CBS (kbyte) - -

PIR (kbit/s) - -


Configuration Guide


Issue 02 (2009-10-30)


PBS (kbyte) - - specified CIR, thepackets are forwardeddirectly to the next port.

l When the rate of thepackets is higher thanthe CIR but is nothigher than the PIR, thepackets whose rate ishigher than the CIRenter the buffer queue,which forwards thepackets to the next portat the CIR.

l When the rate of thepackets is higher thanthe PIR, the packets arediscarded first in thecase of networkcongestion.

l If the rate of the packetsis not higher than theCIR during a certainperiod of time, a part ofthe burst packets aredirectly transmitted.The maximum trafficof the burst packets isdetermined by theCBS.

l If the rate of the packetsis higher than the CIRbut is not higher thanthe PIR during a certainperiod of time, a part ofthe burst packets enterthe buffer queue. Themaximum traffic of theburst packets isdetermined by the PBS.

When certain packetsexist in the buffer queue,the packets whose rate ishigher than the PIRdirectly enter the bufferqueue, which forwards the



B-237


packets to the next port atthe CIR.

Related TasksA.16.6 Configuring Port Shaping

B.12 RMON ParametersThis topic describes the parameters that are related to RMON performances.

B.12.1 Parameter Description: RMON Performance_Statistics GroupThis topic describes the parameters that are related to RMON statistics groups.

B.12.2 Parameter Description: RMON Performance_History GroupThis topic describes the parameters that are related to RMON history groups.

B.12.3 Parameter Description: RMON Performance_History Control GroupThis topic describes the parameters that are related to RMON history control groups.

B.12.4 Parameter Description: RMON Performance_RMON SettingThis topic describes the parameters that are related to RMON setting.

B.12.1 Parameter Description: RMON Performance_StatisticsGroup

This topic describes the parameters that are related to RMON statistics groups.


Performance > RMON Performance from the Function Tree.

2. Click the Statistics Group tab.

Parameters


Object - - This parameter specifies the object to bemonitored.

Sampling Period 5 to 150 5 l This parameter specifies the duration ofthe monitoring period.

l This parameter is valid only whenHistory Table Type is set to CustomPeriod 1 and Custom Period 2.


Configuration Guide


Issue 02 (2009-10-30)


DisplayAccumulatedValue

SelectedDeselected

Deselected l This parameter specifies the method ofdisplaying the performance events.

l If this parameter is not selected, thedisplayed value is an incrementcompared to the value that is collected inlast sampling period and stored in theregister.

l If this parameter is selected, the displayedvalue is an absolute value that is currentlystored in the register.

Display Mode GraphicsList

List l This parameter specifies the method ofdisplaying the performance events.

l If this parameter is set to Graphics, thenumber of performance events to bemonitored at each time cannot be morethan 10, and the unit should be the same.

Legend ColorDescription

- l This parameter indicates the descriptionof different colors.

l This parameter is valid only whenDisplay Mode is set to Graphics.

Event - - l This parameter indicates the queriedperformance events.

l This parameter is valid only whenDisplay Mode is set to List.

Related TasksA.19.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port

B.12.2 Parameter Description: RMON Performance_History GroupThis topic describes the parameters that are related to RMON history groups.


Performance > RMON Performance from the Function Tree.2. Click the History Group tab.


Object - - The parameter indicates the object to bemonitored.



B-239


Ended - - This parameter specifies the start time andend time of the monitoring period.

History TableType

30-Second30-MinuteCustom Period 1Custom Period 2

30-Second This parameter specifies the monitoringperiod.

Display Mode GraphicsList

List l This parameter specifies the method ofdisplaying the performance events.

l If this parameter is set to Graphics, thenumber of performance events to bemonitored at each time cannot be morethan 10, and the unit should be the same.

Legend ColorDescription

- l This parameter indicates the descriptionof different colors.

l This parameter is valid only whenDisplay Mode is set to Graphics.

Event - - l This parameter indicates the queriedperformance events.

l This parameter is valid only whenDisplay Mode is set to List.

Statistical Item - - This parameter indicates the performanceitems to be monitored.

Statistical Value - - This parameter indicates the statistical valueof the monitored performance items.

Time Flag - - This parameter indicates the time point ofeach performance event.

B.12.3 Parameter Description: RMON Performance_HistoryControl Group

This topic describes the parameters that are related to RMON history control groups.

Navigation PathSelect the NE from the Object Tree in the NE Explorer. Choose Performance > RMON HistoryControl.


Configuration Guide


Issue 02 (2009-10-30)

Parameters


30-Second EnabledDisabled

Disabled This parameter indicates or specifieswhether to enable the 30-Secondmonitoring function.

30-Minute EnabledDisabled

Enabled This parameter indicates or specifieswhether to enable the 30-Minutemonitoring function.

Custom Period 1 EnabledDisabled

Disabled This parameter indicates or specifieswhether to enable Custom Period 1.


Disabled This parameter indicates or specifieswhether to enable Custom Period 2.

History RegisterCount(1-50)

1 to 50 166(Custom Period 2)

This parameter indicates or specifies thequantity of the history registers.

Period Length(300to 43200 seconds, amultiple of 30)

300 to 43200 900 l This parameter indicates or specifies themonitoring period in Custom Period 1.

l The value must be an integer multiple of30.

Period Length(300to 86400 seconds, amultiple of 30)

300 to 86400 86400 l This parameter indicates or specifies themonitoring period in Custom Period 2.

l The value must be an integer multiple of30.

Related TasksA.19.3 Configuring a History Control Group

B.12.4 Parameter Description: RMON Performance_RMON SettingThis topic describes the parameters that are related to RMON setting.

Navigation Pathl Select the corresponding board from the Object Tree in the NE Explorer. Choose

Performance > RMON Performance from the Function Tree.

l Click the RMON Setting tab.

Object Parameters


Object - - This parameter indicates the object to becollected.



B-241



- This parameter indicates or specifieswhether to enable the 30-Secondmonitoring function.NOTE

In the case of Object, 30-Second cannot be set.


Disabled l This parameter indicates or specifieswhether to enable the 30-Minutemonitoring function.

l In RMON History Control Group ofthe NE, if 30-Minute is set to Disabled,Not Supported is displayed for thisparameter.


- l This parameter indicates or specifieswhether to enable the monitoringfunction based on Custom Period 1.

l In RMON History Control Group ofthe NE, if Custom Period 1 is set toDisabled, Not Supported is displayedfor this parameter.


- l This parameter indicates or specifieswhether to enable the monitoringfunction based on Custom Period 2.

l In RMON History Control Group ofthe NE, if Custom Period 2 is set toDisabled, Not Supported is displayedfor this parameter.

Event ParametersParameter Value Range Default Value Description

Event - - This parameter indicates the performanceevent to be monitored.


Disabled This parameter indicates or specifieswhether to enable the monitoring functionbased on 30-Second.


- This parameter indicates or specifieswhether to enable the 30-Minutemonitoring function.


Disabled This parameter indicates or specifieswhether to enable the monitoring functionbased on Custom Period 1.


Configuration Guide


Issue 02 (2009-10-30)



Disabled This parameter indicates or specifieswhether to enable the monitoring functionbased on Custom Period 2.

Threshold Detect Report AllDo Not DetectReport Only theUpper ThresholdReport Only theLower Threshold

Report All l This parameter indicates or specifies thethreshold detection method.

l If the number of detected events reachesthe preset threshold, the events arereported to the NMS. Otherwise, theevents are not reported to the NMS.

l If an event does not support thisparameter, Not Supported is displayed.

Upper Threshold 0 to922337203685477580

- This parameter indicates or specifies theupper threshold. If the number ofperformance events exceeds the presetupper threshold, the correspondingperformance events are reported.

Lower Threshold 0 to922337203685477580

- This parameter indicates or specifies thelower threshold. If the number ofperformance events is less than the presetlower threshold, the correspondingperformance events are reported.

Threshold Unit - - This parameter indicates the unit of eachthreshold of the performance events.

Related TasksA.19.2 Configuring an Alarm Group for an Ethernet PortA.19.4 Browsing the Performance Data in the History Group of an Ethernet Port

B.13 Parameters for the Orderwire and Auxiliary InterfacesThis topic describes the parameters that are related to the orderwire and auxiliary interfaces.

B.13.1 Parameter Description: Orderwire_GeneralThis topic describes the parameters that are used for general orderwire features.

B.13.2 Parameter Description: Orderwire_AdvancedThis topic describes the parameters that are used for advanced orderwire features.

B.13.3 Parameter Description: Orderwire_F1 Data PortThis topic describes the parameters that are used for F1 data ports.

B.13.4 Parameter Description: Orderwire_Broadcast Data PortThis topic describes the parameters that are used for broadcast data ports.

B.13.5 Parameter Description: Environment Monitoring Interface



B-243

This topic describes the parameters that are used for environment monitoring interfaces.

B.13.1 Parameter Description: Orderwire_GeneralThis topic describes the parameters that are used for general orderwire features.

Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >

Orderwire from the Function Tree.2. Click the General tab.


Call Waiting Time(s)

1 to 9 9 l This parameter indicates the waiting timeafter the local station dials the number. Ifthe calling station does not receive theresponse message from the called stationwithin the call waiting time, itautomatically removes thecommunication connection.

l If less than 30 nodes exist in the orderwiresubnet, it is recommended that you setthis parameter to five seconds. If morethan 30 nodes exist in the orderwiresubnet, it is recommended that you setthis parameter to nine seconds.

l The call waiting time should be set to thesame for all the NEs.

Dialling Mode PulseDual-ToneFrequency

Dual-ToneFrequency

This parameter indicates the dialling modeof the orderwire phone.


Configuration Guide


Issue 02 (2009-10-30)


Telephone No. - 888 l This parameter specifies the telephonenumber of the network-wide orderwireconference call.

l When a OptiX RTN 910 dials thetelephone number 888, the orderwirephones of all the NEs on the orderwiresubnet ring. When a OptiX RTN 910receives the call, the orderwire phones onthe other NEs do not ring. In this case, theorderwire point-to-multipoint group callchanges to a point-to-point call betweentwo NEs.

l The telephone number of the orderwireconference call should be the same for allthe nodes on the same subnet.

l The telephone number of the orderwireconference call must have the samelength as the telephone number of theorderwire phone (phone 1) at the localsite.

Phone 1 100 to 99999999 101 l This parameter specifies the orderwirephone number of the local station. Anaddressing call refers to a point-to-pointcall.

l The length of the orderwire phonenumber of each NE should be the same.It is recommended that you set the phonenumber to a three-digit number.

l The orderwire phone number of each NEshould be unique. It is recommended thatthe phone numbers are allocated from101 for the NEs in a sequential orderaccording to the NE IDs.

l The orderwire phone number cannot beset to the group call number 888 andcannot start with 888.

AvailableOrderwire Port

- - This parameter indicates the available portfor the orderwire phone.

SelectedOrderwire Port

- - This parameter indicates the selected portfor the orderwire phone.

Related TasksA.29.1 Configuring the Orderwire



B-245

B.13.2 Parameter Description: Orderwire_AdvancedThis topic describes the parameters that are used for advanced orderwire features.


Orderwire from the Function Tree.

2. Click the Advanced tab.

Parameters for Bytes Occupied by Orderwire Phones


OrderwireOccupied Bytes

E1E2

E1 l This parameter specifies the overheadbyte that is used to transmit the orderwiresignals.

l Regardless the parameter value, the radiolink always uses a customized overheadbyte to transmit the orderwire signals.Hence, this parameter should be setaccording to the occupied SDH overheadbytes in the ordinary SDH.

Related TasksA.29.1 Configuring the Orderwire

B.13.3 Parameter Description: Orderwire_F1 Data PortThis topic describes the parameters that are used for F1 data ports.


Orderwire from the Function Tree.

2. Click the F1 Data Port tab.

Parameters


Available DataChannel

- - l This parameter indicates the available F1data channel.

l Two data channels should be selected forthe configuration.

No - - This parameter indicates the number of theF1 data port.


Configuration Guide


Issue 02 (2009-10-30)


Data Channel 1 - - l If an SDH optical or electrical line port isselected, this parameter corresponds tothe F1 byte in the SDH frame at the lineport.

l If an IF port is selected, this parametercorresponds to the customized F1 byte inthe microwave frame at the IF port.

l If F1 is selected, this parametercorresponds to the F1/S1 interface on theSCC, Cross-Connect and Clock Board.The F1/S1 interface complies with ITU-T G.703 and operates at the rate of 64kbit/s.

Data Channel 2

Related TasksA.29.2 Configuring the Synchronous Data Service

B.13.4 Parameter Description: Orderwire_Broadcast Data PortThis topic describes the parameters that are used for broadcast data ports.


Orderwire from the Function Tree.2. Click the Broadcast Data Port tab.

Parameters for Broadcast Data PortsParameter Value Range Default Value Description

Overhead Byte SERIAL1 toSERIAL4

SERIAL1 l In the case of an SDH optical/electricalline, the preset overhead byte is used totransmit the asynchronous data services.

l In the case of a radio link, a customizedserial overhead byte in the microwaveframe is used to transmit theasynchronous data services.



B-247


Broadcast DataSource

- - l When this parameter is set to theSERIAL1, the F1/S1 interface on thecorresponding SCC, Cross-Connect andClock Board is used.

l When this parameter is set to the SDHoptical/electrical line port, the value ofOverhead Byte of this port is used.

l When this parameter is set to the IF port,the customized Serial byte in themicrowave frame of this port is used.

AvailableBroadcast DataSink

- - This parameter indicates the availablebroadcast data sink.

Selected BroadcastData Sink

- - l When this parameter is set to theSERIAL1, the F1/S1 interface on thecorresponding SCC, Cross-Connect andClock Board is used.

l When this parameter is set to the SDHoptical/electrical line port, the value ofOverhead Byte of this port is used.

l When this parameter is set to the IF port,the customized Serial byte in themicrowave frame of this port is used.

Related TasksA.29.3 Configuring the Asynchronous Data Service

B.13.5 Parameter Description: Environment Monitoring InterfaceThis topic describes the parameters that are used for environment monitoring interfaces.

Navigation PathSelect the AUX logical board from the Object Tree in the NE Explorer. ChooseConfiguration > Environment Monitor Configuration > Environment Monitor Interfacefrom the Function Tree.

Parameters for the Basic AttributesParameter Value Range Default Value Description

Operation Object - - This parameter indicates the operationobject.


Configuration Guide


Issue 02 (2009-10-30)


Relay ControlMode

Auto ControlManual Control

Auto Control l Auto Control: If an alarm is reported, thealarming relay is started upautomatically. Otherwise, the alarmingrelay is shut down.

l Manual Control: Relay Status in MajorAlarm(K0) and Relay Status in CriticalAlarm(K1) need to be set.

Relay Status inMajor Alarm(K0)

DisabledEnabled

Disabled l This parameter indicates that the status ofthe relay is set manually for major alarms.

l Enable: The relay is set to the "0N" statusfor major alarms.

l Disabled: The relay is set to the "OFF"status for major alarms.

l This parameter is valid only when RelayControl Mode is set to ManualControl.

Relay Status inCritical Alarm(K1)

DisabledEnabled

Disabled l This parameter indicates that the status ofthe relay is set manually for criticalalarms.

l Enable: The relay is set to the enabledstatus for critical alarms.

l Disabled: The relay is set to the disabledstatus for critical alarms.

l This parameter is valid only when RelayControl Mode is set to ManualControl.

Parameters for the Input RelayParameter Value Range Default Value Description


Path Name - - This parameter indicates or specifies thename of the channel.

Using Status UnusedUsed

Unused This parameter specifies whether the alarminterface of the input relay is used.



B-249


Alarm Mode Relay Turns Off/High LevelRelay Turns On/Low Level

Relay Turns Off/High Level

l If this parameter is set to Relay TurnsOff/High Level, an alarm is generatedwhen the relay is turned off.

l If this parameter is set to Relay TurnsOn/Low Level, an alarm is generatedwhen the relay is turned on.

l This parameter is valid only when UsingStatus is set to Used.

Alarm Severity Critical AlarmMajor AlarmMinor AlarmWarning Alarm

Critical Alarm This parameter specifies the severity of thealarm that is generated at the input relay.

Parameters for the Output RelayParameter Value Range Default Value Description


Output Path Name - - This parameter indicates or specifies thename of the output channel.

Use or Not UnusedUsed

Unused This parameter specifies whether the alarminterface of the output relay is used.

Parameters for the Temperature AttributesParameter Value Range Default Value Description


TemperatureUpper Threshold(Deg.C)

-40.0 to 80.0 - This parameter specifies the uppertemperature threshold of the board. Whenthe actual temperature is higher than thepreset value, an alarm is generated.

TemperatureLower Threshold(Deg.C)

-40.0 to 80.0 - This parameter specifies the lowertemperature threshold of the board. Whenthe actual temperature is lower than thepreset value, an alarm is generated.


Configuration Guide


Issue 02 (2009-10-30)

Parameters for the Alarm RelayParameter Value Range Default Value Description

Alarm Severity Critical AlarmMajor AlarmMinor AlarmWarning Alarm

Critical AlarmMajor AlarmMinor AlarmWarning Alarm

This parameter indicates the severity of thealarm.

Alarm OutputChannel

CSK-1CSK-2CSK-3CSK-4

CSK-1 This parameter specifies the channel of theoutput alarm relay.

Related TasksA.29.5 Configure External Alarms

B.14 Parameters for Board InterfacesThis topic describes the parameters that are related to board interfaces.

B.14.1 Parameter Description: IF Interface_IF AttributeThis topic describes the parameters that are related to IF attributes.

B.14.2 Parameter Description: IF Interface_ATPC AttributeThis topic describes the parameters that are related to the ATPC attributes.

B.14.3 Parameter Description: Hybrid/AM ConfigurationThis topic describes the parameters that are used for configuring the Hybrid/AM function.

B.14.4 Parameter Description: ATPC Adjustment RecordsThis topic describes the parameters that are related to ATPC adjustment records.

B.14.5 Parameter Description: PRBS TestThis topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)test.

B.14.6 Parameter Description: ODU Interface_Radio Frequency AttributeThis topic describes the parameters that are related to radio frequency attributes of an ODU.

B.14.7 Parameter Description: ODU Interface_Power AttributesThis topic describes the parameters that are used for configuring the power attributes of theODU.

B.14.8 Parameter Description: ODU Interface_Equipment InformationThis topic describes the parameters that are used for configuring the equipment information ofthe ODU.

B.14.9 Parameter Description: ODU Interface_Advanced AttributesThis topic describes the parameters that are used for configuring the advanced attributes of theODU.



B-251

B.14.10 Parameter Description: SDH InterfacesThis topic describes the parameters that are related to the SDH interfaces.

B.14.11 Parameter Description: Automatic Laser ShutdownThis topic describes the parameters that are related to the automatic laser shutdown (ALS)function.

B.14.12 Parameter Description: PDH InterfacesThis topic describes the parameters that are related to the PDH interfaces.

B.14.13 Parameter Description: Ethernet Interface_Basic AttributesThis topic describes the parameters that are related to the basic attributes of an Ethernet interface.

B.14.14 Parameter Description: Ethernet Interface_Flow ControlThis topic describes the parameters that are related to flow control.

B.14.15 Parameter Description: Ethernet Interface_Layer 2 AttributesThis topic describes the parameters that are related to the Layer 2 attributes.

B.14.16 Parameter Description: Ethernet Interface_Advanced AttributesThis topic describes the parameters that are used for configuring the advanced attributes.

B.14.17 Parameter Description: Microwave Interface_Basic AttributesThis topic describes the parameters that are related to the basic attributes of microwaveinterfaces.

B.14.18 Parameter Description: Microwave Interface_Layer 2 AttributesThis topic describes the parameters that are related to the Layer 2 attributes of microwaveinterfaces.

B.14.19 Parameter Description: Microwave Interface_Advanced AttributesThis topic describes the parameters that are related to the advanced attributes of microwaveinterfaces.

B.14.1 Parameter Description: IF Interface_IF AttributeThis topic describes the parameters that are related to IF attributes.


Configuration > IF Interface from the Function Tree.l Click the IF Attributes tab.


Port - - This parameter indicates the correspondingIF interface.


Configuration Guide


Issue 02 (2009-10-30)


Radio Link ID 1 to 4094 1 l This parameter indicates or specifies theID of a radio link. As the identifier of aradio link, this parameter is used toprevent incorrect connections of radiolinks between sites.

l Each radio link of an NE should have aunique link ID, and the link IDs at bothends of a radio link should be the same.

Received RadioLink ID

1 to 4094 - l This parameter indicates the received IDof the radio link.

l If the value of Received Radio Link IDdoes not match the preset value of RadioLink ID at the local end, the local endinserts the AIS signal to the downstreamdirection of the service. At the same time,the local end reports an alarm to the NMS,indicating that the link IDs do not match.

IF Port Loopback Non-LoopbackInloopOutloop

Non-Loopback l This parameter indicates or specifies theloopback status of the IF interface.

l Non-Loopback indicates that theloopback is cancelled or not performed.

l Inloop indicates that the IF signalstransmitted to the opposite end are loopedback.

l Outloop indicates that the received SDHsignals are looped back.

l Generally, this parameter is used to locatethe faults that occur at each IF interface.The IF loopback is used for diagnosis. Ifthis function is enabled, the services at therelated ports are affected. In normalcases, this parameter is set to Non-Loopback.

2M WaysideEnable Statusa

DisabledEnabled

Disabled l This parameter indicates or specifieswhether the radio link transmits thewayside E1 service.

l The wayside E1 service can be supportedby the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or9,E3,14MHz,16QAM mode.



B-253


2M Wayside InputBoarda

- - l This parameter indicates or specifies theslot in which the 2M wayside service isaccessed.

l This parameter can be set only when 2MWayside Enable Status is set toEnabled.

l The wayside E1 service can be supportedby the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or9,E3,14MHz,16QAM mode.

350 MHzConsecutive WaveStatus

StopStart

Stop l This parameter indicates or specifies thestatus of transmitting the 350 MHz carriersignals at the IF interface.

l This parameter can be set to Start in thecommissioning process only. In normalcases, this parameter is set to Stop.Otherwise, the services are interrupted.

XPIC Enabledb EnabledDisabled

Enabled l This parameter indicates or specifieswhether the XPIC function of the IFX2board is enabled.

l If the IFX2 board does not perform theXPIC function, this parameter should beset to Disabled. In this case, the XPICcable is required to perform self-loop forthe XPIC port on the IFX2 board.

Enable IEEE-1588Timeslotc

EnabledDisabled

Disabled If the OptiX RTN 910 is interconnected withthe packet radio equipment, this parametershould be set to Enabled. Otherwise, thisparameter should be set to Disabled.

NOTE

l a. The IFU2 and IFX2 boards do not support the 2M wayside service.

l b. The IFU2 and IF1 boards do not support the XPIC function.

l c. The IF1 board does not support the IEEE-1588 timeslot function.

Related TasksA.7.7 Setting IF AttributesA.29.4 Configuring the Wayside E1 Service

B.14.2 Parameter Description: IF Interface_ATPC AttributeThis topic describes the parameters that are related to the ATPC attributes.


Configuration Guide


Issue 02 (2009-10-30)


Configuration > IF Interface from the Function Tree.l Click the ATPC Attributes tab.


Port - - This parameter indicates the correspondingIF interface.

ATPC EnableStatus

DisabledEnabled

Disabled l This parameter specifies whether theATPC function is enabled.

l When this parameter is set to Enabledand if the RSL at the receive end is 2 dBhigher or lower than the central valuebetween the ATPC upper threshold andthe ATPC lower threshold at the receiveend, the receiver notifies the transmitterto decrease or increase the transmit poweruntil the RSL is within the range that is 2dB higher or lower than the central valuebetween the ATPC upper threshold andthe ATPC lower threshold.






l It is recommended that you set ATPCUpper Threshold(dBm) to the sum ofthe planned central value between theATPC upper threshold and the ATPClower threshold and 10 dB, and ATPCLower Threshold(dBm) to thedifference between the planned centralvalue between the ATPC upper thresholdand the ATPC lower threshold and 10 dB.



B-255



-35.0 to -90.0 -70.0 l You can set the ATPC upper thresholdonly when ATPC Automatic Threshold(dBm) is set to Disabled.


EnabledDisabled




ATPC UpperAutomaticThreshold(dBm)

- - l This parameter indicates that theequipment automatically uses the presetATPC upper and lower thresholds.

l This parameter is valid only when ATPCAutomatic Threshold Enable Status isset to Enabled.

ATPC LowerAutomaticThreshold(dBm)

- -

Related TasksA.7.8 Configuring the ATPC Function

B.14.3 Parameter Description: Hybrid/AM ConfigurationThis topic describes the parameters that are used for configuring the Hybrid/AM function.

Navigation PathIn the NE Explorer, select a Hybrid IF board from the Object Tree and then chooseConfiguration > Hybrid/AM Configuration from the Function Tree.


Configuration Guide


Issue 02 (2009-10-30)


Port - - This parameter indicates the correspondingIF port.

IF ChannelBandwidth

7M14M28M56M

7M IF Channel Bandwidth indicates thechannel spacing of the corresponding radiolink. This parameter is set according to theplanning information.

AM Mode Asymmetric Asymmetric When AM Mode is set to Asymmetric, theAM switching in one direction of the radiolink does not trigger AM switching in theother direction of the radio link.NOTE

On the OptiX RTN equipment, this parametercan be set to Asymmetric only.

AM Enable Status DisableEnable

Disable l When this parameter is set to Disable, theradio link uses only the specifiedmodulation scheme. In this case, youneed to select Manually SpecifiedModulation Mode.

l When this parameter is set to Enable, theradio link uses the correspondingmodulation scheme according to thechannel conditions.

Hence, the Hybrid radio can ensure thereliable transmission of the E1 services andprovide bandwidth adaptively for theEthernet services when the AM function isenabled.

Modulation Modeof the GuaranteedAM Capacity


QPSK This parameter specifies the lowest-gainmodulation scheme that the AM functionsupports. This parameter is set according tothe planning information. Generally, thevalue of this parameter is determined by theservice transmission bandwidth that theHybrid radio must ensure and theavailability of the radio link thatcorresponds to this modulation scheme.This parameter is valid only when AMEnable Status is set to Enable.



B-257


Modulation Modeof the Full AMCapacity




This parameter is valid only when AMEnable Status is set to Enable.

ManuallySpecifiedModulation Mode


QPSK This parameter specifies the modulationscheme that the radio link uses for signaltransmission.This parameter is valid only when AMEnable Status is set to Disable.


- - l When AM Enable Status is set toEnable, this parameter depends on IFChannel Bandwidth and ModulationMode of the Guaranteed AMCapacity and is not configurable.

l When AM Enable Status is set toDisable, this parameter depends on IFChannel Bandwidth and ManuallySpecified Modulation Mode and is notconfigurable.

E1 Capacity - - This parameter specifies the number of E1services that can be transmitted in theHybrid work mode.

Related TasksA.7.5 Setting the Hybrid/AM AttributeA.7.12 Querying the AM Status

B.14.4 Parameter Description: ATPC Adjustment RecordsThis topic describes the parameters that are related to ATPC adjustment records.


Configuration Guide


Issue 02 (2009-10-30)

Navigation PathSelect the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > ATPC Adjustment Records from the Function Tree.


Port - - This parameter indicates the port for theATPC adjustment.

Event NO. - - This parameter indicates the number of theATPC adjustment event.

Adjustment Time - - This parameter indicates the time of theATPC adjustment.

AdjustmentDirection

- - This parameter indicates the direction of theadjustment at the port.

Switchover - - This parameter indicates the switchingoperation at the port.

TransmittedPower(dBm)

- - This parameter indicates the transmittedpower of the port to be switched.

Received Power(dBm)

- - This parameter indicates the received powerof the port to be switched.

Related TasksA.7.10 Querying the ATPC Adjustment Records

B.14.5 Parameter Description: PRBS TestThis topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)test.

Navigation PathSelect the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > PRBS Test from the Function Tree.


Port - - This parameter indicates the port for thePRBS test.



B-259


Direction CrossTributary

Cross l This parameter indicates or specifies thedirection of the PRBS test.

l In the tributary direction, the PRBS testis performed to check the connectivity ofthe cable from the tributary board to theDDF.

l In the cross-connect direction, the PRBStest is performed to check the processingof the service from the tributary board tothe NE at the remote end.

Duration 1 to 255 1 This parameter indicates or specifies theduration of the PRBS test.

Measured Time s10minh

s This parameter indicates or specifies thetime unit used for the PRBS test.

Start Time - - This parameter indicates the start time of thePRBS test.

Progress - - This parameter indicates the progresspercentage of the PRBS test.

Total PRBS - - This parameter indicates the number of biterrors that occur in the PRBS test.

AccumulatingMode

SelectedDeselected

Deselected This parameter specifies whether to displaythe values in accumulative mode. IfAccumulating Mode is selected, itindicates that the values are displayed inaccumulative mode.

B.14.6 Parameter Description: ODU Interface_Radio FrequencyAttribute

This topic describes the parameters that are related to radio frequency attributes of an ODU.

Navigation Pathl Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU

Interface from the Function Tree.l Click the Radio Frequency Attributes tab.


Configuration Guide


Issue 02 (2009-10-30)


Board - - This parameter indicates the correspondingODU.

TransmitFrequency(MHz)

- - l This parameter indicates or specifies thetransmit frequency of the ODU, namely,the central frequency of the channel.

l The value of this parameter must not beless than the sum of the minimumtransmit frequency supported by theODU and a half of the channel spacing,and must not be more than the differencebetween the maximum transmitfrequency supported by the ODU and ahalf of the channel spacing.

l The difference between the transmitfrequencies at both ends of a radio linkshould be one T/R spacing.


T/R Spacing(MHz) - - l This parameter indicates or specifies thespacing between the transmit frequencyand receive frequency of the ODU toprevent mutual interference of thetransmitter and receiver.

l If the ODU is a Tx high station, thetransmit frequency is one T/R spacinghigher than the receive frequency. If theODU is a Tx low station, the transmitfrequency is one T/R spacing lower thanthe receive frequency.

l If the ODU supports only one T/Rspacing, this parameter is set to 0,indicating that the T/R spacing supportedby the ODU is used.


l The T/R spacing of the ODU should beset to the same value at both ends of aradio link.

Actual TransmitFrequency(MHz)

- - This parameter indicates the actual transmitfrequency of the ODU.

Actual ReceiveFrequency(MHz)

- - This parameter indicates the actual receivefrequency of the ODU.



B-261


Actual T/RSpacing(MHz)

- - This parameter indicates the actual T/Rspacing of the ODU.

The Range offrequency Point(MHz)

- - This parameter indicates the working rangeof the frequency of the ODU.

Related TasksA.22.1 Setting the Transmit Frequency Attribute of the ODU

B.14.7 Parameter Description: ODU Interface_Power AttributesThis topic describes the parameters that are used for configuring the power attributes of theODU.


Interface from the Function Tree.l Click the Power Attributes tab.









Configuration Guide


Issue 02 (2009-10-30)


Transmit Power(dBm)

- - l This parameter specifies the transmitpower of the ODU. This parametercannot be set to a value that exceeds thenominal power rang of the ODU or avalue that exceeds Maximum TransmitPower(dBm).




Power to BeReceived(dBm)

- - l This parameter is used to set the expectedreceive power of the ODU and is mainlyused in the antenna alignment stage. Afterthis parameter is set, the NEautomatically enables the antennamisalignment indicating function.




Actual TransmitPower(dBm)

- - l This parameter indicates the actualtransmit power of the ODU.

l If the ATPC function is enabled, thequeried actual transmit power may bedifferent from the preset value.

Actual ReceivedPower(dBm)

- - This parameter indicates the actual receivepower of the ODU.



B-263


Actual range ofPower(dBm)

- - This parameter indicates the range of theactual transmit power of the ODU.

Equip Information



Equip Type - - l This parameter indicates the equipmenttype of the ODU.


Station Type Tx LowTx High

- l This parameter indicates whether theODU is a Tx high station or a Tx lowstation.




Standard PowerOutputHigh Power Output

- This parameter indicates the level of theoutput power of the ODU.

Related TasksA.22.3 Setting the Power Attributes of the ODU

B.14.8 Parameter Description: ODU Interface_EquipmentInformation

This topic describes the parameters that are used for configuring the equipment information ofthe ODU.


Configuration > ODU Interface from the Function Tree.

l Click the Equipment Information tab.


Configuration Guide


Issue 02 (2009-10-30)

Parameters




Equipment Type PDHSDH

- l This parameter indicates the equipmenttype of the ODU.


T/R Spacing(MHz) - - This parameter indicates the T/R spacing ofthe ODU.

IntermediateFrequencyBandwidth (MHz)

- - This parameter indicates the IF frequencybandwidth of the ODU.

Station Type - - l This parameter indicates whether theODU is a Tx high station or a Tx lowstation.



- - This parameter indicates the level of theoutput power of the ODU.

Produce Time - - This parameter indicates the manufacturingtime of the ODU.


Related TasksA.22.2 Querying the ODU Attribute

B.14.9 Parameter Description: ODU Interface_Advanced AttributesThis topic describes the parameters that are used for configuring the advanced attributes of theODU.


Interface from the Function Tree.



B-265

l Click the Advanced Attributes tab.



RF Loopback Non-LoopbackInloop

Non-Loopback l This parameter indicates or specifies theloopback status of the RF interface of theODU.

l Non-Loopback indicates that theloopback is canceled or not performed.

l Inloop indicates that the RF signalstransmitted to the opposite end are loopedback.

l This function is used for fault locating forthe RF interfaces. The RF Loopbackfunction is used for diagnosis and mayaffect the services that are transmittedover the interfaces. Hence, exerciseprecaution before starting this function.

l In normal cases, this parameter is set toNon-Loopback.

ConfigureTransmissionStatus

unmutemute

unmute l This parameter indicates or specifies thetransmit status of the ODU.

l If this parameter is set to mute, thetransmitter of the ODU does not work butcan normally receive microwave signals.

l If this parameter is set to unmute, theODU can normally transmit and receivemicrowave signals.


ActualTransmissionStatus

unmutemute

- This parameter indicates the actual transmitstatus of the ODU.

FactoryInformation

- - This parameter indicates the manufacturerinformation about the ODU.

Related TasksA.22.4 Setting the Advanced Attributes of the ODU

B.14.10 Parameter Description: SDH InterfacesThis topic describes the parameters that are related to the SDH interfaces.


Configuration Guide


Issue 02 (2009-10-30)


Configuration > SDH Interface from the Function Tree.l Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.


Port - - This parameter indicates the correspondingSDH interface.

Optical InterfaceNamea

- - This parameter indicates or specifies thename of the optical interface.

Laser Switcha OpenClose

Open l This parameter indicates or specifies theon/off state of the laser.

l This parameter is set for SDH opticalinterfaces only.

l In normal cases, this parameter is set toOpen.

Optical(Electrical)InterfaceLoopbacka

Non-LoopbackInloopOutloop

Non-Loopback l This parameter indicates or specifies theloopback status on the SDH interface.


l Inloop indicates that the SDH signalstransmitted to the opposite end are loopedback.


l This function is used for fault locating forthe SDH interfaces. The Optical(Electrical) Interface Loopbackfunction is used for diagnosis and mayaffect the services that are transmittedover the interfaces. Hence, exerciseprecaution before starting this function.




B-267


VC4 Loopbackb Non-LoopbackInloopOutloop

Non-Loopback l This parameter indicates or specifies theloopback status in the VC-4 path.


l Inloop indicates that the VC-4 signalstransmitted to the opposite end are loopedback.

l Outloop indicates that the received VC-4signals are looped back.

l This function is used for fault locating forthe VC-4 paths. The VC4 Loopbackfunction is used for diagnosis and mayaffect the services that are transmittedover the interfaces. Hence, exerciseprecaution before starting this function.


NOTE

l a: Indicates the parameters that are supported when Port is selected from the list box.

l b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.

Related TasksA.23 Setting the Parameters of SDH Interfaces

B.14.11 Parameter Description: Automatic Laser ShutdownThis topic describes the parameters that are related to the automatic laser shutdown (ALS)function.

Navigation PathSelect the corresponding board from the Object Tree in the NE Explorer. ChooseConfiguration > Automatic Laser Shutdown from the Function Tree.


Optical Interface - - This parameter indicates the correspondingoptical interface.


Configuration Guide


Issue 02 (2009-10-30)


AutomaticShutdown

DisabledEnabled

Disabled l This parameter indicates or specifieswhether the Automatic LaserShutdown function is enabled ordisabled for the laser.

l The ALS function allows the laser to shutdown automatically when an optical portdoes not carry services, an optical fiber isbroken, or no optical signal is received.

l You can set On Period(ms), Off Period(ms), and Continuously On-test Period(ms) only when this parameter is set toEnabled.

On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies theperiod when a shutdown laser automaticallystarts up and tests whether the optical fiberis normal.

Off Period(ms) 2000 to 300000 60000 This parameter indicates or specifies theperiod when the laser does not work (withthe ALS function being enabled).

Continuously On-test Period(ms)

2000 to 300000 90000 This parameter indicates or specifies theperiod when a shutdown laser is manuallystarted up and tests whether the optical fiberis normal.

B.14.12 Parameter Description: PDH InterfacesThis topic describes the parameters that are related to the PDH interfaces.


Configuration > PDH Interface from the Function Tree.

l Select By Board/Port(Channel).

l Select Port from the list box.

Parameters



Port Name - - This parameter indicates or specifies thename of the port.



B-269


TributaryLoopback


- l This parameter indicates or specifies theloopback status in the associated path ofthe tributary unit.


l Inloop indicates that the PDH signalstransmitted to the opposite end are loopedback.

l Outloop indicates that the received PDHsignals are looped back.

l This function is used for fault locating forthe paths of the tributary unit. TheTributary Loopback function is used fordiagnosis and may affect the services thatare transmitted over the interfaces.Hence, exercise precaution beforestarting this function.


Port Impedance 75 Ohm120 ohm

- This parameter indicates the impedance of apath, which depends on the tributary unit.

Service LoadIndication

LoadNon-Loaded

- l This parameter indicates or specifies theservice loading status in a specific path.

l When this parameter is set to Load, theboard detects whether alarms exist in thepath.

l When this parameter is set to Non-Loaded, the board does not detectwhether there are alarms in the path.

l If a path does not carry any services, youcan set this parameter to Non-Loaded forthe path to mask all the alarms. If a pathcarries services, you need to set thisparameter to Load for the path.


Configuration Guide


Issue 02 (2009-10-30)


Retiming Mode NormalRetiming Mode ofTributary ClockRetiming Mode ofCross-connectClock

- l This parameter indicates or specifies theretiming mode of a specific path.

l By using the retiming function, theretiming reference signal from the SDHnetwork and the service data signal arecombined and then sent to the clientequipment, thus decreasing the outputjitter in the signal. In this way, theretiming function ensures that the servicecode flow can normally transfer theretiming reference signal.

l When this parameter is set to Normal, theretiming function is not used.

l When this parameter is set to RetimingMode of Tributary Clock, the retimingfunction is used with the clock of theupstream tributary unit traced.

l When this parameter is set to theretiming function is used with the clockof the upstream tributary unit traced.,the retiming function is used with theclock of the cross-connect unit traced.

l It is recommended that the external clock,instead of the retiming function, shouldbe used to provide reference clock signalsfor the equipment.

l If the retiming function is required, it isrecommended that you set this parameterto Retiming Mode of Cross-connectClock.

Port Service Type E1 - This parameter indicates the type of servicesthat are processed in a path. It depends onthe services that are transmitted in a path.

Related TasksA.24 Setting the Parameters of PDH Interfaces

B.14.13 Parameter Description: Ethernet Interface_Basic AttributesThis topic describes the parameters that are related to the basic attributes of an Ethernet interface.


Management > Ethernet Interface from the Function Tree.



B-271

2. Click the General Attributes tab.


Port - - This parameter indicatesthe port name.

Name - - This parameter specifiesthe port name.

Enable Port EnabledDisabled

Enabled This parameter indicatesthe working mode of theport.

Port Mode Layer 2 Layer 2 This parameter indicatesthe working mode of theport.


- l This parameterspecifies the method ofthe port to process thereceived packets.

l If you set thisparameter to Null, theport transparentlytransmits the receivedpackets.

l If you set thisparameter to 802.1Q,the port identifies thepackets that complywith the IEEE 802.1Qstandard.

l If you set thisparameter to QinQ, theport identifies thepackets that complywith the IEEE 802.1QinQ standard.


Configuration Guide


Issue 02 (2009-10-30)


Working Mode Auto-Negotiation10M Half-Duplex10M Full-Duplex100M Half-Duplex100M Full-Duplex1000M Full-Duplex

Auto-Negotiation l The Ethernet ports ofdifferent types supportdifferent workingmodes.

l When the equipment onthe opposite side worksin auto-negotiationmode, set the workingmode of the equipmenton the local side toAuto-Negotiation.

l When the equipment onthe opposite side worksin full-duplex mode, setthe working mode ofthe equipment on thelocal side to 10M Full-Duplex, 100M Full-Duplex, or 1000MFull-Duplexdepending on the portrate of the equipmenton the opposite side.

l When the equipment onthe opposite side worksin half-duplex mode,set the working modeof the equipment on thelocal side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation dependingon the port rate of theequipment on theopposite side.

l The GE opticalinterface supports the1000M full-duplexmode only.

Max Frame Length(byte)

1518 to 9600 1522 The value of thisparameter should begreater than the length ofany frame to betransported.



B-273


Auto-NegotiationEnable

Auto-Negotiation

10M Half-Duplex

10M Full-Duplex

100M Half-Duplex

100M Full-Duplex

1000M Full-Duplex

100M Full-Duplex l This parameterspecifies the auto-negotiation capabilityof the Ethernet port.

l This parameter is validonly when WorkingMode is set to Auto-Negotiation.

Logical Port Attribute Optical PortElectrical Port

Optical Port l This parameterspecifies the attributeof the logical port.

l The SFP on the EM6Fboard supports theoptical port andelectrical port.

Physical Port Attribute - - This parameter indicatesthe attribute of thephysical port.

Related TasksA.20.1 Setting the General Attributes of Ethernet Interfaces

B.14.14 Parameter Description: Ethernet Interface_Flow ControlThis topic describes the parameters that are related to flow control.


Management > Ethernet Interface from the Function Tree.2. Click the Flow Control tab.




Configuration Guide


Issue 02 (2009-10-30)


Non-AutonegotiationFlow Control Mode

DisabledEnable Symmetric FlowControl

Disabled l This parameter is validonly when WorkingMode is not set toAuto-Negotiation.

l The non-autonegotiation flowcontrol mode of theequipment on the localside must be consistentwith the non-autonegotiation flowcontrol mode of theequipment on theopposite side

Auto-Negotiation FlowControl Mode

DisabledEnable Symmetric FlowControl

Disabled l This parameter is validonly when WorkingMode is set to Auto-Negotiation.

l The auto-negotiationflow control mode ofthe equipment on thelocal side must beconsistent with theauto-negotiation flowcontrol mode of theequipment on theopposite side

Related TasksA.20.2 Configuring the Traffic Control of Ethernet Interfaces

B.14.15 Parameter Description: Ethernet Interface_Layer 2Attributes

This topic describes the parameters that are related to the Layer 2 attributes.


Management > Ethernet Interface from the Function Tree.2. Click the Layer 2 Attributes tab.



B-275



QinQ Type Domain - - l This parameterspecifies the QinQ typedomain.

l When EncapsulationType in the GeneralAttributes tab page isset to QinQ, you needto set QinQ TypeDomain. The defaultvalue is 88A8.

l When EncapsulationType in the GeneralAttributes tab page isset to Null or 802.1Q,you cannot set QinQType Domain. In thiscase, QinQ TypeDomain is displayed asFFFF and cannot bechanged.

l QinQ Type Domainshould be set to thesame value for all theports on the EM6T/EM6F board or theEM4T/EM4F logicalboard.


Configuration Guide


Issue 02 (2009-10-30)



Tag Aware l This parameterspecifies the TAG flagof a port. For detailsabout the TAG flagsand associated frame-processing methods,see Table B-1.

l If all the accessedservices are frameswith the VLAN tag(tagged frames), thisparameter is set to TagAware.

l If all the accessedservices are frameswithout the VLAN tag(untagged frames), thisparameter is set toAccess.

l If the accessed servicescontain tagged framesand untagged frames,this parameter is set toHybrid.

Default VLAN ID 1 to 4094 1 l This parameter is validonly when TAG is setto Access or Hybrid.

l For details about thefunctions of thisparameter, see TableB-1.

l This parameter is setaccording to the actualsituations.



B-277


VLAN Priority 0 to 7 0 l This parameter is validonly when TAG is setto Access or Hybrid.

l For details about thefunctions of thisparameter, see TableB-1.

l When the VLANpriority is required todivide streams or to beused for otherpurposes, thisparameter is setaccording to theplanning information.In normal cases, it isrecommended that youuse the default value.

Table B-1 Methods used by Ethernet interfaces to process data frames

Port Type of DataFrame

Processing Method


Ingress UNI Tagged frame The port receives theframe.

The port discardsthe frame.

The port receivesthe frame.

Untagged frame The port discards theframe.

The ports add theVLAN tag, to whichDefault VLAN IDand VLANPrioritycorrespond, to theframe and receivesthe frame.

The ports add theVLAN tag, to whichDefault VLAN IDand VLANPrioritycorrespond, to theframe and receivesthe frame.


Configuration Guide


Issue 02 (2009-10-30)

Port Type of DataFrame

Processing Method


Egress UNI Tagged frame The port transmitsthe frame.

The port strips theVLAN tag from theframe and thentransmits the frame.

l If the VLAN IDin the frame isDefault VLANID, the port stripsthe VLAN tagfrom the frameand thentransmits theframe.

l If the VLAN IDin the frame is notDefault VLANID, the portdirectly transmitsthe frame.

Related TasksA.20.3 Setting the Layer 2 Attributes of Ethernet Interfaces

B.14.16 Parameter Description: Ethernet Interface_AdvancedAttributes

This topic describes the parameters that are used for configuring the advanced attributes.


Management > Ethernet Interface from the Function Tree.2. Click the Advanced Attributes tab.



Port PhysicalParameters

- - This parameter indicatesthe physical parameters ofthe port.



B-279


MAC Loopback Non-LoopbackInloop

Non-Loopback l This parameterspecifies the loopbackstate at the MAC layer.When this parameter isset to Inloop, theEthernet signalstransmitted to theopposite end are loopedback.

l In normal cases, it isrecommended that youuse the default value.

PHY Loopback Non-LoopbackInloop

Non-Loopback l This parameterspecifies the loopbackstate at the PHY layer.When this parameter isset to Inloop, theEthernet physicalsignals transmitted tothe opposite end arelooped back.

l In normal cases, it isrecommended that youuse the default value.

Loopback Check - - This parameter specifieswhether to enable loopdetection, which is used tocheck whether a loopexists on the port.

Loopback PortShutdown

- - This parameter specifieswhether to enable the loopport shutdown function.

Egress PIR Bandwidth(kbit/s)

- - This parameter specifiesthe egress PIR bandwidth.

Enabling BroadcastPacket Suppression

DisabledEnabled

Disabled This parameter specifieswhether to limit the trafficrate of the broadcastpackets according to theproportion of thebroadcast packets in thetotal packets. When theequipment at the oppositeend may encounter abroadcast storm, thisparameter is set toEnabled.


Configuration Guide


Issue 02 (2009-10-30)



1 to 100 30 When the proportion ofthe broadcast packets inthe total packets exceedsthe value of thisparameter, the receivedbroadcast packets arediscarded. The value ofthis parameter should bemore than the proportionof the broadcast packets inthe total packets beforethe broadcast stormoccurs. In normal cases,this parameter is set to30% or higher.

Related TasksA.20.4 Setting the Advanced Attributes of Ethernet Interfaces

B.14.17 Parameter Description: Microwave Interface_BasicAttributes

This topic describes the parameters that are related to the basic attributes of microwaveinterfaces.

Navigation Pathl Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface

Management > Microwave Interface from the Function Tree.l Click the Basic Attributes tab.



Name - - This parameter indicates or specifies thecustomized port name.

Port Mode Layer 2 Layer 2 This parameter indicates the working modeof the Ethernet name.



B-281


EncapsulationType

Null802.1QQinQ

802.1Q l This parameter specifies the method ofthe port to process the received packets.

l If this parameter is set to Null, the porttransparently transmits the receivedpackets.

l If this parameter is set to 802.1Q, the portidentifies the packets that comply withthe IEEE 802.1Q standard.

l If this parameter is set to QinQ, the portidentifies the packets that comply withthe IEEE 802.1 QinQ standard.

Related TasksA.21.1 Setting the General Attributes of the IF_ETH Port

B.14.18 Parameter Description: Microwave Interface_Layer 2Attributes

This topic describes the parameters that are related to the Layer 2 attributes of microwaveinterfaces.


Management > Microwave Interface from the Function Tree.l Click the Layer 2 Attributes tab.

Parameters for Layer 2 AttributesParameter Value Range Default Value Description


QinQ TypeDomain

- - l This parameter specifies the QinQ typedomain.

l This parameter can be set only whenEncapsulation Type in GeneralAttributes is set to QinQ.


Configuration Guide


Issue 02 (2009-10-30)


Tag Tag AwareAccessHybrid

Tag Aware l This parameter specifies the TAG flag ofa port. For details about the TAG flagsand associated frame-processingmethods, see Table B-2.

l If all the accessed services are frames thatcontain the VLAN tag (tagged frames),set this parameter to "Tag Aware".

l If all the accessed services are frames thatdo not contain the VLAN tag (untaggedframes), set this parameter to "Access".

l If the accessed services contain taggedframes and untagged frames, set thisparameter to "Hybrid".

Default VLAN ID 1 to 4094 1 l This parameter is valid only when TAGis set to Access or Hybrid.

l For details about the functions of thisparameter, see Table B-2.

l This parameter needs to be set accordingto the actual situations.

VLAN Priority 0

1

2

3

4

5

6

7

0 l This parameter is valid only when TAGis set to Access or Hybrid.

l For details about the functions of thisparameter, see Table B-2.

l When the VLAN priority is required todivide streams or to be used for otherpurposes, this parameter needs to be setaccording to the planning information. Innormal cases, it is recommended that youuse the default value.

Table B-2 Data frame processing

Status Type of DataFrame

Processing Method


Ingress Port Tagged frame The port receives theframe.

The port discardsthe frame.

The port receivesthe frame.



B-283

Status Type of DataFrame

Processing Method


Untagged frame The port discards theframe.

The port receivesthe frame after theVLAN tag thatcorresponds to"Default VLAN ID"and "VLANPriority" are addedto the frame.

The port receivesthe frame after theVLAN tag thatcorresponds to"Default VLAN ID"and "VLANPriority" are addedto the frame.

Egress Port Tagged frame The port transmitsthe frame.

The port strips theVLAN tag from theframe and thentransmits the frame.

l If the VLAN IDin the frame is"Default VLANID", the portstrips the VLANtag from theframe and thentransmits theframe.

l If the VLAN IDin the frame is not"Default VLANID", the portdirectly transmitsthe frame.

Related TasksA.21.2 Setting the Layer 2 Attributes of the IF_ETH Port

B.14.19 Parameter Description: Microwave Interface_AdvancedAttributes

This topic describes the parameters that are related to the advanced attributes of microwaveinterfaces.


Management > Microwave Interface from the Function Tree.l Click the Advanced Attributes tab.

Parameters for Advanced AttributesParameter Value Range Default Value Description



Configuration Guide


Issue 02 (2009-10-30)


Radio Link ID 1 to 4094 1 l This parameter specifies the ID of theradio link. As the identifier of a radio link,this parameter is used to prevent incorrectconnections of radio links between sites.

l The ID of each radio link of an NE mustbe unique, and the link IDs at both endsof a radio link must be the same.

Received RadioLink ID

- - l This parameter indicates the received IDof the radio link.

l If the value of Received Radio Link IDdoes not match with the preset value ofRadio Link ID at the local end, the localend inserts the AIS signal to thedownstream direction of the service. Atthe same time, the local end reports analarm to the NMS, indicating that the linkIDs do not match.

IF Port Loopback Non-LoopbackInloopOutloop

Non-Loopback l This parameter indicates or specifies theloopback status of the IF interface.


l Inloop indicates that the IF signalstransmitted to the opposite end are loopedback.


l Generally, this parameter is used to locatethe faults that occur at each IF interface.The IF loopback is used for diagnosis. Ifthis function is enabled, the services at therelated ports are affected. In normalcases, this parameter is set to Non-Loopback.

Composite PortLoopback


Non-Loopback l This parameter indicates or specifies theloopback status on the compositeinterface.


l Inloop indicates that the compositesignals transmitted to the opposite end arelooped back.

l Outloop indicates that the receivedcomposite signals are looped back.




B-285


Error FrameDiscard Enabled

EnabledDisabled

Enabled l This parameter indicates or specifieswhether to discard the Ethernet framewhen a CRC error occurs in an Ethernetframe.

l If the Ethernet service transmitted on theIF_ETH port is a voice service or a videoservice, you can set this parameter toDisabled.

l The IF1 board does not support thisparameter.

MAC Address - - l This parameter indicates the MACaddress of the port.


Transmitting Rate(Kbit/s)

- - l This parameter indicates the transmit rateof the local port.


Receiving Rate(Kbit/s)

- - l This parameter indicates the receive rateof the local port.


MAC Loopback Non-LoopbackInloop

Non-Loopback l This parameter specifies the loopbackstate at the MAC layer. When thisparameter is set to Inloop, the Ethernetsignals transmitted to the opposite end arelooped back.

l In normal cases, it is recommended thatyou use the default value.


PHY Loopback Non-Loopback Non-Loopback The IF port on the OptiX RTN 910 does notsupport the setting of this parameter.

Related TasksA.21.3 Setting the Advanced Attributes of the IF_ETH Port

B.15 Parameters for OverheadThis topic describes the parameters that are related to overhead.

B.15.1 Parameter Description: Regenerator Section Overhead


Configuration Guide


Issue 02 (2009-10-30)

This topic describes the parameters that are related to the regenerator section overheads(RSOHs).

B.15.2 Parameter Description: VC-4 POHsThis topic describes the parameters that are related to the VC-4 path overheads (POHs).


B.15.1 Parameter Description: Regenerator Section OverheadThis topic describes the parameters that are related to the regenerator section overheads(RSOHs).

Navigation Path1. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead

Management > Regenerator Section Overhead from the Function Tree.

2. Choose Display in Text Format or Display in Hexadecimal.

Parameters for Setting the Display Format


Display in TextFormat

SelectedDeselected

Selected This parameter specifies the display in thetext format.

Display inHexadecimal

SelectedDeselected

Deselected This parameter specifies the display in thehexadecimal format.



Object - - This parameter indicates the object to be set.

J0 to be Sent([Mode]Content)

- [16 Bytes]HuaWeiSBS

If the NE at the opposite end reports theJ0_MM alarm, this parameter is setaccording to the J0 byte to be received at theopposite end.

J0 to be Received([Mode]Content)

- [Disabled] l This parameter specifies the J0 byte to bereceived.

l If this parameter is set to [Disabled], theboard does not monitor the received J0byte.




B-287

Related TasksA.25.1 Configuring RSOHs


Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Overhead

Management > VC4 Path Overhead from the Function Tree.2. Choose Display in Text Format or Display in Hexadecimal.

Parameters for Setting the Display FormatParameter Value Range Default Value Description


SelectedDeselected



SelectedDeselected


Parameters for the Trace Byte J1Parameter Value Range Default Value Description


J1 to be Sent([Mode]Content)

- [16 Bytes]HuaWeiSBS

If the NE at the opposite end reports theLP_TIM or LP_TIM_VC3 alarm, thisparameter is set according to the J1 byte tobe received at the opposite end.

J1 to be Received([Mode]Content)

- [Disabled] l If this parameter is set to [Disabled], theboard does not monitor the received J1byte.


Parameters for the Signal Flag C2Parameter Value Range Default Value Description



Configuration Guide


Issue 02 (2009-10-30)


C2 to be Sent - - If the NE at the opposite end reports theHP_SLM alarm, this parameter is setaccording to the C2 byte to be received at theopposite end.

C2 to be Received - - If the NE at the local end reports theHP_SLM alarm, this parameter is setaccording to the C2 byte to be sent at theopposite end.

Parameters for Overhead Termination



VC4 OverheadTermination

TerminationPass-ThroughAuto

Auto l If this parameter is set to Pass-Through,the NE forwards the original overheadafter monitoring the VC-4 path overheadregardless of the C2 byte.

l If this parameter is set to Termination,the NE generates the new VC-4 pathoverhead according to the board settingafter monitoring the VC-4 path overheadregardless of the C2 byte.

l If this parameter is set to Auto, the VC-4path overhead in the VC-4 pass-throughservice is passed through, and the VC-4path overhead in the VC-12 service isterminated.

l It is recommended that you use the defaultvalue.

Related TasksA.25.2 Configuring VC-4 POHs


Navigation Path1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Overhead

Management > VC12 Path Overhead from the Function Tree.

2. Choose Display in Text Format or Display in Hexadecimal.



B-289

Parameters for Setting the Display FormatParameter Value Range Default Value Description


SelectedDeselected



SelectedDeselected


Parameters for the Trace ByteParameter Value Range Default Value Description


J2 to be Sent - [16 Bytes]HuaWeiSBS

If the NE at the opposite end reports theHP_TIM alarm, this parameter is setaccording to the J2 byte to be received bythe NE at the opposite end.

J2 to be Received - [Disabled] l If this parameter is set to [Disabled], theboard does not monitor the received J2byte.


Parameters for the Signal FlagParameter Value Range Default Value Description


Signal Label(L1,L2,L3 of V5) tobe Sent

- - If the NE at the opposite end reports theLP_SLM or LP_SLM_VC3 alarm, thisparameter is set according to the V5 byte tobe received at the opposite end.

Signal Label(L1,L2,L3 of V5) tobe Received

- - If the NE at the local end reports theLP_SLM or LP_SLM_VC3 alarm, thisparameter is set according to the V5 byte tobe sent at the opposite end.

Related TasksA.25.3 Configuring VC-12 POHs


Configuration Guide


Issue 02 (2009-10-30)

C Glossary

Terms are listed in an alphabetical order.

Number

1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)

1+1 protection A radio link protection system composed of one working channel and oneprotection channel. Two ODUs and two IF boards are used at each end ofa radio link.

A

Adaptivemodulation

A technology that is used to automatically adjust the modulation modebased on the channel quality. When the channel quality is favorable, theequipment adopts a high-efficiency modulation mode to improve thetransmission efficiency and the spectrum utilization of the system. Whenthe channel quality is degraded, the equipment adopts the low-efficiencymodulation mode to improve the anti-interference capability of the linkthat carries high-priority services.

Add/Dropmultiplexer

A network element that adds/drops the PDH signal or STM-x (x < N) signalto/from the STM-N signal on the SDH transport network.

Adjacentchannelalternatepolarization

A channel configuration method, which uses two adjacent channels (ahorizontal polarization wave and a vertical polarization wave) to transmittwo signals.

Automatictransmit powercontrol

A method of adjusting the transmit power based on fading of the transmitsignal detected at the receiver.

C

OptiX RTN 910Configuration Guide C Glossary


C-1

Co-channeldualpolarization

A channel configuration method, which uses a horizontal polarizationwave and a vertical polarization wave to transmit two signals. The co-channel dual polarization is twice the transmission capacity of the singlepolarization.

Crosspolarizationinterferencecancellation

A technology used in the case of the co-channel dual polarization (CCDP)to eliminate the cross-connect interference between two polarizationwaves in the CCDP.

D

DC-C A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinetand also on the line between the output of the power supply cabinet andthe electric equipment.

DC-I A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinetand is isolated from the PGND on the line between the output of the powersupply cabinet and the electric equipment.

Digitalmodulation

A digital modulation controls the changes in amplitude, phase, andfrequency of the carrier based on the changes in the baseband digital signal.In this manner, the information can be transmitted by the carrier.

Dual-polarizedantenna

An antenna intended to radiate or receive simultaneously two independentradio waves orthogonally polarized.

E

Equalization A method of avoiding selective fading of frequencies. Equalization cancompensate for the changes of amplitude frequency caused by frequencyselective fading.

Bit error A symptom that the quality of the transmitted information is degradedbecause some bits of a data stream are errored after being received,decided, and regenerated.

F

Forward errorcorrection

A bit error correction technology that adds the correction information tothe payload at the transmit end. Based on the correction information, thebit errors generated during transmission are corrected at the receive end.

Frequencydiversity

A diversity scheme that enables two or more microwave frequencies witha certain frequency interval are used to transmit/receive the same signaland selection is then performed between the two signals to ease the impactof fading.

C GlossaryOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

G

Gatewaynetworkelement

A network element that is used for communication between the NEapplication layer and the NM application layer.

H

Hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybridradio supports the AM function.

I

Indoor Unit The indoor unit of the split-structured radio equipment. It implementsaccessing, multiplexing/demultiplexing, and IF processing for services.

Internet GroupManagementProtocol

The protocol for managing the membership of Internet Protocol multicastgroups among the TCP/IP protocols. It is used by IP hosts and adjacentmulticast routers to establish and maintain multicast group memberships.

Intermediatefrequency

The transitional frequency between the frequencies of a modulated signaland an RF signal.

IGMPsnooping

A multicast constraint mechanism running on a layer 2 device. Thisprotocol manages and controls the multicast group by listening to andanalyze the Internet Group Management Protocol (IGMP) packet betweenhosts and layer 3 devices. In this manner, the spread of the multicast dataon layer 2 network can be prevented efficiently.

L

Layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernetswitch transmits and distributes packet data based on the MAC address.Since the MAC address is the second layer of the OSI model, this dataforwarding method is called layer 2 switch.

LCT The local maintenance terminal of a transport network, which is locatedon the NE management layer of the transport network.

Linkaggregationgroup

An aggregation that allows one or more links to be aggregated together toform a link aggregation group so that a MAC client can treat the linkaggregation group as if it were a single link.

Trail A type of transport entity, mainly engaged in transferring signals from theinput of the trail source to the output of the trail sink, and monitoring theintegrality of the transferred signals.

M



C-3

Multiplexsectionprotection

The function performed to provide capability for switching a signalbetween and including two MST functions, from a "working" to a"protection" channel.

MultipleSpanning TreeProtocol

MSTP is an evolution of the Spanning Tree Protocol and the RapidSpanning Tree Protocol, and was introduced in IEEE 802.1s as amendmentto 802.1Q, 1998 edition. Standard IEEE 802.1Q-2003 now includesMSTP.

N

N+1 protection A microwave link protection system that employs N working channels andone protection channel.

Networkelement

A network element (NE) contains both the hardware and the softwarerunning on it. One NE is at least equipped with one system control boardwhich manages and monitors the entire network element. The NE softwareruns on the system control Unit.

Networkmanagementsystem

The network management system in charge of the operation,administration, and maintenance of a network.

Non-gatewaynetworkelement

A network element whose communication with the NM application layermust be transferred by the gateway network element application layer.

O

Orderwire A channel that provides voice communication between operationengineers or maintenance engineers of different stations.

Outdoor unit The outdoor unit of the split-structured radio equipment. It implementsfrequency conversion and amplification for RF signals.

P

PlesiochronousDigitalHierarchy

A multiplexing scheme of bit stuffing and byte interleaving. It multiplexesthe minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565Mbit/s rates.

Polarization A kind of electromagnetic wave, the direction of whose electric field vectoris fixed or rotates regularly. Specifically, if the electric field vector of theelectromagnetic wave is perpendicular to the plane of horizon, thiselectromagnetic wave is called vertically polarized wave; if the electricfield vector of the electromagnetic wave is parallel to the plane of horizon,this electromagnetic wave is called horizontal polarized wave; if the tip ofthe electric field vector, at a fixed point in space, describes a circle, thiselectromagnetic wave is called circularly polarized wave.


Configuration Guide


Issue 02 (2009-10-30)

Q

QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. Itencapsulates the tag of the user's private virtual local area network (VLAN)into the tag of the public VLAN. The packet carries two layers of tags totravel through the backbone network of the carrier. In this manner, the layer2 virtual private network (VPN) is provided for the user.

R

RapidSpanning TreeProtocol

An evolution of the Spanning Tree Protocol, providing for faster spanningtree convergence after a topology change. The RSTP protocol is backwardcompatible with the STP protocol.

S

Singlepolarizedantenna

An antenna that can transmit only one channel of polarized electromagneticwaves.

Space diversity A diversity scheme that enables two or more antennas separated by aspecific distance to transmit/receive the same signal and selection is thenperformed between the two signals to ease the impact of fading. Currently,only receive SD is used.

Spanning TreeProtocol

An algorithm defined in the IEEE 802.1D. It configures the active topologyof a Bridged LAN of arbitrary topology into a single spanning tree.

Subnet A logical entity in the transmission network, which comprises a group ofnetwork management objects. A subnet can contain NEs and other subnets.

Subnetworkconnectionprotection

A function, which allows a working subnetwork connection to be replacedby a protection subnetwork connection if the working subnetworkconnection fails, or if its performance falls below a required level.

SynchronousDigitalHierarchy

A hierarchical set of synchronous digital transport, multiplexing, andcross-connect structures, which is standardized for the transport of suitablyadapted payloads over physical transmission networks.

U

U2000 A unified network management system developed by Huawei. It cansupport all the NE level and network level management functions, and canmanage the transport network, access network, and MAN Ethernet in aunified manner.

V



C-5

Virtual LAN An end-to-end logical network that can travel through several networksegments or networks by using the network management software basedon the switch LAN. The IEEE 802.1Q is the main standard for the virtualLAN.


Configuration Guide


Issue 02 (2009-10-30)

D Acronyms and Abbreviations

Acronyms and abbreviations are listed in alphabetical order.

A

ADC Analog Digit Converter

AGC Automatic Gain Control

APS Automatic Protection Switching

ARP Address Resolution Protocol

ASK Amplitude Shift Keying

ATPC Automatic Transmit Power Control

AU Administrative Unit

B

BER Bit Error Rate

BIOS Basic Input Output System

BIP Bit-Interleaved Parity

BPDU Bridge Protocol Data Unit

BSC Base Station Controller

C

CAR Committed Access Rate

CBS Committed Burst Size

CCDP Co-Channel Dual Polarization

CF Compact Flash card

CGMP Cisco Group Management Protocol

OptiX RTN 910Configuration Guide D Acronyms and Abbreviations


D-1

CIR Committed Information Rate

CIST Common and Internal Spanning Tree

CoS Class of Service

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CVLAN Customer VLAN

C-VLAN Customer VLAN

D

DC Direct Current

DCC Data Communications Channel

DCN Data Communication Network

DSCP Differentiated Services Code Point

DVMRP Distance Vector Multicast Routing Protocol

E

ECC Embedded Control Channel

E-LAN Ethernet-LAN

EMC Electromagnetic Compatibility

EMI Electromagnetic Interference

ERPS Ethernet Ring Protection Switching

ES-IS End System to Intermediate System

ETSI European Telecommunications Standards Institute

F

FCS Frame Check Sequence

FD Frequency Diversity

FE Fast Ethernet

FEC Forward Error Correction

FIFO First In First Out

FLP Fast Link Pulse

FPGA Field Programmable Gate Array

D Acronyms and AbbreviationsOptiX RTN 910

Configuration Guide

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

Issue 02 (2009-10-30)

FTP File Transfer Protocol

G

GE Gigabit Ethernet

GFP Generic Framing Procedure

GTS Generic Traffic Shaping

GUI Graphical User Interface

H

HDB3 High Density Bipolar Code 3

HDLC High level Data Link Control procedure

HSB Hot Standby

HSM Hitless Switch Mode

I

ICMP Internet Control Message Protocol

IDU Indoor Unit

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers

IETF The Internet Engineering Task Force

IF Intermediate Frequency

IGMP Internet Group Management Protocol

IP Internet Protocol

IPv6 Internet Protocol version 6

IS-IS Intermediate System to Intermediate System

ISO International Standard Organization

ITU-T International Telecommunication Union - TelecommunicationStandardization Sector

IVL Independence VLAN learning

L

LAN Local Area Network

LAPD Link Access Procedure on the D channel



D-3

LAG Link Aggregation Group

LAPS Link Access Procedure-SDH

LB LoopBack

LCT Generation-Local Craft Terminal

LDPC Low-Density Parity Check code

LMSP Linear Multiplex Section Protection

LPT Link State Pass Through

M

MA Maintenance Association

MAC Medium Access Control

MADM Multi Add-Drop Multiplexer

MBS Maximum Burst Size

MD Maintenance Domain

MDI Medium Dependent Interface

MEP Maintenance End Point

MIB Management Information Base

MP Maintenance Point

MSP Multiplex Section Protection

MSTP Multiple Spanning Tree Protocol

MTBF Mean Time Between Failure

MTTR Mean Time To Repair

MTU Maximum Transmission Unit

N

NE Network Element

NLP Normal Link Pulse

NMS Network Management System

NNI Network-to-Network Interface or Network Node Interface

NSAP Network Service Access Point

O


Configuration Guide


Issue 02 (2009-10-30)

OAM Operations, Administration and Maintenance

ODU Outdoor Unit

OSI Open Systems Interconnection

OSPF Open Shortest Path First

P

PDH Plesiochronous Digital Hierarchy

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM Protocol Independent Multicast-Sparse Mode

PIR Peak Information Rate

PPP Point-to-Point Protocol

PRBS Pseudo-Random Binary Sequence

Q

QinQ 802.1Q in 802.1Q

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

R

RF Radio Frequency

RFC Request For Comment

RIP Routing Information Protocol

RMON Remote Monitoring

RNC Radio Network Controller

RS Reed-Solomon encoding

RSL Received Signal Level

RSSI Received Signal Strength Indicator

RSTP Rapid Spanning Tree Protocol

RTN Radio Transmission Node

S

SD Space Diversity



D-5

SDH Synchronous Digital Hierarchy

SFP Small Form-Factor Pluggable

SNC SubNetwork Connection

SNCP Sub-Network Connection Protection

SNMP Simple Network Management Protocol

SNR Signal-to-Noise Ratio

SP Strict Priority

SSM Synchronization Status Message

STM Synchronous Transport Module

STM-1 SDH Transport Module -1

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

STM-N SDH Transport Module -N

STP Spanning Tree Protocol

SVL Shared VLAN Learning

T

TCI Tag Control Information

TCP Transfer Control Protocol

TDM Time Division Multiplex

TMN Telecommunication Management Network

TU Tributary Unit

U

UDP User Datagram Protocol

UNI User-Network Interface

V

VC Virtual Container

VC12 Virtual Container -12

VC-12 Virtual Container -12



Configuration Guide


Issue 02 (2009-10-30)




VCG Virtual Concatenation Group

VLAN Virtual LAN

VoIP Voice over IP

VPN Virtual Private Network

W

WAN Wide Area Network

WRR Weighted Round Robin

WTR Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC Cross-polarization Interference Cancellation



D-7