OptiX RTN 605 Radio Transmission System V100R005C00 Configuration Guide

OptiX RTN 605 Radio Transmission System V100R005C00

Configuration Guide Issue

03

Date

2010-05-30

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

Issue 03 (2010-05-30)

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

i

OptiX RTN 605 Configuration Guide

About This Document

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

Version

OptiX RTN 605 1D/2D/1E/2E

V100R005C00

iManager U2000

V100R002C00

Product Name

Version

OptiX RTN 605 1F/2F

V100R003C00

iManager U2000

V100R002C00

Intended Audience his document describes how to configure various services on the equipment. This document describes the basic information and configuration process, and uses configuration examples to show how to set specific parameters. The intended audience of this document are: l

Installation and commissioning engineer

l

Data configuration engineer

l

System maintenance engineer

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

Issue 03 (2010-05-30)


iii


About This Document

Symbol

Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.

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

Description

Boldface

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

>

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

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

Updates in Issue 03 (2010-05-30) This document is the third release of the V100R005C00 version.

Updates in Issue 02 (2010-03-30) This document is the second release of the V100R005C00 version. iv


Issue 03 (2010-05-30)


About This Document

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

Issue 03 (2010-05-30)


v


Contents

Contents About This Document...................................................................................................................iii 1 Configuration Preparations......................................................................................................1-1 1.1 Preparing Documents and Tools.....................................................................................................................1-2 1.2 Checking Configuration Conditions................................................................................................................1-2 1.3 Specifying the Configuration Procedure.........................................................................................................1-2

2 Configuring NEs.........................................................................................................................2-1 2.1 Basic Concepts................................................................................................................................................2-2 2.1.1 DCN.......................................................................................................................................................2-2 2.1.2 GNE and Non-GNE...............................................................................................................................2-3 2.1.3 ID and IP Address of an NE...................................................................................................................2-3 2.1.4 Physical Boards and Logical Boards......................................................................................................2-4 2.2 Configuration Procedure.................................................................................................................................2-5 2.3 Configuration Example (Configuring NEs)....................................................................................................2-8 2.3.1 Networking Diagram..............................................................................................................................2-8 2.3.2 Board Configuration...............................................................................................................................2-9 2.3.3 Service Planning.....................................................................................................................................2-9 2.3.4 Configuration Process..........................................................................................................................2-10

3 Configuring Radio Links..........................................................................................................3-1 3.1 Basic Concepts................................................................................................................................................3-2 3.1.1 Types of Radio Links.............................................................................................................................3-2 3.1.2 RF Configuration Modes........................................................................................................................3-4 3.2 Configuration Procedure.................................................................................................................................3-5 3.3 Configuration Example (Radio Links)............................................................................................................3-9 3.3.1 Networking Diagram..............................................................................................................................3-9 3.3.2 Service Planning...................................................................................................................................3-10 3.3.3 Configuration Process..........................................................................................................................3-12

4 Configuring TDM Services......................................................................................................4-1 4.1 Basic Concepts................................................................................................................................................4-2 4.1.1 Timeslots for TDM Services on the IF Unit..........................................................................................4-2 4.2 Configuration Procedure.................................................................................................................................4-2 4.3 Configuration Example (TDM Services)........................................................................................................4-2 4.3.1 Networking Diagram..............................................................................................................................4-3 Issue 03 (2010-05-30)


vii


Contents

4.3.2 Service Planning.....................................................................................................................................4-3 4.3.3 Configuration Process............................................................................................................................4-4

5 Configuring Ethernet Services................................................................................................5-1 5.1 Basic Concepts................................................................................................................................................5-2 5.1.1 IFUP Interface........................................................................................................................................5-3 5.1.2 Auto-Negotiation....................................................................................................................................5-3 5.1.3 Flow Control..........................................................................................................................................5-5 5.1.4 VLAN.....................................................................................................................................................5-6 5.1.5 QinQ.......................................................................................................................................................5-7 5.1.6 Bridge.....................................................................................................................................................5-9 5.1.7 Hub/Spoke............................................................................................................................................5-11 5.1.8 Types of Ethernet Services...................................................................................................................5-11 5.1.9 Managing a MAC Address Table.........................................................................................................5-12 5.1.10 Protection for Ethernet Services.........................................................................................................5-13 5.1.11 QoS.....................................................................................................................................................5-14 5.2 Configuration Procedure...............................................................................................................................5-19 5.3 Configuration Example (QinQ-Based EVPL Services)................................................................................5-32 5.3.1 Networking Diagram............................................................................................................................5-32 5.3.2 Service Planning...................................................................................................................................5-33 5.3.3 Configuration Process..........................................................................................................................5-38 5.4 Configuration Example (IEEE 802.1d Bridge-Based EPLAN Services) .....................................................5-44 5.4.1 Networking Diagram............................................................................................................................5-44 5.4.2 Service Planning...................................................................................................................................5-46 5.4.3 Configuration Process..........................................................................................................................5-50 5.5 Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) ..................................................5-56 5.5.1 Networking Diagram............................................................................................................................5-56 5.5.2 Service Planning...................................................................................................................................5-58 5.5.3 Configuration Process..........................................................................................................................5-63

6 Configuring Clocks....................................................................................................................6-1 6.1 Basic Concepts................................................................................................................................................6-2 6.1.1 Clock Source..........................................................................................................................................6-2 6.1.2 Clock Synchronization Policy................................................................................................................6-2 6.2 Configuration Procedure.................................................................................................................................6-2 6.3 Configuration Example (Clock)......................................................................................................................6-3 6.3.1 Networking Diagram..............................................................................................................................6-3 6.3.2 Service Planning.....................................................................................................................................6-4 6.3.3 Configuration Process............................................................................................................................6-5

7 Configuring Auxiliary Interfaces and Functions.................................................................7-1 7.1 Auxiliary Interfaces and Functions.................................................................................................................7-2 7.2 Configuration Example (Orderwire)...............................................................................................................7-4 7.2.1 Networking Diagram..............................................................................................................................7-4 viii


Issue 03 (2010-05-30)


Contents

7.2.2 Service Planning.....................................................................................................................................7-4 7.2.3 Configuration Process............................................................................................................................7-6 7.3 Configuration Example (Synchronous Data Services)....................................................................................7-6 7.3.1 Networking Diagram..............................................................................................................................7-6 7.3.2 Service Planning.....................................................................................................................................7-7 7.3.3 Configuration Process............................................................................................................................7-7 7.4 Configuration Example (Asynchronous Data Services)................................................................................. 7-8 7.4.1 Networking Diagram..............................................................................................................................7-8 7.4.2 Service Planning.....................................................................................................................................7-9 7.4.3 Configuration Process............................................................................................................................7-9 7.5 Configuration Example (External Alarms)...................................................................................................7-10 7.5.1 Networking Diagram............................................................................................................................7-10 7.5.2 Service Planning...................................................................................................................................7-11 7.5.3 Configuration Process..........................................................................................................................7-12

A Supporting Task.......................................................................................................................A-1 A.1 Managing NEs...............................................................................................................................................A-3 A.1.1 Creating NEs by Using the Search Method..........................................................................................A-3 A.1.2 Creating NEs by Using the Manual Method........................................................................................A-4 A.1.3 Logging In to an NE.............................................................................................................................A-6 A.1.4 Changing NE IDs.................................................................................................................................A-8 A.1.5 Changing NE Names..........................................................................................................................A-10 A.1.6 Synchronizing NE Time.....................................................................................................................A-10 A.1.7 Localizing NE Time...........................................................................................................................A-15 A.2 Configuring Performance Monitoring Status of NEs..................................................................................A-17 A.3 Managing Communication..........................................................................................................................A-18 A.3.1 Setting NE Communication Parameters.............................................................................................A-19 A.3.2 Configuring DCCs..............................................................................................................................A-21 A.3.3 Configuring the Extended ECC..........................................................................................................A-23 A.3.4 Creating Static IP Routes....................................................................................................................A-24 A.3.5 Setting Parameters of the OSPF Protocol...........................................................................................A-25 A.3.6 Enabling the ARP Proxy....................................................................................................................A-26 A.3.7 Querying ECC Routes........................................................................................................................A-26 A.3.8 Querying IP Routes............................................................................................................................A-27 A.4 Configuring Service Access of NEs ...........................................................................................................A-27 A.4.1 Configuring LCT Access to NEs........................................................................................................A-27 A.4.2 Configuring Ethernet Access to NEs..................................................................................................A-28 A.4.3 Configuring Serial Interface Access to NEs.......................................................................................A-29 A.5 Managing Radio Links................................................................................................................................A-30 A.5.1 Modifying Parameters of IF 1+1 Protection.......................................................................................A-31 A.5.2 Configuring the IF/ODU Information of a Radio Link......................................................................A-34 A.5.3 Setting the Hybrid/AM Attribute........................................................................................................A-39 A.5.4 Configuring the ATPC function.........................................................................................................A-41 Issue 03 (2010-05-30)


ix


Contents

A.5.5 Setting Parameters of IF Interfaces....................................................................................................A-43 A.5.6 Setting Parameters of ODU Interfaces...............................................................................................A-46 A.5.7 Querying ATPC Adjustment Records................................................................................................A-49 A.5.8 Querying History Transmit Power and Receive Power .....................................................................A-49 A.5.9 Querying the AM Status.....................................................................................................................A-50 A.5.10 Querying the IF 1+1 Protection Status.............................................................................................A-50 A.5.11 Performing IF 1+1 Protection Switching.........................................................................................A-51 A.6 Configuring the Monitored Status of E1 Interfaces....................................................................................A-52 A.7 Managing Clocks.........................................................................................................................................A-53 A.7.1 Configuring Clock Sources of the OptiX RTN 605 1E/2E................................................................A-53 A.7.2 Configuring the Ethernet Clock Source of the OptiX RTN 605 1F/2F..............................................A-54 A.7.3 Querying the Current NE Clock Source.............................................................................................A-55 A.8 Managing the STP.......................................................................................................................................A-56 A.8.1 Configuring the Spanning Tree Protocol............................................................................................A-56 A.8.2 Setting the Parameters of Spanning Tree Protocol ............................................................................A-57 A.8.3 Querying the Running Information About the Spanning Tree Protocol............................................A-61 A.9 Managing LAGs .........................................................................................................................................A-62 A.9.1 Creating a LAG..................................................................................................................................A-62 A.9.2 Setting the Port Priority......................................................................................................................A-67 A.9.3 Querying the Protocol Information of the LAG.................................................................................A-71 A.10 Managing the QoS.....................................................................................................................................A-71 A.10.1 Creating a Flow................................................................................................................................A-72 A.10.2 Creating the CAR.............................................................................................................................A-73 A.10.3 Creating the CoS...............................................................................................................................A-76 A.10.4 Binding the CAR/CoS......................................................................................................................A-78 A.10.5 Configuring the Queue Scheduling Mode........................................................................................A-79 A.11 Using the IEEE 802.1ag OAM .................................................................................................................A-80 A.11.1 Creating MDs...................................................................................................................................A-81 A.11.2 Creating MAs...................................................................................................................................A-83 A.11.3 Creating MPs....................................................................................................................................A-84 A.11.4 Performing a CC Test.......................................................................................................................A-87 A.11.5 Performing an LB Check .................................................................................................................A-88 A.11.6 Performing a Link Trace Check.......................................................................................................A-89 A.11.7 Activating the AIS............................................................................................................................A-91 A.11.8 Performing a Ping Test ....................................................................................................................A-92 A.11.9 Performing Performance Detection..................................................................................................A-94 A.12 Using the IEEE 802.3ah OAM..................................................................................................................A-96 A.12.1 Enabling the OAM Auto-Discovery Function.................................................................................A-96 A.12.2 Enabling the Link Event Notification...............................................................................................A-98 A.12.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold ................................A-101 A.12.4 Performing the Remote Loopback..................................................................................................A-103 A.12.5 Enabling the Self-Loop Detection .................................................................................................A-105 x


Issue 03 (2010-05-30)


Contents

A.13 Using RMON...........................................................................................................................................A-106 A.13.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.................................A-107 A.13.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-108 A.13.3 Configuring a History Control Group............................................................................................A-109 A.13.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-110 A.14 Configuring Ethernet Ports......................................................................................................................A-111 A.14.1 Configuring External Ethernet Ports..............................................................................................A-111 A.14.2 Configuring the IFUP Port of the Ethernet Board..........................................................................A-118 A.14.3 Modifying the Type Field of QinQ Frames....................................................................................A-121 A.15 Configuring Ethernet Services................................................................................................................A-122 A.15.1 Creating Ethernet LAN Services....................................................................................................A-122 A.15.2 Modifying the Mounted Port of a Bridge.......................................................................................A-126 A.15.3 Creating the VLAN Filtering Table...............................................................................................A-129 A.15.4 Creating QinQ Private Line Services.............................................................................................A-131 A.15.5 Deleting an Ethernet Private Line Service.....................................................................................A-134 A.15.6 Creating an Ethernet LAN Service.................................................................................................A-134 A.16 Managing the MAC Address Table.........................................................................................................A-135 A.16.1 Creating a Static MAC Address Entry...........................................................................................A-136 A.16.2 Creating a Blacklist Entry of a MAC Address...............................................................................A-137 A.16.3 Setting the Aging Time of a MAC Address Table Entry...............................................................A-138 A.16.4 Querying or Deleting a Dynamic MAC Address...........................................................................A-140 A.17 Modifying E1 Port Impedance................................................................................................................A-141 A.18 Configuring Auxiliary Interfaces and Functions.....................................................................................A-142 A.18.1 Configuring the Orderwire.............................................................................................................A-142 A.18.2 Configuring Synchronous Data Service.........................................................................................A-144 A.18.3 Configuring Asynchronous Data Service.......................................................................................A-145 A.18.4 Configure External Alarms.............................................................................................................A-146 A.19 Testing Ethernet Services........................................................................................................................A-148

B Glossary......................................................................................................................................B-1 B.1 0-9..................................................................................................................................................................B-2 B.2 A-E.................................................................................................................................................................B-2 B.3 F-J................................................................................................................................................................B-11 B.4 K-O..............................................................................................................................................................B-16 B.5 P-T................................................................................................................................................................B-22 B.6 U-Z...............................................................................................................................................................B-30

Issue 03 (2010-05-30)


xi


Figures

Figures Figure 2-1 HWECC solution................................................................................................................................2-3 Figure 2-2 Networking diagram...........................................................................................................................2-8 Figure 2-3 Board configuration............................................................................................................................2-9 Figure 2-4 Allocated IDs and IP addresses........................................................................................................2-10 Figure 3-1 Mini PDH radio link...........................................................................................................................3-2 Figure 3-2 Mini IP radio link...............................................................................................................................3-3 Figure 3-3 Hybrid radio link................................................................................................................................3-3 Figure 3-4 AM......................................................................................................................................................3-4 Figure 3-5 Networking diagram...........................................................................................................................3-9 Figure 4-1 Networking diagram...........................................................................................................................4-3 Figure 5-1 Tagged Frame Format........................................................................................................................5-6 Figure 5-2 Ethernet frame format with a C-TAG and an S-TAG........................................................................5-8 Figure 5-3 Ethernet frame format with only an S-TAG.......................................................................................5-8 Figure 5-4 802.1d bridge and 802.1q bridge......................................................................................................5-10 Figure 5-5 Link aggregation group....................................................................................................................5-13 Figure 5-6 Networking diagram of the STP/RSTP application.........................................................................5-14 Figure 5-7 CAR processing................................................................................................................................5-15 Figure 5-8 Traffic shaping..................................................................................................................................5-17 Figure 5-9 Queues with different priorities........................................................................................................5-17 Figure 5-10 WRR scheduling algorithm............................................................................................................5-18 Figure 5-11 Networking diagram (QinQ-based EVPL services).......................................................................5-32 Figure 5-12 Networking diagram (IEEE 802.1d bridge-based EPLAN services).............................................5-45 Figure 5-13 Networking diagram (IEEE 802.1q bridge-based EVPLAN services)..........................................5-57 Figure 6-1 Networking diagram...........................................................................................................................6-4 Figure 6-2 Information about clock sources.........................................................................................................6-4 Figure 7-1 Circuits for external alarm input.........................................................................................................7-3 Figure 7-2 Networking diagram (orderwire)........................................................................................................7-4 Figure 7-3 Networking diagram (orderwire)........................................................................................................7-5 Figure 7-4 Networking diagram (synchronous data services)..............................................................................7-7 Figure 7-5 Networking diagram (asynchronous data services)............................................................................7-9 Figure 7-6 Networking diagram (external alarms).............................................................................................7-11 Figure A-1 Networking diagram for testing the Ethernet service ..................................................................A-149

Issue 03 (2010-05-30)


xiii


Tables

Tables Table 1-1 Procedure for initial configuration.......................................................................................................1-2 Table 2-1 Mapping relationships between IDU and logical boards.....................................................................2-4 Table 2-2 Procedure for configuring NEs............................................................................................................2-5 Table 3-1 Procedure for configuring a Mini PDH/IP radio link...........................................................................3-5 Table 3-2 Procedure for configuring a Hybrid radio link.....................................................................................3-7 Table 3-3 Basic information about radio links...................................................................................................3-10 Table 3-4 Power and ATPC information............................................................................................................3-11 Table 3-5 Information about IF boards...............................................................................................................3-11 Table 4-1 Procedure for configuring TDM services.............................................................................................4-2 Table 4-2 Information about E1 services.............................................................................................................4-3 Table 4-3 Information about channel impedance of E1 interfaces.......................................................................4-4 Table 4-4 Information about E1 services.............................................................................................................4-4 Table 4-5 Information about channel impedance of E1 interfaces.......................................................................4-4 Table 5-1 Auto-negotiation rules of FE electrical ports (when the local interface works in the auto-negotiation mode).....................................................................................................................................................................5-3 Table 5-2 Auto-negotiation rules of GE electrical ports (when the local interface works in auto-negotiation mode) ...............................................................................................................................................................................5-4 Table 5-3 Frame processing modes of Ethernet interfaces...................................................................................5-7 Table 5-4 List of bridges....................................................................................................................................5-10 Table 5-5 QinQ-based EVPL service model......................................................................................................5-11 Table 5-6 Models of IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services .............................................................................................................................................................................5-12 Table 5-7 Specifications of QoS.........................................................................................................................5-18 Table 5-8 Procedure for configuring QinQ-based EVPL services.....................................................................5-20 Table 5-9 Procedure for configuring IEEE 802.1d bridge-based EPLAN services...........................................5-24 Table 5-10 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services......................................5-28 Table 5-11 Connections of Ethernet links (NE4)...............................................................................................5-33 Table 5-12 Connections of Ethernet links (NE5)...............................................................................................5-33 Table 5-13 Information about Ethernet interfaces (NE4)...................................................................................5-33 Table 5-14 Information about Ethernet interfaces (NE5)...................................................................................5-34 Table 5-15 Information about Ethernet internal interfaces (NE4)......................................................................5-34 Table 5-16 Information about Ethernet internal interfaces (NE5)......................................................................5-35 Table 5-17 Information about the QinQ-based EVPL service (NE4)................................................................5-35 Table 5-18 Information about the QinQ-based EVPL service (NE5)................................................................5-35 Issue 03 (2010-05-30)


xv


Tables

Table 5-19 Flow (NE4).......................................................................................................................................5-36 Table 5-20 Flow (NE5).......................................................................................................................................5-36 Table 5-21 CAR (services accessed from BTS2 to NE5).................................................................................. 5-37 Table 5-22 VLAN priorities corresponding to different service types (BTS)....................................................5-37 Table 5-23 CoS parameters (NE4 and NE5)......................................................................................................5-38 Table 5-24 QoS (queue scheduling)...................................................................................................................5-38 Table 5-25 Connections of Ethernet links (NE1)...............................................................................................5-45 Table 5-26 Connections of Ethernet links (NE2)...............................................................................................5-45 Table 5-27 Information about Ethernet external interfaces (NE1)....................................................................5-46 Table 5-28 Information about Ethernet external interfaces (NE2)....................................................................5-46 Table 5-29 Information about Ethernet internal interfaces (NE1).....................................................................5-47 Table 5-30 Information about Ethernet internal interfaces (NE2).....................................................................5-47 Table 5-31 Information about the IEEE 802.1d bridge-based EPLAN service (NE1)...................................... 5-47 Table 5-32 Information about the IEEE 802.1d bridge-based EPLAN service (NE2)..................................... 5-47 Table 5-33 Flow (NE1).......................................................................................................................................5-48 Table 5-34 Flow (NE2).......................................................................................................................................5-48 Table 5-35 CAR (services accessed from BTS1 to NE2)................................................................................. 5-49 Table 5-36 CoS attributes of the EMS4 boards..................................................................................................5-49 Table 5-37 CoS parameters of the EMS4 boards...............................................................................................5-49 Table 5-38 Queue scheduling on the EMS4 board.............................................................................................5-50 Table 5-39 Connections of Ethernet links (NE1)...............................................................................................5-57 Table 5-40 Connections of Ethernet links (NE2)...............................................................................................5-57 Table 5-41 Information about Ethernet external interfaces (NE1).....................................................................5-58 Table 5-42 Information about Ethernet external interfaces (NE2).....................................................................5-58 Table 5-43 Information about Ethernet internal interfaces (NE1)......................................................................5-59 Table 5-44 Information about Ethernet internal interfaces (NE2)......................................................................5-59 Table 5-45 Information about the IEEE 802.1q bridge-based EVPLAN service (NE1)....................................5-59 Table 5-46 Information about the IEEE 802.1q bridge-based EVPLAN service (NE2)....................................5-60 Table 5-47 CAR parameters (services accessed from BTS1 to NE2)................................................................5-60 Table 5-48 VLAN priorities corresponding to different service types (BTS)....................................................5-61 Table 5-49 CoS parameters (NE1 and NE2)......................................................................................................5-61 Table 5-50 Flow (NE1).......................................................................................................................................5-62 Table 5-51 Flow (NE1).......................................................................................................................................5-62 Table 5-52 Queue scheduling (NE1 and NE2)...................................................................................................5-63 Table 6-1 Procedures for configuring clock sources............................................................................................6-3 Table 7-1 Information about orderwire interfaces................................................................................................7-5 Table 7-2 Information about the synchronous data service..................................................................................7-7 Table 7-3 Information about the asynchronous data service................................................................................7-9 Table 7-4 Information about input alarms..........................................................................................................7-11 Table 7-5 Information about output alarms........................................................................................................7-12 Table A-1 Parameters..........................................................................................................................................A-8 Table A-2 Parameters..........................................................................................................................................A-9 xvi


Issue 03 (2010-05-30)


Tables

Table A-3 Parameters........................................................................................................................................A-12 Table A-4 Parameters of the standard NTP server............................................................................................A-14 Table A-5 Parameters of the access control rights............................................................................................A-14 Table A-6 Parameters of the NTP key management.........................................................................................A-15 Table A-7 Parameters........................................................................................................................................A-17 Table A-8 Parameters........................................................................................................................................A-20 Table A-9 Parameters........................................................................................................................................A-22 Table A-10 Parameters......................................................................................................................................A-24 Table A-11 Parameters......................................................................................................................................A-25 Table A-12 Parameters......................................................................................................................................A-30 Table A-13 Parameters......................................................................................................................................A-32 Table A-14 Parameters......................................................................................................................................A-35 Table A-15 Parameters......................................................................................................................................A-40 Table A-16 Parameters......................................................................................................................................A-42 Table A-17 Parameters......................................................................................................................................A-45 Table A-18 Parameters......................................................................................................................................A-47 Table A-19 Parameters......................................................................................................................................A-53 Table A-20 Parameters......................................................................................................................................A-82 Table A-21 Parameters......................................................................................................................................A-84 Table A-22 Parameters......................................................................................................................................A-86 Table A-23 Parameters......................................................................................................................................A-89 Table A-24 Parameters......................................................................................................................................A-90 Table A-25 Parameters......................................................................................................................................A-92 Table A-26 Parameters......................................................................................................................................A-93 Table A-27 Parameters......................................................................................................................................A-95 Table A-28 Parameters......................................................................................................................................A-97 Table A-29 Parameters....................................................................................................................................A-100 Table A-30 Parameters....................................................................................................................................A-102 Table A-31 Parameters....................................................................................................................................A-104 Table A-32 Parameters....................................................................................................................................A-106 Table A-33 Parameters....................................................................................................................................A-107 Table A-34 Parameters....................................................................................................................................A-108 Table A-35 Parameters....................................................................................................................................A-109 Table A-36 Parameters....................................................................................................................................A-110 Table A-37 Parameters for the basic attributes................................................................................................A-113 Table A-38 Parameters for flow control..........................................................................................................A-114 Table A-39 Parameters for the TAG attributes................................................................................................A-115 Table A-40 Parameters for the network attributes...........................................................................................A-116 Table A-41 Parameters for the advanced attributes.........................................................................................A-116 Table A-42 Methods used by ports to process data frames.............................................................................A-117 Table A-43 Parameters for the TAG attributes................................................................................................A-119 Table A-44 Parameters for the network attributes...........................................................................................A-120 Issue 03 (2010-05-30)


xvii


Tables

Table A-45 Methods used by ports to process data frames.............................................................................A-120 Table A-46 Parameters on the main interface.................................................................................................A-125 Table A-47 Parameters of service mounting...................................................................................................A-126 Table A-48 Methods used by ports to process data frames.............................................................................A-128 Table A-49 Parameters on the main interface.................................................................................................A-132 Table A-50 Parameters of port attributes.........................................................................................................A-134 Table A-51 Parameters....................................................................................................................................A-141 Table A-52 Parameters....................................................................................................................................A-144 Table A-53 Parameters (input relay)...............................................................................................................A-147 Table A-54 Parameters (output relay).............................................................................................................A-147

xviii


Issue 03 (2010-05-30)


1 Configuration Preparations

1

Configuration Preparations

About This Chapter Before configuring NE data, you must make the required preparations. 1.1 Preparing Documents and Tools The relevant documents and tools must be available to ensure correct configuration of NE data. 1.2 Checking Configuration Conditions Before configuring NE data, check whether configuration conditions meet relevant requirements. 1.3 Specifying the Configuration Procedure You need to select an appropriate configuration mode according to the actual configuration scenario.

Issue 03 (2010-05-30)


1-1



1.1 Preparing Documents and Tools The relevant documents and tools must be available to ensure correct configuration of NE data.

Documents l

Network planning documents, such as the XXX Network Planning

l

OptiX RTN 605 Radio Transmission System Configuration Guide

Tools A computer where the Web LCT software is installed NOTE

For information about the software and hardware required for the Web LCT and the installation method, refer to the documents that accompany the Web LCT.

1.2 Checking Configuration Conditions Before configuring NE data, check whether configuration conditions meet relevant requirements.

Context Ensure that the following requirements are met: l

All the NEs on the network must be powered on and operate normally.

l

The GNE must communicate with non-GNEs normally over the data communication network (DCN).

l

The NEs must gain the access to the computer where the Web LCT software is installed.

1.3 Specifying the Configuration Procedure You need to select an appropriate configuration mode according to the actual configuration scenario.

Procedure for Initial Configuration Initial configuration of a radio network is to configure the network-wide service data by using the NMS for the first time after NE commissioning is complete. Table 1-1 describes the configuration procedure. Table 1-1 Procedure for initial configuration

1-2

Step

Operation

Configuration

1

2 Configuring NEs

Required.

2

3 Configuring Radio Links

Required.


Issue 03 (2010-05-30)


Issue 03 (2010-05-30)


Step

Operation

Configuration

3

4 Configuring TDM Services

Required when TDM services are configured.

4

5 Configuring Ethernet Services

Required when Ethernet services are configured.

4

6 Configuring Clocks

Required.

6

7 Configuring Auxiliary Interfaces and Functions

Required when the orderwire information, or synchronous/ asynchronous data service needs to be transmitted or when the external alarm input/output function needs to be enabled.


1-3


2 Configuring NEs

2

Configuring NEs

About This Chapter You can manage a transport network by using the Web LCT only after configuring NEs on the network. 2.1 Basic Concepts Before configuring NEs, you need to be familiar with the basic concepts. 2.2 Configuration Procedure This section describes the procedures for configuring an NE and the NE attributes. 2.3 Configuration Example (Configuring NEs) This section considers the NEs on a radio network as an example to describe how to configure NEs according to the service planning information.

Issue 03 (2010-05-30)


2-1


2 Configuring NEs

2.1 Basic Concepts Before configuring NEs, you need to be familiar with the basic concepts. 2.1.1 DCN To manage and maintain an NE, the NMS needs to communicate with the NE over the DCN. 2.1.2 GNE and Non-GNE A gateway NE (GNE) refers to an NE whose application layer communicates directly with the application layer of the NMS. A non-GNE refers to an NE whose application layer communicates with the application layer of the NMS by forwarding data through the application layer of its GNE. 2.1.3 ID and IP Address of an NE The ID and IP address are the unique identifiers of an NE on the DCN. 2.1.4 Physical Boards and Logical Boards When managing a physical board, the NE software considers the physical board as one or more logical boards. The NMS also considers a physical board as one or more logical boards when managing the physical board.

2.1.1 DCN To manage and maintain an NE, the NMS needs to communicate with the NE over the DCN. On a DCN, the NMS and all the NEs are considered as nodes on the DCN. The DCN between the NMS and all the NEs is considered as the external DCN, and the DCN between the NEs is considered as the internal DCN. The OptiX RTN 605 supports several DCN solutions, including HWECC and IP over DCC. HWECC is the most common DCN solution. HWECC is the default DCN solution provided by the OptiX RTN 605. In the case of HWECC, the network management (NM) message is encapsulated in the proprietary HWECC protocol stack. Hence, the HWECC solution is easy to configure. As a proprietary protocol stack, however, HWECC can be used only when there is one isolated OptiX RTN 605 NE or when the OptiX RTN 605 NE operates with other OptiX equipment that supports HWECC. Figure 2-1 shows how the NM message is transmitted when HWECC is used. The NM message encapsulated in the HWECC protocol stack can be transmitted in the DCC channels over optical fibers or radio links, and can also be transmitted over the Ethernet between the Ethernet NM interfaces or between the NE cascading interfaces. If there are no fiber connections or radio links between two NEs, ensure that an Ethernet connection is set up between the corresponding Ethernet NM interfaces or NE cascading interfaces on the NEs. Otherwise, the communication between the two NEs fails. The Ethernet connection between the corresponding Ethernet NM interfaces or NE cascading interfaces functions as the extended channel for transmitting the HWECC protocol stack and is hence considered as the extended ECC. In the case of the OptiX RTN 605, the extended ECC function is enabled by default.

2-2


Issue 03 (2010-05-30)


2 Configuring NEs

Figure 2-1 HWECC solution

Message HWECC DCC

Message HWECC DCC

Message HWECC ETH

Message HWECC DCC

NMS Message HWECC DCC

Message HWECC DCC

OptiX radio transmission equipment

OptiX optical transmission equipment Radio link

Fiber

Ethernet link

2.1.2 GNE and Non-GNE A gateway NE (GNE) refers to an NE whose application layer communicates directly with the application layer of the NMS. A non-GNE refers to an NE whose application layer communicates with the application layer of the NMS by forwarding data through the application layer of its GNE.

GNE A GNE is usually connected to the NMS through a LAN/WAN. The application layer of the NMS directly communicates with the application layer of a GNE. One set of NMS needs to be connected to one or more GNEs. To prevent an oversized DCN that is caused due to the ECC communication between GNEs, you need to disable the extended ECC function of the GNEs.

Non-GNE A non-GNE communicates with its GNE through the DCN channels between NEs. It is recommended that fewer than 50 non-GNEs are connected to a GNE.

2.1.3 ID and IP Address of an NE The ID and IP address are the unique identifiers of an NE on the DCN. Issue 03 (2010-05-30)


2-3


2 Configuring NEs

ID of an NE At the application layer of each DCN solution, the NE ID is considered as the address of each OptiX NE. The NE IDs must therefore be unique to each other on the DCN and complies with the uniform DCN planning information. An NE ID has 24 bits. The higher eight bits represent the subnet ID (or the extended ID) and the lower 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID of the NE is 9 and the basic ID is 1.

IP Address of an NE An NE uses the IP address as its unique identifier during TCP/IP communication. In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following scenarios: l

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

l

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

By default (that is, if the IP address of an NE is not changed manually), the IP address and ID of an NE interlock each other. That is, when the NE ID is changed, the IP address is automatically changed to be 0x81000000 + ID. For example, when the NE ID is changed to 0x090001, the IP address is automatically changed to 129.9.0.1. After the IP address is changed manually, the interlocking relationship between the ID and IP address fails.

2.1.4 Physical Boards and Logical Boards When managing a physical board, the NE software considers the physical board as one or more logical boards. The NMS also considers a physical board as one or more logical boards when managing the physical board. Table 2-1 describes the mapping relationships between physical boards and logical boards of the OptiX RTN 605. Table 2-1 Mapping relationships between IDU and logical boards

2-4

IDU

Logical Board

IDU 605 1D

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + IF0 in slot 8

IDU 605 2D

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + IF0 in slot 7 + IF0 in slot 8

IDU 605 1E

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + EM4T in slot 5 + IF0 in slot 8

IDU 605 2E

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + EM4T in slot 5 + IF0 in slot 7 + IF0 in slot 8

IDU 605 1F

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + EMS4 in slot 5 + IFH1 in slot 8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


2 Configuring NEs

IDU

Logical Board

IDU 605 2F

PW48B in slot 1 + SCC in slot 2 + EOW in slot 3 + PH1 in slot 4 + EMS4 in slot 5 + IFH1 in slot 7 + IFH1 in slot 8

ODU

ODU in the slot whose number is 10 plus the slot number of the IF board that is connected to the ODU

2.2 Configuration Procedure This section describes the procedures for configuring an NE and the NE attributes. Table 2-2 Procedure for configuring NEs Step

Operation

1

Creating NEs on the NMS

3

Issue 03 (2010-05-30)

Description A.1.2 Creating NEs by Using the Manual Method

It is recommended that you perform this operation when you need to add one or more NEs on a large existing network by using the NMS.

A.1.1 Creating NEs by Using the Search Method

It is recommended that you perform this operation when you need to create NEs by using the NMS in other cases. Set the parameters as follows:

A.1.4 Changing NE IDs

Domain: When the IP address of the GNE is known, it is recommended that you set the IP address of the GNE as the search domain. In the case of initial configuration, it is recommended that you set the 129.9.255.255 network segment as the search domain. Required. Set the parameters as follows: l

Set New ID to be the NE ID specified in the DCN planning information.

l

If a unique extended NE ID is required, change New Extended ID.


2-5


2 Configuring NEs

Step

Operation

Description

4

A.3.1 Setting NE Communication Parameters

Required. Set the parameters as follows: l

In the case of a GNE, set IP and Subnet Mask according to the planning information of the external DCN.

l

In the case of a GNE, set Gateway IP if the external DCN requires.

l

In the case of a non-GNE, it is recommended that you set IP to 0x81000000 + NE ID. That is, if the NE ID is 0x090001, set IP to 129.9.0.1. Set Subnet Mask to 255.255.0.0.

NOTE If the IP address of an NE has not been changed manually, the IP address changes according to the NE ID and is always 0x81000000 + NE ID. In this case, the IP address of a non-GNE need not be changed manually.

5

A.1.5 Changing NE Names

Optional.

6

A.3.3 Configuring the Extended ECC

Required in the case of a GNE. Set the parameters as follows: l

Set ECC Extended Mode to Specified Mode.

l

Adopt the default values for the other parameters.

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

7

2-6

A.2 Configuring Performance Monitoring Status of NEs

The 15-minute and 24-hour NE performance monitoring functions are enabled by default and thus need not be set manually.


Issue 03 (2010-05-30)


2 Configuring NEs

Step

Operation

8

Synchroni zing the NE time

Description A.1.6 Synchron izing NE Time


l

Issue 03 (2010-05-30)

To synchronize the NEs with the NM server, set the relevant parameters as follows: –

Set Synchronous Mode to NM.

–

Right-click and choose the operation from the shortcut menu to ensure that the NE are synchronized with the NM time immediately.

–

Set the automatic synchronization parameters according to the requirements. It is recommended that the parameters adopt the default values.

To synchronize the NEs with the NTP server, set the relevant parameters as follows: –

Set Synchronous Mode to Standard NTP.

–

Set Standard NTP Authentication according to the requirements for the NTP server.

–

It is recommended that you set the upper level NTP server that the NEs trace as follows: –

In the case of a GNE, set the external NTP server to be the upper level NTP server. Set Standard NTP Server Flag to NE IP and set Standard NTP Server to the IP address of the external NTP server.

–

In the case of a non-GNE, set the GNE to be the upper level NTP server. If the non-GNE needs to communicate with the GNE through the HWECC protocol, set Standard NTP Server Flag to NE ID and set Standard NTP Server to the NE ID of the GNE. If the non-GNE needs to communicate with the GNE through the IP protocol, set Standard NTP Server Flag to NE IP and set Standard NTP Server to the IP address of the GNE.

–

Set Standard NTP Server Key according to the requirements for the NTP server.

–

To perform NTP service verification, configure the NTP key in the Standard NTP Key Management tab page.

–

To limit the access control rights of an NE when the local NE functions as the NTP server, set the access control rights of this NE in the Access Control Rights tab page.


2-7


2 Configuring NEs

Step

Operation

Description A.1.7 Localizin g NE Time

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

NOTE

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

2.3 Configuration Example (Configuring NEs) This section considers the NEs on a radio network as an example to describe how to configure NEs according to the service planning information. 2.3.1 Networking Diagram The section describes the networking information about the NEs. 2.3.2 Board Configuration Before performing networking planning, you need to be familiar with the board configuration information of each NE. 2.3.3 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.3.4 Configuration Process This section describes the procedure for data configuration.

2.3.1 Networking Diagram The section describes the networking information about the NEs. Figure 2-2 shows a backhaul radio subnet for a mobile base station. Figure 2-2 Networking diagram

BTS2 FE

RTN 605 2F

RTN 605 2F

E1 E1

NE5

RTN 605 2E

NE4 RTN 605 2E

FE

NE1

NE2

FE

E1

E1 E1 BTS3

NE3 NE6

RTN 605 1D

BTS1 BSC

RTN 605 1D

2-8


Issue 03 (2010-05-30)


2 Configuring NEs

2.3.2 Board Configuration Before performing networking planning, you need to be familiar with the board configuration information of each NE. NOTE

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

Figure 2-3 shows the board configuration of each NE on the radio network. Figure 2-3 Board configuration OptiX RTN 605 2E PW48A

SCC

EOW

PH1

EM4T

IF0

IF0

OptiX RTN 605 2E NE5

PW48A SCC

EOW

PH1

EM4T

IF0

IF0

PW48A

SCC

EOW

NE4

NE2

PH1

EMS4

SCC

EOW

IFH1

OptiX RTN 605 2F

OptiX RTN 605 2F PW48A

OptiX RTN 605 1D PW48A

IFH1

PH1

EOW

PH1

EMS4

IFH1

IFH1

NE1

IF0

OptiX RTN 605 1D NE6

SCC

PW48A SCC

EOW

PH1

BSC IF0

NE3

2.3.3 Service Planning The service planning information contains all the parameter information required for configuring the NE data. l

The Web LCT is connected to NE1 through the LAN. Hence, NE1 is the GNE and the other NEs are non-GNEs, which access the Web LCT through NE1.

l

The radio network comprises only the OptiX RTN 605s. Hence, HWECC is preferred as the DCN solution. In the HWECC solution, NE2 and NE4 communicate with each other through the extended ECC that is enabled by default; NE2 and NE3 also communicate with each other through the extended ECC that is enabled by default. The other NEs communicate with each other through the DCC channels over radio.

l

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

l

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

Issue 03 (2010-05-30)


2-9


2 Configuring NEs

Figure 2-4 Allocated IDs and IP addresses NMS

9-5 129.9.0.5 0.0.0.0

9-4 129.9.0.4 0.0.0.0

NE5

NE4

10.0.0.100/16

9-2 129.9.0.2 0.0.0.0

9-1 10.0.0.1 0.0.0.0

NE1

NE2 9-6 129.9.0.6 0.0.0.0

9-3 129.9.0.3 0.0.0.0

NE3

NE6

Extended ID-Basic ID IP address Gateway

NOTE

l

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 relationships with the NE IDs. Hence, if the IP address of an NE (not NE1) is not changed manually, the NE automatically changes the IP address to be the planned value after the NE ID is changed.

In this example, the policy of synchronizing the NE with the NM server is used. The automatic synchronization period is one day. The DST scheme is not used at the local area.

2.3.4 Configuration Process This section describes the procedure for data configuration.

Precautions If the NE ID and the values of NE communication parameters are changed 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 relevant parameters are provided as follows.

2-10

Parameter

Value

Domain

129.9.255.255


Issue 03 (2010-05-30)


2 Configuring NEs NOTE

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

Normally, NE1 to NE6 should be added in the NE list. Step 2 See A.1.3 Logging In to an NE and log in to the NEs. The values for the relevant parameters are provided as follows. Parameter

Value

User Name

lct

Password

password

Step 3 See A.1.4 Changing NE IDs and change the IDs of the NEs. The values for the relevant parameters are provided as follows. Paramete r

Value NE1

NE2

NE3

NE4

NE5

NE6

New ID

1

2

3

4

5

6

New Extended ID

9 (default value)

9 (default value)

9 (default value)

9 (default value)

9 (default value)

9 (default value)

Step 4 See A.3.1 Setting NE Communication Parameters and set NE communication parameters. The values for the relevant parameters are provided as follows. Parameter

Value NE1

IP

10.0.0.1

Gateway IP

0.0.0.0 (default value)

Subnet Mask


Extended ID

9

NOTE

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

Step 5 See A.3.3 Configuring the Extended ECC and configure the extend ECC. The values for the relevant parameters are provided as follows. Issue 03 (2010-05-30)


2-11


2 Configuring NEs

Parameter

Value NE1

ECC Extended Mode

Specified mode

Port (on the server side)

1601 (default value)

Opposite IP (on the client side)


Port (on the client side)

1601 (default value)

NOTE

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

Step 6 See A.1.6 Synchronizing NE Time and synchronize the NE time. The values for the relevant parameters are provided as follows. Parameter

Value All the Ports on All the NEs

Synchronous Mode

NM

Synchronization Period(days)

1

----End

2-12


Issue 03 (2010-05-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 Concepts Before configuring radio links, you need to be familiar with the basic concepts. 3.2 Configuration Procedure In different RF configuration modes, the procedures for configuring a radio link are different. 3.3 Configuration Example (Radio Links) This section considers the NEs on a radio network as examples to describe how to configure NEs according to the service planning information.

Issue 03 (2010-05-30)


3-1



3.1 Basic Concepts Before configuring radio links, you need to be familiar with the basic concepts. 3.1.1 Types of Radio Links The OptiX RTN 605 supports three types of radio links, namely, Mini PDH radio links, Mini IP radio links, and Hybrid radio links. 3.1.2 RF Configuration Modes The OptiX RTN 605 supports two RF configuration modes, namely, 1+0 non-protection configuration and 1+1 protection configuration. When adopting different IDUs, the OptiX RTN 605 supports different RF configuration modes.

3.1.1 Types of Radio Links The OptiX RTN 605 supports three types of radio links, namely, Mini PDH radio links, Mini IP radio links, and Hybrid radio links.

Mini PDH Radio Link A Mini PDH radio link refers to a radio link that transmits only PDH services (mainly, E1 services). During transmission, the features of the PDH services are not changed. Figure 3-1 Mini PDH radio link

E1

IDU

ODU

Mini PDH radio

A Mini PDH radio link supports only a fixed modulation mode. That is, in running state, all the equipment on a Mini PDH radio link always works in the same modulation mode. You can specify the modulation mode by using software.

Mini IP Radio Link A Mini IP radio link refers to a radio link that implements hybrid transmission of E1 services and low-capacity Ethernet services based on Mini IP radio features. After accessing E1 services, the OptiX RTN 605 directly transmits the E1 services to the microwave interface. After accessing Ethernet services, the OptiX RTN 605 processes the Ethernet services by means of the embedded packet processing plane and then transmits the Ethernet services to the microwave interface. The microwave interface maps the E1 services and the Ethernet services into Hybrid microwave frames and then transmits the Hybrid microwave frames. 3-2


Issue 03 (2010-05-30)



Figure 3-2 Mini IP radio link IDU E1

ODU

Mini IP radio

Ethernet Packet processing

Native E1 and native Ethernet

A Mini IP radio link supports only a fixed modulation mode. That is, in running state, all the equipment on a Mini IP radio link works in the same modulation mode. You can specify this modulation mode by using the software.

Hybrid Radio Link A Hybrid radio link refers to a radio link that implements hybrid transmission of Native E1 services and Native Ethernet services. A Hybrid radio link supports the AM function. After accessing E1 services, the OptiX RTN 605 directly transmits the E1 services to the microwave interface. After accessing Ethernet services, the OptiX RTN 605 processes the Ethernet services by means of the embedded packet processing plane and then transmits the Ethernet services to the microwave interface. The microwave interface maps the E1 services and the Ethernet services into Hybrid microwave frames and then transmits the Hybrid microwave frames. Figure 3-3 Hybrid radio link IDU E1

ODU

Hybrid radio

Ethernet Packet processing

Native E1 and native Ehernet

A Hybrid radio link supports both the fixed modulation mode and the AM mode. When the AM function is enabled, the equipment adopts a high-efficiency modulation mode to transmit as many user services as possible if the channel quality is favorable (such as on days when the weather is favorable). In this 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 low-efficiency modulation mode to transmit only services with higher priorities over the available bandwidth and to discard services with lower priorities. In this manner, the anti-interference capability of the radio link is improved and the link availability of the services with higher priorities is enhanced. Issue 03 (2010-05-30)


3-3



Figure 3-4 shows service changes caused by the AM function. The orange part indicates E1 services. The blue part indicates Ethernet services. The closer to the edge of the blue part, the lower the priority of the Ethernet services. Under all channel conditions, the E1 services occupy the specific bandwidth permanently. In this manner, the availability of the E1 services is enhanced. The bandwidth for Ethernet services varies with the channel conditions. When the channel is in poor conditions, Ethernet services with lower priorities are discarded. Figure 3-4 AM

256QAM 128QAM 32QAM QPSK 256QAM

128QAM

32QAM 16QAM

Channel Capability

64QAM

16QAM 64QAM

E1 Services Ethernet Services

3.1.2 RF Configuration Modes The OptiX RTN 605 supports two RF configuration modes, namely, 1+0 non-protection configuration and 1+1 protection configuration. When adopting different IDUs, the OptiX RTN 605 supports different RF configuration modes.

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

The OptiX RTN 605 1D/1E/1F adopts the 1+0 non-protection configuration.

1+1 Protection Configuration The 1+1 protection configuration indicates that a radio link has one working channel and one protection channel. The 1+1 protection configuration is classified into 1+1 HSB, 1+1 FD, and 1+1 SD. l

3-4

In 1+1 HSB protection configuration, the equipment provides 1+1 hot backup for the IF boards and ODUs at both ends of each hop of radio link, thus implementing protection. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


3 Configuring Radio Links l

In 1+1 FD protection configuration, the system uses two channels with a specific frequency interval to transmit and receive the same service signal and then selects a signal from the two channels. The 1+1 FD protection configuration reduces the impact on signal transmission caused by fading. The 1+1 FD protection configuration also supports the 1+1 HSB protection configuration.

l

In 1+1 SD protection configuration, the system uses two antennas with a specific space distance from each other to receive the same RF signal and then selects a signal from the two antennas. The 1+1 SD protection configuration reduces the impact on signal transmission caused by fading. The 1+1 SD protection configuration also supports the 1+1 HSB protection configuration. NOTE

The OptiX RTN 605 2D/2E/2F adopts the 1+1 HSB (by default), 1+1FD, or 1+1 SD protection configuration.

3.2 Configuration Procedure In different RF configuration modes, the procedures for configuring a radio link are different. NOTE

In the case of different NMS versions, the IF/ODU tag page may not support certain associated parameter settings. Therefore, you may need to perform the associated parameter settings in compliance with the following links: l

A.5.5 Setting Parameters of IF Interfaces for setting ATPC attributes

l

A.5.6 Setting Parameters of ODU Interfaces for setting power attributes and RF attributes

l

A.5.3 Setting the Hybrid/AM Attribute for setting Hybrid/AM attributes

Procedure for Configuring a Mini PDH/IP Radio Link Table 3-1 Procedure for configuring a Mini PDH/IP radio link Step

Operation

Description

1

A.5.1 Modifying Parameters of IF 1+1 Protection

The default values of the IF 1+1 protection for the OptiX RTN 605 are as follows: l

Working Mode: HSB

l

Revertive Mode: Revertive

l

WTR Time(s): 600

l

Enable Reverse Switching: Enable

Required when the planned parameter values are different from the default values.

Issue 03 (2010-05-30)


3-5



Step

Operation

Description

2

A.5.2 Configuring the IF/ODU Information of a Radio Link


Set Work Mode, Link ID, and ATPC Enable Status according to the service planning information.

l

In the case of Mini IP radio, set E1 Capacity according to the service planning information.

l

During site commissioning, set ATPC Enable Status to Disabled.

l

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

l

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

l

It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.

l

Set TX Frequency (MHz), TX Power(dBm), and T/R Spacing(MHZ) according to the service planning information.

l

Set TX Status to unmute.

l

Set Power to Be Received(dBm) to the receive level specified in the service planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is beyond the range of the preset receive power ± 3 dB, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on and 300 ms off), indicating that the antennas are not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function.

l

To set the maximum transmit power that is supported by ATPC adjustment, you need to set Maximum Transmit Power(dBm) according to the actual requirements.

l

TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold (dBm) affect only the performance events associated with ATPC. Therefore, determine whether to set these parameters according to the actual requirements.

NOTE In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information only on the main radio link. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link.

3-6


Issue 03 (2010-05-30)


3 Configuring Radio Links NOTE

The preceding two steps are usually completed before site commissioning. After site commissioning, you need to re-set ATPC Enable Status according to the actual requirements.

Procedure for Configuring a Hybrid Radio Link Table 3-2 Procedure for configuring a Hybrid radio link Step

Operation

Operation

1

A.5.1 Modifying Parameters of IF 1+1 Protection

The default values of the IF 1+1 protection for the OptiX RTN 605 are as follows: l

Working Mode: HSB

l

Revertive Mode: Revertive

l

WTR Time(s): 600

l

Enable Reverse Switching: Enabled

Required when the planned parameter values are different from the default values.

Issue 03 (2010-05-30)


3-7



3-8

Step

Operation

Operation

2

A.5.2 Configuring the IF/ODU Information of a Radio Link


Set Enable AM and Channel Space according to the networking planning information.

l

When the AM function is enabled on a radio link, set Guaranteed Capacity Modulation and Full Capacity Modulation according to the service planning information.

l

When the AM function is disabled on a radio link, set Manually Specified Modulation according to the service planning information.

l

During site commissioning, set Enable AM to Disabled and set Manually Specified Modulation to Guaranteed Capacity Modulation according to the service planning information.

l

Set E1 Capacity, Link ID, and ATPC Enable Status according to the service planning information.

l

During site commissioning, set ATPC Enable Status to Disabled.

l

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

l

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

l

It is recommended that you set ATPC Automatic Threshold Enable to Disabled.

l

Set TX Frequency(MHz), T/R Spacing(MHz), and TX Power(dBm according to the service planning information.

l

Set TX Status to unmute.

l

Set Power to Be Received(dBm) to the receive level specified in the service planning information. The antenna non-alignment indication function is enabled only after this parameter is set. When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is beyond the range of the preset receive power ± 3 dB, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on and 300 ms off), indicating that the antennas are not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function.

l

To set the maximum transmit power that is supported by ATPC adjustment, you need to set Maximum Transmit Power(dBm) according to the actual requirements.

l

TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold (dBm) affect only the performance events associated with


Issue 03 (2010-05-30)



Step

Operation

Operation ATPC. Therefore, determine whether to set these parameters according to the actual requirements. NOTE In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information only on the main radio link. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link.

NOTE

Generally, during site commissioning, the preceding steps are already complete. After site commissioning, you need to re-set Enable AM and ATPC Enable Status.

3.3 Configuration Example (Radio Links) This section considers the NEs on a radio network as examples to describe how to configure NEs according to the service planning information. 3.3.1 Networking Diagram This section describes the networking information about the NEs. 3.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 3.3.3 Configuration Process This section describes the process for the data configuration.

3.3.1 Networking Diagram This section describes the networking information about the NEs. Based on 2.3 Configuration Example (Configuring NEs), configure the radio links according to the service planning information, as shown in Figure 3-5. Figure 3-5 Networking diagram 102 14952M 14532M 20M,7M,16QAM 1+1 HSB H-polarization

101 14930M 14510M 14M 1+1 HSB V-polarization

Tx high

BTS2 FE

E1

Tx low

NE5 RTN 605 2E

NE4 RTN 605 2E

Tx high

GE

NE2 E1 E1

4E1 BTS3

NE6 Tx high

RTN 605 1D

Issue 03 (2010-05-30)

RTN 605 2F

RTN 605 2F

E1

4E1+10Mbit/s

Tx low 103 14967M 14547M 5E1,7M,QPSK 1+0 V-polarization

Tx low

FE E1

NE1 GE

E1

BTS1

NE3

4E1+15Mbit/s

RTN 605 1D


BSC Link ID Tx high station Tx Freq. Tx low station Tx Freq. Radio work mode/Channel Spacing RF configuarion Polarization

3-9



For board configuration information, see 2.3.2 Board Configuration.

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

Basic Information About Radio Links According to the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about the radio links, as provided in Table 3-3. Table 3-3 Basic information about radio links Parameter

Link 1

Link 2

Link 3

Planned E1 capacity

12

4

4

Planned Ethernet capacity

25 Mbit/s

10 Mbit/s

-

Link ID

101

102

103

Tx high site

NE2

NE5

NE6

Tx low site

NE1

NE4

NE3

Tx frequency at the Tx high site (MHz)

14930

14952

14967

Tx frequency at the Tx low site (MHz)

14510

14532

14547

T/R spacing (MHz)

420

420

420

Channel spacing (MHz)

14M

7M

7M

Radio modulation mode

16QAM (AM guaranteed capacity mode)

16QAM

QPSK

32QAM (AM full capacity mode) RF configuration mode

1+1 HSB

1+1 HSB

1+0

Polarization direction

V (vertical polarization)

H (horizontal polarization)

V (vertical polarization)

NOTE

The planning information that is not associated with the configuration of the IDU (except for the polarization direction) is not provided in this example.

3-10


Issue 03 (2010-05-30)



Power and ATPC Information By using the radio service planning software such as the Pathloss, you can analyze and compute the availability of services and parameters of radio links. Then, you can obtain the power and ATPC information of the radio links as provided in Table 3-4. Table 3-4 Power and ATPC information Parameter

Link 1

Link 2

Link 3

Transmit power (dBm)

16.5 (NE2)

10 (NE5)

10 (NE6)

16.5 (NE1)

10 (NE4)

10 (NE3)

-44 (NE2)

-44 (NE5)

-43 (NE6)

-44 (NE1)

-44 (NE4)

-43 (NE3)

ATPC enabling

Disabled

Disabled

Disabled

ATPC automatic threshold enabling

-

-

-

Upper threshold of ATPC adjustment (dBm)

-

-

-

Lower threshold of ATPC adjustment (dBm)

-

-

-

Maximum transmit power (dBm)

-

-

-

Receive Power (dBm)

NOTE

l

In this example, the ATPC function is disabled.

l

The transmit power of link 1 is calculated in AM guaranteed capacity mode.

l

The receive power of link 1 is calculated in AM guaranteed capacity mode.

l

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

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

Link 1

Link 2

Link 3

Main IF board

8-IFH1 (NE2)

8-IF0 (NE5)

8-IF0 (NE6)

8-IFH1 (NE1)

8-IF0 (NE4)

8-IF0 (NE3)

Issue 03 (2010-05-30)


3-11



Parameter

Link 1

Link 2

Link 3

Standby IF board

7-IFH1 (NE2)

7-IF0 (NE5)

-

7-IFH1 (NE1)

7-IF0 (NE4)

RF configuration mode

1+1 HSB

1+1 HSB

1+0

Revertive mode

Revertive (default value)

Revertive (default value)

-

WTR time

600s (default value)

600s (default value)

-

Reverse switching enabling

Disabled

Disabled

-

NOTE

l

In the case of the OptiX RTN 605 2E and OptiX RTN 605 2F, the IF board in slot 8 is always the main IF board and the IF board in slot 7 is always the standby IF board.

l

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

l

In this example, the planned values of the 1+1 protection parameters are the same as the default values of the OptiX RTN 605. Therefore, you need not change the values of the 1+1 protection parameters in this example.

3.3.3 Configuration Process This section describes the process for the data configuration.

Procedure Step 1 See A.5.1 Modifying Parameters of IF 1+1 Protection and Modify the parameters of IF 1+1 Protection. l

The values for the relevant parameters of NE1 are provided as follows. Parameter

Value 8-IFH1

Enable Reverse Switching

l

Disabled


Value 8-IFH1


l

Disabled


Value 8-IF0

Enable Reverse Switching 3-12

Disabled


Issue 03 (2010-05-30)



l


Value 8-IF0


Disabled

Step 2 See A.5.2 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio links. NOTE

In the case of different NMS versions, the IF/ODU tag page may not support certain associated parameter settings. Therefore, you may need to perform the associated parameter settings in compliance with the following links:

l

l

A.5.5 Setting Parameters of IF Interfaces for setting ATPC attributes

l

A.5.6 Setting Parameters of ODU Interfaces for setting power attributes and RF attributes

l

A.5.3 Setting the Hybrid/AM Attribute for setting Hybrid/AM attributes


Value 8-IFH1 and 18-ODU

l

Issue 03 (2010-05-30)

IF Channel Bandwidth

14

Modulation Mode of the Guarantee AM Capacity

Enabled

Modulation Mode of the Full AM Capacity

16QAM

Manually Specified Modulation Mode

32QAM

E1 Capacity

12

Link ID

101

ATPC Enable Status

Disabled

TX Frequency (MHz)

14510

T/R Spacing(MHZ)

420

TX Power(dBm)

16.5

TX Status

unmute

Power to Be Received(dBm)

-44

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


3-13



Parameter

Value 8-IFH1 and 18-ODU

l


14

Modulation Mode of the Guarantee AM Capacity

Enabled


16QAM


32QAM

E1 Capacity

12

Link ID

101

ATPC Enable Status

Disabled

TX Frequency (MHz)

14930

T/R Spacing(MHZ)

420

TX Power(dBm)

16.5

TX Status

unmute


-44


Value 8-IF0 and 18-ODU

l

3-14

Work Mode

16,5E1,7MHz,QPSK

Link ID

103

ATPC Enable Status

Disabled

TX Frequency (MHz)

14547

T/R Spacing(MHZ)

420

TX Power(dBm)

10

TX Status

unmute


-43



Issue 03 (2010-05-30)



Parameter


l

Work Mode

20,20M,7MHz,16QAM

Link ID

102

E1 Capacity

4

ATPC Enable Status

Disabled

TX Frequency (MHz)

14532

T/R Spacing(MHZ)

420

TX Power(dBm)

10

TX Status

unmute


-44



l

Work Mode

20,20M,7MHz,16QAM

Link ID

102

E1 Capacity

4

ATPC Enable Status

Disabled

TX Frequency (MHz)

14952

T/R Spacing(MHZ)

420

TX Power(dBm)

10

TX Status

unmute


-44



Issue 03 (2010-05-30)

Work Mode

16,5E1,7MHz,QPSK

Link ID

103

ATPC Enable Status

Disabled


3-15



Parameter


TX Frequency (MHz)

14967

T/R Spacing(MHZ)

420

TX Power(dBm)

10

TX Status

unmute


-43

----End

3-16


Issue 03 (2010-05-30)



4

Configuring TDM Services

About This Chapter To configure TDM services, you need to configure the E1 interfaces for accessing the TDM services, rather than configuring the corresponding cross-connections. 4.1 Basic Concepts Before configuring TDM services, you need to be familiar with relevant basic concepts. 4.2 Configuration Procedure This section describes the procedure for configuring E1 services and E1 channel impedance. 4.3 Configuration Example (TDM Services) This section considers a radio network as an example and describes how to configure NEs according to the planning information.

Issue 03 (2010-05-30)


4-1



4.1 Basic Concepts Before configuring TDM services, you need to be familiar with relevant basic concepts. 4.1.1 Timeslots for TDM Services on the IF Unit The TDM service timeslots on the IF unit correspond to the E1 interfaces on the IDU. Therefore, you need not configure cross-connections between TDM service timeslots and E1 interfaces.

4.1.1 Timeslots for TDM Services on the IF Unit The TDM service timeslots on the IF unit correspond to the E1 interfaces on the IDU. Therefore, you need not configure cross-connections between TDM service timeslots and E1 interfaces. The TDM service timeslots on the IF unit correspond to the E1 interfaces on the IDU, when the IF unit works in any radio mode. That is, E1-1 corresponds to the first E1 timeslot on the IF unit, E1-2 corresponds to the second E1 timeslot on the IF unit, and E1-n corresponds to the nth E1 timeslot on the IF unit. In the case of Mini PDH radio, if the radio capacity is 5xE1/10xE1/16xE1, only the services from the first 5/10/16 E1 interfaces are transmitted over radio. In the case of Mini IP radio or Hybrid radio, when E1 Capacity is set to n, the services from n E1 interfaces are transmitted over radio.

4.2 Configuration Procedure This section describes the procedure for configuring E1 services and E1 channel impedance. Table 4-1 Procedure for configuring TDM services Step

Operation

Description

1

A.6 Configuring the Monitored Status of E1 Interfaces

Required. Set the parameters as follows:

2

A.17 Modifying E1 Port Impedance

Required if the actual E1 channel impedance is different from the default value (in the case of OptiX RTN 605, the default E1 channel impedance is 75 ohms).

3

Testing E1 Services Through PRBS

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

l

E1 ports that access services: selected

l

E1 ports that access no services: deselected

4.3 Configuration Example (TDM Services) This section considers a radio network as an example and describes how to configure NEs according to the planning information. 4.3.1 Networking Diagram The section describes the networking information about the NEs. 4-2


Issue 03 (2010-05-30)



4.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 4.3.3 Configuration Process This section describes the process for the data configuration.

4.3.1 Networking Diagram The section describes the networking information about the NEs. Based on 3.3 Configuration Example (Radio Links), configure TDM services according to the service requirements, as shown in Figure 4-1. Figure 4-1 Networking diagram RTN 605 2F

RTN 605 2F

4E1 Tx high

BTS2

NE5 RTN 605 2E

E1

Tx low

NE4

Tx high

RTN 605 2E

NE2

4E1

Tx low

NE1

E1

E1 Tx low

4E1 BTS3

NE3 RTN 605 1D

NE6 Tx high

BTS1 BSC

RTN 605 1D

For board configuration information, see 2.3.2 Board Configuration.


Information About E1 Services Table 4-2 Information about E1 services Parameter

NE1

NE2

NE3

NE4

NE5

NE6

E1 interfaces that access services

1 to12

1 to 12

1 to 4

1 to 4

1 to 4

1 to 4

Issue 03 (2010-05-30)


4-3



Information About Channel Impedance of E1 Interfaces Table 4-3 Information about channel impedance of E1 interfaces Parameter

NE1

NE2

NE3

NE4

NE5

NE6

Channel impedance

120 ohms

120 ohms

120 ohms

120 ohms

120 ohms

120 ohms


Procedure Step 1 See A.6 Configuring the Monitored Status of E1 Interfaces and configure E1 services. The values for the relevant parameters are provided as follows. Table 4-4 Information about E1 services Paramete r

NE1

NE2

NE3

NE4

NE5

NE6

E1-1 to E1-n ("n" indicates the number of E1 interfaces that are used.)

E1-1 to E1-12 (selected)






Step 2 See A.17 Modifying E1 Port Impedance and change channel impedance of E1 interfaces. The values for the relevant parameters are provided as follows. Table 4-5 Information about channel impedance of E1 interfaces Paramete r

NE1

NE2

NE3

NE4

NE5

NE6

Port Impedanc e

120 ohms

120 ohms

120 ohms

120 ohms

120 ohms

120 ohms

Step 3 See Testing E1 Services Through PRBS and test E1 services. 4-4


Issue 03 (2010-05-30)



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

Issue 03 (2010-05-30)


4-5



5

Configuring Ethernet Services

About This Chapter As classified by ITU-T Recommendations, Ethernet services has four types, namely, EPL services, EVPL services, EPLAN services, and EVPLAN services. The OptiX RTN 605 supports QinQ-based EVPL services, EPLAN services, and IEEE 802.1q bridge-based EVPLAN services. 5.1 Basic Concepts Before configuring Ethernet services, you need to be familiar with relevant basic concepts. 5.2 Configuration Procedure The configuration procedure varies according to the type of an Ethernet service. 5.3 Configuration Example (QinQ-Based EVPL Services) This section a QinQ-based EVPL service as an example to describe how to configure Ethernet services according to the service planning information. 5.4 Configuration Example (IEEE 802.1d Bridge-Based EPLAN Services) This section considers an IEEE 802.1d bridge-based EPLAN service as an example to describe how to configure Ethernet services according to the service planning information. 5.5 Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) This section considers an IEEE 802.1q bridge-based EVPLAN service as an example to describe how to configure Ethernet services according to the service planning information.

Issue 03 (2010-05-30)


5-1



5.1 Basic Concepts Before configuring Ethernet services, you need to be familiar with relevant basic concepts. 5.1.1 IFUP Interface When Ethernet services need to be transmitted over radio, you need to configure the Ethernet services between corresponding FE/GE interfaces and the IFUP interface in the OptiX RTN 605. 5.1.2 Auto-Negotiation The auto-negotiation function enables one network device to transmit information about its supported working modes to the opposite end on the network and to receive corresponding information from the opposite end on the network. 5.1.3 Flow Control When the data processing/transferring capability of an interface fails to handle the flow received by the interface, congestion occurs on the transmission line. To reduce the number of packets to be discarded due to buffer overflowing, appropriate flow control measures must be taken. 5.1.4 VLAN According to specific rules, an actual network topology can be divided into several logical subnetworks, which are referred to as VLANs. Packets can be broadcast only in the VLAN domain, that is, a VLAN corresponds to a broadcast domain. 5.1.5 QinQ QinQ is a technology that identifies different packet services by adding two layers of VLAN tags to the packets. QinQ adds the second layer of VLAN tag to extend the range of VLAN IDs. 5.1.6 Bridge A bridge refers to a functional unit that is used to connect two LANs or multiple LANs. 5.1.7 Hub/Spoke In the case of a convergence service, the mutual access between the non-central stations and central stations is required but the access between non-central stations is not required. In this case, specify a mounted port as a Hub port or a Spoke port. 5.1.8 Types of Ethernet Services The OptiX RTN 605 supports QinQ-based EVPL services, IEEE 802.1d bridge-based EPLAN services, and IEEE 802.1q bridge-based EVPLAN services. 5.1.9 Managing a MAC Address Table The entries in a MAC address table indicate the corresponding relationship between MAC addresses and ports. A MAC address table contains the following entries: dynamic entry, static entry, and blacklist entry. 5.1.10 Protection for Ethernet Services The OptiX RTN 605 supports two protection modes for Ethernet services, namely, link aggregation (LAG) and rapid spanning tree protocol (RSTP). 5.1.11 QoS QoS refers to the ability of a communication network to ensure the expected service quality under any conditions, in the aspects of bandwidth, delay, delay jitter, and packet loss ratio. QoS helps to ensure that the request and response from the user or the request and response from the application meet the requirements of an expected service class.

5-2


Issue 03 (2010-05-30)



5.1.1 IFUP Interface When Ethernet services need to be transmitted over radio, you need to configure the Ethernet services between corresponding FE/GE interfaces and the IFUP interface in the OptiX RTN 605. The IFUP interface is the internal GE interface that connects the Ethernet service unit and the IF unit in the OptiX RTN 605. In the transmit direction, the Ethernet service unit transmits Ethernet services to the IF unit through the IFUP interface. The IF unit maps the Ethernet services into microwave frames. In the receive direction, the IF unit demaps Ethernet services from microwave frames and transmits the Ethernet services to the Ethernet service unit through the IFUP interface. The main differences between the IFUP interface and GE/FE interfaces are as follows: l

The IFUP interface is the internal interface, which receives or transmits MAC frames and does not have PHY-layer functions.

l

The bandwidth over the IFUP interface is equal to the available Ethernet service bandwidth supported by the OptiX RTN 605.

l

In the case of the OptiX RTN 605 1F/2F, when the AM function is enabled, the bandwidth over the IFUP interface changes according to the modulation mode.

5.1.2 Auto-Negotiation The auto-negotiation function enables one network device to transmit information about its supported working modes to the opposite end on the network and to receive corresponding information from the opposite end on the network.

Auto-Negotiation Function of FE Electrical Interfaces FE electrical interfaces support four working modes, namely, 10M half-duplex, 10M full-duplex, 100M half-duplex, and 100M full-duplex. Two interfaces that work in different modes cannot communicate with each other. If the auto-negotiation function is enabled, however, the two interfaces can communicate with each other. The auto-negotiation function matches the working modes between the local interface and the opposite interface by transferring information about the negotiated working mode over fast link pulses and normal link pulses. Table 5-1 lists the auto-negotiation rules of FE electrical interfaces. Table 5-1 Auto-negotiation rules of FE electrical ports (when the local interface works in the auto-negotiation mode)

Issue 03 (2010-05-30)

Working Mode of the Opposite Interface

Auto-Negotiation Result

Auto-negotiation

100M full-duplex

10M half-duplex

10M half-duplex

10M full-duplex

10M half-duplex

100M half-duplex

100M half-duplex

100M full-duplex

100M half-duplex


5-3


5 Configuring Ethernet Services NOTE

As provided in Table 5-1, when the opposite interface works in 10M full-duplex or 100M full-duplex mode, auto-negotiation cannot match the working modes between the local interface and the opposite interface; as a result, packets may still be lost. Therefore, when the opposite interface works in 10M full-duplex or 100M fullduplex mode, you need to set the local interface to work in 10 full-duplex or 100M full-duplex mode manually.

When both the local FE interface and the opposite FE interface work in auto-negotiation mode, they can auto-negotiate flow control.

Auto-Negotiation Function of GE Electrical Interfaces GE electrical interfaces support five working modes, namely, 10M half-duplex, 10M fullduplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. As provided in Table 5-2, the auto-negotiation rules of GE electrical interfaces are similar to the auto-negotiation rules of FE electrical interfaces. Table 5-2 Auto-negotiation rules of GE electrical ports (when the local interface works in autonegotiation mode) Working Mode of the Opposite Interface

Auto-Negotiation Result

Auto-negotiation (GE electrical interface)

1000M full-duplex

Auto-negotiation (FE electrical interface)

100M full-duplex

10M half-duplex

10M half-duplex

10M full-duplex

10M half-duplex

100M half-duplex

100M half-duplex

100M full-duplex

100M half-duplex

1000M full-duplex

1000M full-duplex

NOTE

As provided in Table 5-2, when the opposite interface works in 10M full-duplex or 100M full-duplex mode, auto-negotiation cannot match the working modes between the local interface and the opposite interface; as a result, packets may still be lost. Therefore, when the opposite interface works in 10M full-duplex or 100M fullduplex mode, you need to set the local interface to work in 10 full-duplex or 100M full-duplex mode manually.

When both the local GE interface and the opposite GE interface work in auto-negotiation mode, they can auto-negotiate flow control.

Auto-Negotiation Function of GE Optical Interfaces When GE optical interfaces work in auto-negotiation mode, the auto-negotiation result is the 1000M full-duplex mode only. The auto-negotiation mode is generally set to cooperate with the auto-negotiation flow control function.

5-4


Issue 03 (2010-05-30)



5.1.3 Flow Control When the data processing/transferring capability of an interface fails to handle the flow received by the interface, congestion occurs on the transmission line. To reduce the number of packets to be discarded due to buffer overflowing, appropriate flow control measures must be taken. The half-duplex Ethernet applies the back-pressure mechanism to control the flow. The fullduplex Ethernet applies PAUSE frames to control the flow. Currently, as the half-duplex Ethernet is not widely applied, the flow control function is implemented mainly for the fullduplex Ethernet. Flow control of the full-duplex Ethernet is classified into two types, namely, auto-negotiation flow control and non-auto-negotiation flow control.

Auto-Negotiation Flow Control When an Ethernet interface works in auto-negotiation mode, it can implement auto-negotiation flow control. Auto-negotiation flow control can be implemented in the following modes: l

Asymmetric PAUSE toward the link partner In case of congestion, an interface in this flow control mode can send PAUSE frames but cannot process received PAUSE frames.

l

Symmetric PAUSE An interface in this flow control mode can send and process PAUSE frames.

l

Both asymmetric and symmetric PAUSE An interface in this flow control mode has the following three capabilities:

l

–

Sends and processes PAUSE frames.

–

Sends PAUSE frames but does not process received PAUSE frames.

–

Processes received PAUSE frames but does not send PAUSE frames.

Disabled An interface in this flow control mode does not send or process PAUSE frames. NOTE

The OptiX RTN 605 supports only two auto-negotiation flow control modes, namely, "disabled" and "enable symmetric flow control".

Non-Auto-Negotiation Flow Control When an Ethernet interface works in a fixed working mode, it can implement non-autonegotiation flow control. Non-auto-negotiation flow control can be implemented in the following modes: l

Send only In case of congestion, an interface in this flow control mode can send PAUSE frames but cannot process received PAUSE frames.

l

Receive only In case of congestion, an interface in this flow control mode can process received PAUSE frames but cannot send PAUSE frames.

l

Issue 03 (2010-05-30)

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

5-5



The interface can transmit PAUSE frames and can also process received PAUSE frames. l

Disabled An interface in this flow control mode does not send or process PAUSE frames. NOTE

The OptiX RTN 605 supports only two non-auto-negotiation flow control modes, namely, "disabled" mode and "enable symmetric flow control".

5.1.4 VLAN According to specific rules, an actual network topology can be divided into several logical subnetworks, which are referred to as VLANs. Packets can be broadcast only in the VLAN domain, that is, a VLAN corresponds to a broadcast domain.

VLAN Frame Format To implement the VLAN function, IEEE 802.1q defines the Ethernet frame format that contains the VLAN information, namely, the tagged frame format. The tagged frame format is also called the 802.1q frame format. Compared to a common Ethernet frame, a tagged frame has a 4-byte 802.1q header. See Figure 5-1. Figure 5-1 Tagged Frame Format Destination address

Source address

4 bytes 802.1q header

Length/Type

Data

FCS (CRC-32)

TCI TPID 16 bits

PCP 3 bits

CFI

VID

1 bit

12 bits

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

TPID TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value of TPID is always 0x8100. If network equipment cannot identify tagged frames, the network equipment discards the received tagged frames directly.

l

PCP PCP identifies the priority of an Ethernet frame. This field can be used to provide certain QoS requirements.

l

CFI CFI is a 1-byte field, and it is used on certain physical ring networks. This field is not processed on the Ethernet.

l

VID VID is a 12-byte field, and it indicates the VLAN to which a frame belongs.

5-6


Issue 03 (2010-05-30)



TAG Attribute TAG attributes are used to control the mode for an Ethernet interface to process tagged and untagged frames. TAG attributes may be Tag Aware, Access, and Hybrid. Table 5-3 provides the modes for Ethernet interfaces to process frames with different TAG attributes. Table 5-3 Frame processing modes of Ethernet interfaces Direction

Ingress

Egress

Type of Data Frame

Processing Mode Tag Aware

Access

Hybrid

Tagged frame

Receives tagged frames.

Discards tagged frames.

Receives tagged frames.

Untagged frame

Discards untagged frames.

Adds the port VIDs (PVIDs) to untagged frames and then receives the frames.

Adds the port VIDs (PVIDs) to untagged frames and then receives the frames.

Tagged frame

Transmits tagged frames.

Strips VIDs and then transmits the tagged frames.

Strips PVIDs and then transmits the tagged frames (if the VIDs are the same as the PVIDs). Directly transmits tagged frames (if the VIDs are not the same as the PVIDs).

NOTE

No untagged frames exit from an egress interface.

5.1.5 QinQ QinQ is a technology that identifies different packet services by adding two layers of VLAN tags to the packets. QinQ adds the second layer of VLAN tag to extend the range of VLAN IDs.

QinQ Frame Format The QinQ technology defines three Ethernet frame formats: Ethernet frame format with only a C-TAG, Ethernet frame format with a C-TAG and an S-TAG, and Ethernet frame format with only an S-TAG. l

Issue 03 (2010-05-30)

Ethernet frame format with only a C-TAG Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-7



An Ethernet frame with only a C-TAG has the same format as tagged frame defined in IEEE 802.1q. Hence, a tagged frame defined in IEEE 802.1q is an Ethernet frame that contains a C-VLAN tag. l

Ethernet frame format with a C-TAG and an S-TAG In the case of an Ethernet frame that contains a C-TAG and an S-TAG, the S-TAG is added before the C-TAG. See Figure 5-2. The differences between the S-TAG and the C-TAG are as follows: –

The TPIDs are different. As defined in IEEE 802.1ad, the value of the TPID in the S-TAG is 0x88a8, whereas the value of the TPID in the C-TAG is 0x8100. NOTE

The default value of the 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) substitutes the canonical format indicator (CFI). The DEI works with the PCP to indicate the priority of the S-TAG. NOTE

The OptiX RTN 605 cannot process the DEI.

Figure 5-2 Ethernet frame format with a C-TAG and an S-TAG 4 bytes Destination address

Source address

S-TAG

C-TAG

Length/Type

Data

FCS (CRC-32)

TCI TPID

PCP

16 bits

l

3 bits

DEI

VID

1 bit

12 bits

Ethernet frame format with only an S-TAG Figure 5-2 shows an Ethernet frame with only an S-TAG and without a C-TAG. Figure 5-3 Ethernet frame format with only an S-TAG 4 bytes Destination address

Source address

S-TAG

C-TAG

Length/Type

Data

FCS (CRC-32)

TCI TPID 16 bits

5-8

PCP 3 bits

DEI

VID

1 bit

12 bits


Issue 03 (2010-05-30)



Network Attributes According to modes of processing C-TAGs and S-TAGs, Ethernet interfaces are classified into UNI interfaces, C-Aware interfaces, and S-Aware interfaces. l

UNI interface A UNI interface verifies and processes the outer tag of an Ethernet frame according to its own TAG attributes. A UNI interface cannot be configured for QinQ service transmission.

l

C-Aware interface A C-Aware interface considers that received frames do not carry any S-TAGs. A C-Aware interface can be configured for QinQ service transmission. NOTE

l

l

Both C-tagged frames and untagged frames can enter and exit a C-Aware interface.

l

When processing S-tagged frames, a C-Aware interface considers S-TAGs as C-TAGs.

l

When processing Ethernet frames with S-TAGs and C-TAGs, a C-Aware interface considers S-TAGs as C-TAGs and does not identify C-TAGs at the inner layer.

S-Aware interface An S-aware interface is in an equivalent position to a UNI interface on a network. An Saware interface considers that its accessed packets carry S-TAGs. An S-Aware interface can be configured for QinQ service transmission. NOTE

l

Both S-TAG frames and frames that carry S-TAGs and C-TAGs can enter and exit an S-aware interface.

l

When processing C-tagged frames, an S-Aware interface considers C-TAGs as S-TAGs.

l

An S-Aware interface discards untagged frames.

l

When processing frames with S-TAGs and C-TAGs, an S-Aware interface identifies only S-TAGs at the outer layer but does not identify C-TAGs at the inner layer.

5.1.6 Bridge A bridge refers to a functional unit that is used to connect two LANs or multiple LANs.

Bridge Type A bridge supported by equipment is available in two types: 802.1d bridge and 802.1q bridge. As shown in Figure 5-4, the services on different 802.1d bridges are isolated, but the services of different VLANs on one bridge are not isolated. The services on different 802.1q bridges are isolated and the services of different VLANs on one bridge are also isolated.

Issue 03 (2010-05-30)


5-9



Figure 5-4 802.1d bridge and 802.1q bridge LP3

LP1 VLAN1 VLAN2 VLAN3 ...

LP2 LP3

LP4 LP5 LP6 LP7 LP8

LP1 LP2 LP3

802.1d bridge

LP3

VLAN1

LP4 LP5 LP6

VLAN2

LP7

VLAN3

LP8

802.1q bridge LP: Logic Port

Table 5-4 List of bridges Item

802.1d Bridge

802.1q Bridge

Bridge switch mode

SVL/Ingress filter disable

IVL/Ingress filter enable

VLAN filter table

Not configured

Required

Ingress filter

Disabled: Does not check the VLAN tag.

Enabled: Checks the VLAN tag. If the VLAN ID is not the VLAN ID of the port specified in the VLAN filter table, the packet is discarded.

Bridge learning mode

SVLa

IVLb

Packet forwarding mode

Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address of a packet.

Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address and VLAN ID of a packet.

Range of broadcasting

Forwards the broadcast packet to all the ports on a bridge.

Forwards the broadcast packet to the ports that are specified in the VLAN filter table.

Mount port attribute

UNI

UNI

NOTE

5-10

l

a: When using the shared VLAN learning (SVL) mode, a bridge creates an entry based on the source MAC address and the source port of a packet. This entry is valid to all VLANs.

l

b: When using the independent VLAN learning (IVL) mode, a bridge creates an entry based on the source MAC address, VLAN ID, and source port of a packet. This entry is only valid to this VLAN.


Issue 03 (2010-05-30)



Logical Port The OptiX RTN 605 considers all the ports mounted to a bridge are logical ports, each of which can exist in one or more sub-switching domains. A logical port can be a PORT or an IFUP1 port.

5.1.7 Hub/Spoke In the case of a convergence service, the mutual access between the non-central stations and central stations is required but the access between non-central stations is not required. In this case, specify a mounted port as a Hub port or a Spoke port. l

l

Hub Port –

Hub ports can mutually access each other.

–

Hub ports and Spoke ports can mutually access each other.

Spoke Port –

Spoke ports cannot mutually access each other.

–

Spoke ports and Hub ports can mutually access each other.

NOTE

A mounted port is a Hub port by default. During configuration, you can configure the mounted port of a central station to a Hub port, and configure the mounted port of a non-central station to a Spoke port. In this manner, a central station can communicate with a non-central station, but non-central stations cannot communicate with each other.

5.1.8 Types of Ethernet Services The OptiX RTN 605 supports QinQ-based EVPL services, IEEE 802.1d bridge-based EPLAN services, and IEEE 802.1q bridge-based EVPLAN services.

QinQ-Based EVPL Services Table 5-5 describes the QinQ-based EVPL service model. Table 5-5 QinQ-based EVPL service model Network Attribute

Flow Type

Description

C-Aware (source)

PORT (source)

S-Aware (sink)

PORT+S-VLAN (sink)

The source interface adds an S-TAG to all the received Ethernet frames and then transmits the Ethernet frames to the sink interface.

PORT+C-VLAN (source) PORT+S-VLAN (sink)

Issue 03 (2010-05-30)

The source interface adds an S-TAG to all the received Ethernet frames that carry the specific C-TAG, and then transmits the Ethernet frames to the sink interface.


5-11



IEEE 802.1d Bridge-Based EPLAN Services and IEEE 802.1q Bridge-Based EVPLAN Services Table 5-6 describes the models of IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services are described as follows. Table 5-6 Models of IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services Item

IEEE 802.1d Bridge-Based EPLAN Service

IEEE 802.1q Bridge-Based EVPLAN Service

Network attribute

UNI

UNI

Flow type

PORT

PORT+VLAN

Bridge switch mode




SVL

IVL

VLAN filtering table

Not configured

Must be configured

Packet forwarding method

Obtains the packet forwarding port by querying the MAC address table according to the destination MAC address of the packet.

Obtains the packet forwarding port by querying the MAC address table according to the destination MAC address and VLAN ID of the packet.

Broadcast domain

Entire bridge

Packet forwarding port that is specified in the VLAN filtering table

Sub switching domain

The bridge is not divided into sub switching domains.

The bridge is divided into sub switching domains according to VLANs.

5.1.9 Managing a MAC Address Table The entries in a MAC address table indicate the corresponding relationship between MAC addresses and ports. A MAC address table contains the following entries: dynamic entry, static entry, and blacklist entry. l

Dynamic entry A dynamic entry is obtained by learning of a bridge through the SVL/IVL mode. The dynamic entry ages, and is lost after the Ethernet switching board is reset.

l

Static entry A static entry is manually added by a network administrator to the MAC address table by using the NMS. The static entry does not age, and is not lost after the Ethernet switching board is reset. Generally, the static entry is configured when a port corresponds to a device with its MAC address known and this device transmits large traffic for a long time.

l

5-12

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

Issue 03 (2010-05-30)



A blacklist entry, that is, the MAC disabled entry, is used to discard the data frame that contains the specified MAC address (source MAC address or destination MAC address). A blacklist entry is also called a blackhole entry. The blacklist entry is configured by the network administrator. The blacklist entry does not age, and is not lost after the Ethernet processing board is reset. NOTE

If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time.

5.1.10 Protection for Ethernet Services The OptiX RTN 605 supports two protection modes for Ethernet services, namely, link aggregation (LAG) and rapid spanning tree protocol (RSTP).

LAG Link aggregation allows one or more links that are attached to the same equipment to be aggregated together to form a LAG. In this manner, a MAC client can consider a LAG as a link. As shown in Figure 5-5, a LAG provides the following functions: l

Increased bandwidth A LAG provides users with a cost-effective method for increasing the link bandwidth. Users obtain data links with higher bandwidths by combining multiple physical links into one logical link without upgrading the existing equipment. The bandwidth of the logical link is equal to the sum of the bandwidths of the physical links. The aggregation module distributes the traffic to different links by using the load sharing algorithm, thus providing the load sharing function for links.

l

Increased availability The links in a LAG dynamically back up each other. When a link fails, the other links in the LAG quickly take over. The process in which link aggregation starts the backup link is associated only with the links in the same LAG, and the links not in the LAG are not involved.

Figure 5-5 Link aggregation group

Link 1 Link 2 Ethernet packet

Link 3

Ethernet packet

LAG

STP/RSTP The STP/RSTP meets the following requirements: Issue 03 (2010-05-30)


5-13


5 Configuring Ethernet Services l

Configures any activated topology of any bridge to a single spanning tree. Releases the redundant data loop if there is any between two stations in the network topology.

l

Reconfigures the spanning tree topology in the case of a bridge fault or an interrupted route, thus providing a certain protection, and prevents temporary data loops by automatically containing the bridges and ports of the bridges that are newly added into the LAN.

l

Stabilizes the activated topology in a rapid manner.

l

The finally activated topology can be predicted and repeated. In addition, the topology can be selected by managing the parameters of certain algorithms.

l

Operations to the end stations are transparent. For example, the end stations are unaware of their attachment to a single LAN or a bridged LAN.

l

A small part of the available bandwidth of the link is used to create or maintain the spanning tree, and the bandwidth does not increase with the expanding network size.

STP/RSTP on the OptiX RTN 605 provides protection for a user network that has multiple access points. As shown in Figure 5-6, when user equipment accesses the OptiX RTN 605 through two different trails, you can start STP/RSTP for the ports on the OptiX RTN 605 that are connected to the user network. In this manner, the NEs can run the spanning tree algorithm together with the switches that run STP/RSTP, and generate a spanning tree trail. In this case, when an access link becomes faulty and the original spanning tree trail is interrupted, the spanning tree algorithm is run again to generate a new spanning tree trail. In this manner, the user network with multiple access points is protected. Figure 5-6 Networking diagram of the STP/RSTP application

OptiX RTN

LAN Switch A

LAN Switch B

OptiX RTN

LAN Switch A

LAN Switch B

STP/RSTP Pass Blocked Port

5.1.11 QoS QoS refers to the ability of a communication network to ensure the expected service quality under any conditions, in the aspects of bandwidth, delay, delay jitter, and packet loss ratio. QoS helps to ensure that the request and response from the user or the request and response from the application meet the requirements of an expected service class.

Traffic Classification A flow refers to a collection of packets with the same characteristics. In the case of the Ethernet switching unit, a flow refers to a collection of packets that requires the same QoS operations. Traffic classification means, according to certain rules, classifying packets into several types of flows, on which different QoS operations are performed. Traffic classification is a prerequisite and basis for QoS operations. 5-14


Issue 03 (2010-05-30)



The flow type is based on the associated Ethernet service type of the flow. Port flow: the packets from a certain port are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this port as the service source. The Layer 2 switching service can also be classified as a port flow.

CAR The committed access rate (CAR) is a type of traffic policing technology. When the CAR is used, the rate of the traffic after classification is assessed in a certain period (including in the long term and in the short term); the packet whose rate does not exceed the specified value is set to a high priority and the packet whose rate exceeds the specified value is discarded or downgraded. In this manner, the CAR restricts the traffic into the transmission network. The OptiX RTN 605 supports the CAR processing for traffic in the ingress direction after it is classified. The CAR processing operations are as follows: l

When the rate of packets is equal to or lower than the preset committed information rate (CIR), these packets are marked green and pass the policing of the CAR. These packets are always forwarded first in the case of network congestion.

l

When the rate of packets exceeds the preset peak information rate (PIR), these packets whose rate is higher than the PIR are marked red and are directly discarded.

l

When the rate of packets is higher than the CIR but is equal to or lower than the PIR, these packets whose rate exceeds the CIR can pass the restriction of the CAR and is marked yellow, and these packets are discarded first in the case of network congestion.

l

When the rate of packets is equal to or lower than the CIR in a certain period, certain packets can burst and these packets are always forwarded first in the case of network congestion. The maximum traffic of burst packets is determined by the committed burst size (CBS).

l

When the rate of packets is higher than the CIR but is equal to or lower than the PIR, certain packets can burst and these packets are marked yellow. The maximum traffic of burst packets is determined by the maximum burst size (MBS).

Figure 5-7 shows the traffic change after the CAR processing. The packets that are marked red are directly discarded, and the packets that are marked yellow and green pass the policing of the CAR. In addition, the packets that are marked yellow are processed according to the preset value. Figure 5-7 CAR processing

MBS PIR CBS CIR

MBS

PIR CIR

Issue 03 (2010-05-30)

PIR

CAR


CBS CIR

5-15



CoS A class of service (CoS) helps to schedule packets into egress queues with different priorities, so that these packets can be processed according to the priority of each queue. In this manner, packets with different priorities can be processed according to different QoS requirements. This section describes various priority classification methods. For details on the support of the equipment for priority classification methods, see Specifications of QoS. l

VLAN priority If the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets.

l

DSCP If the CoS type of a flow is set to differentiated services code point (DSCP), the packets in this flow are scheduled to specified egress queues according to the DSCPs carried in the IPv6 packets. This CoS type is applicable to IPv6 packets.

Traffic Shaping Traffic shaping can restrict the traffic and burst of a connection on a network, and thus enables the packet to be transmitted at an even rate. The Ethernet switching unit shapes the irregular traffic or the traffic that does not conform to the specified traffic characteristics based on the generic traffic shaping (GTS) technology. In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switching unit processes the packets as follows before they enter the queue: l

When the rate of the packets is equal to or lower than the set CIR, these packets directly enter the egress queue.

l

When the rate of the packets is higher than the set PIR, these packets enter the buffer. When the buffer overflows, the packets are discarded.

l

When the rate of the packets is higher than the CIR but is equal to or lower than the PIR, the packets whose rate is higher than the CIR enter the buffer of the CIR. When the buffer overflows, these packets are marked yellow and enter the egress queue. In this case, these packets are discarded in the case of queue congestion.

l

When the rate of the packets that pass the restriction of the traffic shaping in a certain period is equal to or lower than the CIR, certain burst packets enter the egress queue. The maximum traffic of the burst packets is determined by the CBS.

l

When the rate of the packets that pass the restriction of the traffic shaping in a certain period is higher than the CIR but is equal to or lower than the PIR, certain burst packets enter the buffer of the CIR. The maximum traffic of the burst packets is determined by the MBS.

As is evident from the preceding processing mechanism, the difference of the traffic shaping from the CAR is as follows:

5-16

l

In the processing of the CAR, the packet that does not conform to the traffic characteristics is downgraded in priority or directly discarded.

l

In the processing of the traffic shaping, the packet that does not conform to the traffic characteristics is stored in the buffer. The packet is downgraded in priority or directly discarded only when the buffer overflows.

l

Traffic shaping increases the delay of services, but CAR does not. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)



Figure 5-8 shows the traffic change after traffic shaping. During the traffic shaping process, the yellow part indicates the traffic that is directly transmitted without traveling through the buffer queue, the yellow part indicates the traffic that is transmitted after traveling through the buffer queue, and the red part indicates the traffic that is discarded. Figure 5-8 Traffic shaping

MBS PIR CBS CIR

PIR

PIR

Shaping

CIR

CIR

SP Scheduling Algorithm Figure 5-9 illustrates the SP scheduling algorithm. Figure 5-9 Queues with different priorities Packets to be transmitted through the interface

Classification

Queue

Priority

Queue 8

Highest

Queue 7

High

Queue 6

Low

Packets transmitted out of the interface Out-of-queue grooming

... Queue 1 Lowest

The urgency of packets decreases from left to right.

The SP scheduling algorithm is designed for key service applications. A key service must be processed with the highest priority when congestion occurs so that the response delay can be shortened. For example, a port provides eight egress queues, which are allocated with priorities from 7 to 0 in a descending order. During the SP queue scheduling, packets are transmitted in a descending order of priorities. When a queue with a higher priority is empty, 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-key services (such as email services) are placed into queues with lower priorities. Therefore, the packets of key services can be always transmitted first, and the packets of non-key services are transmitted when the data of key services is not processed. Issue 03 (2010-05-30)


5-17



The disadvantage of the SP scheduling algorithm is as follows: If there are packets in the queues with higher priorities when congestion occurs, the packets in the queues with lower priorities cannot be transmitted all the time.

WRR Scheduling Algorithm Figure 5-10 illustrates the WRR scheduling algorithm. Figure 5-10 WRR scheduling algorithm Packets to be transmitted through the interface

Queue Classification

Packets transmitted out of the interface

Weight

Queue 4

50

Queue 3

30

Queue 2

10

Queue 1

10

Out-of-queue grooming

The urgency of packets decreases from left to right.

The WRR scheduling algorithm divides each port into several egress queues and schedules the packets in these queues in turn. This ensures that each queue obtains a certain service period. For example, a port provides four queues. In a descending order of priorities, the WRR configures the w4, w3, w2, and w1 weights for the four queues. Each weight stands for the proportion of resources that the relevant queue can obtain from the total resources. If this port is a 100 Mbit/ s port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to w4, w3, w2, and w1) by the WRR scheduling algorithm, a minimum of 10 Mbit/s bandwidth is guaranteed for the queue with the lowest priority. This prevents the disadvantage that packets in the queues with lower priorities may fail to obtain services for a long time in the case of the SP queue scheduling. Another advantage of the WRR scheduling is as follows: Although scheduling of multiple queues is performed in the polling manner, time segment allocated to each queue is not fixed. That is, when a queue is empty, the packets in the next queue are scheduled immediately. In this manner, the bandwidth resources can be fully utilized.

Specifications of QoS Table 5-7 Specifications of QoS Item

Specification

Traffic classification

5-18

Maximum number of flows

OptiX RTN 605 1F/ 2F

OptiX RTN 605 1E/ 2E

8

4


Issue 03 (2010-05-30)



Item

Specification

CAR

CoS

Scheduling of queues at a port

OptiX RTN 605 1F/ 2F

OptiX RTN 605 1E/ 2E

Flow type

Port flow

Port flow

Maximum number of CAR strategies

8

4

CIR step

64 kbit/s

64 kbit/s

PIR

Must be equal to the CIR

Must be equal to the CIR

Priority classification method

VLAN priority

VLAN priority

DSCP

DSCP

Number of mapping relationship table

VLAN priority: 1

VLAN priority: 1

DSCP: 1

DSCP: 1

Number of queue scheduling levelsa

4-level queue scheduling

4-level queue scheduling

Queue scheduling methodb

SP

SP

WRR

WRR

Weight allocation of WRR

Fixed weight allocation (which cannot be modified)

Fixed weight allocation (which cannot be modified)

NOTE a: Four queues are available at the port of the Ethernet processing unit. The mapping relationships between

CoS priorities and egress queues are as follows. Under the same condition, if the CoS priority is higher, the priority of the corresponding queue is higher. CoS Priority

Egress Queue

0

Queue 1

1

Queue 2

2

Queue 3

3

Queue 4

b: The queue scheduling methods of all the ports on the Ethernet processing unit must be set to SP or WRR.

Do not set the queue scheduling methods of these ports to SP and WRR at the same time.

5.2 Configuration Procedure The configuration procedure varies according to the type of an Ethernet service. Issue 03 (2010-05-30)


5-19



Procedure for Configuring QinQ-Based EVPL Services NOTE

Only the OptiX RTN 605 1E/2E supports QinQ-based EVPL services.

Table 5-8 Procedure for configuring QinQ-based EVPL services Step

Operation

1

Configuri ng Ethernet interfaces

Description A.14.1 Configuri ng External Ethernet Ports

l

l

A.14.2 Configuri ng the IFUP Port of the Ethernet Board

5-20

You need to set Basic Attributes. Set the parameters as follows: –

In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled.

–

In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation.

Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: –

When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control.

–

When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control.

l

In the case of QinQ-based EVPL services, set Port Attributes in the Network Attributes tab page to C-Aware.

l

Determine whether to set Advanced Attributes according to actual requirements.

Required when internal interfaces need to be used. In the case of QinQ-based EVPL services, set Port Attributes in the Network Attributes tab page to S-Aware.


Issue 03 (2010-05-30)



Step

Operation

2

Configuri ng LAGs

3

4

Description A.9.1 Creating a LAG

Required when FE/GE interfaces are configured in LAGs for protection. Set the parameters as follows: l

Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends.

l

In the case of FE/GE interfaces, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends.

l

Set Main Port and Selected Slave Ports according to the network planning information. It is recommended that you set this parameter to the same value for the main and slave interfaces of the LAGs at both ends.

Creating QinQbased EVPL services

A.15.4 Creating QinQ Private Line Services


Configuri ng the QoS

A.10.1 Creating a Flow

Required when you need to perform CAR or CoS operations. Before performing any CAR or CoS operations, you need to create flows.

l

Set Service Type to EVPL(QinQ).

l

Set Direction to Bidirectional.

l

Set Source Port and Sink Port according to the service planning information.

Set the relevant parameters according to the service planning information. A.10.2 Creating the CAR A.10.3 Creating the CoS

Required if you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CARs or CoSes to the corresponding flows according to the network planning information.

A.10.4 Binding the CAR/ CoS

Issue 03 (2010-05-30)


5-21



Step

5

Operation

Perform a LB test

Description A.10.5 Configuri ng the Queue Schedulin g Mode

In the case of the OptiX RTN 605, the port queue scheduling mode is of board level and is SP by default.

A.11.1 Creating MDs

Required in the case of the two NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows:

A.11.2 Creating MAs

5-22

Required when you need to change the queue scheduling mode. Set the relevant parameters according to the network planning information.

l

Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs.

l

In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.

Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l

Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step.

l

Set Maintenance Association Name to the same value for the two NEs.

l

It is recommended that you set CCM Sending Period(ms) to 1000 ms.


Issue 03 (2010-05-30)



Step

Operation

Description A.11.3 Creating MPs

Testing Ethernet Services by Using the LB Function

Issue 03 (2010-05-30)


Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step.

l

Set Node to the Ethernet interfaces that are involved in the service test.

l

Set MP ID to different values for MEPs in the same maintenance domain.

l

In this example, Ethernet services between two internal NEs on the transport network are tested. Hence, set Direction to Ingress for the MEPs.

l

If the MP ID is used to identify an MEP, set CC Status to Active.

Required. The LB test result should show that no packet loss occurs.


5-23



Procedure for Configuring IEEE 802.1d Bridge-Based EPLAN Services Table 5-9 Procedure for configuring IEEE 802.1d bridge-based EPLAN services Step

Operation

1



l

l



–

In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation.



–


l

You need to set TAG Attributes. In the case of IEEE 802.1d bridge-based EPLAN services, set TAG to Hybrid.

l

To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the service planning information.

5-24


Issue 03 (2010-05-30)



Step

2

3

4

Issue 03 (2010-05-30)

Operation

Configuri ng LAGs

Description A.14.2 Configuri ng the IFUP Port of the Ethernet Board

Required when internal interfaces need to be used.

A.9.1 Creating a LAG

Required when FE/GE interfaces are configured in LAGs for protection. Set the parameters as follows:

In the case of IEEE 802.1d bridge-based EPLAN services, set TAG to Hybrid.

l


l


l


Creating IEEE 802.1d bridgebased EPLAN services

A.15.1 Creating Ethernet LAN Services


Managing the MAC address table

A.16.1 Creating a Static MAC Address Entry

Required if you need to set certain MAC address entries not to age.

A.16.2 Creating a Blacklist Entry of a MAC Address

Required if you need to disable usage of EPLAN services on the host of certain MAC addresses.

l

Set VB Name according to the service planning information.

l

Set Bridge Type to 802.1d.

l

Set Mount Port according to the service planning information.

Set the relevant parameters according to the network planning information.



5-25



Step

Operation

Description A.16.3 Setting the Aging Time of a MAC Address Table Entry

Required if you need to disable the aging function or change the aging time (five minutes by default). Set the relevant parameters according to the network planning information.

5

A.15.2 Modifying the Mounted Port of a Bridge

Required if you need to change a port connected to a VB, enabled status of a port connected to a VB, or Hub/Spoke attribute of a port connected to a VB.

6




Set the relevant parameters according to the network planning information. A.10.2 Creating the CAR A.10.3 Creating the CoS


A.10.4 Binding the CAR/ CoS A.10.5 Configuri ng the Queue Schedulin g Mode

5-26

In the case of the OptiX RTN 605, the port queue scheduling mode is of board level and is SP by default. Required when you need to change the queue scheduling mode. Set the relevant parameters according to the network planning information.


Issue 03 (2010-05-30)



Step

Operation

7

Perform a LB test

Description A.11.1 Creating MDs

A.11.2 Creating MAs

A.11.3 Creating MPs

Issue 03 (2010-05-30)

Required in the case of the two NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l


l




l


l




l


l


l


l



5-27



Step

Operation

Description Testing Ethernet Services by Using the LB Function


Procedure for Configuring IEEE 802.1q Bridge-Based EVPLAN Services Table 5-10 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services Step

Operation

1



l

l



–

In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). IIn the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation.



–


l

You need to set TAG Attributes.

l

To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.

5-28


Issue 03 (2010-05-30)



Step

2

3

4

Issue 03 (2010-05-30)

Operation

Configuri ng LAGs

Description A.14.2 Configuri ng the IFUP Port of the Ethernet Board

Required when internal interfaces need to be used.

A.9.1 Creating a LAG

Required when FE/GE interfaces are configured in LAGs for protection. Set the parameters as follows:

In the case of IEEE 802.1q bridge-based EVPLAN services, set TAG to Hybrid.

l


l


l


Creating IEEE 802.1q bridgebased EPLAN services

A.15.1 Creating Ethernet LAN Services


Managing the MAC address table

A.16.1 Creating a Static MAC Address Entry

Required if you need to set certain MAC address entries not to age.

A.16.2 Creating a Blacklist Entry of a MAC Address

Required if you need to disable usage of EPLAN services on the host of certain MAC addresses.

l

Set VB Name according to the network planning information.

l

Set Bridge Type to 802.1q.

l

Set Mount Port according to the network planning information.




5-29



Step

Operation

Description A.16.3 Setting the Aging Time of a MAC Address Table Entry

Required if you need to disable the aging function or change the aging time (five minutes by default). Set the relevant parameters according to the network planning information.

5

A.15.2 Modifying the Mounted Port of a Bridge

Required if you need to change a port connected to a VB, enabled status of a port connected to a VB, or Hub/Spoke attribute of a port connected to a VB.

6

A.15.3 Creating the VLAN Filtering Table

Required when you need to create the IEEE 802.1q bridge.

7




Set the relevant parameters according to the network planning information. A.10.2 Creating the CAR A.10.3 Creating the CoS


A.10.4 Binding the CAR/ CoS A.10.5 Configuri ng the Queue Schedulin g Mode

5-30

In the case of the OptiX RTN 605, the port queue scheduling mode is of board level and is SP by default. Required when you need to change the queue scheduling mode. Set the relevant parameters according to the network planning information.


Issue 03 (2010-05-30)



Step

Operation

8

Perform a LB test

Description A.11.1 Creating MDs

A.11.2 Creating MAs

A.11.3 Creating MPs

Issue 03 (2010-05-30)

Required in the case of the two NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l


l




l


l




l


l


l


l



5-31



Step

Operation

Description Testing Ethernet Services by Using the LB Function


5.3 Configuration Example (QinQ-Based EVPL Services) This section a QinQ-based EVPL service as an example to describe how to configure Ethernet services according to the service planning information. 5.3.1 Networking Diagram The section describes the networking information about the NEs. 5.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 5.3.3 Configuration Process This section describes the process for the data configuration.

5.3.1 Networking Diagram The section describes the networking information about the NEs. Based on 3.3 Configuration Example (Radio Links), configure Ethernet services on NE4 and NE5 according to the actual requirements. Only one point-to-point Ethernet service from BTS2 to the GE interface on NE2 is transmitted between NE4 and NE5. In this case, the QinQ-based EVPL service is configured on NE4 and NE5 to implement transparent transmission of the pointto-point service. See Figure 5-11. Figure 5-11 Networking diagram (QinQ-based EVPL services) Transparent transmission

BSC

GE

FE BTS2

RTN 605 2F

RTN 605 2F

NE5 RTN 605 2E

NE4

GE

NE2

NE1

FE

RTN 605 2E BTS1

5-32


Issue 03 (2010-05-30)


5 Configuring Ethernet Services NOTE

l

The OptiX RTN 605 1E/2E supports QinQ-based EVPL services.

l

The OptiX RTN 605 1F/2F does not support QinQ-based EVPL services. Therefore, you need to configure the QinQ-based EVPL service only on NE4 and NE5. For details on how to configure Ethernet services on NE1 and NE2, see 5.4 Configuration Example (IEEE 802.1d Bridge-Based EPLAN Services) and 5.5 Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) .

Table 5-11 Connections of Ethernet links (NE4) Link

Port

Description

Between NE4 and NE5

IFUP1

Configure this port to transmit Ethernet services from radio links.

Between NE4 and NE2

5-EM4T-PORT3

Configure this port to transmit backhaul services from a base station.

Table 5-12 Connections of Ethernet links (NE5) Link

Port

Description

Between NE5 and BTS2

5-EM4T-PORT1

Configure this port to access services from BTS2.

Between NE5 and NE4

IFUP1

Configure this port to transmit Ethernet services from radio links.


Information About Ethernet External Interfaces Table 5-13 and Table 5-14 provide the information about Ethernet external interfaces, which is planned according to fiber/cable connections and types of Ethernet services. Table 5-13 Information about Ethernet interfaces (NE4) Parameter

Port 5-EM4T-PORT3

Issue 03 (2010-05-30)

Port enabled

Enabled

Port working mode

Auto-negotiation


5-33



Parameter

Port 5-EM4T-PORT3

Maximum frame length

1522

Flow control

Disabled

Network attribute

C-Aware

Table 5-14 Information about Ethernet interfaces (NE5) Parameter

Port 5-EM4T-PORT1

Port enabled

Enabled

Port working mode

Auto-negotiation


1522

Flow control

Disabled

Network attribute

C-Aware

NOTE

l

In this example, the FE interfaces on all the BTSes work in auto-negotiation mode. Therefore, Ethernet interfaces on all the NEs that access services from BTSes must also work in auto-negotiation mode. If the peer Ethernet interfaces work in a different mode, the local Ethernet interfaces must be planned to work in the same mode as the peer Ethernet interfaces. Plan the Ethernet interfaces within a network to work in autonegotiation mode.

l

In this example, the maximum frame length is planned to be 1522.

l

In the case of the EM4T board, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends.

Information About Ethernet Internal Interfaces An Ethernet internal port is an Ethernet interface connected to the IF unit. Table 5-15 and Table 5-16 provide the information about the Ethernet internal interfaces, which is planned according to the service type. Table 5-15 Information about Ethernet internal interfaces (NE4) Parameter

Port 5-EM4T-IFUP1

Network attribute

5-34

S-Aware


Issue 03 (2010-05-30)



Table 5-16 Information about Ethernet internal interfaces (NE5) Parameter

Port 5-EM4T-IFUP1

Network attribute

S-Aware

QinQ-Based EVPL Services Table 5-17 to Table 5-18 provide the planning information of the QinQ-based EVPL services. Table 5-17 Information about the QinQ-based EVPL service (NE4) Parameter

Value

Board

5-EM4T

Service type

EVPL (QinQ)

Service direction

Bidirectional

Operation Type

Adding S-TAGs

Source port

PORT3

Source C-VLAN

-

Source S-VLAN

-

Sink port

IFUP1

Sink C-VLAN

-

Sink S-VLAN

100

C-VLAN Priority

AUTO

S-VLAN Priority

AUTO

Table 5-18 Information about the QinQ-based EVPL service (NE5)

Issue 03 (2010-05-30)

Parameter

Value

Board

5-EM4T

Service type

EVPL (QinQ)

Service direction

Bidirectional

Operation Type

Adding S-TAGs

Source port

PORT1

Source C-VLAN

-


5-35



Parameter

Value

Source S-VLAN

-

Sink port

IFUP1

Sink C-VLAN

-

Sink S-VLAN

100

C-VLAN Priority

AUTO

S-VLAN Priority

AUTO

QoS (Flow) Before configuring QoS, you need to create the corresponding flows. Table 5-19 Flow (NE4) Parameter

Value

Flow type

PORT flow

Port

5-EM4T-PORT3

S-VLAN ID

100

Bound CAR

-

Bound CoS

1

Table 5-20 Flow (NE5)

5-36

Parameter

Value

Flow type

PORT flow

Port

5-EM4T-PORT1

S-VLAN ID

100

Bound CAR

1

Bound CoS

1


Issue 03 (2010-05-30)



QoS (CAR) Table 5-21 CAR (services accessed from BTS2 to NE5) Parameter

Value

CAR ID

1

Enabled/Disabled

Enabled

Committed information rate (kbit/s)

10240

Committed burst size (kbyte)

0

PIR (kbit/s)

10240

Maximum burst size (kbyte)

0

NOTE

In the case of the OptiX RTN 605, the PIR must be equal to the CIR.

QoS (CoS) During service planning, it is recommended that you allocate corresponding VLAN priorities to the BTS services according to service types. Then, the transmission network performs CoS operations according to the allocated VLAN priorities. Table 5-22 and Table 5-23 provide the planning information of LAGs. Table 5-22 VLAN priorities corresponding to different service types (BTS)

Issue 03 (2010-05-30)

Service type

Service Priority

VLAN Priority

HSDPA data services (HSPA interactive and HSPA background services)

Lowest

User priority 0 in the VLAN tag

R99 non-real-time services (R99 interactive and R99 background services)

Lower


OM and HSDPA real-time services (OM streaming and HSPA streaming services)

Higher


Real-time voice service and signaling service (R99 conversational and R99 streaming services)

Highest



5-37



Table 5-23 CoS parameters (NE4 and NE5) Parameter

Value

CoS ID

1

CoS type

Classifying CoS priorities based on VLAN priorities

CoS priority corresponding to VLAN priority 0

0


0


1


2


0


3


0


0

QoS (Queue Scheduling) Table 5-22 provides the information about queue scheduling. Table 5-24 QoS (queue scheduling) Parameter

Value

Queue scheduling mode

SP


Procedure Step 1 See A.14.1 Configuring External Ethernet Ports and configure Ethernet external interfaces. The values for the relevant parameters of NE4 are provided as follows. 5-38


Issue 03 (2010-05-30)



Parameter

Value 5-EM4T-PORT3

Enabled/Disabled

Enabled

Working Mode

Auto-Negotiation

Maximum Frame Length

1522

Non-Autonegotiation Flow Control Mode

Disabled

Autonegotiation Flow Control Mode

Disabled

Port Attributes

C-Aware


Value 5-EM4T-PORT1

Enabled/Disabled

Enabled

Working Mode

Auto-Negotiation


1522


Disabled


Disabled

Port Attributes

C-Aware

Step 2 See A.14.2 Configuring the IFUP Port of the Ethernet Board and configure the IFUP interface. The values for the relevant parameters of NE4 are provided as follows. Parameter

Value 5-EM4T-IFUP1

Port Attributes

S-Aware


Value 5-EM4T-IFUP1

Port Attributes Issue 03 (2010-05-30)

S-Aware


5-39



Step 3 See A.15.4 Creating QinQ Private Line Services and create QinQ-based EVPL services. The values for the relevant parameters of NE4 are provided as follows. Parameter

Value

Board

5-EM4T

Service Type

EVPL(QinQ)

Direction

Bidirectional

Source Port

PORT3

Operation Type

Add S-VLAN

Sink Port

IFUP

Sink S-VLAN

100

C-VLAN Priority

AUTO

S-VLAN Priority

AUTO


Value

Board

5-EM4T

Service Type

EVPL(QinQ)

Direction

Bidirectional

Source Port

PORT1

Operation Type

Add S-VLAN

Sink Port

IFUP

Sink S-VLAN

100

C-VLAN Priority

AUTO

S-VLAN Priority

AUTO

Step 4 See A.10.1 Creating a Flow and create flows. The values for the relevant parameters of NE4 are provided as follows. Parameter

Value 5-EM4T

5-40

Flow Type

Port Flow

Port

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

Issue 03 (2010-05-30)




Value 5-EM4T

Flow Type

Port Flow

Port

PORT1

Step 5 See A.10.2 Creating the CAR and configure the CAR. The values for the relevant parameters of NE5 are provided as follows. Parameter

Value 5-EM4T

CAR ID

1

Enabled/Disabled

Enabled

Committed Information Rate (kbit/s)

10240

Committed Burst Size (kbyte)

0

Peak Information Rate (kbit/s)

10240

Maximum Burst Size (kbyte)

0

Step 6 See A.10.3 Creating the CoS and configure the CoS. The values for the relevant parameters of NE4 and NE5 are provided as follows. Parameter

Value 5-EM4T

Issue 03 (2010-05-30)

CoS ID

1

CoS Type

VLAN Priority

User Priority 0 in the VLAN Tag

0


0


1


2


0


3


5-41



Parameter

Value 5-EM4T


0


0

Step 7 See A.10.4 Binding the CAR/CoS and configure the bound CAR/CoS. The values for the relevant parameters of NE4 are provided as follows. Parameter

Value 5-EM4T

Flow Type

Port Flow

Port

PORT3

Bound CAR

-

Bound CoS

1


Value 5-EM4T

Flow Type

Port Flow

Port

PORT1

Bound CAR

1

Bound CoS

1

Step 8 See A.10.5 Configuring the Queue Scheduling Mode and configure the queue scheduling mode. The values for the relevant parameters are provided as follows. Parameter

Value

Queue Scheduling Mode

NE4

NE5

5-EM4T

5-EM4T

SP

SP

Step 9 See A.11.1 Creating MDs and create the maintenance domain on NE4 and NE5. 5-42


Issue 03 (2010-05-30)



The values for the relevant parameters are provided as follows. Parameter

Value NE4

NE5

Maintenance Domain Name

EdgeNE

EdgeNE

Maintenance Level

4

4

Step 10 See A.11.2 Creating MAs and create the maintenance association on NE4 and NE5. The values for the relevant parameters are provided as follows Parameter

Value NE4

NE5


EdgeNE

EdgeNE

Maintenance Association Name

BTS2_Qline

BTS2_Qline

Step 11 See A.11.3 Creating MPs and create the maintenance points on NE4 and NE5. l

l

Issue 03 (2010-05-30)


Value


EdgeNE


BTS2_Qline

Node

5-EM4T-3

VLAN ID

100

MP ID

00-00-0004

Direction

Ingress

CC Status

Active

CCM Sending Period(ms)

1000


Value


EdgeNE


BTS2_Qline

Node

5-EM4T-1 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-43



Parameter

Value

VLAN ID

100

MP ID

00-00-0005

Direction

Ingress

CC Status

Activate


1000

Step 12 See A.11.5 Performing an LB Check and perform LB tests. Perform the LB test by considering the MEP whose MP ID is 00-00-0005 as the source MEP and the MEP whose MP ID is 00-00-0004 as the sink MEP. The LB tests should show that no packet loss occurs. ----End

5.4 Configuration Example (IEEE 802.1d Bridge-Based EPLAN Services) This section considers an IEEE 802.1d bridge-based EPLAN service as an example to describe how to configure Ethernet services according to the service planning information. 5.4.1 Networking Diagram This section describes the networking information about the NEs. 5.4.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 5.4.3 Configuration Process This section describes the process for the data configuration.

5.4.1 Networking Diagram This section describes the networking information about the NEs. Based on 3.3 Configuration Example (Radio Links), configure Ethernet services according to the actual requirements. The VLANs used by services on the BTSes on the network are unknown. Therefore, the IEEE 802.1d bridge is configured on NE1 and NE2 to implement service transmission from BTSes to the BSC.

5-44


Issue 03 (2010-05-30)



Figure 5-12 Networking diagram (IEEE 802.1d bridge-based EPLAN services) 802.1d bridge

802.1d bridge BSC

GE

FE BTS2 10Mbit/s

NE5 RTN 605 2E

NE4 RTN 605 2E

GE

NE2

FE

NE1 RTN 605 2F

RTN 605 2F BTS1 15Mbit/s

NOTE

In this example, it is assumed that Ethernet services described in 5.3 Configuration Example (QinQBased EVPL Services) are already configured on NE4 and NE5 and services on BTS2 can be transparently transmitted to the GE interface on NE2. In this case, you need to configure IEEE 802.1d bridge-based EPLAN services on NE1 and NE2 only.

The connections of Ethernet links shown in Figure 5-12 are described as follows. Table 5-25 Connections of Ethernet links (NE1) Link

Port

Description

Between NE1 and the BSC

5-EMS4-PORT4


Between NE3 and NE2

IFUP1

Configure this port to transmit Ethernet services on the radio link.

Table 5-26 Connections of Ethernet links (NE2)

Issue 03 (2010-05-30)

Link

Port

Description

Between NE2 and NE4

5-EMS4-PORT4

Configure this port to transmit backhaul services accessed from BTS2 to NE4.


5-EMS4-PORT1


Between NE2 and NE1

IFUP1

Configure this port to transmit Ethernet services on the radio link.


5-45




Information About Ethernet External Interfaces The following tables provide the information about the Ethernet external interfaces that transmit the IEEE 802.1d bridge-based EPLAN service. Table 5-27 Information about Ethernet external interfaces (NE1) Parameter

Port 5-EMS4-PORT4

Port enabled

Enabled

Port working mode

Auto-negotiation


1522

Flow control

Disabled

Tag attribute

Hybrid

Enabling broadcast packet suppression

Disabled

Loopback check

Disabled

Table 5-28 Information about Ethernet external interfaces (NE2) Parameter

Port 5-EMS4-PORT1

5-EMS4-PORT4

Port enabled

Enabled

Enabled

Port working mode

Auto-negotiation

Auto-negotiation


1522

1522

Flow control

Disabled

Disabled

Tag attribute

Hybrid

Hybrid

Enabling broadcast packet suppression

Disabled

Disabled

Loopback check

Disabled

Disabled

Information About Ethernet Internal Interfaces The following tables provide the information about the Ethernet internal interfaces that transmit the IEEE 802.1d bridge-based EPLAN service. 5-46


Issue 03 (2010-05-30)




Port 5-EMS4-IFUP1

Tag attribute

Hybrid


Port 5-EMS4-IFUP1

Tag attribute

Hybrid

IEEE 802.1d Bridge-Based EPLAN Services The following tables provide the planning information of the IEEE 802.1d bridge-based EPLAN service. Table 5-31 Information about the IEEE 802.1d bridge-based EPLAN service (NE1) Parameter

Value

Board

5-EMS4

VB name

NE1_VB1

Bridge type

802.1d

Bridge switch mode



SVL

Ingress filter

Disabled

MAC address self-learning

Enabled

Service mount port

PORT4 (Hub port) IFUP1 (Hub port)

Table 5-32 Information about the IEEE 802.1d bridge-based EPLAN service (NE2)

Issue 03 (2010-05-30)

Parameter

Value

Board

5-EMS4

VB name

NE2_VB1

Bridge type

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

5-47



Parameter

Value

Bridge switch mode



SVL

Ingress filter

Disabled

MAC address self-learning

Enabled

Service mount porta

PORT1 (Spoke port) PORT4 (Spoke port) IFUP1 (Hub port)

NOTE

a:In this example, services on BTS1 and services on BTS2 need to be isolated from each other. Therefore, PORT1 and PORT4 need to be set to Spoke ports.

QoS (Flow) Before configuring QoS, you need to create the corresponding flows. Table 5-33 Flow (NE1) Parameter

Value

Flow type

PORT-based flow

Port

5-EMS4-PORT4

Bound CAR

-

Bound CoS

1

Table 5-34 Flow (NE2)

5-48

Parameter

Value

Flow type

PORT-based flow

PORT-based flow

Port

5-EMS4-PORT1

5-EMS4-PORT4

Bound CAR

1

-

Bound CoS

1

1


Issue 03 (2010-05-30)



QoS (CAR) Table 5-35 CAR (services accessed from BTS1 to NE2) Parameter

Value

CAR ID

1

Enabled/Disabled

Enabled


15360


0

PIR (kbit/s)

15360


0

NOTE


QoS (CoS) During service planning, it is recommended that you allocate corresponding VLAN priorities to the BTS services according to service types. Then, the transmission network performs CoS operations according to the allocated VLAN priorities. In this example, all the base stations are of the same type. Therefore, configure the same CoS operations for Ethernet interfaces on the EMS4 boards on NE1 and NE2 that access or backhaul services from the base stations. Refer to Table 5-36 and Table 5-37. Table 5-36 CoS attributes of the EMS4 boards Parameter

Value

CoS ID

1

CoS type

VLAN priority

Table 5-37 CoS parameters of the EMS4 boards

Issue 03 (2010-05-30)

CoS Parameter

CoS Priority

Service Type


0



0

-


5-49



CoS Parameter

CoS Priority

Service Type


1



2



0

-


3



0

-


0

-

QoS (Queue Scheduling) To schedule queues over an interface so that the Ethernet packets in the queues are forwarded in a specific sequence computed by a scheduling algorithm, you need to configure queue scheduling. In this example, services from base stations are scheduled in descending order of queue priority. That is, services in queues with higher priority are forwarded from the EMS4 board to the IF board first; after all the services in queues with higher priority are transmitted, services in queues of lower priority are transmitted. Table 5-38 Queue scheduling on the EMS4 board Parameter

Value


SP


Procedure Step 1 See A.14.1 Configuring External Ethernet Ports and configure the external interfaces on the logical Ethernet boards. The values for the relevant parameters of NE1 are provided as follows. 5-50


Issue 03 (2010-05-30)



Parameter

Value 5-EMS4-PORT4

Enabled/Disabled

Enabled

Working Mode

Auto-Negotiation


1522


Disabled


Disabled

TAG

Hybrid

Enabling Broadcast Packet Suppression

Disabled

Loop Detection

Disabled


Value 5-EMS4-PORT1

5-EMS4-PORT4

Enabled/Disabled

Enabled

Enabled

Working Mode

Auto-Negotiation

Auto-Negotiation


1522

1522


Disabled

Disabled


Disabled

Disabled

TAG

Hybrid

Hybrid


Disabled

Disabled

Loop Detection

Disabled

Disabled


Value IFUP1

TAG

Issue 03 (2010-05-30)

Hybrid


5-51




Value IFUP1

TAG

Hybrid

Step 3 See A.15.1 Creating Ethernet LAN Services and create the Ethernet LAN services. The values for the relevant parameters of NE1 are provided as follows. Parameter

Value

Board

5-EMS4

VB Name

NE1_VB1

Bridge Type

802.1d

Bridge Switching Mode

SVL/Ingress Filter Disable

Selected forwarding ports

PORT4 IFUP1


Value

Board

5-EMS4

VB Name

NE2_VB1

Bridge Type

802.1d


SVL/Ingress Filter Disable


PORT1 PORT4 IFUP1

Step 4 See A.15.2 Modifying the Mounted Port of a Bridge and change the ports mounted to the bridge. The values for the relevant parameters of NE1 and NE2 are provided as follows. Parameter

Value NE1_VB1

Mount Port 5-52

PORT4

NE2_VB1 IFUP1

PORT1


PORT4

IFUP1 Issue 03 (2010-05-30)



Parameter

Value NE1_VB1

Hub/Spoke

Hub

NE2_VB1 Hub

Spoke

Spoke

Hub


Value 5-EMS4

Flow Type

Port Flow

Port

PORT4


Value 5-EMS4

Flow Type

Port Flow

Port Flow

Port

PORT1

PORT4

Step 6 See A.10.2 Creating the CAR and configure the CAR. The values for the relevant parameters are provided as follows. Parameter

Value NE2 5-EMS4

CAR ID

1

Enabled/Disabled

Enabled


15360


0


15360


0

Step 7 See A.10.3 Creating the CoS and configure the CoS. The values for the relevant parameters of NE1 and NE2 are provided as follows. Issue 03 (2010-05-30)


5-53



Parameter

Value NE1 5-EMS4

CoS ID

1

CoS Type

VLAN Priority

CoS Parameter

CoS Priority


0


0


1


2


0


3


0


0


Value 5-EMS4

Flow Type

Port Flow

Port

PORT4

Bound CAR

-

Bound CoS

1


Value 5-EMS4

Flow Type

5-54

Port Flow


Port Flow

Issue 03 (2010-05-30)



Parameter

Value 5-EMS4

Port

PORT1

PORT4

Bound CAR

1

-

Bound CoS

1

1

Step 9 See A.10.5 Configuring the Queue Scheduling Mode and configure the queue scheduling mode. The values for the relevant parameters are provided as follows. Parameter

Value


NE1

NE2

5-EMS4

5-EMS4

SP

SP

Step 10 See A.11.1 Creating MDs and create the maintenance domain on NE1, NE2, and NE5. The values for the relevant parameters are provided as follows. Parameter

Value NE1

NE2

NE5


EdgeNE

EdgeNE

EdgeNE

Maintenance Level

4

4

4

Step 11 See A.11.2 Creating MAs and create the maintenance association on NE1, NE2, and NE5. The values for the relevant parameters of NE1, NE2, and NE5 are provided as follows. Parameter

Value NE1

NE2

NE5


EdgeNE

EdgeNE

EdgeNE


Dlan

Dlan

Dlan

Step 12 See A.11.3 Creating MPs and create maintenance points on NE1, NE2, and NE5. The values for the relevant parameters of NE1 are provided as follows. Issue 03 (2010-05-30)


5-55



Parameter

Value NE1

NE2

NE5


EdgeNE

EdgeNE

EdgeNE


Dlan

Dlan

Dlan

Node

5-EMS4-PORT4

5-EMS4-PORT1

5-EM4T-PORT1

VLAN ID

-

-

-

MP ID

00-00-0101

00-00-0201

00-00-0501

Direction

Ingress

Ingress

Ingress

CC Status

Activate

Activate

Activate


1000

1000

1000

Step 13 See A.11.5 Performing an LB Check and perform the LB tests. l

Perform the LB test by considering the MEP whose MP ID is 00-00-0101 as the source MEP and the MEP whose MP ID is 00-00-0201 as the sink MEP.

l


The LB tests should show that no packet loss occurs. ----End

5.5 Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) This section considers an IEEE 802.1q bridge-based EVPLAN service as an example to describe how to configure Ethernet services according to the service planning information. 5.5.1 Networking Diagram The section describes the networking information about the NEs. 5.5.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 5.5.3 Configuration Process This section describes the process for the data configuration.

5.5.1 Networking Diagram The section describes the networking information about the NEs. Based on 3.3 Configuration Example (Radio Links), configure Ethernet services according to the actual requirements. On the network, services from different BTSes are isolated from each 5-56


Issue 03 (2010-05-30)



other by the VLAN IDs. In this case, the IEEE 802.1q bridge-based EVPLAN service is configured on the aggregation link between NE2 and NE1 to implement transmission of services from different BTSes. Figure 5-13 Networking diagram (IEEE 802.1q bridge-based EVPLAN services) BSC

GE

FE BTS2

RTN 605 2F

RTN 605 2F

SVLAN 100

NE5 RTN 605 2E

NE4

GE

NE2

NE1

FE

RTN 605 2E BTS1

NOTE

This section describes only how to configure IEEE 802.1q bridge-based EVPLAN services on NE1 and NE2. For details on how to configure IEEE 802.1q bridge-based EVPLAN services on NE4 and NE5, see 5.3 Configuration Example (QinQ-Based EVPL Services).

The connections of Ethernet links shown in Figure 5-13 are described as follows. Table 5-39 Connections of Ethernet links (NE1) Link

Port

Description

Between NE1 and the BSC

5-EMS4-PORT4


Between NE1 and NE2

IFUP1

Configure this port to transmit Ethernet services from a radio link.

Table 5-40 Connections of Ethernet links (NE2)

Issue 03 (2010-05-30)

Link

Port

Description


5-EMS4-PORT1


Between NE2 and NE4

5-EMS4-PORT4

Configure this port to transmit backhaul services accessed from BTS2 to NE4.

Between NE2 and NE1

IFUP1

Configure this port to transmit Ethernet services from a radio link.


5-57




Information About Ethernet External Interfaces Table 5-41 and Table 5-42 provide the information about Ethernet external interfaces, which is planned according to fiber/cable connections and types of Ethernet services. Table 5-41 Information about Ethernet external interfaces (NE1) Parameter

Port 5-EMS4-PORT4

Port enabled

Enabled

Port working mode

Auto-negotiation


1522

Flow control

Disabled

TAG attribute

Tag Aware

Table 5-42 Information about Ethernet external interfaces (NE2) Parameter

Port 5-EMS4-PORT1

5-EMS4-PORT4

Port enabled

Enabled

Enabled

Port working mode

Auto-negotiation

Auto-negotiation


1522

1522

Flow control

Disabled

Disabled

TAG Attribute

Tag Aware

Tag Aware

NOTE

5-58

l

In this example, the FE interfaces on all the BTSes work in auto-negotiation mode. Therefore, Ethernet interfaces on all the NEs that access services from BTSes must work in auto-negotiation mode. If the peer Ethernet interfaces work in a different mode, the local Ethernet interfaces must be planned to work in the same mode as the peer Ethernet interfaces. Plan the Ethernet interfaces within a network to work in autonegotiation mode.

l

In this example, the maximum frame length is planned to be 1522.

l

In the case of the EMS4 board, the flow control function is enabled only when the NE or the peer equipment is inadequate for QoS processing. The planning information of flow control must be the same for the equipment at both ends.


Issue 03 (2010-05-30)



Information About Ethernet Internal Interfaces An Ethernet internal port is an Ethernet interface connected to the IF unit. Table 5-43 and Table 5-44 provide the information about the Ethernet internal interfaces, which is planned according to the service type. Table 5-43 Information about Ethernet internal interfaces (NE1) Parameter

Port 5-EMS4-IFUP1

TAG attribute

Tag Aware


Port 5-EMS4-IFUP1

TAG attribute

Tag Aware

IEEE 802.1q Bridge-Based EVPLAN Services The IEEE 802.1q bridge isolates Ethernet services in different VLANs according to the service types. Table 5-45 and Table 5-46 provide the planning information of the bridge. Table 5-45 Information about the IEEE 802.1q bridge-based EVPLAN service (NE1) Parameter

Value

Board

5-EMS4

VB name

VB1

Bridge type

802.1q

Bridge switch mode


Mounted port

PORT4, IFUP1

VLAN filter table

Issue 03 (2010-05-30)

VLAN Filtering

VLAN filtering table 1


VLAN ID

101

102

Available forwarding ports

PORT4, IFUP1

PORT4, IFUP1


5-59



Table 5-46 Information about the IEEE 802.1q bridge-based EVPLAN service (NE2) Parameter

Value

Board

5-EMS4

VB name

VB1

Bridge type

802.1q

Bridge switch mode


Mounted port

POR1, PORT4, IFUP1

VLAN filter table

VLAN filtering



VLAN ID

101

102

Available forwarding ports

PORT1, IFUP1

PORT4, IFUP1

QoS (CAR) To prevent excessive Ethernet services from being transmitted from BTSes, you need to enable the CAR on the port on NE2 that accesses BTS services. Traffic over the Ethernet interface on NE1 connecting to the BSC needs not be restricted. Table 5-47 describes the CAR parameters. Table 5-47 CAR parameters (services accessed from BTS1 to NE2) Parameter

Value

CAR ID

1

Enabled/Disabled

Enabled


15360


-

PIR (kbit/s)

15360


-

NOTE


QoS (CoS) During service planning, it is recommended that you allocate corresponding VLAN priorities to the BTS services according to service types. Then, the transmission network performs CoS operations according to the allocated VLAN priorities. 5-60


Issue 03 (2010-05-30)



In this example, the BTS services are configured with corresponding VLAN priorities based on the service types. Refer to Table 5-48. Table 5-48 VLAN priorities corresponding to different service types (BTS) Service type

Service Priority

VLAN Priority


Lowest



Lower



Higher



Highest


In this example, all the base stations are of the same type. Therefore, configure the same CoS operations for Ethernet interfaces on the EMS4 boards on NE1 and NE2 that access or backhaul services from the base stations. Table 5-49 provides the CoS information that is planned based on the information provided in Table 5-48. Table 5-49 CoS parameters (NE1 and NE2)

Issue 03 (2010-05-30)

Parameter

Value

CoS ID

1

CoS type

Classifying CoS priorities based on VLAN priorities


0


0


1


2


0


5-61



Parameter

Value


3


0


0

QoS (Flow) You need to create flows and configure the bound CAR and CoS according to the requirements for Ethernet services. Table 5-50 and Table 5-51 provide the planning information of flows. Table 5-50 Flow (NE1) Parameter

Value

Flow type

PORT-based flow

Port

4-EMS4-PORT4

Bound CAR

-

Bound CoS

1

Table 5-51 Flow (NE1) Parameter

Value

Flow type

PORT-based flow

PORT-based flow

Port

4-EMS4-PORT1

4-EMS4-PORT4

Bound CAR

1

-

Bound CoS

1

1

QoS (Queue Scheduling) To schedule queues over an interface so that the Ethernet packets in the queues are forwarded in a specific sequence computed by a scheduling algorithm, you need to configure queue scheduling. In this example, services from base stations are scheduled in descending order of queue priority. That is, services in queues with higher priority are forwarded; after all the services in queues with higher priority are transmitted, services in queues of lower priority are transmitted. 5-62


Issue 03 (2010-05-30)



Table 5-52 Queue scheduling (NE1 and NE2) Parameter

Value


SP


Procedure Step 1 See A.14.1 Configuring External Ethernet Ports and configure Ethernet external interfaces. The values for the relevant parameters of NE1 are provided as follows. Parameter

Value 5-EMS4-PORT1

Enabled/Disabled

Enabled

Working Mode

Auto-negotiation


1522


Disabled


Disabled

TAG

Tag Aware


Issue 03 (2010-05-30)

Value 5-EMS4-PORT1

5-EMS4-PORT4

Enabled/Disabled

Enabled

Enabled

Working Mode

Auto-Negotiation

Auto-Negotiation


1522

1522


Disabled

Disabled


Disabled

Disabled

TAG

Tag Aware

Tag Aware


5-63




Value 5-EMS4-IFUP1

TAG

Tag Aware


Value 5-EMS4-IFUP1

TAG

Tag Aware

Step 3 See A.15.1 Creating Ethernet LAN Services and configure the Ethernet LAN services. The values for the relevant parameters of NE1 are provided as follows. Parameter

Value

Board

5-EMS4

VB Name

VB1

Bridge Type

802.1q


IVL/Ingress Filter Enable

Mount Port

PORT4, IFUP1


Value

Board

5-EMS4

VB Name

VB1

Bridge Type

802.1q


IVL/Ingress Filter Enable

Mount Port

PORT1, PORT4, IFUP1

Step 4 See A.15.2 Modifying the Mounted Port of a Bridge and configure ports mounted to a bridge. The values for the relevant parameters of NE1 are provided as follows. 5-64


Issue 03 (2010-05-30)



Parameter

Value

Mount Port

PORT4

IFUP1

Hub/Spoke

Hub

Hub

The values for the relevant parameters of NE1 and NE2 are provided as follows. Parameter

Value

Mount Port

PORT1

PORT4

IFUP1

Hub/Spoke

Hub

Hub

Hub

Step 5 See A.15.3 Creating the VLAN Filtering Table and create the VLAN filtering table. The values for the relevant parameters of NE1 are provided as follows. Parameter

Value VLAN Filtering Table 1

VLAN Filtering Table 2

VLAN ID(e.g; 1,3-6)

101

102


PORT4, IFUP1

PORT4, IFUP1


Value VLAN Filtering Table 1

VLAN Filtering Table 2

VLAN ID(e.g; 1,3-6)

101

102


PORT4, IFUP1

PORT1, IFUP1


Value 5-EMS4

Issue 03 (2010-05-30)

Flow Type

Port Flow

Port

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

5-65




Value 5-EMS4

Flow Type

Port Flow

Port Flow

Port

PORT1

PORT4

Step 7 See A.10.2 Creating the CAR and configure the CAR. The values for the relevant parameters of NE2 are provided as follows. Parameter

Value 5-EMS4

CAR ID

1

Enabled/Disabled

Enabled


15360


0


15360


0

Step 8 See A.10.3 Creating the CoS and configure the CoS. The values for the relevant parameters of NE1 and NE2 are provided as follows. Parameter

Value 5-EMS4

5-66

CoS ID

1

CoS Type

VLAN Priority


0


0


1


2


0


3


Issue 03 (2010-05-30)



Parameter

Value 5-EMS4


0


0


Value 5-EMS4

Flow Type

Port Flow

Port

PORT4

Bound CAR

-

Bound CoS

1


Value 5-EMS4

Flow Type

Port Flow

Port Flow

Port

PORT1

PORT4

Bound CAR

1

-

Bound CoS

1

1

Step 10 See A.10.5 Configuring the Queue Scheduling Mode and configure the queue scheduling mode. The values for the relevant parameters of NE1 and NE2 are provided as follows, Parameter

Value


NE1

NE2

5-EMS4

5-EMS4

SP

SP

Step 11 See A.11.1 Creating MDs and create the maintenance domain on NE1 and NE2. Issue 03 (2010-05-30)


5-67



The values for the relevant parameters of NE1 and NE2 are provided as follows, Parameter

Value NE1

NE2


EdgeNE

EdgeNE

Maintenance Level

4

4

Step 12 See A.11.2 Creating MAs and create the maintenance association on NE1 and NE2. The values for the relevant parameters of NE1 and NE2 are provided as follows, Parameter

Value NE1

NE2


EdgeNE

EdgeNE


Qlan

Qlan

Step 13 See A.11.3 Creating MPs and create the maintenance points. The values for the relevant parameters of NE1 are provided as follows. Parameter

Value


EdgeNE

EdgeNE


Qlan

Qlan

Node

5-EMS4-PORT4

5-EMS4-PORT4

VLAN ID

101

102

MP ID

00-00-0101

00-00-0102

Direction

Ingress

Ingress

CC Status

Activate

Activate


1000

1000


5-68


Issue 03 (2010-05-30)



Parameter

Value


EdgeNE

EdgeNE


Dlan

Dlan

Node

5-EMS4-PORT4

5-EMS4-PORT1

VLAN ID

101

102

MP ID

00-00-0201

00-00-0202

Direction

Ingress

Ingress

CC Status

Activate

Activate


1000

1000

Step 14 See A.11.5 Performing an LB Check and perform LB tests. l


l


The LB tests should show that no packet loss occurs. ----End

Issue 03 (2010-05-30)


5-69



6

Configuring Clocks

About This Chapter To ensure that the clocks of all the nodes on the transmission network are synchronized, you need to configure the clocks for these nodes according to a unified clock synchronization policy. 6.1 Basic Concepts Before configuring the clock, you need to be familiar with relevant basic concepts. 6.2 Configuration Procedure In the case of the OptiX RTN 605 1E/2E/1F/2F, you need to configure the priority levels of clock sources. 6.3 Configuration Example (Clock) This section considers a chain network as an example to describe how to configure clock sources according to the service planning information.

Issue 03 (2010-05-30)


6-1



6.1 Basic Concepts Before configuring the clock, you need to be familiar with relevant basic concepts. 6.1.1 Clock Source The clock source is used to synchronize parts of an NE, or upstream and downstream NEs, and to 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 Synchronization Policy You need to plan the clock synchronization policy according to the service type.

6.1.1 Clock Source The clock source is used to synchronize parts of an NE, or upstream and downstream NEs, and to 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 605 1E/2E/1F/2F supports extraction of clock sources from the synchronous Ethernet signals. The OptiX RTN 605 supports transparent transmission of the E1 service clock signal.

6.1.2 Clock Synchronization Policy You need to plan the clock synchronization policy according to the service type.

Service Type and Clock Synchronization Policy l

The OptiX RTN 605 transparently transmits the E1 service clock signal. The OptiX RTN 605 need not be synchronous with the E1 service clock.

l

The OptiX RTN 605 1E/1E/1F/2F supports the synchronous Ethernet function. If BTSes need to obtain the timing reference signal from Ethernet services, all the OptiX RTN 605s on the transmission links must be synchronous with the timing reference signal of the RNC.

l

When accessing E1 services and Ethernet services from the OptiX RTN 605s, a BTS prefers the synchronous Ethernet clock.

Precautions of Planning a Clock Synchronization Policy The number of NEs on a long clock chain should not be more than 20. A number smaller than 10 is recommended. If a large number of NEs exist on a long clock chain, add one more clock source for signal compensation in the middle of the chain.

6.2 Configuration Procedure In the case of the OptiX RTN 605 1E/2E/1F/2F, you need to configure the priority levels of clock sources.

6-2


Issue 03 (2010-05-30)



Table 6-1 Procedures for configuring clock sources Step

Operation

Description

1

A.7.1 Configuring Clock Sources of the OptiX RTN 605 1E/2E (in the case of the OptiX RTN 605 1E/2E)

Required if the OptiX RTN 605 1E/2E needs to trace a synchronous Ethernet clock source. Set the parameters as follows:

A.7.2 Configuring the Ethernet Clock Source of the OptiX RTN 605 1F/2F (in the case of the OptiX RTN 605 1F/ 2F)

Required if the OptiX RTN 605 1F/2F needs to trace a synchronous Ethernet clock source. Set the parameters as follows:

2

A.7.3 Querying the Current NE Clock Source

l

Adjust the priority levels of the synchronous Ethernet clock sources according to the service planning information.

l

Configure clock sources according to the service planning information.

l

When this parameter is set to Yes, the OptiX RTN 605 1F/2F traces the clock source that is recovered from the signal flow over an Ethernet PORT.

Optional. On a radio link hop, one NE should trace an internal clock source or the synchronous Ethernet clock and the other NE should trace the radio clock source.

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

6.3.1 Networking Diagram The section describes the networking information about the NEs. Based on 3.3 Configuration Example (Radio Links), configure the clock sources on a network as shown in Figure 6-1, according to the clock synchronization requirements. The clock synchronization requirements are as follows: l

Issue 03 (2010-05-30)

The radio transmission network is directly synchronized with the clock of the BSC through the GE interface on NE1. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

6-3


6 Configuring Clocks l

The radio transmission network provides clock signals to BTS1 and BTS2 through FE interfaces and provides clock signals to BTS3 through E1 interfaces.

Figure 6-1 Networking diagram FE BTS2

GE

NE5 RTN 605 2E

NE4 RTN 605 2E

NE2 E1 BTS3

RTN 605 2F

RTN 605 2F

NE3

NE1

GE

BTS1

RTN 605 1D

NE6

FE

BSC

RTN 605 1D

For board configuration information, see 2.3.2 Board Configuration. NOTE

The OptiX RTN 605 supports transparent transmission of the E1 service clock.

For details about board configurations, see 2.3.2 Board Configuration.


Information about Clock Sources According to the clock synchronization policy, Figure 6-2 shows the information about clock sources. Figure 6-2 Information about clock sources Radio link clock

NE5 RTN 605 2E

Synchronous Ethernet clock

NE4

Radio link clock

Synchronous Ethernet clock

GE

RTN 605 2E

NE2 E1

RTN 605 2F

NE1 RTN 605 2F

NE3 NE6

6-4

BSC

RTN 605 1D

RTN 605 1D


GE

clock

Issue 03 (2010-05-30)


6 Configuring Clocks NOTE

The OptiX RTN 605 supports transparent transmission of the E1 clock. Therefore, you need not configure clock sources for NE3 or NE6.

Clock Synchronization Policy for a Base Station In this example, NE1 to NE4 are synchronized with the BSC by means of the synchronous Ethernet and radio links. In addition, NE1 and NE2 provide the BSC timing reference signal to BTS1 and BTS2 by means of Ethernet interfaces and NE6 transparently transmits the E1 service clock signal to BTS3 by means of E1 interfaces.


Procedure Step 1 See A.7.2 Configuring the Ethernet Clock Source of the OptiX RTN 605 1F/2F and configure the Ethernet clock source on NE1 and NE2. The values for the relevant parameters are provided as follows. Parameter

Use the clock source of the data port

Value NE1

NE2

NE3

NE4

Yes

No

Yes

No

Step 2 See A.7.1 Configuring Clock Sources of the OptiX RTN 605 1E/2E and configure the clock sources of NE4 and NE5. The values for the relevant parameters are provided as follows. Parameter

Clock Source

Value NE4

NE5

Adjust the priority levels of the clock sources as follows:

Adopt the default priority levels of the clock sources:

5-EM4T-3(PORT-3)

8-IF0-1(IF)

8-IF0-1(IF)

5-EM4T-3(PORT-3)

5-EM4T-4(PORT-4)

5-EM4T-4(PORT-4)

Internal clock source

Internal clock source

Step 3 See A.7.3 Querying the Current NE Clock Source and query the current clock source. On a radio link hop, one NE should trace an internal clock source or the synchronous Ethernet clock and the other NE should trace the radio clock source. ----End Issue 03 (2010-05-30)


6-5



7

Configuring Auxiliary Interfaces and Functions

About This Chapter The OptiX RTN 605 provides multiple auxiliary interfaces and functions. These functions are available only after specific data configurations are complete. 7.1 Auxiliary Interfaces and Functions This section describes the auxiliary interfaces and functions supported by the OptiX RTN 605, namely, the orderwire, synchronous data services, asynchronous data services, and external alarms. 7.2 Configuration Example (Orderwire) This section considers the orderwire on a radio network as an example to describe how to configure the orderwire according to service planning information. 7.3 Configuration Example (Synchronous Data Services) This section considers a synchronous data service that transmits the NM messages as an example to describe how to configure synchronous data services according to the service planning information. 7.4 Configuration Example (Asynchronous Data Services) This section considers an asynchronous data service that transmits the NM messages as an example to describe how to configure asynchronous data services according to the service planning information. 7.5 Configuration Example (External Alarms) This section considers environment monitoring and centralized control of equipment alarms through external alarms as examples to describe how to configure external alarms according to the service planning information.

Issue 03 (2010-05-30)


7-1



7.1 Auxiliary Interfaces and Functions This section describes the auxiliary interfaces and functions supported by the OptiX RTN 605, namely, the orderwire, synchronous data services, asynchronous data services, and external alarms.

Orderwire The OptiX RTN 605 supports one orderwire phone so that the operation or maintenance engineers at different workstations can conduct voice communication through microwave overhead bytes. When using the orderwire phone, take the following precautions: l

The orderwire phone numbers of all the NEs on the network must be of the same length. It is recommended that the orderwire telephone number is a 3-digit number and all orderwire telephone numbers on the network are unique to each other.

l

The dialing method of the orderwire phone of each node is dual-tone multifrequency.

l

The call waiting time of each node must be set to the same value. If fewer than 30 nodes exist in the orderwire subnet, it is recommended that you set the call waiting time to 5s. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set the call waiting time to 9s.

l

The equipment supports the orderwire group call function. When one set of the OptiX RTN equipment dials the orderwire group call number "888", the orderwire phones of all the OptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call, the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-tomultipoint group call changes to a point-to-point ordinary orderwire call.

l

When the orderwire signals are transmitted over a radio link, they are always transmitted over one self-defined overhead byte.

l

The OptiX RTN 605 automatically considers the IF interfaces and the synchronous data interface (if no service is configured on the synchronous data interface) as the interfaces for transmitting the orderwire overheads. Therefore, you need not configure the orderwire phone interface manually.

l

The equipment supports transmission of orderwire overhead bytes through the 64 kbit/s synchronous data interfaces or external clock interfaces.

l

The equipment provides the orderwire interface on the IDU. For definitions of the pins on the interfaces, see the OptiX RTN 605 IDU Hardware Description.

Synchronous Data Services Synchronous data services are also called F1 data services. The OptiX RTN 605 supports one synchronous data service. The radio overhead bytes transmitted between two NEs can be used for transmitting one 64 kbit/s synchronous data service. When using synchronous data services, take the following precautions:

7-2

l

Synchronous data services are fully transparently transmitted, and the interface rate is 64 kbit/s .

l

Synchronous data services are clock-sensitive. If the clock is not synchronized, bit errors occur. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


7 Configuring Auxiliary Interfaces and Functions l

The interfaces on the equipment comply with ITU-T G.703.

l

When synchronous data services are transmitted over the protected radio links , the synchronous data services are also protected.

l

The equipment provides synchronous data service interfaces on the IDU. For definitions of the pins on the interfaces, see the OptiX RTN 605 IDU Hardware Description.

Asynchronous Data Services Asynchronous data services are also called transparent data services or broadcast data interface services. The OptiX RTN 605 supports one channel of asynchronous data service. The microwave overhead bytes transmitted between two sites are used for implementing full-duplex communication of the universal asynchronous receiver/transmitter (UART). When using asynchronous data services, take the following precautions: l

Asynchronous data services are fully transparently transmitted. The interface rate and transmission control protocol need not be configured. The interface rate is 19.2 kbit/s.

l

Asynchronous data services are clock-sensitive. If the clock is not synchronized, bit errors occur.

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 communication.

l

When asynchronous data services are transmitted over the protected radio links , the asynchronous data services are also protected.

l

The equipment provides asynchronous data service interfaces on the IDU. For definitions of the pins on the interfaces, see the OptiX RTN 605 IDU Hardware Description. NOTE

The synchronous data interface and the asynchronous data interface share an RJ-45 connector.

External Alarms External alarms are also called Boolean alarms or relay alarms. The OptiX RTN 605 provides the 3-input and 1-output external alarm interfaces. Figure 7-1 shows the interface circuits of the input external alarms. When the external relay is switched off, the interface circuit generates a high-level signal. When the external relay is switched on, the interface circuit generates a low-level signal. The board generates the corresponding alarm based on the level that is generated by the interface circuit. Input external alarms are mainly used for accessing the relay alarms generated by the environmental alarm generator. Figure 7-1 Circuits for external alarm input Circuit for external alarm input Output level

Issue 03 (2010-05-30)

+3.3 V/+5 V Pull-up resistance

External system Relay


7-3



The interface circuits for the output external alarms function the same as the external system shown 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 in the alarm. Otherwise, the NE drives the relay to change the switch to the reverse status that results in the alarm. Output external alarms are mainly used for indicating the alarm status of the equipment that is contained by the centralized alarming devices. The equipment provides the external alarm interfaces on the IDU. For definitions of the pins on the interfaces, see the OptiX RTN 605 IDU Hardware Description.

7.2 Configuration Example (Orderwire) This section considers the orderwire on a radio network as an example to describe how to configure the orderwire according to service planning information. 7.2.1 Networking Diagram The section describes the networking information about the NEs. 7.2.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.2.3 Configuration Process This section describes the process for the data configuration.

7.2.1 Networking Diagram The section describes the networking information about the NEs. In the networking diagram shown in Figure 7-2, each site needs to be configured with the orderwire. All the other radio links are configured with 1+0 non-protection. No SDH transmission lines or radio links are set up between NE2 and NE3. Therefore, you need to connect NE2 and NE3 through synchronous data interfaces to implement orderwire spanning. Figure 7-2 Networking diagram (orderwire) RTN 605 1F

RTN 605 1F

1+0

1+0 F1 NE4

NE3

E1

NE2

RTN 605 1F

NE1 RTN 605 1F

7.2.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7-4


Issue 03 (2010-05-30)



Information About Orderwire Phone Numbers In this example, the number of NEs is very small. Therefore, the orderwire phone numbers are allocated in the format of 100 + NE ID, as shown in Figure 7-3. Figure 7-3 Networking diagram (orderwire) 1+0

1+0 F1 E1

NE4

NE2

NE3

NE1 101 102

103

104

Information About Orderwire Interfaces l

In this example, the service between NE2 and NE3 is spanned through the E1 line. To implement orderwire spanning, the 64 kbit/s synchronous data service interface is used.

l

NE2 to NE4 are located on the orderwire subnet. Therefore, NE2 to NE4 use the default orderwire interfaces (all the IF interfaces, line interfaces, and unconfigured synchronous data interfaces) that are automatically mapped by the equipment.

l

NE1 is not located at the edge of the orderwire subnet. Therefore, configure orderwire interfaces for NE1 according to the situation of NE2 to NE4. If NE1 is located at the edge of the orderwire subnet and if it is connected to an IF interface or a line interface on another orderwire subnet, delete the IF interface or line interface from the orderwire interfaces on the NMS.

l

The information about orderwire interfaces of each NE is provided in Table 7-1.

Table 7-1 Information about orderwire interfaces NE

Order Interface

NE1

8-IFH1-1

NE2

8-IFH1-1 F1

NE3

8-IFH1-1 F1

NE4

8-IFH1-1

NOTE

l

Certain orderwire ports are unnecessary. They do not receive orderwire signaling and thus do not affect the orderwire phone.

l

If the equipment is configured with a service over the synchronous data interface, the orderwire interface is deleted automatically.

Issue 03 (2010-05-30)


7-5



Information About Orderwire Parameters l

Fewer than 30 NEs exist on the orderwire subnet. Therefore, set the call waiting time to 5s.

l

In this example, the SDH optical transmission equipment is not involved on the orderwire subnet. Therefore, set the orderwire overhead byte to E1 (default value).

l

If services are configured on the synchronous data interface, the orderwire interface is automatically deleted on the NMS.


Procedure Step 1 See A.18.1 Configuring the Orderwire and configure the orderwire phone. The values for the relevant parameters are provided as follows. Parameter

Value NE1

NE2

NE3

NE4

Call Waiting Time(s)

5

5

5

5

Phone 1

101

102

103

104

Selected Orderwire Port

8-IFH1-1

8-IFH1-1

8-IFH1-1

8-IFH1-1

F1

F1

----End

7.3 Configuration Example (Synchronous Data Services) This section considers a synchronous data service that transmits the NM messages as an example to describe how to configure synchronous data services according to the service planning information. 7.3.1 Networking Diagram The section describes the networking information about the NEs. 7.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.3.3 Configuration Process This section describes the process for the data configuration.

7.3.1 Networking Diagram The section describes the networking information about the NEs. 7-6


Issue 03 (2010-05-30)



In the networking diagram shown in Figure 7-4, the radio network transmits the NM information of the third-party equipment. The third-party equipment and the NMS use the protocol converter to convert the NM messages transmitted over Ethernet into the NM messages transmitted over 64 kbit/s synchronous data services. Hence, the radio transmission network needs to transparently transmit the corresponding synchronous data only. The networking information of the network is as follows: l

NE1 and NE4 add or drop the 64 kbit/s synchronous data services. NE2 and NE3 pass through the 64 kbit/s synchronous data services.

l

All the other radio links are configured with 1+0 non-protection.

Figure 7-4 Networking diagram (synchronous data services) NE6

3rd party NM

3rd party equipment 1+0

1+0 F1

ETH

ETH

E1 RTN 605 1F NE4

64kbps

RTN 605 1F

RTN 605 1F

RTN 605 1F

NE3

NE2

NE1

64k/ETH Converter

7.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. l

In this example, the TDM service between NE2 and NE3 needs to be spanned through the E1 channel. To implement service spanning between NE2 and NE3, the two synchronous data interfaces between NE2 and NE3 are interconnected with each other.

l

According to the service path, you can obtain the synchronous data service information provided in Table 7-2. Table 7-2 Information about the synchronous data service NE

Data Channel 1

Data Channel 2

NE1

F1

8-IFH-1

NE2

8-IFH-1

F1

NE3

F1

8-IFH-1

NE4

8-IFH-1

F1

NOTE

In the case of radio links configured with 1+1 protection, only the main link is configured with the synchronous data service.

7.3.3 Configuration Process This section describes the process for the data configuration. Issue 03 (2010-05-30)


7-7



Procedure Step 1 See A.18.2 Configuring Synchronous Data Service and configure synchronous data services. The values for the relevant parameters are provided as follows. Parameter

Value NE1

NE2

NE3

NE4

Data Channel 1

F1

8-IFH-1

F1

8-IFH-1

Data Channel 2

8-IFH-1

F1

8-IFH-1

F1

----End

7.4 Configuration Example (Asynchronous Data Services) This section considers an asynchronous data service that transmits the NM messages as an example to describe how to configure asynchronous data services according to the service planning information. 7.4.1 Networking Diagram The section describes the networking information about the NEs. 7.4.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.4.3 Configuration Process The Serial byte in the radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated.

7.4.1 Networking Diagram The section describes the networking information about the NEs. In the networking diagram shown in Figure 7-5, the radio network transmits the NM information of the third-party equipment. The third-party equipment and the NMS use the protocol converter to convert the network management information transmitted over Ethernet into the network management information transmitted over RS-232 synchronous data services. Therefore, the radio transmission network needs to transparently transmit the corresponding synchronous data only. The networking information of the network is as follows:

7-8

l

NE1 and NE4 add or drop the asynchronous data services. NE2 and NE3 pass through the asynchronous data services.

l

All the other radio links are configured with 1+0 non-protection.


Issue 03 (2010-05-30)



Figure 7-5 Networking diagram (asynchronous data services) 3rd party NM

3rd party equipment 1+0 ETH

RS-232

RS-232/ETH Converter

RTN 605 1F NE4

1+0

S1 RTN 605 1F NE3

RS-232

E1 RTN 605 1F NE2

RTN 605 1F NE1

ETH

RS-232/ETH Converter

7.4.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. l

In this example, the TDM service between NE2 and NE3 needs to be spanned through the E1 channel. To implement service spanning between NE2 and NE3, the two asynchronous data interfaces between NE2 and NE3 are interconnected with each other.

l

In this example, set the overhead byte to SERIAL1 (default value).

l

According to the service path, you can obtain the asynchronous data service information provided in Table 7-3. Table 7-3 Information about the asynchronous data service NE

Broadcast Data Source

Broadcast Data Sink

NE1

SERIAL1

8-IFH-1

NE2

8-IFH-1

SERIAL1

NE3

SERIAL1

8-IFH-1

NE4

8-IFG-1

SERIAL1

NOTE

In the case of radio links configured with 1+1 protection, only the main link is configured with the asynchronous data service.

7.4.3 Configuration Process The Serial byte in the radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated.

Procedure Step 1 See A.18.3 Configuring Asynchronous Data Service and configure asynchronous data services. ----End Issue 03 (2010-05-30)


7-9



7.5 Configuration Example (External Alarms) This section considers environment monitoring and centralized control of equipment alarms through external alarms as examples to describe how to configure external alarms according to the service planning information. 7.5.1 Networking Diagram The section describes the networking information about the NEs. 7.5.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.5.3 Configuration Process This section describes the process for the data configuration.

7.5.1 Networking Diagram The section describes the networking information about the NEs. In the networking diagram shown in Figure 7-6, the requirements for external alarms on NE1 are as follows:

7-10

l

External alarm input interface 1 is used for connecting the alarm interface of the smoke sensor. When the alarm interface of the smoke sensor is closed, NE1 reports an alarm.

l

External alarm input interface 2 is used for connecting the alarm interface of the water sensor. When the alarm interface of the water sensor is closed, NE1 reports an alarm.

l

External alarm input interface 3 is used for connecting the alarm interface of the magnetic door switch sensor. When the alarm interface of the magnetic door switch sensor is closed, NE1 reports 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.


Issue 03 (2010-05-30)



Figure 7-6 Networking diagram (external alarms)

Input 1 Smoke sensor Input 2 NE1 Water sensor Input 3

Magnetic door switch sensor

Output 1

Centralized alarming box


Information About Input Alarms According to the requirements, you can obtain the input alarm information provided in Table 7-4. Table 7-4 Information about input alarms

Issue 03 (2010-05-30)

Input External Alarm

Channel Name

Usage Status

Alarm Mode

Interface 1

Fire alarm

Used

An alarm is generated when the interface is closed.

Interface 2

Water alarm

Used


Interface 3

Open cabinet door

Used



7-11



Information About Output Alarms According to the requirements, you can obtain the output alarm information provided in Table 7-5. Table 7-5 Information about output alarms Input External Alarm

Channel Name

Usage Status

Working Mode

Alarm Trigger Conditions

Alarm Mode

Interface 1

Centralized alarm box

Used

Automatic mode

The alarm is automaticall y triggered by critical and major alarms.

Relay turns off/high level

NOTE

The OptiX RTN 605 supports the automatic mode and the manual mode. The manual mode is used for commissioning the output alarms.


Procedure Step 1 See A.18.4 Configure External Alarms and configure external alarms. l

The values for the input alarm parameters are provided as follows. Parameter

Value NE1

l

Operation Object

NE1-3-EOW-1

NE1-3-EOW-2

NE1-3-EOW-3

Path Name

Fire alarm

Water alarm

Open cabinet door

Use or Not

Used

Used

Used

Alarm Mode

Relay Turns On/ Low Level



The values for the output alarm parameters are provided as follows. Parameter

Value NE1

Operation Object 7-12

NE1-3-EOW-1


Issue 03 (2010-05-30)



Parameter

Value NE1

Path Name

Centralized alarm box

Use or Not

Used

Working Mode

Automatic


Automatically Triggered by Critical and Major Alarms

Alarm Mode

Alarm Occurs when Relay Turns Off

----End

Issue 03 (2010-05-30)


7-13


A Supporting Task

A

Supporting Task

This chapter describes various operation tasks associated with configuration. A.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.2 Configuring Performance Monitoring Status of NEs By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually. A.3 Managing Communication To manage NEs on the NMS, ensure that DCN communication is normal. A.4 Configuring Service Access of NEs You can ensure the security of a network by setting service access of the NEs on the network. A.5 Managing Radio Links Before you configure the radio link between two radio sites, you need to configure the corresponding information about the radio link. A.6 Configuring the Monitored Status of E1 Interfaces This section describes how to set whether to monitor service alarms of E1 interfaces, which do not affect transmission of E1 services. A.7 Managing Clocks To ensure clock synchronization between transmission nodes on a transport network, you need to manage the NE clocks. A.8 Managing the STP If a loop exists in the network topology of Ethernet services, you need to enable the Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP). A.9 Managing LAGs Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved. A.10 Managing the QoS By managing the QoS, you can provide differentiated services for different service types. A.11 Using the IEEE 802.1ag OAM

Issue 03 (2010-05-30)


A-1


A Supporting Task

By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.12 Using the IEEE 802.3ah OAM With the IEEE 802.3ah OAM, you can maintain point-to-point Ethernet links. A.13 Using RMON Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.14 Configuring Ethernet Ports OptiX RTN 605The supported Ethernet ports include the external FE/GE ports on Ethernet boards and the internal IFUP ports. A.15 Configuring Ethernet Services Ethernet services are classified into EPL services, EVPL services, EPLAN services, and EPVLAN services. A.16 Managing the MAC Address Table The MAC address table is the core of the EPLAN or EVPLAN service. The OptiX RTN 605 provides various functions for managing the MAC address table. A.17 Modifying E1 Port Impedance The default E1 port impedance is 75 ohms, you can modify the E1 port impedance to 120 ohms as need. A.18 Configuring Auxiliary Interfaces and Functions The auxiliary interfaces and functions supported by the OptiX RTN 605 include the orderwire, synchronous data service, asynchronous data service, and external alarm. A.19 Testing Ethernet Services By testing Ethernet services, you can check whether Ethernet services are available over radio links. Ethernet services are tested through the ETH OAM function. Therefore, no tester is required.

A-2


Issue 03 (2010-05-30)


A Supporting Task

A.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.1 Creating NEs by Using the Search Method The Web LCT can find all NEs that communicate with a specific gateway NE according to the IP address of the gateway NE or the IP address range of the gateway NE. In addition, the Web LCT can create the NEs in batches. Compared with the method of manually creating NEs, this method is quicker and more reliable. A.1.2 Creating NEs by Using the Manual Method Using the manual method, you can only create NEs one by one. The manual method, unlike the search method, does not enable creation of NEs in batches. A.1.3 Logging In to an NE After an NE is created, you need to log in to the NE before managing the NE. A.1.4 Changing NE IDs This section describes how to change NE IDs according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services. A.1.5 Changing NE Names To accurately identify an NE in the Main Topology, you need to name the NE according to the geographical location or the equipment connected to the NE. A.1.6 Synchronizing NE Time By setting the NE time to be synchronous with the time on the NMS, you can record the exact time when alarms and abnormal events occur. A.1.7 Localizing NE Time When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE with the local time.

A.1.1 Creating NEs by Using the Search Method The Web LCT can find all NEs that communicate with a specific gateway NE according to the IP address of the gateway NE or the IP address range of the gateway NE. In addition, the Web LCT can create the NEs in batches. Compared with the method of manually creating NEs, this method is quicker and more reliable.

Prerequisite The NEs must gain the access to the computer where the Web LCT software is installed.

Tools, Equipment, and Materials Web LCT

Context You can create an NE by searching for the NE and then adding the NE on the Web LCT. In addition, you can create an NE by adding the NE manually. Generally, the NE ID is not known during initial NE configuration. Therefore, the searching method is used to create an NE in most cases. Issue 03 (2010-05-30)


A-3


A Supporting Task

Procedure Step 1 In NE List, click NE Search. Then, the Search NE dialog box is displayed. Step 2 Optional: Set Domain to 129.9.255.255, and click Search. NOTE

During initial configuration, Domain is 129.9.255.255 by default. After the gateway NE IP address of the searched NE is changed, you need to change the value of Domain.

Step 3 After the Web LCT finds the NEs to be managed, click End Search.

Step 4 Select the NE that needs to be added and click Add NE. A dialog box is displayed, indicating that the NE is added successfully. Step 5 Click OK. A new NE is already added to the NE list.

Step 6 Click Cancel. ----End

A.1.2 Creating NEs by Using the Manual Method Using the manual method, you can only create NEs one by one. The manual method, unlike the search method, does not enable creation of NEs in batches.

A-4


Issue 03 (2010-05-30)


A Supporting Task

Prerequisite l

The NEs must gain the access to the computer where the Web LCT software is installed.

l

The NE IDs must be known.


Context You can create an NE by adding the NE manually. In addition, you can create an NE by searching for the NE. If the NE ID is not known during initial NE configuration, you can create the NE by searching for the NE and adding the NE on the Web LCT.

Procedure Step 1 In NE List, click Add NE. Then, select Europe. Then, the Add NE dialog box is displayed. Step 2 In the Add NE dialog box, set the NE parameters.

Step 3 Click OK. A new NE is already added to the NE list.

----End

Parameters Parameter

Value Range

Default Value

Description

NE ID

1 to 49135

-

l

This parameter indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the networks that are managed by the same NMS.

l

Set this parameter according to the DCN planning information.

Issue 03 (2010-05-30)


A-5


A Supporting Task

Parameter

Value Range

Default Value

Description

Extended ID

1 to 254

9

l

Do not change the extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID.

l

It is recommended that this parameter takes the default value.

Gateway Type

IP Gateway

IP Gateway

This parameter specifies the type of the gateway that is used for the communication between the Web LCT and the NEs.

This parameter is set to 129.9.0.x when the NE is delivered from the factory. "x" indicates the basic NE ID that is set when the NE is delivered from the factory.

This parameter specifies the IP address of the gateway NE to which the NE to be created belongs. This parameter is displayed only when Gateway Type is set to IP Gateway.

This parameter specifies the port corresponding to the gateway NE to which the NE to be created belongs.

Serial Port IP Address

-

Port

l

1400 (when Gateway Type is set to IP Gateway)

l

1400 (when Gateway Type is set to IP Gateway)

l

COM1-COM32 (when Gateway Type is set to Serial Port)

l

COM1 (when Gateway Type is set to Serial Port)

Baud Rate

1200bps

1200bps

This parameter specifies the communication rate between the NE to be created and the corresponding gateway NE. This parameter is displayed only when Gateway Type is set to Serial Port.

2400bps 4800bps 9600bps 19200bps 38400bps 57600bps 115200bps User Name

-

lct

This parameter specifies the name of the user. This parameter can take the default value in the case of initial login.

Password

-

-

The default password of user lct is password.

A.1.3 Logging In to an NE After an NE is created, you need to log in to the NE before managing the NE. A-6


Issue 03 (2010-05-30)


A Supporting Task

Prerequisite l

The NE user must have the authority of Operation Level or higher.

l

The NEs to be managed must be created in the NE List.


Procedure Step 1 In the NE List, select the target NE and click NE Login. TIP

You can select more than one NE at one time.

The NE Login dialog box is displayed. Step 2 Enter User Name and Password. Then, click OK.

l

The default User Name is lct.

l

The default Password of user lct is password.

Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is changed from Unknown to the current alarm status of the NE. Step 3 Click NE Explorer. The NE Explorer is displayed. TIP

To quickly start the NE Explorer, double-click the NE to be managed in the NE list.

Issue 03 (2010-05-30)


A-7


A Supporting Task

TIP

l

Check the legend to learn the specific meanings of different colors and symbols in the slot layout diagram.

l

Click

to fold/unfold the legend.

----End

Example Table A-1 Parameters Parameter

Value Range

Default Value

Description

User Name

-

lct

This parameter specifies the name of the user. This parameter can take the default value in the case of initial login.

Password

-

-

The default password of user lct is password.

Use same user name and password to login

Selected

Deselected

When this parameter is selected, enter User Name and Password to log in to all the selected NEs.

Use the user name and password that was used last time

Selected

Deselected

When this parameter is selected, enter User Name and Password that were used for the latest login to log in to the NE.

Deselected

Deselected

A.1.4 Changing NE IDs This section describes how to change NE IDs according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services.

Prerequisite The NE user must have the authority of Operation Level or higher. A-8


Issue 03 (2010-05-30)


A Supporting Task


Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID. The Modify NE ID dialog box is displayed. Step 3 Set a new ID for the NE.

Step 4 Click OK. Then, a dialog box is displayed. Click OK. ----End


Value Range

Default Value

Description

New ID

1 to 49135

-

l

The new ID refers to the basic ID. When the extended ID is not used, the basic ID of an NE within any network that is managed by an NMS must be unique.

l

Set this parameter according to the DCN planning information.

l

When the number of existing NEs does not exceed the range represented by the basic ID, do not modify the extended ID.

l


1 to 254

New Extended ID

9

NOTE

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

Issue 03 (2010-05-30)


A-9


A Supporting Task

Postrequisite In the case of the OptiX RTN 605, you only need to close the NE Explorer and then re-log in to the NE, if the IP address does not change accordingly after the NE ID changes; You need to delete the original NE, create an NE, and then log in to the NE, if the IP address of the NE changes after the NE ID changes. Before the IP address of the NE is changed manually, the IP address changes accordingly if the NE ID changes. After the IP address of the NE is changed manually, the IP address does not change accordingly if the NE ID changes.

A.1.5 Changing NE Names To accurately identify an NE in the Main Topology, you need to name the NE according to the geographical location or the equipment connected to the NE.

Prerequisite The NE user must have the authority of Operation Level or higher.


Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Attribute from the Function Tree. Step 2 Enter the name of the NE in Name. Step 3 Click Apply. ----End

A.1.6 Synchronizing NE Time By setting the NE time to be synchronous with the time on the NMS, you can record the exact time when alarms and abnormal events occur.

Prerequisite l


l

Ensure that the time zone and time on the NM computer are correctly set.


Precautions In the commissioning phase, you only need to synchronize the NE time with the time of the Web LCT server to ensure that the time of the alarms and abnormal events reported on the NE is correct. After all the NEs are placed under the NMS, re-synchronize the NE time according to the synchronization strategy of the network time. A-10


Issue 03 (2010-05-30)


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Synchronization from the Function Tree. Step 2 Set the synchronous mode. If ...

Then ...

You set Synchronous Mode to NULL or NTP Set the relevant parameters, and then click Apply. You set Synchronous Mode to NM

Set the relevant parameters, and then click Apply to perform step Step 6.

You set Synchronous Mode to Standard NTP Set the related parameters, and then click Apply to perform steps Step 3 to Step 5.

NOTE

If you only need to synchronize the NE time and need not change the type of synchronization or parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize with NM Time.

Step 3 Configure the upper-layer standard NTP server of the NE. 1.

Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add.

2.

After setting the parameters of the standard NTP server, click OK. NOTE

l

If the NE is a GNE, set the external NTP server as the standard NTP server.

l

If the NE is a non-GNE, set the GNE as the standard NTP server.

Step 4 Optional: Configure the NTP access control rights. 1.

Click the Access Control Rights tab. In the Access Control Rights tab page, click Add.

2.

After setting the parameters of the access control rights, click OK.

Step 5 Optional: Configure the NTP key. 1.

Click the Standard NTP Key Management tab. In the Standard NTP Key Management tab page, click Add.

2.

After setting the parameters of the NTP key management, click OK. NOTE

l

Configuring the NTP key is required only when NTP authentication is enabled.

l

To pass the NTP authentication, the NTP authentication must be enabled on both the client and the server, and Key, Password, and Encryption Type of the client must be consistent with those of the server.

Step 6 Optional: Set Synchronization Starting Time and click Apply. ----End

Issue 03 (2010-05-30)


A-11


A Supporting Task


Value Range

Default Value

Description

Synchronous Mode

NTP

NULL

l

When this parameter is set to NM, the NE is synchronized with the NMS server.

l

When this parameter is set to NTP, the NE is synchronized with the network time protocol (NTP) server.

l

When this parameter is set to Standard NTP, the NE is synchronized with the NTP server through the standard NTP protocol.

l

This parameter is valid only when Synchronous Mode is set to Standard NTP.

l

When this parameter is set to Enable, the NTP authentication is required. Therefore, the key used for the NTP authentication should be configured.

l

This parameter is valid only when Synchronous Mode is set to NTP.

l

This parameter indicates whether the NE functions as the ECC server and provides NTP service for the ECC communication between this NE and other NEs.

l

If this NE can communicate with the NTP server over IP but the other NEs that communicate with this NE over ECC cannot communicate with the NTP server over IP, set this parameter to ECC Server. Otherwise, set this parameter to Disable.

Standard NTP NM NULL

Standard NTP Authentication

Server Enabled

Enable

Disable

Disable

ECC Server

ECC Server

Disable

A-12


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Client Enabled

l

l

Synchronous Server

Polling Period (min)

The Number of Sampling

Issue 03 (2010-05-30)

ECC Client, IP Client, Disable (when Server Enabled is set to ECC Server)

Default Value

Description

ECC Client

l


l

When this parameter is set to ECC Client, the NE is synchronized with the ECC server of the NTP based on ECC communication.

l

When this parameter is set to IP Client, the NE is synchronized with the NTP server based on IP communication.

l

When the NE can implement communication directly through IP or the NTP server, set this parameter to IP Client. When the NE can communicate with the ECC server of the NTP over ECC, set this parameter to ECC Client.

l

When the NE functions as the ECC server and is not synchronized with an NTP server, set this parameter to Disable.

l


l

To modify this parameter, right-click this parameter and then select the option from the shortcut menu according to actual requirements.

l

When Client Enabled is set to ECC Client, this parameter indicates the NE ID of the ECC server.

l

When Client Enabled is set to IP Client, this parameter indicates the IP address of the higher level NTP server.

l


l

This parameter indicates the interval between the requests sent by the NTP client.

l

Set this parameter according to the requirements of the NTP server.

l


l

This parameter indicates the number of NTP packets that are sent for obtaining information required for synchronizing the time at each request.

l

Set this parameter according to the requirements of the NTP server.

ECC Client, IP Client (when Server Enabled is set to Disable)

-

2 to 1440

1 to 8

-

120

8


A-13


A Supporting Task

Table A-4 Parameters of the standard NTP server Parameter

Value Range

Default Value

Description

Standard NTP Server Flag

NE ID

NE ID

l

When ECC is used to communicate with the standard NTP server, set the parameter to NE ID.

l

When the IP protocol is used to communicate with the standard NTP server, set the parameter to NE IP.

NE IP

Standard NTP Server

-

-

This parameter specifies the ID or IP address of the standard NTP server.

Standard NTP Server Key

0 to 1024

1

This parameter specifies the NTP protocol key. 0 indicates that no key is required.

Standard NTP Version

2

2

Set this parameter according to the settings for the standard NTP protocol version used at the peer end.

Used First

Yes

No

This parameter specifies whether to select a server preferentially when multiple NTP servers are available.

3

No

Table A-5 Parameters of the access control rights Parameter

Value Range

Default Value

Description

ACL No.

1 to 250

1

This parameter specifies the number of the ACL.

NE Flag

NE ID

NE ID

l

When ECC is used to communicate with the standard NTP server, set the parameter to NE ID.

l

When the IP protocol is used to communicate with the standard NTP server, set the parameter to NE IP.

NE IP

NE

-

-

This parameter specifies the ID or IP address of an NE.

Whether to Receive Data Packet

Yes

Yes

This parameter specifies whether to receive packets from an NE.

A-14

No


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Right Level

query

query

The equipment provides four levels of access control. When an NTP access request is received on the local equipment, the request is matched with the levels from the minimum access limit to the maximum access limit, and the first matched level prevails. The matching order is as follows:

synchronize server peer

l

Peer (minimum access limit): The time request and the control query can be carried out for the NTP service of the local equipment. The local clock can also be synchronized with the remote server.

l

Server: The time request and the control query can be carried out for the NTP service of the local equipment, but the local clock is not synchronized to the remote server.

l

Synchronization: The time query is allowed for only the NTP service of the local equipment.

l

Query (maximum access limit): The control query can be carried out only for the NTP service of the local equipment.

Table A-6 Parameters of the NTP key management Parameter

Value Range

Default Value

Description

Encryption

MD5

MD5

This parameter specifies the MD5 key algorithm.

Key

1 to 1024

1

This parameter specifies the number of the key.

Password

-

-

This parameter specifies the password of the key.

Trusted

Yes

No

If you set this parameter to No, the key is verified but cannot be trusted during the clock synchronization. Therefore, the clock of the NE cannot be synchronized.

No

A.1.7 Localizing NE Time When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE with the local time.

Issue 03 (2010-05-30)


A-15


A Supporting Task



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Localization Management from the Function Tree. Step 2 Set the correct time zone and daylight saving time of the NE depending on the location of the NE.

Step 3 Click Apply. ----End

A-16


Issue 03 (2010-05-30)


A Supporting Task


Value Range

Default Value

Description

Time Zone

-

-

l

Changing the time zone results in transition of the current NE time.

l

Set this parameter according to the location of the NE.

l

The DST-related parameters are valid only if this parameter is set to Enabled.

l

Set these parameters depending on whether the location of the NE adopts the DST.

l

When the DST Rule is set to MM-WWDD, Start Time and Stop Time of the DST is set in month-week-day format.

l

When the DST Rule is set to MM-DD, Start Time and Stop Time of the DST is set in month-day format.

l

Set this parameter according to the DST rule in the location of the NE.

l

Start Time is automatically added with the DST Offset time according to the current NE time. Stop Time is automatically decreased by the DST Offset time according to the current NE time. Set the three parameters according to the DST rule in the location of the NE.

DST

Enabled

Disabled

Disabled

DST Rule

MM-WW-DD

MM-WW-DD

MM-DD

DST Offset

-

-

Start Time

-

-

Stop Time

-

-

l

l

A.2 Configuring Performance Monitoring Status of NEs By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually.



Issue 03 (2010-05-30)


A-17


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE and then choose Performance > NE Performance Monitor Time from the Function Tree. Step 2 Set the parameters of NE performance monitoring. 1.

Select 15-Minute or 24-Hour.

2.

Select Enable or Disable 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

l

Set 15-Minute Monitoring and Set 24-Hour Monitoring are generally set to Enable.

l

You can specify the start time of the performance monitoring function, only after selecting Enable in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

l

You can specify the end time of the performance monitoring function, only after selecting Enable and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.


A.3 Managing Communication To manage NEs on the NMS, ensure that DCN communication is normal. A.3.1 Setting NE Communication Parameters The communication parameters of an NE include the IP address and extended ID of the NE, the gateway IP address, NSAP address, and the subnet mask. A.3.2 Configuring DCCs A-18


Issue 03 (2010-05-30)


A Supporting Task

To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the service planning information. A.3.3 Configuring the Extended ECC When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports on the system control unit of the NEs to realize communication through the extended ECC. A.3.4 Creating Static IP Routes When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually. A.3.5 Setting Parameters of the OSPF Protocol When the IP over DCC solution is used to realize the interconnection between the OptiX equipment and the third-party equipment, you need to set the parameters of the OSPF protocol according to the requirements of the third-party equipment, thus implementing the route protocol interworking between the OptiX equipment and the third-party equipment. A.3.6 Enabling the ARP Proxy The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. A.3.7 Querying ECC Routes By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal. A.3.8 Querying IP Routes By querying IP routes, you can check whether the IP over DCC solution is configured correctly and whether the communication between NEs is normal.

A.3.1 Setting NE Communication Parameters The communication parameters of an NE include the IP address and extended ID of the NE, the gateway IP address, NSAP address, and the subnet mask.



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Communication Parameters from the Function Tree. Step 2 Set the communication parameters of the NE.

Issue 03 (2010-05-30)


A-19


A Supporting Task



Value Range

Default Value

Description

IP

-

Before delivery, the IP address of the NE is set to 129.9.0.x. The letter x indicates the basic ID.

Gateway IP

-

0.0.0.0

Subnet Mask

-

255.255.0.0

In the HWECC solution, an IP address is set according to the following rules: l The IP address, subnet mask, and default gateway of the gateway NE must meet the planning requirements of the external DCN. l If an NE uses the extended ECC, the IP address must be in the same network segment. l The IP address of other NEs must be set according to the NE ID. In this example, the IP address of an NE must be set in the format of 0x81000000+ID. That is, if the ID is 0x090001, the IP address must be set to 129.9.0.1.

Extended ID

1 to 254

9

l

Do not change the extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID.

l


A-20


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

NSAP Address

-

-

The OptiX RTN 605 does not support this parameter.

Connection Mode

Common

Common

The OptiX RTN 605 does not support this parameter.

Security SSL

A.3.2 Configuring DCCs To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the service planning information.



Precautions The OptiX RTN 605 simultaneously supports 12 channels comprising byte D1, 12 channels comprising bytes D1 to D3, 6 channels comprising bytes D4 to D12, and 2 channels comprising bytes D1 to D12. If the DCC communication configuration already exceeds the restriction, close or adjust the DCCs of certain interfaces, depending on the actual situation. The OptiX RTN 605 supports only one channel that comprises bytes D1 to D3.

Procedure Step 1 In the NE Explorer, select the NE and then choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab. Step 2 Optional: Modify the channel type or protocol type of an existing DCC. 1.

Select the DCC to be modified and click Delete.

2.

Click Create. Then, the Create dialog box is displayed.

3.

Set the DCCs.

4.

Click OK.

Issue 03 (2010-05-30)


A-21


A Supporting Task

Step 3 Optional: Modify the enabled status of a DCC. 1.

Double-click the cell in the Enable Status column to which the DCC corresponds. Set the required state in the drop-down box.

2.

Click Apply.

----End


Value Range

Default Value

Description

Port

IF interface

-

This parameter specifies the port of the DCCs.

Enabled/Disabled

Enabled

Enabled (in the case of line interfaces)

It is recommended that you use the default value except in the following cases:

Disabled (in the case of the external clock interface)

l

Set Enabled/Disabled of the interface that is connected to another ECC subnet to Disabled.

l

Set Enabled/Disabled of the interface that is connected to a third-party network but does not transmit NM messages to Disabled.

l

When the DCC transparent transmission through the external clock interface solution is applied, set Enabled/ Disabled of the used external clock interface to Enabled.

Disabled

Channel Type

D1-D1

-

D1-D3 D4-D12

It is recommended that you use the default value except in the following cases: l

When the IP over DCC solution or OSI over DCC solution is applied, set Channel Type of the SDH line interfaces to the same value as the channel type of third-party network.

l

When the DCC transparent transmission solution is applied, the channel type of the SDH line interfaces must not conflict with the channel type of the third-party network.

D1-D12

Protocol Type

HWECC TCP/IP OSI

A-22

HWECC

It is recommended that you use the default value except in the following cases: l

When the IP over DCC solution is applied, set Protocol Type to TCP/IP.

l

When the OSI over DCC solution is applied, set Protocol Type to OSI.


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

LAPD Role

User

User

l

This parameter is valid only when Protocol Type is set to OSI.

l

Set LAPD Role to User at one end of a DCC and to Network at the other end of the DCC.

Network

A.3.3 Configuring the Extended ECC When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports on the system control unit of the NEs to realize communication through the extended ECC.



Procedure Step 1 In the NE Explorer, select the NE and then choose Communication > ECC Management from the Function Tree. Step 2 Set ECC Extended Mode. Step 3 Optional: 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 the communication between NEs. Step 5 Click OK. ----End Issue 03 (2010-05-30)


A-23


A Supporting Task


Value Range

Default Value

Description

ECC Extended Mode

Auto mode

Specified mode


Port (on the server side)

1601 to 1699

1601

l

This parameter is valid only when ECC Extended Mode is set to Specified mode.

l

This parameter can be set only when the NE functions as the server of the extended ECC. In normal cases, the NE that is close to the U2000 functions as the server.

l

This parameter can be set to any value from 1601 to 1699.

l

This parameter is valid only when ECC Extended Mode is set to Specified mode. This parameter can be set only when the NE functions as the client of the extended ECC. Except for the NE that functions as the server, all other NEs that use the extended ECC can function as the client. Opposite IP and Port are respectively set to the IP address of the server NE and the specified port number.

Specified mode

Opposite IP (on the client side)

-

-

Port (on the client side)

1601 to 1699

1601

l

l

A.3.4 Creating Static IP Routes When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually.



Procedure Step 1 In the NE Explorer, select the NE, and choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. A-24


Issue 03 (2010-05-30)


A Supporting Task

Step 2 Click New. Then, the Create an IP Route dialog box is displayed. Step 3 Set the parameters of the static IP route.

Step 4 Click OK. ----End


Value Range

Default Value

Description

Destination Address

-

-

Set this parameter to an IP address or an IP address range.

Mask

-

-

This parameter specifies the subnet mask of the set Destination Address.

Gateway IP

-

-

This parameter specifies the IP address of the gateway to which the set Destination Address corresponds, that is, the next-hop address.

NOTE

The created static route has a lower priority than a dynamic route.

A.3.5 Setting Parameters of the OSPF Protocol When the IP over DCC solution is used to realize the interconnection between the OptiX equipment and the third-party equipment, you need to set the parameters of the OSPF protocol according to the requirements of the third-party equipment, thus implementing the route protocol interworking between the OptiX equipment and the third-party equipment.


Tools, Equipment, and Materials Web LCT Issue 03 (2010-05-30)


A-25


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Communication > IP Stack Protocol 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

A.3.6 Enabling the ARP Proxy The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other.



Procedure Step 1 In the NE Explorer, select the NE, and choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Click the Proxy ARP tab. Step 3 Set the enabled status of the proxy ARP. Step 4 Click Apply. ----End

A.3.7 Querying ECC Routes By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal.



A-26


Issue 03 (2010-05-30)


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link Management List. ----End

A.3.8 Querying IP Routes By querying IP routes, you can check whether the IP over DCC solution is configured correctly and whether the communication between NEs is normal.



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Check whether the IP routes and related parameters in the routing table are in accordance with the service planning information. ----End

A.4 Configuring Service Access of NEs You can ensure the security of a network by setting service access of the NEs on the network. A.4.1 Configuring LCT Access to NEs When an NE is managed by the NMS, the LCT cannot access this NE by default. A.4.2 Configuring Ethernet Access to NEs By default, the NMS can access an NE by using the Ethernet port. A.4.3 Configuring Serial Interface Access to NEs By default, the NMS can access an NE through serial interfaces.

A.4.1 Configuring LCT Access to NEs When an NE is managed by the NMS, the LCT cannot access this NE by default.

Prerequisite The NE user must have the authority of Operation Level or higher. Issue 03 (2010-05-30)


A-27


A Supporting Task


Context l

If the LCT requests to log in to an NE to which the NMS has logged in, the NE determines whether to permit the login of the LCT according to the status of LCT Access Control Switch.

l

If the LCT requests to log in to an NE to which the NMS has not logged in, the NE permits the login of the LCT regardless of the status of LCT Access Control Switch. The NMS, however, can log in to an NE to which the LCT has logged in. That is, the login of the LCT does not affect the login of the NMS. After the NMS user logs in to the NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is set to Disable Access, the logged LCT user is also not affected.

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT Access Control from the Function Tree.

Step 2 Click Access Allowed to enable the LCT access function. NOTE

To disable the LCT access function, click Disable Access.

----End

A.4.2 Configuring Ethernet Access to NEs By default, the NMS can access an NE by using the Ethernet port.



Context

A-28

l

It is recommended that the LCT accesses an NE through Ethernet interfaces.

l

If you need to initialize an NE or perform software loading by using the LCT, the LCT needs to access the NE through Ethernet interfaces.


Issue 03 (2010-05-30)


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Select the Enable Ethernet Access check box and click Apply to enable the Ethernet access function.

NOTE

To disable the Ethernet access function, deselect the Enable Ethernet Access check box and click Apply.

----End

A.4.3 Configuring Serial Interface Access to NEs By default, the NMS can access an NE through serial interfaces.



Context If the LCT cannot access an NE through serial interfaces when the Enable Serial Port Access check box is selected, the LCT access function may be disabled.

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Select the Enable Serial Port Access check box and select Access NM. Then, click Apply.

Issue 03 (2010-05-30)


A-29


A Supporting Task

Step 3 Optional: Select the baud rate of the serial interface from the Baud Rate drop-down list. Click Apply to complete the setting. ----End


Value Range

Default Value

Description

Enable Serial Port Access

Selected

Selected

If the Enable Serial Port Access check box is selected, the serial port access function is available.

Access Command Line

Selected

Not selected

If Access Command Line is selected, the serial interface can be used to access the command line terminal.

Selected

If Access NM is selected, the serial interface can be used to access the NMS.

9600

This parameter specifies the communication rate of the serial port. This parameter can be set only when the Enable Serial Port Access check box is selected.

Not selected

Not selected

Access NM

Selected Not selected

Baud Rate

1200 2400 4800 9600 19200 38400 57600 115200

A.5 Managing Radio Links Before you configure the radio link between two radio sites, you need to configure the corresponding information about the radio link. A.5.1 Modifying Parameters of IF 1+1 Protection In the case of the OptiX RTN 605 2D/2E/2F, the system automatically creates a 1+1 HSB protection group. The working mode and other parameters of the protection group can be modified. A.5.2 Configuring the IF/ODU Information of a Radio Link By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the radio link. A.5.3 Setting the Hybrid/AM Attribute Hybrid radio supports hybrid transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Therefore, Hybrid radio ensures reliable transmission of A-30


Issue 03 (2010-05-30)


A Supporting Task

E1 services and flexible transmission of Ethernet services whose bandwidth is large and changes dynamically. A.5.4 Configuring the ATPC function To configure the ATPC function, set the ATPC attributes of the IF board. A.5.5 Setting Parameters of IF Interfaces This section describes how to set parameters of IF interfaces, including the IF attributes and ATPC attributes of the IF boards. A.5.6 Setting Parameters of ODU Interfaces This section describes how to set parameters of an ODU interface, including the RF attributes, power attributes, and advanced attributes of the ODU. A.5.7 Querying ATPC Adjustment Records By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function. A.5.8 Querying History Transmit Power and Receive Power Checking the change trend of the history transmit power and receive power provides reference for radio link troubleshooting. A.5.9 Querying the AM Status By querying the AM status, you can trace the change of the modulation mode when the AM function is used. A.5.10 Querying the IF 1+1 Protection Status You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status. A.5.11 Performing IF 1+1 Protection Switching You can perform an external switching on an IF 1+1 protection group by performing an IF 1+1 protection switching.

A.5.1 Modifying Parameters of IF 1+1 Protection In the case of the OptiX RTN 605 2D/2E/2F, the system automatically creates a 1+1 HSB protection group. The working mode and other parameters of the protection group can be modified.



Context In the case of the OptiX RTN 605 2D/2E/2F, the board installed in slot 8 is always the main IF board (this board corresponds to the IF interface "ODU-M" on the front panel of the OptiX RTN 605 2D/2E/2F), and the board installed in slot 7 is always the standby IF board (this board corresponds to IF interface "ODU-S" on the front panel of the OptiX RTN 605 2D/2E/2F).

Issue 03 (2010-05-30)


A-31


A Supporting Task

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Modify the parameters of IF 1+1 protection.



Value Range

Default Value

Description

Working Mode

HSB

HSB

l

In 1+1 HSB protection mode, the system provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to provide protection.

l

In 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced.

l

In 1+1 SD protection mode, the system uses two antennas with a specific space distance from each other to receive the same RF signal. The equipment selects from the two received signals. The 1+1 SD protection configuration reduces the impact on signal transmission caused by fading.

l

The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function.

l

Set this parameter according to the service planning information.

FD SD

A-32


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Revertive Mode

Revertive

Revertive

l

When this parameter is set to Revertive, the NE that is in the switching state releases the switching and causes the former working channel to return to the working state some time after the former working channel is restored to normal.

l

When this parameter is set to NonRevertive, the NE that is in the switching state keeps the state of the former working channel unchanged even though the former working channel is restored to normal unless another switching occurs.

l


l

This parameter is valid only when Revertive Mode is set to Revertive.

l

When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs.

l


l

When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end.

l

This parameter is valid only when Working Mode is set to HSB or SD.

l

Generally, if Working Mode is set to HSB, it is recommended that you set this parameter to Disabled; if Working Mode is set to SD, it is recommended that you set this parameter to Enabled.

Non-Revertive

WTR Time(s)


300 to 720

Enable

300

Enable

Disable

NOTE

The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.

Issue 03 (2010-05-30)


A-33


A Supporting Task

Postrequisite l

In the case of 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ ODU information of the main radio link later. The standby radio link automatically copies the relevant information of the main radio link except the transmission status of the ODU.

l

In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the information of the standby ODU later. The standby radio link automatically copies the IF information of the main radio link. NOTE

The default TX Status of an ODU is Unmute. Therefore, you need not configure the TX Status of the standby ODU after you create an IF 1+1 protection group.

A.5.2 Configuring the IF/ODU Information of a Radio Link By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the radio link.

Prerequisite l


l

The ODU to which the IF interface is connected must be added.


Precautions l

In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In this case, you need configure only the IF/ODU information of the main equipment.

l

In 1+1 FD protection mode, one protection group corresponds to one radio link. In this case, you need configure the IF/ODU information of the main equipment and the ODU information of the standby equipment.

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF/ODU Configuration tab. Step 3 Click an IF board icon or ODU icon. Then, the system displays the IF/ODU information of the radio link to which the IF board or ODU to which the IF board is connected belongs. Step 4 Configure the 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. A-34


Issue 03 (2010-05-30)


A Supporting Task NOTE

You need to click Apply after you set the IF information of the radio link and click Apply after you set the ODU information of the radio link.

----End


Value Range

Default Value

Description

Work Mode

5)32M, 28MHz,QPSK

-

l

This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format.

16)10M, 7MHz,QPSK

l

The IDU 605 1D/2D does not support work modes 21-24.

17)20M, 14MHz,QPSK

l

The IFH1 board on the IDU 605 1F/2F does not support Work Mode.

19)10M,3.5MHz, 16QAM

l

Set this parameter according to the service planning information. The radio working modes of the IF boards at both ends of the radio link must be the same.

l

As the identifier of a radio link, this parameter is used to prevent misconnection of radio links between sites.

l

If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream.

l

Set this parameter according to the service planning information. Each radio link of an NE must have a unique link ID, and the link IDs at both ends of a radio link must be the same.

6)32M,14MHz, 16QAM

20)20M,7MHz, 16QAM 21)40M, 28MHz,QPSK 22)40M,14MHz, 16QAM 23)64M,28MHz, 16QAM 24)80M,28MHz, 16QAM Link ID

Issue 03 (2010-05-30)

1 to 4094

-


A-35


A Supporting Task

Parameter

Value Range

Default Value

Description

Received Link ID

-

-

This parameter displays the received link ID. NOTE The link ID at the local end must the same as the link ID at the opposite end.

ATPC Enable Status

Enabled

-

l

This parameter specifies whether the ATPC function is enabled. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the transmit power of the transmitter automatically traces the changes of the receive level at the receive end, within the ATPC controlled range.

l

In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled.

l

During commissioning, set this parameter to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.

l

Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. You can set the ATPC upper threshold only when ATPC Automatic Threshold (dBm) is set to Disabled.

Disabled

ATPC Upper Threshold(dBm)

-75.0 to -20.0

-45.0

ATPC Lower Threshold(dBm)

-35.0 to -90.0

-70.0 l

l

A-36


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

ATPC Automatic Threshold Enable Status

Enabled

Disabled

l

This parameter specifies whether the ATPC automatic threshold function is enabled.

l

If this parameter is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link.

l

If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm).

l

The parameter specifies the channel center frequency.

l

The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing.

l

The difference between the transmit frequencies of the ODUs at both ends of a radio link is a T/R spacing.

l


TX Frequency (MHz)

Disabled

0 to 4294967.295

-

Range of TX Frequency(MHz)

-

-

This parameter specifies the transmit frequency range of an ODU.

Actual TX Frequency(MHz)

-

-

This parameter displays the actual transmit frequency of an ODU.

Actual RX Frequency(MHz)

-

-

This parameter displays the actual receive frequency of an ODU.

Issue 03 (2010-05-30)


A-37


A Supporting Task

Parameter

Value Range

Default Value

Description

T/R Spacing (MHZ)

0 to 4294967.295

-

l

This parameter indicates the spacing between the TX frequency and receive frequency of the ODU. If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive power.

l

If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used.

l

The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.

Actual T/R Spacing(MHZ)

-

-

This parameter displays the actual T/R spacing of a board.

TX Power(dBm)

-10.0 to +35.0

-

l

The value of this parameter must not exceed the rated power range supported by the ODU.

l

The transmit power of the ODU must be set to the same value at both ends of a radio link.

l


Range of TX Power (dBm)

-

-

This parameter specifies the transmit power range of an ODU.

Actual TX Power (dBm)

-

-

This parameter displays the actual transmit power of an ODU.

Actual RX Power (dBm)

-

-

This parameter displays the actual receive power of an ODU.

TX Status

mute

-

l

When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive radio signals.

l

When Transmission Status is set to unmute, the ODU normally transmits and receives radio signals.

l

This parameter, generally, takes the default value.

unmute

Actual TX Status

mute unmute

A-38

-

This parameter displays the transmission status of the RF transmitter.


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Frequency(GHz)

-

-

This parameter displays the operating frequency band of an ODU.

Equip Type

-

-

This parameter displays the type of an ODU.

Station Type

-

-

This parameter displays the type of a site.

Produce SN

-

-

This parameter displays the production serial number and the manufacturer code of an ODU.

Transmission Power Type

-

-

This parameter displays the output power level of an ODU.

NOTE

The ATPC attributes must be set to the same at both the ends of a radio link.

A.5.3 Setting the Hybrid/AM Attribute Hybrid radio supports hybrid transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Therefore, Hybrid radio ensures reliable transmission of E1 services and flexible transmission of Ethernet services whose bandwidth is large and changes dynamically.



Context The OptiX RTN 605 1F/2F supports the Hybrid/AM function.

Procedure Step 1 In the NE Explorer, select the Hybrid IF board, and then choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Click Query. Step 3 Set the parameters associated with the Hybrid/AM function.

Step 4 Click Apply. ----End Issue 03 (2010-05-30)


A-39


A Supporting Task


Value Range

Default Value

Description


In the case of the IFH1 board on the OptiX RTN 605 1F/2F:

7M

IF Channel Bandwidth indicates the channel spacing of the corresponding radio links. This parameter needs to set according to the service planning information.

-

l

When this parameter is set to Disable, the radio link uses the specific modulation mode only. In this case, you need to select Manually Specified Modulation Mode.

l

When this parameter is set to Enable, the radio link uses the corresponding modulation mode according to the channel conditions.

AM Enable Status

l

7M

l

14M

l

28M

Disable Enable

Hence, the Hybrid radio ensures reliable transmission of the E1 services and provides dynamic bandwidth for the Ethernet services when the AM function is enabled. Modulation Mode of the Guarantee AM Capacity

QPSK

QPSK

16QAM 32QAM 64QAM 128QAM 256QAM


QPSK 16QAM 32QAM 64QAM 128QAM 256QAM

A-40

This parameter specifies the lowest-efficiency modulation mode that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation mode. This parameter is valid only when AM Enable Status is set to Enable.

128QAM

This parameter specifies the highest-efficiency modulation mode that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation mode. This parameter is valid only when AM Enable Status is set to Enable.


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description


QPSK

-

This parameter specifies the modulation mode that the radio link uses for the transmission.

16QAM

This parameter is valid only when AM Enable Status is set to Disable.

32QAM 64QAM 128QAM 256QAM

E1 Capacity

1 to 16

-

This parameter specifies the maximum number of E1 services that are transmitted in Hybrid radio mode. The value of this parameter cannot exceed the Assured E1 Capacity. E1 Capacity must be set to the same value at both ends of a radio link.

A.5.4 Configuring the ATPC function To configure the ATPC function, set the ATPC attributes of the IF board.

Prerequisite l


l

The corresponding IF board must be added.


Precautions l

In the case of two IF boards that are configured as a 1+1 protection group, set only the ATPC attributes of the main IF board.

l

The following procedure describes how to set ATPC parameters in the IF interface configuration dialog box of the IF board. You can also set ATPC parameters during the following process: A.5.2 Configuring the IF/ODU Information of a Radio Link

Procedure Step 1 In the NE Explorer, select the IF board from the Object Tree and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the ATPC Attributes tab. Step 3 Set the ATPC attributes.

Issue 03 (2010-05-30)


A-41


A Supporting Task



Value Range

Default Value

Description

ATPC Enable Status

Enabled

Disabled

l

This parameter specifies whether the ATPC function is enabled. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range.

l

In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled.

l

Set the central value between the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB.

Disabled

ATPC Upper Threshold (dBm)

-20 to -75

-45

ATPC Lower Threshold (dBm)

-35 to -90

-70

ATPC Adjustment (dB)

1

l

2 3

-

This parameter specifies the step for an ATPC adjustment to the ODU transmit power.

4 5

A-42


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

ATPC Automatic Threshold Enable Status

Enabled

Enabled

l

This parameter specifies whether the ATPC function is enabled. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range.

l

When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board.

l

When the function is disabled, the manually set ATPC upper and lower thresholds are used.

Disabled

ATPC Automatic Threshold (dBm)

-

-

This parameter displays the ATPC automatic threshold.

ATPC Upper Automatic Threshold(dBm)

-

-

This parameter displays the ATPC upper automatic threshold.

ATPC Lower Automatic Threshold(dBm)

-

-

This parameter displays the ATPC lower automatic threshold.

NOTE

l

Set ATPC attributes to the same values at both ends of a radio link.

l

During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.

A.5.5 Setting Parameters of IF Interfaces This section describes how to set parameters of IF interfaces, including the IF attributes and ATPC attributes of the IF boards.




A-43


A Supporting Task

Procedure Step 1 In the NE Explorer, select the IF board from the Object Tree and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Set each parameter for the IF attributes.

NOTE

In the case of the IFH1 board on the OptiX RTN 605 1F/2F, Radio Work Mode cannot be specified manually.

Step 4 Click Apply. Step 5 Click the ATPC Attributes tab. Step 6 Set each parameter for the ATPC attributes.


A-44


Issue 03 (2010-05-30)


A Supporting Task


Value Range

Default Value

Description

Radio Work Mode

5)32M, 28MHz,QPSK

-

l

This parameter indicates the radio working mode in "working mode, service capacity, channel spacing, modulation mode" format.

16)10M, 7MHz,QPSK

l

The IDU 605 1D/2D does not support work modes 21-24.

17)20M, 14MHz,QPSK

l

In the case of the IFH1 board on the OptiX RTN 605 1F/2F, Radio Work Mode cannot be specified manually.

l

Set this parameter according to the service planning information. The radio working modes of the IF boards at both ends of the radio link must be the same.

l

As the identifier of a radio link, this parameter is used to prevent misconnection of radio links between sites.

l

If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream.

l

Set this parameter according to the service planning information. Each radio link of an NE must have a unique link ID, and the link IDs at both ends of a radio link must be the same.

l

IF port inloop indicates that loopback occurs in the IF signals to be transmitted to the opposite end.

l

IF port outloop indicates that loopback occurs in the IF signals to be received.

l

This parameter generally takes the default value.

6)32M,14MHz, 16QAM

19)10M,3.5MHz, 16QAM 20)20M,7MHz, 16QAM 21)40M, 28MHz,QPSK 22)40M,14MHz, 16QAM 23)64M,28MHz, 16QAM 24)80M,28MHz, 16QAM Radio Link ID

IF Port Loopbacka

1 to 4094

-

Non-Loopback

Non-Loopback

Inloop Outloop

Issue 03 (2010-05-30)


A-45


A Supporting Task

Parameter

Value Range

Default Value

Description

Consecutive Wave Status

Stop

-

This parameter displays or specifies the status of transmitting the carrier signals from the IF interface.

Start

This parameter can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, services are interrupted.

NOTE

a: The ATPC attributes must be set to the same values at both ends of a radio link.

A.5.6 Setting Parameters of ODU Interfaces This section describes how to set parameters of an ODU interface, including the RF attributes, power attributes, and advanced attributes of the ODU.

Prerequisite l


l

The corresponding IF boards must be added.

l

The corresponding ODU must be added in the slot layout diagram.


Procedure Step 1 In the NE Explorer, select the ODU from the Object Tree and then choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Set the transmit frequency and T/R spacing.

Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Set the transmit power of the ODU.

Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. A-46


Issue 03 (2010-05-30)


A Supporting Task

Step 9 Set Configure Transmission Status.



Value Range

Default Value

Description

Transmit Frequency (MHz)

-

-

l

The parameter specifies the channel center frequency.

l

The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing.

l

The difference between the transmit frequencies of the ODUs at both ends of a radio link is a T/R spacing.

l


l

This parameter indicates the spacing between the transmit frequency and receive frequency of the ODU. If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive power.

l

If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used.

l

The T/R spacing of the ODU must be set to the same value at both ends of a radio link.

T/R Spacing (MHz)

Issue 03 (2010-05-30)

0 to 4294967.295

-


A-47


A Supporting Task

Parameter

Value Range

Default Value

Description

Maximum Transmit Power (dBm)

-

-

l


l

This parameter specifies the upper threshold of the transmit power range of an ODU. After an ATPC adjustment, the transmit power cannot exceed the value of this parameter.

l


l


l

The transmit power of the ODU must be set to the same value at both ends of a radio link.

l


l

This parameter specifies the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna nonalignment indication function.

l

When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is 3 dB or more beyond the preset receive power, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on and 300 ms off), indicating that the antennas are not aligned.

l

After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna nonalignment indication function.

l


Transmit Power (dBm)

Receive Power (dBm)

A-48

-

-

-

-


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Configure Transmission Status

mute

unmute

l

When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive radio signals.

l

When Transmission Status is set to unmute, the ODU normally transmits and receives radio signals.

l

This parameter generally takes the default value.

unmute

A.5.7 Querying ATPC Adjustment Records By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function.

Prerequisite l


l

The corresponding IF boards must be added.

l

The corresponding ODU must be added in the slot layout diagram.


Procedure Step 1 In the NE Explorer, select the ODU from the Object Tree and then choose Configuration > ATPC Adjustment Record from the Function Tree. Step 2 Click Query. Then, the running information of the ATPC function is returned. ----End

A.5.8 Querying History Transmit Power and Receive Power Checking the change trend of the history transmit power and receive power provides reference for radio link troubleshooting.




A-49


A Supporting Task

Procedure Step 1 In the NE Explorer, select the ODU for which the history transmit power and receive power need be queried from the Object Tree, and choose Configuration > Performance Graph Analyse from the Function Tree. Step 2 Specify the start time and end time of a specific time span. The time span starts from the last routine maintenance time to the current time. Step 3 Set Counter Type to 15M. Step 4 Click Drawing. The history transmit and receive power curve of the ODU in the specified time span is displayed. Step 5 Analyze the power curve. If the receive power fading of two adjacent points exceeds 20 dB, but the weather does not change, contact the troubleshooting engineers. ----End

A.5.9 Querying the AM Status By querying the AM status, you can trace the change of the modulation mode when the AM function is used.



Related Information The AM working state can be queried only when the OptiX RTN 605 1F/2F is configured with Hybrid radio services.

Procedure Step 1 Choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Select the corresponding IFH1 board in the Hybrid/AM Configuration tab page. Step 3 Click Query. The current modulation modes of the transmit end and the receive end of the IFH1 board are displayed. ----End

A.5.10 Querying the IF 1+1 Protection Status You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status. A-50


Issue 03 (2010-05-30)


A Supporting Task

Prerequisite l


l

The 1+1 protection group must be configured.


Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Select the ID of the protection group to be queried under Protection Group. Step 4 Click Query. Check the working status of the IF 1+1 protection group in the Slot Mapping Relation area. ----End

A.5.11 Performing IF 1+1 Protection Switching You can perform an external switching on an IF 1+1 protection group by performing an IF 1+1 protection switching.

Prerequisite l


l

An IF 1+1 protection group must be configured.


Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click the selected unit and select the required switching mode from the shortcut menu. A dialog box is displayed, prompting you whether to perform the switching. Step 4 Click Yes. A dialog box is displayed, indicating that the operation is successful. Step 5 Click OK. Step 6 Click Query. ----End Issue 03 (2010-05-30)


A-51


A Supporting Task

A.6 Configuring the Monitored Status of E1 Interfaces This section describes how to set whether to monitor service alarms of E1 interfaces, which do not affect transmission of E1 services.



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Select the used E1 interfaces.


A-52


Issue 03 (2010-05-30)


A Supporting Task


Value Range

Default Value

Description

E1-1 to E1-n ("n" indicates the number of E1 interfaces that are used.)

Selected

Selected

l

An E1 port corresponds to a radio E1 timeslot, that is, E1-1 corresponds to the first E1 timeslot in the radio and E1-2 corresponds to the second E1 timeslot. Hence, if the radio capacity is 2xE1, 5xE1, or 10xE1, only the services over the first two E1 interfaces, the first five E1 interfaces, or the first ten E1 interfaces are transmitted over radio.

l

The system does not monitor the E1 services over the interfaces that are not selected. The E1 services, however, are still transmitted over radio.

l

Set the parameters according to the working mode of the radio link and the used E1 interface.

l

In the case of the OptiX RTN 605 1F/2F, you can set the number of E1 interfaces to be the same as E1 Capacity.

Not selected

A.7 Managing Clocks To ensure clock synchronization between transmission nodes on a transport network, you need to manage the NE clocks. A.7.1 Configuring Clock Sources of the OptiX RTN 605 1E/2E When the OptiX RTN 605 1E/2E needs to trace the synchronous Ethernet clock, you need to adjust the priorities of the clock sources. A.7.2 Configuring the Ethernet Clock Source of the OptiX RTN 605 1F/2F The OptiX RTN 605 1F/2F supports the synchronous Ethernet function. You can select the Ethernet clock source as the timing synchronization signal for the OptiX RTN 605 1F/2F. A.7.3 Querying the Current NE Clock Source This section describes how to check the current clock reference signal that the NE traces.

A.7.1 Configuring Clock Sources of the OptiX RTN 605 1E/2E When the OptiX RTN 605 1E/2E needs to trace the synchronous Ethernet clock, you need to adjust the priorities of the clock sources.

Prerequisite The NE user must have the authority of Operation Level or higher. Issue 03 (2010-05-30)


A-53


A Supporting Task


Context In the case of the OptiX RTN 605 1E/2E, the default priority levels of clock sources are Um interface Clock Source > Ethernet Clock Source1 > Ethernet Clock Source2 > Internal Clock Source. When the OptiX RTN 605 1E/2E needs to trace the synchronous Ethernet clock, you need to adjust the priority level of Ethernet Clock Source1 and/or Ethernet Clock Source2.

Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock Source Priority from the Function Tree. or to adjust the priority of a clock source. Step 2 Select a clock source and click The clock priorities levels are arranged in a descending order from the first row to the last row. The internal clock source is always of the lowest priority. Step 3 Click Apply. ----End

Parameter Description Parameter

Value Range

Default Value

Description

Clock Source

-

-

l

Um interface Clock Source indicates the microwave clock source.

l

Ethernet Clock Source1 indicates the synchronous Ethernet clock source of the GE1 port.

l

Ethernet Clock Source2 indicates the synchronous Ethernet clock source of the GE2 port.

l

The Internal Clock Source is always of the lowest priority and indicates that the NE works in the free-run mode.

l

Determine the clock sources and the corresponding clock source priority levels according to the clock synchronization scheme.

A.7.2 Configuring the Ethernet Clock Source of the OptiX RTN 605 1F/2F The OptiX RTN 605 1F/2F supports the synchronous Ethernet function. You can select the Ethernet clock source as the timing synchronization signal for the OptiX RTN 605 1F/2F. A-54


Issue 03 (2010-05-30)


A Supporting Task



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock Source Priority from the Function Tree. Step 2 Set Use the clock source of the data port. Step 3 Click Apply. ----End

Parameter Description Parameter

Value Range

Default Value

Description

Use the clock source of the data port

Yes

No

When this parameter is set to Yes, the OptiX RTN 605 1F/2F traces the clock source that is recovered from the signal flow on the Ethernet PORT.

No

A.7.3 Querying the Current NE Clock Source This section describes how to check the current clock reference signal that the NE traces.



Procedure Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock Source Priority from the Function Tree. Step 2 Click Query. Step 3 Check Synchronous Source of the NE. Issue 03 (2010-05-30)


A-55



On a radio link hop, one NE traces an internal clock source or the synchronous Ethernet clock and the other NE traces the radio clock source.

----End

A.8 Managing the STP If a loop exists in the network topology of Ethernet services, you need to enable the Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP). A.8.1 Configuring the Spanning Tree Protocol In the case of the Layer 2 switching service, if a loop is formed, you need to enable the STP or RSTP for the bridge and set bridge parameters and port parameters. A.8.2 Setting the Parameters of Spanning Tree Protocol If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment. A.8.3 Querying the Running Information About the Spanning Tree Protocol The running information about the STP includes the bridge running information and port running information.

A.8.1 Configuring the Spanning Tree Protocol In the case of the Layer 2 switching service, if a loop is formed, you need to enable the STP or RSTP for the bridge and set bridge parameters and port parameters.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created.


Precautions The Ethernet switching board supported by the OptiX RTN 605 1E/2E is the EM4T (a logical board).

Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Enable the protocol. 1. A-56

Click the Protocol Enable tab. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


A Supporting Task

2.

Set the parameters of the enabled protocol.

3.

Click Apply.

----End


Value Range

Default Value

Description

VB

-

-

Indicates the created bridge.

Protocol Enabled

Enable

Disabled

l

Indicates whether to enable the STP.

l

In the service networking process, it is recommended that you prevent a loop from forming in the case of the Layer 2 switching service and thus avoid enabling the STP or RSTP.

l

If a loop is already formed in the service networking process, you must enable the STP or RSTP.

l

This parameter is valid only when Protocol Enabled is set to Enabled.

l

The protocol type is set according to the requirement of the interconnected Ethernet equipment. In normal cases, it is recommended that you use the default value.

Disabled

STP

Protocol Type

RSTP

RSTP

NOTE

l


l

Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the relevant parameters as instructed, before enabling the STP or RSTP.

A.8.2 Setting the Parameters of Spanning Tree Protocol If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created. Issue 03 (2010-05-30)


A-57


A Supporting Task



Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Set bridge parameters. 1.

Click the Bridge Parameter tab.

2.

Set bridge parameters.

3.

Click Apply.

Step 3 Set port parameters. 1.

Click the Port Parameter tab.

2.

Set port parameters.

3.

Click Apply.

Step 4 Optional: To enable the RSTP, specify the point-to-point attribute of the Ethernet port. 1.

Click the Point to Point Attribute tab.

2.

Set the point-to-point attributes of the port.

3.

Click Apply.

----End

A-58


Issue 03 (2010-05-30)


A Supporting Task


Value Range

Default Value

Description

Priority (Bridge Parameter)

0 to 61440

32768

l

The most significant 16 bits of the bridge ID indicate the priority of the bridge.

l

When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge.

l

If the priorities of all the bridges on the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.

l

Indicates the maximum age of the CBPDU packet that is recorded by the port.

l

The greater the value, the longer the transmission distance of the CBPDU, which indicates that the network diameter is greater. When the value of this parameter is greater, it is less possible that the bridge detects the link fault immediately and thus the network adaptability is reduced.

l

Indicates the interval for transmitting the CBPDU packets through the bridge.

l

The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.

l

Indicates the holding time of a port in the listening state and in the learning state.

l

The greater the value, the longer the delay of the network state change. Hence, the topology changes are slower and recovery in the case of faults is slower.

Max Age(s)

Hello Time(s)

Forward Delay(s)

6 to 40

1 to 10

4 to 30

20

2

15

TxHoldCount (per second)

1 to 10

6

Indicates the number of times the port transmits the CBPDU in every second.

Priority (Port Parameters)

0 to 240

128

l

The most significant eight bits of the port ID indicate the port priority.

l

When the value is smaller, the priority is higher.

Issue 03 (2010-05-30)


A-59


A Supporting Task

Parameter

Value Range

Default Value

Description

Port Path Cost

1 to 200000000

19

l

Indicates the status of the network that the port is connected to.

l

In the case of the bridges on both ends of the path, set this parameter to the same value.

l

This parameter is valid for the RSTP only.

l

This parameter indicates whether to set the port as an edge port. The edge port refers to the bridge port that is connected only to the LAN. The edge port receives the BPDU but does not transmit the BPDU.

l

You can set this parameter to Enabled only when the Ethernet port on the Ethernet board is connected directly to a data communications terminal, such as a computer. In other cases, it is recommended that you use the default value.

l

Indicates whether the STP/RSTP is enabled for the port.

l

If you set this parameter to Disabled, the BPDU cannot be processed or transmitted.

l

It is recommended that you use the default value.

l

This parameter is valid only when Admin Edge Attribute is set to Enabled.

l

When you set this parameter to Enabled, the RSTP considers this port as a non-edge port if the bridge detects that this port is connected to a port of another bridge.

l

If you set Admin Edge Attribute to Enabled, you need to set this parameter to Enabled. In other cases, it is recommended that you use the default value.

Admin Edge Attribute

Protocol Enabled

Enabled

Disabled

Disabled

Enabled

Enabled

Disabled

Auto Edge Detection

A-60

Enabled

Disabled

Disabled


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Point-to-Point Attribute

Adaptive connection

Adaptive connection

l

This parameter is valid only when the RSTP is used.

l

If you set this parameter to Adaptive connection, the bridge determines the actual point-to-point attribute of the port according to the actual working mode of the port. If the actual working mode is full-duplex, the actual point-to-point attribute is "true". If the actual working mode is half-duplex, the actual point-topoint attribute is "false".

l

If you set this parameter to Link connection, the actual point-to-point attribute of the port is "true".

l

If you set this parameter to Shared media, the actual point-to-point attribute of the port is "false".

l

Only the port whose actual point to point attribute is "true" can transmit the fast transition request and response messages.

l


Link connection Shared media

NOTE

l


l

Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the relevant parameters as instructed, before enabling the STP or RSTP.

A.8.3 Querying the Running Information About the Spanning Tree Protocol The running information about the STP includes the bridge running information and port running information.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet LAN services must be created. The STP or RSTP of the bridge must be enabled.

Issue 03 (2010-05-30)


A-61


A Supporting Task



Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Query the bridge running information. 1.

Click the Bridge Running Info tab.

2.

Click Query.

3.

View the bridge running information.

Step 3 Query the port running information. 1.

Click the Port Running Info tab.

2.

Click Query.

3.

View the port running information.

----End

A.9 Managing LAGs Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved. A.9.1 Creating a LAG To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG. A.9.2 Setting the Port Priority In a LAG that uses the static aggregation mode, a port with higher priority is preferred to transmit services. A.9.3 Querying the Protocol Information of the LAG This section describes how to learn about the running information of the LACP protocol used by LAGs.

A.9.1 Creating a LAG To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG.

Prerequisite l

A-62

The NE user must have the authority of Operation Level or higher. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


A Supporting Task l

The physical network topology must be established.

l

The corresponding Ethernet switching board must be added to the Slot Layout.


Precautions The OptiX RTN 605 1E/2E supports LAGs. The OptiX RTN 605 1F/2F supports LAGs.

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New. Then, the Create Link Aggregation Group dialog box is displayed. Step 4 Set the parameters of the LAG.

Step 5 Click OK. ----End Issue 03 (2010-05-30)


A-63


A Supporting Task


Value Range

Default Value

Description

LAG No.

-

-

This parameter specifies the LAG number.

LAG Name

-

-

This parameter specifies the LAG name.

LAG Type

Static

Static

l

Static: To add or delete a member port of a LAG, you need to enable the Link Aggregation Control Protocol (LACP) protocol. In a LAG, a port may be in Selected or Standby state. The aggregation information is exchanged among different equipment through the LACP protocol to ensure that the aggregation information is the same among all the nodes.

l

Manual: To add or delete a member port of a LAG, you need not enable the LACP protocol. The port may be in UP or DOWN state. Determine whether to perform aggregation according to the port status.

Manual

A-64


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Load Sharing

Sharing

Sharing

l

Sharing: Each member link of a LAG processes traffic at the same time and shares the traffic load. The sharing mode increases bandwidth utilization of the link. When the LAG members change, or certain links fail, the system automatically reallocates the traffic.

l

Non-Sharing: Only one member link of a LAG carries traffic, and the other links is in standby state. In this case, a hot backup mechanism is provided. When the active link of a LAG is faulty, the system activates the standby link, thus preventing against a link failure.

Non-Sharing

Issue 03 (2010-05-30)


A-65


A Supporting Task

A-66

Parameter

Value Range

Default Value

Description

Main Port

-

-

l

This parameter specifies the main port in a LAG.

l

In the case of a LAG that is created for IF 1+1 protection, you need to set Main Port to the port that is interconnected with the main IF board IFH2.

l

In other cases, set this parameter according to the configuration on the opposite equipment.

l

After creating a LAG, you can add Ethernet services to the main port only and cannot add services to a slave port.

l

When Load Sharing is set to Non-Sharing, all services are transmitted on the link to which the main port is connected. The links to which other slave ports are connected function as protection links.


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Available Slave Ports

-

-

l

This parameter specifies the slave ports in a LAG. A LAG is manually created rather than being automatically created by the system. A LAG contains a main port and slave ports. The slave ports in a LAG are fixed. The system does not automatically add or remove slave port of a LAG. If required, you need to change slave ports of a LAG manually.

l

In other cases, set this parameter according to the configuration on the opposite equipment.

Selected Slave Ports

-

-

This parameter displays the ports that are already selected as slave ports of a LAG.

A.9.2 Setting the Port Priority In a LAG that uses the static aggregation mode, a port with higher priority is preferred to transmit services.

Prerequisite l


l




A-67


A Supporting Task

Precautions The OptiX RTN 605 1E/2E/1F/2F supports port priorities.

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Parameters tab. Step 3 Set the parameters about the port priority.

NOTE

l

A port ID consists of Port and Port Priority. The port that has the smaller ID in a LAG is aggregated first.

l

A system ID consists of System Parameter Settings and System MAC Address. When the system negotiates with the remote system, the system with the smaller ID can first select the ports to be aggregated. In this example, the system refers to the board, and the system MAC address refers to the MAC address of the board. The factory-set MAC address is globally unique and cannot be modified.

----End

Parameters

A-68

Parameter

Value Range

Default Value

Description

Port

-

-

This parameter displays the port whose priority can be set.


Issue 03 (2010-05-30)


Issue 03 (2010-05-30)

A Supporting Task

Parameter

Value Range

Default Value

Description

Port Priority

0 to 65535 (step: 1)

32768

l

This parameter is valid only when LAG Type is set to Static.

l

This parameter indicates the priorities of the ports in a LAG as defined in the LACP protocol. The smaller the value, the higher the priority.

l

When ports are added into a LAG, the port of the highest priority is preferred for service transmission.


A-69


A Supporting Task

Parameter

Value Range

Default Value

Description

System Priority

0 to 65535 (step: 1)

32768

l

This parameter is valid only when LAG Type is set to Static.

l

This parameter indicates the priority of a LAG. The smaller the value, the higher the priority.

l

When a local LAG negotiates with an opposite LAG through LACP packets, both LAGs can obtain the system priorities of each other. Then, the computation result based on the logic that is selected by the LAG with the higher system priority is considered as the result of both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the computation result based on the logic that is selected by the LAG with lower system MAC address is considered as the result of both LAGs.

System MAC Address

A-70

-

-


This parameter displays the system MAC address.

Issue 03 (2010-05-30)


A Supporting Task

A.9.3 Querying the Protocol Information of the LAG This section describes how to learn about the running information of the LACP protocol used by LAGs.



Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click Query. Step 4 In the main interface, select the LAG to be queried. Right-click the LAG and choose an option from the dropdown list. A dialog box is displayed, indicating the query result. ----End

A.10 Managing the QoS By managing the QoS, you can provide differentiated services for different service types. A.10.1 Creating a Flow In the case of an Ethernet switching board, a flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations. A.10.2 Creating the CAR CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network. A.10.3 Creating the CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. A.10.4 Binding the CAR/CoS To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS. A.10.5 Configuring the Queue Scheduling Mode Issue 03 (2010-05-30)


A-71


A Supporting Task

The OptiX RTN 605 1F/2F and 1E/2E respectively supports the setting of the board-level queue scheduling mode of the EMS4 (a logic board) and EM4T (a logic board).

A.10.1 Creating a Flow In the case of an Ethernet switching board, a flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations.

Prerequisite The NE user must have the authority of Operation Level or higher. The associated Ethernet services must be created.


Precautions The Ethernet switching board supported by the OptiX RTN 605 1F/2F is the EMS4 (a logical board). The Ethernet switching board supported by the OptiX RTN 605 1E/2E is the EM4T (a logical board).

Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. Step 3 Click New. The New Flow dialog box is displayed. Step 4 Set the flow parameters.

Step 5 Click OK. ----End A-72


Issue 03 (2010-05-30)


A Supporting Task


Value Range

Default Value

Description

Flow Type

Port Flow

Port Flow

Port flow: The packets from a certain port are classified as a type of flow. The Ethernet service associated with this flow type is the Ethernet private line service or Layer 2 switching service that uses this port as the service source.

Port

In the case of the EMS4 board: PORT1-PORT4

PORT1

l

When the associated service is the private line service, set this parameter to the source port or sink port of the associated Ethernet service.

l

When the associated service is the Layer 2 switching service, set this parameter to a mounted port of the bridge.

In the case of the EM4T board: PORT1-PORT4

Postrequisite After creating a flow, bind it to the corresponding CAR or CoS operation as required.

A.10.2 Creating the CAR CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network.




Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Issue 03 (2010-05-30)


A-73


A Supporting Task

Step 2 Click the CAR Configuration tab. Step 3 Click New. The New CAR dialog box is displayed. Step 4 Set the CAR parameters.



Value Range

Default Value

Description

CAR ID

In the case of the EMS4 board: 1-1024

-

Identifies a CAR operation. This parameter is used to bind a flow to an associated CAR operation. In the case of the EMS4 board, only eight CARs can be created.

In the case of the EM4T board: 1-1024 Enabled/Disabled

Enable

In the case of the EMS4 and EM4T boards, only five CARs can be created. Disabled

Indicates whether to enable the CAR operation performed on the flow bound to the CAR.

0

l

Indicates the CIR. When the rate of the packets is not more than the CIR, these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion.

l

The value of this parameter cannot be more than the PIR.

Disabled Committed Information Rate (kbit/s)

FE: an integer ranging from 0 to 100032, in the increments of 64 GE: an integer ranging from 0 to 1048576, in the increments of 64

A-74


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Committed Burst Size (kbyte)a

0: This parameter cannot be set in the case of the EMS4 board.

0

Indicates the CBS. When the rate of the packets that pass the restriction of the CAR is not more than the CIR in a certain period, certain packets can burst and can pass the restriction of the CAR. These packets can be forwarded first even in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. Note that the CBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the CBS is determined by the CIR. The greater the CIR, the greater the CBS.

0

l

Indicates the PIR. When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When the rate of the packets is more than the CIR but is not more than the PIR, the packets whose rate is more than the CIR can pass the restriction of the CAR and are marked yellow, which enables these packets to be discarded first in the case of network congestion.

l

The value of this parameter is not more than the bandwidth at the port.

0: This parameter cannot be set in the case of the EM4T board.

FE: an integer ranging from 0 to 100032, in the increments of 64

Peak Information Rate (kbit/s)a

FE: an integer ranging from 0 to 1048576, in the increments of 64

0: This parameter cannot be set in the case of the EMS4 board.

Maximum Burst Size (kbyte)a

0: This parameter cannot be set in the case of the EM4T board.

0

Indicates the MBS. When the rate of the packets that pass the restriction of the CAR is more than the CIR but is not more than the PIR, certain packets can burst and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The maximum traffic of the burst packets is determined by the specified MBS. Note that the MBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the MBS is determined by the PIR. The greater the PIR, the greater the MBS.

NOTE

a. In the case of the OptiX RTN 605 1F/2F/1E/2E, the CIR must be the same as the PIR, and the CBS and MBS cannot be set.

Postrequisite After creating the CAR, bind the flow to the corresponding CAR operation as required. Issue 03 (2010-05-30)


A-75


A Supporting Task

A.10.3 Creating the CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements.




Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CoS Configuration tab. Step 3 Click New. The New CoS dialog box is displayed. Step 4 Set the CoS parameters.

A-76


Issue 03 (2010-05-30)


A Supporting Task



Value Range

Default Value

Description

CoS ID

1-65535

1

Identifies a CoS operation. This parameter is used to bind a flow to an associated CoS operation. In the case of the EMS4 and EM4T boards, only one CoS can be created. When the CoS is bound, this CoS operation is valid for all the ports on the board.

CoS Type

Issue 03 (2010-05-30)

l

VLAN priority

l

DSCP

-

l

If you set the CoS type of a flow to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets.

l

If you set the CoS type of a flow to DSCP, the packets in this flow are scheduled to specified egress queues according to differentiated services code point (DSCP) in the IPv6 tags of these packets.


A-77


A Supporting Task

Parameter

Value Range

Default Value

Description

CoS Priority

0-3

0

Specifies a queue to which a packet is scheduled. l

In the case of the EMS4 and EM4T boards, each Ethernet port supports four egress port queues. Queues 1-4 respectively correspond to the CoS priority of 0, 1, 2, and 3.

l

When the SP algorithm is used, queue 4 (with the CoS priority of 3) is of the highest priority, and queue 1 (with the CoS priority of 0) is of the lowest priority.

l

When the WRR algorithm is used, the weighted proportion of the queues whose CoS priorities are from 0 to 3 is 1:2:4:8.

Postrequisite After creating the CoS, bind the flow to the corresponding CoS operation as required.

A.10.4 Binding the CAR/CoS To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS.

Prerequisite The NE user must have the authority of Operation Level or higher. The flow and CAR/CoS must be created.



Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. A-78


Issue 03 (2010-05-30)


A Supporting Task

Step 3 Bind the CAR/CoS.



Value Range

Default Value

Description

Bound CAR

-

-

Indicates the CAR ID that corresponds to a CAR operation. Different CAR IDs are bound to different flows, even though the parameters of the CAR operations are the same.

Bound CoS

-

-

Indicates the CoS ID that corresponds to a CoS operation. In the case of the EMS4 and EM4T boards, only one CoS can be created. When the CoS is bound, this CoS operation is valid for all the ports on the board.

A.10.5 Configuring the Queue Scheduling Mode The OptiX RTN 605 1F/2F and 1E/2E respectively supports the setting of the board-level queue scheduling mode of the EMS4 (a logic board) and EM4T (a logic board).




Issue 03 (2010-05-30)


A-79


A Supporting Task

Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 Select Queue Scheduling Mode.



Value Range

Default Value

Description


SP

SP

l

The board-level queue scheduling mode uniformly takes effect on all the Ethernet ports on the EMS4/EM4T.

l

If you set this parameter to SP, the EMS4 or EM4T adopts the SP algorithm to perform scheduling on the queues of each egress Ethernet port on the board. Queue 4 (with the CoS priority of 3) is of the highest priority, and queue 1 (with the CoS priority of 0) is of the lowest priority.

l

If you set this parameter to WRR, the EMS4 or EM4T adopts the WRR algorithm to perform scheduling on the queues of each egress Ethernet port on the board. The weight of queues 1-4 (with the CoS priorities of 0-3) is in the proportion of 1:2:4:8. According to the fixed weight value, you can allocate the time slice to each WRR queue. Then, the port transmits the packets in the corresponding WRR queue in each time slice. If a WRR queue in a time slice does not contain any packets, the WRR queue removes this time slice and then transmits the packets in the corresponding WRR queue in the next time slice.

WRR

A.11 Using the IEEE 802.1ag OAM By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.11.1 Creating MDs A-80


Issue 03 (2010-05-30)


A Supporting Task

A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users. A.11.2 Creating MAs A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation. A.11.3 Creating MPs The functions of the IEEE 802.1ag OAM can be used only after MPs are created. A.11.4 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is faulty after the CC test is started at the source end, the sink equipment reports the EX_ETHOAM_CC_LOS (Huawei MP) or ETH_CFM_LOS (Standard MP) alarm. A.11.5 Performing an LB Check During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MEP in the same traffic flow. A.11.6 Performing a Link Trace Check Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test. A.11.7 Activating the AIS After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault. A.11.8 Performing a Ping Test By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time. A.11.9 Performing Performance Detection After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services.

A.11.1 Creating MDs A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users.

Prerequisite l


l

The board for creating the MDs has been installed.

l

Ethernet services have been created.


Issue 03 (2010-05-30)


A-81


A Supporting Task

Procedure Step 1 In the NE Explorer, select the relevant board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Free. Step 2 In the right-hand pane, click OAM Configuration to display the OAM Configuration dialog box.

NOTE

In this user interface, you can maintain or delete OAM MDs.

Step 3 Click New, and then select Create MD from the drop-down list. Step 4 In the Create MD dialog box that is displayed, set the corresponding parameters.


Example Table A-20 Parameters Field

Value

Default

Description


For example: MD1

-

Displays or sets the MD name.


For example: MA1

-

Displays or sets the maintenance association name.

A-82


Issue 03 (2010-05-30)


A Supporting Task

Field

Value

Default

Description

Maintenance Domain Level

Consumer High(7)

Operator Low(0)

Displays or sets the maintenance domain level. The greater the value, the higher the priority.

Operator Low(0)

The priority of the MP is the priority of the MD. The greater the value, the higher the priority.

Consumer Middle(6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0)

Maintenance Level

Consumer High(7) Consumer Middle(6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0)

A.11.2 Creating MAs A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation.

Prerequisite l


l

The MD has been created.


Procedure Step 1 In the NE Explorer, select the relevant board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Free. Step 2 In the right-hand pane, click OAM Configuration to display the OAM Configuration dialog box. NOTE

In this user interface, you can create or delete OAM MAs.

Step 3 Click New, and then select Create MA from the drop-down list. Issue 03 (2010-05-30)


A-83


A Supporting Task

Step 4 In the Create MA dialog box that is displayed, set the corresponding parameters.



Value

Default

Description


For example: MD1

-

Displays the maintenance domain name.


For example: MA1

-

Sets the maintenance association name. MA is a domain related to a service. Through MA division, the connectivity check (CC) can be performed on the network that transmits a service instance.

A.11.3 Creating MPs The functions of the IEEE 802.1ag OAM can be used only after MPs are created.

Prerequisite l


l

The Ethernet service has been created and activated.

l

The MD and MA have been created before you create the standard MP.

Tools, Equipment, and Materials Web LCT A-84


Issue 03 (2010-05-30)


A Supporting Task

Precautions In an OAM test, all maintenance points that are involved in the operation of the same service flow must be in the same maintenance domain. In an existing maintenance domain involved in the same service flow, creating a maintenance point of the same level or a higher level may damage the existing maintenance domain. As a result, the OAM test fails.

Procedure Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Click New to displayed the Create MP dialog box. Set the relevant parameters in the dialog box.

NOTE

Note: l

VLAN ID: Leave this field blank for PORT services. For PORT+VLAN services, set this parameter for the services to be monitored.

l

Service Direction: Only MEPs have the directions. Set the direction in which the packets are transmitted to the port as the Ingress direction, and set the direction in which the packets are transmitted from the port as the Egress direction. The direction of the MIPs can be only bidirectional.

Step 3 Optional: Click Advanced. In the dialog box that is displayed, click Advanced. NOTE

If an MEP is created, you can choose whether to perform the following configuration. l

Activate the CC and configure the sending period of the CC test.

l

Set the timeout time for the LB or LT test.


Issue 03 (2010-05-30)


A-85


A Supporting Task


Value

Default

Description


For example: MD1

NULL

Displays the MD of the MP.


For example: MA1

Node

slot-board-port

-

Selects the port where you want to create an MP.

VLAN ID

1-4095

-

Configures the ID of the VLAN to which the service of the MP belongs. The information is contained in the OAM data packet. The MPs with the same VLAN ID in an MD can communicate with each other.

MP ID

Standard MP: 00-00-0000 to FFFF-1FFF

-

Uniquely identifies an MP. The bytes from higher bits to lower bits are respectively described here. The first byte indicates the network number. The second byte indicates the number of the node in the local network. The third and forth bytes indicate the ID of the MP on the network node. The MP ID must be unique in the entire network.

MEP

Specifies the MP type defined in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for Maintenance association Intermediate Point.

-

l

Specifies the direction of the MEP.

l

Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates the direction in which the packets are transmitted from the port.

NOTE An MD is not required for a non-standard MP. For the creation of a non-standard MP, select NULL.

NULL

NOTE An MA is not required for a non-standard MP. For the creation of a non-standard MP, select NULL.

Non-standard MP: 00-00-0000 to FFFF-FF00

Type

MEP MIP

Direction

Ingress Egress

CC Status

Activate

Inactivate

Specifies whether to activate the connectivity check (CC) function at an MP.

5000

Displays the timeout duration in the LB test.

Inactivate LB Timeout(ms)

A-86

Displays the MA of the created MP.

3000-60000, in increments of 100


Issue 03 (2010-05-30)


A Supporting Task

Field

Value

Default

Description

LT Timeout(ms)

3000-60000, in increments of 100

5000

Sets the timeout duration of the LT test.


Standard MP:

Standard MP:

1000

1000

10000

Common MP:

Sets the time interval for sending the CCM packet at the maintenance point where the CC test is performed.

6000

5000

600000 Common MP: 1000-60000

l

If the time interval is very short, excessive service bandwidths are used.

l

If the time interval is very long, the CC test is less sensitive to the service interruption. Thus, the default value is recommended.

A.11.4 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is faulty after the CC test is started at the source end, the sink equipment reports the EX_ETHOAM_CC_LOS (Huawei MP) or ETH_CFM_LOS (Standard MP) alarm.

Prerequisite l


l

The MEP must be created.

l

Only the MEP can enable the CC test and function as the receiving and responding end in the test.


Procedure Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and then select Activate CC. TIP

l

Alternatively, you can select a node, right-click, and then choose Activate CC from the shortcut menu to start the CC test.

l

You can select a node, right-click, and then choose Inactivate CC from the shortcut menu to stop the CC test.

NOTE

Before the CC test, set an appropriate value for CCM Sending Period (ms) according to the actual requirements.

----End Issue 03 (2010-05-30)


A-87


A Supporting Task

A.11.5 Performing an LB Check During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MEP in the same traffic flow.

Prerequisite l


l

The source and sink MEPs, and MIPs in the same maintenance domain must be created.

l

Only the MEP can enable the LB check.

l

For a standard MP, the LB test must be performed based on the MAC address when the MIP functions as the receive end of the test.

l

On a standard MP, the CC function must be enabled before the LB test can be performed.


Context During the LB check, the source MEP constructs and transmits the LBM frames, and starts the timer. If the destination MP receives the LBM frames, it sends the LBR frames back to the source MEP. This indicates that the loopback is successful. If the source MEP timer times out, it indicates that the loopback fails.

Procedure Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LB. The LB Test dialog box is displayed. Step 3 Enter the ID of the LB test source MP and the ID of the sink MP. Step 4 Click Start LB. The check result is displayed. TIP

Alternatively, you can select a node, right-click, and then choose Start LB from the shortcut menu to start the LB test. NOTE

Before you perform the check, set LB Timeout(ms) to an appropriate value.

----End A-88


Issue 03 (2010-05-30)


A Supporting Task


Value

Default

Description

LB Source MP ID

For example: 00-00-0001

-

Displays the source MP of the LT test.

LB Sink MP ID


-

Displays the sink MP of the LB test.

Test Result

Succeeded

-

Displays the test result after an LB test or LT test is performed.

Unchecked

Specifies whether the test is performed based on the MAC address.

Failed Test based on the MAC Address

Checked Unchecked

NOTE You can perform the MAC address-based LB test on only standard MPs.

LB Sink MP MAC Address

For example: 00-01-00-0F-00-00

-

Displays the MAC address of the sink MP.

A.11.6 Performing a Link Trace Check Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test.

Prerequisite l


l


l

Only MEPs can initiate the LT test and work as the termination point in the test.

l

In the case of a standard MP, you must activate CC before LT check.


Context l

Issue 03 (2010-05-30)

During the LT check, the source MEP constructs and transmits LTM frames and starts the timer. All the MPs that receive the LTM frames send the LTR frame response. According to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the destination MEP.


A-89


A Supporting Task

Performing an LT check does not affect the service.

l

Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LT. The LT Test dialog box is displayed. Step 3 Enter the LT test source maintenance point ID and sink maintenance point ID. Step 4 Click Start LT and the check result is displayed. TIP

Alternatively, you can right-click a node and choose Start LT from the shortcut menu to start the LT test. NOTE

Before you perform the check, set an appropriate LT Timeout(ms) as required.

----End


Value Range

Default Value

Description

LT Source MP ID


-

This parameter displays the source maintenance point in the LT test.

LT Sink MP ID


-

This parameter displays the source maintenance point in the LT test.

Responding MP

-

-

This parameter displays the maintenance point that responds to the test.

Responding MP Type

MEP

-

This parameter displays the type of the responding maintenance point in each LT test.

MIP

A-90


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Hop Count

For example: 1

-

This parameter displays the number of hops from the maintenance source endpoint to a maintenance intermediate point, namely, That is, the number of responding intermediate points from the maintenance source point to a certain responding point.

Test Result

Succeeded

-

This parameter displays the test result after an LB test or LT test is performed.

Failed

A.11.7 Activating the AIS After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault.

Prerequisite l


l



Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored. Double-click or right-click AIS Active State and then select Active or Deactive. Step 3 Click Apply. ----End

Issue 03 (2010-05-30)


A-91


A Supporting Task


Value Range

Default Value

Description

AIS Active State

Active

Inactive

This parameter displays or specifies the AIS activation status.

7

This parameter displays or specifies the level of the MP where AIS fault messages are suppressed.

Inactive Client Layer Level

1 to 7

If Level of the MP is set to Operator High(2) and Client Layer Level to 4, this MP reports AIS packets to only the MP whose Level is Provider Low(3) or Level is higher than Consumer Low(5). NOTE Usually, if the Level of an MP is set to n, its Client Layer Level is set to n+1.

1000

AIS Period(ms)

-

60000

This parameter displays or specifies the AIS period.

A.11.8 Performing a Ping Test By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time.

Prerequisite l


l


l

You must be aware of the IP addresses of the source MP and the sink MP for the ping test.


Context The source end of the ping test obtains the IP addresses of the source MP and sink MP, and constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets or ICMP packets parses the packets, and responds to the source end. After receiving the response A-92


Issue 03 (2010-05-30)


A Supporting Task

packet, the source end reports the ping test result to the NE software (including the ratio of packet loss and time delay) based on the response packet.

Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start Ping. The Ping Test dialog box is displayed. Step 3 Select Send Mode. Then set Packet Length, Timeout, and Ping Attempts for the ping packet. Step 4 Set Destination IP Address and Local IP Address. Step 5 Click Start Ping. The check result is displayed. ----End


Value Range

Default Value

Description

Send Mode

Burst Mode

Burst Mode

This parameter displays a mode in which ping test packets are sent.

Continue Mode

Burst Mode: sending the ping test packets according to the set sending times. Continue Mode: sending the ping test packets constantly. When this mode is selected, the sending times cannot be set. Packet Length

64 to 1522 bytes

64

This parameter displays the packet length of the ping test packet.

Timeout

3 to 60 seconds

5

This parameter displays the timeout time. If the ping test packet has been sent and the source MP does not receive the returned packet from the sink MP after timeout, it indicates that the ping test fails.

Issue 03 (2010-05-30)


A-93


A Supporting Task

Parameter

Value Range

Default Value

Description

Ping Attempts

1 to 1000 attempts

1

This parameter displays the times of sending ping test packets when Send Mode is set to Burst Mode.

Destination IP Address

-

0.0.0.0

This parameter displays the IP address of the sink MP.

Local IP Address

-

0.0.0.0

This parameter displays the IP address of the source MP.

A.11.9 Performing Performance Detection After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services.

Prerequisite l


l



Context After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services. The implementation principle of the performance detection is as follows: The source MP initiates multiple LB tests, and then the MP collects information about the packet loss ratio and delay time.

Procedure Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Performance Detect. The Performance Detect dialog box is displayed. Step 3 Select Send Mode. Then set Frame Length, Timeout, and Detect Attempts for the tested packet. A-94


Issue 03 (2010-05-30)


A Supporting Task

Step 4 Set Source MP ID and Destination MP ID. Step 5 Click Start Detect. The check result is displayed. ----End


Value

Default

Description

Send Mode

Burst Mode

Burst Mode

Specifies a mode in which performance detection packets are sent.

Continue Mode

Burst Mode: sending the detection packets according to the set sending times Continue Mode: sending the detection packets constantly. When this mode is selected, the sending times cannot be set. Packet Length

64 to 1522 bytes

64

Specifies the length of a performance detection packet.

Timeout

3 to 60 seconds

5

Specifies the timeout time. If the performance detection packet has been sent and the source MP does not receive the returned packet from the sink MP after timeout, it indicates that the performance detection fails.

Detect Attempts

1-1000(Times)

1

Specifies the times of sending performance detection packets when Send Mode is set to Burst Mode.

Source MP ID

Standard MP: 00-00-0000 to FF-FF-1FFF

-

Specifies the ID of the source MP that sends detection packets.

Common MP: 00-00-0000 to FF-FF-FF00

Issue 03 (2010-05-30)


A-95


A Supporting Task

Parameter

Value

Default

Description

Destination MP ID

Standard MP: 00-00-0000 to FF-FF-1FFF

-

Specifies the ID of the sink MP involved in the performance detection.

Common MP: 00-00-0000 to FF-FF-FF00

A.12 Using the IEEE 802.3ah OAM With the IEEE 802.3ah OAM, you can maintain point-to-point Ethernet links. A.12.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is realized based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link. A.12.2 Enabling the Link Event Notification After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed. A.12.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link. A.12.4 Performing the Remote Loopback After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data. A.12.5 Enabling the Self-Loop Detection After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.

A.12.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is realized based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link.



Context The OAM auto-discovery is realized through the auto-negotiation between the local equipment and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After the OAM auto-discovery succeeds, the link performance is monitored according to the error frame threshold. You can set the error frame threshold on the NMS. A-96


Issue 03 (2010-05-30)


A Supporting Task l

The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery fails.

l

If the OAM modes of the two systems are passive modes, a fault occurs on the line, or one system fails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-discovery fails.

Procedure Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab, and then set OAM Working Mode. Select Enabled from the Enable OAM Protocol drop-down list.

Step 3 Click Apply. Step 4 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the peer end. ----End


Value

Default

Description

Port

For example: PORT1

-

Displays the port name.

Enable OAM Protocol

Enabled

Disabled

Specifies whether the point-to-point OAM protocol (IEEE 802.3ah protocol) is enabled.

Disabled

After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end.

Issue 03 (2010-05-30)


A-97


A Supporting Task

Field

Value

Default

Description

OAM Working Mode

Active

Active

IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive.

Passive

The port for which this field is set to Active can initiate the OAM connection. The port for which this field is set to Passive can only wait for the peer end to send the OAM connection request. Remote Alarm Support for Link Event

Enabled

Enabled

Specifies whether the detected link event is reported to the peer end (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold).

Unidirectional Operation

Enabled

Disabled

Displays whether the unidirectional operation is supported.

Max. OAM Packet Length (byte)

For example: 1000

-

Displays the maximum length of the OAM packets.

Loopback Status

Initiate Loopback at Local

Non-Loopback

Specifies the loopback status of a port on a board.

Disabled

Disabled

Respond Loopback of Remote Non-Loopback

A.12.2 Enabling the Link Event Notification After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed.

Prerequisite

A-98

l


l

Make sure that the OAM auto-discovery succeeds at both ends.


Issue 03 (2010-05-30)


A Supporting Task


Context When the OAM auto-discovery succeeds at both ends, the link fault detection and performance detection are automatically started. l

To report the detected link fault event to the opposite equipment, Remote Alarm Support for Link Event must be set to Enabled for the local equipment.

l

To report the detected link fault event to the opposite equipment, the following operations must be performed for the local equipment. –

Set Remote Alarm Support for Link Event to Enabled.

–

Set Error Frame Period Window (Frame) and Error Frame Monitor Threshold.

l

After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the ETHOAM_RMT_SD alarm, which is reported on the local end, by using the Web LCT. Based on 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, if the opposite equipment detects a link fault event or encounters a fault that makes the equipment fail to be restored (such as a power failure), you can query the ET_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the Web LCT. Based on the alarm, you can determine the fault type.

Procedure Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab, and then set Remote Alarm Support for Link Event to Enabled.


Issue 03 (2010-05-30)


A-99


A Supporting Task


Value

Default

Description

Port

For example: PORT1

-


Enable OAM Protocol

Enabled

Disabled


Disabled

After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end. OAM Working Mode

Active

Active

Passive

IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive. The port for which this field is set to Active can initiate the OAM connection. The port for which this field is set to Passive can only wait for the peer end to send the OAM connection request.

Remote Alarm Support for Link Event

Enabled


Enabled


For example: 1000

A-100

Enabled


Disabled


-


Disabled

Disabled


Issue 03 (2010-05-30)


A Supporting Task

Field

Value

Default

Description

Loopback Status


Non-Loopback



A.12.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link.

Prerequisite l


l

The IEEE 802.3ah OAM function must be enabled on the remote equipment. In addition, OAM auto-discovery succeeds at both ends.


Context After the OAM auto-discovery succeeds, set Error Frame Period Window (Frame) and Error Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled for the local equipment. If the local equipment detects a link event in the receive direction, it informs the opposite equipment of the link event. If the remote alarm for the link event is also supported on the opposite end, the opposite equipment can also inform the local equipment of the link event that is detected on the side of the opposite end. Therefore, the local end reports the ETHOAM_RMT_SD alarm.

Procedure Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Then, click the OAM Error Frame Monitor tab. Step 2 Select a port and set the error frame monitoring parameters.

Issue 03 (2010-05-30)


A-101


A Supporting Task



Value Range

Default Value

Description

Error Frame Monitor Window (ms)

1000 to 60000, in step of 100

-

In the specified Error Frame Monitor Window (ms), if the number of error frames exceeds the specified Error Frame Monitor Threshold (Entries) due to the link degradation, the link event alarm is reported.

Error Frame Monitor Threshold (Entries)

1 to 4294967295, in step of 1

-

This parameter specifies the threshold of monitoring error frames.

Error Frame Period Window (frame)

For an FE interface:

-

Within the specified value of Error Frame Period Window (frame), if the number of error frames on the link exceeds the preset value of Error Frame Period Threshold (frame), an alarm is reported.

14880 to 8928000, in step of 1 For a GE interface: 148800 to 89280000, in step of 1

Error Frame Period Threshold (frame)

1 to 892800000, in step of 1

-

This parameter specifies the threshold of monitoring the error frame period.

Error Frame Second Window (s)

10 to 900, in step of 1

-

If any error frame occurs in one second, this second is called an errored frame second. Within the specified value of Error Frame Second Window(s), if the number of error frames on the link exceeds the preset value of Error Frame Second Threshold (s), an alarm is reported.

A-102


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Error Frame Second Threshold (s)

1 to 900, in step of 1

-

This parameter specifies the threshold of monitoring error frame seconds.

A.12.4 Performing the Remote Loopback After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.

Prerequisite l


l

Make sure that the OAM auto-discovery succeeds.

l

For the equipment where the loopback is initiated, OAM Working Mode must be set to Active.

l

The remote equipment that responds to the loopback must support the remote loopback. In addition, the function of responding to the remote loopback must be enabled on the remote equipment.


Context l

The OptiX RTN 605 does not respond to a remote loopback.

l

If a port is capable of responding to loopbacks, it enters the Respond Loopback of Remote state and reports the loopback responding alarm when receiving the command of enabling the remote loopback function sent from the opposite OAM port. In this case, the equipment that initiates the loopback enters the loopback initiating state and reports the loopback initiating alarm.

l

After the remote loopback function is enabled, service packets except the OAMPDU are looped back at the remote end.

l

After using the remote loopback function to locate faults and test link performance, you should disable the remote loopback function at the end where the loopback is initiated and then restore the services. At this time, the alarm clears automatically.

Procedure Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Select the port that needs to initiate a loopback, and choose Enable Remote Loopback from the drop-down list of OAM. Step 3 Click Apply. ----End Issue 03 (2010-05-30)


A-103


A Supporting Task


Value

Default

Description

Port

For example: PORT1

-


Enable OAM Protocol

Enabled

Disabled


Disabled

After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end. OAM Working Mode

Active

Active

Passive

IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive. The port for which this field is set to Active can initiate the OAM connection. The port for which this field is set to Passive can only wait for the peer end to send the OAM connection request.

Remote Alarm Support for Link Event

Enabled


Enabled


For example: 1000

A-104

Enabled


Disabled


-


Disabled

Disabled


Issue 03 (2010-05-30)


A Supporting Task

Field

Value

Default

Description

Loopback Status


Non-Loopback



A.12.5 Enabling the Self-Loop Detection After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.

Prerequisite l


l

The physical Ethernet port to be detected must be enabled.


Context When the self-loop detection is enabled for an external physical port, if the self-loop situation occurs at the port, the ETHOAM_SELF_LOOP alarm is reported.

Procedure Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Configure the physical Ethernet port to be detected. 1.

Select External Port and then click the Advanced Attributes tab.

2.

Enable Loop Detection.

3.

Click Apply.

----End Issue 03 (2010-05-30)


A-105


A Supporting Task


Value Range

Default Value

Description

Port

PORTn

-

Indicates the PORT port. The letter n indicates the number of the PORT port.


Disabled

Disabled

Enables or disables broadcast packet suppression.

Broadcast Packet Suppression Threshold

10%-100%

-

When the broadcast packet suppression function is enabled, if the broadcast packet occupies a bandwidth that exceeds the overall bandwidth of the port multiplied by the suppression threshold, the broadcast packet is suppressed.

Loop Detection

Disabled

Disabled

Specifies whether to enable loop detection, which is used to check whether a loop exists on a port.

Enabled

Enabled

A.13 Using RMON Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.13.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port. A.13.2 Configuring an Alarm Group for an Ethernet Port After you configure an RMON alarm group for an Ethernet port, you can monitor the performance threshold-crossing events of the port in the long term. A.13.3 Configuring a History Control Group When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance A-106


Issue 03 (2010-05-30)


A Supporting Task

data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items. A.13.4 Browsing the Performance Data in the History Group of an Ethernet Port After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.

A.13.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port.

Prerequisite l


l

The associated boards must be added to the Slot Layout.


Procedure Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the Statistics Group tab. Step 3 Set the required parameters for the statistics group. 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


Value Range

Default Value

Description

Sampling Interval

5-150 seconds

5

This parameter specifies the period of sampling the performance data.

Display Accumulated Value

Selected

Deselected

This parameter specifies whether the displayed performance value is the increment of the register value compared with the register value at the end of the previous sampling interval or the current absolute value of the register.

Issue 03 (2010-05-30)

Deselected


A-107


A Supporting Task

A.13.2 Configuring an Alarm Group for an Ethernet Port After you configure an RMON alarm group for an Ethernet port, you can monitor the performance threshold-crossing events of the port in the long term.

Prerequisite l


l



Procedure Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the Alarm Group tab. Step 3 Set the required parameters for the alarm group. Step 4 Click Apply. ----End


Value Range

Default Value

Description

Sampling Interval (s)

5-600

10

This parameter specifies the period of sampling the performance data.

Report Mode

Report All

Report All

This parameter specifies how the performance threshold-crossing events are reported.

Report in Case of Upper ThresholdCrossing Report in Case of Lower ThresholdCrossing Upper Threshold

1-4294967295

1

This parameter specifies the upper threshold of the performance data.

Lower Threshold

0-4294967294

0

This parameter specifies the lower threshold of the performance data.

Monitor Status

Enabled

Disabled

This parameter specifies whether to monitor the object.

Disabled

A-108


Issue 03 (2010-05-30)


A Supporting Task

A.13.3 Configuring a History Control Group When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items.

Prerequisite l


l



Procedure Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Control Group tab. Step 3 Set the required parameters for the history group. Step 4 Click Apply. ----End


Value Range

Default Value

Description

History Control Group

30-Second

30-Second

This parameter specifies the period of sampling the history performance data.

30-Minute Custom Period1 Custom Period2

Sampling Interval (s)

l

300-43200 (Custom Period1)

l

900 (Custom Period1)

l

300-86400 (Custom Period2)

l

86400 (Custom Period2)

This parameter is valid only when History Control Group is set to Custom Period1 or Custom Period2. This parameter specifies the period of sampling the performance data.

Number of Items

1-50

50

This parameter specifies the number of performance data items.

Monitor Status

Enabled

Disabled

This parameter specifies whether to monitor the object.

Disabled

Issue 03 (2010-05-30)


A-109


A Supporting Task

A.13.4 Browsing the Performance Data in the History Group of an Ethernet Port After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.

Prerequisite l


l


l

The monitored objects and the corresponding history table type must be set in the History Control Group tab.


Procedure Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Group tab. Step 3 Set the required parameters for the history group. Step 4 Click Query. ----End


Value Range

Default Value

Description

History Table Type

30-Second

30-Second

This parameter specifies the period of sampling the history performance data.

30-Minute Custom Period1 Custom Period2 Start Item

1-50

1

This parameter specifies the item from which the system queries the history performance data. 1 represents the earliest item.

End Item

1-50

1

This parameter specifies the item after which the system stops querying the history performance data. The value of this parameter must not be more than the sum of Start Item plus 9.

A-110


Issue 03 (2010-05-30)


A Supporting Task

A.14 Configuring Ethernet Ports OptiX RTN 605The supported Ethernet ports include the external FE/GE ports on Ethernet boards and the internal IFUP ports. A.14.1 Configuring External Ethernet Ports When an NE uses external ports of Ethernet boards to gain access to Ethernet services, the attributes of external ports need to be configured so that external ports can work with the data communication equipment on the client side to provide normal access to Ethernet services. A.14.2 Configuring the IFUP Port of the Ethernet Board When an NE transmits Ethernet services through Hybrid radio, the attributes of the IFUP port need to be set. A.14.3 Modifying the Type Field of QinQ Frames By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to 0x8100.

A.14.1 Configuring External Ethernet Ports When an NE uses external ports of Ethernet boards to gain access to Ethernet services, the attributes of external ports need to be configured so that external ports can work with the data communication equipment on the client side to provide normal access to Ethernet services.



Precautions l

The Ethernet board supported by the OptiX RTN 605 1E/2E is the EM4T (a logical board). Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively. Ethernet ports GE1-GE2 of an EM4T board correspond to PORT3-PORT4 respectively.

l

The Ethernet board supported by the OptiX RTN 605 1F/2F is the EMS4 (a logical board). The EMS4 board does not support the setting of the network attributes. Ethernet ports FE1-FE3 of an EMS4 board correspond to PORT1-PORT3 respectively. Ethernet port GE1 of an EMS4 board correspond to PORT4 respectively.

l

The following procedures describe how to configure the external port of an EM4T board.

Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select External Port. Step 3 Set the basic attributes of the port. Issue 03 (2010-05-30)


A-111


A Supporting Task

1.

Click the Basic Attributes tab.

2.

Set the basic attributes of the port.

3.

Click Apply.

Step 4 Set the flow control mode of the port. 1.

Click the Flow Control tab.

2.

Set the flow control mode of the port.

3.

Click Apply.

Step 5 Optional: Set the TAG attributes of the port. 1.

Click the TAG Attributes tab.

2.

Set the TAG attributes of the port.

3.

Click Apply.

Step 6 Optional: Set the network attributes of the port. 1.

Click the Network Attributes tab.

2.

Set the network attributes of the port.

3.

Click Apply.

Step 7 Optional: Specifies the network attribute of a port. 1.

Click the Advanced Attributes tab.

2.

Set the advanced attributes of the port.

3.

Click Apply.

----End

A-112


Issue 03 (2010-05-30)


A Supporting Task

Example Table A-37 Parameters for the basic attributes Parameter

Value Range

Default Value

Description

Enabled/Disabled

Enabled

Disabled

l

If the port gains access to services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled.

l

If you set this parameter to Enabled for the port that does not gain access to services, an ETH_LOS alarm may be generated.

l

The Ethernet ports of different types support different working modes.

l

When the equipment at the opposite end works in the auto-negotiation mode, set the working mode of the equipment at the local end to Auto-Negotiation.

l

When the equipment at the opposite end works in full-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 1000 Full-Duplex or 1000M Full-Duplex, depending on the port rate of the equipment at the opposite end.

l

When the equipment at the opposite end works in half-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 100M Full-Duplex or set to AutoNegotiation, depending on the port rate of the equipment at the opposite end.

Disabled

Working Mode

l

In the case of PORT1-PORT3 of the EMS4 board and PORT1-PORT2 of the EM4T board: Auto-Negotiation

Auto-Negotiation

10M HalfDuplex 10M Full-Duplex 100M HalfDuplex 100M FullDuplex l

In the case of PORT4 of the EMS4 board and PORT3-PORT4 of the EM4T board: Auto-Negotiation 10M HalfDuplex 10M Full-Duplex 100M HalfDuplex 100M FullDuplex 1000M FullDuplex

Issue 03 (2010-05-30)


A-113


A Supporting Task

Parameter

Value Range

Default Value

Description


1522

1522

l

The value of this parameter is greater than the maximum length of a frame among all the data frames to be transmitted.

l

In the case of the OptiX RTN 605, set Maximum Frame Length to the same value for all the ports of the logical boards.

l

When you set this parameter to Inloop, the Ethernet physical signals to be sent to the opposite end are looped back.

l

In normal cases, it is recommended that you use the default value.

PHY LoopBack

1535

Non-Loopback

Non-Loopback

Inloop

Table A-38 Parameters for flow control Parameter

Value Range

Default Value

Description

NonAutonegotiation Flow Control Mode

Disabled

Disabled

l

This parameter is valid only when you set Working Mode to Auto-Negotiation.

l

When you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames and process the received PAUSE frames.

l

The non-autonegotiation flow control mode of the equipment at the local end must be the same as the nonautonegotiation flow control mode of the equipment at the opposite end.

l

This parameter is valid only when you set Working Mode to Auto-Negotiation.

l

When you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames and process the received PAUSE frames.

l

The auto-negotiation flow control mode of the equipment at the local end must be the same as the auto-negotiation flow control mode of the equipment at the opposite end.


A-114

Enable Symmetric Flow Control

Disabled

Disabled

Enable Symmetric Flow Control


Issue 03 (2010-05-30)


A Supporting Task

Table A-39 Parameters for the TAG attributes Parameter

Value Range

Default Value

Description

TAG

Tag Aware

Tag Aware

l

When ports are configured with TAG flags, the ports process frames by using the methods provided in Table A-42.

l

If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware.

l

If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to Access.

l

If the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.

l

This parameter is valid only when you set TAG to Access or Hybrid.

l

For details about the functions of this parameter, see Table A-42.

l

You need to set this parameter according to the actual situation.

l


l


l

When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to the actual situation. Generally, it is recommended that you use the default value.

Access Hybrid

Default VLAN ID

VLAN Priority

Issue 03 (2010-05-30)

1 to 4095

0 to 7

1

0


A-115


A Supporting Task

Table A-40 Parameters for the network attributes Parameter

Value Range

Default Value

Description

Port Attributes

UNI

UNI

l

When you set this parameter to UNI, the port processes data frames according to the tag attributes.

l

When you set this parameter to CAware, the port does not process the data frames according to the tag attributes but processes the data frames according to the method of processing QinQ services.

l

To create a QinQ-based EVPL service, set this parameter to C-Aware. To create an EPLAN/EVPLAN service, set this parameter to UNI.

l

The EMS4 board does not support the setting of network attributes.

C-Aware

Table A-41 Parameters for the advanced attributes Parameter

Value Range

Default Value

Description


Disabled

Disabled

Specifies whether to restrict the traffic of broadcast packets according to the ratio of the broadcast packets to the total packets. When a broadcast storm may occur in the equipment at the opposite end, set this parameter to Enabled.

Broadcast Packet Suppression Threshold

10% to 100%

30%

The port discards the received broadcast packets when the ratio of the received broadcast packets to the total packets exceeds the value of this parameter. The value of this parameter is greater than the ratio of the broadcast packets to the total packets when the broadcast storm does not occur. Generally, set this parameter to 30% or a greater value.

Flow Threshold (Mbps)

In the case of PORT1-PORT2: 0 to 100

In the case of PORT1-PORT2: 100

l

In the case of PORT3-PORT4: 0 to 1000

In the case of PORT3-PORT4: 1000

Specifies the threshold when the flow is zero. This parameter is valid only when you set Zero-Flow Monitor to Enabled.

l

This parameter is not applicable to the EMS4 board.

A-116

Enabled


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Zero-Flow Monitor

Disabled

Disabled

l

Specifies whether to enable the zero-flow monitoring function.

l

When this parameter is set to Enabled for a port, the traffic threshold-crossing alarm is reported if the traffic over the port is lower than the traffic threshold.

l


l

Specifies the zero-flow monitoring cycle. This parameter is valid only when you set Zero-Flow Monitor to Enabled.

l


Zero-Flow Monitor Interval (min)

Loop Detection

Enabled

0 to 30

0

Disabled

Disabled

Enabled

Specifies whether to enable loop detection, which is used to check whether a loop exists on the port.

Table A-42 Methods used by ports to process data frames Direction

Ingress

Issue 03 (2010-05-30)

Type of Data Frame

Processing Method Tag aware

Access

Hybrid

Tagged frame

The port receives the frame.

The port discards the frame.


Untagged frame


The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.



A-117


A Supporting Task

Direction

Egress

Type of Data Frame


Access

Hybrid

Tagged frame

The port transmits the frame.

The port strips the VLAN tag from the frame and then transmits the frame.

l

If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame.

l

If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.

A.14.2 Configuring the IFUP Port of the Ethernet Board When an NE transmits Ethernet services through Hybrid radio, the attributes of the IFUP port need to be set.



Precautions l

The Ethernet switching board supported by the OptiX RTN 605 1E/2E is the EM4T (a logical board).

l

The Ethernet switching board supported by the OptiX RTN 605 1F/2F is the EMS4 (a logical board).

l

IFUP ports refer to the Ethernet ports that are connected to the IF ports.

l

The following procedures describe how to configure the IFUP port of an EM4T board. The EMS4 board does not support the configuration of the network attributes.

Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select Internal Port. A-118


Issue 03 (2010-05-30)


A Supporting Task

Step 3 Set the TAG attributes. 1.

Click the TAG Attributes tab.

2.

Set the relevant attributes.

3.

Click Apply.

Step 4 Set the network attributes. 1.

Click the Network Attributes tab.

2.

Set the relevant attributes.

3.

Click Apply.

----End

Example Table A-43 Parameters for the TAG attributes Parameter

Value Range

Default Value

Description

TAG

Tag Aware

Tag Aware

l


l

If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware.

l

If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to Access.

l

If the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.

l


l


l


Hybrid Access

Default VLAN ID

Issue 03 (2010-05-30)

1 to 4095

1


A-119


A Supporting Task

Parameter

Value Range

Default Value

Description

VLAN Priority

0 to 7

0

l


l


l

When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to the actual situation. Generally, it is recommended that you use the default value.

Table A-44 Parameters for the network attributes Parameter

Value Range

Default Value

Description

Port Attributes

UNI

S-Aware

l

When you set this parameter to UNI, the port processes data frames according to the tag attributes.

l

When you set this parameter to SAware, the port does not process the data frames according to the tag attributes but processes the data frames according to the method of processing QinQ services.

l

To create a QinQ-based EVPL service, set this parameter to S-Aware. To create an EPLAN/EVPLAN service, set this parameter to UNI.

S-Aware


Ingress

A-120

Type of Data Frame


Access

Hybrid

Tagged frame



Untagged frame



If you set the TAG attribute of an IFUP port to Hybrid, the packets forwarded by the port are the same as the packets before they enter the bridge.


Issue 03 (2010-05-30)


A Supporting Task

Direction

Egress

Type of Data Frame


Access

Tagged frame

The port transmits the frame.


Hybrid

A.14.3 Modifying the Type Field of QinQ Frames By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to 0x8100.

Prerequisite l


l

The Ethernet board must be added on the Slot Layout.


Precautions In the case of the OptiX RTN 605, the Ethernet board that supports modification of the QinQ type area is the EM4T (logical board).

Procedure Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Advanced Attribute > QinQ Type Type Area Settings from the Function Tree. Step 2 Modify the type field of QinQ frames.



Value Range

Default Value

Description

QinQ Type Area (Hexadecimal)

81 00

81 00

Indicates the type field of QinQ frames. You need to set this parameter according to the type field of the accessed QinQ frames.

88 A8 91 00

Issue 03 (2010-05-30)


A-121


A Supporting Task

A.15 Configuring Ethernet Services Ethernet services are classified into EPL services, EVPL services, EPLAN services, and EPVLAN services. A.15.1 Creating Ethernet LAN Services This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services. A.15.2 Modifying the Mounted Port of a Bridge This section describes how to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port. A.15.3 Creating the VLAN Filtering Table To create an IEEE 802.1q bridge-based EPLAN service, you need to create the VLAN filtering table. A.15.4 Creating QinQ Private Line Services To enable the Ethernet switching board to transmit QinQ private line services, perform this task to configure the related information such as the service source and service sink. A.15.5 Deleting an Ethernet Private Line Service When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources. A.15.6 Creating an Ethernet LAN Service When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources.

A.15.1 Creating Ethernet LAN Services This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services.

Prerequisite l



Precautions l

The OptiX RTN 605 1E/2E supports the Ethernet switching board EM4T (logical board).

l

The OptiX RTN 605 1F/2F supports the Ethernet switching board EMS4 (logical board).

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. A-122


Issue 03 (2010-05-30)


A Supporting Task

The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the bridge according to the bridge type. l

Set the attributes of the IEEE 802.1q bridge.

l

Set the attributes of the IEEE 802.1d bridge.

Issue 03 (2010-05-30)


A-123


A Supporting Task

Step 4 Configure the mounted ports of the bridge. 1.

Click Configure Mount. The Service Mount Configuration dialog box is displayed.

2.

Select a port from the ports listed in Available Mounted Ports, and then click .

3.

A-124

Optional: Repeat step Step 4.2 to mount other ports.


Issue 03 (2010-05-30)


A Supporting Task

4.

Click OK.


Parameters Table A-46 Parameters on the main interface Parameter

Value Range

Default Value

Description

VB Name

-

-

This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge.

Bridge Type

802.1q

802.1q

l

After setting this parameter to 802.1q, create the IEEE 802.1q bridge.

l

After setting this parameter to 802.1d, create the IEEE 802.1d bridge.

l

The IEEE 802.1q bridge is preferred. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data among VLANs, you can also use the IEEE 802.1d bridge.

802.1d

Issue 03 (2010-05-30)


A-125


A Supporting Task

Parameter

Value Range

Default Value

Description


IVL/Ingress Filter Enable(802.1q)

IVL/Ingress Filter Enable(802.1q)

l

SVL/Ingress Filter Disable(802.1d)

SVL/Ingress Filter Disable(802.1d)

When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables.

l

If the ingress filter is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filter is disabled, the preceding described check is not conducted.

Table A-47 Parameters of service mounting Parameter

Value Range

Default Value

Description

Mount Port

-

-

l

Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge.

l

Set this parameter according to actual requirements.

A.15.2 Modifying the Mounted Port of a Bridge This section describes how to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port.

Prerequisite l


l

The EPLAN service must be created.


Precautions

CAUTION Modifying the ports that are mounted to the bridge may interrupt services. l

A-126

The OptiX RTN 605 1E/2E supports the Ethernet switching board EM4T (logical board). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


A Supporting Task


l

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the Service Mount tab. Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.

----End


Value Range

Default Value

Description

VB Port

1 to9600 (EMS6)

-

This parameter specifies the ID of the logical port of the bridge.

-

l

Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge.

l


1 to 5 (EM4T) Mount Port

Port Enabled

-

Enabled

Enabled

Set Port Enabled to Enabled. Otherwise, the port cannot forward the service.

Hub

l

The Spoke ports cannot access each other. The Hub port and the Spoke port can access each other. The Hub ports can access each other.

l


l


l

When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware.

l

When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access.

l

When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.

Disabled Hub/Spoke

Hub Spoke

TAG

Access

Tag Aware

Tag Aware Hybrid

Issue 03 (2010-05-30)


A-127


A Supporting Task

Parameter

Value Range

Working Mode

l

PORT1 to PORT3 on the EMS4 logical board and PORT1 to PORT2 on the EM4T logical board: Auto-Negotiation

Default Value

Description

Auto-negotiation

l

Ethernet ports of different types support different working modes.

l

When the equipment on the opposite side works in the auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation.

l

When the equipment at the opposite end works in full-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 1000 Full-Duplex or 1000M Full-Duplex depending on the port rate of the equipment at the opposite end.

l

When the equipment at the opposite end works in half-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 100M Full-Duplex, 1000M Full-Duplex, or Auto-Negotiation depending on the port rate of the equipment at the opposite end.

10M HalfDuplex 10M Full-Duplex 100M HalfDuplex 100M FullDuplex l

PORT4 on the EMS4 logical board and PORT3 to PORT4 on the EM4T logical board: Auto-Negotiation 10M HalfDuplex 10M Full-Duplex 100M HalfDuplex 100M FullDuplex 1000M FullDuplex 1000M HalfDuplex


Ingress

A-128

Type of Data Frame


Access

Hybrida

Tagged frame

Receiving

Discarding

Receiving


Issue 03 (2010-05-30)


A Supporting Task

Direction

Egress

Type of Data Frame


Access

Hybrida

Untagged frame

Discarding



Tagged frame

Transmitting


l

If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame.

l

If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.

A.15.3 Creating the VLAN Filtering Table To create an IEEE 802.1q bridge-based EPLAN service, you need to create the VLAN filtering table.

Prerequisite l


l

The EPLAN service must be created.

l

The OptiX RTN 605 1E/2E supports the Ethernet switching board EM4T (logical board).

l


Precautions

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the VLAN Filtering tab. Issue 03 (2010-05-30)


A-129


A Supporting Task

Step 3 Create a VLAN filtering table. 1.

Click New. Then, the Create VLAN dialog box is displayed.

2.

Set VLAN ID(e.g:1,3-6).

3.

Select a port from the ports listed in Available forwarding ports, and then click .

4.

Optional: Repeat step Step 3.3 to select other service forwarding ports.

5.

Click OK.

----End


Value Range

Default Value

Description

VLAN ID(e.g; 1,3-6)

1 to 4095

1

l

You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6.

l


A-130


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description


-

-

l

Packets are forwarded between the Selected forwarding ports only.

l

The ports that are in Selected forwarding ports can forward only the packet that carries the VLAN ID(e.g; 1,3-6) tag. These ports discard the packet that carries other VLAN tags.

l

The broadcast packet that is transmitted by the ports in Selected forwarding ports is broadcast only to the ports included in Selected forwarding ports.

A.15.4 Creating QinQ Private Line Services To enable the Ethernet switching board to transmit QinQ private line services, perform this task to configure the related information such as the service source and service sink.

Prerequisite l


l



Precautions The OptiX RTN 605, the Ethernet board that supports the QinQ feature is the EM4T (logical board).

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Select Display QinQ Shared Service. Step 3 Click New. The Create Ethernet Line Service dialog box is displayed. Step 4 Set the attributes of the QinQ private line service.

Issue 03 (2010-05-30)


A-131


A Supporting Task


Parameters Table A-49 Parameters on the main interface Parameter

Value Range

Default Value

Description

Service Type

EVPL (QinQ)

EVPL (QinQ)

When creating a QinQ private line service, set this parameter to EVPL(QinQ).

Direction

Bidirectional

Bidirectional

l

After setting this parameter to Unidirectional, create the service only from the service source to the service sink. That is, the service source is forwarded only to the sink port.

l

After setting this parameter to Bidirectional, create the service from the service source to the service sink and the service from the service sink to the service source. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port.

l

It is recommended that you set this parameter to Bidirectional.

l

This parameter specifies the port where the service source resides.

l

When creating the bidirectional Ethernet service from a PORT to a IFUP1, it is recommended that you use a specific PORT as the source port.

Unidirectional

Source Port

A-132

-

-


Issue 03 (2010-05-30)


A Supporting Task

Parameter

Value Range

Default Value

Description

Operation Type

Add S-VLAN

Add S-VLAN

l

For the meanings of the values, see Application of the QinQ Technology in Private Line Services.

l

Operation Type can be set to Strip SVLAN only when Direction is Unidirectional.

l


Strip S-VLAN

Source C-VLAN (e.g.1,3-6)

1 to 4095

-

In the case of the OptiX RTN 605, this parameter cannot be specified manually.

Source S-VLAN

1 to 4095

-

l

This parameter must be set to a numerical value.

l

Only the services of the source port whose S-VLAN IDs are equal to the value of this parameter work as the service source.

l

This parameter specifies the port where the service sink resides.

l

Set the value of this parameter to be different from the value of Source Port.

l

When creating the bidirectional Ethernet service from a PORT to a IFUP1, it is recommended that you use a specific IFUP1 as the sink port.

Sink Port

-

-

Sink C-VLAN(e.g. 1,3-6)

1 to 4095

-


Sink S-VLAN

1 to 4095

-

l

This parameter must be set to a numerical value.

l

Only the services of the sink port whose S-VLAN IDs are equal to the value of this parameter work as the service sink.

C-VLAN Priority

AUTO

AUTO


S-VLAN Priority

AUTO

AUTO


Priority 0 to Priority 7

Issue 03 (2010-05-30)


A-133


A Supporting Task

Table A-50 Parameters of port attributes Parameter

Value Range

Default Value

Description

Port Enabled

Enabled

-

When the source port or the sink port is set to a PORT, set Port Enabled to Enabled.

Tag Aware

l

When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware.

l

When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access.

l

When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.

Disabled TAG

Tag Aware Access Hybrid

A.15.5 Deleting an Ethernet Private Line Service When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources.

Prerequisite l


l

The Ethernet private line service must be configured and the service is not used.


Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click Query. Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete. Click OK in the dialog box that is displayed. Step 4 Click Query. At this time, the Ethernet private line service is already deleted. ----End

A.15.6 Creating an Ethernet LAN Service When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources. A-134


Issue 03 (2010-05-30)


A Supporting Task

Prerequisite l


l

The Ethernet LAN service must be configured and the service is not used.


Background Information Deleting an Ethernet LAN service involves the following tasks: 1.

Deleting the VLAN filtering table

2.

Deleting the service mounting configuration

Procedure Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click Query. Step 3 Click the VLAN Filtering tab. Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete. Click Ok in the dialog box that is displayed. Step 5 Click the Service Mount tab. Step 6 Select the Ethernet LAN service that needs to be deleted and then click Delete. Click Ok in the dialog box that is displayed. Step 7 Click Query. At this time, the Ethernet LAN service is already deleted. ----End

A.16 Managing the MAC Address Table The MAC address table is the core of the EPLAN or EVPLAN service. The OptiX RTN 605 provides various functions for managing the MAC address table. A.16.1 Creating a Static MAC Address Entry A bridge can obtain a dynamic MAC address entry by using the SVL/IVL learning mode. A unicast MAC address entry (namely, a static MAC address entry) can also be created manually, and the static MAC address entry is not aged. If a piece of equipment whose MAC address is known is connected to a port and if the equipment has heavy traffic for a long time, you can specify a static MAC address entry for the equipment. A.16.2 Creating a Blacklist Entry of a MAC Address An entry that is used for discarding data frames that contain the specified MAC addresses is called a disabled MAC address entry (also called a blacklist entry). A blacklist entry is configured by the network administrator and is not aged. Issue 03 (2010-05-30)


A-135


A Supporting Task

A.16.3 Setting the Aging Time of a MAC Address Table Entry In the case of an Ethernet switching board, the aging time of a MAC address table entry is five minutes by default. A.16.4 Querying or Deleting a Dynamic MAC Address By querying a dynamic MAC address, you can learn about all the MAC address entries that are learned by a bridge.

A.16.1 Creating a Static MAC Address Entry A bridge can obtain a dynamic MAC address entry by using the SVL/IVL learning mode. A unicast MAC address entry (namely, a static MAC address entry) can also be created manually, and the static MAC address entry is not aged. If a piece of equipment whose MAC address is known is connected to a port and if the equipment has heavy traffic for a long time, you can specify a static MAC address entry for the equipment.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet services must be created.



Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the VLAN Unicast tab. Step 3 Click New. The Create VLAN Unicast dialog box is displayed. Step 4 Set the parameters of the unicast MAC address entry.

A-136


Issue 03 (2010-05-30)


A Supporting Task



Value Range

Default Value

Description

VLAN ID

1 to 4095

-

l

In the case of IEEE 802.1d and IEEE 802.1ad bridges, this parameter is invalid if you set MAC Address Learning Mode to SVL. That is, the preset static MAC address entries are valid for all VLANs.

l

In the case of IEEE 802.1d and IEEE 802.1ad bridges, if you set MAC Address Learning Mode to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID.

l


MAC Address

-

-


Physical Port

A port that is mounted to a bridge

-

Indicates an Ethernet port that corresponds to a MAC address. You need to set this parameter according to the actual situation.

A.16.2 Creating a Blacklist Entry of a MAC Address An entry that is used for discarding data frames that contain the specified MAC addresses is called a disabled MAC address entry (also called a blacklist entry). A blacklist entry is configured by the network administrator and is not aged.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet services must be created.


Precautions The Ethernet switching board supported by the OptiX RTN 605 1F/2F is the EMS4 (a logical board). Issue 03 (2010-05-30)


A-137


A Supporting Task

The Ethernet switching board supported by the OptiX RTN 605 1E/2E is the EM4T (a logical board).

Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the Disable MAC Address tab. Step 3 Click New. The Disable MAC Address Creation dialog box is displayed. Step 4 Set the parameters of the disabled MAC address entries.



Value Range

Default Value

Description

VLAN ID

1 to 4095

-

l

In the case of IEEE 802.1d and IEEE 802.1ad bridges, this parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset static MAC address entries are valid for all VLANs.

l

In the case of IEEE 802.1d and IEEE 802.1ad bridges, if MAC Address Learning Mode is set to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID.

l


MAC Address

-

-


A.16.3 Setting the Aging Time of a MAC Address Table Entry In the case of an Ethernet switching board, the aging time of a MAC address table entry is five minutes by default. A-138


Issue 03 (2010-05-30)


A Supporting Task

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created.



Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree. Step 2 Change the aging time of the MAC address table entry. 1.

Double-click MAC Address Aging Time corresponding to this Ethernet switching board. The MAC Address Aging Time dialog box is displayed.

2.

Set the duration and unit of the aging time.

3.

Click OK.


Issue 03 (2010-05-30)


A-139


A Supporting Task


Value Range

Default Value

Description

MAC Address Aging Time

1 Min to 120 Day

5 Min

l

If one entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the relearning of this MAC address, this entry is deleted automatically. This mechanism is called aging, and this period is called the aging time.

l

If you set this parameter to a very large value, the bridge stores excessive MAC address table entries that are outdated, which exhausts the resources of the MAC address forwarding table.

l

If you set this parameter to a very small value, the bridge may delete the MAC address table entry that is required, which reduces the forwarding efficiency.

l


A.16.4 Querying or Deleting a Dynamic MAC Address By querying a dynamic MAC address, you can learn about all the MAC address entries that are learned by a bridge.

Prerequisite The NE user must have the authority of Operation Level or higher. Ethernet boards must be created on the Slot Layout. Ethernet services must be created.



A-140


Issue 03 (2010-05-30)


A Supporting Task

Procedure Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the Self-learning MAC Address tab. Step 3 Click First Page, Previous, or Next to view the dynamic entries of a MAC address table. Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC Address. ----End

A.17 Modifying E1 Port Impedance The default E1 port impedance is 75 ohms, you can modify the E1 port impedance to 120 ohms as need.



Procedure Step 1 Select the NE from the Object Tree in the NE Explore. Choose Configuration > Port Impedance from the Function Tree. Step 2 Set Port Impedance.



Value Range

Default Value

Description

Port Impedance

75ohm

75ohm

l

Set this parameter to 75ohm when using the 75-ohm coaxial cables.

l

Set this parameter to 120ohm when using the 120-ohm twisted pair cables.

120ohm

Issue 03 (2010-05-30)


A-141


A Supporting Task

A.18 Configuring Auxiliary Interfaces and Functions The auxiliary interfaces and functions supported by the OptiX RTN 605 include the orderwire, synchronous data service, asynchronous data service, and external alarm. A.18.1 Configuring the Orderwire The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use. A.18.2 Configuring Synchronous Data Service To configure the synchronous data services, you need set the F1 data port of the OptiX RTN 605. The synchronous data services are transmitted over the F1 overhead bytes in the radio frame. The transmission rate is 64 kbit/s, that is, E0 level. A.18.3 Configuring Asynchronous Data Service To configure the asynchronous data services, you need to set the broadcast data port of the OptiX RTN 605. The Serial byte in the radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated. A.18.4 Configure External Alarms To configure external alarms, you need to configure the environment monitor port on the EOW board of the OptiX RTN 605. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 605 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 605 and then to the processing equipment at the remote end.

A.18.1 Configuring the Orderwire The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use.



Context The communication channel must be available for activating the orderwire. l

When a radio link exists between two NEs, a fixed overhead byte in the radio frames can be used as the orderwire communication channel.

l

When no microwave link exists between two NEs, connect the synchronous data ports of the two NEs to provide the orderwire communication channel.

The OptiX RTN 605 supports the group call function of the orderwire. When an OptiX RTN 605 dials the orderwire group call number 888, the orderwire phones of all the OptiX RTN 605s in the orderwire subnet ring. When an OptiX RTN 605 answers the phone call, the other A-142


Issue 03 (2010-05-30)


A Supporting Task

OptiX RTN 605s stop ringing, that is, the group call becomes a point-to-point call between two NEs.

Procedure Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the General tab. Step 3 Configure the orderwire information.

Step 4 Click the Apply. ----End

Issue 03 (2010-05-30)


A-143


A Supporting Task


Value Range

Default Value

Description

Call Waiting Time (s)

1 to 9

9

l

This parameter indicates the waiting time after the local station dials the number. If the calling station does not receive the response message from the called station within the call waiting time, it automatically removes the communication connection.

l

If less than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to 5s. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to 9s.

l

Set the same call waiting time for all the NEs.

l

This parameter indicates the orderwire phone number of the local station.

l

The length of the orderwire phone number of each NE should be the same. It is recommended that the phone number consists of three numerics.

l

The orderwire phone number of each NE should be unique. It is recommended that the phone numbers are allocated from 101 for the NEs according to the NE IDs.

l

The orderwire phone number cannot be set to the group call number 888 and cannot start with 888.

100 to99999999

Phone 1

101

A.18.2 Configuring Synchronous Data Service To configure the synchronous data services, you need set the F1 data port of the OptiX RTN 605. The synchronous data services are transmitted over the F1 overhead bytes in the radio frame. The transmission rate is 64 kbit/s, that is, E0 level.

Prerequisite l

A-144



Issue 03 (2010-05-30)


A Supporting Task

Procedure Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the F1 Data Porttab. Step 3 Press the Ctrl key and select two data channels from Available Data Channel. Click .



Value Range

Default Value

Description

Data Channel 1

7-IF0-1 8-IF0-1 F1

-

When the F1 data channel of the OptiX RTN 605 transmits the synchronous data services, the F1 data channel is bound with the working channel in most cases.

Data Channel 2

A.18.3 Configuring Asynchronous Data Service To configure the asynchronous data services, you need to set the broadcast data port of the OptiX RTN 605. The Serial byte in the radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated.

Context The asynchronous data port of the OptiX RTN 605 is an RS-232 port and can implement the universal asynchronous receiver/transmitter (UART) full-duplex communication. The service transmission is required to be point-to-point transparent transmission. Therefore, the port rate and transmission control protocol need not be configured and the maximum communication rate is 19.2 kbit/s. Hence, the asynchronous data port is also considered as the transparent data port. Issue 03 (2010-05-30)


A-145


A Supporting Task

A.18.4 Configure External Alarms To configure external alarms, you need to configure the environment monitor port on the EOW board of the OptiX RTN 605. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 605 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 605 and then to the processing equipment at the remote end.



Context The external alarms of the OptiX RTN 605 are also considered as housekeeping alarms. The external alarm port of the OptiX RTN 605 is a relay port. This port can be either in the "on" state or in the "off" state. The OptiX RTN 605 provides one alarm output port and three alarm input ports. The alarm input ports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of the input alarm) after the external alarm is triggered. To ensure that the external alarm port works normally, the external alarm cables must be correctly connected.

Procedure Step 1 Select the EOW board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Configure the input alarm. 1.

Select Input Relay from the drop-down list.

2.

Configure the parameters of the input alarm. NOTE

The OptiX RTN 605 1F/2F does not support the Path Name parameter.

3.

Click Apply.

Step 3 Configure the output alarm.

A-146

1.

Select Output Relay from the drop-down list.

2.

Configure the parameters of the output alarm. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)



The OptiX RTN 605 1F/2F does not support the Path Name parameter.

3.

Click Apply.

----End

Example Table A-53 Parameters (input relay) Parameter

Value Range

Default Value

Description

Path Name

-

-

This parameter specifies the path name with a maximum length of 20 bytes. This parameter is used to indicates the purpose of the external alarm.

Using Status

Used

Unused

This parameter specifies whether the alarm interface of the input relay is used.

Relay Turns Off/ High Level

l

If this parameter is set to Relay Turns On/Low Level, an alarm is generated when the relay is turned off.

l

If this parameter is set to Relay Turns Off/High Level, an alarm is generated when the relay is turned on.

Unused Alarm Mode

Relay Turns On/ Low Level Relay Turns Off/ High Level

Table A-54 Parameters (output relay) Parameter

Value Range

Default Value

Description

Path Name

-

-

This parameter specifies the path name with a maximum length of 20 bytes. This parameter is used to indicates the purpose of the external alarm.

Use or Not

Used

Unused

This parameter specifies whether the alarm interface of the output relay is used.

Automatic

l

Automatic: Changing the status of the output relay according to Alarm Trigger Conditions and Alarm Mode.

l

Manual: Determining the status of the output relay manually

Unused Working Mode

Automatic Manual

Issue 03 (2010-05-30)


A-147


A Supporting Task

Parameter

Value Range


l

Available values when Working Mode is set to Automatic: Input Path 1

Default Value l

Input Path 2 Input Path 3 Automatically Triggered by Major Alarms Automatically Triggered by Critical Alarms

l

Available values when Working Mode is set to Automatic: Automatically Triggered by Critical and Major Alarms

Description l

Automatic: Automatically changing the status of the relay according to the preset value

l

Manual: Outputting the high level or low level according to the setting

l

If this parameter is set to Relay Turns Off/High Level, the interface is in off state when the alarm is generated.

l

If this parameter is set to Relay Turns On/Low Level, the interface is in on state when the alarm is generated.

Available values when Working Mode is set to Manual: Output High Level in Manual

Automatically Triggered by Critical and Major Alarms l

Available values when Working Mode is set to Manual: Output Low Level in Manual Output High Level in Manual

Alarm Mode




A.19 Testing Ethernet Services By testing Ethernet services, you can check whether Ethernet services are available over radio links. Ethernet services are tested through the ETH OAM function. Therefore, no tester is required.

Prerequisite Ethernet services must be configured. Creating the Maintenance Domain (MD), creating the Maintenance Association (MA), and creating the Maintenance Association End Point (MEP) must be complete.

A-148


Issue 03 (2010-05-30)


A Supporting Task


Test Connection Diagram The following test procedure considers the Ethernet service between PORT1 on NE1 and PORT2 on NE2 as an example, as shown in Figure A-1. Figure A-1 Networking diagram for testing the Ethernet service

NE 2

NE 1 Microwave networking PORT 1

PORT 2

An Ethernet link is available from PORT1 on NE1 to PORT2 on NE2. In addition, MD, MA, and MEP are configured.

Procedure Step 1 In NE Explorer of NE1, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the MD, MA, and MEP that correspond to PORT1, and click OAM Operation. Step 3 Select Start LB. The LB Test window is displayed.

Issue 03 (2010-05-30)


A-149


A Supporting Task

Step 4 Enter the MP ID of NE2 in LB Sink MP ID. Step 5 Click Start LB. Step 6 Check Test Result. The test results should meet the service requirements. ----End

A-150


Issue 03 (2010-05-30)


B Glossary

B

Glossary

Terms are listed in an alphabetical order. B.1 0-9 B.2 A-E B.3 F-J B.4 K-O B.5 P-T B.6 U-Z

Issue 03 (2010-05-30)


B-1


B Glossary

B.1 0-9 1+1 protection

An architecture that has one normal traffic signal, one working SNC/trail, one protection SNC/trail and a permanent bridge. At the source end, the normal traffic signal is permanently bridged to both the working and protection SNC/trail. At the sink end, the normal traffic signal is selected from the better of the two SNCs/trails. Due to the permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic signal to be provided.

1U

The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)

802.1Q in 802.1Q

802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLAN tag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN tag, making the frame encapsulated with two layers of VLAN tags. The frame is forwarded over the service provider's backbone network based on the public VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQ feature enables the transmission of the private VLANs to the peer end transparently.

B.2 A-E A ABR

See Available Bit Rate

ACAP

See adjacent channel alternate polarization

Access Control List

Access Control List (ACL) is a list of IP address. The addresses listed in the ACL are used for authentication. If the ACL for the user is not null, it indicates that the address where the user logged in is contained in the list.

ACL

See Access Control List

adaptive modulation

A technology that is used to automatically adjust the modulation mode according to the channel quality. When the channel quality is favorable, the equipment adopts a highefficiency modulation mode to improve the transmission efficiency and the spectrum utilization of the system. When the channel quality is degraded, the equipment adopts the low-efficiency modulation mode to improve the anti-interference capability of the link that carries high-priority services.

ADC

See Analog to Digital Converter

add/drop multiplexer

Add/Drop Multiplexing. Network elements that provide access to all or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/or dropped from (extracted) the STM-N signal as it passed through the ADM.

Address Resolution Protocol

Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and routers to determine the link layer addresses through ARP requests and ARP responses. The address resolution is a process in which the host converts the target IP address into a target MAC address before transmitting a frame. The basic function of the ARP is to query the MAC address of the target equipment through its IP address.

B-2


Issue 03 (2010-05-30)


B Glossary

adjacent channel alternate polarization

A channel configuration method, which uses two adjacent channels (a horizontal polarization wave and a vertical polarization wave) to transmit two signals.

ADM

See add/drop multiplexer

Administrative Unit

The information structure which provides adaptation between the higher order path layer and the multiplex section layer. It consists of an information payload (the higher order VC) and an AU pointer which indicates the offset of the payload frame start relative to the multiplex section frame start.

AF

See Assured Forwarding

AGC

See Automatic Gain Control

aggregation

A collection of objects that makes a whole. An aggregation can be a concrete or conceptual set of whole-part relationships among objects.

AIS

See Alarm Indication Signal

Alarm automatic report

When an alarm is generated on the device side, the alarm is reported to the N2000. Then, an alarm panel prompts and the user can view the details of the alarm.

alarm cascading

The shunt-wound output of the alarm signals of several subracks or cabinets.

Alarm Filtering

An NE reports the detected alarm to the element management system (EMS). Based on the filter state of the alarm, the EMS determines whether to display or save the alarm information. If the filter state of an alarm is set to Filter, the alarm is not displayed or stored on the EMS. The alarm, however, is still monitored by the NE.

Alarm Indication Signal

A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. Note: See ITU-T Rec. G.707/Y.1322 for specific AIS signals.

Alarm suppression

A function used not to monitor alarms for a specific object, which may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board.

AM

See adaptive modulation

Analog to Digital Converter

An electronic circuit that converts continuous signals to discrete digital numbers. The reverse operation is performed by a digital-to-analog converter (DAC).

APS

See Automatic Protection Switching

ARP

See Address Resolution Protocol

ASK

amplitude shift keying

Assured Forwarding

Assured Forwarding (AF) is one of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF. AF is suitable for certain key data services that require assured bandwidth and short delay. For traffic within the limit, AF assures quality in forwarding. For traffic that exceeds the limit, AF degrades the service class and continues to forward the traffic instead of discarding the packets.

Asynchronous Transfer Mode

A data transfer technology based on cell, in which packets allocation relies on channel demand. It supports fast packet switching to achieve efficient utilization of network resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte header.

ATM

See Asynchronous Transfer Mode

ATM PVC

ATM Permanent Virtual Circuit

Issue 03 (2010-05-30)


B-3


B Glossary

ATPC

See automatic transmit power control

attenuator

A device used to increase the attenuation of an Optical Fibre Link. Generally used to ensure that the signal at the receive end is not too strong.

AU

See Administrative Unit

Automatic Gain Control

A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter, such as received signal level.

Automatic Protection Switching

Automatic Protection Switching (APS) is the capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic.

automatic transmit power control

A method of adjusting the transmit power based on fading of the transmit signal detected at the receiver

Available Bit Rate

A kind of service categories defined by the ATM forum. ABR only provides possible forwarding service and applies to the connections that does not require the real-time quality. It does not provide any guarantee in terms of cell loss or delay.

B Backward Defect Indication

When detecting a defect, the sink node of a LSP uses backward defect indication (BDI) to inform the upstream end of the LSP of a downstream defect along the return path.

bandwidth

A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate.

Base Station Controller A logical entity that connects the BTS with the MSC in a GSM network. It interworks with the BTS through the Abis interface, the MSC through the A interface. It provides the following functions: Radio resource management, Base station management, Power control, Handover control, and Traffic measurement. One BSC controls and manages one or more BTSs in an actual network. Base Transceiver Station

A Base Transceiver Station terminates the radio interface. It allows transmission of traffic and signaling across the air interface. The BTS includes the baseband processing, radio equipment, and the antenna.

BDI

See Backward Defect Indication

BE

See best effort

BER

See Bit Error Rate

best effort

A kind of PHB (Per-Hop-Behavior). In the forwarding process of a DS domain, the traffic of this PHB type features reachability but the DS node does not guarantee the forwarding quality.

BIOS

Basic Input Output System

BIP

Bit-Interleaved Parity

bit error

An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal.

Bit Error Rate

Bit error rate. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network.

B-4


Issue 03 (2010-05-30)


B Glossary

blank filler panel

A piece of board to cover vacant slots, to keep the frame away from dirt, to keep proper airflow inside the frame, and to beautify the frame appearance.

BPDU

See Bridge Protocol Data Unit

Bridge Protocol Data Unit

The data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol (STP) topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology. The loops are then removed by shutting down selected bridges interfaces and placing redundant switch ports in a backup, or blocked, state.

Broadcast

A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address.

BSC

See Base Station Controller

BTS

See Base Transceiver Station

Buffer

A storage area used for handling data in transit. Buffers are used in internetworking to compensate for differences in processing speed between network devices. Bursts of data can be stored in buffers until they can be handled by slower processing devices.

C C-VLAN

Customer VLAN

Cable distribution plate A component which is used to arrange the cables in order. cable ladder

(1) A cable ladder is a frame which supports electrical cables. (2) Two metal cables usually made of stainless steel with rungs of lightweight metal tubing such as aluminum, six or eight inches wide spaced about eighteen inches apart. It can be rolled into a compact lightweight bundle for transport ease.

cable tie

The tape used to bind the cables.

cabling trough

The trough which is used for cable routing in the cabinet.

captive nut

Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses but are more commonly used in the hobby for engine fixing (securing engine mounts to the firewall), wing fixings, and undercarriage fixing.

CAR

See committed access rate

CBR

See Constant Bit Rate

CCC

See Circuit Cross Connect

CCDP

See Co-Channel Dual Polarization

CCM

See continuity check message

CE

See Customer Edge

Central Processing Unit

The CPU is the brains of the computer. Sometimes referred to simply as the processor or central processor, the CPU is where most calculations take place.

CES

See Circuit Emulation Service

CF

See compact flash

CGMP

Cisco Group Management Protocol

Issue 03 (2010-05-30)


B-5


B Glossary

CIR

See Committed Information Rate

Circuit Cross Connect

An implementation of MPLS L2VPN through the static configuration of labels.

Circuit Emulation Service

A function with which the E1/T1 data can be transmitted through ATM networks. At the transmission end, the interface module packs timeslot data into ATM cells. These ATM cells are sent to the reception end through the ATM network. At the reception end, the interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES technology guarantees that the data in E1/T1 timeslots can be recovered to the original sequence at the reception end.

CIST

See Common and Internal Spanning Tree

CIST root

A switch of the highest priority is elected as the root in an MSTP network.

Class of Service

A class object that stores the priority mapping rules. When network congestion occurs, the class of service (CoS) first processes services by different priority levels from high to low. If the bandwidth is insufficient to support all services, the CoS dumps the services of low priority.

Clock tracing

The method to keep the time on each node being synchronized with a clock source in a network.

Co-Channel Dual Polarization

A channel configuration method, which uses a horizontal polarization wave and a vertical polarization wave to transmit two signals. The Co-Channel Dual Polarization is twice the transmission capacity of the single polarization.

Coarse Wavelength Division Multiplexing

A signal transmission technology that multiplexes widely-spaced optical channels into the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM does not support optical amplifiers and is applied in short-distance chain networking.

Colored packet

A packet whose priority is determined by defined colors.

Combined cabinet

Two or multiple BTS cabinets of the same type are combined to serve as one BTS.

committed access rate

A traffic control method that uses a set of rate limits to be applied to a router interface. CAR is a configurable method by which incoming and outgoing packets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined.

Committed Information Rate

The rate at which a frame relay network agrees to transfer information in normal conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket.

Common and Internal Common and Internal Spanning Tree. The single Spanning Tree calculated by STP and Spanning Tree RSTP together with the logical continuation of that connectivity through MST Bridges and regions, calculatedby MSTP to ensure that all LANs in the Bridged Local Area Network are simply and fully connected. compact flash

Compact flash (CF) was originally developed as a type of data storage device used in portable electronic devices. For storage, CompactFlash typically uses flash memory in a standardized enclosure.

Concatenation

A process that combines multiple virtual containers. The combined capacities can be used a single capacity. The concatenation also keeps the integrity of bit sequence.

connecting plate for combining cabinets

A plate that connects two adjacent cabinet together at the cabinet top for fixing.

B-6


Issue 03 (2010-05-30)


B Glossary

Connectivity Check

Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically. This detection is called CC detection.

Constant Bit Rate

constant bit rate. A kind of service categories defined by the ATM forum. CBR transfers cells based on the constant bandwidth. It is applicable to service connections that depend on precise clocking to ensure undistorted transmission.

Constraint Shortest Path First

An extension of shortest path algorithms like OSPF and IS-IS. The path computed using CSPF is a shortest path fulfilling set of constrains. It simply means that it runs shortest path algorithm after pruning those links that violate a given set of constraints. A constraint could be minimum bandwidth required per link (also know as bandwidth guaranteed constraint), end-to-end delay, maximum number of link traversed etc. CSPF is widely used in MPLS Traffic Engineering. The routing using CSPF is known as Constraint Based Routing (CBR).

Constraint-based Routed-Label Distribution Protocol

An alternative to RSVP (Resource ReSerVation Protocol) in MPLS (MultiProtocol Label Switching) networks. RSVP, which works at the IP (Internet Protocol) level, uses IP or UDP datagrams to communicate between LSR (Label Switched Routing) peers. RSVP does not require the maintenance of TCP (Transmission Control Protocol) sessions, although RSVP must assume responsibility for error control. CR-LDP is designed to facilitate the routing of LSPs (Label Switched Paths) through TCP sessions between LSR peers through the communication of label distribution messages during the session.

continuity check message

CCM is used to detect the link status.

corrugated tube

A pipe which is used for fiber routing.

CoS

See Class of Service

CPU

See Central Processing Unit

CR-LDP

See Constraint-based Routed-Label Distribution Protocol

CRC

See Cyclic Redundancy Check

cross polarization interference cancellation

A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate the cross-connect interference between two polarization waves in the CCDP.

CSPF

See Constraint Shortest Path First

Customer Edge

A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the Service Provider (SP) network. A CE can be a router, switch, or host.

CWDM

See Coarse Wavelength Division Multiplexing

Cyclic Redundancy Check

A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values.

Issue 03 (2010-05-30)


B-7


B Glossary

D Data Circuit-terminal Equipment

Also Data Communications Equipment (DCE) and Data Carrier Equipment (DCE). The basic function of a DCE is to convert data from one interface, such as a digital signal, to another interface, such as an analog signal. One example of DCE is a modem.

Data Communication Network

A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF).

Data Communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to Channel transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-M channel. Datagram

A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram, UDP datagram.

DC

See Direct Current

DC-C

See DC-Return Common (with Ground)

DC-I

See DC-Return Isolate (with Ground)

DC-Return Common (with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinet and also on the line between the output of the power supply cabinet and the electric equipment.

DC-Return Isolate (with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinet and is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment.

DCC

See Data Communications Channel

DCE

See Data Circuit-terminal Equipment

DCN

See Data Communication Network

DDF

See Digital Distribution Frame

DDN

See Digital Data Network

DE

See discard eligible

Detour LSP

The LSP that is used to re-route traffic around a failure in one-to-one backup.

diamond-shaped nut

A type of nut that is used to fasten the wiring frame to the cabinet.

Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a series of functional units implemented at the network nodes, including a small group of perhop forwarding behaviors, packet classification functions, and traffic conditioning functions such as metering, marking, shaping and policing. Differentiated Services Differentiated Services CodePoint. A marker in the header of each IP packet using bits Code Point 0-6 in the DS field. Routers provide differentiated classes of services to various service streams/flows based on this marker. In other words, routers select corresponding PHB according to the DSCP value. DiffServ

See Differentiated Services

Digital Data Network

A high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and the cross multiplex technology.

B-8


Issue 03 (2010-05-30)


B Glossary

Digital Distribution Frame

A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals.

digital modulation

A digital modulation controls the changes in amplitude, phase, and frequency of the carrier based on the changes in the baseband digital signal. In this manner, the information can be transmitted by the carrier.

Direct Current

Electrical current whose direction of flow does not reverse. The current may stop or change amplitude, but it always flows in the same direction.

discard eligible

A bit in the frame relay header. It indicates the priority of a packet. If a node supports the FR QoS, the rate of the accessed FR packets is controlled. When the packet traffic exceeds the specified traffic, the DE value of the redundant packets is set to 1. In the case of network congestion, the packets with DE value as 1 are discarded at the node.

Distance Vector Multicast Routing Protocol

Distance Vector Multicast Routing Protocol. The DVMRP protocol is an Internet gateway protocol mainly based on the RIP. The protocol implements a typical dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing datagrams with its neighbors.

DS boundary node

A DS node that connects one DS domain to a node either in another DS domain or in a domain that is not DS-capable.

DS domain

In the DifferServ mechanism, the DS domain is a domain consisting of a group of network nodes that share the same service provisioning policy and same PHB. It provides point-to-point QoS guarantees for services transmitted over this domain.

DS interior node

A DS node located at the center of a DS domain. It is a non-DS boundary node.

DS node

A DS-compliant node, which is subdivided into DS boundary node and ID interior node.

DSCP

See Differentiated Services Code Point

dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves orthogonally polarized. DVMRP

See Distance Vector Multicast Routing Protocol

E E-AGGR

Ethernet-Aggregation

E-LAN

See Ethernet LAN

E-Tree

See Ethernet-Tree

EBS

See Excess Burst Size

ECC

See Embedded Control Channel

EF

See Expedited Forwarding

EFM

See Ethernet in the First mile

Electro Magnetic Interference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment.

Issue 03 (2010-05-30)


B-9


B Glossary

electromagnetic compatibility

Electromagnetic compatibility is the condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment. [NTIA]

ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field. Embedded Control Channel

An ECC provides a logical operations channel between SDH NEs, utilizing a data communications channel (DCC) as its physical layer.

EMC

See electromagnetic compatibility

EMI

See Electro Magnetic Interference

Engineering label

A mark on a cable, a subrack, or a cabinet for identification.

EPLn

See Ethernet Private LAN

equalization

A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading.

ERPS

See ethernet ring protection switching

ES-IS

End System to Intermediate System

ESD

See ElectroStatic Discharge

ESD jack

Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap.

ETH-CC

Ethernet Continuity Check

ETH-LB

Ethernet Loopback

ETH-LT

Ethernet Link Trace

Ethernet

A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/ s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..

Ethernet in the First mile

Last mile access from the broadband device to the user community. The EFM takes the advantages of the SHDSL.bis technology and the Ethernet technology. The EFM provides both the traditional voice service and internet access service of high speed. In addition, it meets the users' requirements on high definition television system (HDTV) and Video On Demand (VOD).

Ethernet LAN

Ethernet LAN. A L2VPN service type that is provided for the user Ethernet in different domains over the PSN network. For the user Ethernet, the entire PSN network serves as a Layer 2 switch.

Ethernet Private LAN

Both a LAN service and a private service. Transport bandwidth is never shared between different customers.

ethernet ring protection switching

protection switching mechanisms for ETH layer Ethernet ring topologies.

Ethernet Virtual Private LAN

A service that is both a LAN service and a virtual private service.

Ethernet-Tree

etherenet tree. An Ethernet service type that is based on a Point-to-multipoint Ethernet Virtual Connection.

B-10


Issue 03 (2010-05-30)


B Glossary

ETS

European Telecommunication Standards

ETSI

See European Telecommunications Standards Institute

ETSI 300mm cabinet

A cabinet which is 600mm in width and 300mm in depth, compliant with the standards of the ETSI.

European Telecommunications Standards Institute

A standards-setting body in Europe. Also the standards body responsible for GSM.

EVPL

Ethernet Virtual Private Line

EVPLn

See Ethernet Virtual Private LAN

Excess Burst Size

excess burst size. In the single rate three color marker (srTCM) mode, the traffic control is realized by the token buckets C and E. Excess burst size is a parameter used to define the capacity of token bucket E, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

Exercise Switching

An operation to check if the protection switching protocol functions normally. The protection switching is not really performed.

Expedited Forwarding Expedited Forwarding (EF) is the highest order QoS in the Diff-Serv network. EF PHB is suitable for services that demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP value of EF PHB is "101110".

B.3 F-J F Failure

If the fault persists long enough to consider the ability of an item with a required function to be terminated. The item may be considered as having failed; a fault has now been detected.

Fast Ethernet

A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies with the IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard.

fast link pulse

The likn pulse that is used to encode information during automatic negotiation.

FCS

Frame Check Sequence

FD

See frequency diversity

FDI

See Forward Defect Indication

FE

See Fast Ethernet

FEC

See Forward Error Correction

FFD

Fast Failure Detection

Fiber Connector

A device installed at the end of a fiber, optical source or receive unit. It is used to couple the optical wave to the fiber when connected to another device of the same type. A connector can either connect two fiber ends or connect a fiber end and a optical source (or a detector).

Issue 03 (2010-05-30)


B-11


B Glossary

fiber patch cord

A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack.

Field Programmable Gate Array

A type of semi-customized circuit used in the Application Specific Integrated Circuit (ASIC) field. It is developed on the basis of the programmable components, such as the PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also overcomes the disadvantage of the original programmable components in terms of the limited number of gate arraies.

FIFO

See First in First out

File Transfer Protocol

A member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTP roles: one must be an FTP client and the other an FTP server.

First in First out

A stack management mechanism. The first saved data is first read and invoked.

FLP

See fast link pulse

Forced switch

This function forces the service to switch from the working channel to the protection channel, with the service not to be restored automatically. This switch occurs regardless of the state of the protection channels or boards, unless the protection channels or boards are satisfying a higher priority bridge request.

Forward Defect Indication

Forward defect indication (FDI) is generated and traced forward to the sink node of the LSP by the node that first detects defects. It includes fields to indicate the nature of the defect and its location. Its primary purpose is to suppress alarms being raised at affected higher level client LSPs and (in turn) their client layers.

Forward Error Correction

A bit error correction technology that adds the correction information to the payload at the transmit end. Based on the correction information, the bit errors generated during transmission are corrected at the receive end.

Forwarding plane

Also referred to as the data plane. The forwarding plane is connection-oriented, and can be used in Layer 2 networks such as an ATM network.

FPGA

See Field Programmable Gate Array

Fragment

Piece of a larger packet that has been broken down to smaller units.

Fragmentation

Process of breaking a packet into smaller units when transmitting over a network medium that can not support the original size of the packet.

frame

A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.

frequency diversity

A diversity scheme that enables two or more microwave frequencies with a certain frequency interval are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading.

FTP

See File Transfer Protocol

Full duplex

The system that can transmit information in both directions on a communication link.On the communication link, both parties can send and receive data at the same time.

B-12


Issue 03 (2010-05-30)


B Glossary

G gateway network element

A network element that is used for communication between the NE application layer and the NM application layer

GCP

See GMPLS control plan

GE

See Gigabit Ethernet

Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is to adapt the traffic to network resources that can be provided by the downstream router to avoid packet discarding and congestion. GFP

Generic Framing Procedure

Gigabit Ethernet

GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.It runs at 1000Mbit/s. Gigabit Ethernet uses a private medium, and it does not support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge (switch) or a router as the center, it gives full play to the performance and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that are private, causing the length of the links to be sufficient for backbone applications in a building and campus.

Global Positioning System

A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users .

GMPLS control plan

The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei. The OptiX GCP applies to the OptiX OSN product series. By using this software, the traditional network can evolve into the ASON network. The OptiX OSN product series support the ASON features.

GNE

See gateway network element

GPS

See Global Positioning System

GR

See Graceful Restart

Graceful Restart

In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/ MPLS) such as Open Shortest Path First (OSPF), Intermediate System-Intermediate System (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP), and Resource Reservation Protocol (RSVP) are extended to ensure that the forwarding is not interrupted when the system is restarted. This reduces the flapping of the protocols at the control plane when the system performs the active/standby switchover. This series of standards is called Graceful Restart.

Graphical User Interface

A visual computer enviroment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen.

ground resistance

(electricity) Opposition of the earth to the flow of current through it; its value depends on the nature and moisture content of the soil, on the material, composition, and nature of connections to the earth, and on the electrolytic action present.

GTS

See Generic traffic shaping

GUI

See Graphical User Interface

guide rail

Components to guide, position, and support plug-in boards.

Issue 03 (2010-05-30)


B-13


B Glossary

H H-QoS

Hierarchical Quality of Service

HA

See High Availability

half-duplex

A transmitting mode in which a half-duplex system provides for communication in both directions, but only one direction at a time (not simultaneously). Typically, once a party begins receiving a signal, it must wait for the transmitter to stop transmitting, before replying.

HDB3

High Density Bipolar Code 3

HDLC

See High level Data Link Control procedure

High Availability

The ability of a system to continuously perform its functions during a long period, which may exceeds the suggested working time of the independent components. You can obtain the high availability (HA) by using the error tolerance method. Based on learning cases one by one, you must also clearly understand the limitations of the system that requires an HA ability and the degree to which the ability can reach.

High level Data Link Control procedure

A data link protocol from ISO for point-to-point communications over serial links. Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocols including X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLC have been developed under the name of Link Access Procedure (LAP).

High Speed Downlink Packet Access

A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement for asymmetric uplink and downlink transmission of data services. It enables the maximum downlink data service rate to reach 14.4 Mbit/s without changing the WCDMA network topology.

Hold priority

The priority of the tunnel with respect to holding resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the resources occupied by the tunnel can be preempted by other tunnels.

Hop

A network connection between two distant nodes. For Internet operation a hop represents a small step on the route from one main computer to another.

hot standby

A mechanism of ensuring device running security. The environment variables and storage information of each running device are synchronized to the standby device. When the faults occur on the running device, the standby device can take over the services in the faulty device in automatic or manual way to ensure the normal running of the entire system.

HP

Higher Order Path

HSDPA

See High Speed Downlink Packet Access

HSM

Hitless Switch Mode

HTB

High Tributary Bus

hybrid radio

The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.

I ICMP

See Internet Control Messages Protocol

IDU

See indoor unit

B-14


Issue 03 (2010-05-30)


B Glossary

IEC

See International Electrotechnical Commission

IEEE

See Institute of Electrical and Electronics Engineers

IETF

The Internet Engineering Task Force

IF

See intermediate frequency

IGMP

See Internet Group Management Protocol

IGMP snooping

A multicast constraint mechanism running on a layer 2 device. This protocol manages and controls the multicast group by listening to and analyze the Internet Group Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner, the spread of the multicast data on layer 2 network can be prevented efficiently.

IMA

See Inverse Multiplexing over ATM

indoor unit

The indoor unit of the split-structured radio equipment. It implements accessing, multiplexing/demultiplexing, and IF processing for services.

Inloop

A method of looping the signals from the cross-connect unit back to the cross-connect unit.

Institute of Electrical and Electronics Engineers

A society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEE focuses on electrical, electronics, computer engineering, and science-related matters.

Interface board area

The area for the interface boards on the subrack.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF signal. Intermediate System

The basic unit in the IS-IS protocol used to transmit routing information and generate routes.

Intermediate System to A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol Intermediate System (IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF) algorithm to calculate the route. Internal Spanning Tree Internal spanning tree. A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0. International Electrotechnical Commission

The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards.

International Organization for Standardization

ISO (International Organization for Standardization) is the world's largest developer and publisher of International Standards.

Internet Control Messages Protocol

ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messages during the transmission of IP-type data packets.

Internet Group Management Protocol

The protocol for managing the membership of Internet Protocol multicast groups among the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships.

Internet Protocol

The TCP/IP standard protocol that defines the IP packet as the unit of information sent across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part. The entire protocol suite is often referred to as TCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791.

Issue 03 (2010-05-30)


B-15


B Glossary

Internet Protocol Version 6

A update version of IPv4. It is also called IP Next Generation (IPng). The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits.

Inverse Multiplexing over ATM

Inverse Multiplexing over ATM. The ATM inverse multiplexing technique involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links grouped to form a higher bandwidth logical link whose rate is approximately the sum of the link rates. This is referred to as an IMA group.

IP

See Internet Protocol

IPv6

See Internet Protocol Version 6

IS-IS

See Intermediate System to Intermediate System

ISO

See International Organization for Standardization

IST

See Internal Spanning Tree

ITU-T

International Telecommunication Union - Telecommunication Standardization Sector

IVL

Independence VLAN learning

J Jitter

Short waveform variations caused by vibration, voltage fluctuations, and control system instability.

B.4 K-O L L2VPN

See Layer 2 virtual private network

Label Switched Path

A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label switching mechanisms. A label-switched path can be chosen dynamically, based on normal routing mechanisms, or through configuration.

Label Switching Router The Label Switching Router (LSR) is the basic element of MPLS network. All LSRs support the MPLS protocol. The LSR is composed of two parts: control unit and forwarding unit. The former is responsible for allocating the label, selecting the route, creating the label forwarding table, creating and removing the label switch path; the latter forwards the labels according to groups received in the label forwarding table. LACP

See Link Aggregation Control Protocol

LAG

See link aggregation group

LAN

See Local Area Network

LAPD

Link Access Procedure on the D channel

LAPS

Link Access Procedure-SDH

B-16


Issue 03 (2010-05-30)


B Glossary

Laser

A component that generates directional optical waves of narrow wavelengths. The laser light has better coherence than ordinary light. The fiber system takes the semi-conductor laser as the light source.

layer 2 switch

A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits and distributes packet data based on the MAC address. Since the MAC address is the second layer of the OSI model, this data forwarding method is called layer 2 switch.

Layer 2 virtual private A virtual private network realized in the packet switched (IP/MPLS) network by Layer network 2 switching technologies. LB

See Loopback

LCAS

See Link Capacity Adjustment Scheme

LDPC

Low-Density Parity Check code

line rate forwarding

The line rate equals the maximum transmission rate capable on a given type of media.

Link Aggregation Control Protocol

Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad) that allows you to bundle several physical ports to form a single logical channel. LACP allows a switch to negotiate an automatic bundle by sending LACP packets to the peer.

link aggregation group An aggregation that allows one or more links to be aggregated together to form a link aggregation group so that a MAC clientcan treat the link aggregation group as if it were a single link. Link Capacity Adjustment Scheme

The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamic provisioning of bandwidth, using VCAT, to meet customer requirements.

Link Protection

Protection provided by the bypass tunnel for the link on the working tunnel. The link is a downstream link adjacent to the PLR. When the PLR fails to provide node protection, the link protection should be provided.

LMSP

Linear Multiplex Section Protection

Local Area Network

A network formed by the computers and workstations within the coverage of a few square kilometers or within a single building. It features high speed and low error rate. Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/ s (that is, 1 Gbit/s).

Locked switching

When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel.

LOF

See Loss Of Frame

LOM

Loss Of Multiframe

Loopback

A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors.

LOP

See Loss Of Pointer

LOS

See Loss Of Signal

Loss Of Frame

A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost frame delineation. This is used to monitor the performance of the PHY layer.

Issue 03 (2010-05-30)


B-17


B Glossary

Loss Of Pointer

Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost the pointer to the start of cell in the payload. This is used to monitor the performance of the PHY layer.

Loss Of Signal

Loss of signal (LOS) indicates that there are no transitions occurring in the received signal.

Lower subrack

The subrack close to the bottom of the cabinet when a cabinet contains several subracks.

LP

Lower Order Path

LPT

Link State Path Through

LSP

See Label Switched Path

LSR

See Label Switching Router

M MA

See Maintenance Association

MAC

See Medium Access Control

MAC

See Media Access Control

MADM

Multi Add-Drop Multiplexer

Maintenance Association

That portion of a Service Instance, preferably all of it or as much as possible, the connectivity of which is maintained by CFM. It is also a full mesh of Maintenance Entities.

Maintenance association End Point

A MEP is an actively managed CFM Entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM frames and track any responses. It is an end point of a single Maintenance Association, and terminates a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association.

Maintenance Domain

The Maintenance Domain (MD) refers to the network or the part of the network for which connectivity is managed by CFM. The devices in an MD are managed by a single ISP.

Maintenance Point

Maintenance Point (MP) is one of either a MEP or a MIP.

Management Information Base

A type of database used for managing the devices in a communications network. It comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network.

Manual switching

A protection switching. When the protection path is normal and there is no request of a higher level switching, the service is manually switched from the working path to the protection path, to test whether the network still has the protection capability.

Maximum Transfer Unit

The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be sent over a network.

MBS

Maximum Burst Size

MCF

See Message Communication Function

MD

See Maintenance Domain

MDI

See Medium Dependent Interface

Mean Time To Repair

The average time that a device will take to recover from a failure.

B-18


Issue 03 (2010-05-30)


B Glossary

Media Access Control

A protocol at the media access control sublayer. The protocol is at the lower part of the data link layer in the OSI model and is mainly responsible for controlling and connecting the physical media at the physical layer. When transmitting data, the MAC protocol checks whether to be able to transmit data. If the data can be transmitted, certain control information is added to the data, and then the data and the control information are transmitted in a specified format to the physical layer. When receiving data, the MAC protocol checks whether the information is correct and whether the data is transmitted correctly. If the information is correct and the data is transmitted correctly, the control information is removed from the data and then the data is transmitted to the LLC layer.

Medium Access Control

A general reference to the low-level hardware protocols used to access a particular network. The term MAC address is often used as a synonym for physical addresses.

Medium Dependent Interface

The electrical and mechanical interface between the equipment and the media transmission.

MEP

See Maintenance association End Point

Message Communication Function

The MCF is composed of a protocol stack that allows exchange of management information with their prs .

MIB

See Management Information Base

MIP

Maintenance Intermediate Point

MLPPP

See Multi-link Point to Point Protocol

mount angle

An L-shape steel sheet. One side is fixed on the front panel with screws, and the other side is fixed on the installation hole with screws. On both sides of a rack, there is an Lshaped metal fastener. This ensures that internal components are closely connected with the rack. Normally, an internal component is installed with two mount angles.

MP

See Maintenance Point

MPID

Maintenance Point Identification

MPLS

See Multi-Protocol Label Switch

MPLS L2VPN

The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network.In this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of different media types, such as ATM, FR, VLAN, Ethernet, and PPP.

MPLS OAM

The MPLS OAM provides continuity check for a single LSP, and provides a set of fault detection tools and fault correct mechanisms for MPLS networks. The MPLS OAM and relevant protection switching components implement the detection function for the CRLSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs. In this way, the impact of a fault can be lowered to the minimum.

MPLS TE

Multiprotocol Label Switching Traffic Engineering

MPLS TE tunnel

In the case of reroute deployment, or when traffic needs to be transported through multiple trails, multiple LSP tunnels might be used. In traffic engineering, such a group of LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has two identifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquely define the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE or FILTER_SPEC object.

MS

See Multiplex Section

MSP

See multiplex section protection

Issue 03 (2010-05-30)


B-19


B Glossary

MSTI

See Multiple Spanning Tree Instance

MSTP

See Multiple Spanning Tree Protocol

MTBF

Mean Time Between Failure

MTTR

See Mean Time To Repair

MTU

See Maximum Transfer Unit

Multi-link Point to Point Protocol

A protocol used in ISDN connections. MLPPP lets two B channels act as a single line, doubling connection rates to 128Kbps.

Multi-Protocol Label Switch

A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing.

Multicast

A process of transmitting packets of data from one source to many destinations. The destination address of the multicast packet uses Class D address, that is, the IP address ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast group rather than a host.

Multiple Spanning Tree Instance

Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP within an MST Region, to provide a simply and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to multiple MSTIs.

Multiple Spanning Tree Protocol

Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In this case, the proliferation and endless cycling of packets is avoided in the loop network.The protocol that introduces the mapping between VLANs and multiple spanning trees. This solves the problem that data cannot be normally forwarded in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.

Multiple Spanning Tree Region

The MST region consists of switches that support the MSTP in the LAN and links among them. Switches physically and directly connected and configured with the same MST region attributes belong to the same MST region. The attributes for the same MST region are as follows: Same region name Same revision level Same mapping relation between the VLAN ID to MSTI

Multiplex Section

The trail between and including two multiplex section trail termination functions.

multiplex section protection

A function, which is performed to provide capability for switching a signal between and including two multiplex section termination (MST) functions, from a "working" to a "protection" channel.

N N+1 protection

A radio link protection system composed of N working channels and one protection channel.

NE

See Network Element

NE Explorer

The main operation interface, of the U2000, which is used to manage the OptiX equipment. In the NE Explorer, the user can configure, manage and maintain the NE, boards, and ports on a per-NE basis.

B-20


Issue 03 (2010-05-30)


B Glossary

Network Element

A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control board which manages and monitors the entire network element. The NE software runs on the system control board.

network management system

The network management system in charge of the operation, administration, and maintenance of a network.

Network Service Access A network address defined by ISO, through which entities on the network layer can Point access OSI network services. Network to Network Interface

This is an internal interface within a network linking two or more elements.

next hop

The next router to which a packet is sent from any given router as it traverses a network on its journey to its final destination.

NLP

Normal Link Pulse

NMS

See network management system

NNHOP

Next-Next-Hop

NNI

See Network to Network Interface

Node

A node stands for a managed device in the network.For a device with a single frame, one node stands for one device.For a device with multiple frames, one node stands for one frame of the device.Therefore, a node does not always mean a device.

Node Protection

A parameter of the FRR protection. It indicates that the bypass tunnel should be able to protect the downstream node that is involved in the working tunnel and adjacent to the PLR. The node cannot be a merge point, and the bypass tunnel should also be able to protect the downstream link that is involved in the working tunnel and adjacent to the PLR.

non-gateway network element

A network element whose communication with the NM application layer must be transferred by the gateway network element application layer.

non-GNE

See non-gateway network element

NSAP

See Network Service Access Point

NSF

Not Stop Forwarding

NSMI

Network Serial Multiplexed Interface

O OAM

See Operation, Administration and Maintenanc

ODF

See Optical Distribution Frame

ODU

See outdoor unit

One-to-One Backup

A local repair method in which a backup tunnel is separately created for each protected tunnel at a PLR.

Open Shortest Path First

A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A link state database is constructed of the network topology which is identical on all routers in the area.

Issue 03 (2010-05-30)


B-21


B Glossary

Open Systems Interconnection

A standard or "reference model" (officially defined by the International Organization of Standards (ISO)) for how messages should be transmitted between any two points in a telecommunication network. The reference model defines seven layers of functions that take place at each end of a communication.

Operation, Administration and Maintenanc

Operation, Administration and Maintenance. A group of network support functions that monitor and sustain segment operation, activities that are concerned with, but not limited to, failure detection, notification, location, and repairs that are intended to eliminate faults and keep a segment in an operational state and support activities required to provide the services of a subscriber access network to users/subscribers.

Optical Distribution Frame

A frame which is used to transfer and spool fibers.

orderwire

A channel that provides voice communication between operation engineers or maintenance engineers of different stations.

OSI

See Open Systems Interconnection

OSP

OptiX Software Platform

OSPF

See Open Shortest Path First

outdoor unit

The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for RF signals.

Outloop

A method of looping back the input signals received at an port to an output port without changing the structure of the signals.

Output optical power

The ranger of optical energy level of output signals.

B.5 P-T P Packet over SDH/ SONET

A MAN and WAN technology that provides point-to-point data connections. The POS interface uses SDH/SONET as the physical layer protocol, and supports the transport of packet data (such as IP packets) in MAN and WAN.

packet switched network

A telecommunication network which works in packet switching mode.

Packing case

A case which is used for packing the board or subrack.

Path/Channel

A logical connection between the point at which a standard frame format for the signal at the given rate is assembled, and the point at which the standard frame format for the signal is disassembled.

PBS

See peak burst size

PCB

See Printed Circuit Board

PCI bus

PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bit for interconnecting chips, expansion boards, and processor/memory subsystems.

PDH

See Plesiochronous Digital Hierarchy

PDU

Protocol Data Unit

PE

See Provider Edge

B-22


Issue 03 (2010-05-30)


peak burst size

B Glossary

A parameter used to define the capacity of token bucket P, that is, the maximum burst IP packet size when the information is transferred at the peak information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. Penultimate Hop Popping

Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLS enabled network. It refers to the process whereby the outermost label of an MPLS tagged packet is removed by a Label Switched Router (LSR) before the packet is passed to an adjacent Label Edge Router (LER).

Per-Hop-Behavior

A forwarding behavior applied at a DS-compliant node. This behavior belongs to the behavior aggregate defined in the DiffServ domain.

PHB

See Per-Hop-Behavior

PHP

See Penultimate Hop Popping

PIM-DM

Protocol Independent Multicast-Dense Mode

PIM-SM

See Protocol Independent Multicast-Sparse Mode

PIR

See Peak Information Rate

Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum Hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates. Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. polarization

A kind of electromagnetic wave, the direction of whose electric field vector is fixed or rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is perpendicular to the plane of horizon, this electromagnetic wave is called vertically polarized wave; if the electric field vector of the electromagnetic wave is parallel to the plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the tip of the electric field vector, at a fixed point in space, describes a circle, this electromagnetic wave is called circularly polarized wave.

POS

See Packet over SDH/SONET

Power box

A direct current power distribution box at the upper part of a cabinet, which supplies power for the subracks in the cabinet.

PPP

See Point-to-Point Protocol

PPVPN

Provider Provisioned VPN

PQ

See Priority Queuing

PRBS

Pseudo-Random Binary Sequence

PRC

Primary Reference Clock

Printed Circuit Board

A board used to mechanically support and electrically connect electronic components using conductive pathways, tracks, or traces, etched from copper sheets laminated onto a non-conductive substrate.

Issue 03 (2010-05-30)


B-23


B Glossary

Priority Queuing

A priority queue is an abstract data type in computer programming that supports the following three operations: 1) InsertWithPriority: add an element to the queue with an associated priority 2) GetNext: remove the element from the queue that has the highest priority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3) PeekAtNext (optional): look at the element with highest priority without removing it

Processing board area

An area for the processing boards on the subrack.

protection grounding cable

A cable which connects the equipment and the protection grounding bar. Usually, one half of the cable is yellow; while the other half is green.

Protection path

A specific path that is part of a protection group and is labeled protection.

Protocol Independent A protocol for efficiently routing to multicast groups that may span wide-area (and interMulticast-Sparse Mode domain) internets. This protocol is named protocol independent because it is not dependent on any particular unicast routing protocol for topology discovery, and sparsemode because it is suitable for groups where a very low percentage of the nodes (and their routers) will subscribe to the multicast session. Unlike earlier dense-mode multicast routing protocols such as DVMRP and PIM-DM which flooded packets everywhere and then pruned off branches where there were no receivers, PIM-SM explicitly constructs a tree from each sender to the receivers in the multicast group. Multicast packets from the sender then follow this tree. Provider Edge

A device that is located in the backbone network of the MPLS VPN structure. A PE is responsible for VPN user management, establishment of LSPs between PEs, and exchange of routing information between sites of the same VPN. During the process, a PE performs the mapping and forwarding of packets between the private network and the public channel. A PE can be a UPE, an SPE, or an NPE.

Pseudo wire

An emulated connection between two PEs for transmitting frames. The PW is established and maintained by PEs through signaling protocols. The status information of a PW is maintained by the two end PEs of a PW.

Pseudo Wire Emulation Edge-toEdge

Pseudo-Wire Emulation Edge to Edge (PWE3) is a type of end-to-end Layer 2 transmitting technology. It emulates the essential attributes of a telecommunication service such as ATM, FR or Ethernet in a Packet Switched Network (PSN). PWE3 also emulates the essential attributes of low speed Time Division Multiplexed (TDM) circuit and SONET/SDH. The simulation approximates to the real situation.

PSN

See packet switched network

PTN

Packet Transport Network

PW

See Pseudo wire

PWE3

See Pseudo Wire Emulation Edge-to-Edge

Q QoS

See Quality of Service

QPSK

See Quadrature Phase Shift Keying

Quadrature Phase Shift Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmission Keying through the conversion or modulation and the phase determination of the reference signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are evenly distributed on a circle. On these phases, each QPSK character can perform two-bit coding and display the codes in Gray code on graph with the minimum BER. B-24


Issue 03 (2010-05-30)


Quality of Service

B Glossary

Quality of Service, which determines the satisfaction of a subscriber for a service. QoS is influenced by the following factors applicable to all services: service operability, service accessibility, service maintainability, and service integrity.

R Radio Freqency

A type of electric current in the wireless network using AC antennas to create an electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave. The AC with the frequency lower than 1 kHz is called low-frequency current. The AC with frequency higher than 10 kHz is called high-frequency current. RF can be classified into such high-frequency current.

Radio Network Controller

A device used in the RNS to control the usage and integrity of radio resources.

Random Early Detection

A packet loss algorithm used in congestion avoidance. It discards the packet according to the specified higher limit and lower limit of a queue so that global TCP synchronization resulted in traditional Tail-Drop can be prevented.

Rapid Spanning Tree Protocol

An evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change. The RSTP protocol is backward compatible with the STP protocol.

RDI

See Remote Defect Indication

Received Signal Strength Indicator

The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD within a specified timeslot. The reference point for the measurement shall be the antenna

Receiver Sensitivity

Receiver sensitivity is defined as the minimum acceptable value of average received power at point R to achieve a 1 x 10-10 BER.

RED

See Random Early Detection

REI

See Remote Error Indication

Remote Defect Indication

A signal transmitted at the first opportunity in the outgoing direction when a terminal detects specific defects in the incoming signal.

Remote Error Indication

A remote error indication (REI) is sent upstream to signal an error condition. There are two types of REI alarms: Remote error indication line (REI-L) is sent to the upstream LTE when errors are detected in the B2 byte. Remote error indication path (REI-P) is sent to the upstream PTE when errors are detected in the B3 byte.

remote network monitoring

A manage information base (MIB) defined by the Internet Engineering Task Force (IETF). RMON is mainly used to monitor the data flow of one network segment or the entire network.

Resource Reservation Protocol

The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. RSVP is a network control protocol like Internet Control Message Protocol (ICMP).

Reverse pressure

A traffic control method. In telecommunication, when detecting that the transmit end transmits a large volume of traffic, the receive end sends signals to ask the transmit end to slow down the transmission rate.

RF

See Radio Freqency

RFC

Request For Comment

Issue 03 (2010-05-30)


B-25


B Glossary

RIP

See Routing Information Protocol

RMON

See remote network monitoring

RNC

See Radio Network Controller

Root alarm

An alarm directly caused by anomaly events or faults in the network. Some lower-level alarms always accompany a root alarm.

route

A route is the path that network traffic takes from its source to its destination. In a TCP/ IP network, each IP packet is routed independently. Routes can change dynamically.

Routing Information Protocol

Routing Information Protocol: A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route based on the smallest hop count between source and destination. RIP is a distance vector protocol that routinely broadcasts routing information to its neighboring routers and is known to waste bandwidth.

routing table

A table that stores and updates the locations (addresses) of network devices. Routers regularly share routing table information to be up to date. A router relies on the destination address and on the information in the table that gives the possible routes--in hops or in number of jumps--between itself, intervening routers, and the destination. Routing tables are updated frequently as new information is available.

RS

Reed-Solomon encoding

RSL

Received Signal Level

RSSI

See Received Signal Strength Indicator

RSTP

See Rapid Spanning Tree Protocol

RSVP

See Resource Reservation Protocol

RTN

Radio Transmission Node

S SD

See space diversity

SDH

See Synchronous Digital Hierarchy

SDP

Serious Disturbance Period

SEMF

Synchronous Equipment Management Function

Service Level Agreement

A management-documented agreement that defines the relationship between service provider and its customer. It also provides specific, quantifiable information about measuring and evaluating the delivery of services. The SLA details the specific operating and support requirements for each service provided. It protects the service provider and customer and allows the service provider to provide evidence that it has achieved the documented target measure.

SES

Severely Errored Second

Setup Priority

The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the tunnel can preempt the resources required by other backup tunnels.

SF

See Signal Fail

SFP

See Small Form-Factor Pluggable

B-26


Issue 03 (2010-05-30)


B Glossary

side trough

The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet.

signal cable

Common signal cables cover the E1cable, network cable, and other non-subscriber signal cable.

Signal Fail

SF is a signal indicating the associated data has failed in the sense that a near-end defect condition (not being the degraded defect) is active.

Signal Noise Ratio

The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel).

Simple Network Management Protocol

A network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. This protocol ensures the transmission of management information between any two points. The polling mechanism is adopted to provide basic function sets. According to SNMP, agents, which can be hardware as well as software, can monitor the activities of various devices on the network and report these activities to the network console workstation. Control information about each device is maintained by a management information block.

simplex

Of or relating to a telecommunications system in which only one message can be sent in either direction at one time.

SLA

See Service Level Agreement

Slicing

To divide data into the information units proper for transmission.

Small Form-Factor Pluggable

A specification for a new generation of optical modular transceivers.

SNC

See SubNetwork Connection

SNCP

See SubNetwork Connection Protection

SNMP

See Simple Network Management Protocol

SNR

See Signal Noise Ratio

SP

Strict Priority

space diversity

A diversity scheme that enables two or more antennas separated by a specific distance to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Currently, only receive SD is used.

Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant network to block some undesirable redundant paths through certain algorithms and prune a loop network into a loop-free tree network. SSM

See Synchronization Status Message

Static Virtual Circuit

Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPN information by manual configuration of VC labels, instead of by a signaling protocol.

Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be transmitted across a single physical channel. It dynamically allocates bandwidth only to active input channels, to make better use of available bandwidth and allow more devices to be connected than with other multiplexing techniques. Compare with TDM. STM

See synchronous transport module

STM-1

SDH Transport Module -1

Issue 03 (2010-05-30)


B-27


B Glossary

STM-1e

STM-1 Electrical Interface

STM-1o

STM-1 Optical Interface

STP

See Spanning Tree Protocol

sub-network

Sub-network is the logical entity in the transmission network and comprises a group of network management objects. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a sub-network is used to contain the equipments which are located in adjacent regions and closely related with one another, and it is indicated with a sub-network icon on a topological view. The U2000 supports multilevels of sub-networks. A sub-network planning can better the organization of a network view. On the one hand, the view space can be saved, on the other hand, it helps the network management personnel focus on the equipments under their management.

subnet mask

The technique used by the IP protocol to determine which network segment packets are destined for. The subnet mask is a binary pattern that is stored in the client machine, server or router and is matched with the IP address.

SubNetwork Connection

A "transport entity" that transfers information across a subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork.

SubNetwork A working subnetwork connection is replaced by a protection subnetwork connection if Connection Protection the working subnetwork connection fails, or if its performance falls below a required level. SVC

See Static Virtual Circuit

SVL

Shared VLAN Learning

Switch

To filter, forward frames based on label or the destination address of each frame. This behavior operates at the data link layer of the OSI model.

Synchronization Status A message that is used to transmit the quality levels of timing signals on the synchronous Message timing link. Through this message, the node clocks of the SDH network and the synchronization network can aquire upper stream clock information, and the two perform operations on the corresponding clocks, such as tracing, switchover, or converting hold), and then forward the synchronization information of this node to down stream. Synchronous Digital Hierarchy

SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is only used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure.

synchronous transport An STM is the information structure used to support section layer connections in the SDH. It consists of information payload and Section Overhead (SOH) information fields module organized in a block frame structure which repeats every 125 . The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.

B-28


Issue 03 (2010-05-30)


B Glossary

T tail drop

A type of QoS. When a queue within a network router reaches its maximum length, packet drops can occur. When a packet drop occurs, connection-based protocols such as TCP slow down their transmission rates in an attempt to let queued packets be serviced, thereby letting the queue empty. This is also known as tail drop because packets are dropped from the input end (tail) of the queue.

Tail drop

A congestion management mechanism, in which packets arrive later are discarded when the queue is full. This policy of discarding packets may result in network-wide synchronization due to the TCP slow startup mechanism.

TCI

Tag Control Information

TCP

See TransmissionControl Protocol

TDM

See Time Division Multiplexing

TE

See traffic engineering

TEDB

See Traffic Engineering DataBase

Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T Management Network for managing open systems in a communications network.An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services. TIM

Trace Identifier Mismatch

Time Division Multiplexing

It is a multiplexing technology. TDM divides the sampling cycle of a channel into time slots (TSn, n=0, 1, 2, 3......), and the sampling value codes of multiple signals engross time slots in a certain order, forming multiple multiplexing digital signals to be transmitted over one channel.

Time To Live

A technique used in best-effort delivery systems to prevent packets that loop endlessly. The TTL is set by the sender to the maximum time the packet is allowed to be in the network. Each router in the network decrements the TTL field when the packet arrives, and discards any packet if the TTL counter reaches zero.

TMN

See Telecommunication Management Network

ToS priority

A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header.

TPS

See Tributary Protection Switch

traffic engineering

A task that effectively maps the service flows to the existing physical topology.

Traffic Engineering DataBase

TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to know the features of the dynamic TE of every links by expanding the current IGP, which uses the link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS contain some TE features, such as the link bandwidth and color. The maximum reserved bandwidth of the link and the unreserved bandwidth of every link with priority are rather important. Every router collects the information about TE of every links in its area and generates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLS TE network.

Traffic shaping

It is a way of controlling the network traffic from a computer to optimize or guarantee the performance and minimize the delay. It actively adjusts the output speed of traffic in the scenario that the traffic matches network resources provided by the lower layer devices, avoiding packet loss and congestion.

Issue 03 (2010-05-30)


B-29


B Glossary

trail

A type of transport entity, mainly engaged in transferring signals from the input of the trail source to the output of the trail sink, and monitoring the integrality of the transferred signals.

TransmissionControl Protocol

The protocol within TCP/IP that governs the breakup of data messages into packets to be sent via IP (Internet Protocol), and the reassembly and verification of the complete messages from packets received by IP. A connection-oriented, reliable protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in the ISO/OSI reference model.

Tributary Protection Switch

Tributary protection switching, a function provided by the equipment, is intended to protect N tributary processing boards through a standby tributary processing board.

trTCM

See Two Rate Three Color Marker

TTL

See Time To Live

TU

Tributary Unit

Tunnel

A channel on the packet switching network that transmits service traffic between PEs. In VPN, a tunnel is an information transmission channel between two entities. The tunnel ensures secure and transparent transmission of VPN information. In most cases, a tunnel is an MPLS tunnel.

Two Rate Three Color The trTCM meters an IP packet stream and marks its packets based on two rates, Peak Marker Information Rate (PIR) and Committed Information Rate (CIR), and their associated burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the CIR.

B.6 U-Z U UAS

Unavailable Second

UBR

See Unspecified Bit Rate

UDP

See User Datagram Protocol

underfloor cabling

The cables connected cabinets and other devices are routed underfloor.

UNI

See User Network Interface

Unicast

The process of sending data from a source to a single recipient.

Unspecified Bit Rate

No commitment to transmission. No feedback to congestion. This type of service is ideal for the transmission of IP datagrams. In case of congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the sender.

Upper subrack

The subrack close to the top of the cabinet when a cabinet contains several subracks.

UPS

Uninterruptible Power Supply

upward cabling

Cables or fibres connect the cabinet with other equipment from the top of the cabinet.

B-30


Issue 03 (2010-05-30)


User Datagram Protocol

B Glossary

A TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User Datagram Protocol (UDP) uses IP to deliver datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDP messages can be lost, duplicated, delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is, the destination device does not actively confirm whether the correct data packet is received.

User Network Interface A type of ATM Forum specification that defines an interoperability standard for the interface between ATM-based products (a router or an ATM switch) located in a private network and the ATM switches located within the public carrier networks. Also used to describe similar connections in Frame Relay networks.

V V-NNI

See virtual network-network interface

V-UNI

See Virtual User-Network Interface

Variable Bit Rate

One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth and is better suited to non real time transfers than to real-time streams such as voice calls.

VBR

See Variable Bit Rate

VC

See Virtual Channel

VC-12

Virtual Container -12

VC-3


VC-4


VCC

Virtual Channel Connection

VCC,VPL

See Virtual Chanel Connection

VCG

See virtual concatenation group

VCI

See Virtual Channel Identifier

Virtual Chanel Connection

Virtual Channel Connection. The VC logical trail that carries data between two end points in an ATM network. A logical grouping of multiple virtual channel connections into one virtual connection.

Virtual Channel

Any logical connection in the ATM network. A VC is the basic unit of switching in the ATM network uniquely identified by a virtual path identifier (VPI)/virtual channel identifier (VCI) value. It is the channel on which ATM cells are transmitted by the sw

Virtual Channel Identifier

virtual channel identifier. A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination.

virtual concatenation group

A group of co-located member trail termination functions that are connected to the same virtual concatenation link

Virtual Leased Line

A point-to-point, layer-2 channel that behaves like a leased line by transparently transporting different protocols with a guaranteed throughput.

Issue 03 (2010-05-30)


B-31


B Glossary

Virtual Local Area Network

A logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number. This is often associated with switched Ethernet.

virtual networknetwork interface

A virtual network-network interface (V-NNI) is a network-side interface.

Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs. Virtual Private LAN Service

A type of point-to-multipoint L2VPN service provided over the public network. VPLS enables geographically isolated user sites to communicate with each other through the MAN/WAN as if they are on the same LAN.

Virtual Private Network

The extension of a private network that encompasses encapsulated, encrypted, and authenticated links across shared or public networks. VPN connections can provide remote access and routed connections to private networks over the Internet.

Virtual Private Wire Service

A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR, Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.

Virtual Routing and Forwarding

A technology included in IP (Internet Protocol) network routers that allows multiple instances of a routing table to exist in a router and work simultaneously.

Virtual Switch Instance An instance through which the physical access links of VPLS can be mapped to the virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge function and can terminate PW. Virtual User-Network Interface

virtual user-network interface. A virtual user-network interface, works as an action point to perform service claissification and traffic control in HQoS.

VLAN

See Virtual Local Area Network

VLL

See Virtual Leased Line

Voice over IP

An IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. VoIP involves sending voice information in a digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (PSTN).

VoIP

See Voice over IP

VPI

See Virtual Path Identifier

VPLS

See Virtual Private LAN Service

VPN

See Virtual Private Network

VPWS

See Virtual Private Wire Service

VRF

See Virtual Routing and Forwarding

VSI

See Virtual Switch Instance

W Wait to Restore Time

A period of time that must elapse before a - from a fault recovered - trail/connection can be used again to transport the normal traffic signal and/or to select the normal traffic signal from.

WAN

See Wide Area Network

B-32


Issue 03 (2010-05-30)


Web LCT

B Glossary

The local maintenance terminal of a transport network, which is located on the NE management layer of the transport network

Weighted Fair Queuing Weighted Fair Queuing (WFQ) is a fair queue scheduling algorithm based on bandwidth allocation weights. This scheduling algorithm allocates the total bandwidth of an interface to queues, according to their weights and schedules the queues cyclically. In this manner, packets of all priority queues can be scheduled. Weighted Random Early Detection

A packet loss algorithm used for congestion avoidance. It can prevent the global TCP synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio.

WFQ

See Weighted Fair Queuing

Wide Area Network

A network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broad area, such as a province, a state or even a country.

Winding pipe

A tool for fiber routing, which acts as the corrugated pipe.

wire speed

Wire speed refers to the maximum packet forwarding capacity on a cable. The value of wire speed equals the maximum transmission rate capable on a given type of media.

WMS

Wholesale Managed Services

WRED

See Weighted Random Early Detection

WRR

Weighted Round Robin

WTR

See Wait to Restore Time

X XPD

Cross-Polarization Discrimination

XPIC

See cross polarization interference cancellation

Issue 03 (2010-05-30)


B-33

OptiX RTN 605 Radio Transmission System V100R005C00 Configuration Guide

Recommend Documents