Sie sind auf Seite 1von 1089

iManager U2000 Unified Network Management System V100R002C01

Operation Guide for RTN NE Management


Issue Date 02 2010-09-24

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 http://www.huawei.com support@huawei.com

Website: Email:

Issue 02 (2010-09-24)

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

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

About This Document

About This Document


Related Version
The following table lists the product version related to this document. Product Name iManager U2000 Version V100R002C01

Intended Audience
This document describes the operations, such as how to configure the communication, clock and service of the RTN equipment on the U2000. This document also provides the glossary and the acronyms and abbreviations. This document guides the user to understand basic operations of the U2000. This document is intended for: l l l l Network Monitoring Engineer Data Configuration Engineer NMS Administrators System Maintenance Engineer

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

DANGER

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.

WARNING
Issue 02 (2010-09-24)

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

iii

About This Document

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Symbol

Description

CAUTION
TIP

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.

NOTE

Command Conventions
The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

[ x | y | ... ]*

GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

iv

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

About This Document

Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.

Updates in Issue 02 (2010-09-24) Based on Product Version V100R002C01


The second release of the iManager U2000 V100R002C01. Some bugs in the manual of the previous version are fixed.

Updates in Issue 01 (2010-08-16) Based on Product Version V100R002C01


The first release of the iManager U2000 V100R002C01.

Issue 02 (2010-09-24)

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

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

Contents
About This Document...................................................................................................................iii 1 Creating NEs, Links, and Topology Subnets........................................................................1-1
1.1 Creating NEs...................................................................................................................................................1-2 1.1.1 Creating NEs in Batches........................................................................................................................1-2 1.1.2 Creating a Single NE..............................................................................................................................1-4 1.2 Configuring the NE Data.................................................................................................................................1-5 1.2.1 Configuring the NE Data Manually.......................................................................................................1-6 1.2.2 Replicating the NE Data.........................................................................................................................1-7 1.2.3 Uploading the NE Data..........................................................................................................................1-8 1.3 Checking Board Parameters............................................................................................................................1-8 1.4 Creating Links...............................................................................................................................................1-13 1.4.1 Creating Fibers Automatically.............................................................................................................1-13 1.4.2 Automatically Creating Radio Links....................................................................................................1-15 1.4.3 Manually Creating Radio Links...........................................................................................................1-16 1.5 Creating a Topology Subnet..........................................................................................................................1-16

2 DCN Management.....................................................................................................................2-1
2.1 DCN Overview................................................................................................................................................2-3 2.1.1 Background of DCN...............................................................................................................................2-4 2.1.2 DCN Solutions.......................................................................................................................................2-5 2.1.3 HWECC Features and Functions...........................................................................................................2-5 2.1.4 HWECC Application..............................................................................................................................2-6 2.1.5 Basic Concepts of IP over DCC.............................................................................................................2-7 2.1.6 Features and Functions of IP over DCC.................................................................................................2-8 2.1.7 Application of IP over DCC...................................................................................................................2-8 2.1.8 Basic Concepts of OSI over DCC........................................................................................................2-12 2.1.9 Features and Functions of OSI over DCC............................................................................................2-13 2.1.10 Application of OSI over DCC............................................................................................................2-13 2.2 DCN Management Flow...............................................................................................................................2-15 2.3 Configuring ECC Communication................................................................................................................2-16 2.3.1 Modifying the NE ID...........................................................................................................................2-17 2.3.2 Configuring an Extended ECC Communication..................................................................................2-18 2.3.3 Viewing the ECC Route for an NE......................................................................................................2-19 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 2.3.4 Adding the Manual ECC Route for an NE...........................................................................................2-20 2.3.5 Customizing Communication Channels Between NEs........................................................................2-20 2.3.6 Configuring Communication for Third-Party Equipment Interconnection..........................................2-21

2.4 Configuring IP Over DCC Communication..................................................................................................2-21 2.4.1 Modifying the NE ID...........................................................................................................................2-22 2.4.2 Setting NE Communication Parameters...............................................................................................2-23 2.4.3 Configuring the IP Static Route for an NE..........................................................................................2-23 2.4.4 Customizing Communication Channels Between NEs........................................................................2-24 2.4.5 Viewing the Communication Status of DCC Channel.........................................................................2-24 2.4.6 Querying the OSPF Protocol Status.....................................................................................................2-25 2.4.7 Configuring Proxy ARP.......................................................................................................................2-25 2.5 Configuring OSI Over DCC Communication...............................................................................................2-25 2.5.1 Modifying the NE ID...........................................................................................................................2-26 2.5.2 Setting the NSAP Address for an NE...................................................................................................2-27 2.5.3 Configuring the Node Type for an NE.................................................................................................2-28 2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port........................2-29 2.5.5 Configuring OSI Tunnel.......................................................................................................................2-29 2.5.6 Customizing Communication Channels Between NEs........................................................................2-30 2.5.7 Querying the Route Information of a Node.........................................................................................2-30 2.5.8 Creating an OSI GNE...........................................................................................................................2-31 2.6 Configuring DCC Transparent Transmission...............................................................................................2-31 2.6.1 Configuring Communication for Third-Party Equipment Interconnection..........................................2-32 2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces..............................2-33 2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces.........................................2-35 2.7 Modifying GNE Parameters..........................................................................................................................2-35 2.8 Changing the GNE for NEs...........................................................................................................................2-36 2.9 Configuring Standby GNEs for NEs.............................................................................................................2-37 2.10 Changing a GNE to a Normal NE...............................................................................................................2-38 2.11 Changing a Normal NE to a GNE...............................................................................................................2-39 2.12 Checking GNE Switching Status................................................................................................................2-39 2.13 Testing the Communication Between the U2000 and the GNE..................................................................2-39 2.14 Checking the Network Communication Status...........................................................................................2-40 2.14.1 Overview of the Inband DCN............................................................................................................2-41 2.14.2 Basic Concepts...................................................................................................................................2-42 2.14.3 Application of the Inband DCN.........................................................................................................2-43 2.14.4 Configuring an Inband DCN..............................................................................................................2-43 2.14.4.1 Setting NE Communication Parameters..........................................................................................2-44 2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN....................................................2-45 2.14.4.3 Setting the U2000 Access Parameters.............................................................................................2-45 2.14.4.4 Enabling the Port DCN...................................................................................................................2-46 2.14.4.5 Enabling the Tunnel DCN...............................................................................................................2-47

3 Configuring Clocks....................................................................................................................3-1
viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

3.1 Clock Configuration Process...........................................................................................................................3-3 3.2 Clock Synchronization Scheme...................................................................................................................... 3-4 3.3 Basic Concepts................................................................................................................................................3-8 3.3.1 Clock Synchronization...........................................................................................................................3-9 3.3.2 SSM Protocol and Clock ID.................................................................................................................3-10 3.3.3 Clock Subnet........................................................................................................................................3-13 3.3.4 Clock Protection...................................................................................................................................3-13 3.4 Viewing Clock Synchronization Status.........................................................................................................3-14 3.5 Viewing the Clock Tracing Status................................................................................................................3-14 3.6 Configuring the Clock Sources.....................................................................................................................3-15 3.7 Configuring Protection for Clock Sources ...................................................................................................3-17 3.8 Configuring Switching Conditions for Clock Sources..................................................................................3-20 3.9 Configuring the Clock Source Reversion......................................................................................................3-20 3.10 Modifying the Parameters of the External Clock Output............................................................................3-21 3.11 Setting the Clock Source Quality................................................................................................................3-22 3.12 Configuring the SSM Output......................................................................................................................3-23 3.13 Configuring the Ethernet Clock Source......................................................................................................3-24 3.14 Viewing the Clock Tracing Status..............................................................................................................3-24 3.15 Checking the Clock Switching Status.........................................................................................................3-25 3.16 Switching a Clock Source...........................................................................................................................3-25

4 Configuring PTP Clock.............................................................................................................4-1


4.1 Introduction to the PTP Clock.........................................................................................................................4-2 4.2 Basic Information............................................................................................................................................4-3 4.3 Application of the PTP Clock......................................................................................................................... 4-6 4.4 Configuration Flow for the PTP Clock...........................................................................................................4-7 4.5 Configuring the PTP Clock.............................................................................................................................4-9 4.5.1 Setting the Frequency Selection Mode.................................................................................................4-10 4.5.2 Setting the PTP System Time...............................................................................................................4-11 4.5.3 Setting the PTP Clock Subnet..............................................................................................................4-11 4.5.4 Setting the Attributes of the External Time Interface..........................................................................4-12 4.5.5 Setting the PTP NE Attributes.............................................................................................................4-13 4.5.6 Creating the PTP Clock Port................................................................................................................4-14 4.5.7 Creating the PTP Clock Service...........................................................................................................4-14 4.5.8 Setting the PTP Packet Period..............................................................................................................4-16 4.5.9 Setting the PTP Clock Port Status........................................................................................................4-17 4.5.10 Setting the Cable Transmitting Wrap.................................................................................................4-18 4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source............................................................4-19 4.5.12 Setting the PTP Clock Source Priority...............................................................................................4-19

5 Configuring Orderwire.............................................................................................................5-1
5.1 Configuring Orderwire....................................................................................................................................5-2 5.2 Configuring F1 Data Port Services................................................................................................................. 5-2 5.2.1 F1 Data Port Services.............................................................................................................................5-2 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 5.2.2 Configuring F1 Data Port Services........................................................................................................5-3

5.3 Configuring Asynchronous Data Services......................................................................................................5-4 5.3.1 Asynchronous Data Services..................................................................................................................5-5 5.3.2 Configuring Asynchronous Data Services.............................................................................................5-5 5.4 Configuration Example (Synchronous Data Services RTN 600)....................................................................5-6 5.4.1 Networking Diagram..............................................................................................................................5-7 5.4.2 Service Planning.....................................................................................................................................5-7 5.4.3 Configuration Process............................................................................................................................5-9 5.5 Configuration Example (Asynchronous Data Services RTN 600)...............................................................5-10 5.5.1 Networking Diagram............................................................................................................................5-11 5.5.2 Service Planning...................................................................................................................................5-11 5.5.3 Configuration Process..........................................................................................................................5-13

6 Configuring Environment Monitor Interfaces.....................................................................6-1


6.1 Configuring External Alarms..........................................................................................................................6-2 6.2 Configuration Example (External Alarms RTN 600).....................................................................................6-3 6.2.1 Networking Diagram..............................................................................................................................6-3 6.2.2 Service Planning.....................................................................................................................................6-4 6.2.3 Configuration Process............................................................................................................................6-5

7 Configuring Interfaces (RTN 600)...........................................................................................7-1


7.1 Checking Board Parameters............................................................................................................................7-2 7.2 Configuring the Parameters of Various Ports ................................................................................................7-6 7.2.1 Configuring the Parameters of SDH Interfaces .....................................................................................7-6 7.2.2 Configuring the Parameters of PDH Interfaces .....................................................................................7-8 7.2.3 Setting the Parameters of IF Ports........................................................................................................7-11 7.2.4 Setting the Parameters of ODU Ports...................................................................................................7-17 7.3 Configuring Ethernet Ports............................................................................................................................7-20 7.3.1 Configuring External Ethernet Ports....................................................................................................7-20 7.3.2 Configuring the Internal Port of the Ethernet Board............................................................................7-29 7.3.3 Modifying the Type Field of Jumbo Frames........................................................................................7-36 7.3.4 Modifying the Type Field of QinQ Frames.........................................................................................7-37 7.3.5 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth........................................................7-38 7.4 Disabling an Ethernet Port............................................................................................................................7-39 7.5 Configuring a Service Load Indication.........................................................................................................7-40

8 Configuring Interfaces (RTN 900)...........................................................................................8-1


8.1 Configuring SDH Interfaces............................................................................................................................8-3 8.1.1 Setting the General Attributes of SDH Interfaces..................................................................................8-3 8.1.2 Setting the Advanced Attributes of SDH Interfaces..............................................................................8-4 8.1.3 Querying the Running Status of PPP.....................................................................................................8-4 8.1.4 Resetting the PPP...................................................................................................................................8-5 8.2 Configuring PDH Interfaces............................................................................................................................8-5 8.2.1 Setting General Attributes of PDH Interfaces........................................................................................8-7 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

8.2.2 Setting the Layer 3 Attributes of PDH Interfaces..................................................................................8-8 8.2.3 Setting the Advanced Attributes of PDH Interfaces.............................................................................. 8-8 8.2.4 Querying the Running Status of PPP..................................................................................................... 8-9 8.2.5 Resetting the PPP...................................................................................................................................8-9 8.3 Configuring Ethernet Interfaces....................................................................................................................8-10 8.3.1 Setting the General Attributes of Ethernet Interfaces..........................................................................8-11 8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces...........................................................................8-11 8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface........................................................................8-12 8.3.4 Setting the Advanced Attributes of Ethernet Interfaces.......................................................................8-13 8.3.5 Configuring Flow Control....................................................................................................................8-13 8.4 Configuring Microwave Interfaces...............................................................................................................8-14 8.4.1 Setting the General Attributes of Microwave Interfaces......................................................................8-16 8.4.2 Setting the IF Attributes of Microwave Interfaces...............................................................................8-17 8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces......................................................................8-17 8.4.4 Setting the Layer 3 Attributes of Microwave Interfaces......................................................................8-18 8.4.5 Setting the Advanced Attributes of Microwave Interfaces..................................................................8-19 8.4.6 Setting the Parameters of ODU Ports(RTN900V1R1)........................................................................8-19 8.4.7 Setting the Parameters of ODU Ports(RTN900V1R2)........................................................................8-21 8.5 Configuring Serial Interfaces........................................................................................................................8-24 8.5.1 Creating Serial Interfaces.....................................................................................................................8-24 8.5.2 Setting the General Attributes of a Serial Interface.............................................................................8-25 8.5.3 Setting the Layer 3 Attributes of Serial Interfaces...............................................................................8-25 8.5.4 Querying the Running Status of PPP...................................................................................................8-26 8.5.5 Resetting the PPP.................................................................................................................................8-26 8.6 Configuring ML-PPP....................................................................................................................................8-27 8.6.1 Overview of the ML-PPP.....................................................................................................................8-29 8.6.2 Basic Concepts.....................................................................................................................................8-29 8.6.3 ML-PPP Application............................................................................................................................8-30 8.6.4 Creating MP Groups.............................................................................................................................8-31 8.6.5 Configuring Member Interfaces of MP Groups...................................................................................8-31 8.7 Configuring an Ethernet Virtual Interface.....................................................................................................8-32 8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces..............................................................8-32 8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces..............................................................8-33 8.8 Configuring an IMA Group...........................................................................................................................8-33 8.8.1 Configuring Bound Channels in an ATM IMA Group........................................................................8-35 8.8.2 Configuring Attributes of an ATM IMA Group..................................................................................8-36 8.8.3 Configuring ATM Interface Attributes................................................................................................8-36 8.8.4 Querying IMA Group States................................................................................................................8-37 8.8.5 Querying IMA Link States...................................................................................................................8-37 8.8.6 Resetting an IMA Group......................................................................................................................8-38 8.8.7 Modifying an IMA Group....................................................................................................................8-38 8.8.8 Deleting an IMA Group.......................................................................................................................8-39 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links..........................................................................................................9-1


9.1 Radio Link.......................................................................................................................................................9-2 9.2 Configuring the IF/ODU Information of a Radio Link...................................................................................9-2 9.3 Configuring the ATPC Function.....................................................................................................................9-8 9.4 Creating an XPIC Workgroup.......................................................................................................................9-11 9.5 Configuring the Hybrid/AM Attribute..........................................................................................................9-13 9.6 Hop Management..........................................................................................................................................9-13 9.6.1 Introduction to the Hop Management..................................................................................................9-14 9.6.2 Starting HOP Management..................................................................................................................9-14

10 Configuring Board 1+1 Protection......................................................................................10-1


10.1 Querying Board 1+1 Protection Group.......................................................................................................10-2 10.2 Verifying the Board 1+1 Protection Switching...........................................................................................10-2

11 Configuring the IF 1+1 Protection...................................................................................... 11-1


11.1 1+1 HSB......................................................................................................................................................11-2 11.1.1 Feature Description............................................................................................................................11-2 11.1.2 Availability.........................................................................................................................................11-2 11.1.3 Relation with Other Features..............................................................................................................11-3 11.1.4 Realization Principle..........................................................................................................................11-3 11.1.4.1 SDH/PDH Microwave.....................................................................................................................11-4 11.1.4.2 Hybrid Microwave..........................................................................................................................11-6 11.1.5 Planning Guide...................................................................................................................................11-9 11.2 1+1 FD.........................................................................................................................................................11-9 11.2.1 Feature Description..........................................................................................................................11-10 11.2.2 Availability.......................................................................................................................................11-10 11.2.3 Relation with Other Features............................................................................................................11-11 11.2.4 Realization Principle........................................................................................................................11-11 11.2.4.1 SDH/PDH Microwave...................................................................................................................11-11 11.2.4.2 Hybrid Microwave........................................................................................................................11-14 11.2.5 Planning Guide.................................................................................................................................11-17 11.3 1+1 SD.......................................................................................................................................................11-18 11.3.1 Feature Description..........................................................................................................................11-18 11.3.2 Availability.......................................................................................................................................11-19 11.3.3 Relation with Other Features............................................................................................................11-19 11.3.4 Realization Principle........................................................................................................................11-20 11.3.4.1 SDH/PDH Microwave...................................................................................................................11-20 11.3.4.2 Hybrid Microwave........................................................................................................................11-22 11.3.5 Planning Guide.................................................................................................................................11-26 11.4 Creating IF 1+1 Protection........................................................................................................................11-27 11.5 Modifying the Parameters of IF 1+1 Protection........................................................................................11-28

12 Configuring Network Level Protection.............................................................................12-1


12.1 Basic Concept..............................................................................................................................................12-3 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

12.1.1 Multiplex Section...............................................................................................................................12-3 12.1.2 MSP Protection Switching Priority....................................................................................................12-4 12.1.3 SNCP Protection................................................................................................................................12-6 12.1.4 N+1 Protection...................................................................................................................................12-9 12.2 Configuring N+1 Protection......................................................................................................................12-10 12.2.1 Feature Description..........................................................................................................................12-11 12.2.2 Availability.......................................................................................................................................12-13 12.2.3 Realization Principle........................................................................................................................12-13 12.2.3.1 2+1 Protection Configuration........................................................................................................12-13 12.2.3.2 3+1 Protection Configuration........................................................................................................12-15 12.2.4 Configuration Guide.........................................................................................................................12-17 12.2.4.1 Configuration Flow.......................................................................................................................12-17 12.2.4.2 Creating REGs...............................................................................................................................12-18 12.2.4.3 Creating an N+1 Protection Group................................................................................................12-21 12.2.4.4 Enabling the N+1 Protection Control Protocol.............................................................................12-23 12.2.4.5 Verifying the N+1 Protection Switching.......................................................................................12-24 12.3 Configuring Linear Multiplex Section Protection.....................................................................................12-25 12.3.1 Feature Description..........................................................................................................................12-25 12.3.1.1 Protection Type.............................................................................................................................12-27 12.3.2 Availability.......................................................................................................................................12-28 12.3.3 Realization Principle........................................................................................................................12-29 12.3.3.1 1+1 Linear MSP............................................................................................................................12-29 12.3.3.2 1:N Linear MSP............................................................................................................................12-31 12.3.4 Configuration Guide.........................................................................................................................12-32 12.3.4.1 Creating Linear MSP.....................................................................................................................12-32 12.3.4.2 Verifying Linear MSP Switching..................................................................................................12-36 12.3.4.3 Setting an MS Node Number........................................................................................................12-37 12.4 Configuring Two-Fiber Bidirectional Ring MSP......................................................................................12-38 12.4.1 Feature Description..........................................................................................................................12-38 12.4.2 Availability.......................................................................................................................................12-40 12.4.3 Realization Principle........................................................................................................................12-40 12.4.3.1 Configuring the Ring MSP............................................................................................................12-42 12.5 Configuring Sub-Network Connection Protection....................................................................................12-45 12.5.1 Feature Description..........................................................................................................................12-45 12.5.2 Availability.......................................................................................................................................12-47 12.5.3 Realization Principle........................................................................................................................12-47 12.5.4 Configuration Guide.........................................................................................................................12-48 12.5.4.1 Creating Cross-Connections for SNCP Services..........................................................................12-49 12.5.4.2 Setting SNCP Service Control Attributes.....................................................................................12-53 12.5.4.3 Setting the Automatic Switching Conditions of SNCP Services..................................................12-54 12.5.4.4 Verifying the SNCP Service Switching........................................................................................12-55 12.5.4.5 Converting Non-Protection Services into SNCP Services............................................................12-56 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 12.5.4.6 Converting SNCP Services into Non-Protection Services............................................................12-60

12.6 Configuring MPLS Tunnel Protection......................................................................................................12-60 12.6.1 Introduction to MPLS APS..............................................................................................................12-61 12.6.2 Basic Concepts.................................................................................................................................12-64 12.6.3 MPLS APS Application...................................................................................................................12-65 12.6.4 Creating an MPLS Tunnel Protection Group...................................................................................12-67 12.6.5 Perform MPLS Tunnel Protection Switching..................................................................................12-69 12.6.6 Deleting an MPLS Tunnel Protection Group...................................................................................12-70 12.7 Ethernet Ring Protection...........................................................................................................................12-70 12.7.1 Introduction to Ethernet Ring Protection.........................................................................................12-71 12.7.2 Basic Concepts.................................................................................................................................12-71 12.7.3 Availability.......................................................................................................................................12-74 12.7.4 Function Implementation.................................................................................................................12-74 12.7.5 Application of Ethernet Ring Protection..........................................................................................12-78 12.7.6 Configuring Ethernet Ring Protection..............................................................................................12-79 12.7.6.1 Configuration Rules......................................................................................................................12-80 12.7.6.2 Creating Ethernet Ring Protection................................................................................................12-80 12.7.6.3 Modifying Parameters of Ethernet Ring Protection......................................................................12-80 12.8 Configuring Link Aggregation..................................................................................................................12-81 12.8.1 Overview..........................................................................................................................................12-81 12.8.2 Availability.......................................................................................................................................12-83 12.8.3 Principle...........................................................................................................................................12-84 12.8.4 Configuration Guide.........................................................................................................................12-85 12.8.4.1 Creating an LAG...........................................................................................................................12-86 12.8.4.2 Modifying LAG Parameters..........................................................................................................12-87 12.8.4.3 Querying Port LACP Packet Statistics..........................................................................................12-87 12.8.4.4 Querying Detailed LAG Information............................................................................................12-88

13 Configuring SDH/PDH Services.........................................................................................13-1


13.1 Numbering Schemes for SDH Timeslots ...................................................................................................13-3 13.2 Configuring E1 Services............................................................................................................................. 13-4 13.3 Configuring Cross-Connections..................................................................................................................13-6 13.3.1 Creating Cross-Connections of Point-to-Point Services....................................................................13-8 13.3.2 Creating Cross-Connections for SNCP Services............................................................................... 13-9 13.3.3 Setting the Automatic Switching Conditions of SNCP Services.....................................................13-14 13.3.4 Deleting the Cross-Connections of a Point-to-Point Service...........................................................13-15 13.3.5 Deleting the Cross-Connections of a Service...................................................................................13-16 13.4 Configuring SNCP Services......................................................................................................................13-17 13.5 Converting Between SNCP and Non-Protection Services........................................................................13-20 13.5.1 Converting Non-Protection Services into SNCP Services...............................................................13-20 13.5.2 Converting SNCP Services into Non-Protection Services...............................................................13-24 13.6 Configuring Overhead Bytes.....................................................................................................................13-24 13.6.1 Configuring RSOHs.........................................................................................................................13-25 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

13.6.2 Configuring VC-4 POHs..................................................................................................................13-26 13.6.3 Configuring VC-3 POHs..................................................................................................................13-30 13.6.4 Configuring VC-12 POHs................................................................................................................13-32 13.7 Configuration Example (Hop Between Two IDU 620s)...........................................................................13-34 13.7.1 Networking Diagram........................................................................................................................13-35 13.7.2 Service Planning...............................................................................................................................13-36 13.7.3 Configuring NE1..............................................................................................................................13-45 13.7.4 Configuring NE2..............................................................................................................................13-49 13.7.5 Configuring NE3..............................................................................................................................13-57 13.7.6 Configuring NE4 .............................................................................................................................13-61 13.7.7 Configuring NE5..............................................................................................................................13-64 13.8 Configuration Example (Hop Between Two IDU 605s)...........................................................................13-64 13.8.1 Networking Diagram........................................................................................................................13-65 13.8.2 Service Planning...............................................................................................................................13-65 13.8.3 Configuring NE1..............................................................................................................................13-69 13.8.4 Configuring NE2..............................................................................................................................13-72 13.9 Configuration Example (Hop between the IDU 605 and the IDU 620)....................................................13-76 13.9.1 Networking Diagram........................................................................................................................13-76 13.9.2 Service Planning...............................................................................................................................13-77 13.9.3 Configuring NE1 to NE4 .................................................................................................................13-80 13.9.4 Configuring NE5..............................................................................................................................13-80

14 Ethernet Feature(RTN 600)...................................................................................................14-1


14.1 Creating Ethernet Services..........................................................................................................................14-2 14.1.1 Basic Concepts...................................................................................................................................14-3 14.1.1.1 Formats of Ethernet Frames............................................................................................................14-3 14.1.1.2 Internal Ports and External Ports.....................................................................................................14-6 14.1.1.3 Auto-Negotiation.............................................................................................................................14-6 14.1.1.4 Flow Control...................................................................................................................................14-8 14.1.1.5 Encapsulation and Mapping Protocol...........................................................................................14-10 14.1.1.6 Virtual Concatenation...................................................................................................................14-10 14.1.1.7 Tag Attributes................................................................................................................................14-12 14.1.1.8 Bridge............................................................................................................................................14-13 14.1.2 Configuring the Cross-Connections of Ethernet Services................................................................14-17 14.1.2.1 Creating Cross-Connections of Ethernet Services........................................................................14-17 14.1.2.2 Deleting the Cross-Connections of an Ethernet Service...............................................................14-17 14.1.3 Configuring EPL Services................................................................................................................14-18 14.1.3.1 EPL Service Configuration Process..............................................................................................14-19 14.1.3.2 Setting Port Attributes and Bound Paths for an Ethernet Board...................................................14-20 14.1.3.3 Creating Ethernet Line Service.....................................................................................................14-20 14.1.3.4 Testing Ethernet Services..............................................................................................................14-25 14.1.3.5 Deleting an Ethernet Private Line Service....................................................................................14-26 14.1.4 Configuring Ethernet LAN Services................................................................................................14-27 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 14.1.4.1 Ethernet LAN Service Configuration Process..............................................................................14-27 14.1.4.2 Setting Port Attributes and Bound Paths for an Ethernet Board...................................................14-28 14.1.4.3 Creating the Ethernet LAN Service...............................................................................................14-29 14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge............................14-33 14.1.4.5 Creating the VLAN Filter Table...................................................................................................14-37 14.1.4.6 Testing Ethernet Services..............................................................................................................14-39 14.1.4.7 Deleting an Ethernet LAN Service................................................................................................14-40 14.1.5 Configuring EVPL (QinQ) Services................................................................................................14-41 14.1.5.1 EVPL(QinQ) Service Configuration Process................................................................................14-41 14.1.5.2 Setting Port Attributes and Bound Paths for an Ethernet Board...................................................14-42 14.1.5.3 Modifying the Type Field of QinQ Frames..................................................................................14-43 14.1.5.4 Creating QinQ Line Services........................................................................................................14-43 14.1.5.5 Testing Ethernet Services..............................................................................................................14-48 14.1.6 Configuration Example (Point-to-Point EPL Services)...................................................................14-49 14.1.6.1 Networking Diagram.....................................................................................................................14-49 14.1.6.2 Service Planning............................................................................................................................14-50 14.1.6.3 Configuring NE1...........................................................................................................................14-52 14.1.6.4 Configuring NE2...........................................................................................................................14-55 14.1.7 Configuration Example (PORT-Shared EVPL Services)................................................................14-56 14.1.7.1 Networking Diagram.....................................................................................................................14-56 14.1.7.2 Service Planning............................................................................................................................14-57 14.1.7.3 Configuring NE1...........................................................................................................................14-59 14.1.7.4 Configuring NE2 and NE3............................................................................................................14-65 14.1.8 Configuration Example (VCTRUNK-Shared EVPL Services).......................................................14-65 14.1.8.1 Networking Diagram.....................................................................................................................14-65 14.1.8.2 Service Planning............................................................................................................................14-66 14.1.8.3 Configuring NE1...........................................................................................................................14-69 14.1.8.4 Configuring NE2...........................................................................................................................14-73 14.1.9 Configuration Example (802.1d Bridge-Based EPLAN Services)..................................................14-73 14.1.9.1 Networking Diagram.....................................................................................................................14-74 14.1.9.2 Service Planning............................................................................................................................14-74 14.1.9.3 Configuring NE1...........................................................................................................................14-77 14.1.9.4 Configuring NE2 and NE3............................................................................................................14-82 14.1.10 Configuration Example (802.1q Bridge-Based EVPLAN Services).............................................14-83 14.1.10.1 Networking Diagram...................................................................................................................14-83 14.1.10.2 Service Planning..........................................................................................................................14-84 14.1.10.3 Configuring NE1.........................................................................................................................14-88 14.1.10.4 Configuring NE2 and NE3..........................................................................................................14-96 14.1.11 Configuration Example (EVPL Services Based on QinQ)............................................................14-96 14.1.12 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge).......................14-98 14.1.13 Configuring Services Based on the Hybrid Microwave.................................................................14-99 14.1.13.1 Networking Diagram.................................................................................................................14-100

xvi

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

14.1.13.2 Service Planning (Microwave Services)...................................................................................14-101 14.1.13.3 Service Planning (Ethernet Services Accessed Through the EMS6 Board).............................14-106 14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)...............................14-110 14.1.13.5 Configuring NE1 (Microwave Services)...................................................................................14-112 14.1.13.6 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board).............................14-116 14.1.13.7 Configuring NE2 (Microwave Services)...................................................................................14-125 14.1.13.8 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board).............................14-132 14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)..............................14-141 14.1.13.10 Configuring NE3 (Ethernet Services).....................................................................................14-142 14.2 Configuring QinQ...................................................................................................................................14-145 14.2.1 Feature Description........................................................................................................................14-146 14.2.2 Basic Concepts...............................................................................................................................14-146 14.2.2.1 Frame Format..............................................................................................................................14-147 14.2.2.2 Network Attributes......................................................................................................................14-148 14.2.2.3 Application of the QinQ Technology in Line Services...............................................................14-149 14.2.2.4 Application of the QinQ Technology in LAN Services..............................................................14-151 14.2.3 Availability.....................................................................................................................................14-154 14.2.4 Relation with Other Features..........................................................................................................14-154 14.2.5 Realization Principle......................................................................................................................14-154 14.2.6 Planning Guide...............................................................................................................................14-156 14.2.6.1 EVPL Services Based on QinQ...................................................................................................14-156 14.2.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge..............................................................14-158 14.2.7 Configuration Guide.......................................................................................................................14-159 14.2.7.1 Configuration Flow (EVPL Services Based on QinQ)...............................................................14-160 14.2.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)..........................14-161 14.2.7.3 Modifying the Type Field of QinQ Frames................................................................................14-163 14.2.7.4 Creating QinQ Line Services......................................................................................................14-164 14.2.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge..........................14-168 14.3 Configuring Features of Ethernet Ports...................................................................................................14-172 14.3.1 Feature Description........................................................................................................................14-173 14.3.2 Basic Concepts...............................................................................................................................14-173 14.3.2.1 Auto-Negotiation Function.........................................................................................................14-174 14.3.2.2 Jumbo Frames.............................................................................................................................14-176 14.3.2.3 Flow Control Function................................................................................................................14-176 14.3.3 Availability.....................................................................................................................................14-177 14.3.4 Relation with Other Features..........................................................................................................14-178 14.3.5 Realization Principle......................................................................................................................14-178 14.3.5.1 Auto-Negotiation Function.........................................................................................................14-178 14.3.5.2 Flow Control Function................................................................................................................14-179 14.3.6 Planning Guide...............................................................................................................................14-180 14.3.7 Configuration Guide.......................................................................................................................14-181 14.3.7.1 Configuring External Ethernet Ports...........................................................................................14-181 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 14.3.7.2 Modifying the Type Field of Jumbo Frames...............................................................................14-190

14.4 Configuring Encapsulation and Mapping of Ethernet Services..............................................................14-190 14.4.1 Feature Description........................................................................................................................14-191 14.4.2 Basic Concepts...............................................................................................................................14-192 14.4.2.1 Encapsulation and Mapping Protocols........................................................................................14-192 14.4.2.2 Virtual Concatenation.................................................................................................................14-193 14.4.2.3 LCAS...........................................................................................................................................14-194 14.4.3 Availability.....................................................................................................................................14-194 14.4.4 Relation with Other Features..........................................................................................................14-195 14.4.5 Realization Principle......................................................................................................................14-195 14.4.5.1 Encapsulation and Mapping........................................................................................................14-195 14.4.5.2 Virtual Concatenation.................................................................................................................14-199 14.4.5.3 LCAS...........................................................................................................................................14-200 14.4.6 Planning Guide...............................................................................................................................14-204 14.4.7 Configuring Guide..........................................................................................................................14-205 14.4.7.1 Configuring the Internal Port of the Ethernet Board...................................................................14-205 14.4.7.2 Configuring LCAS......................................................................................................................14-213 14.5 Configuring VLAN.................................................................................................................................14-214 14.5.1 Feature Description........................................................................................................................14-215 14.5.2 Basic Concepts...............................................................................................................................14-216 14.5.2.1 Frame Format..............................................................................................................................14-216 14.5.2.2 TAG Attribute.............................................................................................................................14-217 14.5.2.3 Application..................................................................................................................................14-218 14.5.3 Availability.....................................................................................................................................14-219 14.5.4 Relation with Other Features..........................................................................................................14-219 14.5.5 Realization Principle......................................................................................................................14-219 14.5.6 Planning Guide...............................................................................................................................14-220 14.5.7 Configuration Guide.......................................................................................................................14-221 14.5.7.1 Configuration Flow.....................................................................................................................14-221 14.5.7.2 Creating Ethernet Line Service...................................................................................................14-223 14.5.8 Configuration Example (PORT-Shared EVPL Service)................................................................14-228 14.5.9 Configuration Example (VCTRUNK-Shared EVPL Service).......................................................14-229 14.6 Configuring Layer 2 Switching...............................................................................................................14-230 14.6.1 Feature Description........................................................................................................................14-232 14.6.2 Basic Concepts...............................................................................................................................14-232 14.6.2.1 Bridge..........................................................................................................................................14-233 14.6.2.2 STP/RSTP...................................................................................................................................14-236 14.6.2.3 IGMP Snooping...........................................................................................................................14-237 14.6.2.4 Broadcast Packet Suppression.....................................................................................................14-239 14.6.3 Availability.....................................................................................................................................14-240 14.6.4 Relation with Other Features..........................................................................................................14-240 14.6.5 Realization Principle......................................................................................................................14-240 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

14.6.5.1 Bridge..........................................................................................................................................14-241 14.6.5.2 STP/RSTP...................................................................................................................................14-241 14.6.5.3 IGMP Snooping...........................................................................................................................14-246 14.6.6 Planning Guide...............................................................................................................................14-248 14.6.7 Configuration Guide.......................................................................................................................14-249 14.6.8 Creating the Ethernet LAN Service................................................................................................14-249 14.6.9 Modifying the Mounted Port of a Bridge.......................................................................................14-254 14.6.10 Creating the VLAN Filter Table..................................................................................................14-257 14.6.11 Creating the Entry of a MAC Address Table Manually ..............................................................14-259 14.6.12 Modifying the Aging Time of the MAC Address Table Entry....................................................14-260 14.6.13 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry...................14-261 14.6.14 Configuring the Spanning Tree Protocol ....................................................................................14-262 14.6.15 Querying the Running Information About the Spanning Tree Protocol......................................14-267 14.6.16 Configuring the IGMP Snooping Protocol...................................................................................14-267 14.6.17 Querying the Running Information About the IGMP Snooping Protocol ..................................14-269 14.6.18 Modifying the Aging Time of the Multicast Table Item..............................................................14-270 14.6.19 Querying the Multicast Router Port.............................................................................................14-271 14.6.20 Configuring the Static Multicast Table Item................................................................................14-271 14.6.21 Querying the Multicast Table Item..............................................................................................14-272 14.7 Configuring QoS.....................................................................................................................................14-272 14.7.1 Feature Description........................................................................................................................14-273 14.7.2 Basic Concepts...............................................................................................................................14-274 14.7.2.1 Flow Classification......................................................................................................................14-275 14.7.2.2 CAR.............................................................................................................................................14-275 14.7.2.3 CoS..............................................................................................................................................14-276 14.7.2.4 Traffic Shaping............................................................................................................................14-277 14.7.3 Availability.....................................................................................................................................14-278 14.7.4 Relation with Other Features..........................................................................................................14-279 14.7.5 Realization Principle......................................................................................................................14-279 14.7.5.1 CAR.............................................................................................................................................14-279 14.7.5.2 Traffic Shaping............................................................................................................................14-281 14.7.5.3 Egress Queue Scheduling............................................................................................................14-282 14.7.6 Planning Guide...............................................................................................................................14-284 14.7.7 Configuration Guide.......................................................................................................................14-285 14.7.7.1 Creating a Flow...........................................................................................................................14-286 14.7.7.2 Creating the CAR........................................................................................................................14-289 14.7.7.3 Creating the CoS.........................................................................................................................14-292 14.7.7.4 Binding the CAR/CoS.................................................................................................................14-294 14.7.7.5 Configuring the Traffic Shaping.................................................................................................14-295 14.7.7.6 Configuring the CoS of the IFH2 Board.....................................................................................14-297 14.7.7.7 Setting the Queue Scheduling Mode...........................................................................................14-298 14.7.7.8 Creating a Flow by Using a Template.........................................................................................14-299 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 14.7.7.9 Modifying CAR Parameters........................................................................................................14-300 14.7.7.10 Modifying CoS Parameters.......................................................................................................14-300 14.7.8 Configuring the Clock Sources......................................................................................................14-301 14.7.9 Configuring the Ethernet Clock Source.........................................................................................14-303

15 Ethernet Feature(RTN 900)...................................................................................................15-1


15.1 Configuring the QoS Policy........................................................................................................................15-2 15.1.1 Overview of the QoS..........................................................................................................................15-2 15.1.2 Basic Concepts...................................................................................................................................15-3 15.1.2.1 DiffServ...........................................................................................................................................15-4 15.1.2.2 HQoS...............................................................................................................................................15-6 15.1.3 Application of the QoS.......................................................................................................................15-7 15.1.3.1 Tunnel-Based QoS..........................................................................................................................15-7 15.1.3.2 QoS Policy.......................................................................................................................................15-7 15.1.4 Configuring the DiffServ Domain......................................................................................................15-8 15.1.4.1 Creating a DiffServ Domain...........................................................................................................15-8 15.1.4.2 Modifying a DiffServ Domain......................................................................................................15-10 15.1.4.3 Deleting a DiffServ Domain.........................................................................................................15-11 15.1.5 Configuring the Port Policy..............................................................................................................15-11 15.1.5.1 Creating the Port Policy................................................................................................................15-11 15.1.5.2 Modifying the Port Policy.............................................................................................................15-12 15.1.5.3 Deleting the Port Policy................................................................................................................15-13 15.1.6 Creating the CAR Policy..................................................................................................................15-13 15.1.7 Configuring the V-UNI Ingress Policy............................................................................................15-14 15.1.7.1 Creating the WFQ Scheduling Policy...........................................................................................15-15 15.1.7.2 Creating the V-UNI Ingress Policy...............................................................................................15-16 15.1.7.3 Modifying the V-UNI Ingress Policy............................................................................................15-17 15.1.7.4 Querying the V-UNI Ingress Policy-Applied Object....................................................................15-17 15.1.7.5 Deleting the V-UNI Ingress Policy...............................................................................................15-18 15.1.8 Configuring the ATM CoS Mapping...............................................................................................15-18 15.1.9 Configuring the ATM Policy...........................................................................................................15-19 15.1.9.1 Creating the ATM Policy..............................................................................................................15-20 15.1.9.2 Modifying the ATM Policy...........................................................................................................15-21 15.1.9.3 Querying the ATM Policy-Applied Object...................................................................................15-21 15.1.9.4 Deleting the ATM Policy..............................................................................................................15-22 15.2 Configuring an Ethernet Service...............................................................................................................15-22 15.2.1 Basic Concepts.................................................................................................................................15-23 15.2.1.1 E-Line Service...............................................................................................................................15-23 15.2.1.2 E-LAN Service..............................................................................................................................15-27 15.2.1.3 E-AGGR Service...........................................................................................................................15-27 15.2.2 Configuring an E-Line Service(RTN 900 V100R001)....................................................................15-28 15.2.2.1 Configuration Flow for the E-Line Service...................................................................................15-29 15.2.2.2 Creating a UNI-UNI E-Line Service.............................................................................................15-32 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

15.2.2.3 Creating a UNI-NNI E-Line Service Carried by a Port................................................................15-33 15.2.2.4 Creating a UNI-NNI E-Line Service Carried by a PW.................................................................15-33 15.2.2.5 Creating a QinQ Link....................................................................................................................15-34 15.2.2.6 Creating a UNI-NNI E-Line Service Carried by the QinQ Link..................................................15-35 15.2.2.7 Modifying an E-Line Service........................................................................................................15-36 15.2.2.8 Deleting an E-Line Service...........................................................................................................15-37 15.2.3 Configuring an E-Line Service (RTN 900 V100R002)...................................................................15-37 15.2.3.1 Configuration Flow for the E-Line Service...................................................................................15-38 15.2.3.2 Creating a UNI-UNI E-Line Service.............................................................................................15-39 15.2.3.3 Creating a QinQ Link....................................................................................................................15-40 15.2.3.4 Creating a UNI-NNI E-Line Service Carried by the QinQ Link..................................................15-41 15.2.3.5 Modifying an E-Line Service........................................................................................................15-41 15.2.3.6 Deleting an E-Line Service...........................................................................................................15-42 15.2.4 Configuring an E-LAN Service........................................................................................................15-42 15.2.4.1 Configuration Flow for E-LAN Service........................................................................................15-43 15.2.4.2 Creating a QinQ Link....................................................................................................................15-45 15.2.4.3 Creating an E-LAN Service..........................................................................................................15-45 15.2.4.4 Managing the Blacklist..................................................................................................................15-47 15.2.4.5 Setting the Broadcast Storm Suppression.....................................................................................15-48 15.2.4.6 Modifying E-LAN Service............................................................................................................15-49 15.2.4.7 Deleting E-LAN Service...............................................................................................................15-49 15.2.5 Configuring an E-AGGR Service....................................................................................................15-50 15.2.5.1 Configuration Flow for the E-AGGR Service...............................................................................15-50 15.2.5.2 Creating an E-AGGR Service.......................................................................................................15-52 15.2.5.3 Modifying an E-AGGR Service....................................................................................................15-53 15.2.5.4 Deleting an E-AGGR Service.......................................................................................................15-53 15.3 Configuring Port Mirroring.......................................................................................................................15-54

16 Configuring Cross-Polarization Interference Cancellation...........................................16-1


16.1 Feature Description.....................................................................................................................................16-2 16.2 Availability..................................................................................................................................................16-2 16.3 Realization Principle...................................................................................................................................16-3 16.4 Creating an XPIC Workgroup.....................................................................................................................16-3

17 Configuring Automatic Transmit Power Control Function...........................................17-1


17.1 Feature Description.....................................................................................................................................17-2 17.2 Availability..................................................................................................................................................17-3 17.3 Realization Principle...................................................................................................................................17-3 17.4 Configuring the ATPC Function.................................................................................................................17-5

18 Configuring Hybrid Microwave.........................................................................................18-1


18.1 Feature Description.....................................................................................................................................18-2 18.2 Basic Concepts............................................................................................................................................18-2 18.2.1 Service Transmission Mode...............................................................................................................18-3 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 18.2.2 AM..................................................................................................................................................... 18-3 18.2.3 Working Mode...................................................................................................................................18-5 18.2.4 QoS Control for Ethernet Services.....................................................................................................18-6

18.3 Availability..................................................................................................................................................18-7 18.4 Realization Principle...................................................................................................................................18-7 18.5 Configuration Guide....................................................................................................................................18-9

19 Configuring the MSTP..........................................................................................................19-1


19.1 Overview of the MSTP...............................................................................................................................19-3 19.2 Basic Concepts............................................................................................................................................19-6 19.3 MSTP Application.......................................................................................................................................19-8 19.4 Configuring a Port Group............................................................................................................................19-9 19.5 Configuring Bridge Parameters...................................................................................................................19-9 19.6 Configuring CIST and MSTI Parameters..................................................................................................19-10 19.7 Querying the CIST Running Information.................................................................................................19-11 19.8 Configuring Protocol Transfer for Ports...................................................................................................19-11

20 Configuring the Control Plane............................................................................................20-1


20.1 Basic Concepts............................................................................................................................................20-3 20.1.1 IGP-ISIS Protocol..............................................................................................................................20-3 20.1.2 MPLS-LDP Protocol..........................................................................................................................20-4 20.1.3 MPLS-RSVP Protocol........................................................................................................................20-6 20.1.4 ARP Protocol......................................................................................................................................20-7 20.2 Configuring the IGP-ISIS Protocol...........................................................................................................20-10 20.2.1 Setting Node Attributes....................................................................................................................20-10 20.2.2 Setting Port Attributes......................................................................................................................20-11 20.2.3 Configuring Parameters of Route Importing....................................................................................20-11 20.2.4 Querying the Link TE Information..................................................................................................20-12 20.3 Configuring the MPLS-LDP Protocol.......................................................................................................20-12 20.3.1 Creating MPLS-LDP Peer Entities..................................................................................................20-12 20.3.2 Configuring the MPLS-LDP Protocol..............................................................................................20-13 20.4 Configuring the MPLS-RSVP Protocol....................................................................................................20-13 20.5 Configuring the OSPF Protocol................................................................................................................20-14 20.5.1 Setting Node Attributes....................................................................................................................20-14 20.5.2 Setting Port Attributes......................................................................................................................20-15 20.5.3 Configuring Parameters of Route Importing....................................................................................20-16 20.5.4 Querying the Link TE Information..................................................................................................20-16 20.6 Configuring the MP-BGP..........................................................................................................................20-17 20.7 Configuring Static Routes.........................................................................................................................20-17 20.8 Configuring the Address Parse..................................................................................................................20-18

21 Configuring an MPLS Tunnel.............................................................................................21-1


21.1 Basic Concepts............................................................................................................................................21-2 21.1.1 MPLS and MPLS Tunnel...................................................................................................................21-2 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

21.1.2 Application of the MPLS Tunnel.......................................................................................................21-2 21.2 Configuring an MPLS Tunnel.....................................................................................................................21-4 21.2.1 Configuring Basic Attributes of the MPLS........................................................................................21-4 21.2.2 Creating an MPLS Tunnel..................................................................................................................21-5 21.2.3 Deleting an MPLS Tunnel..................................................................................................................21-6 21.3 Querying the Tunnel Label Information.....................................................................................................21-6

22 Configuring an IP Tunnel....................................................................................................22-1
22.1 IP Tunnel.....................................................................................................................................................22-2 22.2 Configuring a UDP PW Port.......................................................................................................................22-2 22.3 Creating IP Tunnels.....................................................................................................................................22-3 22.4 Deleting IP Tunnels.....................................................................................................................................22-3

23 Configuring a GRE Tunnel..................................................................................................23-1


23.1 GRE Tunnel.................................................................................................................................................23-2 23.2 Creating GRE Tunnels................................................................................................................................23-2 23.3 Deleting GRE Tunnels................................................................................................................................23-3

24 Configuring an MPLS PW....................................................................................................24-1


24.1 Querying an MPLS PW...............................................................................................................................24-2 24.2 Querying QoS-Related Parameters of an MPLS PW..................................................................................24-2 24.3 Querying the PW Label Information...........................................................................................................24-2

25 Configuring CES Services....................................................................................................25-1


25.1 CES Service Type.......................................................................................................................................25-2 25.2 Configuration Flow of CES Services..........................................................................................................25-5 25.3 Configuring a CES Service.........................................................................................................................25-7 25.3.1 Creating a UNI-UNI CES Service.....................................................................................................25-8 25.3.2 Creating a UNI-NNI CES Service.....................................................................................................25-8 25.3.3 Deleting a CES Service....................................................................................................................25-10

26 Configuring an ATM Service...............................................................................................26-1


26.1 Basic Concepts............................................................................................................................................26-2 26.1.1 IMA....................................................................................................................................................26-2 26.1.2 Application of the IMA......................................................................................................................26-3 26.1.3 ATM Service......................................................................................................................................26-4 26.1.4 ATM Traffic.......................................................................................................................................26-5 26.2 ATM Service Configuration Flow..............................................................................................................26-7 26.3 Configuring an IMA Group.......................................................................................................................26-12 26.3.1 Configuring Bound Channels in an ATM IMA Group....................................................................26-14 26.3.2 Configuring Attributes of an ATM IMA Group..............................................................................26-15 26.3.3 Configuring ATM Interface Attributes............................................................................................26-15 26.3.4 Querying IMA Group States............................................................................................................26-16 26.3.5 Querying IMA Link States...............................................................................................................26-16 26.3.6 Resetting an IMA Group..................................................................................................................26-17 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management 26.3.7 Modifying an IMA Group................................................................................................................26-17 26.3.8 Deleting an IMA Group................................................................................................................... 26-18

26.4 Configuring the ATM Service...................................................................................................................26-18 26.4.1 Creating ATM Services....................................................................................................................26-19 26.4.2 Modifying ATM Services................................................................................................................ 26-22 26.4.3 Deleting ATM Services....................................................................................................................26-22

27 Configuring the BFD.............................................................................................................27-1


27.1 Overview of the BFD..................................................................................................................................27-2 27.2 Basic Concepts............................................................................................................................................27-2 27.3 Creating a BFD Session..............................................................................................................................27-3 27.4 Configuring Parameters of the BFD Session..............................................................................................27-3 27.5 Querying the BFD Session Information......................................................................................................27-4 27.6 Deleting a BFD Session..............................................................................................................................27-4

28 Configuring the IGMP Snooping.......................................................................................28-1


28.1 Overview of the IGMP Snooping................................................................................................................28-3 28.2 Basic Concepts............................................................................................................................................28-4 28.3 Application of the IGMP Snooping............................................................................................................28-6 28.4 Configuring the IGMP Snooping Parameters.............................................................................................28-7 28.5 Configuring the Router Management..........................................................................................................28-8 28.6 Configuring the Route Member Port Management.....................................................................................28-8 28.7 Configuring the Packet Statistics................................................................................................................28-9

29 OAM Management................................................................................................................29-1
29.1 Configuring ETH OAM..............................................................................................................................29-2 29.1.1 Feature Introduction...........................................................................................................................29-2 29.1.2 Basic Concept.....................................................................................................................................29-3 29.1.2.1 IEEE 802.1ag OAM Management..................................................................................................29-4 29.1.2.2 IEEE 802.1ag OAM Operation.......................................................................................................29-7 29.1.2.3 IEEE 802.3ah OAM Operations......................................................................................................29-8 29.1.3 Availability.........................................................................................................................................29-9 29.1.4 Function Implementation................................................................................................................. 29-10 29.1.4.1 802.1ag OAM................................................................................................................................29-10 29.1.4.2 802.3ah OAM................................................................................................................................29-14 29.1.5 Using the IEEE 802.1ag OAM.........................................................................................................29-23 29.1.5.1 Creating MDs................................................................................................................................29-24 29.1.5.2 Creating MAs................................................................................................................................29-25 29.1.5.3 Creating MPs.................................................................................................................................29-26 29.1.5.4 Performing a Continuity Check.....................................................................................................29-27 29.1.5.5 Performing a Loopback Check......................................................................................................29-28 29.1.5.6 Performing a Link Trace Check....................................................................................................29-29 29.1.5.7 Activating the AIS(RTN 600).......................................................................................................29-31 29.1.5.8 Performing a Ping Test(RTN 600)................................................................................................29-31 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

29.1.5.9 Performing Performance Detection(RTN 600).............................................................................29-32 29.1.6 Using the IEEE 802.3ah OAM.........................................................................................................29-33 29.1.6.1 Enabling the Auto-Discovery Function of OAM..........................................................................29-33 29.1.6.2 Enabling the Link Event Notification...........................................................................................29-34 29.1.6.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold................................29-35 29.1.6.4 Performing the Remote Loopback................................................................................................29-37 29.1.6.5 Enabling the Self-Loop Detection (RTN 600)..............................................................................29-38 29.2 Configuring the MPLS OAM....................................................................................................................29-38 29.2.1 Overview of the MPLS OAM..........................................................................................................29-39 29.2.2 Basic Concepts.................................................................................................................................29-39 29.2.3 Application of the MPLS OAM.......................................................................................................29-41 29.2.4 Enabling the MPLS OAM of a Tunnel............................................................................................29-42 29.2.5 Setting the MPLS OAM Parameters of a Tunnel.............................................................................29-42 29.2.6 Starting the CV/FFD for a Tunnel....................................................................................................29-43 29.2.7 Performing an LSP Ping Test...........................................................................................................29-44 29.2.8 Performing an LSP Traceroute Test.................................................................................................29-45 29.3 Configuring the PW OAM........................................................................................................................29-46 29.3.1 Overview of the PW OAM...............................................................................................................29-46 29.3.2 Basic Concepts.................................................................................................................................29-46 29.3.3 Application of the PW OAM...........................................................................................................29-47 29.3.4 Performing the PW Ping Test...........................................................................................................29-47 29.4 Configuring ATM OAM...........................................................................................................................29-48 29.4.1 Overview of the ATM OAM............................................................................................................29-49 29.4.2 Basic Concepts.................................................................................................................................29-49 29.4.3 Application of the ATM OAM.........................................................................................................29-50 29.4.4 Setting Segment End Attribute.........................................................................................................29-51 29.4.5 Setting the CC Activation Status......................................................................................................29-52 29.4.6 Setting Remote Loopback Test........................................................................................................29-53 29.4.7 Setting Local Loopback ID..............................................................................................................29-53

30 Configuring Link State Pass Through...............................................................................30-1


30.1 Feature Description.....................................................................................................................................30-2 30.2 Availability..................................................................................................................................................30-4 30.3 Realization Principle...................................................................................................................................30-4 30.3.1 Point-to-Point Service(RTN 600).......................................................................................................30-4 30.3.2 Point-to-Multipoint Service(RTN 600)..............................................................................................30-6 30.4 LPT Configuration....................................................................................................................................30-10

31 Configuring Remote Monitoring Feature.........................................................................31-1


31.1 Feature Description.....................................................................................................................................31-2 31.2 Basic Concepts............................................................................................................................................31-2 31.2.1 SNMP.................................................................................................................................................31-2 31.2.2 RMON Management Groups.............................................................................................................31-3 31.2.3 List of RMON Alarm Entries and RMON Performance Entries.......................................................31-5 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv

Contents

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

31.3 Availability..................................................................................................................................................31-7 31.4 Realization Principle...................................................................................................................................31-8 31.5 Configuration Guide....................................................................................................................................31-9 31.5.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................31-10 31.5.2 Configuring an Alarm Group for an Ethernet Port.......................................................................... 31-10 31.5.3 Configuring a History Control Group..............................................................................................31-11 31.5.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................31-11 31.5.5 Setting Performance Monitoring Status for an Ethernet Port.......................................................... 31-12

32 Configuring Synchronous Ethernet....................................................................................32-1


32.1 Feature Description.....................................................................................................................................32-2 32.2 Availability..................................................................................................................................................32-2 32.3 Realization Principle...................................................................................................................................32-3 32.4 Configuration Guide....................................................................................................................................32-4

33 Modifying the Configuration Data.....................................................................................33-1


33.1 Modifying NE Attributes............................................................................................................................33-2 33.1.1 Modifying the NE ID.........................................................................................................................33-2 33.1.2 Modifying the NE Name....................................................................................................................33-3 33.1.3 Deleting NEs......................................................................................................................................33-3 33.1.4 Modifying GNE Parameters...............................................................................................................33-4 33.1.5 Changing the GNE for NEs................................................................................................................33-5 33.2 Modifying the Board Configuration Data...................................................................................................33-6 33.2.1 Adding Boards....................................................................................................................................33-6 33.2.2 Deleting Boards..................................................................................................................................33-7 33.2.3 Modifying Board Configuration Parameters......................................................................................33-8 33.3 Modifying the Fiber Configuration Data....................................................................................................33-8 33.3.1 Modifying Fiber/Cable Information...................................................................................................33-9 33.3.2 Deleting Fibers...................................................................................................................................33-9 33.3.3 Deleting DCN Communication Cables............................................................................................33-10 33.4 Modifying the Service Configuration Data...............................................................................................33-10 33.4.1 Modifying SDH Services.................................................................................................................33-11 33.4.2 Deleting SDH Services.....................................................................................................................33-12 33.4.3 Deleting EPL Services..................................................................................................................... 33-13 33.4.4 Deleting EVPL Services...................................................................................................................33-13 33.4.5 Deleting EPLAN Services................................................................................................................33-14 33.4.6 Converting a Normal Service to an SNCP Service..........................................................................33-15 33.4.7 Converting an SNCP Service to a Normal Service..........................................................................33-16

34 Common Maintenance Operations.....................................................................................34-1


34.1 Checking the Network Communication Status...........................................................................................34-3 34.2 Turning On and Off a Laser........................................................................................................................34-3 34.3 Setting a Scheduled Task............................................................................................................................34-4 34.4 Checking Networkwide Maintenance Status..............................................................................................34-5 xxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Contents

34.4.1 Checking Path Loopback Status.........................................................................................................34-6 34.4.2 Checking Port Laser Status................................................................................................................34-6 34.4.3 Checking Path Loading Status...........................................................................................................34-7 34.4.4 Checking Path Alarm Reversion Status.............................................................................................34-8 34.4.5 Checking Path Alarm Suppression Status..........................................................................................34-9 34.4.6 Checking the DCC Enabling Status.................................................................................................34-10 34.5 Checking Protection Switching Status......................................................................................................34-10 34.5.1 Checking the SNCP Service Switching Status.................................................................................34-11 34.5.2 Checking Linear MSP Switching Status..........................................................................................34-11 34.5.3 Checking 1+1 Board Switching Status.............................................................................................34-12 34.5.4 Checking the Switching Status of 1+1 Intermediate Frequency Protection.....................................34-12 34.5.5 Check the Switching Status of the N+1 Protection..........................................................................34-13 34.5.6 Checking GNE Switching Status.....................................................................................................34-13 34.5.7 Checking the Clock Switching Status..............................................................................................34-14 34.6 Resetting Boards.......................................................................................................................................34-14 34.6.1 Reset.................................................................................................................................................34-15 34.6.2 Resetting the SCC Board..................................................................................................................34-15 34.6.3 Resetting a Non-SCC Board............................................................................................................34-15 34.6.4 Resetting a Board.............................................................................................................................34-16 34.7 Performing a Loopback.............................................................................................................................34-16 34.7.1 Setting a Loopback for an SDH Interface........................................................................................34-17 34.7.2 Setting a Loopback for a PDH Interface..........................................................................................34-19 34.7.3 Setting a Loopback for an Ethernet Interface...................................................................................34-20 34.7.4 Setting a Loopback for an IF Interface.............................................................................................34-21 34.7.5 Setting a Loopback for an ODU Interface........................................................................................34-23 34.7.6 Setting a Loopback for a Digital Interface.......................................................................................34-24 34.7.7 Setting a Loopback for a VC4 Path..................................................................................................34-25 34.7.8 Setting a Loopback for a VC3 Path..................................................................................................34-27 34.8 Setting Automatic Laser Shutdown...........................................................................................................34-28 34.9 Disabling Service-Affecting Settings Automatically................................................................................34-29 34.10 Performing a PRBS Test.........................................................................................................................34-29 34.11 Diagnosing Ethernet Protocol Faults.......................................................................................................34-30 34.12 Checking the Network Communication Status.......................................................................................34-31

Issue 02 (2010-09-24)

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

xxvii

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figures

Figures
Figure 2-1 DCN network......................................................................................................................................2-3 Figure 2-2 Positions of DCC bytes in SDH overheads........................................................................................2-5 Figure 2-3 Networking that involves only Huawei equipment............................................................................2-6 Figure 2-4 Networking that involves Huawei equipment and third-party equipment..........................................2-7 Figure 2-5 Gateway NE mode..............................................................................................................................2-8 Figure 2-6 Gateway NE mode (by default gateway)............................................................................................2-9 Figure 2-7 Direct connection mode (by static routes)........................................................................................2-10 Figure 2-8 Direct connection mode through a router (by static routes).............................................................2-11 Figure 2-9 Format of a simple NSAP address....................................................................................................2-12 Figure 2-10 Format of a complicated NSAP address.........................................................................................2-12 Figure 2-11 Third-party equipment forwarding OAM information of Huawei equipment...............................2-14 Figure 2-12 Huawei equipment forwarding OAM information of third-party equipment.................................2-15 Figure 2-13 DCN management flow..................................................................................................................2-16 Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)..................2-33 Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)..................2-34 Figure 2-16 Inband DCN networking mode.......................................................................................................2-41 Figure 2-17 Inband networking scheme.............................................................................................................2-42 Figure 2-18 Outband networking scheme..........................................................................................................2-43 Figure 3-1 Configuration flow when SSM protocol is disabled..........................................................................3-3 Figure 3-2 Configuration flow when standard SSM protocol is enabled.............................................................3-3 Figure 3-3 Configuration flow when extended SSM protocol is enabled............................................................3-3 Figure 3-4 Clock synchronization scheme for a chain network...........................................................................3-4 Figure 3-5 Clock synchronization scheme for a tree network..............................................................................3-5 Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line) ...............................................................................................................................................................................3-6 Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line) ...............................................................................................................................................................................3-7 Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports.........................3-8 Figure 3-9 Clock synchronization......................................................................................................................3-10 Figure 4-1 Architecture of the IEEE 1588V2 clock.............................................................................................4-4 Figure 4-2 Master-slave synchronization process................................................................................................4-5 Figure 4-3 Networking diagram for typical application of the PTP clock...........................................................4-7 Figure 4-4 Configuration flow for the PTP clock................................................................................................4-8 Figure 5-1 Configuring the F1 data port service..................................................................................................5-3 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix

Figures

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Figure 5-2 Networking diagram...........................................................................................................................5-7 Figure 5-3 Timeslot allocation of synchronous data services..............................................................................5-8

Figure 5-4 Networking diagram.........................................................................................................................5-11 Figure 5-5 Timeslot allocation diagram ............................................................................................................5-12 Figure 6-1 Networking diagram...........................................................................................................................6-3 Figure 8-1 Procedure for configuring a PDH interface........................................................................................8-6 Figure 8-2 Procedure for configuring an microwave interface..........................................................................8-15 Figure 8-3 Procedure for configuring an MP group...........................................................................................8-28 Figure 8-4 ML-PPP packet format.....................................................................................................................8-30 Figure 8-5 ML-PPP application scenario...........................................................................................................8-31 Figure 8-6 IMA group configuration flow.........................................................................................................8-34 Figure 9-1 Classification of Radio Stations.........................................................................................................9-2 Figure 9-2 Radio link.........................................................................................................................................9-14 Figure 11-1 1+1 HSB protection........................................................................................................................11-2 Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)...........................11-4 Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction).............................11-4 Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)................................11-5 Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)..............................11-5 Figure 11-6 1+1 HSB realization principle (before the switching, in the transmit direction)...........................11-6 Figure 11-7 1+1 HSB realization principle (before the switching, in the receive direction).............................11-7 Figure 11-8 1+1 HSB realization principle (after the switching, in the receive direction)................................11-8 Figure 11-9 1+1 HSB realization principle (after the switching, in the transmit direction)..............................11-8 Figure 11-10 1+1 FD protection.......................................................................................................................11-10 Figure 11-11 1+1 FD realization principle (before the switching, in the transmit direction)..........................11-12 Figure 11-12 1+1 FD realization principle (before the switching, in the receive direction)............................11-12 Figure 11-13 1+1 FD HSB realization principle (after the switching, in the receive direction)......................11-13 Figure 11-14 1+1 FD HSM realization principle (after the switching, in the receive direction).....................11-13 Figure 11-15 1+1 FD realization principle (before the switching, in the transmit direction)..........................11-14 Figure 11-16 1+1 FD realization principle (before the switching, in the receive direction)............................11-15 Figure 11-17 1+1 HSB realization principle (after the switching, in the transmit direction)..........................11-16 Figure 11-18 1+1 FD HSB realization principle (after the switching, in the receive direction)......................11-16 Figure 11-19 1+1 FD HSM realization principle (after the switching, in the receive direction).....................11-17 Figure 11-20 1+1 SD protection.......................................................................................................................11-18 Figure 11-21 1+1 SD realization principle (before the switching, in the transmit direction)..........................11-20 Figure 11-22 1+1 SD realization principle (before the switching, in the receive direction)............................11-21 Figure 11-23 1+1 SD HSB realization principle (after the switching, in the receive direction)......................11-21 Figure 11-24 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................11-22 Figure 11-25 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-22 Figure 11-26 1+1 SD realization principle (before the switching, in the transmit direction)..........................11-23 Figure 11-27 1+1 SD realization principle (before the switching, in the receive direction)............................11-24 Figure 11-28 1+1 SD HSB realization principle (after the switching, in the receive direction)......................11-25 Figure 11-29 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................11-25 xxx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figures

Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-26 Figure 12-1 Multiplex section schematic diagram.............................................................................................12-4 Figure 12-2 SNCP service pair...........................................................................................................................12-7 Figure 12-3 SNCP service..................................................................................................................................12-7 Figure 12-4 N+1 protection .............................................................................................................................12-11 Figure 12-5 Realization principle of 2+1 protection (before the switching)....................................................12-14 Figure 12-6 Realization principle of 2+1 protection (after the switching).......................................................12-14 Figure 12-7 Realization principle of the 3+1 protection (before the switching)..............................................12-15 Figure 12-8 Realization principle of the 3+1 protection (after the switching).................................................12-16 Figure 12-9 Configuration flow for the N+1 protection mode.........................................................................12-18 Figure 12-10 1+1 linear MSP ..........................................................................................................................12-26 Figure 12-11 1:N linear MSP ..........................................................................................................................12-27 Figure 12-12 Realization principle of 1+1 linear MSP (before the switching)................................................12-29 Figure 12-13 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)........ 12-30 Figure 12-14 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode)...........12-30 Figure 12-15 Realization principle of 1:1 linear MSP (before the switching).................................................12-31 Figure 12-16 Realization principle of 1:1 linear MSP (after the switching)....................................................12-31 Figure 12-17 Two-fiber bidirectional MSP ring.............................................................................................. 12-39 Figure 12-18 Realization principle of the two-fiber bidirectional ring MSP (before the switching)...............12-40 Figure 12-19 Realization principle of the two-fiber bidirectional ring MSP (after the switching)..................12-41 Figure 12-20 Sub-Network Connection Protection..........................................................................................12-46 Figure 12-21 SNCP service pair.......................................................................................................................12-47 Figure 12-22 SNCP realization principle (before the switching).....................................................................12-48 Figure 12-23 SNCP realization principle (after the switching)........................................................................12-48 Figure 12-24 MPLS APS 1+1 protection.........................................................................................................12-62 Figure 12-25 MPLS APS 1:1 protection..........................................................................................................12-63 Figure 12-26 MPLS APS 1+1 protection.........................................................................................................12-66 Figure 12-27 MPLS APS 1:1 protection..........................................................................................................12-66 Figure 12-28 R-APS format.............................................................................................................................12-72 Figure 12-29 ERPS switching process (upon a fault not on the RPL link)......................................................12-76 Figure 12-30 ERPS switching process (upon a fault on the RPL link)............................................................12-77 Figure 12-31 Ethernet ring protection switching............................................................................................. 12-79 Figure 12-32 Link aggregation group.............................................................................................................. 12-82 Figure 12-33 Application of the LACP protocol..............................................................................................12-84 Figure 12-34 Application of the link aggregation group..................................................................................12-85 Figure 13-1 Numbering VC-12 timeslots by order............................................................................................13-3 Figure 13-2 Numbering VC-12 timeslots in the interleaved scheme ................................................................13-4 Figure 13-3 Chain network.................................................................................................................................13-7 Figure 13-4 SNCP ring with unprotected chain...............................................................................................13-19 Figure 13-5 Networking diagram.....................................................................................................................13-35 Figure 13-6 Planning the radio link..................................................................................................................13-37 Figure 13-7 IDU board configuration (NE1)....................................................................................................13-38 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi

Figures

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Figure 13-8 IDU board configuration (NE2)....................................................................................................13-38 Figure 13-9 IDU board configuration (NE3)....................................................................................................13-38 Figure 13-10 IDU board configuration (NE4)..................................................................................................13-38 Figure 13-11 IDU board configuration (NE5)..................................................................................................13-38 Figure 13-12 Timeslot allocation diagram.......................................................................................................13-42

Figure 13-13 Clock Synchronization Scheme..................................................................................................13-44 Figure 13-14 Networking diagram...................................................................................................................13-65 Figure 13-15 Planning the radio link................................................................................................................13-66 Figure 13-16 IDU board configuration (NE1 and NE2)..................................................................................13-67 Figure 13-17 Networking diagram...................................................................................................................13-77 Figure 13-18 Planning the radio link................................................................................................................13-78 Figure 13-19 IDU board configuration (NE5)..................................................................................................13-78 Figure 14-1 Ethernet frame format.....................................................................................................................14-4 Figure 14-2 Positions of the TPID and TCI in the frame structure....................................................................14-4 Figure 14-3 TCI structure of the C-TAG...........................................................................................................14-5 Figure 14-4 TCI structure of the S-TAG ...........................................................................................................14-5 Figure 14-5 External ports and internal ports on Ethernet boards......................................................................14-6 Figure 14-6 Waveform of a single FLP..............................................................................................................14-7 Figure 14-7 Consecutive FLP and NLP bursts ..................................................................................................14-8 Figure 14-8 Structure of the PAUSE frame.......................................................................................................14-9 Figure 14-9 VC-3-Xv/VC-4-Xv multiframe and sequence indicator...............................................................14-12 Figure 14-10 Relation between VB, LP, external port, and VCTRUNK port.................................................14-14 Figure 14-11 Transparent bridge and virtual bridge.........................................................................................14-15 Figure 14-12 EPL service configuration process.............................................................................................14-19 Figure 14-13 Ethernet test................................................................................................................................14-26 Figure 14-14 Ethernet LAN service configuration process..............................................................................14-28 Figure 14-15 Ethernet test................................................................................................................................14-40 Figure 14-16 EVPL(QinQ) service configuration process...............................................................................14-42 Figure 14-17 Ethernet test................................................................................................................................14-48 Figure 14-18 Networking diagram...................................................................................................................14-50 Figure 14-19 IDU board configuration ...........................................................................................................14-50 Figure 14-20 Configuring Ethernet services....................................................................................................14-50 Figure 14-21 Timeslot allocation of Ethernet services.....................................................................................14-51 Figure 14-22 Networking diagram...................................................................................................................14-56 Figure 14-23 IDU board configuration (NE1)..................................................................................................14-57 Figure 14-24 IDU board configuration (NE2 and NE3)..................................................................................14-57 Figure 14-25 Configuring Ethernet services....................................................................................................14-57 Figure 14-26 Timeslot allocation of Ethernet services.....................................................................................14-59 Figure 14-27 Networking diagram...................................................................................................................14-66 Figure 14-28 IDU board configuration (NE1 and NE2)..................................................................................14-66 Figure 14-29 Configuring Ethernet services....................................................................................................14-67 Figure 14-30 Timeslot allocation of Ethernet services.....................................................................................14-68 xxxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figures

Figure 14-31 Networking diagram...................................................................................................................14-74 Figure 14-32 IDU board configuration (NE1)..................................................................................................14-75 Figure 14-33 IDU board configuration (NE2 and NE3)..................................................................................14-75 Figure 14-34 Configuring Ethernet services....................................................................................................14-75 Figure 14-35 Timeslot allocation of Ethernet services.....................................................................................14-77 Figure 14-36 Networking diagram...................................................................................................................14-84 Figure 14-37 IDU board configuration (NE1)..................................................................................................14-84 Figure 14-38 IDU board configuration (NE2 and NE3)..................................................................................14-85 Figure 14-39 Configuring Ethernet services....................................................................................................14-85 Figure 14-40 Timeslot allocation of Ethernet services.....................................................................................14-87 Figure 14-41 Networking diagram.................................................................................................................14-101 Figure 14-42 Link planning diagram .............................................................................................................14-102 Figure 14-43 Board layout of the IDU (NE1)................................................................................................14-104 Figure 14-44 Board layout of the IDU (NE2)................................................................................................14-104 Figure 14-45 Board layout of the IDU (NE3)................................................................................................14-104 Figure 14-46 Timeslot allocation diagram.....................................................................................................14-105 Figure 14-47 Clock synchronization scheme.................................................................................................14-106 Figure 14-48 Configuration information of Ethernet parameters...................................................................14-107 Figure 14-49 Configuration diagram of the Ethernet services between NE2 and NE3.................................14-111 Figure 14-50 Format of the Ethernet frame with only a C-TAG...................................................................14-147 Figure 14-51 Format of the Ethernet frame with a C-TAG and an S-TAG...................................................14-148 Figure 14-52 Format of the Ethernet frame with only an S-TAG..................................................................14-148 Figure 14-53 EVPL (QinQ) Services.............................................................................................................14-154 Figure 14-54 Example of the EVPLAN (802.1ad bridge) service.................................................................14-155 Figure 14-55 Ports used by the QinQ line services........................................................................................14-157 Figure 14-56 Configuration flow for the QinQ line service...........................................................................14-160 Figure 14-57 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge..................14-162 Figure 14-58 Waveform of a single FLP........................................................................................................14-179 Figure 14-59 Consecutive FLP bursts and NLPs ..........................................................................................14-179 Figure 14-60 Structure of the PAUSE frame.................................................................................................14-180 Figure 14-61 Internal port of the Ethernet service board...............................................................................14-191 Figure 14-62 Structure of the GFP frame ......................................................................................................14-196 Figure 14-63 GFP type field format...............................................................................................................14-197 Figure 14-64 VC-3-Xv/VC-4-Xv multiframe and sequence indicator ..........................................................14-200 Figure 14-65 Capacity adjustment process (addition of a member) ..............................................................14-202 Figure 14-66 Capacity adjustment process (deletion of a member) ..............................................................14-203 Figure 14-67 Capacity adjustment process (one member link restored after a failure).................................14-203 Figure 14-68 Tagged frame format................................................................................................................14-216 Figure 14-69 PORT-shared EVPL service.....................................................................................................14-218 Figure 14-70 VCTRUNK-shared EVPL service............................................................................................14-219 Figure 14-71 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared or VCTRUNKshared EVPL service) .....................................................................................................................................14-221 Figure 14-72 Relations among the VB, LP, external port, and VCTRUNK port..........................................14-233 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii

Figures

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Figure 14-73 802.1d bridge and 802.1q bridge..............................................................................................14-234 Figure 14-74 802.1ad Bridge..........................................................................................................................14-234 Figure 14-75 Transmission of the multicast packet (with IGMP Snooping disabled)...................................14-238 Figure 14-76 Transmission of the multicast packet (with IGMP Snooping enabled)....................................14-239 Figure 14-77 FIFO queue...............................................................................................................................14-273 Figure 14-78 SP queue...................................................................................................................................14-274 Figure 14-79 Basic principle of the token bucket algorithm..........................................................................14-279 Figure 14-80 Basic principle of the algorithm that is used by the CAR........................................................14-280

Figure 14-81 Basic principle of the algorithm that is used by the traffic shaping......................................... 14-281 Figure 14-82 SP queue...................................................................................................................................14-282 Figure 14-83 WRR scheduling algorithm......................................................................................................14-283 Figure 14-84 SP+WRR scheduling algorithm................................................................................................14-284 Figure 15-1 Networking diagram for the DiffServ model..................................................................................15-4 Figure 15-2 HQoS function points and corresponding QoS processing............................................................15-7 Figure 15-3 UNI-UNI E-Line service..............................................................................................................15-24 Figure 15-4 UNI-NNI E-Line service carried by ports....................................................................................15-24 Figure 15-5 UNI-NNI E-Line service carried by a PW...................................................................................15-25 Figure 15-6 UNI-NNI E-Line service carried by a QinQ link.........................................................................15-26 Figure 15-7 NNI-NNI E-Line service carried by a QinQ link.........................................................................15-27 Figure 15-8 E-AGGR service...........................................................................................................................15-28 Figure 15-9 Flow diagram for configuring the E-LAN service.......................................................................15-44 Figure 15-10 Configuration flow for the E-AGGR service..............................................................................15-51 Figure 16-1 Channel configuration in ACAP mode (without the application of the XPIC technology)...........16-2 Figure 16-2 Channel configuration in CCDP mode (with the application of the XPIC technology)................16-2 Figure 16-3 Realization principle of XPIC........................................................................................................16-3 Figure 17-1 ATPC realization principle.............................................................................................................17-4 Figure 18-1 Application of the Hybrid microwave feature................................................................................18-2 Figure 18-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame......................18-3 Figure 18-3 Working principle of the Hybrid microwave .................................................................................18-4 Figure 18-4 AM switching (before the switching).............................................................................................18-8 Figure 18-5 AM switching (after the switching)................................................................................................18-9 Figure 19-1 STP/RSTP.......................................................................................................................................19-3 Figure 19-2 Limitations of the STP/RSTP.........................................................................................................19-4 Figure 19-3 MSTI in an MST region.................................................................................................................19-5 Figure 19-4 Example of the MSTP....................................................................................................................19-6 Figure 19-5 Example of the MST region...........................................................................................................19-7 Figure 20-1 LSP tunnel created by using the MPLS-RSVP..............................................................................20-7 Figure 20-2 ARP frame format..........................................................................................................................20-8 Figure 20-3 ARP address resolution..................................................................................................................20-9 Figure 21-1 MPLS tunnel in the MPLS network...............................................................................................21-2 Figure 21-2 Transparent transmission of point-to-point data packets................................................................21-3 Figure 21-3 Protection principle for unicast tunnels..........................................................................................21-4 xxxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figures

Figure 22-1 ATM PWE3 over IP tunnel............................................................................................................22-2 Figure 23-1 ATM PWE3 over GRE tunnel........................................................................................................23-2 Figure 25-1 CES service networking sample.....................................................................................................25-3 Figure 25-2 External Clock synchronization of CES service clock...................................................................25-4 Figure 25-3 UNI-UNI CES service configuration flow.....................................................................................25-5 Figure 25-4 UNI-NNI CES service configuration flow.....................................................................................25-6 Figure 26-1 ATM IMA group............................................................................................................................26-2 Figure 26-2 IMA networking diagram 1............................................................................................................26-3 Figure 26-3 IMA networking diagram 2............................................................................................................26-3 Figure 26-4 IMA networking diagram...............................................................................................................26-4 Figure 26-5 ATM connection convergence sample...........................................................................................26-4 Figure 26-6 Configuration flow of the UNI-UNI ATM service.........................................................................26-8 Figure 26-7 Configuration flow of the UNIs-NNI ATM service.......................................................................26-9 Figure 26-8 IMA group configuration flow.....................................................................................................26-13 Figure 28-1 Application of the IGMP Snooping-Supported Equipment in the Network..................................28-3 Figure 28-2 Multicast forwarding......................................................................................................................28-6 Figure 29-1 Ethernet OAM solution..................................................................................................................29-3 Figure 29-2 Logical diagram of maintenance domain layers.............................................................................29-6 Figure 29-3 IEEE 802.1ag OAMPDU.............................................................................................................29-11 Figure 29-4 Continuity check diagram.............................................................................................................29-12 Figure 29-5 Loopback test diagram..................................................................................................................29-13 Figure 29-6 Link trace test diagram.................................................................................................................29-14 Figure 29-7 IEEE 802.3ah OAMPDU.............................................................................................................29-15 Figure 29-8 Packet format of the information OAMPDU...............................................................................29-17 Figure 29-9 Packet format of event notification OAMPDU............................................................................29-21 Figure 29-10 Packet format of the loopback control OAMPDU.....................................................................29-22 Figure 29-11 Connectivity check of the MPLS OAM.....................................................................................29-40 Figure 29-12 Application scenarios of MPLS OAM.......................................................................................29-41 Figure 29-13 Application scenario of the PW OAM.......................................................................................29-47 Figure 30-1 Point-to-Point LPT networking diagram........................................................................................30-2 Figure 30-2 Point-to-Multipoint LPT networking diagram...............................................................................30-3 Figure 32-1 Application of the synchronous Ethernet in the wireless access network......................................32-2 Figure 32-2 Realization principle of the synchronous Ethernet.........................................................................32-4 Figure 34-1 Outloop.........................................................................................................................................34-18 Figure 34-2 Inloop............................................................................................................................................34-18 Figure 34-3 Outloop.........................................................................................................................................34-19 Figure 34-4 Inloop............................................................................................................................................34-20 Figure 34-5 Inloop............................................................................................................................................34-21 Figure 34-6 Outloop.........................................................................................................................................34-22 Figure 34-7 Inloop............................................................................................................................................34-22 Figure 34-8 Outloop.........................................................................................................................................34-23 Figure 34-9 Inloop............................................................................................................................................34-23 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv

Figures

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Figure 34-10 Outloop.......................................................................................................................................34-24

Figure 34-11 Inloop..........................................................................................................................................34-25 Figure 34-12 Outloop.......................................................................................................................................34-26 Figure 34-13 Inloop..........................................................................................................................................34-26 Figure 34-14 Outloop.......................................................................................................................................34-27 Figure 34-15 Inloop..........................................................................................................................................34-28

xxxvi

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Tables

Tables
Table 1-1 SDH board parameters.........................................................................................................................1-9 Table 1-2 PDH board parameters.......................................................................................................................1-10 Table 1-3 RTN board parameters.......................................................................................................................1-10 Table 1-4 Data board parameters........................................................................................................................1-11 Table 3-1 SSM allocation...................................................................................................................................3-11 Table 3-2 Methods of selecting clock sources in different modes.....................................................................3-12 Table 5-1 Configuration of the synchronous data port.........................................................................................5-8 Table 5-2 Configuration of the synchronous data port.........................................................................................5-8 Table 5-3 Configuration of the asynchronous data services...............................................................................5-11 Table 5-4 Configuration of the asynchronous data services...............................................................................5-12 Table 6-1 Configuration of the external alarms....................................................................................................6-4 Table 6-2 Configuration of the external alarms....................................................................................................6-4 Table 7-1 SDH board parameters.........................................................................................................................7-2 Table 7-2 PDH board parameters.........................................................................................................................7-3 Table 7-3 RTN board parameters.........................................................................................................................7-3 Table 7-4 Data board parameters..........................................................................................................................7-4 Table 7-5 Methods used by ports to process data frames...................................................................................7-28 Table 7-6 Methods used by ports to process data frames...................................................................................7-35 Table 8-1 Application scenario of PDH interfaces...............................................................................................8-5 Table 8-2 Application scenario of Ethernet interfaces.......................................................................................8-10 Table 8-3 Application scenario of microwave interfaces...................................................................................8-14 Table 11-1 Availability of the 1+1 HSB feature................................................................................................11-3 Table 11-2 Availability of the 1+1 HSB feature................................................................................................11-3 Table 11-3 Availability of the 1+1 FD feature.................................................................................................11-10 Table 11-4 Availability of the 1+1 FD feature.................................................................................................11-10 Table 11-5 Availability of the 1+1 SD feature.................................................................................................11-19 Table 11-6 Availability of the 1+1 SD feature.................................................................................................11-19 Table 12-1 MSP type..........................................................................................................................................12-4 Table 12-2 Preemptible relation of priorities of MSP protection switching......................................................12-5 Table 12-3 SNCP parameters.............................................................................................................................12-8 Table 12-4 Availability of the N+1 protection feature.....................................................................................12-13 Table 12-5 Availability of the N+1 protection feature.....................................................................................12-13 Table 12-6 Description of the configuration flow of the N+1 protection mode...............................................12-18 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvii

Tables

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Table 12-7 Availability of the linear MSP solution.........................................................................................12-29 Table 12-8 Availability of the linear MSP solution.........................................................................................12-29 Table 12-9 Availability of the two-fiber bidirectional ring MSP.....................................................................12-40 Table 12-10 Availability of the SNCP solution................................................................................................12-47 Table 12-11 Availability of the SNCP solution................................................................................................12-47 Table 12-12 Parameters for MPLS APS 1+1 protection..................................................................................12-62 Table 12-13 Parameters for MPLS APS 1:1 protection...................................................................................12-63 Table 12-14 Description of each filed in R-APS specific information............................................................12-72 Table 12-15 Boards and equipment versions of the OptiX RTN 910, OptiX RTN 950, OptiX RTN 620 and NMS versions that support the ERPS protection........................................................................................................12-74 Table 12-16 Availability of the LAG feature...................................................................................................12-83 Table 12-17 Availability of the LAG feature...................................................................................................12-83 Table 13-1 Service requirements......................................................................................................................13-36 Table 13-2 Planning information of the radio link...........................................................................................13-37 Table 13-3 Attributes of the IF 1+1 protection ................................................................................................13-39 Table 13-4 Information of IF ports (NE1 and NE2).........................................................................................13-39 Table 13-5 Information of IF ports (NE3, NE4, and NE5)..............................................................................13-40 Table 13-6 Information of ODU ports (NE1 and NE2)....................................................................................13-40 Table 13-7 Information of ODU ports (NE3, NE4, and NE5).........................................................................13-41 Table 13-8 Clock information..........................................................................................................................13-44 Table 13-9 Orderwire information...................................................................................................................13-44 Table 13-10 Planning information of the radio link.........................................................................................13-66 Table 13-11 Attributes of the IF 1+1 protection...............................................................................................13-67 Table 13-12 Information of IF ports.................................................................................................................13-67 Table 13-13 Information of ODU ports............................................................................................................13-68 Table 13-14 PDH service configuration...........................................................................................................13-68 Table 13-15 Orderwire information.................................................................................................................13-68 Table 13-16 Planning information of the radio link between NE3 and NE5...................................................13-78 Table 13-17 Attributes of the IF 1+1 protection (NE5)....................................................................................13-79 Table 13-18 Information of ODU ports (NE5).................................................................................................13-79 Table 13-19 PDH service configuration (NE5)................................................................................................13-80 Table 13-20 Orderwire information.................................................................................................................13-80 Table 14-1 Tag types defined by using the TPID...............................................................................................14-5 Table 14-2 Processing mode of data frames at ports with different tags..........................................................14-13 Table 14-3 Transparent bridge and virtual bridge............................................................................................14-15 Table 14-4 Types of bridges supported by the Ethernet boards.......................................................................14-16 Table 14-5 Parameters of external Ethernet ports............................................................................................14-51 Table 14-6 Parameters of internal Ethernet ports.............................................................................................14-51 Table 14-7 Parameters of external Ethernet ports............................................................................................14-58 Table 14-8 Parameters of internal Ethernet ports.............................................................................................14-58 Table 14-9 Parameters of EPL services............................................................................................................14-58 Table 14-10 Parameters of external Ethernet ports..........................................................................................14-67 Table 14-11 Parameters of internal Ethernet ports...........................................................................................14-67

xxxviii

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Tables

Table 14-12 Parameters of EPL services..........................................................................................................14-68 Table 14-13 Parameters of external Ethernet ports..........................................................................................14-76 Table 14-14 Parameters of internal Ethernet ports...........................................................................................14-76 Table 14-15 Parameters of Ethernet LAN services..........................................................................................14-76 Table 14-16 Parameters of external Ethernet ports..........................................................................................14-85 Table 14-17 Parameters of internal Ethernet ports...........................................................................................14-86 Table 14-18 Parameters of Ethernet LAN services..........................................................................................14-87 Table 14-19 Link capacity..............................................................................................................................14-102 Table 14-20 Information for planning a radio link.........................................................................................14-103 Table 14-21 Attributes of the IF 1+1 protection.............................................................................................14-104 Table 14-22 Clock information...................................................................................................................... 14-106 Table 14-23 Orderwire information............................................................................................................... 14-106 Table 14-24 Parameters of external ports of the EMS6 board....................................................................... 14-107 Table 14-25 Parameters of external ports of the IFH2 board.........................................................................14-108 Table 14-26 Parameters of Ethernet private line services (NE1)...................................................................14-108 Table 14-27 Parameters of Ethernet private line services (NE2)...................................................................14-108 Table 14-28 Flow configuration.....................................................................................................................14-109 Table 14-29 Parameters of the CARa.............................................................................................................14-109 Table 14-30 Parameters of the CoS................................................................................................................14-110 Table 14-31 Parameters of the link aggregation group.................................................................................. 14-110 Table 14-32 Parameters of external Ethernet ports........................................................................................ 14-111 Table 14-33 Parameters of the CoS of the IFH2 board (NE2).......................................................................14-111 Table 14-34 Parameters of Ethernet services (NE3)...................................................................................... 14-111 Table 14-35 Line services between C-aware ports.........................................................................................14-149 Table 14-36 Line services between a C-aware port and an S-aware port...................................................... 14-150 Table 14-37 Line services between S-aware ports.........................................................................................14-151 Table 14-38 Characteristics of the IEEE 802.1ad bridge...............................................................................14-151 Table 14-39 LAN services that enter and exit the IEEE 802.1ad bridge through the C-aware port..............14-152 Table 14-40 LAN services that enter and exit the IEEE 802.1ad bridge through the S-aware port...............14-153 Table 14-41 Availability of the QinQ feature................................................................................................ 14-154 Table 14-42 Description of the configuration flow of the QinQ line service.................................................14-160 Table 14-43 Description of the configuration flow of the EVPLAN service that is based on the 802.1ad bridge .........................................................................................................................................................................14-162 Table 14-44 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-negotiation mode) .........................................................................................................................................................................14-174 Table 14-45 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-negotiation mode) .........................................................................................................................................................................14-175 Table 14-46 Availability of the Ethernet port feature.................................................................................... 14-177 Table 14-47 Methods used by ports to process data frames...........................................................................14-189 Table 14-48 Availability of the Ethernet encapsulation and mapping feature...............................................14-194 Table 14-49 UPI values of the client management frame.............................................................................. 14-198 Table 14-50 LCAS CTRL words ...................................................................................................................14-201 Table 14-51 Methods used by ports to process data frames...........................................................................14-212 Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxix

Tables

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management Table 14-52 Data frame processing method of the switch port......................................................................14-217 Table 14-53 Availability of the VLAN..........................................................................................................14-219 Table 14-54 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared EVPL service) .........................................................................................................................................................................14-222 Table 14-55 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-shared EVPL service)............................................................................................................................................................14-222 Table 14-56 Three Types of Bridges Supported by the Ethernet Switching Board.......................................14-234 Table 14-57 Availability of Layer 2 Switching..............................................................................................14-240 Table 14-58 CoS Type....................................................................................................................................14-277 Table 14-59 Availability of the QoS Feature.................................................................................................14-278 Table 15-1 Scheduling and application..............................................................................................................15-6 Table 15-2 Table for mapping relations between the RTN equipment and the supported QoS policies...........15-8 Table 15-3 PHB service level and mapping PHB service quality......................................................................15-9 Table 15-4 Mapping relation between the ATM service type and PHB service class.....................................15-19 Table 15-5 Tasks for configuring the UNI-UNI E-Line service......................................................................15-29 Table 15-6 Tasks for configuring the UNI-UNI E-Line service carried by a port...........................................15-30 Table 15-7 Tasks for configuring the UNI-NNI E-Line service carried by PWs.............................................15-30 Table 15-8 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link...................................15-31 Table 15-9 Tasks for configuring the UNI-UNI E-Line service......................................................................15-38 Table 15-10 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link.................................15-39 Table 16-1 Availability of the XPIC feature......................................................................................................16-2 Table 17-1 ATPC performance..........................................................................................................................17-2 Table 17-2 Availability of the ATPC feature.....................................................................................................17-3 Table 17-3 Availability of the ATPC feature.....................................................................................................17-3 Table 18-1 Radio work modes in the case of hybrid microwave frames...........................................................18-5 Table 18-2 Availability of the Hybrid microwave feature.................................................................................18-7 Table 18-3 Availability of the Hybrid microwave feature.................................................................................18-7 Table 25-1 CES service clock type.....................................................................................................................25-4 Table 25-2 Tasks for configuring the UNI-UNI CES service............................................................................25-5 Table 25-3 Tasks for configuring the UNIs-NNI CES service..........................................................................25-6 Table 26-1 ATM service type and traffic...........................................................................................................26-5 Table 26-2 Tasks for configuring the UNI-UNI ATM service...........................................................................26-8 Table 26-3 Tasks for configuring the UNIs-NNI ATM service.........................................................................26-9 Table 26-4 ATM Interface................................................................................................................................26-11 Table 29-1 Availability of the ETH-OAM Feature..........................................................................................29-10 Table 29-2 Availability of the ETH-OAM Feature..........................................................................................29-10 Table 29-3 Mapping relation between values and OMA packet types (non-standard MP).............................29-11 Table 29-4 Mapping relation between code values and OAM packet types....................................................29-15 Table 29-5 Details of OAM configuration bytes..............................................................................................29-18 Table 29-6 Mapping relation between OAM working modes and OAM functions.........................................29-20 Table 29-7 Application scenarios of MPLS OAM detection methods.............................................................29-41 Table 29-8 Classification of the OAM function layers....................................................................................29-49 Table 29-9 Application scenarios of ATM OAM detection methods..............................................................29-51

xl

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Tables

Table 30-1 Availability of the LPT feature(RTN600)........................................................................................30-4 Table 30-2 Availability of the LPT feature(RTN900)........................................................................................30-4 Table 30-3 Parameter of the Point-to-Point LPT(RTN600).............................................................................30-13 Table 30-4 Parameter of the Point-to-Multipoint LPT(RTN600)....................................................................30-14 Table 30-5 Parameter of the LPT(RTN900).....................................................................................................30-14 Table 31-1 List of RMON alarm entries............................................................................................................31-5 Table 31-2 List of RMON performance entries.................................................................................................31-5 Table 31-3 Availability of the RMON Feature..................................................................................................31-7 Table 31-4 Availability of the RMON Feature..................................................................................................31-8 Table 32-1 Availability of the synchronous Ethernet feature.............................................................................32-2

Issue 02 (2010-09-24)

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

xli

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

Creating NEs, Links, and Topology Subnets

About This Chapter


On the U2000, you can create NEs , Links, and Topology Subnets to perform management through the U2000. 1.1 Creating NEs Each set of the equipment is represented as an NE on the U2000. Before the U2000 manages the actual equipment, you need to create the corresponding NEs on the U2000. There are two ways of creating NEs: creating a single NE (manually) and creating NEs in batches (through search). When you add an NE or certain NEs to a large network, for example, during deployment, it is recommended to create NEs in batches through search. In other scenarios, it is recommended to create a single NE manually. 1.2 Configuring the NE Data Though an NE is successfully created, it is not configured. You need to configure the NE first so that the U2000 can manage and operate the NE. 1.3 Checking Board Parameters To learn about board parameter status, you can check board parameters. Before actual configuration operations in networking, you need to check board parameters, to make sure that the board parameter status meets the requirements of actual networking. 1.4 Creating Links You need to create fibers before managing services on the U2000 in the end-to-end manner. 1.5 Creating a Topology Subnet The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet.

Issue 02 (2010-09-24)

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

1-1

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1.1 Creating NEs


Each set of the equipment is represented as an NE on the U2000. Before the U2000 manages the actual equipment, you need to create the corresponding NEs on the U2000. There are two ways of creating NEs: creating a single NE (manually) and creating NEs in batches (through search). When you add an NE or certain NEs to a large network, for example, during deployment, it is recommended to create NEs in batches through search. In other scenarios, it is recommended to create a single NE manually. 1.1.1 Creating NEs in Batches When the U2000 communicates properly with the GNE, you can create NEs in batches by searching for all NEs that communicate with the GNE, by using the IP address of the GNE or the network segment to which the IP address is associated, or by using the NSAP address of the NE. This method is quicker and more accurate than manual creation. 1.1.2 Creating a Single NE After the NE is created, you can use the U2000 to manage the NE. Although creating a single NE is not as fast and exact as creating NEs in batches, you can use this method regardless of whether the data is configured on the NE or not.

1.1.1 Creating NEs in Batches


When the U2000 communicates properly with the GNE, you can create NEs in batches by searching for all NEs that communicate with the GNE, by using the IP address of the GNE or the network segment to which the IP address is associated, or by using the NSAP address of the NE. This method is quicker and more accurate than manual creation.

Prerequisite
l l l You must be an NM user with "NE administrator" authority or higher. The U2000 must communicate properly with the GNE. The NE Explorer instance of the NEs must be created.

Procedure
Step 1 Choose File > Discovery > NE from the main menu. The Auto Discovery window is displayed. Step 2 Click the Transport NE Search tab. Step 3 Optional: Enter the network segment or IP addresses NEs to search for the NEs. 1. 2. Click Add and the Input Search Domain dialog box is displayed. Set Address type to IP Address Range of GNE, IP Address of GNE or NSAP Address, and enter the information of the search address. Click OK.

1-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

NOTE

You can repeat Steps 2 through 3 to add more search fields. You can delete the system default search field. l If you use IP address to search for NEs, and the IP address of the U2000 computer and that of the GNE are within the same network segment, you can select IP Address Range of GNE or IP Address of GNE. l If the IP addresses are not within the same network segment, select only IP Address of GNE. l If you use NSAP address, you can only select NSAP address.

Step 4 Optional: If you fail to enter a network segment correctly, enable IP auto discovery and enter the User Name and Password of the NEs.
NOTE

After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEs related to the GNE.

Step 5 In the Search for NE area, perform the following operations: l l Select Search for NE. All NEs in the selected domain are searched out. Select Create device after search, enter the NE User and Password.

NOTE

l The default NE user is root. l The default password is password.

Select Upload after create. The data related to the NEs are uploaded to the U2000 after the NEs are created.
NOTE

You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NE data at a time.

Step 6 Click Next and the Result area is displayed.


Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 7 When the search ends or if you click Stop, select the uncreated NEs in the Result list and click Create. The Create dialog box is displayed. Step 8 Enter the NE user name and password.
NOTE

l The default NE user is root. l The default password is password.

Step 9 Click OK. ----End

Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows: l l The password for the NE user is incorrect. Enter the correct password for the NE user. The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

1.1.2 Creating a Single NE


After the NE is created, you can use the U2000 to manage the NE. Although creating a single NE is not as fast and exact as creating NEs in batches, you can use this method regardless of whether the data is configured on the NE or not.

Prerequisite
l l l You must be an NM user with "NM operator" authority or higher. The license must be installed and the license must support creating the NE of the type. The NE Explorer instance of the NEs must be created.

Context
First create a GNE, and then create a non-gateway NE. If the NE is not created properly or the communication between the NE and the U2000 is abnormal, the NE is displayed in gray color.

Procedure
Step 1 Choose File > Create > NE from the main menu. The Create NE dialog box is displayed. Step 2 Select the NE type from the Object Type tree. Step 3 Complete the following information: ID, Extended ID, Name and Remarks. Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6. Step 5 Choose Gateway Type, Protocol and set the IP address or serial port number and serial port rate. 1. 2.
1-4

Select Gateway from the Gateway Type drop-down list. Select the Protocol type.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

If the U2000 communicates with NEs through IP protocol

Do...

Select IP from the Protocol drop-down list. Enter the IP Address and use the default value for the Port number of the GNE. Select OSI from the Protocol drop-down list. Enter the NSAP Address of the GNE.

OSI protocol

NOTE

The domain address that contains a maximum of 13 bytes is entered by the user. NSEL is the port number of the network-level protocol, with a fixed value of 1d (one byte).

Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE is associated to from the Affiliated Gateway drop-down list. Step 7 Enter the NE User and Password.
NOTE

The default NE user is root, and the default password is password.

Step 8 Click OK. Click in the blank space of the Main Topology and the NE icon appears in the position where you clicked. ----End

Result
After an NE is successfully created, the system automatically saves the information, such as the IP address, NSAP address, subnet mask, and NE ID to the U2000 database.

Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows: l l l The communication between the U2000 and the NE is abnormal. Check the settings of communication parameters, such as the IP address of the NE and NE ID. The password for the NE user is incorrect. Enter the correct password for the NE user. The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

1.2 Configuring the NE Data


Though an NE is successfully created, it is not configured. You need to configure the NE first so that the U2000 can manage and operate the NE. 1.2.1 Configuring the NE Data Manually You need to manually configure the NE data during initialization. The operation clears original service data from NEs and then deliver the new configuration data to NEs. 1.2.2 Replicating the NE Data
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-5

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

You can replicate the data of an existing NE to a new NE, if the existing NE is already configuration and if the existing NE is of the same NE type and the same NE version as the new NE. 1.2.3 Uploading the NE Data By uploading the NE data, you can synchronize the current NE configuration data to the network management system directly.

1.2.1 Configuring the NE Data Manually


You need to manually configure the NE data during initialization. The operation clears original service data from NEs and then deliver the new configuration data to NEs.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully.

Background Information
When you manually configure the NE data, the original service data is cleared from the NEs. Therefore, the communications between the NEs and the U2000 may be interrupted and the subsequent procedures of manually configuring the NE data cannot be performed. In the case of the RTN NEs, this operation is used for configuring gateway NEs for the first time.

Procedure
Step 1 Select the NE whose data you want to configure. Double-click the unconfigured NE on the Main Topology. The NE Configuration Wizard dialog box is displayed. Step 2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating that manual configuration clears the data on the NE side. Step 3 Click OK. The Confirm dialog box is displayed indicating that manual configuration interrupts the service on the NE. Step 4 Click OK. The Set NE Attribute dialog box is displayed. Step 5 Set NE Name, Equipment Type, NE Remarks and Subrack Type and then click Next. The NE slot window is displayed. Step 6 Optional: Click Query Logical Information to query the logical boards of the NE. Step 7 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE

The Query Logical Information and Query Physical Information operations cannot be performed for a preconfigured NE.

Step 8 Right-click on the slot to add a board. Click Next to display the Send Configuration window. Step 9 Choose Verify and Run as required and click Finish.
NOTE

Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.

----End
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

1.2.2 Replicating the NE Data


You can replicate the data of an existing NE to a new NE, if the existing NE is already configuration and if the existing NE is of the same NE type and the same NE version as the new NE.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully. The type and NE software version of the source NE must be consistent with the type and software version of the replicated NE.

Procedure
Step 1 Select the NE whose data you need to replicate. NE to Be Configured RTN equipment Operation Double-click the unconfigured NE on the Main Topology. Then, the NE Configuration Wizard dialog box is displayed.

Step 2 Select Copy NE Data and click Next. The NE Replication dialog box is displayed. Step 3 Select the NE from the drop-down list and click Start. The Confirm dialog box is displayed, indicating that the replication operation copies all the data of the source NE to overwrite all the data of the selected NE.

NOTE

After the NE data is replicated, only the data on the U2000 side is changed, but the data on the equipment side is not changed. Data coping between the NEs of different equipment type is not recommended.

Step 4 Click OK. The Confirm dialog box is displayed, indicating that the replication operation results in the loss of the original data of the NE to which the data is copied. Step 5 Click OK to start the replication. The Operation Result dialog box is displayed after a few seconds.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-7

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 6 Click Close. ----End

1.2.3 Uploading the NE Data


By uploading the NE data, you can synchronize the current NE configuration data to the network management system directly.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully.

Procedure
Step 1 Select the NE whose data you need to Replicate. NE to Be Configured RTN equipment Operation Double-click the unconfigured NE on the Main Topology. The NE Configuration Wizard dialog box is displayed.

Step 2 Select Upload and click Next. The Confirm dialog box is displayed, indicating that the upload may take a long time. Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading is complete. Step 4 Click Close. ----End

1.3 Checking Board Parameters


To learn about board parameter status, you can check board parameters. Before actual configuration operations in networking, you need to check board parameters, to make sure that the board parameter status meets the requirements of actual networking.

Procedure
Step 1 Select the corresponding navigation path and check the related board parameters. 1. Check SDH board parameters. For the SDH board parameters, see Table 1-1.

1-8

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

Table 1-1 SDH board parameters Board Type SDH Parameter Laser Switch Navigation Path a. In the NE Explorer, select a board. b. Choose Configuration > SDH Interface from the Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list. Application Scenario When configuring services on an optical interface of a board, enable this parameter. l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: The loop is performed toward the local NE. l Outloop: The loop is performed toward the opposite NE. Inloop and outloop of an optical interface affect services. They are used to locate faults. 2. Check PDH board parameters. For the PDH board parameters, see Table 1-2.

Optical(Electrical) Interface Loopback

Issue 02 (2010-09-24)

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

1-9

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Table 1-2 PDH board parameters Boar d Type Paramet er Tributary Loopback Navigation Path Application Scenario l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: When input service signals reach the tributary board of the target NE, the signals revert to the original trail. This function is used to locate faults of each service path. l Outloop: When input service signals reach the tributary board through the input port of the local NE, the signals are looped back directly to the service output end. l Non-loaded: The service path does not process the services that are carried, to suppress alarms in non-loaded service paths. l Load: The service path processes the services that are carried. In the case of a tributary board that has services, set this parameter to Load. Normal, Retiming Mode of Tributary Clock, Retiming Mode of Cross-Connect Clock Default: Normal Sets the retiming mode of the board. The default value is usually selected.

PDH

Service Load Indication

Retiming Mode

a. In the NE Explorer, select a board. b. Choose Configuratio n > PDH Interface from the Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list.

3.

Check RTN board parameters. For the RTN board parameters, see Table 1-3. Table 1-3 RTN board parameters Boar d Type Paramet er Radio Work Mode RTN Navigation Path a. In the NE Explorer, select a board. b. Choose Configuratio n > IF Interface from the Application Scenario Specifies the microwave working mode. Its formats are service capacity, working bandwidth and modulation mode. The transmit end and the receive end must have the same settings of the microwave working mode. Radio Link ID: 1 to 4094

Radio Link ID

1-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

Boar d Type

Paramet er IF Port Loopback

Navigation Path Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list.

Application Scenario Sets the loopback status of an intermediate frequency interface on the equipment. Non-Loopback refers to the normal status. It is not required to set loopback during normal equipment operation. Outloop means that the input signal passes through the ingress port and reaches the intermediate frequency board at the local NE and then is directly loopbacked to the service egress end. Inloop means that the input signal returns from the intermediate frequency board of the destination NE along the original trail. This function is usually used to locate faults for various IF interfaces. Performing loopback on an intermediate frequency interface is a diagnosis function which may affect services of related ports. Exercise caution before performing this function.

2M Wayside Enable Status ATPC Enable Status

Enables or disables a 2 Mbit/s bypath service. This parameter is available only when you set Radio Work Mode to STM-1,28MHz, 128QAM. When the ATPC is enabled, according to the current receive power of the ODU and the set ATPC thresholds, the ATPC module inserts the ATPC overhead. According to the ATPC overhead, the opposite ODU adjusts the transmit power. When the ATPC is disabled, the ATPC module does not insert any ATPC overhead.

4.

Check data board parameters. For the data board parameters, see Table 1-4. Table 1-4 Data board parameters Boar d Type Ethern et Parame ter Enabled/ Disabled Navigation Path a. In the NE Explorer, select a board. b. Choose Configuration > Application Scenario

When configuring Ethernet board port services, set the port to Enabled.

Issue 02 (2010-09-24)

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

1-11

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Boar d Type

Parame ter Working Mode Maximu m Frame Length

Navigation Path Ethernet Interface Management > Ethernet Interface from the Function Tree. c. Click External Port. d. Click the Basic Attributes tab.

Application Scenario Set the working mode of Ethernet ports according to networking configuration requirements. When a packet exceeds the maximum frame length that is set, the packet is discarded. Alternatively, the packet length is minimized to satisfy the specified frame length. By default, the value is set to 1522, unless otherwise specified. l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: Inside the equipment, services from the cross-connect side are looped back to the cross-connect side. This operation affects services configured on ports and is used to locate faults.

MAC Loopbac k

PHY Loopbac k

l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: Inside the equipment, services from the cross-connect side are looped back to the cross-connect side. This operation affects services configured on ports and is used to locate faults.

TAG a. In the NE Explorer, select a board. b. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. c. Click External Port. d. Click the TAG Attributes tab.

l Tag Aware: If the client-side equipment sends tag packets, set the TAG attribute of external ports to Tag Aware. l Access: If the client-side equipment sends untag packets, set the TAG attribute of external ports to Access. l Hybrid: If the client-side equipment sends tag and untag packets, set the TAG attribute of external ports to Hybrid. This parameter is used to identify tags in data packets. During the configuration of VLAN services, set this parameter to Enabled.

Entry Detectio n

1-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

Step 2 Modify board parameters according to service planning and actual board configurations. ----End

1.4 Creating Links


You need to create fibers before managing services on the U2000 in the end-to-end manner. 1.4.1 Creating Fibers Automatically Fiber links are often created through search. By using the fiber search function, you can obtain the information about the fiber link to which the specified optical interface is connected. Then, the radio link to which the optical interface is connected can be created on the Fiber links are often created through search. By using the fiber search function, you can obtain the information about the fiber link to which the specified optical interface is connected. Then, the radio link to which the optical interface is connected can be created on the in the fast manner. In a new network, after you configure the boards of the NEs on the , you need to search all optical interface to create the fiber links networkwide. Then, you can easily monitor the actual working status of each fiber link. This method is often used to create fiber links. in the fast manner. In a new network, after you configure the boards of the NEs on the U2000 1.4.2 Automatically Creating Radio Links Using the fiber/cable search function, you can know whether any radio links are connected at a specified IF interface. This helps you quickly create radio links at the IF interface. For a newly created network, you can search for all the IF interfaces networkwide to create radio links after you complete the board configuration on the U2000. In this way, you can monitor the actual working state of each radio link. 1.4.3 Manually Creating Radio Links After you manually fill in the table, the U2000 can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed.

1.4.1 Creating Fibers Automatically


Fiber links are often created through search. By using the fiber search function, you can obtain the information about the fiber link to which the specified optical interface is connected. Then, the radio link to which the optical interface is connected can be created on the Fiber links are often created through search. By using the fiber search function, you can obtain the information about the fiber link to which the specified optical interface is connected. Then, the radio link to which the optical interface is connected can be created on the in the fast manner. In a new network, after you configure the boards of the NEs on the , you need to search all optical interface to create the fiber links networkwide. Then, you can easily monitor the actual working status of each fiber link. This method is often used to create fiber links. in the fast manner. In a new network, after you configure the boards of the NEs on the U2000

Prerequisite
l l l
Issue 02 (2010-09-24)

You must be an NM user with "NE maintainer" authority or higher. The optical interfaces of every NE must be connected using fibers. The boards of every NE must be created on the U2000.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-13

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Context
l l If conflicting fibers are found during the creation, delete the conflicting fibers on the U2000 before you start creating fibers. When a fiber between two SDH NEs passes through a WDM NE, if the normal fiber between an SDH NE and a WDM NE has been created on the U2000, the fiber found by the trail search function is created as a virtual fiber. If the WDM NE is not created on the U2000, the fiber is created as a normal fiber. When a fiber is created, it is usually bidirectional. But when the fiber is connected to the ports of the REG functions or the SDH and WDM equipment, the fiber is unidirectional.

CAUTION
Fiber/Cable search may interrupt services. Exercise caution when performing this operation.

Procedure
Step 1 CChoose File > Discovery > Fiber from the main menu. The Search for Fiber/Cable window is displayed. Step 2 In the left pane select some ports from one or more NEs and click Search to search for the fibers or cables. A progress bar is displayed showing the progress of the search.
NOTE

l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system only searches for the ports that do not have fibers. l To check if the created fiber is consistent with the actual fiber connection, leave the check box unchecked. l If you check the Do not search the ports with Fiber/Cable created on NMS check box, and if all the selected ports have fibers created, the system displays a message indicating that the search field is null.

Step 3 A prompt is displayed indicating that the operation is successful. Click Close. Step 4 To create fibers, select one or more fibers from the Physical Fiber/Cable Link List list and click Create Fiber/Cable.
NOTE

l When one or more fibers are selected in the Physical Fiber/Cable Link List list, fibers that conflict with the selected fibers, are shown in the Logical Fiber/Cable Link List list. If there is any conflicting fiber, proceed to Step 5 and delete it before creating fibers. l During fiber creation, if all the selected fibers are in the Already created state, the system displays the message as follows: No fiber to create.

Step 5 To delete the conflicting fibers, from the Logical Fiber/Cable Link List list select one or more fibers whose values are Yes for the Conflict with logical link (Y/N) parameter in the Misconnected Fiber list. Click Delete Fiber/Cable. ----End

Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can supplement the information about the fiber by modifying the fiber/cable information.
1-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

1.4.2 Automatically Creating Radio Links


Using the fiber/cable search function, you can know whether any radio links are connected at a specified IF interface. This helps you quickly create radio links at the IF interface. For a newly created network, you can search for all the IF interfaces networkwide to create radio links after you complete the board configuration on the U2000. In this way, you can monitor the actual working state of each radio link.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher. The IF board for each NE must be created on the U2000.

Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are called radio signals. The links that transmit radio signals are called radio links.

Procedure
Step 1 Choose File > Discovery > Fiber from the main menu. Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress bar is displayed.
NOTE

l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system does not search for the ports at which radio links are already created. l If you need to check consistency between the created radio links and the actual radio links, do not check this check box. l If you check this check box and if all the selected ports radio links are created, a dialog box is displayed after the search is complete, telling that the search domain is empty.

Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful. Click Close. Step 4 In the Physical Fiber/Cable Link List list, select one or multiple radio links. Click Create Fiber/Cable.
NOTE

l When you select one or multiple radio links in the Physical Fiber/Cable Link List list, the radio links that conflict with the selected ones are automatically displayed in the Logical Fiber/Cable Link List list. In this case, refer to Step 5 to delete the conflicting radio links before the creation. l During the creation of radio links, if the selected links are all in the Already created state, the system prompts No fiber to create.

Step 5 In the Logical Fiber/Cable Link List list, select one or multiple conflicting radio links (the Conflict with logical link (Y/N) value of which in the Misconnected Fiber list is displayed as Yes), Click Delete Fiber/Cable. ----End

Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can supplement the information about the radio link by modifying the fiber/cable information.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-15

1 Creating NEs, Links, and Topology Subnets

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1.4.3 Manually Creating Radio Links


After you manually fill in the table, the U2000 can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed.

Prerequisite
l l You must be an NM user with "NE maintainer" authority or higher. The boards to be connected with radio links must be created.

Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz is called a radio signal. The link that transmits radio signals is called a radio link.

Procedure
Step 1 Click the to a + sign. shortcut icon on the toolbar of the U2000 Main Topology and the cursor changes

Step 2 Click the source NE of the radio link on the U2000 Main Topology. Step 3 Select the source board and port in the Select Fiber/Cable Source dialog box. Step 4 Click OK and the cursor changes to a + sign. Step 5 Click the sink NE of the radio link on the U2000 Main Topology. Step 6 Select the sink board and port in the Select Fiber/Cable Sink dialog box.
TIP

When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box to exit.

Step 7 Click OK. Enter the information of the fiber or cable in the Create Link dialog box. Step 8 Click OK. The created radio link appears between the source and sink NEs on the U2000 Main Topology. ----End

1.5 Creating a Topology Subnet


The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet.

Prerequisite
You must be an NM user with "NM operator" authority or higher.

Background Information
A topology subnet is created only to simplify the user interface and has no impact on the NEs.
1-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

1 Creating NEs, Links, and Topology Subnets

Procedure
Step 1 Right-click in the blank space of the U2000 Main Topology and choose New > Subnet from the shortcut menu. Step 2 On the subnet tree of the displayed dialog box, select the type of subnet to be created. Step 3 Click the Property tab. Enter the attributes of the subnet. Step 4 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane and click to add the NEs or subnet to the Select Objects pane.
NOTE

In the case of a similar dialog box for selecting objects, l l indicates that objects on the left pane are selected one by one to the right pane. indicates that all objects are selcted from the left pane to the right pane.

Step 5 Click OK. ----End

Issue 02 (2010-09-24)

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

1-17

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2
About This Chapter

DCN Management

The U2000 communicates with NEs, and manages and maintains network nodes through a DCN. In the DCN, the U2000 and NEs are considered as nodes, which are connected by using the Ethernet or DCC physical channels. In practice, the U2000 and NEs may be located at different floors of the same building, different buildings or different cities. Hence, U2000 and NEs are connected through a DCN, which consists of switches and routers. The DCN between the NEs is referred to as an internal DCN. 2.1 DCN Overview The element management system (EMS) sets up communication with NEs through a data communication network (DCN), to manage and maintain these NEs. 2.2 DCN Management Flow This section describes operation tasks of creating and maintaining the DCN by using the U2000. It also describes the relation between the operation tasks. 2.3 Configuring ECC Communication ECC configuration is simple. By default, all Huawei equipment support the ECC protocol and the physical transmission channel is D1-D3 bytes. When the NE ID is set and fibers are connected, the ECC communication is established without any configurations. If you want to modify the ECC communication parameters, locally modify them. Do not remotely modify the parameters because ECC communication may be interrupted and cannot be recovered. If you have to remotely modify the parameters, start from the farthest end. 2.4 Configuring IP Over DCC Communication The IP over DCC communication transmits DCC data by the using IP data packets. The IP over DCC directly operates and maintains remote NEs by using standard TCP/IP protocol. In addition, it realizes the application functions, such as FTP, Telnet, and SNMP. As essential parts of the IP over DCC communication, the dynamic and static routing protocols are used to create route information. 2.5 Configuring OSI Over DCC Communication The OSI protocol is a widely used communication protocol in a network. By using the OSI over DCC communication, a network that consists of equipment from multiple vendors transparently transmits management information at the network layer. Hence, the interconnection with the equipment that supports OSI protocol from the third party is realized.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-1

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2.6 Configuring DCC Transparent Transmission In the case of hybrid networking composed by equipment from Huawei and other vendors, the service channel can be used to transparently transmit the DCC information to the third-party network. The DCC information enters the service channel through the external clock interface or the F1 data interface, and then reaches the third-party network over the related service channel. In this way, the DCC information is transparently transmitted. 2.7 Modifying GNE Parameters During the network optimization and adjustment, you may need to change the GNE type or modify the communication address. 2.8 Changing the GNE for NEs When the GNE that the non-gateway NE belongs to is changed and this non-gateway NE does not belong to another GNE, you need to change the GNE to maintain the communication between the NEs and the U2000. When the number of NEs managed by a certain GNE exceeds a certain number (It is recommended that the number of non-gateway NEs that a GNE manages be no more than 50 or 60 at most.), change the GNE for certain NEs so that the communication between the U2000 and the NEs is not affected. 2.9 Configuring Standby GNEs for NEs You can configure standby GNEs for NEs, to avoid service interruption due to GNE failure. When the GNE for NEs fails, after an automatic switching to the standby GNE, the NEs are connected to the U2000 through the standby GNE. During the switching of GNEs for NEs, the communication may be interrupted transiently. But, this does not affect the services. You can configure up to three standby GNEs for an NE. 2.10 Changing a GNE to a Normal NE When you adjust the communication link between the GNE and the U2000, you can change the GNE to a normal NE. 2.11 Changing a Normal NE to a GNE When you adjust the communication link between the GNE and the U2000, you can change a normal NE to a GNE. 2.12 Checking GNE Switching Status If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically communicates with the U2000 through the standby GNE. To detect the GNE communication failure in time, you need to check the GNE switching status to ensure that the NEs communicate correctly with the U2000 through the GNE. 2.13 Testing the Communication Between the U2000 and the GNE When the network communication fails, you can view the communication between the GNE and the U2000. 2.14 Checking the Network Communication Status On some occasions, the U2000 cannot manage some NEs during the running of the network. By checking the communication status of the network, you can learn the communication status between the U2000 and NEs.

2-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.1 DCN Overview


The element management system (EMS) sets up communication with NEs through a data communication network (DCN), to manage and maintain these NEs. In a DCN, the EMS and NEs are both regarded as network nodes, which can be connected through Ethernet or physical data communication channels (DCCs). In practical networking, the EMS and NEs can be located on different floors in a building, in different buildings, or even in different cities. Therefore, the connection between the EMS and NEs usually requires an external DCN that is composed of equipment such as LAN switch and routers. On the other hand, the DCN among NEs is referred to as an internal DCN. This section describes the internal DCN composed of SDH NEs. See Figure 2-1. Figure 2-1 DCN network
U2000

IP/OSI DCN

External DCN

HW ECC or IP/OSI over DCC

Internal DCN

OptiX NE LAN switch

2.1.1 Background of DCN With the development of network scale, OAM of a network becomes more and more difficult. A stable and robust DCN management network helps lower the OAM cost. 2.1.2 DCN Solutions The OptiX series equipment of Huawei provide multiple DCN solutions. 2.1.3 HWECC Features and Functions To help the U2000 to manage NEs in a network, the embedded control channel (ECC) transmits operation, administration and maintenance (OAM) information by using the D bytes.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-3

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2.1.4 HWECC Application The ECC that Huawei implements provides a more flexible networking mode. The NEs can be connected through an optical port or the Ethernet port for ECC communication. In some special conditions, the Huawei equipment can transparently transmit the OAM information from the third-party equipment. 2.1.5 Basic Concepts of IP over DCC This section introduces the basic concept of IP over DCC. 2.1.6 Features and Functions of IP over DCC IP over DCC has the functions and features that are different from the traditional DCC. 2.1.7 Application of IP over DCC An Ethernet port is used to connect the U2000 and NEs. The NEs are connected to each other through fibers or Ethernet. 2.1.8 Basic Concepts of OSI over DCC This section introduces the basic concept of OSI over DCC. 2.1.9 Features and Functions of OSI over DCC When a transmission network consists of equipment from multiple vendors, the OSI over DCC transparently transmits the management information at the network layer, thereby offering greater flexibility in networking. A user can use the existing DCC resources to uniformly manage the equipment from multiple vendors without creating extra DCN channels. 2.1.10 Application of OSI over DCC According to different network situations, OSI over DCC has two major applications.

2.1.1 Background of DCN


With the development of network scale, OAM of a network becomes more and more difficult. A stable and robust DCN management network helps lower the OAM cost. In a DCN, the DCC bytes in SDH overheads are used as physical channels for DCN management. The customer does not need to set up private DCN channels so that the network construction cost is greatly lowered. For a DCN, the SDH provides the following bandwidth: l l l By using the D1-D3 bytes in SDH regenerator section overheads (RSOH), the SDH provides a 192 kbit/s bandwidth for the DCN. By using the D4-D12 bytes in SDH multiplex section overheads (MSOH), the SDH provides a 576 kbit/s bandwidth for the DCN. By using the D1-D12 bytes in SDH section overheads, the SDH provides a 768 kbit/s bandwidth for the DCN.

Figure 2-2 shows the positions of DCC bytes in SDH overheads.

2-4

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Figure 2-2 Positions of DCC bytes in SDH overheads


A1 B1 D1 A1 A1 A2 E1 D2 AU PTR B2 D4 D7 D10 S1 B2 B2 K1 D5 D8 D11 M1 K2 D6 D9 D12 E2 MSOH A2 A2 J0 F1 D3 RSOH

2.1.2 DCN Solutions


The OptiX series equipment of Huawei provide multiple DCN solutions. The OptiX series equipment support the DCN networking by using the following three protocols: l l l HWECC TCP/IP (IP over DCC) OSI (OSI over DCC)

The HWECC protocol is a private protocol developed by Huawei to support the DCN networking of OptiX equipment. The HWECC protocol features easy configuration and application. As it is private, the HWECC protocol does not meet the management requirements for hybrid networking with equipment from other vendors. The TCP/IP and OSI protocols are standard communication protocols that solve the management issue in the case of hybrid networking with equipment from other vendors. These two protocols can also be used in a network that is composed of only Huawei equipment.
NOTE

When OptiX equipment is interconnected with other vendors' equipment that does not support the TCP/IP and OSI standard communication protocols, Huawei provides the transparent transmission function for DCC bytes, and provides relevant Ethernet service channels to transparently transmit the OAM information.

2.1.3 HWECC Features and Functions


To help the U2000 to manage NEs in a network, the embedded control channel (ECC) transmits operation, administration and maintenance (OAM) information by using the D bytes. The HWECC protocol is mainly applied to transmit OAM information between Huawei optical equipment. The HWECC protocol stake itself does not recognize the OAM information of the third-party equipment. When the networking involves third-party equipment, the OAM information cannot be interconnected but Huawei optical equipment can transparently transmit
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

the OAM information of the third-party equipment. Hence, customers can use the current DCC resources to manage all equipment.

2.1.4 HWECC Application


The ECC that Huawei implements provides a more flexible networking mode. The NEs can be connected through an optical port or the Ethernet port for ECC communication. In some special conditions, the Huawei equipment can transparently transmit the OAM information from the third-party equipment. There are two typical applications of the HWECC protocol for networking schemes.

Application 1 Networking That Involves Only Huawei Equipment


Figure 2-3 shows the networking that involves only Huawei equipment. Figure 2-3 Networking that involves only Huawei equipment

NM computer

HUB1

GNE1

NE NE6 6

HUB2

NE7

NE12

NE2

NE5

NE8

NE11

Network cable Fiber

NE3

NE4 Subnet 1

NE9

NE10 Subnet 2

Such networking requires that one gateway NE (GNE) be present for the communication between other NEs and the U2000 through the Ethernet interface. The NEs communicate with each other through an optical port or Ethernet interfaces. The subnetworks in Figure 2-3 perform the extended ECC communication through Ethernet interfaces, such as NE6 and NE7.
NOTE

Extended ECC means the ECC communication by using the Ethernet when there is no connected optical path between two or more NEs.

Application 2 Networking That Involves Huawei Equipment and Third-Party Equipment


Figure 2-4 shows the networking that involves Huawei equipment and third-party equipment.

2-6

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Figure 2-4 Networking that involves Huawei equipment and third-party equipment

Third-party NM

HUB

NE

NE

NE

NE Third-party equipment NE Huawei equipment NE NE

NE

NE

NE

For such networking, the OAM information of the third-party equipment should travel through Huawei equipment, which provides the function to transparently transmit the DCC. During the transmission, Huawei equipment does not analyze the data. For the DCC transparent transmission, perform the corresponding configuration at each NE along the data transmitting trail.

2.1.5 Basic Concepts of IP over DCC


This section introduces the basic concept of IP over DCC.

IP over DCC
The IP over DCC protocol follows the TCP/IP protocol and is applied to control remote NEs through the Internet. For the IP over DCC protocol, the D bytes (D1-D3 by default) of the overhead are used for communication. Huawei optical equipment supports dynamic and static routing.

OSPF
The open shortest path first (OSPF) protocol is a dynamic routing protocol based on the link state. The NEs update the route table of each NE dynamically by using the OSPF protocol. The OSPF protocol divides an autonomous domain into different areas so that routes are updated within an area or between areas. Normally, the gateway NE (GNE) and all the non-gateway NEs (non-GNEs) managed by it must be within the same OSPF area.

Remote Access
l Gateway NE mode: The ECC protocol is used. U2000 logs in to the GNE that is connected to the computer. Then other NEs can be accessed through the NE ID. After the IP over DCC feature is added, this mode can still be used to access remote NEs. Direct connection mode: The IP over DCC feature is used, and the remote NE can be connected directly through the IP address. You just need to enter the destination IP address
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-7

Issue 02 (2010-09-24)

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

in the login interface. For this mode, however, you need to add in advance the static route or default gateway in the U2000 and the NE that needs to be accessed directly.

2.1.6 Features and Functions of IP over DCC


IP over DCC has the functions and features that are different from the traditional DCC. The DCC is used to transmit the OAM (operation, maintenance, and administration) data between NEs. The protocol stacks used by different vendors are not compatible with each other. Thus, extra overhead bytes or service resources need to be allocated to transmit DCC data transparently in a network composed of multi-vendor products. The IP over DCC meets most of the networking requirements in existing networks without occupying extra overhead bytes or service resources. The IP over DCC simplifies the network structure, saves network resources, and meets the networking requirements quickly. The IP over DCC supports the following features: l Adopting the standard TCP/IP protocol, which makes it be compatible with other vendor's equipment and simplifies the network management l Adopting the forwarding function of the third layer in the protocol stack, which requires extra overhead bytes or service paths l Bringing flexible networking models l Bringing simple upgrade modes and great compatibility. It is easy for IP over DCC to work with new forwarding or multi-protocol features on the application layer

2.1.7 Application of IP over DCC


An Ethernet port is used to connect the U2000 and NEs. The NEs are connected to each other through fibers or Ethernet.

Application 1: Gateway NE Mode


If the U2000 and the GNE connect to the same Ethernet (the U2000 and the GNE need to be in the same subnet), and other NEs are accessed in the gateway NE mode, you need not to add any static routes. As shown in Figure 2-5, the U2000 with the IP address of 129.9.0.100 uses the nearby NE1 as the GNE to access other NEs. You need not to add static routes on the U2000 or NEs. Figure 2-5 Gateway NE mode
NM computer IP address 129.9.0.100 Subnet mask 255.255.255.0

NE4 133.168.0.4 255.255.255.0

NE1 129.9.0.2 255.255.255.0

NE3 133.168.0.3 255.255.255.0

NE name IP address Subnet mask

NE2 133.168.0.2 255.255.255.0

2-8

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Application 2: Gateway NE Mode (by Default Gateway)


If the U2000 is connected to the GNE through a router and other NEs are accessed in the gateway NE mode, you need to add a default gateway on the U2000 and on the GNE. As shown in Figure 2-6, the U2000 with the IP address of 10.100.11.12 connects with the GNE (NE1) through a router and accesses other NEs in the gateway NE mode. In this case, you need to set a default gateway on both the U2000 and NE1. Set the default gateway on the U2000 to 10.100.11.1, and that on NE1 to 129.9.0.254. Figure 2-6 Gateway NE mode (by default gateway)
NM computer IP address 10.100.11.12 Subnet mask 255.255.255.0 Default gateway 10.100.11.1

10.100.11.1 255.255.255.0 Router 129.9.0.254 255.255.255.0 NE1 129.9.0.2 255.255.255.0 129.9.0.254 NE2 133.168.0.2 255.255.255.0 NE4 133.168.0.4 255.255.255.0 NE3 133.168.0.3 255.255.255.0

NE name IP address Subnet mask Default gateway

Application 3: Direct Connection Mode (by Static Routes)


If the U2000 and the GNE connect to the same Ethernet and other NEs are accessed in the direct connection mode, you need to set on the U2000 the default gateway to the IP address of the NE that is connected to the U2000 directly. Or you need to add the static route to the non-GNEs, with the forwarding address as the IP address of the GNE. As shown in Figure 2-7, if the U2000 with the IP address of 129.9.0.100 needs to access NE3 directly, you need to add the static route to 133.168.0.0/24 on the U2000.

Issue 02 (2010-09-24)

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

2-9

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 2-7 Direct connection mode (by static routes)


NM computer 129.9.0.100 IP address 255.255.255.0 Subnet mask Default gateway 129.9.0.2 Static routes Destination: 133.168.0.0 Mask: 255.255.255.0

NE4 133.168.0.4 255.255.255.0

NE1 129.9.0.2 255.255.255.0 NE name IP address Subnet mask Default gateway Static routes NE2 133.168.0.2 255.255.255.0

NE3 133.168.0.3 255.255.255.0

Application 4: Direct Connection Mode through a Router (by Static Routes)


The U2000 connects to the Ethernet port of a certain NE through a router and accesses other NEs in the direct connection mode. You need to perform the following operations. l l l On the U2000, set the static route to the GNE and non-GNEs. On the GNE, set the default route to the U2000. Add static routes to the U2000 on the destination station and the intermediate station.

As shown in Figure 2-8, the U2000 with the IP address of 10.100.11.12 connects to NE1 through a router and accesses NE3 in the direct connection mode. Suppose the IP address of the U2000 is 10.100.11.0 (subnet mask 255.255.255.0). Perform the listed operations: l l l l Add the static route on the U2000 to the gateway 129.9.0.2. Set the default gateway on NE1 to 129.9.0.254. Add the static route on NE2 to 10.100.11.0, with the next hop address as 129.9.0.2. Add the static route on NE3 to 10.100.11.0, with the next hop address as 133.168.0.2.

2-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Figure 2-8 Direct connection mode through a router (by static routes)
NM computer IP address 10.100.11.12 Subnet mask 255.255.255.0 Default gateway 10.100.11.1 Static routes Destination:129.9.0.2 Mask:255.255.255.0 Destination:133.168.0.0 Mask:255.255.255.0

10.100.11.1 255.255.255.0 Router 129.9.0.254 255.255.255.0

NE4 133.168.0.4 255.255.255.0 NE1 129.9.0.2 255.255.255.0 129.9.0.254 NE2 133.168.0.2 255.255.255.0 Static routes Destination:10.100.11.0 Mask: 255.255.255.0 Next hop:129.9.0.2

NE3 133.168.0.3 255.255.255.0 Static routes Destination:10.100.11.0 Mask: 255.255.255.0 Next hop:133.168.0.2

NE name IP address Subnet mask Default gateway Static routes

Configuration Requirements
If NEs communicate with each other through IP over DCC, note the following rules for setting the network scale. It is recommended that the number of non-gateway NEs (including the extended ECC) that a GNE manages be no more than 50 or 60 at most. If NEs communicate with each other through IP over DCC, note the following rules for setting the IP address. l l l l If NEs communicate through IP addresses on the network layer, each NE need to have a unique IP address to avoid routing error due to conflict. NEs support standard A, B, C types of IP addresses, that is, the IP address ranges from 1.0.0.1 to 223.255.255.254. The 127.x.x.x, a loopback address, cannot be used. The IP address must be used with the subnet mask. The subnet mask supports consecutive masks in addition to natural masks, for example, 255.255.224.0. When the IP over DCC communication is used between a GNE and a non-GNE, the IP addresses can be of different network sections.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-11

Issue 02 (2010-09-24)

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

l l l l l

The GNE and non-GNEs cannot be in the same IP subnet. The NEs managed through the same GNE can be in different IP subnets. Do not configure one GNE and one non-GNE into the same IP subnet. The Ethernets in the network must belong to different subnets. Otherwise, a routing error will occur in the whole network. This is not allowed. The subnet masks of the NEs must be the same. The priority of static routes is higher than that of dynamic routes. If there is a conflict, static routes take priority.

2.1.8 Basic Concepts of OSI over DCC


This section introduces the basic concept of OSI over DCC.

NSAP
The OSI protocol takes the network service access point (NSAP) address as the protocol identification for nodes. The format of a simple NSAP address is shown in Figure 2-9. Figure 2-9 Format of a simple NSAP address
AREA ID 1-13 bytes SYS ID 6 bytes NSEL 1 byte

AREA ID: The length is adjustable and ranges from 1 to 13 bytes. The AREA ID is used for L2 routing addressing within a domain. The values should be the same in the L1 route domain and be different in the L2 route domain. SYS ID: The length is fixed to six bytes. The SYS ID is used for route addressing within a domain. For Huawei optical equipment, the former three bytes are fixed to 0x08003E and the latter three bytes are the same with the NE ID. NSEL: The NSEL value is fixed to 0x1D. The AREA ID of Huawei optical equipment is 47000400060001. The ISO8348/AD2 defines a complicated format of the NSAP address, as shown in Figure 2-10. Figure 2-10 Format of a complicated NSAP address
IDP Higher-Order DSP AFI IDI+pad DFI ORG RES RD AREA SYS ID 9 10 11 12 13 14 15 16 17 18 19
NSEL

DSP

Area Address 1 2 3 4 5 6 7 8

20

2-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

This manual does not cover the naming details and functions of each character in the NSAP address format. For the OSI protocol, only the simple NSAP address format needs to be noticed. Huawei equipment applies the simple NSAP address format, which does not affect the interconnection between Huawei equipment and third-party equipment. The configuration of the NSAP address requires that the AREA ID in the same domain should be the same. l l l l l l l l l AFI: 47 IDI: 0005 DFI: 80 ORG: 000000 RES: 0000 RD: 0001 AREA: 0001 SYS ID: 00206005FA68 NSEL: 1D

When a networking involves Huawei equipment and third-party equipment within the same domain, set the AREA ID to 4700058000000000000001 0001.

TP4
The TP4 protocol locates at the transport layer of the OSI protocol stake. The TP4 protocol is applied to create a reliable communication connection. The TP4 protocol can handle the problems as data packet loss, repetition and falsification, which are caused by network faults.

2.1.9 Features and Functions of OSI over DCC


When a transmission network consists of equipment from multiple vendors, the OSI over DCC transparently transmits the management information at the network layer, thereby offering greater flexibility in networking. A user can use the existing DCC resources to uniformly manage the equipment from multiple vendors without creating extra DCN channels. The OSI protocol supports the following three types of network nodes: ES (End System), L1IS (Level 1 Intermediate Systems) and L2-IS (Level 2 Intermediate Systems). The ES only supports limited routing functions. To communicate with other network nodes, an ES can only forward data packets to them by L1-IS or L2-IS that is directly connected to the ES and has the routing function. As a result, only the nodes at the tips of a network rather than the nodes amid a network are allowed to be set to ES. Because of the limited routing function that may be an obstacle in network expansion, it is recommended not to set an NE to an ES during the networking. The networking system of Huawei acts as an ES network node. L1-IS is the default node type of Huawei optical network equipment. It only supports the routing within an area, also known as Level 1 Routing. If a piece of equipment requires the routing across multiple areas, also known as Level 2 Routing, you need to set the node type of the equipment to L2-IS. An L2-IS-type node is in charge of two routing tables, one for intra-area routing and the other one for inter-area routing.

2.1.10 Application of OSI over DCC


According to different network situations, OSI over DCC has two major applications.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-13

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Application 1 Third-Party Equipment Forwarding OAM Information of Huawei Equipment


As shown in Figure 2-11, Huawei equipment locates at the edge of the network and third-party equipment locates at the core. The third-party equipment forwards the OAM information between Huawei equipment and the Huawei U2000. In this case, at least one GNE should be configured in the subnet of the Huawei equipment. Figure 2-11 Third-party equipment forwarding OAM information of Huawei equipment
Huawei NM ES OSI LAN OSI DCN Third-party NM

Level 2 Routing Area

GNE

Legacy Network GNE New Network Third-party NE

Huawei NE

Application 2 Huawei Equipment Forwarding OAM Information of Third-Party Equipment


As shown in Figure 2-12, Huawei equipment locates at the core of the network while third-party equipment at the edge. Huawei equipment forwards the OAM information between the thirdparty NM and equipment.

2-14

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Figure 2-12 Huawei equipment forwarding OAM information of third-party equipment


Huawei NM ES OSI LAN OSI DCN Third-party NM

Level 2 Routing Area

GNE

Legacy Network GNE New Network Third-party NE

Huawei NE

2.2 DCN Management Flow


This section describes operation tasks of creating and maintaining the DCN by using the U2000. It also describes the relation between the operation tasks. To configure and maintain the DCN, see the flow chart in Figure 2-13. During network deployment, set up the communication between NEs according to the planned communication mode. You can perform adjustment during the maintenance according to network situations.

Issue 02 (2010-09-24)

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

2-15

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 2-13 DCN management flow


Required Optional

Configuring ECC Communication

Configuring IP Over DCC Communication

Configuring OSI Over DCC Communication

Common Maintenance Operations

Modifying the NE ID

Modifying the NE ID

Modifying the NE ID

Modifying GNE Parameters

Configuring an Extended ECC Communication Viewing the ECC Route for an NE

Setting NE Communication Parameters Configuring the IP Static Route for an NE Customizing Communication Channels Between NEs Viewing the Communication Status of DCC Channel Querying the OSPF Protocol Status

Setting the NSAP Address for an NE

Changing the GNE for NEs

Configuring the Node Type for an NE Configuring the Communication Protocol Stack and LAPD Role for an Optical Port

Configuring Standby GNEs for NEs

Adding the Manual ECC Route for an NE

Changing a GNE to a Normal NE

Customizing Communication Channels Between NEs

Changing a Normal NE to a GNE

Configuring OSI Tunnel

Configuring Communication for Third-Party Equipment Interconnection Configuring Overhead Services

Checking GNE Switching Status

Customizing Communication Channels Between NEs

Configuring Proxy ARP Querying the Route Information of a Node

Testing the Communication Between the NMS and the GNE

Creating an OSI GNE

Checking the Network Communication Status

2.3 Configuring ECC Communication


ECC configuration is simple. By default, all Huawei equipment support the ECC protocol and the physical transmission channel is D1-D3 bytes. When the NE ID is set and fibers are connected, the ECC communication is established without any configurations. If you want to modify the ECC communication parameters, locally modify them. Do not remotely modify the parameters because ECC communication may be interrupted and cannot be recovered. If you have to remotely modify the parameters, start from the farthest end. 2.3.1 Modifying the NE ID The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE ID, it causes an ECC route conflict and the U2000 cannot manage certain NEs. During the commissioning or expansion process, when you need to adjust the original network planning and change NE IDs, you can use the U2000 to change NE IDs.
2-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.3.2 Configuring an Extended ECC Communication You can establish an extended ECC communication between two shelves without fiber connections through an Ethernet line. In this way, the U2000 manages the equipment in a centralized manner. 2.3.3 Viewing the ECC Route for an NE You can check whether the ECC route is correct. If the ECC route is incorrect, you need to reconfigure it. 2.3.4 Adding the Manual ECC Route for an NE If the ECC route of an NE is inconsistent with the planned route, you can modify the ECC route by manually adding it. 2.3.5 Customizing Communication Channels Between NEs NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types. 2.3.6 Configuring Communication for Third-Party Equipment Interconnection In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's equipment to ensure that the bytes are transmitted transparently.

2.3.1 Modifying the NE ID


The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE ID, it causes an ECC route conflict and the U2000 cannot manage certain NEs. During the commissioning or expansion process, when you need to adjust the original network planning and change NE IDs, you can use the U2000 to change NE IDs.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The NE must be created.

Precautions

CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed. Step 3 Enter the New ID and the New Extended ID. Click OK.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-17

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 4 Click OK in the Warning dialog box. ----End

2.3.2 Configuring an Extended ECC Communication


You can establish an extended ECC communication between two shelves without fiber connections through an Ethernet line. In this way, the U2000 manages the equipment in a centralized manner.

Prerequisite
l l You must be an NM user with "NE maintainer" authority or higher. NEs are properly connected with crossover cables.

Context

CAUTION
This operation may restore the settings of communication, and may interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > ECC Management from the Function Tree. Step 2 Select the ECC Extended Mode.

If you set ECC Extended Mode to Then Auto mode You need not set other parameters.

2-18

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

If you set ECC Extended Mode to Then Specified mode If the NE serves as the server, set Port in the Set Server. If the NE serves as the client, set Opposite IP and Port in the Set Client area.
NOTE l Some NEs can be set as the server and client at the same time. l If you need to set the NE as the server and client at the same time, the port number when the NE serves as the server cannot be duplicate with the port number when the NE serves as the client.

NOTE

l Auto mode: Establish an extended ECC connection automatically. Though this mode is convenient, extra connections will be established and the resource availability is low. It is recommended when there are less than four NEs. No extended ECC can be established automatically unless both the NEs between which an extended ECC is to be established are set to the automatic mode. l Specified mode: Specifies that an extended ECC is to be established between the server and the client. The connection is highly reliable and the bandwidth availability is high. This mode is usually used to establish an extended ECC connection. l For an NE, the two modes cannot be used at the same time to extend ECC.

Step 3 Click Apply and the Warning dialog box is displayed. Click OK. ----End

Postrequisite
After you complete the settings for one NE, you need to configure the settings for the opposite NE to enable the extended ECC communication. Note the following points: l l If you set ECC Extended Mode to Auto mode for an NE, configure the same settings for the opposite NE. If you set ECC Extended Mode to Specified mode for an NE, configure the same settings for the opposite NE. In addition, the roles of the two NEs must be different. That is, if an NE serves as the server, the opposite NE must be the client.

2.3.3 Viewing the ECC Route for an NE


You can check whether the ECC route is correct. If the ECC route is incorrect, you need to reconfigure it.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Issue 02 (2010-09-24)

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

2-19

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link Management from the Function Tree. Step 2 Click Refresh and the ECC route for an NE is displayed in the NE ECC Link Management Table. ----End

2.3.4 Adding the Manual ECC Route for an NE


If the ECC route of an NE is inconsistent with the planned route, you can modify the ECC route by manually adding it.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link Management from the Function Tree. Step 2 Click Add Manual Route and the Add Manual Route dialog box is displayed. Set Destination NE, Transfer NE, Distance and Level. Step 3 Click OK. and then click Close in the Operation Result dialog box. ----End

2.3.5 Customizing Communication Channels Between NEs


NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol Type in the dialog box that is displayed. Step 3 Click OK and then click Close in the Operation Result dialog box. ----End
2-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.3.6 Configuring Communication for Third-Party Equipment Interconnection


In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's equipment to ensure that the bytes are transmitted transparently.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently. This may occur in one of the following three ways: l Huawei's equipment is in the network center, while a third party's equipment is at the edge of the network. The Huawei equipment and third-party equipment are managed by their respective network management systems by using the D1 to D3 bytes. In this case, Huawei's equipment transparently transmits the third party's DCC bytes through three consecutive bytes between D4 and D12. Huawei's equipment is at the edge of the network, while a third party's equipment is in the network center. The Huawei equipment and third-party equipment are managed by their respective network management systems by using the D1 to D3 bytes. In this case, Huawei's equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12. Hence, Huawei's equipment transparently transmits the network management information through the third-party's equipment. Huawei's equipment also transparently transmits the other overhead bytes, for example, E2, F1, or X1-X4, through the idle D bytes.

For the DCC transparent transmission, perform the corresponding configuration at each NE along the data transmitting trail.

Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the Function Tree. Click the DCC Transparent Transmission Management tab. Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed. Select the source and the sink timeslot, port and overhead bytes. Step 3 Click OK. and then click Close in the Operation Result dialog box. ----End

2.4 Configuring IP Over DCC Communication


The IP over DCC communication transmits DCC data by the using IP data packets. The IP over DCC directly operates and maintains remote NEs by using standard TCP/IP protocol. In addition, it realizes the application functions, such as FTP, Telnet, and SNMP. As essential parts of the IP over DCC communication, the dynamic and static routing protocols are used to create route information.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-21

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2.4.1 Modifying the NE ID In the commissioning or expansion process, when you need to adjust the original planning and change the NE ID, you can use the U2000 to achieve it. 2.4.2 Setting NE Communication Parameters When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE. 2.4.3 Configuring the IP Static Route for an NE A static route forwards the data between NEs, or between a router and the computer where the U2000 is installed. 2.4.4 Customizing Communication Channels Between NEs NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types. 2.4.5 Viewing the Communication Status of DCC Channel You can view the communication status of DCC channel. 2.4.6 Querying the OSPF Protocol Status You can query the Open Shortest Path First (OSPF) protocol status. 2.4.7 Configuring Proxy ARP The address resolution protocol (ARP) helps you to query the MAC address of the destination equipment using its IP address. If you enable proxy ARP for a GNE, the GNE can answer ARP requests for other non-gateway NEs, so that you can set IP addresses of NEs of the same network in the same network segment.

2.4.1 Modifying the NE ID


In the commissioning or expansion process, when you need to adjust the original planning and change the NE ID, you can use the U2000 to achieve it.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The NE must be created.

Context

CAUTION
Modifying the NE ID may interrupt NE communication.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
2-22 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Step 3 Enter the New ID and the New Extended ID. Click OK. Step 4 Click OK in the Warning dialog box. ----End

2.4.2 Setting NE Communication Parameters


When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE.

Prerequisite
l l You must be an NM user with "NE maintainer" authority or higher. The IP GNE must be created.

Context

CAUTION
The operation of modifying the NE communication parameters interrupts the communication and affects the services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication Parameters from the Function Tree. Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended ID, NSAP Address. Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning dialog box that appears twice. Click Close in the Operation Result dialog box. ----End

2.4.3 Configuring the IP Static Route for an NE


A static route forwards the data between NEs, or between a router and the computer where the U2000 is installed.

Prerequisite
l You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack Management from the Function Tree. Click the IP Route Management tab. Step 2 Click New and the Create an IP Route dialog box is displayed. Set the Destination Address, Subnet Mask and Gateway.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-23

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 3 Click OK. and then click Close in the Operation Result dialog box. ----End

2.4.4 Customizing Communication Channels Between NEs


NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol Type in the dialog box that is displayed. Step 3 Click OK and then click Close in the Operation Result dialog box. ----End

2.4.5 Viewing the Communication Status of DCC Channel


You can view the communication status of DCC channel.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab. Step 2 Click Query, and view the communication status of DCC channel. ----End
2-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.4.6 Querying the OSPF Protocol Status


You can query the Open Shortest Path First (OSPF) protocol status.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
OSPF is a link-state, hierarchical IGP routing algorithm . OSPF features include least-cost routing, multipath routing, and load balancing. OSPF was derived from an early version of the IS-IS protocol.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack Management from the Function Tree. Click the OSPF Parameter Settings tab. Step 2 Click Query to check if the OSPF protocol status is normal. ----End

2.4.7 Configuring Proxy ARP


The address resolution protocol (ARP) helps you to query the MAC address of the destination equipment using its IP address. If you enable proxy ARP for a GNE, the GNE can answer ARP requests for other non-gateway NEs, so that you can set IP addresses of NEs of the same network in the same network segment.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack Management from the Function Tree. Click the Proxy ARP tab. Step 2 Optional: Click Query. Step 3 Set Value to Disabled or Enabled from the drop-down list. Step 4 Click Apply. ----End

Postrequisite
After you enable proxy ARP, you need to create a static route for each NE.

2.5 Configuring OSI Over DCC Communication


The OSI protocol is a widely used communication protocol in a network. By using the OSI over DCC communication, a network that consists of equipment from multiple vendors transparently
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-25

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

transmits management information at the network layer. Hence, the interconnection with the equipment that supports OSI protocol from the third party is realized. 2.5.1 Modifying the NE ID In the commissioning or expansion process, when you need to adjust the original planning and change the NE ID, you can use the U2000 to achieve it. 2.5.2 Setting the NSAP Address for an NE If the U2000 sets up a TP4 connection with an NE, after you modify the NSAP address range that was previously set according to network planning, the communication between the U2000 and the GNE is interrupted, so you need to re-create the communication. You can use the U2000 to create a TCP connection with an NE, set the NSAP address range for the NE, and then modify the connection mode between the U2000 and the NE to TP4. 2.5.3 Configuring the Node Type for an NE Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For easy expansion of the network, avoid the ES type. 2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port The default protocol stack enabled for optical ports on an NE depends on products. If the current protocol stack enabled for an optical port differs from the planned one, you can configure it on the U2000. If an optical port uses the OSI protocol stack, the link access procedure on the D channel (LAPD) role of all optical ports is User by default. You can set the LAPD role for each optical port based on network planning. The local LAPD role depends on the remote LAPD role. Ensure that the two LAPD roles are different. 2.5.5 Configuring OSI Tunnel When the OSI-protocol-based third-party equipment needs to transfer information through an IP network that consists of Huawei equipment, you can create a virtual OSI tunnel to transparently transmit the information. 2.5.6 Customizing Communication Channels Between NEs NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types. 2.5.7 Querying the Route Information of a Node After you finish configuring and connecting the fibers, you can check whether the route information of each node is correct. If the route information is correct, it means that the nodes can normally communicate with each other. 2.5.8 Creating an OSI GNE After you configure the NSAP address of an NE, you can create an OSI GNE in the TP4 connection mode.

2.5.1 Modifying the NE ID


In the commissioning or expansion process, when you need to adjust the original planning and change the NE ID, you can use the U2000 to achieve it.

Prerequisite
l l
2-26

You must be an NM user with "NE operator" authority or higher. The NE must be created.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Context

CAUTION
Modifying the NE ID may interrupt NE communication.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed. Step 3 Enter the New ID and the New Extended ID. Click OK. Step 4 Click OK in the Warning dialog box. ----End

2.5.2 Setting the NSAP Address for an NE


If the U2000 sets up a TP4 connection with an NE, after you modify the NSAP address range that was previously set according to network planning, the communication between the U2000 and the GNE is interrupted, so you need to re-create the communication. You can use the U2000 to create a TCP connection with an NE, set the NSAP address range for the NE, and then modify the connection mode between the U2000 and the NE to TP4.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication Parameters from the Function Tree. Step 2 Set the NSAP Address. Step 3 Click Apply. Step 4 Choose Administration > DCN Management from the main menu. Click the GNE tab. Step 5 Right-click a GNE and choose Modify GNE from the shortcut menu. Step 6 In the Modify GNE dialog box, select OSI Gateway from the Gateway Type drop-down list, and enter the NSAP Address.

Issue 02 (2010-09-24)

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

2-27

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 7 Click OK and then click Close in the Operation Result dialog box. ----End

2.5.3 Configuring the Node Type for an NE


Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For easy expansion of the network, avoid the ES type.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context

CAUTION
Setting the Configuration Role of an NE may cause service interruption.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the Function Tree. Click the Network Layer Parameters tab. Step 2 Double-click the Configuration Role and select a node type from the drop-down list.

Step 3 Click Apply and click OK in the Confirm dialog box. dialog box. Then, click Close in the Operation Result dialog box. ----End
2-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port
The default protocol stack enabled for optical ports on an NE depends on products. If the current protocol stack enabled for an optical port differs from the planned one, you can configure it on the U2000. If an optical port uses the OSI protocol stack, the link access procedure on the D channel (LAPD) role of all optical ports is User by default. You can set the LAPD role for each optical port based on network planning. The local LAPD role depends on the remote LAPD role. Ensure that the two LAPD roles are different.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab. Step 2 Optional: Click Query. Step 3 Select the optical port you want to set and click Delete. Step 4 Click New and set parameters in the Create dialog box.

Step 5 Click OK. ----End

2.5.5 Configuring OSI Tunnel


When the OSI-protocol-based third-party equipment needs to transfer information through an IP network that consists of Huawei equipment, you can create a virtual OSI tunnel to transparently transmit the information.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
As OSI tunnel is an end-to-end function, you must configure this function at both ends of a tunnel.

Issue 02 (2010-09-24)

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

2-29

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the Function Tree. Click the OSI Tunnel tab. Step 2 Click New. In the Create OSI Tunnel window, set Remote IP Address and LAPD Actor.
NOTE

LAPD Actor refers to the LAPD role at an end. When setting this parameter, you must configure different roles for the two ends of a tunnel.

Step 3 Click OK and then click Close in the Operation Result dialog box. Step 4 Set the parameters in the LAPD Parameter pane.
NOTE

Set the same parameter settings for both ends of a tunnel.

Step 5 Click Apply and then click Close in the Operation Result dialog box. ----End

2.5.6 Customizing Communication Channels Between NEs


NEs communicate with each other through data communications channel (DCC). To meet the requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC rate and allocate DCC resources according to DCC channel types.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol Type in the dialog box that is displayed. Step 3 Click OK and then click Close in the Operation Result dialog box. ----End

2.5.7 Querying the Route Information of a Node


After you finish configuring and connecting the fibers, you can check whether the route information of each node is correct. If the route information is correct, it means that the nodes can normally communicate with each other.

Prerequisite
You must be an NM user with "NE monitor" authority or higher.
2-30 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the Function Tree. Click the Routing Table tab. Step 2 Optional: Click Refresh to query the route information on the NE. Step 3 View the information in the Link Adjacency Table and ensure that the information is correct. Step 4 Click the L1 Routing and the L2 Routing tabs to check if the respective route information is correct. ----End

2.5.8 Creating an OSI GNE


After you configure the NSAP address of an NE, you can create an OSI GNE in the TP4 connection mode.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Choose File > Create > NE from the main menu. Step 2 In the Add Object dialog box, select the NE type from the Object Type tree. Enter the ID, Extended ID, Name and Remarks. Step 3 Select Gateway from the Gateway Type drop-down list. Step 4 Select OSI from the Protocol drop-down list. Step 5 Enter the NSAP Address of the GNE.
NOTE

The NSAP address consists of hexadecimal digits of up to 20 bytes, and its format is: domain address +08003e+NE ID+NSEL. The domain address is composed of 13 bytes and is entered by the user. The NSEL is the port number of the network-layer protocol, with a fixed value of 1d (one byte).

Step 6 Enter the NE user and password.


NOTE

The default NE user of the U2000 must be root, and the default password is password.

Step 7 Click OK. Click on the Main Topology and the NE icon is displayed in the position where you click.
NOTE

If the NE is not created properly or the communication between the NE and the U2000 is abnormal, the NE is displayed in gray.

----End

2.6 Configuring DCC Transparent Transmission


In the case of hybrid networking composed by equipment from Huawei and other vendors, the service channel can be used to transparently transmit the DCC information to the third-party
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-31

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

network. The DCC information enters the service channel through the external clock interface or the F1 data interface, and then reaches the third-party network over the related service channel. In this way, the DCC information is transparently transmitted. 2.6.1 Configuring Communication for Third-Party Equipment Interconnection In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's equipment to ensure that the bytes are transmitted transparently. 2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces If a third-party network exists between networks composed of Huawei equipment, the external clock interfaces can be used to transparently transmit the DCC information. In this way, the U2000 can uniformly manage the networks composed of Huawei equipment. 2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces You can configure the F1 data interface on the SCC board, to transparently transmit the data communication channel (DCC) information between back-to-back NEs.

2.6.1 Configuring Communication for Third-Party Equipment Interconnection


In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's equipment to ensure that the bytes are transmitted transparently.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently. This may occur in one of the following three ways: l Huawei's equipment is in the network center, while a third party's equipment is at the edge of the network. The Huawei equipment and third-party equipment are managed by their respective network management systems by using the D1 to D3 bytes. In this case, Huawei's equipment transparently transmits the third party's DCC bytes through three consecutive bytes between D4 and D12. Huawei's equipment is at the edge of the network, while a third party's equipment is in the network center. The Huawei equipment and third-party equipment are managed by their respective network management systems by using the D1 to D3 bytes. In this case, Huawei's equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12. Hence, Huawei's equipment transparently transmits the network management information through the third-party's equipment. Huawei's equipment also transparently transmits the other overhead bytes, for example, E2, F1, or X1-X4, through the idle D bytes.

For the DCC transparent transmission, perform the corresponding configuration at each NE along the data transmitting trail.

2-32

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the Function Tree. Click the DCC Transparent Transmission Management tab. Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed. Select the source and the sink timeslot, port and overhead bytes. Step 3 Click OK. and then click Close in the Operation Result dialog box. ----End

2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces


If a third-party network exists between networks composed of Huawei equipment, the external clock interfaces can be used to transparently transmit the DCC information. In this way, the U2000 can uniformly manage the networks composed of Huawei equipment.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The 2M external clock interface signals must be accessed to the E1 tributary board through a cable.

Context
As shown in Figure 2-14, when a third-party network exists, external clock interfaces can be used to transmit DCC information. In this way, the U2000 can configure and manage ring 2. Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)

NMS

NE1 Ring 1 Third Party Transport network DCC

NE2 Ring 2

DCC

NOTE

If the third-party network does not exist, you can use a cable to connect the external clock interfaces of NE1 and NE2 to transparently transmit the DCC information.

Figure 2-15 shows how to connect NE1 and NE2. Through the third-party network, NE1 and NE2 can exchange E1 (DCC) signals.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-33

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)
NE1 SDH processing board Third-party network External clock interface
E1(DCC)

SDH processing board

NE2

PDH processing board

External clock interface


E1(DCC)

PDH processing board

The network planning is as follows:


NOTE

l The external clock interfaces of NE1 and NE2 are connected to the first interface of the tributary board. l Configure a bidirectional cross-connection between the first VC-12 timeslot of the tributary board and the first VC-12 timeslot in the first VC-4 of the line board. l The RTN equipment can be connected to the third-party network by using the line board or intermediate frequency (IF) board.

Procedure
Step 1 Configure the DCC transparent transmission through the external clock interface of NE 1. 1. 2. In the NE Explorer, click an NE and choose Communication > DCC Management from the Function Tree. Click DCC Rate Configuration. Click Create. In the Create dialog box displayed, select an external clock interface and set the parameters such as the channel type and protocol type. Click OK. Then, in the Operation Result dialog box, click Close. Select the external clock interface and set its enabling status to Enabled. Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Click Close.

3. 4.

Step 2 Configure a bidirectional cross-connection between the tributary board and the line board. Step 3 Disable the DCC communication of the line board interconnected with the third-party network. 1. 2. 3. 4. Select the port of the corresponding line board, click Enable Status, and select Disable. The Warning dialog box is displayed. Click OK. Click Apply. The Confirmation dialog box is displayed. Click OK. The Operation Result dialog box is displayed indicating that the operation was successful.

Step 4 Follow Steps 1 to 3 to perform the configuration on NE2. ----End

2-34

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces


You can configure the F1 data interface on the SCC board, to transparently transmit the data communication channel (DCC) information between back-to-back NEs.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Orderwire from the Function Tree. Step 2 Click the F1 tab. Step 3 In the Available Data Channel area, select two data channels and click Step 4 Click Apply. In the Operation Result dialog box displayed, click Close. ----End .

2.7 Modifying GNE Parameters


During the network optimization and adjustment, you may need to change the GNE type or modify the communication address.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Precautions

CAUTION
This operation is risky, because it may interrupt the communication.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab. Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu. Step 3 In the Modify GNE dialog box displayed, set Gateway Type. l
Issue 02 (2010-09-24)

When Gateway Type is set to IP Gateway, modify IP Address.


Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-35

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

When Gateway Type is set to OSI Gateway, modify NSAP Address.

NOTE

l Do not modify the Port No.. l Make sure that the IP address of the GNE is in the same network segment as the IP address of the U2000. If they are not in the same network segment, set the corresponding network ports, to make sure that the U2000 can log in to the GNE.

Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close. ----End

2.8 Changing the GNE for NEs


When the GNE that the non-gateway NE belongs to is changed and this non-gateway NE does not belong to another GNE, you need to change the GNE to maintain the communication between the NEs and the U2000. When the number of NEs managed by a certain GNE exceeds a certain number (It is recommended that the number of non-gateway NEs that a GNE manages be no more than 50 or 60 at most.), change the GNE for certain NEs so that the communication between the U2000 and the NEs is not affected.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
2-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Precautions

CAUTION
This operation may interrupt the NE communication.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Step 2 Click the NE tab. Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.

Step 4 Click Apply. Click Close in the Operation Result dialog box. Step 5 Click Refresh. Test the modification with reference to Checking the Network Communication Status. ----End

2.9 Configuring Standby GNEs for NEs


You can configure standby GNEs for NEs, to avoid service interruption due to GNE failure. When the GNE for NEs fails, after an automatic switching to the standby GNE, the NEs are connected to the U2000 through the standby GNE. During the switching of GNEs for NEs, the communication may be interrupted transiently. But, this does not affect the services. You can configure up to three standby GNEs for an NE.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab. Step 2 Select an NE. Double-click GNE2 and select a GNE from the drop-down list.

Issue 02 (2010-09-24)

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

2-37

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

l To configure multiple standby GNEs, select a GNE from the GNE3 and GNE4 drop-down lists. l When the active GNE and standby GNEs fail one by one, the switching sequence is Primary GNE1, GNE2, GNE23, and GNE4. l You can select multiple lines at a time to set standby NEs in batches. Step 3 Click Apply. Click Close in the Operation Result dialog box. ----End

2.10 Changing a GNE to a Normal NE


When you adjust the communication link between the GNE and the U2000, you can change the GNE to a normal NE.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context

CAUTION
This operation may interrupt the service.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab. Step 2 Right-click the GNE that you want to change and choose Delete GNE from the shortcut menu. Click OK in the Confirm and Reconfirm dialog box. Click Close in the Operation Result dialog box. ----End

Postrequisite
After changing the GNE to a normal NE, modify the attributes of the NE that uses the GNE and select another GNE.
2-38 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.11 Changing a Normal NE to a GNE


When you adjust the communication link between the GNE and the U2000, you can change a normal NE to a GNE.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab. Step 2 Right-click a normal NE and choose Change to GNE from the shortcut menu. Step 3 Click OK. Click Close in the Operation Result dialog box.
NOTE

The NE is now changed to a GNE and appears in the GNE tab.

----End

2.12 Checking GNE Switching Status


If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically communicates with the U2000 through the standby GNE. To detect the GNE communication failure in time, you need to check the GNE switching status to ensure that the NEs communicate correctly with the U2000 through the GNE.

Prerequisite
The active and standby GNEs must be created for an NE. You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Step 2 Click the NE tab. Step 3 Click Refresh to query the GNE switching status. ----End

2.13 Testing the Communication Between the U2000 and the GNE
When the network communication fails, you can view the communication between the GNE and the U2000.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-39

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab. Step 2 Right-click the GNE to be tested and choose Test GNE from the shortcut menu. Step 3 Click Close in the Operation Result dialog box. ----End

2.14 Checking the Network Communication Status


On some occasions, the U2000 cannot manage some NEs during the running of the network. By checking the communication status of the network, you can learn the communication status between the U2000 and NEs.

Prerequisite
You must be an NM user with "NE maintainer" authority or higher.

Context
l When an NE uses IP over DCC, to check the NE communication status by using the ping function, you can right-click the NE on the Main Topology and choose Ping from the shortcut menu. You can use the ping function after installing the OSI software on the NE that uses OSI over DCC and the computer where the U2000 resides.

Procedure
l Check the communication status between the U2000 and a non-gateway NE. 1. 2. 3. 4. l Choose Administration > DCN Management from the main menu. Click the NE tab. Click Refresh to view the communication status of all NEs. Select an NE. Right-click in the Communication Status column and choose Test NE from the shortcut menu. The Operation Result dialog box is displayed indicating the test result of the nongateway NE. Choose Administration > DCN Management from the main menu. Click the GNE tab. Click Refresh to view the communication status of the GNE. Right-click an NE and choose Test GNE from the shortcut menu. The Operation Result dialog box is displayed indicating the test result of the GNE.

Check the communication status between the U2000 and the GNE. 1. 2. 3. 4.

----End 2.14.1 Overview of the Inband DCN


2-40 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Inband DCN refers to the networking mode that uses service paths provided by the managed equipment to realize the management of network equipment. In this mode, the network management information is transmitted over service paths of the equipment. 2.14.2 Basic Concepts The DCN contains two networking modes, which are inband networking and outband networking. 2.14.3 Application of the Inband DCN When no special DCN is available for transmitting network management information, you can perform the networking in the inband DCN mode. 2.14.4 Configuring an Inband DCN This section describes how to configure an inband DCN.

2.14.1 Overview of the Inband DCN


Inband DCN refers to the networking mode that uses service paths provided by the managed equipment to realize the management of network equipment. In this mode, the network management information is transmitted over service paths of the equipment.

Objectives and Benefits


A characteristic of the inband DCN mode is the convenient and flexible networking that does not require additional equipment. In this mode, you need not separately provide a network for the DCN and thus save the operation cost.

Realization Principle
As shown in Figure 2-16, in the inband DCN mode, the DCN information and service information share the same path for transmission. Figure 2-16 Inband DCN networking mode
NMS

Ethernet Link

Ethernet Link

Service DCN information

Issue 02 (2010-09-24)

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

2-41

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2.14.2 Basic Concepts


The DCN contains two networking modes, which are inband networking and outband networking.

Inband DCN Scheme


The inband DCN networking involves using the service channels provided by the managed devices to manage the devices in the network. In this mode, the network management information is transmitted through the service channels of the devices. The inband DCN networking is flexible and does not require additional devices. Figure 2-17 shows the networking diagram. Figure 2-17 Inband networking scheme

Managed network Firewall

NOTE

l The devices managed by the U2000 are connected to the IP core network. The NMS center only needs to be connected to the nearby IP devices in the IP core network. You can manage all the devices in the network by configuring the route. l The mode of connection between the NMS center and the IP core network is based on the location of the IP devices near the NMS center. If the U2000 and the nearby IP device are in the same equipment room, you can adopt the LAN networking mode. In the case of the long distance transmission, the networking is realized through private line services.

Outband Networking Scheme


The outband networking scheme involves using other channels except service channels to transmit the network management information and thus realizing the network management. Compared with the inband networking, the outband working scheme provides more reliable management channels. When faults occur on the service channels, you can obtain the network management information in time and perform the real-time monitoring. In the outband mode, you need provide a dedicated communication channel as the maintenance channel that is unrelated to the service channel. In the outband networking scheme, the NMS center can set up the DCN network with the equipment managed in various ways, such as the E1 private line or Ethernet. The U2000 manages the equipment within the management range through the DCN network. Figure 2-18 shows the networking diagram.
2-42 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

Figure 2-18 Outband networking scheme

DCN Firewall

Managed network

NOTE

The U2000 uses the dedicated communication channels to transmit the management information to the managed networks.

2.14.3 Application of the Inband DCN


When no special DCN is available for transmitting network management information, you can perform the networking in the inband DCN mode. When network management information is transmitted through Ethernet ports, the NE distinguishes between network management information and service information by special VLAN ID. When network management information is transmitted through E1 ports, the NE distinguishes between network management information and service information by special MPLS tag.

2.14.4 Configuring an Inband DCN


This section describes how to configure an inband DCN.

Context
The configuration of an inband DCN includes the following contents: 2.14.4.1 Setting NE Communication Parameters When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE. 2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-43

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

The RTN equipment communicates with the U2000 in inband DCN mode. The network management information is transmitted with the service information, and the equipment marks the management information with a default VLAN ID. You can adjust the bandwidth of an inband DCN. 2.14.4.3 Setting the U2000 Access Parameters In the case of the traditional DCN network, the equipment accesses to the U2000 through the SCC board. The RTN equipment can also access to the U2000 through the network interface of the Ethernet board. When the RTN equipment accesses to the U2000 by using the network interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment to communicate with the U2000. 2.14.4.4 Enabling the Port DCN The NM information can be transported in the inband DCN only when the DCN access function is enabled for the ports at two ends of the link. 2.14.4.5 Enabling the Tunnel DCN The NM information can be transported in the IP/GRE Tunnel only when the DCN access function is enabled for the IP/GRE tunnel.

2.14.4.1 Setting NE Communication Parameters


When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE.

Prerequisite
l l You must be an NM user with "NE maintainer" authority or higher. The IP GNE must be created.

Context

CAUTION
The operation of modifying the NE communication parameters interrupts the communication and affects the services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication Parameters from the Function Tree. Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended ID, NSAP Address. Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning dialog box that appears twice. Click Close in the Operation Result dialog box. ----End

2-44

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN


The RTN equipment communicates with the U2000 in inband DCN mode. The network management information is transmitted with the service information, and the equipment marks the management information with a default VLAN ID. You can adjust the bandwidth of an inband DCN.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Context
l If the default VLAN ID of the DCN conflicts with the VLAN ID used by the service, manually modify the VLAN ID of the DCN to ensure that the networkwide DCN uses the same VLAN ID. If the DCN packets do not use all the available bandwidth, the idle bandwidth can be shared with the service packets. It is recommended to perform the modification on non-gateway NEs and then the gateway NE, to prevent the non-gateway NEs from being unreachable to the U2000.

l l

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Bandwidth Management tab, and enter parameters.
NOTE

When setting the parameters, note the following points: l Click Default to adopt the default value. l Generally, use the default VLAN ID. When the VLAN ID used by a service conflicts with that used by a DCN channel, you can define another VLAN ID. Make sure that the networkwide VLAN ID is consistent.

Step 3 Click Apply. ----End

2.14.4.3 Setting the U2000 Access Parameters


In the case of the traditional DCN network, the equipment accesses to the U2000 through the SCC board. The RTN equipment can also access to the U2000 through the network interface of the Ethernet board. When the RTN equipment accesses to the U2000 by using the network interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment to communicate with the U2000.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Issue 02 (2010-09-24)

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

2-45

2 DCN Management

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Context
NOTE

l You need to set the parameters only when the U2000 accesses the equipment by using an Ethernet service board. l By default, the Enabled Status is Disabled.

CAUTION
In the case of the OptiX RTN equipment, when the DCN port is interconnected to the U2000, the IP address of the U2000 and the IP address of the NNI should not be set to the same subnet. This operation may affect the communication between the U2000 and NEs.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Access Control tab, and enter parameters. Step 3 Click Apply. ----End

2.14.4.4 Enabling the Port DCN


The NM information can be transported in the inband DCN only when the DCN access function is enabled for the ports at two ends of the link.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Port Settings tab. Step 3 Select different interface types, and set the corresponding attributes.
NOTE

Take the following precautions when enabling the DCN: l When you configure an Ethernet service that exclusively uses a port, disable the DCN function of the port. l When an E1 port accesses the CES and IMA services, disable the DCN function of the port. l After you enable DCN for an port, the VLAN IDs of other services configured for the port cannot be the same as the VLAN IDs of DCN packets.

Step 4 Click Apply. ----End


2-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2 DCN Management

2.14.4.5 Enabling the Tunnel DCN


The NM information can be transported in the IP/GRE Tunnel only when the DCN access function is enabled for the IP/GRE tunnel.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Tunnel Settings tab. Step 3 Select different tunnel types, and set the corresponding attributes. Step 4 Click Apply. ----End

Issue 02 (2010-09-24)

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

2-47

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

3
About This Chapter

Configuring Clocks

A clock is the basis for the normal running of NEs. You must configure clocks for all NEs prior to configuring services. In addition, you need to configure clock protection for complex networks. 3.1 Clock Configuration Process This section describes the process of clock configuration based on a flow chart. 3.2 Clock Synchronization Scheme This section describes the clock synchronization schemes. You need choose the clock synchronization scheme according to the actual networking architecture. 3.3 Basic Concepts Before clock configuration, you need to master the basic concepts. 3.4 Viewing Clock Synchronization Status If the clocks between NEs in the network are not synchronous, the pointer justification, bit error, even service interruption may occur on NE. Using the U2000, you can learn and monitor the synchronization status of the NE clocks. 3.5 Viewing the Clock Tracing Status Correct clock tracing relationships are critical to ensure the clock synchronization within the entire network. Using the U2000, you can monitor the clock trace status of each NE. 3.6 Configuring the Clock Sources This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock. 3.7 Configuring Protection for Clock Sources This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring networks, protection for the clock sources need to be implemented through the standard SSM protocol or extended SSM protocol. 3.8 Configuring Switching Conditions for Clock Sources

Issue 02 (2010-09-24)

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

3-1

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

If the traceable clock source of an NE is line clock, you can customize switching conditions for the clock source, so that the NE switches to other clocks when the clock source fails. In this manner, services are less affected. 3.9 Configuring the Clock Source Reversion When there are multiple clock sources for an NE, set the clock sources to automatic reversion mode, so that the deteriorated clock source automatically becomes the traceable timing reference after it recovers. 3.10 Modifying the Parameters of the External Clock Output The NE outputs the 2 Mbit/s external clock regardless of the clock quality. 3.11 Setting the Clock Source Quality In a complex clock network, there may be some unknown clock sources. You can uniformly define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources. The NE obtains their quality information automatically for clock sources that are allocated to an NE. You should define the quality level of clock sources only during test and maintenance. 3.12 Configuring the SSM Output If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages automatically. You can prevent clock sources from sending SSM messages to other clock subnets. This helps you to ensure that the equipment of different clock subnets do not affect each other at the edge of clock networks. 3.13 Configuring the Ethernet Clock Source Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock synchronization strategy to ensure that all the NEs in the network trace the same clock. 3.5 Viewing the Clock Tracing Status Correct clock tracing relationships are critical to ensure the clock synchronization within the entire network. Using the U2000, you can monitor the clock trace status of each NE. 3.15 Checking the Clock Switching Status Clock failure may interrupt services. To detect failure of the clock source in time, you need to check the clock switching status. 3.16 Switching a Clock Source When the traceable clock source in a network deteriorates, NEs may not be able to execute a switch on the clock source. You need to manually switch the clock source to prevent clock deterioration from affecting the normal running of NEs.

3-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

3.1 Clock Configuration Process


This section describes the process of clock configuration based on a flow chart. The details of the clock configuration flow varies with the situation. See Figure 3-1, Figure 3-2, and Figure 3-3. Figure 3-1 Configuration flow when SSM protocol is disabled
Required Optional Set switching conditions for clock sources

Set the clock source priority

Set the clock source reversion

View the clock synchronization status

Switch a clock source

Figure 3-2 Configuration flow when standard SSM protocol is enabled


Required Optional

Set the clock source priority

Set the clock source protection

Set switching conditions for clock sources

Set the clock source reversion

View the clock synchronization status

Set the clock source quality

Set the phase-locked source for external clock output

Switch a clock source

Enable the standard SSM protocol

Set the affiliated clock subnet for the NE

Figure 3-3 Configuration flow when extended SSM protocol is enabled


Required Optional

Set the clock source priority

Set the clock source protection

Set switching conditions for clock sources

Set the clock source reversion

View the clock synchronization status

Set the clock source quality

Set the phase-locked source for external clock output

Switch a clock source

Enable the extended SSM protocol Set the affiliated clock subnet for the NE

Set the ID for clock

NOTE

l The horizontal direction of the figure shows the three stages when you use the U2000 to configure clocks. l The vertical direction of the figure shows the relations between operation tasks at each stage.

Issue 02 (2010-09-24)

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

3-3

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3.2 Clock Synchronization Scheme


This section describes the clock synchronization schemes. You need choose the clock synchronization scheme according to the actual networking architecture.

Clock Synchronization Scheme for a Chain/Tree Network


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

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

Figure 3-4 Clock synchronization scheme for a chain network


NE1 NE2 NE3 NE4

External 1/ Internal Master clock

5-IF1A-1/ 7-IF1A-1/ Internal

5-IF1A-1/ Internal

5-IF1A-1/ Internal

3-4

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

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

Figure 3-5 Clock synchronization scheme for a tree network


NE3

NE1

NE2 5-IF1A-1/ Internal

NE4 4-SL1-1/ Internal 5-IFX-1/ 7-IFX-1/ Internal

Master clock

5-IF1A-1/ Internal

Clock Synchronization Scheme for a Ring Network


The clock synchronization schemes for a ring network formed by the OptiX RTN equipment only or formed by the OptiX RTN equipment and other OptiX equipment are as follows: l When the entire ring network line is an SDH line, set the SSM or extended SSM according to the clock synchronization schemes of an optical transmission network.

Issue 02 (2010-09-24)

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

3-5

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

When a PDH section exists on the line of the ring network, divide the ring network into two chains and set the synchronization according to the clock synchronization schemes of a chain network.

Figure 3-6 shows the clock synchronization scheme of a ring network of which the entire ring network line is an SDH line. l l The SSM or extended SSM protection is enabled on all the nodes in the ring network. The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence, the clock source priority levels are external clock source 1 and internal clock source in the descending order. The clock source priority levels of other nodes are the west clock source, east clock source, and internal clock source in the descending order.

Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line)
NE2 NE1 West/ East/ Internal West/ East/ Internal NE6

External 1/ Internal

West/ East/ Internal NE3 Master clock NE4 West/ East/ Internal NE5

West/ East/ Internal

Figure 3-7 shows the clock synchronization scheme of a ring network of which not the entire ring network line is an SDH line. l l l l l This ring network is formed by PDH microwave. Hence, divide the ring network at the main node NE1 into two chains: from NE1 to NE2 and from NE3 to NE4. The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source level priority levels are 4-SL1-1 and internal clock source in the descending order. NE2 traces the clock of the main node. Hence, the clock source level priority levels are the west clock source and internal clock source in the descending order. NE4 traces the clock of the main node. Hence, the clock source level priority levels are the east clock source and internal clock source in the descending order. NE3 traces the clock of NE4. Hence, the clock source level priority levels are the east clock source and internal clock source in the descending order.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

3-6

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

Do not configure the SSM or extended SSM protection.

Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line)
NE1

NE2 4-SL1-1/ Internal

NE4

West/ Internal

NE3

East/ Internal

Master clock

East/ Internal

Clock Synchronization Scheme for Networking with Convergence at Tributary Ports


Networking with convergence at tributary ports indicates that several OptiX RTN 600 NEs are converged to the higher-level OptiX RTN NE through the E1/E3 cable. The clock synchronization schemes for networking with convergence at tributary ports are as follows: l l l The higher-level NE accesses the clock source (external clock source or line clock source). The lower-level NEs trace the tributary clock sources (port 1 and port 5 of the PO1/PH1/ PD1 board can be used as the tributary clock sources). When a lower-level NE is connected to multiple hops of radio links, abnormal pointer adjustments may occur if the lower-level NE traces the tributary clock. Therefore, the lower-level NEs should trace the external clock output by the higher-level NE. Do not configure the SSM or extended SSM protection.

Figure 3-8shows the clock synchronization scheme for networking with convergence at tributary ports. l The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence, the clock source priority levels are external clock source 1 and internal clock source in the descending order. The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the clock source level priority levels are 5-IF1A-1 and internal clock source in the descending order.

Issue 02 (2010-09-24)

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

3-7

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

NE3 converges services TO NE2 through ports 1-4 of the PO1 board in slot 4. Hence, the clock source level priority levels are 4-PO1-1 and internal clock source in the descending order. Multiple microwave hops exist in the downstream of NE4. In this case, the downstream nodes will report point adjustments if NE4 adopts the tributary clock source. Hence, NE4 adopts the external clock output from NE2 as the external clock input to the PXC board in slot 1. Do not configure the SSM or extended SSM protection.

Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports
NE3

NE1

NE2

4-PO1-1/ Internal NE4

External 1/ Internal

5-IF1A-1/ Internal

External/ Internal Master clock E1 External clock

Precautions for Making the Clock Synchronization Scheme


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

3.3 Basic Concepts


Before clock configuration, you need to master the basic concepts. 3.3.1 Clock Synchronization
3-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

By keeping the clock synchronization of each NE in the network, you can avoid pointer justification events, jitters, and bit errors thus caused when the clocks are not synchronous. All NEs trace the same PRC through a specific clock synchronization path, thus realizing the networkwide synchronization. 3.3.2 SSM Protocol and Clock ID The synchronization status message (SSM) protocol and clock ID are used for clock protection. 3.3.3 Clock Subnet The nodes that have clock tracing relations between each other comprise a clock subnet. 3.3.4 Clock Protection Clock protection ensures that each node traces the correct clock source even when a fault occurs in a network.

3.3.1 Clock Synchronization


By keeping the clock synchronization of each NE in the network, you can avoid pointer justification events, jitters, and bit errors thus caused when the clocks are not synchronous. All NEs trace the same PRC through a specific clock synchronization path, thus realizing the networkwide synchronization.

Working Modes and Timing Methods of the Clock


Currently, the communication network adopts the master-slave synchronization mode. That is, the master clock that is with high precision and stability transfers clock signals to slave clocks of each level through the clock network. Each slave clock is synchronous with the clock signal that is from the upper level. Thus, the networkwide synchronization is realized. In this mode, the slave clock usually has the following three working modes: l l Tracing mode: It is the normal working mode. In this mode, the local clock is synchronized with the input reference clock signals. Holdover mode: When all timing reference signals are lost, the slave clock enters into the holdover mode. In this mode, the slave clock takes timing reference from the last frequency information saved before the loss of timing reference signals. This mode can be used to cope with an interruption of external timing signals lasting many days. Free-run mode: When all timing reference signals are lost and the slave clock losses the saved configuration data about the timing reference or the slave clock fails to enter the holdover mode, the internal oscillator of the slave clock enters the free-run mode from the holdover mode.

The clock source has the following four timing methods: l l l l External clock source: 2M timing signals from the external clock interface of an NE Line clock source: timing signals extracted from optical signals that the line board receives Tributary clock source: timing signals extracted from optical signals that the tributary board receives Internal clock source: The internal timing source is available for each NE. When the external source is lost, the NE can use the internal timing source.

Clock Synchronization
Generally, an NE can obtain the PRC through several paths. In Figure 3-9, NE4 can trace the clock from NE3 and the clock from NE5. These two clock sources are from the same PRC.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-9

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 3-9 Clock synchronization


BITS

NE1

NE2

NE6

NE3

NE5

NE4 Clock Signal Flow

3.3.2 SSM Protocol and Clock ID


The synchronization status message (SSM) protocol and clock ID are used for clock protection.

S1 Byte
The S1 byte is located in row 9 and column 1 in the multiplex section overhead in an SDH frame structure. The lower four bits (bit 5-bit 8) of the S1 byte are allocated to transport a synchronization status of an NE, which is referred to as the synchronization status message byte (SSMB). Table 3-1 shows the meaning of clock quality that the SSMB stands for. The smaller the SSMB value, the higher the quality of the clock source that the SSMB represents. In a clock network, the node that is connected to an external clock extracts a reference timing source from the BITS equipment, writes an SSMB to bit 5-bit 8 of S1 byte, and transports the SSMB to downstream nodes. In this way, the SSMB is output. A downstream node extracts the timing source from a line signal, and obtains the clock quality level from bit 5-bit 8 of S1 byte. In this way, the downstream node often determines whether the current clock source is effective and transmits back 0xf to the upstream node through bit 5-bit 8 of S1 byte. 0xf means the returned
3-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

clock source is unavailable. This prevents two nodes from tracing the timing source mutually. Each node obtains the quality of all clock sources from the S1 byte, and choose to trace a clock source according to the preset priority level. Table 3-1 SSM allocation Bit 5-bit 8 of S1 byte 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 SDH Synchronization Quality Level The synchronization quality is unknown (the existing synchronous network). Retained G.811 clock signal Retained SSU-ANote 1 Retained Retained Retained SSU-BNote 1 Retained Retained Synchronous equipment timing source (SETS) signal Retained Retained Retained Not used for synchronization

Note 1: The "G.812 Transit Exchange" and "G.812 Local Clock" terms are used in the previous version of ITU-T Recommendations. In the new version of ITU-T G.812, the clock definition is changed to synchronization supply unit (SSU). The SSU has A and B types. The SSU-A corresponds to the "G.812 Transit Exchange" and the SSU-B corresponds to the "G.812 Local Clock" that are previously used.

SSM Protocol
The standard SSM protocol is mechanism of network synchronization management. It uses bit 5-bit 8 of S1 byte to exchange the quality information of clock sources between nodes. This ensures that the equipment automatically selects the clock source of the highest quality and priority levels, to prevent an interlock of clocks. The standard SSM protocol improves the performance of a synchronous network, and realizes synchronization of different network
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-11

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

structures in an easy manner. The standard SSM protocol applies to the interconnection of equipment from different vendors. In the case that the S1 byte is enabled for clock protection, the concept of clock ID is introduced. That is, clock protection is extended based on the original SSM protocol. In this manner, the extended SSM protocol is developed. In the case of the extended SSM protocol, Huawei introduces the concept of clock ID based on the standard SSM protocol. The extended SSM protocol uses b1 through b4 of S1 byte as the unique ID of a clock source and transports the clock ID with an SSM. After a node receives the S1 byte, the node verifies the clock ID (bit 1-bit 4) to determine whether the clock is locally output. If the clock is locally output, the node regards the clock as unavailable. This prevents a timing loop. The extended SSM protocol is mainly used to realize the interconnection of transmission equipment from Huawei. When an NE works in different clock protection modes, the method of selecting a clock source during automatic clock switching is changed accordingly, as shown in Table 3-2. Table 3-2 Methods of selecting clock sources in different modes Working Mode Non-SSM protocol mode Clock Source Selection The NE selects a clock source with the highest priority according to the clock source priority list. If the clock source with the highest priority is lost, the NE selects and trace the clock source with the second highest priority. The NE selects a clock source according to the priority and quality of the clock source. The clock source with highest quality is preferred. If the clock sources are of the same quality, the NE selects the clock with the highest priority. The NE selects a clock source according to the priority, quality, and clock source ID. Specifically, the NE selects and traces the clock source that is with the highest quality and priority but not transmitted from the NE itself.

Standard SSM protocol mode

Extended SSM protocol mode

Clock ID
A clock ID use bit 1-bit 4 of S1 byte, and the value range is 0x0 to 0xf. Basically, a clock ID is used to distinguish the clock information between local and other nodes, to prevent a node from tracing the clock signal that is locally transmitted and comes from the negative direction. Hence, a timing loop is prevented. A value of 0 indicates that a clock ID is invalid. Hence, the default value of a clock ID is 0 when an ID is not set for a clock source. When enabling the extended SSM protocol, an NE does not select the clock source whose ID is 0 as the current clock source.
3-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

A clock ID is a tag set for a reference timing source. The clock sources at the same quality level that carry different IDs mean different timing signals and are not different in priority levels and other aspects. Set the clock ID according to the following principles: l l l l Allocate a clock ID to each external BITS. Allocate a clock ID to the internal clock source of each node that has an external BITS. Allocate a clock ID to the internal clock source of each node that enters into another ring network from one chain or ring network. Allocate a clock ID to the line clock source of the node that enters into another ring network from one chain or ring network, when the line clock source exists.

3.3.3 Clock Subnet


The nodes that have clock tracing relations between each other comprise a clock subnet. During the configuration of a clock subnet, pay attention to the following points: l l l All the NEs that trace the same clock source should be divided to the same clock subnet. To make sure that the clock tracing chain is not too long, configure at most 20 NEs to prevent the clock precision from being degraded. You must divide the NEs that have the SSM clock protection to clock subnets. Otherwise, SSM is not enabled for the NEs that are not divided to the clock subnets. This results in incorrect traced clock switching.

3.3.4 Clock Protection


Clock protection ensures that each node traces the correct clock source even when a fault occurs in a network. Clock protection refers to the process during which a timing source selects a new route so that the entire network continues to trace the PRC, when services are switched and select a standby route to realize protection because an optical path is interrupted or a node fails. In other words, clock protection is a process during which, when one PRC fails in the network, a new route is selected to trace another PRC networkwide. In Figure 3-9, NE4 traces the clock that is from NE3. If this clock is lost, NE4 can automatically switches to trace the clock that is from NE5. When automatic protection switching occurs in a clock, the new clock source may trace the same PRC as the original clock source or another PRC with worse quality, such as another standby BITS. The clock protection switching is performed based on the following principles: l If the clock source priority is set, the NE selects the clock source of the highest quality level as the synchronization source and sends the synchronization status message bit (SSMB) to downstream NEs. If multiple clock sources of the same quality level exist, the NE selects the clock source of the highest priority level as the synchronization source and sends the SSMB to downstream NEs. If NE B traces the clock source that is output from NE A, the clock of NE B is an unavailable source for NE A. If the extended SSM protocol is enabled, the NE does not select the clock that has the same ID as the local clock, or the clock whose ID is 0, as the clock source.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-13

l l

Issue 02 (2010-09-24)

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3.4 Viewing Clock Synchronization Status


If the clocks between NEs in the network are not synchronous, the pointer justification, bit error, even service interruption may occur on NE. Using the U2000, you can learn and monitor the synchronization status of the NE clocks.

Prerequisite
You must be an NM user with "NE monitor" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Synchronization Status from the Function Tree.
NOTE

To view the clock synchronization status of NEs in batches, Choose Configuration > NE Batch Configuration > Batch Clock Operation from the main menu. Then, click the Clock Synchronization Status tab. In the Object Tree, select the desired NEs and click .

Step 2 Click Query. You can view the information about the clock synchronization status queried from the NE side.

----End

3.5 Viewing the Clock Tracing Status


Correct clock tracing relationships are critical to ensure the clock synchronization within the entire network. Using the U2000, you can monitor the clock trace status of each NE.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the Clock View automatically.

Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list. Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click and choose Search Clock Link from the shortcut menu. Step 3 In the Operation Result dialog box, click Close. ----End
3-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

3.6 Configuring the Clock Sources


This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The PXC boards and input/output clock source boards must be configured.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Priority from the Function Tree. Step 2 Click Create. The Add Clock Source dialog box is displayed. Step 3 Select the clock sources.

TIP

By pressing the Ctrl key, you can select multiple clock sources at one time.

Step 4 Click OK. Step 5 Optional: Repeat Step 2 to Step 4 to add other clock sources. Step 6 Optional: Select a clock source and click this clock source. or to adjust the priority level of

The clock priority levels are arranged in the descending order from the first row to the last row. The internal clock source is fixed with the lowest priority. Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-15

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 8 Click Apply. ----End

Parameters
Parameter Clock Source Value Range Default Value Description l External clock source 1 indicates the external clock source at the port of the PXC board in slot 1. External clock source 2 indicates the external clock source at the port of the PXC board in slot 3. l IFH2-1(SDH) indicates the microwave clock source. l IFH2-2(ETH) indicates the clock source of the synchronous Ethernet. l The internal clock source is fixed with 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 schemes. External Clock Source Mode 2 Mbit/s, 2 MHz 2 Mbit/s l This parameter indicates the type of the external clock source signal. l Set this parameter depending on the external clock signal. Generally, the external clock signal is a 2 Mbit/s signal. Synchronization Status Byte SA4-SA8 SA4 l This parameter is valid only when External Clock Source Mode is set to 2 Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. l This parameter need to be set only when the SSM or extended SSM is enabled. Generally, the external clock sources use the SA4 to pass the SSM.

3-16

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

3.7 Configuring Protection for Clock Sources


This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring networks, protection for the clock sources need to be implemented through the standard SSM protocol or extended SSM protocol.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The clock source priority table must be configured.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Subnet Configuration from the Function Tree. Step 2 Enable the clock protection protocol. 1. 2. Click the Clock Subnet tab. Enable the clock protection protocol and set the protocol parameters.

3.

Click Apply.

Step 3 Set the SSM output port. 1. 2. Click the SSM Output Control tab. Set the SSM output port.

Issue 02 (2010-09-24)

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

3-17

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3. 1. 2.

Click Apply. Click the Clock ID Status tab. Set the clock ID output port.

Step 4 Optional: Set the clock ID output port.

3.

Click Apply.

----End

Parameters
Parameter Protection Status Value Range Start Extended SSM Protocol, Start Standard SSM Protocol, Stop SSM Protocol Default Value Stop SSM Protocol Description l The SSM protocol is a scheme used for synchronous management in an SDH network and indicates that the SSM is passed by the lower four bits of the S1 byte and can be exchanged between the nodes. The SSM protocol ensures that the equipment automatically select the clock source with the highest quality and highest priority, thus preventing clock mutual tracing. l The extended SSM protocol is the extension of the standard SSM protocol. It defines the unique ID for each clock source and uses the higher four bits of the S1 byte to pass the ID. The extended SSM protocol can be used to prevent the NEs from tracing their own clocks. l If third-party equipment exists in the ring network, enable the SSM protocol. If only OptiX equipment exists in the ring network and clock mutual tracing can be prevented through certain configurations of the clock sources, the SSM protocol can also be enabled. l If only OptiX equipment exists in the ring network, it is recommended that the extended SSM protocol is used.

3-18

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

Parameter Affiliated Subnet

Value Range 0-255

Default Value 0

Description l This parameter is used when the clock subnet need to be created on the NMS. l The NEs that trace the same clock source should be allocated with the same clock subnet ID.

Clock Source ID

(None), 0-15

(None)

l This parameter is valid only when the SSM protocol is enabled. l Allocate the clock source ID for the following clock sources only: External clock sources Internal clock source of the node that accesses the external clock sources Internal clock source of the joint node of a ring and a chain or the joint node of two rings Line clock source that enters the ring when the intra-ring line clock source is configured at the joint node of a ring and a chain or the joint node of two rings

Control Status

Enabled, Disabled

Enabled

l This parameter is valid only when the SSM protocol or the extended SSM protocol is enabled. l This parameter indicates whether the SSM is output at the line port. l When the line port is connected to an NE in the same clock subnet, set this parameter to Enabled; otherwise, set this parameter to Disabled.

Enable Status

Enabled, Disabled.

Enabled

l This parameter is valid only when the SSM protocol is enabled. l This parameter indicates whether the clock source ID is output at the line port. l When the line port is connected to an NE in the same clock subnet and the extended SSM protocol is enabled at the remote NE, set this parameter to Enabled; otherwise, set this parameter to Disabled.

Issue 02 (2010-09-24)

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

3-19

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3.8 Configuring Switching Conditions for Clock Sources


If the traceable clock source of an NE is line clock, you can customize switching conditions for the clock source, so that the NE switches to other clocks when the clock source fails. In this manner, services are less affected.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching Condition tab. Step 2 Click Query to query the existing parameter settings. Step 3 Double-click the parameter column and set the alarms and performance events that are to be used as the clock source switching conditions to Yes.

Step 4 Click Apply. In the Operation Result dialog box, click Close. ----End

3.9 Configuring the Clock Source Reversion


When there are multiple clock sources for an NE, set the clock sources to automatic reversion mode, so that the deteriorated clock source automatically becomes the traceable timing reference after it recovers.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source Switching from the Function Tree. Click the Clock Source Reversion Parameter tab.
NOTE

To set the clock source reversion for multiple NEs in batches, Choose Configuration > NE Batch Configuration > Batch Clock Operation from the main menu. . Click the Clock Source Reversion Parameter tab. In the Object Tree, select the desired NEs and click .

Step 2 Double-click and set the reversion mode and the WTR time.

3-20

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

3 Configuring Clocks

Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.

Step 3 Click Apply. In the Operation Result dialog box, click Close. ----End

3.10 Modifying the Parameters of the External Clock Output


The NE outputs the 2 Mbit/s external clock regardless of the clock quality.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The PXC board must be configured.

Precautions
In the OptiX RTN 600, external clock source 1 indicates the external clock on the PXC board in slot 1 and external clock source 2 indicates the external clock on the PXC board in slot 3.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Phase-Locked Source Output by External Clock from the Function Tree. Step 2 Modify the clock output parameters.

Step 3 Click Apply. ----End

Parameters
Parameter External Clock Output Mode Value Range 2 Mbit/s, 2 MHz Default Value 2 Mbit/s Description l This parameter indicates the mode of the output clock. l Set this parameter according to the requirements of the interconnected equipment. Generally, the output clock signal is a 2 Mbit/s signal.

Issue 02 (2010-09-24)

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

3-21

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter External Clock Output Timeslot

Value Range SA4-SA8, ALL

Default Value ALL

Description l This parameter is valid only when External Clock Output Mode is set to 2 Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. l When this parameter is set to ALL, it indicates that each bit can transmit the SSM. l It is recommended that this parameter takes the default value.

External Clock Output Threshold

Threshold Disabled, Not Inferior to G. 813 SETS Signal, Not Inferior to G. 812 Local Clock Signal, Not Inferior to G.812 Transit Clock Signal, Not Inferior to G.811 Clock Signal No Failure Condition, AIS, LOF, AIS OR LOF

Threshold Disabled

l This parameter indicates the lowest clock quality of the output clock. When the clock quality is lower than the parameter value, the signal is not output. l When this parameter is set to Threshold Disabled, it indicates that the clock signal is continuously output. l It is recommended that this parameter takes the default value.

2M Phase-Locked Source Fail Condition

No Failure Condition

l This parameter indicates the conditions when the 2M phase-locked clock source fails. l It is recommended that you use the default value.

2M Phase-Locked Source Fail Action

Shut Down Output, 2M Output S1 Byte Unavailable, Send AIS

Shut Down Output

l This parameter is valid only when 2M Phase-Locked Source Fail Condition is No Failure Condition. l This parameter indicates the action of the 2M phase-locked loop when 2M PhaseLocked Source Fail Condition is met. l It is recommended that you use the default value.

3.11 Setting the Clock Source Quality


In a complex clock network, there may be some unknown clock sources. You can uniformly define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources. The NE obtains their quality information automatically for clock sources that are allocated to an NE. You should define the quality level of clock sources only during test and maintenance.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
3-22 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet Configuration from the Function Tree. Click the Clock Quality tab. Step 2 Click Query to query the existing parameter settings. Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.

NOTE

Generally, use the default Automatic Extraction.

Step 4 Click Apply. In the Operation Result dialog box, click Close. Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level.
NOTE

To set the clock source quality for multiple NEs in batches, Choose Configuration > NE Batch Configuration > Batch Clock Operation from the main menu. Click the Manual Setting of 0 Quality Level tab. In the Object Tree, select the desired NEs and click .

Step 6 Click Apply. In the Operation Result dialog box, click Close. ----End

3.12 Configuring the SSM Output


If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages automatically. You can prevent clock sources from sending SSM messages to other clock subnets. This helps you to ensure that the equipment of different clock subnets do not affect each other at the edge of clock networks.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet Configuration from the Function Tree. Click the SSM Output Control tab. Step 2 Set the Control Status of the clock source.

Issue 02 (2010-09-24)

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

3-23

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 3 Click Apply. In the Operation Result dialog box, click Close. ----End

3.13 Configuring the Ethernet Clock Source


Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock synchronization strategy to ensure that all the NEs in the network trace the same clock.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. 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

Parameters
Parameter Use the clock source of the data port Value Range Yes, No Default Value No Description When this parameter is set to Yes, the IDU 605 1F/2F traces the clock source that is recovered from the signal flow on the Ethernet PORT.

3.14 Viewing the Clock Tracing Status


Correct clock tracing relationships are critical to ensure the clock synchronization within the entire network. Using the U2000, you can monitor the clock trace status of each NE.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
3-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3 Configuring Clocks

Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the Clock View automatically.

Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list. Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click and choose Search Clock Link from the shortcut menu. Step 3 In the Operation Result dialog box, click Close. ----End

3.15 Checking the Clock Switching Status


Clock failure may interrupt services. To detect failure of the clock source in time, you need to check the clock switching status.

Prerequisite
l l You must be an NM user with "NE monitor" authority or higher. The reference clock source must be set.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source Switching from the Function Tree. Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status of the current clock source.

Step 3 In the Operation Result dialog box, click Close. ----End

3.16 Switching a Clock Source


When the traceable clock source in a network deteriorates, NEs may not be able to execute a switch on the clock source. You need to manually switch the clock source to prevent clock deterioration from affecting the normal running of NEs.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-25

3 Configuring Clocks

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The clock source has been created.

Context

CAUTION
Performing clock source switching may cause signal jitter and bit errors.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching tab. Step 2 Click Query to query the current switching status of a clock source. Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout. Step 4 Right-click the clock source that you want to switch and choose a switching operation.
NOTE

Before switching the clock source, make sure that the new clock source that is not locked and that is of a good quality is created in the priority table.

Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock source and choose Clear Switching. ----End

3-26

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

4
About This Chapter

Configuring PTP Clock

The equipment complies with the IEEE 1588V2 protocol and can achieve frequency synchronization and time synchronization. 4.1 Introduction to the PTP Clock The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution (LTE). 4.2 Basic Information Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm, clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their functions. 4.3 Application of the PTP Clock By using the IEEE 1588V2 protocol, the OptiX RTN equipment can transfer the precise time information to achieve clock synchronization and time synchronization for equipment in the network. This meets the requirement of the telecommunications network for precise time. The equipment with the PTP clock can achieve networkwide frequency synchronization and time synchronization in the packet switching network (PSN). The telecommunications network carry various services. Certain services require precise time synchronization, such as the network voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and ensures precise time synchronization. 4.4 Configuration Flow for the PTP Clock This section describes the flow of configuring the PTP clock in different modes. 4.5 Configuring the PTP Clock To achieve time synchronization and clock synchronization between NEs, configure the PTP clock.

Issue 02 (2010-09-24)

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

4-1

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4.1 Introduction to the PTP Clock


The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution (LTE).

Objective and Benefit


As the rate at which the Ethernet data is transmitted is increased to the gigabit-per-second level, the synchronization of the Ethernet fails to meet the requirements. To solve the synchronization problem, the network time protocol (NTP) is presented, which helps achieve the precision of clock synchronization at 200 us. The precision, however, fails to meet the precision requirements of the test instruments and industrial control. To improve the synchronization precision, in 2002, the IEEE committee presented the IEEE 1588 clock protocol. Then, the protocol evolved to the current IEEE 1588V2 protocol, which helps achieve nanosecond-level precision. There are two synchronization modes, that is, clock (frequency) synchronization and time (phase) synchronization. Time (phase) synchronization is applicable to the networks where the absolute networkwide time should be of certain precision, such as the power system network and 3G network. Though the GPS at every node can also solve the precision problem, the high cost limits the application scope of this solution. The traditional clock protocols can achieve only frequency synchronization. The IEEE 1588V2 protocol is the clock protocol that can achieve both frequency synchronization and phase synchronization. The IEEE 1588V2 protocol is applicable for time synchronization at every node in the distributed network that requires precise synchronization. The hardware and software synchronize the system clock of the network equipment (client) with the primary clock in the network at a nanosecond precision level. In the Ethernet where the IEEE 1588V2 protocol is not enabled, there is a 1000 us delay. In the Ethernet where the IEEE 1588V2 protocol is enabled, the timing synchronization is improved to a great extent. The approach of adopting the IEEE 1588V2 protocol to achieve clock synchronization and time synchronization marks a technical innovation for the transformation of the carrier-class IP network. The IEEE 1588V2 protocol helps achieve clock synchronization and time synchronization that meet the requirements of Node B and RNC in a 3G network.
NOTE

l Clock synchronization refers to frequency synchronization. l Time synchronization refers to phase synchronization, which requires that both the time and frequency should be synchronous.

Standards and Protocols Compliance


The IEEE 1588V2 clock complies with 1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE, 2002.

4-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

4.2 Basic Information


Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm, clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their functions.

BMC Algorithm
In a PTP clock network, the equipment computes the best clock source according to the BMC algorithm. The BMC algorithm compares the descriptive data of two clocks and detects the better one, which is selected as the clock source. The BMC algorithm includes the following algorithms: l Data set comparison algorithm: The NE selects the clock of better quality as the clock source. If an NE receives two or more channels of clock signals from the same grandmaster clock (GMC), the NE selects one channel of the clock signals that traverses the least nodes as the clock source. State decision algorithm: The result of data set comparison determines the next state of the port.

Clock Architecture
Figure 4-1 shows the architecture of the IEEE 1588V2 clock.

Issue 02 (2010-09-24)

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

4-3

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 4-1 Architecture of the IEEE 1588V2 clock

BITS

OC

GMC Master

TC

BC

Slave Master Master

BC Slave Master

TC+OC

OC

Slave

OC

Slave

NOTE

l Master: A master port provides a time source for the downstream equipment. l Slave: A slave port receives the clock signals from the upstream port.

The OptiX RTN equipment supports four architectures of the IEEE 1588V2 clock. l Ordinary clock (OC): The OC equipment provides only one port to extract the IEEE 1588 packets. The OC equipment can work as a slave clock equipment and maintains synchronization with the upstream clock. The equipment extracts the clock packets from the port that supports the IEEE 1588 packets and recovers the clock. The equipment can also work as a master clock equipment, which inputs the external time from the external time interface, and outputs the clock signals to the downstream through the port that supports the IEEE 1588 packets. Boundary clock (BC): When used as a BC, the equipment provides multiple ports to extract the IEEE 1588 packets. The BC can work as either master clock equipment or slave clock equipment. The BC equipment can distribute the clock packets to the downstream through multiple ports, but the OC equipment can distribute the clock packets to the downstream through only one port. Transparent clock (TC): The TC equipment transparently transmits the IEEE 1588 packets and records the period when the packets stay on the equipment. During the period, the TC
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

4-4

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

equipment transports the packets to the slave clock equipment for processing. The TC equipment only transparently transmits the clock, and does not recover the clock. End-to-end TC: The TC equipment adopts the end-to-end delay measurement mechanism between the master and slave clocks. Peer-to-peer TC: The TC adopts the point-to-point delay measurement mechanism. l TC+OC: The TC+OC equipment corrects and transparently transmits the time stamps for the IEEE 1588V2 packets, and achieves clock synchronization. By adopting the BMC algorithm, the TC+OC equipment selects the clock source, which is then sent to the system clock module. If necessary, the clock source can be used as the system clock of the equipment.
NOTE

The end-to-end TC and peer-to-peer TC adopt different mechanisms to realize delay transmission, and cannot operate in the same communication channel alternatively. That is, the adjacent TC equipment along one time channel adopts either the end-to-end TC or peer-to-peer TC, but not both at the same time.

Master-Slave Synchronization
In the case of master-slave synchronization, each slave clock maintains synchronization with the master clock by exchanging the synchronization packets with the master clock. Figure 4-2 shows the master-slave synchronization process of the equipment. Figure 4-2 Master-slave synchronization process

Master clock

Time stamp at slave clock Slave clock

t1

Sync packets t2 t1t2

Delay_Req packets t3 t4 t1t2t3

Delay_Resp packets

t1t2t3t4

l l l
Issue 02 (2010-09-24)

At time point t1, the master clock sends the Sync packets that contain time stamp t1 to the slave clock. At time point t2, the slave clock receives the Sync packets and obtains time stamp t1. At time point t3, the slave clock sends the Delay_Req packets to the master clock.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-5

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

At time point t4, the master clock receives the Delay_Req packets. Then, the master clock sends the Delay_Resp packets that contain time stamp t4 to the slave clock.
NOTE

A time stamp (TS) is used to transmit the time information. The Sync packets, Delay_Req packets, and Delay_Resp packets are used to generate or communicate the time information. The OC equipment and BC equipment maintain synchronization by processing related time information.

The slave clock computes the delay and offset from the master clock according to time stamps t1, t2, t3, and t4. Then, the slave clock corrects the time according to the delay and offset. l l Delay = [(t4-t1)-(t3-t2)]/2 Offset = [(t2-t1)+(t3-t4)]/2

Protocol Packets and Their Functions


The IEEE 1588 protocol defines the Event messages and General messages. The Event messages are timing messages. To transmit and receive the Event messages, the equipment should generate the precise time stamp. To transmit and receive the General messages, the equipment does not need to generate the precise time stamp. The Event messages include the following packets: l l l l Sync Delay_Req Pdelay_Req Pdelay_Resp

The General messages include the following packets: l l l l Announce Delay_Resp Management Signaling

The Sync, Delay_Req, and Delay_Resp packets are used to generate or transport the timing information. The OC and BC maintains synchronization by using the timing information and adopting the delay request-response mechanism. The Pdelay_Req and Pdelay_Resp packets are used to measure the link delay between two clock ports that support the Pdelay mechanism. The link delay is used to correct the timing information contained in the Sync packets in the P2P TC system. The OC and BC maintain synchronization according to the link delay and the timing information contained in the Sync messages.
NOTE

The Pdelay mechanism is intended to measure the point-to-point transmission time between two communication ports that support the Pdelay mechanism. The point-to-point transmission time is the link delay. The P2P TC has to compute the link delay by adopting the Pdelay mechanism.

The Announce messages are used to set up the synchronization system.

4.3 Application of the PTP Clock


By using the IEEE 1588V2 protocol, the OptiX RTN equipment can transfer the precise time information to achieve clock synchronization and time synchronization for equipment in the
4-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

network. This meets the requirement of the telecommunications network for precise time. The equipment with the PTP clock can achieve networkwide frequency synchronization and time synchronization in the packet switching network (PSN). The telecommunications network carry various services. Certain services require precise time synchronization, such as the network voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and ensures precise time synchronization. Figure 4-3 shows the scenario where the PTP clock is applicable. Figure 4-3 Networking diagram for typical application of the PTP clock
Node B

NE E GPS NE B NE A OC RTN 910

BC NE C

RNC

BC NE D BC NE F OC RTN 910 RTN 950 External time signals Node B PTP time signals RTN 910

BC

As shown in Figure 4-3, BITS sends clock signals to NE A and RNC. NE A works as BC equipment and sends the PTP packets to two ports. NE E and NE F, which are connected to Node B, work as the OC equipment, recover the PTP clock, and send the clock to Node B through the external time interface.

4.4 Configuration Flow for the PTP Clock


This section describes the flow of configuring the PTP clock in different modes. Figure 4-4 shows the flow for configuring the PTP clock.

Issue 02 (2010-09-24)

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

4-7

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 4-4 Configuration flow for the PTP clock

Required Optional

Start Setting the Frequency Selection Mode Setting the PTP System Time Setting the PTP Clock Subnet

Setting the Attributes of the External Time Interface Setting the PTP NE Attributes

Creating the PTP Clock Port Creating the PTP Clock Service

Setting the PTP Packet Period

Setting the PTP Clock Port Status Setting the Cable Transmitting Wrap Setting the WTR Time for the PTP Clock Sourc Setting the PTP Clock Source Priority End
4-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

The PTP priority service needs to be configured only when the PTP clock works in the TC or TC+OC mode. The PTP clock source priority needs to be configured only when the PTP clock works in the TC +OC mode.

4.5 Configuring the PTP Clock


To achieve time synchronization and clock synchronization between NEs, configure the PTP clock. 4.5.1 Setting the Frequency Selection Mode The OptiX RTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode. 4.5.2 Setting the PTP System Time If the OptiX RTN equipment is used as the grandmaster clock in the PTP clock network, you should set the PTP system time on the OptiX RTN equipment. Hence, the downstream OptiX RTN equipment can trace the clock. 4.5.3 Setting the PTP Clock Subnet According to the actual networking, the networking planner plans the clock network and divides the entire network into clock domains. In each clock domain, the clock and time of the equipment are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock domain. The equipment selects the source in only one clock domain, and discards the clock packets from other clock domains. 4.5.4 Setting the Attributes of the External Time Interface If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment. 4.5.5 Setting the PTP NE Attributes The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time Adjusting. 4.5.6 Creating the PTP Clock Port When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set the clock reference source number on the PTP clock port created in the BC or OC mode. 4.5.7 Creating the PTP Clock Service When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the NE so that the NE transparently transmits the PTP clock packets. 4.5.8 Setting the PTP Packet Period When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC, DELAY, and PDELAY packets. 4.5.9 Setting the PTP Clock Port Status In the scenario where the OptiX RTN equipment is connected to the client equipment, properly set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-9

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for the PTP packets. 4.5.10 Setting the Cable Transmitting Wrap The cable transmitting distance wrap indicates the transmitting time difference of the cables between two sets of equipment in the transmit and receive directions. During deployment, you can use the GPS to compute the transmitting time difference between the two directions. Set the cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap modes includes the length wrap and time wrap. The equipment can choose only one mode. 4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source When a clock port recovers from a failure, the system acknowledges the validity of the port a certain period later. This period is referred to as the wait-to-restore (WTR) time. During the WTR time, the system considers the clock signals as unavailable and the clock signals are not involved in the clock source selection. 4.5.12 Setting the PTP Clock Source Priority If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP clock source of the highest priority fails, the OC traces the PTP clock source of the second highest priority. The priority table is configured with a source ID. When a local port receives a clock source in the priority table, the port checks whether the domain that the clock source belongs to is consistent with the domain configured at the local end.

4.5.1 Setting the Frequency Selection Mode


The OptiX RTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the Function Tree. Step 2 In Frequency Selection Mode, you can select one of the clock synchronization mode.

CAUTION
l When the external time interface is set to the external time input interface, the NE can run in only the physical synchronization mode. That is, the frequency selection mode of the equipment that accesses the external clock must be set to the physical synchronization mode. l When the NE is running in the PTP synchronization mode, the external interface cannot be set to the external time input interface.

4-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

Step 3 Click Apply. ----End

4.5.2 Setting the PTP System Time


If the OptiX RTN equipment is used as the grandmaster clock in the PTP clock network, you should set the PTP system time on the OptiX RTN equipment. Hence, the downstream OptiX RTN equipment can trace the clock.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The PTP system time can be set only when the current time of the NE traces the local clock.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute. Step 2 In PTP System Time, click to set the system time.

NOTE

Move the cursor to the time bar. To increase the value, click or right-click the time bar. To decrease the value, hold the Shift key, and click or right-click the time bar.

Step 3 Click Apply. ----End

4.5.3 Setting the PTP Clock Subnet


According to the actual networking, the networking planner plans the clock network and divides the entire network into clock domains. In each clock domain, the clock and time of the equipment are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock domain. The equipment selects the source in only one clock domain, and discards the clock packets from other clock domains.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-11

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Prerequisite
You must be an NM user with "NE operator" authority or higher. The working mode of the equipment clock should not be TC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function Tree. Step 2 Select the Clock Subnet tab to set the clock subnet number. Step 3 Click Apply. Step 4 Click the BMC tab to set the parameters related to the BMC in the clock subnet. Step 5 Click Apply. ----End

4.5.4 Setting the Attributes of the External Time Interface


If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface. Step 2 Click the Basic Attribute tab. Step 3 Set Interface Mode of the external time interface. Step 4 Optional: If Interface Mode is set to External Time Interface, you can set Direction, Interface Protocol Type, and Interface Eletricity.
NOTE

l OptiX RTN 910 and 950: Interface Protocol Type is set according to the type of the external time protocol. Interface Protocol Type can be set to DCLS or 1PPS+TIME. l OptiX RTN 910 and 950: Interface Level is set according to the setting of the external time interface. Interface Level can be set to RS422.

Step 5 Click the BMC tab to set the BMC-related parameters.


NOTE

The BMC-related parameters can be set only the working mode is set to BC or OC, and when the Interface Mode of the External Time Interface is set to External Time Interface.

Step 6 Click Apply.


4-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

Step 7 Click the Cable Transmitting Distance tab to set the cable parameters for the clock compensation such as Transmitting Distance Mode, Transmitting Length(m), and Transmitting Time(ns).
NOTE

Transmitting Distance Mode can be set to Time or Length. l When Transmitting Distance Mode is set to Time, the transmitting time ranges from 0 ns to 1350 ns. l When Transmitting Distance Mode is set to Length, the length range is 0-300 m. l 1 m is equivalent to 4.5 ns.

Step 8 Click Apply. ----End

4.5.5 Setting the PTP NE Attributes


The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time Adjusting.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Set Work Mode, SLAVE_ONLY, Time Adjusting, and Transmitting Packet Multi-cast Mode. Step 3 According to the working mode of the NE in the network, set Work Mode.
NOTE

The PTP standard defines four working modes, that is, BC, OC, TC, and TC+OC. When the NE working mode is TC or TC+OC, if the PTP clock service or the clock source priority table is already configured, you cannot modify the working mode.

Step 4 When Work Mode is set to OC, SLAVE_ONLY can be set to SLAVE_ONLY or NON_SLAVE_ONLY.
NOTE

l SLAVE_ONLY indicates that the NE in the OC mode can only trace other PTP clocks. l NON_SLAVE_ONLY indicates that in the OC mode the NE can function as the standy clock to trace other PTP clocks and the NE can also function as the primary clock. Whether the NE functions as the standby clock or primary clock depends on the quality of the PTP clock.

Step 5 When Work Mode is set to BC or OC, Time Adjusting is configurable.


NOTE

If the NE requires time synchronized, Time Adjusting needs to be set to Enabled.

Step 6 When Work Mode is set to BC or OC, Transmitting Packet Multi-cast Mode is configurable.
NOTE

If the mode is set to Entire Multi-cast, the equipment multicasts all the PTP packets. If the mode is set to Part Multi-cast, the equipment unicasts the DELAY packets.

Issue 02 (2010-09-24)

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

4-13

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 7 When Work Mode is set to BC or OC, Protocol Packet Format is configurable.
NOTE

The Protocol Packet Format can be set to NMEA or UBX. The default parameter value is NMEA. This parameter is valid only when Interface Protocol Type of the external time interface is set to 1PPS +Time. When Interface Protocol Type of the external time interface is set to DCLS, the parameter can still be set but the parameter value is invalid.

----End

4.5.6 Creating the PTP Clock Port


When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set the clock reference source number on the PTP clock port created in the BC or OC mode.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog box. Step 3 Select the corresponding board, and then select the corresponding port from Available Port. Click Step 4 Click OK. ----End .

4.5.7 Creating the PTP Clock Service


When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the NE so that the NE transparently transmits the PTP clock packets.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Service from the Function Tree. Step 2 Click New to display the New Clock Service dialog box. Step 3 Set Service ID and Service Name. Step 4 In the dialog box, click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
4-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

Step 5 Select the port from the Available Port list, and then click Selected Port list.
NOTE

to add the port to the

l When the PTP packets contain VLAN tags, you need to set a VLAN tag for the port. The OptiX RTN equipment supports the setting of only one VLAN tag. l When two TC services share a port, set a VALN tag for the port if the port is a UNI port. l If the port is Layer 3 port, the port can be used only as a UNI port for the TC service. The encapsulation mode should be ETH and no VLAN tag can be set.

Step 6 Click OK, and thus the UNI configuration is complete. Step 7 Optional: If the PTP packets need to be carried by the MPLS tunnel, you can set the related NNI parameters. 1. 2. In the dialog box, click the NNI tab. Then, click New to display the New PW dialog box. Click the General Attributes tab to set PW ID, PW Type, PW Ingress Label, and PW Egress Label.

3.

Click to display Resource Selection Window. Select the tunnel that carries the PW, and then click OK.
NOTE

Select the static MPLS tunnel, because the dynamic MPLS tunnel cannot carry the PTP packets.

4.

Optional: Click the Advanced Attributes tab to set the corresponding parameters.

Issue 02 (2010-09-24)

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

4-15

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5.

Click OK in the New PW dialog box to finish the PW configuration on the NNI side.

Step 8 Click OK in the New Clock Service dialog box to complete the configuration of the clock service. ----End

4.5.8 Setting the PTP Packet Period


When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC, DELAY, and PDELAY packets.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Message tab to set P/E Mode and the corresponding packet periods.
NOTE

In P2P mode, the TC equipment transmits only the PDELAY packets. You can set the period for the TC equipment to transmit the PDELAY packets.

Step 3 Click Apply. ----End


4-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

4.5.9 Setting the PTP Clock Port Status


In the scenario where the OptiX RTN equipment is connected to the client equipment, properly set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for the PTP packets.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created. The working mode of the NE must be set to BC or OC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Status tab and set PTP Message Format.
NOTE

If the port is configured with a clock service, do not change the PTP message format of the port.

Step 3 Optional: If the working mode of the NE is set to BC or OC, and the PTP packets contain VLAN IDs, set PTP Message VLAN to a proper VLAN value accordingly.
NOTE

In the case of interconnection with the client equipment, if the client equipment forwards the PTP packets according to VLAN IDs, the PTP packets should contain VLAN IDs.

Step 4 Optional: If the working mode of the NE is set to BC or OC, set Port Status accordingly.
NOTE

l Set Port Status to MASTER+SLAVE, MASTER, or SLAVE. l When the Port Status is MASTER, Actual Port Status should not be SLAVE. l When the Port Status is SLAVE, Actual Port Status should not be MASTER. l If the NE is set to SLAVE_ONLY in the synchronization attributes, set Port Status only to SLAVE.

Step 5 Optional: If the working mode of the NE is set to BC or OC, double-click the blank line below Selected Clock Source to display the Clock Source Coding Configuration dialog box. Step 6 Optional: Set the parameters related to the clock source and click OK.

Issue 02 (2010-09-24)

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

4-17

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

CAUTION
The clock sources at the local port should be numbered in the same manner as the clock sources at the upstream port, or the clock sources do not need to be numbered. Otherwise, clock tracing fails if the working mode of the NE is set to BC or OC.
NOTE

When one PTP clock port receives multiple channels of clock signals, number the clock sources so that the NE selects one clock source. For example, multiple TC clock services from the upstream equipment are converged onto one clock port on the local equipment and then are transmitted to the downstream equipment. As a result, the port on the downstream equipment connected to the upstream equipment receives the multiple TC clock services. In this case, you need to number the clock sources at the port on the downstream equipment.

Step 7 Click Apply. ----End

4.5.10 Setting the Cable Transmitting Wrap


The cable transmitting distance wrap indicates the transmitting time difference of the cables between two sets of equipment in the transmit and receive directions. During deployment, you can use the GPS to compute the transmitting time difference between the two directions. Set the cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap modes includes the length wrap and time wrap. The equipment can choose only one mode.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute. Step 2 Click the Cable Transmitting Wrap tab. Step 3 Set Wrap Direction. Positive direction indicates that the transmitting distance or transmitting time of the clock receive end is longer than the transmitting distance or transmitting time at the clock transmit end. Negative direction indicates that the transmitting distance or transmitting time of the clock transmit end is longer than the transmitting distance or transmitting time at the clock receive end. Step 4 Wrap Mode can be set to Length or Time. Step 5 According to Wrap Mode, set Wrap Length(m) or Wrap Time(ns).
NOTE

l The range of Wrap Length(m) is 0-14562 m. l The range of Wrap Time(ns) is 0-65529 ns. l 1 m is equivalent to 4.5 ns.

Step 6 Click Apply. ----End


4-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

4 Configuring PTP Clock

4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a certain period later. This period is referred to as the wait-to-restore (WTR) time. During the WTR time, the system considers the clock signals as unavailable and the clock signals are not involved in the clock source selection.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created. The working mode of the NE must be set to BC, OC or TC+OC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority Table from the NE Explorer. Step 2 Click the Clock Source Reversion Parameter tab and set Clock Source WTR Time(min.).
NOTE

Set Clock Source WTR Time(min.) within the range of 0 minutes to 12 minutes at a spacing of 1 minute. By default, the WTR time is 5 minutes.

Step 3 Click Apply. ----End

4.5.12 Setting the PTP Clock Source Priority


If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP clock source of the highest priority fails, the OC traces the PTP clock source of the second highest priority. The priority table is configured with a source ID. When a local port receives a clock source in the priority table, the port checks whether the domain that the clock source belongs to is consistent with the domain configured at the local end.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The working mode of the NE must be set to TC+OC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority Table from the NE Explorer. Step 2 Click the Clock Source Priority Table tab and click New to create a clock source. You can change the working mode of NE only after you delete the PTP clock source priority. Step 3 Select a clock source and click
Issue 02 (2010-09-24)

or

to adjust the priority of the clock source.


4-19

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

4 Configuring PTP Clock

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 4 Click Apply. ----End

4-20

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

5
About This Chapter

Configuring Orderwire

You can configure orderwire for NEs by using the U2000. 5.1 Configuring Orderwire To provide the maintenance personnel with a dedicated express orderwire channel, you can configure orderwire for NEs. 5.2 Configuring F1 Data Port Services You can use the U2000 to configure F1 Data port services. 5.3 Configuring Asynchronous Data Services You can configure Asynchronous data services by using the U2000. 5.4 Configuration Example (Synchronous Data Services RTN 600) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the synchronous data service requirements. 5.5 Configuration Example (Asynchronous Data Services RTN 600) This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the point-to-point asynchronous data service requirements.

Issue 02 (2010-09-24)

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

5-1

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5.1 Configuring Orderwire


To provide the maintenance personnel with a dedicated express orderwire channel, you can configure orderwire for NEs.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function Tree. Click the General tab. Step 2 Click Query to query information from the NE. Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE

l Call Waiting Time(s) should be set to the same value for all NEs with orderwire communication. When the number of NEs is smaller than 30, set the value to 5 seconds. Otherwise, set it to 9 seconds. l The telephone number must be unique in an orderwire subnet. l Set the length of the telephone number according to the actual requirements. The maximum length is eight digits and the minimum length is three digits. In the same orderwire subnet, the number length must be the same.

Step 4 Click Apply. ----End

5.2 Configuring F1 Data Port Services


You can use the U2000 to configure F1 Data port services. 5.2.1 F1 Data Port Services The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by using the F1 byte. 5.2.2 Configuring F1 Data Port Services The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire connections, the engineer can create F1 data port services. The transmission rate is 64 kbit/s, that is, E0 level.

5.2.1 F1 Data Port Services


The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by using the F1 byte. The F1 data port is a transparent data port that transports codirectional P2P services at the rate of 64 kbit/s. It does not support data broadcast. Hence, only the P2P services can be turned up at an F1 data port. When you use the F1 data port, you only need to configure routes for the 64 kbit/s data, that is, whether the data is added to, dropped from or passes through the port. If you manually configure the port, you need to use the U2000 to configure each node along the communication channel. After the configurations take effect, the data can be transmitted.
5-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

Example for Configuring the F1 Data Port Services


Figure 5-1 shows how a F1 Data Port Services is configured. Figure 5-1 Configuring the F1 data port service
F1 Data Port F1 Data Port

Node A

Node B

Node C

Node A and node C transmit data through the F1 data port. You can use the U2000 to configure each node as follows: l Configure added or dropped services at node A. Select the F1 data port and a port on the intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port service from the client side is added or dropped from the F1 data port of the orderwire board, and is transmitted through the a port on the intermediate frequency (IF) board. Configure pass-through services at node B. Select two a port on the intermediate frequency (IF) board as the data channel ports. In this case, the F1 data port service passes through the two a port on the intermediate frequency (IF) board at this node. Configure added or dropped services at node C. Select the F1 data port and a port on the intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port service is cross-connected from the a port on the intermediate frequency (IF) board to the orderwire board, and then added or dropped from the F1 data port of the orderwire board.

5.2.2 Configuring F1 Data Port Services


The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire connections, the engineer can create F1 data port services. The transmission rate is 64 kbit/s, that is, E0 level.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The boards that are related to the synchronous data services must be configured.

Context
In the case of the RTN 610/620, the synchronous data services are transmitted over the F1 overhead bytes in the SDH/PDH radio frame or STM-N frame.In the case of the RTN 605, the synchronous data services are transmitted over the F1 overhead bytes in the radio frame.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-3

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 2 Click the F1 Data Port tab. Step 3 Press the Ctrl key and select two data channels from Available Data Channel. Click .

NOTE

Data Channel 1 and Data Channel 2: Depending on the board configuration, the following ports can be selected. l SDH optical/electrical port: When the SDH optical/electrical line port is selected, the F1 byte in the SDH frame of this port is used. l IF port: When the IF port is selected, the self-defined F1 byte in the radio frame of this port is used. l F1 port: When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port conforms to the G.703 and the rate is 64 kbit/s. l external clock port of the PXC board: When the PXC-1 is selected, the external clock port of the PXC board is used. In this case, the external clock port is used as the output port of the overhead bytes. When the F1 data channel of the RTN 605 transmits the synchronous data services, the F1 data channel is bound with the working channel in most cases.

Step 4 Click Apply. ----End

5.3 Configuring Asynchronous Data Services


You can configure Asynchronous data services by using the U2000. 5.3.1 Asynchronous Data Services The asynchronous data interfaces of the RTN equipment uses RS232 to implement universal asynchronous receiver/transmitter (UART) full-duplex communication. The data is transmitted transparently, and it is not required to configure interface rate or transmission control protocols by using the U2000. The maximum bit rate is 19.2 kbit/s. You can connect an NE to the data terminal equipment through this asynchronous data interface, and configure the communication mode as point to point. 5.3.2 Configuring Asynchronous Data Services To configure the asynchronous data services, you need to set the broadcast data port of the RTN equipment. In the case of the RTN 610/620, the Serial byte in the SDH/PDH radio overheads or
5-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

any of the bytes Serial1-Serial4 in the normal SDH overheads is used to transparently transmit the asynchronous data services. In the case of the RTN 605, the Serial byte in the PDH radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated.

5.3.1 Asynchronous Data Services


The asynchronous data interfaces of the RTN equipment uses RS232 to implement universal asynchronous receiver/transmitter (UART) full-duplex communication. The data is transmitted transparently, and it is not required to configure interface rate or transmission control protocols by using the U2000. The maximum bit rate is 19.2 kbit/s. You can connect an NE to the data terminal equipment through this asynchronous data interface, and configure the communication mode as point to point. Asynchronous data services use the overhead bytes (serial) in the SDH or PDH microwave or any one byte (serial1 through serial4) in the ordinary SDH overhead as the broadcast data communication channel.

5.3.2 Configuring Asynchronous Data Services


To configure the asynchronous data services, you need to set the broadcast data port of the RTN equipment. In the case of the RTN 610/620, the Serial byte in the SDH/PDH radio overheads or any of the bytes Serial1-Serial4 in the normal SDH overheads is used to transparently transmit the asynchronous data services. In the case of the RTN 605, the Serial byte in the PDH radio overheads is used to transmit the asynchronous data services. The asynchronous data services need to not be configured, but are automatically activated.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The boards that are related to the asynchronous data services must be configured.

Context
The asynchronous data port of the OptiX RTN 600 is an RS-232 port and can implement the universal asynchronous receiver/transmitter (UART) full-duplex communication. The service transmission is required to be point-to-point transparent transmission. Therefore, the port rate and transmission control protocol need not be configured and the maximum communication rate is 19.2 kbit/s. Hence, the asynchronous data port is also considered as the transparent data port.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the Broadcast Data Port tab. Step 3 Set the parameters of the broadcast data port.

Issue 02 (2010-09-24)

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

5-5

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

NOTE

l Overhead Byte: SERIAL1-SERIAL4, and default value is SERIAL1. l In the case of an SDH optical/electrical line, the preset overhead byte is used to transmit the asynchronous data services. l In the case of a radio link, a self-defined Serial overhead byte in the radio frame is used to transmit the asynchronous data services. l Broadcast Data Source/Broadcast Data Sink: Depending on the board configuration, the following values can be selected. l SERIAL1-SERIAL4: When this parameter is set so that it is the same as the SERIAL byte corresponding to the Overhead Byte, the asynchronous data port on the SCC board is used. l SDH optical/electrical port: When this parameter is set to the SDH optical/electrical line port, the Overhead Byte of this port is used. l IF port: When this parameter is set to IF port, the self-defined Serial byte in the radio frame of this port is used. l external clock port of the PXC board: When this parameter is set to the external clock port on the PXC board, the external clock port on the PXC board is used. In this case, the external clock port is used as the output port of overhead bytes.

Step 4 Click Apply. ----End

5.4 Configuration Example (Synchronous Data Services RTN 600)


This topic uses an example to describe how to plan the service parameters and complete the entire process of configuring the parameters of each NE according to the synchronous data service requirements. 5.4.1 Networking Diagram
5-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

The networking diagram forms the foundation of service planning. In the following example, the networking diagram shows the NE networking mode and service requirements. 5.4.2 Service Planning According to the service requirements and the equipment specifications that are shown in the networking diagram, the network planning department can plan all the services of the NEs. In the following example, the service planning covers all the parameter information required for configuring the NEs. 5.4.3 Configuration Process You can configure the synchronous data services of each NE based on the parameters of the service planning, by using the NMS.

5.4.1 Networking Diagram


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

64kbit/s

64kbit/s

5.4.2 Service Planning


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

Board Configuration Information


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

Issue 02 (2010-09-24)

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

5-7

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Configuring the Synchronous Data Port


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

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

Timeslot Allocation Information


Figure 5-3 Timeslot allocation of synchronous data services
Station Timeslot NE1 6-SL1-1 F1 2-SCC: F1 Add/Frop Forward NE2 6-SL1-1 5-IF1A-1 F1 2-SCC: F1 NE3 5-IF1A-1

Station Timeslot

NE1 6-SL1-1 F1 2-SCC: F1 Add/Frop Forward

NE2 6-SL1-1 5-IF0A-1 F1

NE3 8-IF0-1

2-SCC: F1

l l l

The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of NE3 are used to add/drop the synchronous data services. The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1 board in slot 6 of NE2 is used to transmit the synchronous data services. The F1 overhead byte on the radio link between the IF1A board in slot 5 of NE2 and the IF1A board in slot 5 of NE3 is used to transmit the synchronous data services.

5-8

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

l l l l l

The synchronous data services are passed through between the SL1 board in slot 6 and the IF1A board in slot 5 of NE2. The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of NE3 are used to add/drop the synchronous data services. The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1 board in slot 6 of NE2 is used to transmit the synchronous data services. The F1 overhead byte on the radio link between the IF0A board in slot 5 of NE2 and the IF board in logical slot 8 of NE3 is used to transmit the synchronous data services. The synchronous data services are passed through between the SL1 board in slot 6 and the IF0A board in slot 5 of NE2.

5.4.3 Configuration Process


You can configure the synchronous data services of each NE based on the parameters of the service planning, by using the NMS.

Prerequisite
You must be an NM user with "NE operator" authority or higher. All the required boards must be added.

Procedure
Step 1 5.2.2 Configuring F1 Data Port Services. 1. 2. 3. In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply. Parameter Data Channel 1 Data Channel 2 Value Range 6-SL1-1 F1 Description When the 6-SL1-1 port is selected, the F1 byte in the SDH frame of this port is used. When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port complies with ITU-T G.703 and the rate is 64 kbit/ s.

Step 2 5.2.2 Configuring F1 Data Port Services. 1. 2. 3. In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-9

Issue 02 (2010-09-24)

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Data Channel 1 Data Channel 2

Value Range 6-SL1-1 5-IF1A-1

Description When the 6-SL1-1 port is selected, the F1 byte in the SDH frame of this port is used. When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is used.

Step 3 5.2.2 Configuring F1 Data Port Services. 1. 2. 3. In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab. Hold down the Ctrl key and select two data channels from Available Data Channel. Then, click Apply. Parameter Data Channel 1 Value Range 5-IF1A-1 Description When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is used. When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1 port complies with ITU-T G.703 and the rate is 64 kbit/ s.

Data Channel 2

F1

----End

5.5 Configuration Example (Asynchronous Data Services RTN 600)


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

5-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

5.5.1 Networking Diagram


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

RS-232

RS-232

5.5.2 Service Planning


The timeslot allocation can be planned for the asynchronous data services based on the networking diagram.

Configuration of the Asynchronous Data Services


Table 5-3 Configuration of the asynchronous data services Parameter Overhead Byte Broadcast Data Source Broadcast Data Sink NE1 SERIAL1 6-SL1-1 S1 NE2 SERIAL1 5-IF1A-1 6-SL1-1 NE3 SERIAL1 5-IF1A-1 S1

Issue 02 (2010-09-24)

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

5-11

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Table 5-4 Configuration of the asynchronous data services Parameter Overhead Byte Broadcast Data Source Broadcast Data Sink NE1 SERIAL1 6-SL1-1 S1 NE2 SERIAL1 5-IF0A-1 6-SL1-1 NE3 SERIAL 8-IF0-1 S1

Timeslot Allocation Information


Figure 5-5 Timeslot allocation diagram
Station Timeslot NE1 6-SL1-1 Serial1 2-SCC: S1 Add/Frop Forward Station Timeslot NE1 6-SL1-1 Serial1 2-SCC: S1 Add/Frop Forward NE2 6-SL1-1 5-IF0A-1 Serial 2-SCC: S1 NE3 8-IF0-1 NE2 6-SL1-1 5-IF1A-1 Serial1 2-SCC: S1 NE3 5-IF1A-1

As shown in the timeslot allocation diagram, the asynchronous data services are as follows: l l l l l l l The S1 port on the SCC board in slot 2 of NE1 and S1 port on the SCC board in slot 2 of NE3 are used to add and drop the asynchronous data services. The S1 port on the SCC board in slot 2 of NE1 and S1 port of NE3 are used to add and drop the asynchronous data services. The SERIAL1 overhead byte on the SDH optical line between the SL1 board in slot 6 of NE1 and the SL1 board in slot 6 of NE2 is used to transmit the asynchronous data services. The self-defined SERIAL byte on the radio link between the IF1A board in slot 5 of NE2 and the IF1A board in slot 5 of NE3 to transmit the asynchronous data services. The self-defined SERIAL byte on the radio link between the IF0A board in slot 5 of NE2 and the IF0 board in logical slot 8 of NE3 to transmit the asynchronous data services. The asynchronous data services are passed through between port 1 of the SL1 board in slot 6 and port 1 of the IF1A board in slot 5 of NE2. The asynchronous data services are passed through between port 1 of the SL1 board in slot 6 and port 1 of the IF0A board in slot 5 of NE2.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

5-12

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5 Configuring Orderwire

5.5.3 Configuration Process


You can configure the asynchronous data services of each NE based on the parameters of the service planning, by using the NMS.

Prerequisite
You must be an NM user with "NE operator" authority or higher. All the required boards must be added.

Procedure
Step 1 5.3.2 Configuring Asynchronous Data Services. 1. 2. In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply. Parameter Overhead Byte Value Range SERIAL1 Description l In this example, Overhead Byte is set to SERIAL1. l In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services. Broadcast Data Source 6-SL1-1 l In this example, Broadcast Data Source is set to 6-SL1-1. l When this parameter is set to the SDH optical/electrical line port, Overhead Byte of this port is used. Selected Broadcast Data Sink S1 l In this example, Broadcast Data Sink is set to S1. l When this parameter is set so that it is the same as Overhead Byte, the asynchronous data port on the SCC board is used.

Step 2 5.3.2 Configuring Asynchronous Data Services. 1. 2. In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply.

Issue 02 (2010-09-24)

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

5-13

5 Configuring Orderwire

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Overhead Byte

Value Range SERIAL1

Description l In this example, Overhead Byte is set to SERIAL1. l In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services.

Broadcast Data Source

6-SL1-1

l In this example, Broadcast Data Source is set to 6-SL1-1. l When this parameter is set to the SDH optical/electrical line port, Overhead Byte of this port is used.

Selected Broadcast Data Sink

5-IF1A-1

l In this example, Selected Broadcast Data Sink is set to 5-IF1A-1. l When this parameter is set to IF port, the selfdefined SERIAL byte in the radio frame of this port is used.

Step 3 5.3.2 Configuring Asynchronous Data Services. 1. 2. In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab. After setting the parameters, click Apply. Parameter Overhead Byte Value Range SERIAL1 Description l In this example, Overhead Byte is set to SERIAL1. l In the case of a radio link, a self-defined SERIAL overhead byte in the radio frame is used to transmit the asynchronous data services. Broadcast Data Source 5-IF1A-1 l In this example, Broadcast Data Source is set to 5-IF1A-1. l When this parameter is set to IF port, the selfdefined SERIAL byte in the radio frame of this port is used. Selected Broadcast Data Sink S1 l In this example, Selected Broadcast Data Sink is set to S1. l When this parameter is set so that it is the same as Overhead Byte, the asynchronous data port on the SCC board is used.

----End

5-14

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

6 Configuring Environment Monitor Interfaces

Configuring Environment Monitor Interfaces

About This Chapter


6.1 Configuring External Alarms To configure external alarms, you need to configure the environment monitor port. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 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 and then to the processing equipment at the remote end. 6.2 Configuration Example (External Alarms RTN 600) This topic uses an example to describe how to plan the parameters of the external alarms and complete the data configuration according to the external alarm requirements.

Issue 02 (2010-09-24)

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

6-1

6 Configuring Environment Monitor Interfaces

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

6.1 Configuring External Alarms


To configure external alarms, you need to configure the environment monitor port. After the outputting of external alarms is configured, the alarm information of the OptiX RTN 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 and then to the processing equipment at the remote end.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Apply to the EOW, AUX and CXP boards.

Context
The external alarms are also considered as housekeeping alarms. The external alarm port is a relay port. This port can be either in the "on" state or in the "off" state. 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 board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 In the case of RTN 600 NEs: 1. Configure the input alarm. a. b. Select Input Relay from the drop-down list. Set the parameters of the input alarm.

c. 2.

Click Apply.

Configure the output alarm. a. b. Select Output Relay from the drop-down list. Set the parameters of the output alarm.

6-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

6 Configuring Environment Monitor Interfaces

c. 1. 2. 3.

Click Apply.

Step 3 In the case of RTN 900 NEs: Select the attributes you want to configure from the drop-down list. Click Query to query parameter values. Double-click a field to select or enter a value. click Apply.

----End

6.2 Configuration Example (External Alarms RTN 600)


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

6.2.1 Networking Diagram


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

Figure 6-1 Networking diagram

Alarm In1 Alarm In2 Alarm In3 Alarm Out

Issue 02 (2010-09-24)

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

6-3

6 Configuring Environment Monitor Interfaces

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Alarm In1 Alarm In2 Alarm In3 Alarm Out1 Alarm Out2

6.2.2 Service Planning


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

Alarm output port 2

Major Alarm Auto Trigger

Alarm input port 1

Alarm input port 2

Alarm input port 3

Table 6-2 Configuration of the external alarms Port No. Alarm output port Alarm Mode An Alarm is Generated if the Relay Turns Off and Low Level is Caused An Alarm is Generated if the Relay Turns On and High Level is Caused Alarm Trigger Condition Critical Alarm Auto Trigger

Alarm input port 1

6-4

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

6 Configuring Environment Monitor Interfaces

Port No. Alarm input port 2

Alarm Mode An Alarm is Generated if the Relay Turns On and High Level is Caused An Alarm is Generated if the Relay Turns On and High Level is Caused

Alarm Trigger Condition -

Alarm input port 3

6.2.3 Configuration Process


You can configure the external alarm services based on the parameters of the service planning, by using the NMS.

Prerequisite
You must be logged in to the NE. You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Configure external alarms. 1. 2. In the NE Explorer, select the EOW board and then choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Configure the input alarm. Select Input Relay from the drop-down list. Click Apply. Paramet er Using Status Alarm Mode Value Range EOW-1 Used EOW-2 EOW-3 In this example, Using Status of the alarm interface is set to Used. The alarm is generated when the relay is on. Description

An Alarm is Generated if the Relay Turns On and High Level is Caused

3.

Configure the output alarm. Select Output Relay from the drop-down list. Click Apply. Parameter Value Range EOW-1 Use or Not Working Mode Used Automatic In this example, Use or Not of the alarm interface is set to Used. Changing the status of the output relay according to Alarm Trigger Conditions and Alarm Mode.
6-5

Description

Issue 02 (2010-09-24)

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

6 Configuring Environment Monitor Interfaces

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter

Value Range EOW-1

Description

Alarm Trigger Conditions Alarm Mode

Critical Alarm Auto Trigger An Alarm is Generated if the Relay Turns Off and Low Level is Caused

The status of the output relay is changed automatically according to the preset value. The alarm is generated when the relay is off.

Parameter

Value Range EOW-1 EOW-2

Description

Use or Not Working Mode Alarm Trigger Conditions Alarm Mode

Used Automatic

In this example, Use or Not of the alarm interface is set to Used. Changing the status of the output relay according to Alarm Trigger Conditions and Alarm Mode. Major Alarm Auto Trigger The status of the output relay is changed automatically according to the preset value. The alarm is generated when the relay is off.

Critical Alarm Auto Trigger

An Alarm is Generated if the Relay Turns Off and Low Level is Caused

----End

6-6

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Configuring Interfaces (RTN 600)

About This Chapter


This section describes how to set the interface attributes of the boards. 7.1 Checking Board Parameters To learn about board parameter status, you can check board parameters. Before actual configuration operations in networking, you need to check board parameters, to make sure that the board parameter status meets the requirements of actual networking. 7.2 Configuring the Parameters of Various Ports This topic describes how to set the parameters of various ports. Normally, the default values of the parameters are adopted to meet the relevant requirements. In certain cases, however, the parameters of the ports need to be modified. 7.3 Configuring Ethernet Ports The Ethernet ports contain the internal Ethernet ports and external Ethernet ports. The external Ethernet ports are the physical ports that are used to connect the Ethernet equipment. The internal Ethernet ports (VCTRUNKs) are internal paths that implement Ethernet over SDH. 7.4 Disabling an Ethernet Port It is recommended that you disable an unused Ethernet port to suppress the reporting of the alarms related to the port. 7.5 Configuring a Service Load Indication There are two service load indications, which are Non-Loaded and Load. If a path is configured with services and carries real services, set Service Load Indication to Load. If a path is configured with services but does not carry real services, set Service Load Indication to NonLoaded to suppress the reporting of certain alarms.

Issue 02 (2010-09-24)

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

7-1

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7.1 Checking Board Parameters


To learn about board parameter status, you can check board parameters. Before actual configuration operations in networking, you need to check board parameters, to make sure that the board parameter status meets the requirements of actual networking.

Procedure
Step 1 Select the corresponding navigation path and check the related board parameters. 1. Check SDH board parameters. For the SDH board parameters, see Table 7-1. Table 7-1 SDH board parameters Board Type SDH Parameter Laser Switch Navigation Path a. In the NE Explorer, select a board. b. Choose Configuration > SDH Interface from the Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list. Application Scenario When configuring services on an optical interface of a board, enable this parameter. l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: The loop is performed toward the local NE. l Outloop: The loop is performed toward the opposite NE. Inloop and outloop of an optical interface affect services. They are used to locate faults. 2. Check PDH board parameters. For the PDH board parameters, see Table 7-2.

Optical(Electrical) Interface Loopback

7-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Table 7-2 PDH board parameters Boar d Type Paramet er Tributary Loopback Navigation Path Application Scenario l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: When input service signals reach the tributary board of the target NE, the signals revert to the original trail. This function is used to locate faults of each service path. l Outloop: When input service signals reach the tributary board through the input port of the local NE, the signals are looped back directly to the service output end. l Non-loaded: The service path does not process the services that are carried, to suppress alarms in non-loaded service paths. l Load: The service path processes the services that are carried. In the case of a tributary board that has services, set this parameter to Load. Normal, Retiming Mode of Tributary Clock, Retiming Mode of Cross-Connect Clock Default: Normal Sets the retiming mode of the board. The default value is usually selected.

PDH

Service Load Indication

Retiming Mode

a. In the NE Explorer, select a board. b. Choose Configuratio n > PDH Interface from the Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list.

3.

Check RTN board parameters. For the RTN board parameters, see Table 7-3. Table 7-3 RTN board parameters Boar d Type Paramet er Radio Work Mode RTN Navigation Path a. In the NE Explorer, select a board. b. Choose Configuratio n > IF Interface from the Application Scenario Specifies the microwave working mode. Its formats are service capacity, working bandwidth and modulation mode. The transmit end and the receive end must have the same settings of the microwave working mode. Radio Link ID: 1 to 4094

Radio Link ID

Issue 02 (2010-09-24)

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

7-3

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Boar d Type

Paramet er IF Port Loopback

Navigation Path Function Tree. c. Click By Board/Port (channel) and select Port from the drop-down list.

Application Scenario Sets the loopback status of an intermediate frequency interface on the equipment. Non-Loopback refers to the normal status. It is not required to set loopback during normal equipment operation. Outloop means that the input signal passes through the ingress port and reaches the intermediate frequency board at the local NE and then is directly loopbacked to the service egress end. Inloop means that the input signal returns from the intermediate frequency board of the destination NE along the original trail. This function is usually used to locate faults for various IF interfaces. Performing loopback on an intermediate frequency interface is a diagnosis function which may affect services of related ports. Exercise caution before performing this function.

2M Wayside Enable Status ATPC Enable Status

Enables or disables a 2 Mbit/s bypath service. This parameter is available only when you set Radio Work Mode to STM-1,28MHz, 128QAM. When the ATPC is enabled, according to the current receive power of the ODU and the set ATPC thresholds, the ATPC module inserts the ATPC overhead. According to the ATPC overhead, the opposite ODU adjusts the transmit power. When the ATPC is disabled, the ATPC module does not insert any ATPC overhead.

4.

Check data board parameters. For the data board parameters, see Table 7-4. Table 7-4 Data board parameters Boar d Type Ethern et Parame ter Enabled/ Disabled Navigation Path a. In the NE Explorer, select a board. b. Choose Configuration > Application Scenario

When configuring Ethernet board port services, set the port to Enabled.

7-4

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Boar d Type

Parame ter Working Mode Maximu m Frame Length

Navigation Path Ethernet Interface Management > Ethernet Interface from the Function Tree. c. Click External Port. d. Click the Basic Attributes tab.

Application Scenario Set the working mode of Ethernet ports according to networking configuration requirements. When a packet exceeds the maximum frame length that is set, the packet is discarded. Alternatively, the packet length is minimized to satisfy the specified frame length. By default, the value is set to 1522, unless otherwise specified. l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: Inside the equipment, services from the cross-connect side are looped back to the cross-connect side. This operation affects services configured on ports and is used to locate faults.

MAC Loopbac k

PHY Loopbac k

l Non-loopback: It is a normal state. When the equipment runs normally, set this parameter to non-loopback. l Inloop: Inside the equipment, services from the cross-connect side are looped back to the cross-connect side. This operation affects services configured on ports and is used to locate faults.

TAG a. In the NE Explorer, select a board. b. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. c. Click External Port. d. Click the TAG Attributes tab.

l Tag Aware: If the client-side equipment sends tag packets, set the TAG attribute of external ports to Tag Aware. l Access: If the client-side equipment sends untag packets, set the TAG attribute of external ports to Access. l Hybrid: If the client-side equipment sends tag and untag packets, set the TAG attribute of external ports to Hybrid. This parameter is used to identify tags in data packets. During the configuration of VLAN services, set this parameter to Enabled.

Entry Detectio n

Issue 02 (2010-09-24)

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

7-5

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 2 Modify board parameters according to service planning and actual board configurations. ----End

7.2 Configuring the Parameters of Various Ports


This topic describes how to set the parameters of various ports. Normally, the default values of the parameters are adopted to meet the relevant requirements. In certain cases, however, the parameters of the ports need to be modified. 7.2.1 Configuring the Parameters of SDH Interfaces This section describes how to set the parameters of SDH interfaces, including loopback of the SDH interface board and the enabling/disabling of the lasers at the SDH optical ports. 7.2.2 Configuring the Parameters of PDH Interfaces When the IDU 610/620 is used, you can set the loopback status and service loading indication of the tributary boards, by performing the operations. In the case of the E1 interface board, you can also set the tributary retiming function. In the case of the E3/T3 interface board, you can also set the service type and signal equalization. When the IDU 605 is used, you can set the path usage status, tributary loopback status, and path impedance, by performing the operations. 7.2.3 Setting the Parameters of IF Ports This topic describes how to configure the parameters of IF ports, including the IF attributes and ATPC attributes of the IF boards. 7.2.4 Setting the Parameters of ODU Ports This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

7.2.1 Configuring the Parameters of SDH Interfaces


This section describes how to set the parameters of SDH interfaces, including loopback of the SDH interface board and the enabling/disabling of the lasers at the SDH optical ports.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required SDH interface boards must be added.

Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explore. Choose Configuration > SDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel) (default option of the system). Step 3 Select Port from the dropdown list and set the parameters of the SDH interface board.

7-6

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Step 4 Click Apply. A dialog box is displayed and click OK. Step 5 Select VC4 Channel from the dropdown list. Step 6 Configure VC-4 path loopback.

Step 7 Click Apply. A dialog box is displayed and click OK. ----End

Parameters
Parameter Laser Switcha Value Open, Close Default Value Open Description l This parameter indicates whether the laser is enabled to receive/transmit optical signals. l Normally, this parameter takes the default value. Optical (Electrical) Interface Loopback Non-Loopback, Inloop, Outloop Non-Loopback l Optical (electrical) inloop indicates that loopback occurs in the SDH optical (electrical) signals to be transmitted to the opposite end. l Optical (electrical) outloop indicates that loopback occurs in the SDH optical (electrical) signals to be received. l Normally, this parameter takes the default value.

Issue 02 (2010-09-24)

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

7-7

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter VC4 Loopback

Value Non-Loopback, Inloop, Outloop

Default Value Non-Loopback

Description l VC-4 path inloop indicates that loopback occurs in the VC-4 signals to be transmitted to the opposite end. l VC-4 path outloop indicates that loopback occurs in the VC-4 signals to be received. l Normally, this parameter takes the default value.

NOTE

a: Only SDH optical interface boards support this parameter.

7.2.2 Configuring the Parameters of PDH Interfaces


When the IDU 610/620 is used, you can set the loopback status and service loading indication of the tributary boards, by performing the operations. In the case of the E1 interface board, you can also set the tributary retiming function. In the case of the E3/T3 interface board, you can also set the service type and signal equalization. When the IDU 605 is used, you can set the path usage status, tributary loopback status, and path impedance, by performing the operations.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required PDH interface boards must be added.

Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel) (default value). Step 3 Select Port from the drop-down list, Set the parameters of the PDH interface.

Step 4 Select Port from the drop-down list, Set the parameters of the PDH interfaces according to the types of the PDH interfaces. l Set the parameters of the PDH interfaces on the E1 interface board.
7-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

l Set the parameters of the PDH interface on the E3/T3 interface board.

Step 5 Click Apply. A dialog box is displayed and click OK. ----End

Parameters
Parameter Tributary Loopback Value Range Non-Loopback, Inloop, Outloop Default Value Non-Loopback Description l Tributary inloop indicates that loopback occurs in the tributary signals to be transmitted to the remote end. l Tributary outloop indicates that loopback occurs in the tributary signals to be received. l Generally, this parameter takes the default value. Path Impedance Service Load Indication 75 ohms, 120 ohms Load, Non-Loaded 75 ohms Load Generally, this parameter takes the default value. l This parameter is valid for the tributary ports that are configured with services. l When this parameter is set to Load, the board detects whether alarms exist in this path. l When this parameter is set to NonLoaded, the board does not detect whether alarms exist in this path. l Generally, this parameter takes the default value.

Issue 02 (2010-09-24)

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

7-9

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Retiming Modea

Value Range Normal, Retiming Mode of Tributary Clock, Retiming Mode of CrossConnect Clock

Default Value Normal

Description l By using the retiming function, the retiming reference signal from the SDH network and the service data signal are combined and then sent to the client equipment, thus decreasing the output jitter in the signal. In this way, the retiming function ensures that the service code flow can normally transfer the retiming reference signal. l When this parameter is set to Normal, the retiming function is not used. l When this parameter is set to Retiming Mode of Tributary Clock, the retiming function is used with the clock of the upstream tributary unit traced. l When this parameter is set to Retiming Mode of Cross-Connect Clock, the retiming function is used with the clock of the cross-connect unit traced. l It is recommended that the external clock, instead of the retiming function, is used to provide an external clock for the client equipment. l If the retiming function is required, it is recommended that you adopt Retiming Mode of Cross-Connect Clock.

Port Service Typeb

E3, T3

E3

l This parameter indicates the type of the services the tributary board processes. l Set this parameter according to the type of the accessed services.

Input Signal Equalizationb

Unequalized, Equalized

Unequalized

l This parameter is valid only when Service Type is set to T3. l This parameter indicates whether the input signals are equalized. l If the trunk cable exceeds 70 m, it is recommended that you set this parameter to Equalized. Otherwise, adopt the default value.

7-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Output Signal Equalizationb

Value Range Unequalized, Equalized

Default Value Unequalized

Description l This parameter is valid only when Service Type is set to T3. l This parameter indicates whether the output signals are equalized. l If the trunk cable exceeds 70 m, it is recommended that you set this parameter to Equalized. Otherwise, adopt the default value.

NOTE

l a: Only E1 interface boards support this parameter. l b: Only E3/T3 interface boards support the parameters.

7.2.3 Setting the Parameters of IF Ports


This topic describes how to configure the parameters of IF ports, including the IF attributes and ATPC attributes of the IF boards.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required IF boards must be added.

Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Set each parameter for the IF attributes.

NOTE

The IFH1 board of the IDU 605 1F/2F does not support the setting of the Radio Work Mode. The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode.

Step 4 Click Apply. Step 5 Click the ATPC Attributes tab. Step 6 Set each parameter for the ATPC attributes.

Issue 02 (2010-09-24)

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

7-11

7 Configuring Interfaces (RTN 600)


NOTE

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Automatic Threshold Enable Status.

Step 7 Click Apply. ----End

7-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameters
Parameter Radio Work Mode Value Range l In the case of the IDU 610/620, the value range is as follows: 1,4E1,7MHz,QP SK 2,4E1,3.5MHz, 16QAM 3,8E1,14MHz,Q PSK 4,8E1,7MHz, 16QAM 5,16E1,28MHz, QPSK 6,16E1,14MHz, 16QAM 7,STM-1,28MH z,128QAM 8,E3,28MHz,QP SK 9,E3,14MHz, 16QAM 10,22E1,14MHz ,32QAM 11,26E1,14MHz ,64QAM 12,32E1,14MHz ,128QAM 13,35E1,28MHz ,16QAM 14,44E1,28MHz ,32QAM 15,53E1,28MHz ,64QAM 16,5E1,7MHz,Q PSK 17,10E1,14MHz ,QPSK 18,2E1,3.5MHz, QPSK l In the case of the IDU 605 1A/1B/ 2B, the value
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-13

Default Value 1,4E1,7MHz,QPSK (IF1A/B) 5,16E1,28MHz,QP SK (IF0A/B) 7,STM-1,28MHz, 128QAM (IFX) 5,16E1,28MHz,QP SK (IF0)

Description l This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format. l The IF1A/B board supports radio work modes 1 to 15. The IF0A/B board supports radio work modes 5, 16, 17, and 18. The IFX board supports radio work mode 7 only. l The IFH1 board of the IDU 605 1F/2F does not support the setting of the Radio Work Mode. l The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode. l Set this parameter according to the network planning. The radio work modes of the IF boards at both the radio link must be the same.

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter

Value Range range is as follows: 5,16E1,28MHz, QPSK 16,5E1,7MHz,Q PSK 17,10E1,14MHz ,QPSK 18,2E1,3.5MHz, QPSK

Default Value

Description

Radio Link ID

1 to 4094

l As the identifier of a radio link, this parameter is used to avoid 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 planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same.

IF Port Loopbacka

Non-Loopback, Inloop, Outloop

Non-Loopback

l IF port inloop indicates that loopback occurs in the IF signals to be transmitted to the remote end. l IF port outloop indicates that loopback occurs in the IF signals to be received. l Generally, this parameter takes the default value.

7-14

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter 2M Wayside Enable Statusb

Value Range Enabled, Disabled

Default Value Disabled

Description l In the case of the IFX board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz, 128QAM. l In the case of the IF1A/B board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz, 128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM. l This parameter indicates whether the radio link transmits the wayside E1 service. l The wayside E1 service is a 2.048 kbit/s service that is transmitted by the microwave frame overhead. The IDU 610/620 accesses the wayside E1 service through the external clock interface on the PXC board.

2M Wayside Input Boardb

1, 3

l This parameter is valid only when 2M Wayside Enable Status is set to Enabled. l This parameter indicates the slot in which the PXC board accesses the wayside E1 service through the external clock port.

XPIC Enablec

Enabled, Disabled

Enabled

l This parameter indicates whether the XPIC function is enabled. l If the IF board does not use the XPIC function, set this parameter to Disabled. In this case, use the XPIC cable to perform self-loop at the XPIC port.

Issue 02 (2010-09-24)

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

7-15

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter ATPC Enable Statusd

Value Range Enabled, Disabled

Default Value Disabled

Description l This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the TX power of the transmitter automatically traces the changes of the RX level at the receive end, within the ATPC controlled range. l It is recommended that you set this parameter to Disabled in areas where fast fading severely affects the radio transmission. l To ensure that the TX power does not change during the commissioning process, set this parameter to Disabled. After the commissioning is complete, you can set this parameter to another value.

ATPC Upper Threshold (dBm)d ATPC Lower Threshold (dBm)d

-20 dBm to -75 dBm -35 dBm to -90 dBm

-45 dBm -70dBm

l Set the central value of the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. l Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB. l This parameter sets whether to enable the ATPC. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. l When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATP upper and lower thresholds based on the working mode of the IF board. l When the function is disabled, the manually set ATPC upper and lower thresholds are used. l The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Automatic Threshold Enable Status.

ATPC Automatic Threshold Enable Status

Enabled, Disabled

Enabled

7-16

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

7 Configuring Interfaces (RTN 600)

l a: The IFH2 and IFX boards do not support the loopback on the IF ports. l b: The IFH2 and IF0A/B boards do not support wayside E1 services. l c: The IFH2, IF0A/B, and IF1A/B boards do not support the XPIC function. l d: The ATPC attributes need to be set to the same values at both ends of a radio link.

7.2.4 Setting the Parameters of ODU Ports


This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Configure the TX frequency and T/R spacing.

Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Configure the transmit power and receive power of the ODU.

Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status.

Step 10 Click Apply. ----End


Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-17

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameters
Parameter Transmit Frequency (MHz) Value Range Default Value Description l The parameter specifies the channel center frequency. l This parameter cannot be set to a value that is less than the minimum Transmit frequency supported by the ODU + 50% channel spacing or more than the maximum Transmit frequency supported by the ODU - 50% channel spacing. l The difference between the Transmit frequencies of both the ends of a radio link is a T/R spacing. l Set this parameter according to the planning. Maximum Transmit Power (dBm) l This parameter cannot be set to a value that exceeds the rated power range supported by the ODU. l Set this parameter to limit the maximum transmit power of the ODU within this preset value. The maximum transmit power adjusted by ATPC should not exceed this value. l Set this parameter according to the planning. Transmit Power (dBm) l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. l The Transmit power of the ODU should be set to the same value at both the ends of a radio link. l Set this parameter according to the planning.

7-18

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Receive Power (dBm)

Value Range -

Default Value -

Description l This parameter is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l Set this parameter according to the planning.

T/R Spacing (MHz)

0-4294967.295

l This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. 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.

Configure Transmission Status

mute, unmute

unmute

l When this parameter is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. l When this parameter is set to unmute, the ODU can normally receive and transmit microwave signals. l Generally, this parameter takes the default value.

Issue 02 (2010-09-24)

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

7-19

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7.3 Configuring Ethernet Ports


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

7.3.1 Configuring External Ethernet Ports


When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet services, the attributes of the external ports need to be configured so that the external ports can work with the data communication equipment on the client side to provide the normal access to the Ethernet services.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Ethernet board must be included in the NE Panel.

Precautions
l The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6. Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively. The EFT4 board does not support the setting of TAG attributes, network attributes, and advanced attributes. Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively. Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
7-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board). Ethernet ports FE1-FE3 of an EMS4 board (a logical board) correspond to PORT1PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4. Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively. Ports GE1 and GE2 of an EM4T board corresponds to PORT3 and PORT4 respectively.

The following procedures describe how to configure the external port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes, network attributes, and advanced attributes. The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it supports certain Ethernet service access functions. The procedure for configuring the Ethernet port of the IFH2 board is similar to the procedure for configuring the external Ethernet port. The IFH2 board, however, supports the configuration of only the basic attributes and flow control function.

Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE

If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the NE Explorer.

Step 2 Set the basic attributes of the port. 1. 2. Click the Basic Attributes tab. Set the basic attributes of the port.

3.

Click Apply.

Step 3 Set the flow control mode of the port. 1. 2. Click the Flow Control tab. Set the flow control mode of the port.

3.

Click Apply.

Step 4 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.

Issue 02 (2010-09-24)

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

7-21

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

3. 1. 2.

Click Apply. Click the Network Attributes tab. Set the network attributes of the port.

Step 5 Optional: Set the network attributes of the port.

3. 1. 2.

Click Apply. Click the Advanced Attributes tab. Set the advanced attributes of the port.

Step 6 Optional: Set the advanced attributes of the port.

3.

Click Apply.

----End

Parameters
Parameter Enabled/Disabled Value Range Enabled, Disabled Default Value Disabled Description l In the case of the port that accesses services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled. l If this parameter is set to Enabled for the port that does not access services, an ETH_LOS alarm may be generated.

7-22

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Working Mode

Value Range 10M Full-Duplex, 100M Full-Duplex, Auto-Negotiation (EFT4) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (EMS6) Auto-Negotiation, 10M Full-Duplex, 100M Full-Duplex, 1000M Full-Duplex (IFH2) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, Auto-Negotiation (a logical board EMS4, PORT1-PORT3) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (a logical board EMS4, PORT4)

Default Value Auto-Negotiation

Description l The 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 on the opposite side works in the full-duplex mode, set the working mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. l When the equipment on the opposite side works in the half-duplex mode, set the working mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side. l The GE optical interface on the EMS6 board supports the 1000M full-duplex mode only.

Issue 02 (2010-09-24)

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

7-23

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Maximum Frame Length

Value Range 1518-1535 (EFT4) 1518-9600 (EMS6) 1522/1632 (a logical board EMS4)

Default Value 1522

Description The value of this parameter should be greater than the maximum length of a frame among all the data frames to be transported. In the case of the EFT4 board, this parameter is invalid for Jumbo frames. In the case of the EMS6 board, this parameter has a restriction on Jumbo frames. If Jumbo frames are not considered and the accessed services are ordinary Ethernet frames that use VLAN tags or do not have VLAN tags, it is recommended that you use the default value. If the access services include services that use double tags such as QinQ services, it is recommended that you set this parameter to 1526. In the case of the IDU 605 1F/2F, set Maximum Frame Length of all the ports on the logical EMS4 board to the same value.

MAC Loopback

Non-Loopback, Inloop

Non-Loopback

l When this parameter is set to Inloop, the Ethernet frame signals that are to be sent to the remote end are looped back. l In normal cases, use the default value.

PHY Loopback

Non-Loopback, Inloop

Non-Loopback

l When this parameter is set to Inloop, the Ethernet physical signals that are to be sent to the remote end are looped back. l In normal cases, use the default value.

7-24

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter NonAutonegotiation Flow Control Mode

Value Range Disabled, Enable Symmetric Flow Control, Send Only, Receive Only (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2) Disabled, Enable (a logical board EMS4)

Default Value Disabled

Description l This parameter is used when Working Mode is not set to Auto-Negotiation. l When this parameter is set to Enable Symmetric Flow Control, the port can send PAUSE frames and process received PAUSE frames. l When this parameter is set to Send Only, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. l When this parameter is set to Receive Only, the port can process received PAUSE frames but cannot send PAUSE frames in the case of congestion. l When this parameter is set to Enable for the logical EMS4 board, the port can send PAUSE frames and process received PAUSE frames. l The non-autonegotiation flow control mode of the equipment on the local side must match the non-autonegotiation flow control mode of the equipment on the opposite side.

Issue 02 (2010-09-24)

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

7-25

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Autonegotiation Flow Control Mode

Value Range Disabled, Enable Symmetric/ Dissymmetric Flow Control, Enable Symmetric Flow Control, Enable Dissymmetric Flow Control (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2) Disabled, Enable Symmetric Flow Control (a logical board EMS4)

Default Value Disabled

Description l This parameter is used when Working Mode is set to Auto-Negotiation. l When this parameter is set to Enable Symmetric Flow Control, the port can send and process PAUSE frames. l When this parameter is set to Enable Dissymmetric Flow Control, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. l When this parameter is set to Enable Symmetric/Dissymmetric Flow Control, the port can perform as follows: Sends and processes PAUSE frames. Sends but does not process PAUSE frames. Processes but does not send PAUSE frames. l The autonegotiation flow control mode of the equipment on the local side must match the autonegotiation flow control mode of the equipment on the opposite side.

Entry Detection

Enabled, Disabled

Enabled

l This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. l Set this parameter according to actual situations.

TAG

Access, Tag Aware, Hybrid

Tag Aware

l When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 7-5. 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 that do not have 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.

7-26

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Default VLAN ID

Value Range 1 to 4095

Default Value 1

Description l This parameter is valid only when TAG is set to Access or Hybrid. l For using this parameter, see Table 7-5. l Set this parameter according to actual situations.

VLAN Priority

0 to 7

l This parameter is valid only when TAG is set to Access or Hybrid. l For using this parameter, see Table 7-5. l When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value.

Port Attributes

UNI, C-Aware, SAware

UNI

l When this parameter is set to UNI, the port processes data frames according to the tag attributes. l When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. l In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.

Enabling Broadcast Packet Suppression

Enabled, Disabled

Disabled

This parameter specifies whether to restrict the traffic of broadcast packets according to the ratio of the broadcast packets to the total packets. When a broadcast storm may occur in the equipment on the opposite side, set this parameter to Enabled. The port discards the received broadcast packets when the ratio of the received broadcast packets to the total packets exceeds the value of this parameter. The value of this parameter should be greater than the ratio of the broadcast packets to the total packets when the broadcast storm does not occur. Generally, set this parameter to 30% or a greater value.

Broadcast Packet Suppression Threshold

10% to 100%

30%

Issue 02 (2010-09-24)

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

7-27

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Loop Detection

Value Range Disabled, Enabled

Default Value Disabled

Description Sets whether to enable loop detection, which is used to check whether a loop exists at the port. Sets whether to enable the loop port shutdown function. After the loop port shutdown function is enabled, the port is automatically shut down when a self-loop is detected. It is recommended that this parameter adopts the default value.

Loop Port Shutdown

Disabled, Enabled

Enabled

Table 7-5 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame How to Process Tag aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrida The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.

Ingress

Egress

Tagged frame

The port transmits the frame.

7-28

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

7 Configuring Interfaces (RTN 600)

a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605 1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters the bridge.

7.3.2 Configuring the Internal Port of the Ethernet Board


When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board on the opposite side to realize the transmission of the Ethernet services in the network.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Ethernet board must be included in the slot layout.

Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6. l l The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively. The EFT4 board does not support the setting of TAG attributes and network attributes. The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be transmitted depending on information of the created Ethernet services.

The following procedures describe how to configure the internal port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes and network attributes.

Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Choose Internal Port. Step 2 Set the encapsulation and mapping protocol used by the port. 1. 2. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters.

3. 1. 2. 3. 4.
Issue 02 (2010-09-24)

Click Apply. Click the Bound Path tab. Click Configuration. The system displays the Bound Path Configuration dialog box. In Configurable Ports, select a VCTRUNK as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-29

Step 3 Set the VC paths to be bound with the port.

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

5. 6. 7.

Select required items in Available Resources and Available Timeslots and click Optional: Repeat Step 3.5 and bind other VCTRUNKs. Click OK. Then, click Yes in the dialog box that is displayed.

Step 4 Configure the LCAS function for the port. 1. 2. Click the LCAS tab. Set the Enabling LCAS parameter and other LCAS parameters.

3.

Click Apply.

Step 5 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.

3.

Click Apply.

Step 6 Optional: Set the network attributes of the port. 1. 2.


7-30

Click the Network Attributes tab. Set the network attributes of the port.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

3.

Click Apply.

----End

Parameters
Parameter Mapping Protocol Scramble Value Range GFP, LAPS, HDLC Unscrambled, Scrambling Mode [X43+1], Scrambling Mode [X48+1] Yes, No Default Value GFP Scrambling Mode [X43+1] Description It is recommended that you use the default value. l This parameter specifies the scrambling polynomial used by the mapping protocol. l It is recommended that you use the default value. Yes l This parameter is valid only when Mapping Protocol is set to LAPS or HDLC. l When this parameter is set to Yes, the FCS is the result after you perform a negation operation for the CRC. l When this parameter is set to No, the FCS is the CRC. Check Field Length FCS32, FCS16, No FCS32 l When this parameter is set to FCS32, a 32-bit FCS is used. l When this parameter is set to FCS16, a 16-bit FCS is used. l When the Ethernet board uses the GFP mapping protocol, this parameter can be set to FCS32, FCS16, or No. l When the Ethernet board uses the HDLC mapping protocol, this parameter can be set to FCS32 or FCS16. l When the Ethernet board uses the LAPS mapping protocol, this parameter can be set to FCS32 or FCS16. l It is recommended that you use the default value.

Set Inverse Value for CRC

Issue 02 (2010-09-24)

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

7-31

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter FCS Calculated Bit Sequence

Value Range Big endian, Little endian

Default Value l Big endian (GFP) l Little endian (LAPS or HDLC)

Description l When this parameter is set to Big endian, the least significant byte of the FCS is placed first and the most significant byte is placed last. l When this parameter is set to Little endian, the most significant byte of the FCS is placed first and the least significant byte is placed last. l It is recommended that you use the default value.

Extension Header Option

No, Yes

No

l This parameter specifies whether the GFP payload header contains the extension header and eHEC. l It is recommended that you use the default value.

Configurable Ports Available Bound Paths

VCTRUNKs -

VCTRUNK 1 -

This parameter specifies the VCTRUNK whose VC paths are to be configured. Adhere to the following principles to plan and set this parameter: l The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. l Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. l Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. l Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. l Generally, bidirectional paths are bound.

7-32

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Enabling LCAS

Value Range Enabled, Disabled

Default Value Disabled

Description l This parameter specifies whether the LCAS function is enabled. l The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved.

LCAS Mode

Huawei Mode, Standard Mode

Huawei Mode

l This parameter specifies the sequence in which the LCAS sink sends the MST control packet and Rs-Ack control packet. l When this parameter is set to Huawei Mode, the LCAS sink first sends the RsAck and then sends the MST. l When this parameter is set to Standard Mode, the LCAS sink first sends the MST and then sends the Rs-Ack. l If the equipment on the opposite side is the third-party equipment and does not support the Huawei mode, it is recommended that you set this parameter to Standard Mode. Otherwise, set this parameter to Huawei Mode.

Hold Off Time (ms)

0, any integer that ranges from 2000 to 10000 and has a step of 100

2000

l When a member link is faulty, the LCAS performs switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and performs an LCAS switching. This parameter specifies the duration of the delay. l If the paths of the VCTRUNK are configured with protection, it is recommended that you set this parameter to 2000 ms. Otherwise, set this parameter to 0.

WTR Time(s)

0 to 720

300

l When the time after a member link is restored to normal reaches the set value of this parameter, the VCG uses the restored member link. l It is recommended that you use the default value.

Issue 02 (2010-09-24)

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

7-33

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter TSD

Value Range Enabled, Disabled

Default Value Disabled

Description l This parameter specifies whether the TSD is used as a condition for determining whether a member link is faulty. In the case of the VC-12, the TSD refers to the BIP_SD. In the case of the VC-3, the TSD refers to the B3_SD_VC3. l It is recommended that you use the default value.

Entry Detection

Enabled, Disabled

Enabled

l This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. l Set this parameter according to actual situations.

TAG

Access, Tag Aware, Hybrid

Tag Aware

l When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 7-6. 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 that do not have 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.

Default VLAN ID

1 to 4095

l This parameter is valid only when TAG is set to Access or Hybrid. l For using this parameter, see Table 7-6. l Set this parameter according to actual situations.

VLAN Priority

0 to 7

l This parameter is valid only when TAG is set to Access or Hybrid. l For using this parameter, see Table 7-6. l When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value.

7-34

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameter Port Attributes

Value Range UNI, C-Aware, SAware

Default Value UNI

Description l When this parameter is set to UNI, the port processes data frames according to the tag attributes. l When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. l In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.

Activation Status

Activated, Inactivated

Displays whether the VCTRUNK is activated.

NOTE

l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other end of the transmission line. l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line.

Table 7-6 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame How to Process Tag Aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.

Ingress

Issue 02 (2010-09-24)

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

7-35

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Direction

Type of Data Frame Tagged frame

How to Process Tag Aware The port transmits the frame. Access The port strips the VLAN tag from the frame and then transmits the frame. Hybrid l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.

Egress

7.3.3 Modifying the Type Field of Jumbo Frames


By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Ethernet board must be included in the slot layout.

Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.

Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Jumbo Frame from the Function Tree. Step 2 Modify the type field of Jumbo frames.

Step 3 Click Apply. ----End


7-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

Parameters
Parameter Jumbo Frame Value Range 00 00 to FF FF Default Value 88 70 Description This parameter specifies the type field of Jumbo frames. Set this parameter according to the type field of the accessed Jumbo frames.

7.3.4 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
You must be an NM user with "NE operator" authority or higher. The Ethernet board must be included in the slot layout.

Precautions
The IDU 620 supports the Ethernet switching board EMS6.

Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes > QinQ Type Area Settings from the Function Tree. Step 2 Modify the type field of QinQ frames.

Step 3 Click Apply. ----End

Parameters
Parameter QinQ Type Area (Hexadecimal) Value Range 81 00, 98 A8, 91 00 Default Value 81 00 Description This parameter specifies the type field of QinQ frames. Set this parameter according to the type field of the accessed QinQ frames.

Issue 02 (2010-09-24)

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

7-37

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7.3.5 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth


When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Ethernet board must be included in the slot layout.

Procedure
Step 1 Select the Ethernet board from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Step 2 Click the Bound Path tab. Step 3 Click Configuration. The system displays the Bound Path Configuration dialog box. Step 4 Optional: Dynamically increase the VCTRUNK bandwidth. 1. 2. 3. 4. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select desired items in Available Resources and Available Timeslots and click Optional: Repeat Step 4.3 and bind other VC paths. .

Step 5 Optional: Dynamically decrease the VCTRUNK bandwidth. 1. 2.


7-38

Do not select the Display in Combination check box. Select the VC paths to be deleted in Selected Bound Paths and click
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7 Configuring Interfaces (RTN 600)

3.

Optional: Repeat Step 5.2 to delete other VC paths.

Step 6 Click OK. ----End

Parameters
For specific parameters, see 7.3.2 Configuring the Internal Port of the Ethernet Board.

7.4 Disabling an Ethernet Port


It is recommended that you disable an unused Ethernet port to suppress the reporting of the alarms related to the port.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. There must be no service at the Ethernet port to be disabled.

Context

CAUTION
Disabling an Ethernet port may interrupt services.

Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the External Port option button. Step 3 Click the Basic Attributes tab. Double-click Enabled/Disabled of the port to be disabled and select Disabled.

Step 4 Click Apply. In the Prompt dialog box, click OK. In the Operation Result dialog box, click Close. ----End
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-39

7 Configuring Interfaces (RTN 600)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

7.5 Configuring a Service Load Indication


There are two service load indications, which are Non-Loaded and Load. If a path is configured with services and carries real services, set Service Load Indication to Load. If a path is configured with services but does not carry real services, set Service Load Indication to NonLoaded to suppress the reporting of certain alarms.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Context

CAUTION
If you set the service load indication to Non-Loaded, the services may be interrupted or you may fail to log in to certain NEs.

Procedure
Step 1 In the NE Panel, select a board, right-click, and choose Service Load Indication from the shortcut menu. Step 2 Double-click Service Load Indication of the corresponding path, and select Load or NonLoaded. Step 3 Click Apply. In the Operation Result dialog box, click Close.
NOTE

If you select Non-Loaded, you need not click OK in the Confirm dialog box.

----End

Postrequisite
In the case of a path that is configured with services but does not carry real services, if you set Service Load Indication to Non-Loaded, you need to change the value of Service Load Indication to Load at both ends of the services after the path carries real services in the future.

7-40

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Configuring Interfaces (RTN 900)

About This Chapter


This section describes how to set the interface attributes of the boards. 8.1 Configuring SDH Interfaces This section describes how to set the attributes of SDH interfaces. The attributes of SDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced attributes. 8.2 Configuring PDH Interfaces This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different settings of the interface attributes. The attributes of a PDH interface include the general attributes, layer 2 attributes, layer 3 attributes and advanced attributes. 8.3 Configuring Ethernet Interfaces This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different settings of the interface attributes. The attributes of the Ethernet interface include the general attributes, Layer 3 attributes, advanced attributes and flow control. 8.4 Configuring Microwave Interfaces This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU information of the radio link, microwave interface attributes, and ODU interface parameters. 8.5 Configuring Serial Interfaces This topic describes how to set the attributes of serial interfaces. 8.6 Configuring ML-PPP This section describes how to configure Multilink PPP (MP) group. MP is a technology used to bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP links in the MP group to the same destination. 8.7 Configuring an Ethernet Virtual Interface This section describes how to configure an Ethernet virtual interface. After you configure the Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated

Issue 02 (2010-09-24)

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

8-1

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3 attributes. 8.8 Configuring an IMA Group When the RTN equipment accesses IMA services, configure an ATM IMA group at the access node.

8-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.1 Configuring SDH Interfaces


This section describes how to set the attributes of SDH interfaces. The attributes of SDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced attributes. 8.1.1 Setting the General Attributes of SDH Interfaces The general attributes of an SDH interface define the physical-layer information, such as the port mode, encapsulation type, and maximum data packet length. 8.1.2 Setting the Advanced Attributes of SDH Interfaces The routine maintenance parameters can be set by setting the advanced attributes of SDH interfaces. 8.1.3 Querying the Running Status of PPP In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 8.1.4 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

8.1.1 Setting the General Attributes of SDH Interfaces


The general attributes of an SDH interface define the physical-layer information, such as the port mode, encapsulation type, and maximum data packet length.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Select the desired board. Step 3 Set the parameters as required.
NOTE

Note the following issues during parameter settings: l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case, channelized STM-N services can be accessed. l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM services can be accessed. l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the interface does not enable the PPP, and thus the equipment bears less load. If you select PPP, the interface can access the MPLS or IP service. l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Issue 02 (2010-09-24)

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

8-3

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.1.2 Setting the Advanced Attributes of SDH Interfaces


The routine maintenance parameters can be set by setting the advanced attributes of SDH interfaces.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.1.3 Querying the Running Status of PPP


In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created SDH interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End
8-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.1.4 Resetting the PPP


In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created SDH interface must be PPP.

Context

CAUTION
Resetting the PPP will interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

8.2 Configuring PDH Interfaces


This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different settings of the interface attributes. The attributes of a PDH interface include the general attributes, layer 2 attributes, layer 3 attributes and advanced attributes.

Context
The application scenario of a PDH interface depends on the setting of the interface attributes. For details, refer to Table 8-1. Table 8-1 Application scenario of PDH interfaces Application Scenario Carrying the CES service Interface Type E1 interface Required Interface Attribute General attributes, Advanced attributes
8-5

Issue 02 (2010-09-24)

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

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Application Scenario Carrying the ATM service Carrying the tunnel

Interface Type E1 interface E1 interface

Required Interface Attribute General attributes, Layer 2 attributes General attributes, Layer 3 attributes

NOTE

When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, that is, frame format, to ensure that the frame format is the same as the service encapsulation format. When the emulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interface to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interface should be set to non-framing. When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, the IMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer 2 in 8.2.1 Setting General Attributes of PDH Interfaces. When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create the ML-PPP group, and configure the interface as an ML-PPP member.

Follow the procedure shown in Figure 8-1 to configure a PDH interface. Figure 8-1 Procedure for configuring a PDH interface
Carry CES service Carry ATM service Carry Tunnel

Start

Start

Start

Configure general attributes

Configure general attributes

Configure general attributes

Configure advanced attributes

Configure advanced attributes

Configure layer 3 attributes

End

End

Configure advanced attributes

End

Required

Optional

8.2.1 Setting General Attributes of PDH Interfaces


8-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Before you create services, you need to set the general attributes of the corresponding PDH interfaces. The general attributes of a PDH interface define the related information of the physical layer. 8.2.2 Setting the Layer 3 Attributes of PDH Interfaces Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface. The layer 3 attributes of a PDH interface define the related attributes of the network layer. 8.2.3 Setting the Advanced Attributes of PDH Interfaces The advanced attributes of PDH interfaces include frame format, line encoding format and loopback mode. 8.2.4 Querying the Running Status of PPP In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 8.2.5 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

8.2.1 Setting General Attributes of PDH Interfaces


Before you create services, you need to set the general attributes of the corresponding PDH interfaces. The general attributes of a PDH interface define the related information of the physical layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Select the desired board. Step 3 Set the parameters as required.
NOTE

Note the following issues during parameter settings: l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case, TDM services can be accessed. l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM services can be accessed. l If the PDH interface is used for the inband DCN, the Port Mode cannot be set to Layer 1 or Layer 2. l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the interface does not enable the PPP protocol, and thus the equipment bears less load. If you select PPP, the interface can carry the MPLS. l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-7

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 5 Click Close. ----End

8.2.2 Setting the Layer 3 Attributes of PDH Interfaces


Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface. The layer 3 attributes of a PDH interface define the related attributes of the network layer.

Prerequisite
l l l You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 3. In General Attributes, Encapsulation Type must be set to PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings:

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.2.3 Setting the Advanced Attributes of PDH Interfaces


The advanced attributes of PDH interfaces include frame format, line encoding format and loopback mode.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required.

8-8

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

8 Configuring Interfaces (RTN 900)

In the case of the OptiX RTN , Frame Mode of the packets at the PDH interface can be set to 30 or 31. In hybrid networking, make sure that the frame modes of the local port and opposite port should be the same. l 30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data. l 31: In the E1 frame format, timeslots 1-31 are used to transport service data.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.2.4 Querying the Running Status of PPP


In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created PDH interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End

8.2.5 Resetting the PPP


In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created PDH interface must be PPP.

Context

CAUTION
Resetting the PPP will interrupt services.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-9

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

8.3 Configuring Ethernet Interfaces


This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different settings of the interface attributes. The attributes of the Ethernet interface include the general attributes, Layer 3 attributes, advanced attributes and flow control.

Context
The application scenario of an Ethernet interface depends on the setting of the interface attributes. For details, refer to Table 8-2. Table 8-2 Application scenario of Ethernet interfaces Application Scenario Accessing the Ethernet service Carrying the tunnel Interface Type Ethernet interface Ethernet interface Required Interface Attribute General attributes General attributes, Layer 3 attributes

Follow the procedure shown in to configure an Ethernet interface. 8.3.1 Setting the General Attributes of Ethernet Interfaces Before you configure the layer 3 attributes of an Ethernet interface, you need to configure the general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length. 8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an Ethernet interface define the related information of the data link layer. 8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface
8-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related attributes of the network layer. 8.3.4 Setting the Advanced Attributes of Ethernet Interfaces The routine maintenance parameters can be set through setting the advanced attributes of Ethernet interfaces. 8.3.5 Configuring Flow Control In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting Ethernet packets. As a result, congestion is avoided.

8.3.1 Setting the General Attributes of Ethernet Interfaces


Before you configure the layer 3 attributes of an Ethernet interface, you need to configure the general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

l When Port Mode is set to Layer 2, the Encapsulation Type support Null. l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface can be used by tunnel. l When Port Mode is set to Layer Mix, the port can carry layer 2 services and layer 3 services. To create a VLAN sub-interface, set the port mode to Layer Mix. l Before changing Layer 3 to Layer Mix, make sure that route protocols, such as IGP-ISIS not enabled on the port. Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port and no Layer 2 service is configured on the port. l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces


After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-11

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

within the PSN network. The Layer 2 attributes of an Ethernet interface define the related information of the data link layer.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 2.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings: l QinQ Type Domain can be set only when Encapsulation Type is QinQ. l TAG can be set only when Encapsulation Type is 802.1Q. l Default VLAN ID and VLAN Priority are valid when TAG is access or hybrid.

Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.3.3 Setting the Layer 3 Attributes of an Ethernet Interface


When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related attributes of the network layer.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 3.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.

8-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

8 Configuring Interfaces (RTN 900)

Note the following issues during parameter settings: l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnels carried by port cannot exceed the physical bandwidth of the port. l When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.3.4 Setting the Advanced Attributes of Ethernet Interfaces


The routine maintenance parameters can be set through setting the advanced attributes of Ethernet interfaces.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.3.5 Configuring Flow Control


In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting Ethernet packets. As a result, congestion is avoided.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Flow Control tab.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-13

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 3 Select the desired board and set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.4 Configuring Microwave Interfaces


This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU information of the radio link, microwave interface attributes, and ODU interface parameters.

Context
The application scenario of an microwave interface depends on the setting of the interface attributes. For details, refer to Table 8-3. Table 8-3 Application scenario of microwave interfaces Interface Attributes Layer 2 attributes Layer 3 attributes Signal to Carry Ethernet packets Tunnels Functioning Location UNI side or NNI side NNI side

NOTE

When the microwave interface is used to carry the QinQ Link, the configuration procedure is similar to the configuration procedure when the microwave interface is used to carry the Ethernet service. In this case, however, the encapsulation types are different. For details, see 8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces.

Follow the procedure shown in Figure 8-2 to configure an microwave interface.

8-14

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Figure 8-2 Procedure for configuring an microwave interface


Carry Ethernet Packets Carry Tunnel

Start

Start

Creating IF 1+1 Protection

Creating IF 1+1 Protection

Configuring the IF/ ODU Information of a Radio Link

Configuring the IF/ ODU Information of a Radio Link

Setting the General Attributes

Setting the General Attributes

Setting the IF Attributes

Setting the IF Attributes

Setting the Layer 2 Attributes

Setting the Layer 3 Attributes

Setting the Advanced Attributes

Setting the Advanced Attributes

Setting the Parameters of ODU Ports

Setting the Parameters of ODU Ports

End

End

Required Optional

8.4.1 Setting the General Attributes of Microwave Interfaces Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to configure the general attributes of the corresponding microwave interface. The general attributes of an microwave interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length. 8.4.2 Setting the IF Attributes of Microwave Interfaces The IF information of the microwave interface specifies the relevant information of the IF board, including the AM attribute and ATPC attribute.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-15

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces After the layer 2 attributes of an microwave interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an microwave interface define the related information of the data link layer. 8.4.4 Setting the Layer 3 Attributes of Microwave Interfaces The layer 3 attributes of an microwave interface define the related attributes of the network layer. 8.4.5 Setting the Advanced Attributes of Microwave Interfaces The routine maintenance parameters can be set through setting the advanced attributes of microwave interfaces. 8.4.6 Setting the Parameters of ODU Ports(RTN900V1R1) This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU. 8.4.7 Setting the Parameters of ODU Ports(RTN900V1R2) This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

8.4.1 Setting the General Attributes of Microwave Interfaces


Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to configure the general attributes of the corresponding microwave interface. The general attributes of an microwave interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ. l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface can be used by tunnel. l In the case an NNI interface, MTU(byte), which indicates the maximum data packet length, must be set to a value larger than 960. A DCN packet contains a maximum of 960 bytes. If MTU(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End
8-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.4.2 Setting the IF Attributes of Microwave Interfaces


The IF information of the microwave interface specifies the relevant information of the IF board, including the AM attribute and ATPC attribute.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

l When you set Assured Capacity Modulation and Full Capacity Modulation, note the following points: This parameter is valid only when Enable AM is set to Enable. l When you set Manually Specified Modulation, note the following points: This parameter is valid only when Enable AM is set to Disable. l When you set ATPC Upper Threshold(dBm), note the following points: Generally, ATPC Upper Threshold(dBm) should be 20 dB to 30 dB higher than ATPC Lower Threshold(dBm), and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power is adjusted in a timely manner and the interference to adjacent systems is reduced. l When you set ATPC Lower Threshold(dBm), note the following points: Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.4.3 Setting the Layer 2 Attributes of Microwave Interfaces


After the layer 2 attributes of an microwave interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an microwave interface define the related information of the data link layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-17

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

When you set QinQ Type Domain, note the following points: QinQ Type Domain can be set only when Encapsulation Type is QinQ.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.4.4 Setting the Layer 3 Attributes of Microwave Interfaces


The layer 3 attributes of an microwave interface define the related attributes of the network layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings: l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnel that is carried by a port cannot exceed the physical bandwidth of the port. l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are interrupted. l When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End
8-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.4.5 Setting the Advanced Attributes of Microwave Interfaces


The routine maintenance parameters can be set through setting the advanced attributes of microwave interfaces.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

When you set Radio Link ID, note the following points: 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 planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same. l Before performing the loopback operation for the IF board, disable the AM function at the two ends of a link.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.4.6 Setting the Parameters of ODU Ports(RTN900V1R1)


This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-19

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 3 Configure the TX frequency and T/R spacing.


NOTE

l When you set Transmission Frequency (MHz), note the following points: l The parameter specifies the channel center frequency. l This parameter cannot be set to a value that is less than the minimum TX frequency supported by the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU - 50% channel spacing. l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing. l Set this parameter according to the planning. l When you set T/R Spacing (MHz), note the following points: l This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. 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.

Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Configure the TX power of the ODU.
NOTE

Note the following when setting the Transmit Power(dBm) parameters. l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. l The TX power of the ODU should be set to the same value at both the ends of a radio link. l Set this parameter according to the planning. Note the following when setting the TX High Threshold(dBm) and TX Low Threshold(dBm) parameters. l When the actual launched power of the ODU is higher than TX High Threshold(dBm), the system records the time when the actual launched power is higher than TX High Threshold(dBm) and the time when the actual launched power is higher than TX Low Threshold(dBm) as performance events. l When the actual launched power of the ODU is within the range from TX Low Threshold(dBm) to TX High Threshold(dBm), the system records the time when the actual launched power of the ODU is higher than TX Low Threshold(dBm) as a performance event. l When the actual launched power of the ODU is lower than TX Low Threshold(dBm), no record is saved. l The TX High Threshold(dBm) and TX Low Threshold(dBm) parameters are valid only when the ATPC function is enabled. Note the following when setting the RX High Threshold(dBm) and RX Low Threshold(dBm). l When the actual received power of the ODU is lower than RX Low Threshold(dBm), the system records the time when the actual received power is lower than RX High Threshold(dBm) and the time when the actual received power is lower than RX Low Threshold(dBm) as performance events. l When the actual received power of the ODU is within the range from RX Low Threshold(dBm) to RX High Threshold(dBm), the system records the time when the actual received power of the ODU is higher than RX Low Threshold(dBm) as a performance event. l When the actual received power of the ODU is higher than RX Low Threshold(dBm), no record is saved.

Step 7 Click Apply.


8-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status. Step 10 Click Apply. ----End

8.4.7 Setting the Parameters of ODU Ports(RTN900V1R2)


This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Configure the TX frequency and T/R spacing.

Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Configure the transmit power and receive power of the ODU.

Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status.

Step 10 Click Apply. ----End


Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-21

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameters
Parameter Transmit Frequency (MHz) Value Range Default Value Description l The parameter specifies the channel center frequency. l This parameter cannot be set to a value that is less than the minimum Transmit frequency supported by the ODU + 50% channel spacing or more than the maximum Transmit frequency supported by the ODU - 50% channel spacing. l The difference between the Transmit frequencies of both the ends of a radio link is a T/R spacing. l Set this parameter according to the planning. Maximum Transmit Power (dBm) l This parameter cannot be set to a value that exceeds the rated power range supported by the ODU. l Set this parameter to limit the maximum transmit power of the ODU within this preset value. The maximum transmit power adjusted by ATPC should not exceed this value. l Set this parameter according to the planning. Transmit Power (dBm) l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. l The Transmit power of the ODU should be set to the same value at both the ends of a radio link. l Set this parameter according to the planning.

8-22

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Parameter Receive Power (dBm)

Value Range -

Default Value -

Description l This parameter is used to set the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l Set this parameter according to the planning.

T/R Spacing (MHz)

0-4294967.295

l This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. 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.

Configure Transmission Status

mute, unmute

unmute

l When this parameter is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. l When this parameter is set to unmute, the ODU can normally receive and transmit microwave signals. l Generally, this parameter takes the default value.

Issue 02 (2010-09-24)

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

8-23

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8.5 Configuring Serial Interfaces


This topic describes how to set the attributes of serial interfaces. 8.5.1 Creating Serial Interfaces You can create a serial interface at the VC12 level or 64 kbit/s timeslot level. 8.5.2 Setting the General Attributes of a Serial Interface Before you set the layer 3 attributes of a serial interface, you need to set the general attributes of the serial interface. The general attributes of a serial interface define the related information of the physical layer. 8.5.3 Setting the Layer 3 Attributes of Serial Interfaces In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data. The layer 3 attributes of a serial interface define the related attributes of the network layer. 8.5.4 Querying the Running Status of PPP In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 8.5.5 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

8.5.1 Creating Serial Interfaces


You can create a serial interface at the VC12 level or 64 kbit/s timeslot level.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed. Step 3 Set the parameters as required.
NOTE

l In the case of the serial interface at the VC12 level, currently a serial interface can be bound to only one timeslot. l In the case of the serial interface at the 64 kbit/s level, when the E1 frame mode is 30, timeslots 0 and 16 are unavailable. When the E1 frame mode is 31, timeslot 0 is unavailable.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End
8-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.5.2 Setting the General Attributes of a Serial Interface


Before you set the layer 3 attributes of a serial interface, you need to set the general attributes of the serial interface. The general attributes of a serial interface define the related information of the physical layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A serial interface must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Set the parameters as required.
NOTE

When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMA binding. When you set Port Mode to Layer 3, you can set Encapsulation Type to PPP or Null. When you set Encapsulation Type to PPP, you can add the serial interface to an MP group. The serial interfaces that are bound to the same MP group have the same E1 frame mode. When Encapsulation Type is Null, Port Mode can be changed to Layer 2. In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 4 Click Close. ----End

8.5.3 Setting the Layer 3 Attributes of Serial Interfaces


In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data. The layer 3 attributes of a serial interface define the related attributes of the network layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. In General Attributes, Encapsulation Type must be set to PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab and set the parameters as required.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-25

8 Configuring Interfaces (RTN 900)


NOTE

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Note the following issues during parameter settings: l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnels carried by port should be not more than the physical bandwidth of the port. l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are interrupted. l When changing Specify IP Address from Manually to Unnumbered IP, manually specify the invalid IP address (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manually specified. l When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 4 Click Close. ----End

8.5.4 Querying the Running Status of PPP


In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created serial interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End

8.5.5 Resetting the PPP


In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created serial interface must be PPP.
8-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Context

CAUTION
Resetting the PPP will interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

8.6 Configuring ML-PPP


This section describes how to configure Multilink PPP (MP) group. MP is a technology used to bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP links in the MP group to the same destination.

Context
Follow the procedure shown in Figure 8-3 to configure an MP group.

Issue 02 (2010-09-24)

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

8-27

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 8-3 Procedure for configuring an MP group


Start

Enable the PPP at the interface

Create MP group

Configure members to an MP group

End

Required

Optional

8.6.1 Overview of the ML-PPP The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP) links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP. 8.6.2 Basic Concepts Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format of the ML-PPP. 8.6.3 ML-PPP Application In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided into fragments, which are transported over several PPP links to the same destination. The MLPPP is applicable to the PPP-supported ports, such as the E1 interface. 8.6.4 Creating MP Groups You can bind E1 interfaces on which PPP is enabled by creating an MP group, so that the bound E1 interfaces are used as a logical port to carry tunnels. 8.6.5 Configuring Member Interfaces of MP Groups To modify the bandwidth of the MP group, add or delete the member interfaces into or from the MP group.

8-28

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.6.1 Overview of the ML-PPP


The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP) links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP. The ML-PPP function benefits the network in the following aspects: l l l Bandwidth increased. Load shared and backed up. Delay shortened by fragments.

The ML-PPP complies with RFC1990 (PPP multilink protocol). The ML-PPP protocol focuses on the transmission of fragments of data packets over multiple data links, reassembly and sequence of these fragments.

8.6.2 Basic Concepts


Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format of the ML-PPP.

ML-PPP Packet Format


The ML-PPP packets have the following formats, shown as Figure 8-4: l l Long sequence number fragment format (LSNFF): The sequence number field has 24 bits. This format is the default format. Short sequence number fragment format (SSNFF): The sequence number field has 12 bits.

The fragment format of transmitted packets can be different from that of received packets on the condition of mutual negotiation. If the negotiation does not allow that the received packets are of the LSNFF format, the MP packets of the SSNFF format should be transmitted.

Issue 02 (2010-09-24)

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

8-29

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 8-4 ML-PPP packet format


Adress PPP Header Protocol 0x003d 0x003d 0xFF 0xFF Control 0x03

B ML-PPP Header

sequence number

sequence number

fragment data ....

PPP FCS

FCS

Long Sequence Number Fragment Format

Adress PPP Header

0xFF 0xFF

Control

0x03

Protocol

0x003d 0x003d

ML-PPP Header

sequence number

fragment data ....

PPP FCS

FCS

Short Sequence Number Fragment Format

8.6.3 ML-PPP Application


In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided into fragments, which are transported over several PPP links to the same destination. The MLPPP is applicable to the PPP-supported ports, such as the E1 interface. As shown in Figure 8-5, the ML-PPP bundles several PPP links into one logical port.

8-30

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Figure 8-5 ML-PPP application scenario


NE1 PPP link PPP link PPP link ML-PPP NE2

8.6.4 Creating MP Groups


You can bind E1 interfaces on which PPP is enabled by creating an MP group, so that the bound E1 interfaces are used as a logical port to carry tunnels.

Prerequisite
l l l You must be an NM user with "NE operator" authority or higher. E1 interfaces on which PPP is enabled must be created. The E1 Frame Format of the local MP group and the opposite MP group should be consistent.

Context
NOTE

The MP group can be bound only with the E1 interfaces of the same board.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP Group Management from the Function Tree. Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed. Step 3 Set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 5 Click Close. ----End

8.6.5 Configuring Member Interfaces of MP Groups


To modify the bandwidth of the MP group, add or delete the member interfaces into or from the MP group.

Prerequisite
l l
Issue 02 (2010-09-24)

You must be an NM user with "NE operator" authority or higher. An MP group must be configured.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-31

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP Group Management from the Function Tree. Step 2 Select an MP group and click Configuration. The Config Member Interface dialog box is displayed. Step 3 Set the parameters as required. Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interrupt the services.
NOTE

Deleting the member interface of the MP group may damage the service. The member interface in the same MP group must have the same frame mode. That is, the values of Frame Mode are all 30 or 31. for the parameters of Frame Mode, to see E1 Frame Format.

Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful. Step 6 Click Close. ----End

8.7 Configuring an Ethernet Virtual Interface


This section describes how to configure an Ethernet virtual interface. After you configure the Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3 attributes. 8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces The general attributes of an Ethernet virtual interface define the related information of the ATM adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need to configure the general attributes of the Ethernet virtual interface. 8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling status. You can create a tunnel after setting the Layer 3 attributes.

8.7.1 Setting the General Attributes of Ethernet Virtual Interfaces


The general attributes of an Ethernet virtual interface define the related information of the ATM adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need to configure the general attributes of the Ethernet virtual interface.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree.
8-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Step 2 Click Query. The Operation Result dialog box is displayed dialog box is displayed indicating that the operation is successful. Step 3 Click Close. The general attributes of an Ethernet virtual interface are displayed in the field. Step 4 Specify the port name as required. Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close. ----End

8.7.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces


The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling status. You can create a tunnel after setting the Layer 3 attributes.

Prerequisite
You must be an NM user with "NE monitor" authority or higher. The general attributes of Ethernet virtual interface must be set.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab, set the Specify IP to Manually and set the IP Address and IP Mask for the port. Step 3 Double-click the Enable Tunnel field, and select Enabled.

Step 4 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close. ----End

8.8 Configuring an IMA Group


When the RTN equipment accesses IMA services, configure an ATM IMA group at the access node.

Context
Figure 8-6 shows the flow for configuring an IMA group.

Issue 02 (2010-09-24)

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

8-33

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 8-6 IMA group configuration flow


Start

Configure bound paths for an ATM IMA group

Configure IMA group attributes

Configure ATM interface attributes

Query the IMA group states

Query the states of the link of an IMA group

Reset an IMA group

Modify an IMA group

Delete an IMA group

End

Required

Optional

8.8.1 Configuring Bound Channels in an ATM IMA Group When the RTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1 or Fractional E1 ports. 8.8.2 Configuring Attributes of an ATM IMA Group After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements. 8.8.3 Configuring ATM Interface Attributes This section describes methods of configuring the ATM interface parameters. 8.8.4 Querying IMA Group States In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal. 8.8.5 Querying IMA Link States In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal. 8.8.6 Resetting an IMA Group In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol.
8-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.8.7 Modifying an IMA Group When attributes of an IMA group displayed on the U2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services. 8.8.8 Deleting an IMA Group Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

8.8.1 Configuring Bound Channels in an ATM IMA Group


When the RTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1 or Fractional E1 ports.

Prerequisite
You must be an NM user with "NE operator" authority or higher. When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the VCTRUNK resources are occupied and thus the IMA group cannot be created. When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to Layer 2.

Context
NOTE

Only the E1 ports on the same processing board can be bound.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed. Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports respectively. Step 4 Select E1, Fractional E1 for Level. Step 5 Select a port in Available Resources. Click to bind the port to the VCTRUNK. Click

to cancel binding of the port to the VCTRUNK.

Issue 02 (2010-09-24)

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

8-35

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last. The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12 frame mode. When the member links of an IMA group are at the serial ports of the 64K level, there are the following restrictions: l One serial port should be bound with a minimum of three 64K timeslots. l The number of bound 64K timeslots should be the same for different serial ports. l In one E1, only one serial port can be used as a member link of an IMA group. Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

8.8.2 Configuring Attributes of an ATM IMA Group


After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
NOTE

Take the following precautions when setting parameters. l You can enable or disable the IMA Protocol Enable Status of the IMA group only after configuring the bound path of the corresponding VCTRUNK of the IMA group. l IMA Transmit Frame Length: The optional values are 32, 64, 128 and 256. l When IMA Symmetry Mode be set to Symmetric Mode and Symmetric Operation, Minimum Number of Active Transmitting Links should be consistent with Minimum Number of Active Receiving Links. l Maximum Delay Between Links: This parameter indicates the maximum delay variance among different links in one IMA group. The value ranges from 1 ms to 120 ms, with 1 ms spacing. l If the IMA protocol is enabled, only Minimum Number of Active Transmitting Links, Minimum Number of Active Receiving Links and Maximum Delay Between Links can be set. l You can modify the IMA Protocol Version, IMA Transmit Frame Length and IMA Symmetry Mode only after you disable the IMA Protocol Enable Status.

----End

8.8.3 Configuring ATM Interface Attributes


This section describes methods of configuring the ATM interface parameters.
8-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the ATM Interface Management tab. Step 2 Optional: Click Query to query the current attributes of each interface. Step 3 Set relevant attributes of the interfaces bound with the IMA group as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

8.8.4 Querying IMA Group States


In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal.

Prerequisite
l l You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

8.8.5 Querying IMA Link States


In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal.

Prerequisite
l l You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA link.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-37

8 Configuring Interfaces (RTN 900)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

8.8.6 Resetting an IMA Group


In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. You must complete the creation of the IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

8.8.7 Modifying an IMA Group


When attributes of an IMA group displayed on the U2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification of the IMA group may interrupt services. Exercise caution for this.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End
8-38 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

8 Configuring Interfaces (RTN 900)

8.8.8 Deleting an IMA Group


Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The IMA Protocol Enable Status of the IMA group must be Disabled.

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting the IMA group may interrupt the services. Exercise caution for this.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed, indicating that the operation may interrupt the services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

Issue 02 (2010-09-24)

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

8-39

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

9
About This Chapter

Configuring Radio Links

Before creating a radio link between two radio sites, you must configure the corresponding radio link information. 9.1 Radio Link A radio link is the channel that is used to transmit the information between stations. This chapter describes basic concepts of the radio link. 9.2 Configuring the IF/ODU Information of a Radio Link You can set the IF/ODU information that is frequently used by the radio link based on each radio link. 9.3 Configuring the ATPC Function To configure the ATPC function, set the ATPC attributes of the IF board. 9.4 Creating an XPIC Workgroup When two IF boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes. 9.5 Configuring the Hybrid/AM Attribute The Hybrid microwave supports the transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the reliable transmission of the E1 services and flexible transmission of the Ethernet services whose bandwidth is large and changes dynamically. 9.6 Hop Management The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time.

Issue 02 (2010-09-24)

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

9-1

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9.1 Radio Link


A radio link is the channel that is used to transmit the information between stations. This chapter describes basic concepts of the radio link. The radio frequency signal whose frequency ranges from 300 MHz to 300 GHz is usually called to be the radio signal. The line that transmit the radio signal is the radio link.
NOTE

During the creation of a radio link, the link ID at local end must be consistent with that at the opposite end, to ensure the communication.

Refer to Figure 9-1. The communication channel between two radio stations is the radio link. The radio stations are classified by function as follows: Figure 9-1 Classification of Radio Stations

Relay Station

Terminal Station

Add/Drop Station Terminal Station

Pivotal Station Terminal Station

l l l l

Terminal station: A station located at either end of the link or at the endpoint of a tributary link. Relay station: A station located in the middle of the link without adding or dropping voice channels. Pivotal station: A station located in the backbone link to communicate with other stations in various directions. Add/drop station: A station located in the middle of the link to add/drop tributaries and realize the communication in two directions of the backbone link.

9.2 Configuring the IF/ODU Information of a Radio Link


You can set the IF/ODU information that is frequently used by the radio link based on each radio link.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board or IF port must be added.
9-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

Precautions
l 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. 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. In the case of XPIC radio links, one XPIC workgroup corresponds to two radio links. The IF/ODU information of the radio links should be configured in the XPIC workgroup. In the case of N+1 radio links, one N+1 protection group corresponds to N+1 radio links and the IF/ODU information of the N+1 radio links should be set respectively.
NOTE

l l

In the example in the preceding figure: l l l 1+1HSB: indicates that the IF 1+1 HSB protection is configured for the NE. 3-IFX2: indicates the IF card that is being configured. 4-IFX2: S indicates the standby IF card of the 1+1 protection.

Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs, select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 In the case of RTN 900 V100R001 NEs, select the NE from the Object Tree in the NE Explorer. Choose Configuration > Microwave Link Configuration from the Function Tree. Step 3 Click IF/ODU Configuration. Step 4 Click an IF board icon or ODU icon. Then, the system displays the IF/ODU information of the radio link to which the IF board belongs. Step 5 Set the corresponding IF information of the radio link.

Step 6 Click Apply. Step 7 Set the corresponding ODU information of the radio link.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-3

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 8 Click Apply.


NOTE

Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio link.

----End

Parameters
Parameter Work Mode Value Range l 1,4E1,7MHz,Q PSK l 2,4E1,3.5MHz, 16QAM l 3,8E1,14MHz, QPSK l 4,8E1,7MHz, 16QAM l 5,16E1,28MHz, QPSK l 6,16E1,14MHz, 16QAM l 7,STM-1,28MH z,128QAM l 8,E3,28MHz,Q PSK l 9,E3,14MHz, 16QAM l 10,22E1,14MH z,32QAM l 11,26E1,14MH z,64QAM l 12,32E1,14MH z,128QAM l 13,35E1,28MH z,16QAM l 14,44E1,28MH z,32QAM l 15,53E1,28MH z,64QAM l 16,5E1,7MHz, QPSK l 17,10E1,14MH z,QPSK l 18,2E1,3.5MHz ,QPSK
9-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

Default Value The default value varies with different IF boards.

Description l This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format. l The IFH1 board of the RTN 605 does not support the setting of the Work Mode. l The IF1A/IF1B board supports radio work modes 1-15 and the IF0A/IF0B board supports radio work modes 5 and 16-18. The IFX board supports radio work mode 7. l The IFH2 board of the RTN 620 does not support the setting of the Work Mode. l Set this parameter according to the planning. The radio work modes of the IF boards at both the radio link must be the same.

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

Parameter Link ID

Value Range 1-4094

Default Value 1

Description l As the identifier of a radio link, this parameter is used to avoid 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 planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same.

ATPC Enable Status

Enabled, Disabled

Disabled

l This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the TX power of the transmitter automatically traces the changes of the RX level at the receive end, within the ATPC controlled range. l It is recommended that you set this parameter to Disabled in areas where fast fading severely affects the radio transmission. l To ensure that the TX power does not change during the commissioning process, set this parameter to Disabled. After the commissioning is complete, you can set this parameter to another value.

ATPC Automatic Threshold Enable Status

Enabled, Disabled

Enabled

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

Issue 02 (2010-09-24)

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

9-5

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter TX Frequency (MHz)

Value Range 0-4294967.295

Default Value 0.0

Description l The parameter specifies the channel center frequency. l This parameter cannot be set to a value that is less than the minimum TX frequency supported by the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU - 50% channel spacing. l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing. l Set this parameter according to the planning.

Range of Frequency (MHz) TX Power (dBm)

For example: 22017 to 23025 -10.0 to +35.0

-10.0

Sets the range of the transmit frequencies of an ODU board. l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. l The TX power of the ODU should be set to the same value at both the ends of a radio link. l Set this parameter according to the planning.

T/R Spacing (MHz)

0-4294967.295

0.0

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 TX frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX frequency is one T/R spacing lower than the receive power. 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.

9-6

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

Parameter TX Status

Value Range mute, unmute

Default Value unmute

Description l When this parameter is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. l When this parameter is set to unmute, the ODU can normally receive and transmit microwave signals. l Generally, this parameter takes the default value.

TX Power (dBm) TX High Threshold TX Low Threshold RX High Threshold RX Low Threshold Range of Power (dBm) Enable AM Channel Space Assured Capacity Modulation

-10.0 to 35.0 -10.0 to 35.0 -10.0 to 35.0 -90.0 to -20.0 -90.0 to -20.0 For example: 12 Enabled, Disabled 7M, 14M, 28M, 56M QPSK, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM

Disabled 7M QPSK

Sets the transmit power for a radio frequency port. Sets the higher threshold of the transmitted optical power. Sets the lower threshold of the transmitted optical power. Sets the higher threshold of the received optical power. Sets the lower threshold of the received optical power. Sets the range of the transmitted optical power of the ODU board. Sets the enable statue of AM. Sets the channel spacing of the corresponding radio links. This parameter specifies the lowest modulation scheme that the AM function supports. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid microwave must ensure and the availability of the radio link that corresponds to this modulation scheme. This parameter is valid only when Enable AM is set to Enabled.

Issue 02 (2010-09-24)

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

9-7

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter Full Capacity Modulation

Value Range QPSK, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM

Default Value QPSK

Description This parameter specifies the highest modulation scheme that the AM function supports. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid microwave and the availability of the radio link that corresponds to this modulation scheme. This parameter is valid only when Enable AM is set to Enabled.

Manually Specified Modulation

QPSK, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM

QPSK

This parameter specifies the modulation scheme that the radio link uses for the transmission. This parameter is valid only when Enable AM is set to Disabled.

NOTE

The ATPC attributes at both the ends of a radio link should be set to the same.

9.3 Configuring the ATPC Function


To configure the ATPC function, set the ATPC attributes of the IF board.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The related IF board must be added.

Precautions
l l In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC attributes of the main IF board. The following procedure describes the configuration of ATPC parameters in the IF interface configuration dialog box of the IF board. You can also set ATPC parameters in the following configuration dialog boxes: Create an XPIC working group IF/ODU configuration l l In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be modified. The transmit power of the two ODUs that are in an XPIC working group should be the same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value for the IF boards that are in an XPIC working group.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

9-8

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

In the case of the Hybrid microwave, the AM switching is controlled through detection of the change in the ATPC information and returned microwave message.

Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs. 1. 2. 3. Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Click the ATPC Attributes tab. Set the ATPC attributes.

NOTE

The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.

4.

Click Apply.

Step 2 In the case of RTN 900 V1R1 NEs, see Configuring the IF Attributes of Microwave Interfaces to take the details of configuration. ----End

Parameters
Parameter ATPC Enable Status Value Range Enabled, Disabled Default Value Disabled Description l This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. l In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled.

Issue 02 (2010-09-24)

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

9-9

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter ATPC Upper Threshold (dBm)

Value Range -20 to -75

Default Value -45

Description l When the ATPC function is enabled, if the RSL at the receive end is higher than the preset ATPC upper threshold at the receive end, the receiver notifies the transmitter to decrease the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold. l Generally, ATPC Upper Threshold (dBm) should be 20 dB to 30 dB higher than ATPC Lower Threshold (dBm), and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power is adjusted in a timely manner and the interference to adjacent systems is reduced.

ATPC Lower Threshold (dBm)

-35 to -90

-70

l When the ATPC function is enabled, if the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver notifies the transmitter to increase the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold. l Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity.

9-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

Parameter ATPC Automatic Threshold Enable Status

Value Range Enabled, Disabled

Default Value Enabled

Description l 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. l The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.

NOTE

l Set ATPC parameters consistent at the two sides of a hop of microwave link. l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes. l It is recommended that you disable the ATPC function for areas where fast fading is severe. l To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC lower threshold 10 dB or more higher than the receiver sensitivity. l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely manner and the interference to adjacent systems can be reduced. l It is recommended that you set the ATPC adjustment step to 5 dB. l In the case of hybrid radio links, the automatic ATPC threshold is recommended. In the case of SDH/PDH radio links, the automatic ATPC threshold is recommended or you can make adjustment according to multipath fading situation.

9.4 Creating an XPIC Workgroup


When two IF boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The XPIC Enabled parameter must be set to Enabled for the IF boards.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-11

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Context
l Relation with the 1+1 Protection Configuration: The two IF boards in an XPIC working group cannot be configured into one 1+1 protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1 protection groups. Relation with the N+1 Protection: Each member of an XPIC working group can work as the working channel or the protection channel of the N+1 protection. Relation with the ATPC Feature: The transmit power of the two ODUs that are in an XPIC working group should be the same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value for the IFX boards that are in an XPIC working group.

l l

Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click New. Step 4 In the dialog displayed box, Set the parameters for the XPIC workgroup. For RTN 600 NEs:

NOTE

l When CCDP is applied to the STM-1 microwave links, the IFX/IFX2 boards must be installed and the XPIC function must be enabled. l An XPIC working group must be configured to ensure that the XPIC working group is configured with the same working mode, transmission frequency, transmit power, and ATPC attributes. l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group adopt the same T/R spacing.

9-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

Step 5 Click OK. ----End

Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU Configuration tab page if the used ODU supports two T/R spacings.

9.5 Configuring the Hybrid/AM Attribute


The Hybrid microwave supports the transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Hence, the Hybrid microwave ensures the reliable transmission of the E1 services and flexible transmission of the Ethernet services whose bandwidth is large and changes dynamically.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 Select the target Hybrid IF board in the NE Explorer. Then, choose Configuration > Hybrid/ AM Configuration from the Function Tree. Step 2 Click Query. Step 3 Set the parameters related to the Hybrid/AM function.

Step 4 Optional: In the case of a card that supports the function of enabling E1 priority, click the Advanced Attributes tab to set the minimum number of E1 services in different modulation modes and check the bandwidth of data services. Step 5 Click Apply. ----End

9.6 Hop Management


The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time. 9.6.1 Introduction to the Hop Management Based on Hop management, the system can simultaneously display the information of the two ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop management supports the functions such as the setting and query of the intermediate frequency (IF) and radio frequency (RF) information, and the configuration of services and protection. 9.6.2 Starting HOP Management Based on HOP management, the system can simultaneously display the information of the two ends of a link. By selecting an IF card, you can switch to the radio link in the corresponding
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-13

9 Configuring Radio Links

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

direction and search out the peer NE quickly. The HOP management integrates all functions in one GUI, in which a user can perform all maintenance operations.

9.6.1 Introduction to the Hop Management


Based on Hop management, the system can simultaneously display the information of the two ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop management supports the functions such as the setting and query of the intermediate frequency (IF) and radio frequency (RF) information, and the configuration of services and protection. The Hop management function is used to view and set the information based on a pair of equipment, one of which transmits signals and the other receives signals. In the case of the radio equipment, the configuration parameters are complicated. You need to ensure the consistency of parameters between the equipment at the two ends of a radio link. By using the Hop management function, you can perform operations on the equipment at the two ends of a link at the same time. This facilitates the parameter configuration. In Figure 9-2, a radio link represents a hop. Figure 9-2 Radio link

The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time. This ensures the consistency of configuration data between NEs at the two ends.

9.6.2 Starting HOP Management


Based on HOP management, the system can simultaneously display the information of the two ends of a link. By selecting an IF card, you can switch to the radio link in the corresponding direction and search out the peer NE quickly. The HOP management integrates all functions in one GUI, in which a user can perform all maintenance operations.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The radio link must be created.

Procedure
Step 1 In the case of RTN 600 and RTN 900 V1R2 NEs. 1. 2.
9-14

In the NE Explorer, select an NE and choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

9 Configuring Radio Links

3. 4.

Select the IF board, right-click, and choose HOP Management from the shortcut menu. In the HOP Management window, choose Configuration > Link Configuration from the Function Tree. Then, click the IF/ODU Configuration tab. Double click the NE on the main topology, select the IF board in the NE panel, right-click, and choose HOP Management from the shortcut menu. In the NE Explorer, select an NE and choose Configuration > Microwave Link Configuration from the Function Tree.

Step 2 In the case of RTN 900 V1R1 NEs 1. 2.

Step 3 In the IF/ODU Configuration tab, set the related parameters.

CAUTION
Modifying the value of Transmit Frequency interrupts the link. Exercise caution when you perform this operation. Step 4 Click Apply. ----End

Issue 02 (2010-09-24)

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

9-15

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

10 Configuring Board 1+1 Protection

10

Configuring Board 1+1 Protection

About This Chapter


BPS is a protection mode based on the board. BPS requires two boards: active and standby. When a link is down or a hardware failure is detected on the active board at any port, services are switched from the active board to the protection board. In this way, services are protected. 10.1 Querying Board 1+1 Protection Group After a redundant board is created, the equipment automatically configures a board 1+1 protection group. You can view the configuration information of the protection group. 10.2 Verifying the Board 1+1 Protection Switching By using the U2000, you can perform or clear protection switching for a board. During deployment and commissioning, you can perform switching to test whether the board protection switching works properly. In fault maintenance, you can perform this operation to locate faults.

Issue 02 (2010-09-24)

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

10-1

10 Configuring Board 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

10.1 Querying Board 1+1 Protection Group


After a redundant board is created, the equipment automatically configures a board 1+1 protection group. You can view the configuration information of the protection group.

Prerequisite
You must be an NM user with "NE monitor" authority or higher.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to query the configuration of the board 1+1 protection group. ----End

10.2 Verifying the Board 1+1 Protection Switching


By using the U2000, you can perform or clear protection switching for a board. During deployment and commissioning, you can perform switching to test whether the board protection switching works properly. In fault maintenance, you can perform this operation to locate faults.

Prerequisite
l l l You must be an NM user with "NE operator" authority or higher. The 1+1 board protection group must be available. The protection board works properly.

Context

CAUTION
If the protection board is abnormal, services may be interrupted when you perform switching.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to view the active board and the current working board. Step 3 Select a 1+1 protection group and click Working/Protection Switching. The Confirm dialog box is displayed. Step 4 Click OK. The Operation Result dialog box is displayed. Step 5 Click Close.
10-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

10 Configuring Board 1+1 Protection

Step 6 Click Query to refresh the switching status of the 1+1 protection group.
NOTE

In the case of SCC protection pair, you can query standby status of the SCC board.

----End

Issue 02 (2010-09-24)

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

10-3

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

11

Configuring the IF 1+1 Protection

About This Chapter


The IF 1+1 protection includes the 1+1 HSB protection, 1+1 FD protection, and 1+1 SD protection. 11.1 1+1 HSB 1+1 HSB is a configuration mode of 1+1 protection. The equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection by using the 1+1 HSB. 11.2 1+1 FD 1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same service signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 11.3 1+1 SD 1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same RF signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 11.4 Creating IF 1+1 Protection If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group. 11.5 Modifying the Parameters of IF 1+1 Protection The working mode and other parameters of the protection group can be modified.

Issue 02 (2010-09-24)

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

11-1

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11.1 1+1 HSB


1+1 HSB is a configuration mode of 1+1 protection. The equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection by using the 1+1 HSB. 11.1.1 Feature Description This topic describes the 1+1 HSB protection through its application. 11.1.2 Availability The 1+1 HSB feature requires the support of the applicable equipment and boards. 11.1.3 Relation with Other Features The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 11.1.4 Realization Principle The realization principle of the 1+1 HSB for the Hybrid microwave is different from the realization principle of the 1+1 HSB for the SDH/PDH microwave. 11.1.5 Planning Guide In the case of the radio links whose transmission performance is slightly affected by multipath fading, it is recommended that you adopt the 1+1 HSB protection configuration.

11.1.1 Feature Description


This topic describes the 1+1 HSB protection through its application. Figure 11-1 shows application of the 1+1 HSB protection. Figure 11-1 1+1 HSB protection
Main channel Main channel

MODEM Service MODEM

Transmitter

Transmitter

MODEM Service

Transmitter

Transmitter

MODEM

Standby channel

Standby channel

In the case of the 1+1 HSB protection configuration, the main channel of the transmit end transmits the RF signal to the opposite end. the main channel and standby channel of receive end received the same RF signal respectively. When the main channel if faulty, the service unit of receive end receives the signal from the standby channel. In this manner, the protection switching is realized.

11.1.2 Availability
The 1+1 HSB feature requires the support of the applicable equipment and boards.
11-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

Table 11-1 Availability of the 1+1 HSB feature Applicable Board IF0A/IF0B IF1A/IF1B IFX IFH2 RTN 620 Applicable Equipment RTN 605

Table 11-2 Availability of the 1+1 HSB feature Applicable Board IFE2 IF1 IFU2 IFX2 RTN 910/950 Applicable Equipment

11.1.3 Relation with Other Features


The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. l l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 HSB protection. The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IF boards in an XPIC working group cannot be configured into one 1+1 HSB protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 HSB protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1 HSB protection groups. The IF boards in a 1+1 HSB protection group cannot be configured to provide the N+1 protection. The radio link with the 1+1 HSB configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 HSB protection.

l l l

11.1.4 Realization Principle


The realization principle of the 1+1 HSB for the Hybrid microwave is different from the realization principle of the 1+1 HSB for the SDH/PDH microwave.

Issue 02 (2010-09-24)

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

11-3

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11.1.4.1 SDH/PDH Microwave This topic considers the configuration with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave. 11.1.4.2 Hybrid Microwave This topic considers the configuration with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.

11.1.4.1 SDH/PDH Microwave


This topic considers the configuration with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave.

Before the Switching


Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main Cross-connect IF board board Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the cross-connect board. The cross-connect board transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF signal).

Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Main Cross-connect IF board board Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

11-4

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

In the receive direction: 1. 2. 3. 4. 5. The hybrid coupler splits the RF signal received from the antenna to two signals and sends them to both the main ODU and the standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board send the service signal to the cross-connect board. The cross-connect board selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.

After the Switching


Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Main Cross-connect IF board board Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)
Main ODU Main Cross-connect IF board board Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

After a 1+1 HSB switching: l In the receive direction, the cross-connect board selects the service signal from the standby IF board.

Issue 02 (2010-09-24)

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

11-5

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU does not send the RF signal).
NOTE

In the case of the RTN 605, the multiplexing sub-unit that is embedded in the IF unit replaces the cross-connect unit of the IDU 620 to realize the dual fed and selective receiving function.

11.1.4.2 Hybrid Microwave


This topic considers the configuration with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.

Before the Switching


Figure 11-6 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Cross-connect board Service board

Hybrid coupler Antenna

Standby ODU

Standby IF board

EMS6 board

In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal tin the VC-4 o the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by their corresponding IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

4.

5.

11-6

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. 6. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).

Figure 11-7 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect board Service board

Standby ODU

Standby IF board

EMS6 board

In the receive direction: 1. 2. 3. 4. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF board and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.

5.

6. 7.

Issue 02 (2010-09-24)

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

11-7

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

After the Switching


Figure 11-8 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect board Service board

Standby ODU

Standby IF board

EMS6 board

Figure 11-9 1+1 HSB realization principle (after the switching, in the transmit direction)
Main ODU Main IF board Cross-connect board Service board

Hybrid coupler Antenna

Standby ODU

Standby IF board

EMS6 board

After a 1+1 HSB switching: l In the receive direction: The analog IF signal received at the standby IF board is separated into the E1 service signal and Ethernet service signal by the MUX unit. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board. l In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and
11-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

the standby IF board send the analog IF signal to the main ODU and the standby ODU. The standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).
NOTE

l The two built-in IF units of theRTN 605 realize the functions of two IF boards of the RTN 620.

11.1.5 Planning Guide


In the case of the radio links whose transmission performance is slightly affected by multipath fading, it is recommended that you adopt the 1+1 HSB protection configuration.

Procedure
Step 1 Plan the parameters relevant to the protection configuration. l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. l It is recommended that you enable the reverse switching. If reverse switching is enabled, and both the main IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end. l In the case of the RTN 620, although the 1+1 HSB protection has no restriction on the slot of the IF board, it is recommended that you install a pair of main and standby IF boards in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). ----End

11.2 1+1 FD
1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same service signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 11.2.1 Feature Description This topic describes the 1+1 FD protection through its application. 11.2.2 Availability The 1+1 FD feature requires the support of the applicable equipment and boards. 11.2.3 Relation with Other Features The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 11.2.4 Realization Principle The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization principle of the 1+1 FD for the SDH/PDH microwave. 11.2.5 Planning Guide If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD protection configuration.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-9

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11.2.1 Feature Description


This topic describes the 1+1 FD protection through its application. Figure 11-10 shows the application of the 1+1 FD protection. Figure 11-10 1+1 FD protection
Main channel Main channel

MODEM

Transmitter F1 F1 F2

Transmitter

MODEM

Service MODEM Transmitter

F2

Service Transmitter MODEM

Standby channel

Standby channel

In the case of the 1+1 FD protection configuration, the main channel and the standby channel of the receive end receive RF signals of different frequencies which from the transmit end respectively. When the quality of the microwave signal received by the main antenna is degraded, bit errors occur in the service on the main channel. The service unit then receives the service signal from the standby channel to protect the service. In addition, the 1+1 FD protection supports the 1+1 HSB protection switching.

11.2.2 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards. Table 11-3 Availability of the 1+1 FD feature Applicable Board IF0A/IF0B IF1A/IF1B IFX IFH2 RTN 620 Applicable Equipment RTN 605

Table 11-4 Availability of the 1+1 FD feature Applicable Board IFE2


11-10

Applicable Equipment RTN 910/950

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

Applicable Board IF1 IFU2 IFX2

Applicable Equipment

11.2.3 Relation with Other Features


The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. l l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 FD protection. The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IF boards in an XPIC working group cannot be configured into one 1+1 FD protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 FD protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1 FD protection groups. The IF boards in a 1+1 FD protection group cannot be configured to provide the N+1 protection. The radio link with the 1+1 FD configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 FD protection.

l l l

11.2.4 Realization Principle


The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization principle of the 1+1 FD for the SDH/PDH microwave. 11.2.4.1 SDH/PDH Microwave This topic considers the configuration with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave. 11.2.4.2 Hybrid Microwave This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.

11.2.4.1 SDH/PDH Microwave


This topic considers the configuration with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave.

Issue 02 (2010-09-24)

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

11-11

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Before the Switching


Figure 11-11 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Main ODU Main Cross-connect IF board board Service board

f2

Antenna

Standby ODU

Standby IF board

In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the cross-connect board. The cross-connect board transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively. The main ODU and the standby ODU transmit RF signals at different frequencies and send the signals to their respective antennas.

Figure 11-12 1+1 FD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

In the receive direction: 1. 2. 3. 4. 5. The antennas receive RF signals and send the signals to their respective ODUs. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The multiplex unit of the IF board sends the processed baseband signal to itself and to the multiplex unit of its paired board. The main IF board and the standby IF board select their own baseband signal. The cross-connect board selects the service signal from the main IF board and sends the signal to the service board.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

11-12

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

6.

The service board sends the service signal to the equipment at the opposite end.

After the Switching


Figure 11-13 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

After a 1+1 FD HSB switching: l l In the receive direction, the IF boards select their own service signal. The cross-connect board selects the signal from the standby IF board. In the transmit direction, no processing is required.

Figure 11-14 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

After a 1+1 FD HSM switching: l l In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.
NOTE

l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620. l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of the cross-connect board of the IDU 620.

Issue 02 (2010-09-24)

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

11-13

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11.2.4.2 Hybrid Microwave


This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.

Before the Switching


Figure 11-15 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board

f2 Antenna Standby ODU Standby IF board EMS6 board

In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna. The standby ODU transmits the RF signal at frequency f2 to the standby antenna.

4.

5.

6.

11-14

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

Figure 11-16 1+1 FD realization principle (before the switching, in the receive direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board

Antenna

f2

Standby ODU

Standby IF board

EMS6 board

In the receive direction: 1. 2. 3. The antennas receive RF signals at different frequencies and send the signals to their corresponding main ODU and standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF board and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.

4.

5.

6. 7.

Issue 02 (2010-09-24)

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

11-15

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

After the Switching


Figure 11-17 1+1 HSB realization principle (after the switching, in the transmit direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board

f2 Antenna Standby ODU Standby IF board EMS6 board

Figure 11-18 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board

Antenna

f2

Standby ODU

Standby IF board

EMS6 board

After a 1+1 FD HSB switching: l In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna and the standby ODU transmits the RF signal at frequency f2 to the standby antenna.
11-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

In the receive direction: The Hybrid microwave frame demultiplexed by the main IF board is transmitted to the standby IF board through the protection bus. The MUX unit of the main IF board receives the Hybrid microwave frame that is multiplexed by the main IF board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board.

Figure 11-19 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board

Antenna

f2

Standby ODU

Standby IF board

EMS6 board

After a 1+1 FD HSM switching: l l In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE

l The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.

11.2.5 Planning Guide


If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD protection configuration.

Procedure
Step 1 Plan the parameters relevant to the protection configuration.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-17

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. l The spacing between the emission frequency of the main ODU and that of the standby ODU should be greater than 56 MHz to prevent adjacent-channel interference. l In the case of the RTN 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). In the case of the RTN 605 , the active/standby relation of the IF unit is fixed. Hence, planning is not required. ----End

11.3 1+1 SD
1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same RF signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 11.3.1 Feature Description This topic describes the 1+1 FD protection through its application. 11.3.2 Availability The 1+1 SD feature requires the support of the applicable equipment and boards. 11.3.3 Relation with Other Features The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 11.3.4 Realization Principle The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization principle of the 1+1 SD for the SDH/PDH microwave. 11.3.5 Planning Guide In the case of the radio links whose transmission performance is significantly affected by multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.

11.3.1 Feature Description


This topic describes the 1+1 FD protection through its application. Figure 11-20 shows the application of the 1+1 SD protection. Figure 11-20 1+1 SD protection
Main channel
T1 T2 T1

Main channel
T2

MODEM Service MODEM

Transmitter

Transmitter

MODEM Service

Transmitter
T2 T1

Transmitter

MODEM

Standby channel

Standby channel

11-18

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

In the case of the 1+1 SD protection configuration, the two antennas at the receive end receive the same RF signals from the transmit end. When the quality of the microwave signal that is received by the main antenna is degraded, bit errors may occur in the service on the main channel. Due to the space diversity, the signal that is received by the standby antenna may not be degraded. In this case, the service unit receives the service from the standby receive channel to protect the service. In addition, the 1+1 SD protection supports the 1+1 HSB protection switching.

11.3.2 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards. Table 11-5 Availability of the 1+1 SD feature Applicable Board IF0A/IF0B IF1A/IF1B IFX IFH2 RTN 620 Applicable Equipment RTN 605

Table 11-6 Availability of the 1+1 SD feature Applicable Board IFE2 IF1 IFU2 IFX2 RTN 910/950 Applicable Equipment

11.3.3 Relation with Other Features


The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. l l The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 SD protection. The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IF boards in an XPIC working group cannot be configured into one 1+1 SD protection group, but the two IF boards in different XPIC working groups can be configured
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-19

Issue 02 (2010-09-24)

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

into one 1+1 SD protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1 SD protection groups. l l l The IF boards in a 1+1 SD protection group cannot be configured to provide the N+1 protection. The radio link with the 1+1 SD configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 SD protection switching.

11.3.4 Realization Principle


The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization principle of the 1+1 SD for the SDH/PDH microwave. 11.3.4.1 SDH/PDH Microwave This topic considers the configuration with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave. 11.3.4.2 Hybrid Microwave This topic considers the configuration with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the Hybrid microwave.

11.3.4.1 SDH/PDH Microwave


This topic considers the configuration with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave.

Before the Switching


Figure 11-21 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna Main ODU Main Cross-connect board IF board Service board

Antenna

Standby ODU

Standby IF board

In the transmit direction: 1. 2. 3. The service board sends the received service signal to the cross-connect board. The cross-connect board transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

11-20

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

4.

The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF signal).

Figure 11-22 1+1 SD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

In the receive direction: 1. 2. 3. 4. 5. 6. The antennas receive RF signals and send the signals to their respective ODUs. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The multiplex unit of the IF board sends the processed baseband signal to itself and to the multiplex unit of its paired board. The main IF board and the standby IF board select their own baseband signal. The cross-connect board selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.

After the Switching


Figure 11-23 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

Issue 02 (2010-09-24)

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

11-21

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 11-24 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna Main ODU Main Cross-connect IF board board Service board

Antenna

Standby ODU

Standby IF board

After a 1+1 SD HSB switching: l l In the receive direction, the IF boards select their own service signal. The cross-connect board selects the signal from the standby IF board. In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU does not send the RF signal).

Figure 11-25 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

After a 1+1 SD HSM switching: l l In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.
NOTE

l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620. l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of the cross-connect board of the IDU 620.

11.3.4.2 Hybrid Microwave


This topic considers the configuration with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the Hybrid microwave.
11-22 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

Before the Switching


Figure 11-26 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

EMS6 board

In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).

4.

5.

6.

Issue 02 (2010-09-24)

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

11-23

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 11-27 1+1 SD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

EMS6 board

In the receive direction: 1. 2. 3. The antennas receive RF signals and transmit the signals to their corresponding main ODU and standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the IF signal into the Hybrid microwave frame. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF board and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.

4.

5.

6. 7.

11-24

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

After the Switching


Figure 11-28 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

EMS6 board

Figure 11-29 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

EMS6 board

After a 1+1 SD HSB switching: l In the receive direction: The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby IF board. The cross-connect board receives the E1 service signal that is demultiplexed from the Hybrid microwave frame received at the standby IF board and cross-connects the E1 service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the standby IF board because the Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-25

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state. The Ethernet service port of the standby IF board is in LinkUp state. The main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the standby IF board and then transmit the modulated Hybrid microwave frame to the main ODU and the standby ODU respectively. The standby ODU transmits the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).

Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board

Antenna

Standby ODU

Standby IF board

EMS6 board

After a 1+1 SD HSM switching: l l In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE

The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.

11.3.5 Planning Guide


In the case of the radio links whose transmission performance is significantly affected by multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.

Procedure
Step 1 Plan the parameters relevant to the protection configuration. l There should be a height difference between the two antennas so that the dependence of the diversity-received microwave signals on the space is minimized. l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
11-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

l It is recommended that you enable the reverse switching. If reverse switching is enabled, and both the main IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end. l In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit is fixed. Hence, planning is not required. ----End

11.4 Creating IF 1+1 Protection


If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.

Background Information
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original services are not interrupted.

Precautions
The 18,2E1,3.5MHz,QPSK work mode does not support IF 1+1 protection.

Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002/V100R001C02 NEs. 1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box.

3. 1.

Click OK. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Microwave Link Configuration from the Function Tree.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-27

Step 2 In the case of RTN 900 V100R001C00 and RTN 900 V100R001C01 NEs.

Issue 02 (2010-09-24)

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

2. 3. 4.

Click the IF 1+1 Protection tab. Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box. Click OK.

----End

Postrequisite
l In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU. In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE

The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby ODU after you create an IF 1+1 protection group.

11.5 Modifying the Parameters of IF 1+1 Protection


The working mode and other parameters of the protection group can be modified.

Prerequisite
You must be an NM user with "NE operator" authority or higher.

Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > IF 1 +1 Protection from the Function Tree. Step 2 Modify the parameters of the IF 1+1 protection.

Step 3 Click Apply. ----End

11-28

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

11 Configuring the IF 1+1 Protection

Parameters
Parameter Working Mode Value Range HSB, FD, SD Default Value HSB Description l In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. l In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite 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 the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 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 planning information. Revertive Mode Revertive, NonRevertive Revertive l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l It is recommended that you use the default value.

Issue 02 (2010-09-24)

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

11-29

11 Configuring the IF 1+1 Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Parameter WTR Time(s)

Value Range 300 to 720

Default Value -

Description 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 It is recommended that you use the default value.

Enable Reverse Switching

Enable, Disable

Enable

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 It is recommended that you use the default value.

NOTE

Each of the following parameters should be set to the same value at the two ends of a microwave link: Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.

Postrequisite
l In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU. In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE

The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby ODU after you create an IF 1+1 protection group.

11-30

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

12

Configuring Network Level Protection

About This Chapter


The network level protection includes the linear MSP, SNCP protection, MPLS tunnel protection and LAG. 12.1 Basic Concept To configure the network-level protection, you need to master basic concepts. 12.2 Configuring N+1 Protection The N+1 protection refers to the protection configuration in which N working channels in a microwave direction share one protection channel. 12.3 Configuring Linear Multiplex Section Protection The linear MSP is applicable to point-to-point physical networks. The linear MSP provides protection for the services between two nodes at the multiplex section level. 12.4 Configuring Two-Fiber Bidirectional Ring MSP The two-fiber bidirectional ring MSP scheme is applicable to an SDH ring network of the STM-4 or higher level formed by fibers, and provides protection at the MS level for services between the nodes of a ring network. 12.5 Configuring Sub-Network Connection Protection The sub-network connection protection (SNCP) scheme protects the services that are across subnets. The subnet can be a chain, a ring, or a more complicated network. 12.6 Configuring MPLS Tunnel Protection When you configure an MPLS tunnel on a per-NE basis, you can configure 1+1 protection and 1:1 protection for the MPLS tunnel. You can also create an MPLS tunnel protection group, perform switching, and delete an MPLS tunnel protection group. 12.7 Ethernet Ring Protection Based on the traditional Ethernet mechanism, the Ethernet ring protection switching (ERPS) uses the ETH-OAM function and the ring automatic protection switching (R-APS) protocol to achieve fast protection switching on the Ethernet ring network. 12.8 Configuring Link Aggregation

Issue 02 (2010-09-24)

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

12-1

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link.

12-2

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

12.1 Basic Concept


To configure the network-level protection, you need to master basic concepts. 12.1.1 Multiplex Section Multiplex section protection (MSP) is a protection mode, which is commonly used to configure the protection. 12.1.2 MSP Protection Switching Priority MSP protection switching can be triggered by automatic switching conditions and external switching requests. Automatic switching is triggered by signal failure (SF) (for example, LOS, LOF, MS_AIS and B2OVER raised on the equipment) and signal degrade (SD) (for example, B2SD raised on the equipment). External switching is performed after you issue an external switching command, and thus brings a status change of the multiplex section. External switching requests include lockout, forced switching, manual switching, exercise switching, and clear of switching. 12.1.3 SNCP Protection Subnetwork connection protection (SNCP) is a type of 1+1 protection that uses single-ended switching. SNCP is mainly used to protect services across subnets. This function is dual fed and selective receiving. 12.1.4 N+1 Protection The N+1 protection is to use a standby channel to protect the services on N (N3) active channels. When the services on the active channel are normal, the standby channel can transmit extra services. When the receive end detects that the signal is unavailable, the receive end checks whether the standby channel is available and whether the standby channel is already occupied by the services that are switched from another active channel for protection. The N+1 protection has two protection schemes: single-NE N+1 protection and dual-NE N+1 protection. This section describes the typical networking of the two schemes.

12.1.1 Multiplex Section


Multiplex section protection (MSP) is a protection mode, which is commonly used to configure the protection. The SDH transmission system can be divided into four layers on a functional basis. From the bottom to the top layer, there is a physical layer, section layer, path layer and circuit layer. Among the four layers, the section layer is used to ensure the integrity of the signals transmitted between the nodes within an SDH network. The section layer consists of the regenerator section and the multiplex section. The regenerator section refers to the section between the regenerator section terminals (RSTs) of two pieces of equipment. The equipment contains two RSTs and the fibers in between. The multiplex section refers to the section between the multiplex section terminals (MSTs) of two pieces of equipment. The equipment contains two MSTs and the fibers in between. See Figure 12-1.

Issue 02 (2010-09-24)

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

12-3

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 12-1 Multiplex section schematic diagram

...

MST

RST

SPI

... ...
RS MS

SPI

RST

MST

...

SPI: SDH Physical Interface

RST: Regenerator Section Termination

MST: Multiplex Section Termination

Table 12-1 describes the commonly used MSP types. Table 12-1 MSP type Type 1+1 linear MSP Capacity The maximum service capacity is STM-N. Description This is a linear networking mode that provides 1+1 protection based on the MSP protocol for the services. If a fault occurs on the transmission link, this networking mode enables the working service to switch to the other link according to the MSP protocol. In this way, the service is protected. This is a linear networking mode that provides 1:N protection based on the MSP protocol for the services. If a fault occurs on the transmission link, this networking mode enables the working service to switch to the other link according to the MSP protocol. In this way, the service is protected.
NOTE N is the number of working links.

1:N(N3) linear MSP

The maximum service capacity is (1+N) STM-N.

12.1.2 MSP Protection Switching Priority


MSP protection switching can be triggered by automatic switching conditions and external switching requests. Automatic switching is triggered by signal failure (SF) (for example, LOS, LOF, MS_AIS and B2OVER raised on the equipment) and signal degrade (SD) (for example,
12-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

B2SD raised on the equipment). External switching is performed after you issue an external switching command, and thus brings a status change of the multiplex section. External switching requests include lockout, forced switching, manual switching, exercise switching, and clear of switching. For MSP protection, the following switching requests can bring a status change of the multiplex section. For their switching (or preemption) priorities, refer to Table 12-2.
NOTE

l The following table lists the switching priorities in a descending order, that is, LP_S (SF_P) has the highest priority, and NR has the lowest. The requests of lockout, forced switching, manual switching and exercise switching can be cleared as required. l For LP_S (SF_P), the lockout of protection is available for only the span instead of the ring. LP_S and SF_P have the same priority, and perform the same action on both the protocol and service. LP_S is triggered by an external command, and SF_P is triggered by the protection channel failure in a four-fiber ring. l The span switching has a higher priority than the ring switching. l External commands are issued on the U2000. After a command is executed, the NE keeps this request until the command is cleared or is preempted by another command of a higher priority. If there is a switching request of a higher priority in the network, the external command cannot be executed, and thus the NE loses this external command request.

Table 12-2 Preemptible relation of priorities of MSP protection switching No. 1 Switching Request LP_S(SF_P) Description Span lockout Cause SF in the protection channel of a fourfiber ring or the issue of an external command Issue of an external command Issue of an external command SF in the working channel of a span on a four-fiber ring SF in the working channel of a fourfiber or two-fiber ring SD in the protection channel of a fourfiber or two-fiber ring SD in the working channel of a span on a four-fiber ring
12-5

2 3 4

FS_S FS_R SF_S

Forced switching of a span Forced switching of a ring SF of a span

SF_R

SF of a ring

SD_P

SD of the protection channel

SD_S

SD of a span

Issue 02 (2010-09-24)

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

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

No. 8

Switching Request SD_R

Description SD of a ring

Cause SD in the working channel of a fourfiber or two-fiber ring Issue of an external command Issue of an external command Status request during a switching Issue of an external command Issue of an external command Reverse request during a switching Reverse request during a switching

9 10 11 12 13 14 15 16

MS_S MS_R WTR EXER_S EXER_R RR_S RR_R NR

Manual switching of a span Manual switching of a ring Wait-to-restore Exercise switching of a span Exercise switching of a ring Reverse request of a span Reverse request of a ring No request

12.1.3 SNCP Protection


Subnetwork connection protection (SNCP) is a type of 1+1 protection that uses single-ended switching. SNCP is mainly used to protect services across subnets. This function is dual fed and selective receiving.

Principle
The transmit end of an SNCP service transmits two service sources, and the receive end checks the service sources and selectively receives one. In this way, the service is protected. Hence, SNCP is dual fed and selective receiving, which is similar to path protection (PP). The difference between the SNCP and PP is about the specific implementation. When a service is selectively received at the receive end, in path protection, the tributary board verifies the selective receiving. In SNCP protection, the cross-connect board verifies the selective receiving. Hence, SNCP can protect services on the line, and PP protects only services on the local tributary board.

Subnet-Related Concepts
The definitions in ITU-T G.805 are as follows: l Subnetwork: A topological component used to effect routing of specific characteristic information.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

12-6

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

l l

Subnetwork connection: A "transport entity" that transfers information across a subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork. Subnetwork connection protection: A protection type that is modeled by a sublayer that is generated by expanding the "subnetwork" "connection point".

Implementation Principle
l Service pair: SNCP service pair is the service structure that consists of a working source, a protection source, and a service sink. See Figure 12-2. Figure 12-2 SNCP service pair

Working source

Protection source

Service sink

SNCP service is from line to line. A service that is added to and dropped from the local tributary board is not an SNCP service and an SNCP service pair cannot be generated. See Figure 12-3. Figure 12-3 SNCP service
SCC Issue data/ Collect data Cross-connect board Intra-board communication Intra-board communication

Line board

Line board

Check point: In an SNCP service pair, the status of the sink node is not checked. The two source nodes are two check points of the protection group. The line board of the corresponding service source checks the status of a check point (SF, SD, or Normal). Check point migration: An SNCP service pair usually has two check points. When a network contains SNCP and MSP, several types of protection exists. Hence, some standby check points are added accordingly. The line board enables the standby check point
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12-7

Issue 02 (2010-09-24)

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

according to a command, and disables the original check point to realize migration of the check point. l SNCP service number: It uniquely identifies a service pair. The SNCP service number information is saved to the SCC, cross-connect board, and line board. The SNCP protection switching on the line board and cross-connect board handles according to SNCP service number. Hence, ensure that the SNCP service number on the line board is consistent with that on the cross-connect board. Condition of generating an SNCP service pair: The node attributes must contain or imply the SNCP attribute. The service must across rings. SCC board side: The SCC verifies the SNCP service, analyzes service route, and issues the configuration data. The tasks contain setting check points, issuing SNCP service attribute data, collecting the SNCP service status from the cross-connect board, and reporting the SNCP service status. Cross-connect board side: The cross-connect board collects the SNCP service status from the line board, realizes the switching process of the service source, and reports changes of the SNCP service status to the SCC. Line board side: The line board mainly monitors the SNCP service and periodically reports the service monitoring status to the cross-connect board. When the service status changes, the line board notifies the cross-connect board of the change in real time. Service flow: The flow of the SNCP service is the flow that the system configures the service. Because of the special dual fed and selective receiving attribute, SNCP attribute must be specified during service configuration.

l l

SNCP Protection Parameters


Table 12-3 lists the parameters of the SNCP protection. Table 12-3 SNCP parameters Protection Type Revertive Mode Switching Time Default WTR Time Switching Condition (Trigger by Any One Condition) R_LOS R_LOF AU_LOP TU_LOP MS_AIS TU_AIS HP_UNEQ HP_TIM B2_EXC B3_EXC B3_SD BIP_EXC BIP_SD
Issue 02 (2010-09-24)

SNCP

Revertive Non-revertive

<= 50 ms <= 50 ms

600s -

12-8

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

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

12.1.4 N+1 Protection


The N+1 protection is to use a standby channel to protect the services on N (N3) active channels. When the services on the active channel are normal, the standby channel can transmit extra services. When the receive end detects that the signal is unavailable, the receive end checks whether the standby channel is available and whether the standby channel is already occupied by the services that are switched from another active channel for protection. The N+1 protection has two protection schemes: single-NE N+1 protection and dual-NE N+1 protection. This section describes the typical networking of the two schemes. l l You need to configure the line board whose rate is at the STM-1 for the N+1 protection. Protection schemes: Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the protection. Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE

The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected, every two ODUs are installed on a combiner and then the combiner is connected to the antenna.

Single-NE N+1 Protection


Take the 2+1 as an example.
Protect IF F A N SL1 PXC PXC IF IF SD1 SCC Add/Drop Services ODU ODU ODU ODU Dual-Polarized Antennas ODU F A N ODU Protect IF SL1 PXC PXC Add/Drop Services IF IF SD1 SCC

The realization principles of the 2+1 protection are as follows: l l l A standby channel is used to protect the services on two active channels. Line board: The rate level of the line board should be STM-1. Others: The SCC board and the integrated power, cross-connect and clock (PXC) board are required.

Dual-NE N+1 Protection


Take the 3+1 as an example.

Issue 02 (2010-09-24)

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

12-9

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

IF F A N IF PXC PXC SD1 SCC

ODU Secondary NE ODU Dual-Polarized Antennas

ODU ODU F A N PXC PXC

IF IF SD1 SCC

Fiber Interconnection SD1 F A N SD1 PXC PXC IF IF SD1 SCC ODU ODU

Fiber Interconnection ODU SD1 F A N SD1 PXC PXC IF IF SD1 SCC

Primary NE

ODU

Add/Drop Services

Add/Drop Services

The realization principles of the 3+1 protection are as follows: l A standby channel is used to protect the services on three active channels. The IF 3+1 protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on the primary NE. Line board: The line board should support the interaction between the primary and secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards are needed for adding and dropping services. Others: The SCC board and the integrated power, cross-connect and clock (PXC) board are required.

12.2 Configuring N+1 Protection


The N+1 protection refers to the protection configuration in which N working channels in a microwave direction share one protection channel. 12.2.1 Feature Description This topic considers the application of the N+1 protection as an example to describe the N+1 protection. 12.2.2 Availability The N+1 protection feature requires the support of the applicable equipment and boards. 12.2.3 Realization Principle The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1 protection protocol is similar to the 1:N linear multiplex section protection protocol. 12.2.4 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the N +1 protection mode. An example is provided as additional information to help understand the configuration.

12-10

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

12.2.1 Feature Description


This topic considers the application of the N+1 protection as an example to describe the N+1 protection. The N+1 protection realizes protection for microwave channels. The IF board, ODU, and radio link on the working channel can be protected through the N+1 protection. The N+1 protection provides N working channels and one protection channel. When the working channel becomes faulty, the normal services on the working channel can be switched to the protection channel for transmission. When the working channel is restored to normal, the protection channel can transmit the extra services. Figure 12-4 shows the application of the N+1 protection. Figure 12-4 N+1 protection
Site A Normal service 1 Working channel 1 Site B Normal service1

...
Normal service N Extra service

Working channel N Protection channel

...
Normal service N Extra service

Protection switching Site A Normal service 1 Working channel 1 Site B Normal service1

...
Normal service N Extra service

Working channel N Protection channel

...
Normal service N Extra service

l l

You need to configure the line board whose rate is at the STM-1 for the N+1 protection. Protection schemes: Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the protection. Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE

The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected, every two ODUs are installed on a combiner and then the combiner is connected to the antenna.

Issue 02 (2010-09-24)

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

12-11

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Single-NE N+1 Protection


Take the 2+1 as an example.
Protect IF F A N SL1 PXC PXC IF IF SD1 SCC Add/Drop Services ODU ODU ODU ODU Dual-Polarized Antennas ODU F A N ODU Protect IF SL1 PXC PXC Add/Drop Services IF IF SD1 SCC

The realization principles of the 2+1 protection are as follows: l l l A standby channel is used to protect the services on two active channels. Line board: The rate level of the line board should be STM-1. Others: The SCC board and the integrated power, cross-connect and clock (PXC) board are required.

Dual-NE N+1 Protection


Take the 3+1 as an example.
IF F A N IF PXC PXC SD1 SCC ODU Dual-Polarized Antennas ODU Secondary NE ODU ODU F A N PXC PXC IF IF SD1 SCC

Fiber Interconnection SD1 F A N SD1 PXC PXC IF IF SD1 SCC ODU ODU

Fiber Interconnection ODU SD1 F A N SD1 PXC PXC IF IF SD1 SCC

Primary NE

ODU

Add/Drop Services

Add/Drop Services

The realization principles of the 3+1 protection are as follows: l A standby channel is used to protect the services on three active channels. The IF 3+1 protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on the primary NE.

12-12

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

Line board: The line board should support the interaction between the primary and secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards are needed for adding and dropping services. Others: The SCC board and the integrated power, cross-connect and clock (PXC) board are required.

12.2.2 Availability
The N+1 protection feature requires the support of the applicable equipment and boards. Table 12-4 Availability of the N+1 protection feature Applicable Board IF1A/IF1B IFX Applicable Equipment RTN 620

Table 12-5 Availability of the N+1 protection feature Applicable Board IFU2 IFX2 Applicable Equipment RTN 910/950

NOTE

The Hybrid microwave does not support the N+1 protection.

12.2.3 Realization Principle


The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1 protection protocol is similar to the 1:N linear multiplex section protection protocol. 12.2.3.1 2+1 Protection Configuration In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize protection switching. 12.2.3.2 3+1 Protection Configuration In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group to realize protection switching and the secondary NE forms two STM-1 REGs to realize transparent transmission of byte K.

12.2.3.1 2+1 Protection Configuration


In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize protection switching.
NOTE

The following describes the switching principle of the 2+1 protection as an example.

Issue 02 (2010-09-24)

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

12-13

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 12-5 Realization principle of 2+1 protection (before the switching)


PXC 4-SD1-1 5-IF1B-1 15-ODU

6-SL1-1

7-IF1B-1

17-ODU

4-SD1-2

8-IF1B-1

18-ODU

Working channel

Protection channel

Figure 12-6 Realization principle of 2+1 protection (after the switching)


PXC 4-SD1-1 5-IF1B-1 15-ODU

6-SL1-1

7-IF1B-1

17-ODU

4-SD1-2

8-IF1B-1

18-ODU

Working channel

Protection channel

In this example, port 1 of the IF1B board in slot 5, port 1 of the IF1B board in slot 7, and port 1 of the IF1B board in slot 8 form a 2+1 protection group. When a working channel fails, the switching principle of the 2+1 protection configuration is as follows: 1. 2. Before the switching, the NE sends and receives normal traffic signals on the working channel, and sends and receives extra traffic signals on the protection channel. On detecting that the signals on a working channel fail (for example, the IF1B board in slot 5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCC board. The SCC board controls the PXC board to realize the transmission of the working traffic signals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1B board in slot 8). The SCC board also interacts with the NE on the opposite side through byte K to enable the NE on the opposite side to perform synchronous switching.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

3.

12-14

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management
NOTE

12 Configuring Network Level Protection

The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP protocol. For details, see Realization Principle of 1:N Linear MSP.

12.2.3.2 3+1 Protection Configuration


In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group to realize protection switching and the secondary NE forms two STM-1 REGs to realize transparent transmission of byte K.
NOTE

The following describes the switching principle of the 3+1 protection as an example.

Figure 12-7 Realization principle of the 3+1 protection (before the switching)
Primary NE PXC 6-SD1-1 5-IF1B-1 15-ODU

6-SD1-2

7-IF1B-1

17-ODU

8-SD1-1

4-SD1-1

8-SD1-2

4-SD1-2

Secondary NE PXC 4-SD1-1 5-IF1B-1 15-ODU

4-SD1-2

7-IF1B-1

17-ODU

Working channel

Protection channel

Issue 02 (2010-09-24)

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

12-15

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 12-8 Realization principle of the 3+1 protection (after the switching)
Primary NE PXC 6-SD1-1 5-IF1B-1 15-ODU

6-SD1-2

7-IF1B-1

17-ODU

8-SD1-1

4-SD1-1

8-SD1-2

4-SD1-2

Secondary NE PXC 4-SD1-1 5-IF1B-1 15-ODU

4-SD1-2

7-IF1B-1

17-ODU

Working channel

Protection channel

In this example, port 1 of the IF1B board in slot 5 of the primary NE, port 1 of the IF1B board in slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE form a 3+1 protection group. An REG is established between port 1 of the IF1B board in slot 5 of the secondary NE and port 1 of the SD1 board in slot 4 of the secondary NE. Another REG is established between port 1 of the IF1B board in slot 7 of the secondary NE and port 2 of the SD1 board in slot 4 of the secondary NE. When a working channel fails, the switching principle of the 3+1 protection configuration is as follows: 1. Before the switching, the primary NE sends and receives normal traffic signals on the working channel, and sends and receives extra traffic signals on the protection channel. The secondary NE works as an REG to transparently transmit VC signals and multiplex section overheads. On detecting that the signals on a working channel fail (for example, the IF1B board in slot 5 detects that an MW_LOF alarm is generated on port 1), an IF board of the secondary NE inserts the MS_AIS alarm and transparently transmits the multiplex section overheads and VC signals to port 1 of the SD1 board in slot 4 of the primary NE through port 1 of the SD1 board in slot 4 of the secondary NE.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2010-09-24)

2.

12-16

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

3. 4.

On detecting the MS_AIS alarm, the SD1 board in slot 4 of the primary NE reports the alarm to the SCC board. The SCC board controls the PXC board to realize the transmission of the working traffic signals (port 1 of the SD1 board in slot 8) on the protection channel (port 2 of the SD1 board in slot 4). The SCC board also interacts with the NE on the opposite side through byte K to enable the NE on the opposite side to perform synchronous switching. When the primary NE exchanges byte K with the NE on the opposite side, the secondary NE always transparently transmits byte K because byte K belongs to the multiplex section overheads.
NOTE

l In this example, the working channels of the secondary NE fail. If the working channels of the primary NE fail, the IF board directly reports the alarm to the SCC board to trigger the protection switching. l The REG formed by the secondary NE is slightly different from an ordinary REG. The REG formed by the secondary NE does not insert an AU_AIS alarm but inserts an MS_AIS alarm to trigger the N+1 protection switching when an MW_LOF alarm or a regenerator section alarm (for example, R_LOS, R_LOC, and R_LOF) is generated. l The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP protocol. For details, see Realization Principle of 1:N Linear MSP.

12.2.4 Configuration Guide


This topic describes the configuration flow and the corresponding configuration tasks of the N +1 protection mode. An example is provided as additional information to help understand the configuration. 12.2.4.1 Configuration Flow This topic describes the configuration flow for the N+1 protection mode. 12.2.4.2 Creating REGs In the case of the 3+1 protection, you need to configure REGs for the secondary NE. 12.2.4.3 Creating an N+1 Protection Group When the OptiX RTN NE transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration. 12.2.4.4 Enabling the N+1 Protection Control Protocol When the N+1 protection control protocol is in the disabled status, if you want to restore the normal protection function, you need to enable the N+1 protection control protocol. 12.2.4.5 Verifying the N+1 Protection Switching On the U2000, you can perform the external switching commands such as the clear switching, lockout of switching and forced switching, to meet the requirements in certain scenarios.

12.2.4.1 Configuration Flow


This topic describes the configuration flow for the N+1 protection mode.

Issue 02 (2010-09-24)

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

12-17

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Figure 12-9 Configuration flow for the N+1 protection mode


Start 1

Create an N+1 protection group

Is the 3+1 protection mode used? Yes 2 Create REGs

No

End

Table 12-6 Description of the configuration flow of the N+1 protection mode Number 1 Description l In the case of the 3+1 protection, an N+1 protection group needs to be created only for the primary NE. l For the configuration process, see 12.2.4.3 Creating an N+1 Protection Group. 2 l Create REGs between two IF boards of the secondary NE and two ports of the SD1 board that is connected to the primary NE. l For the configuration process, see 12.2.4.2 Creating REGs.

Relation with other features


l l l The members of an N+1 protection group cannot be configured with the 1+1 protection. Each member of an XPIC working group can work as the working channel or the protection channel of the N+1 protection. The radio link with the N+1 protection configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source.

12.2.4.2 Creating REGs


In the case of the 3+1 protection, you need to configure REGs for the secondary NE.

12-18

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface board that is connected to the primary NE must be created. The IF boards must work in the STM-1 mode.

Context
In the case of the 3+1 protection, you need to two configure REGs for the secondary NE.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection Configuration > REG Configuration from the Function Tree. Step 2 Click Create. The system displays the Create REG dialog box. Step 3 Set the SD Enabled parameter. Step 4 Set the slot mapping relation. 1. 2. In Slot Mapping Direction, select West Line. In Select Mapping Mode, select the line port to which the west line corresponds and click . 3. 4. In Slot Mapping Direction, select East Line. In Select Mapping Mode, select the line port to which the east line corresponds and click .

Issue 02 (2010-09-24)

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

12-19

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 5 Click OK. Step 6 Repeat Step 2 to Step 5, Create another REG.

----End

12-20

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

Parameters
Parameter SD Enabled Value Range Enabled, Disabled Default Value Enabled Description l When this parameter is set to Enabled, the REG inserts an MS-AIS alarm when a B2_SD alarm is generated. l It is recommended that you use the default value. Slot Mapping Relation It is recommended that you map the IF port as West Line and the port of the STM-1 optical/electrical interface board as East Line.

12.2.4.3 Creating an N+1 Protection Group


When the OptiX RTN NE transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be configured with 3+1 protection) must be created. The IF boards must work in the STM-1 mode.

Background Information
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the original services are not interrupted.
NOTE

It is recommended that you configure the channels in the ACAP mode.

Procedure
Step 1 Select a navigation path: l In the NE Explorer, select the NE from the Function Tree and then choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. l In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Protection Configuration > N+1 Protection from the Function Tree. Step 2 Click Create. The system displays the Create an N+1 Protection Group dialog box. Step 3 Set the attributes of the N+1 protection group.
Issue 02 (2010-09-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12-21

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select Working Unit. In Select Mapping Mode, select the line port to which a working channel corresponds and click 3. 4. 5. .

Repeat Step 4.2 to select the line ports to which other working channels correspond. In Select Mapping direction, select Protection Unit. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .

NOTE

l Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. l It is recommended that you use SD as a switching condition.

Step 5 Click OK. ----End

Parameters
Parameter WTR Time(s) Value Range 300 to 720 Default Value 600 Description l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that you use the default value.

12-22

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

Issue 02 (2010-09-24)

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

12 Configuring Network Level Protection

Parameter SD enable

Value Range Enabled, Disabled

Default Value Enabled

Description l When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that you use the default value.

Slot Mapping Relation

l In the case of 2+1 protection, map two IF ports as Working Unit and map the remaining IF port as Protection Unit. l In the case of the 3+1 protection, it is recommended that you map the two IF ports and the first line port of the STM-1 optical/electrical interface board that is connected to the secondary NE as Working Unit, and map the other line port as Protection Unit.

NOTE

The N+1 protection groups of the equipment at both ends must have the same attributes.

12.2.4.4 Enabling the N+1 Protection Control Protocol


When the N+1 protection control protocol is in the disabled status, if you want to restore the normal protection function, you need to enable the N+1 protection control protocol.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. Protocol Status of the N+1 protection must be Disabled.

Context
After maintaining the equipment, enable the N+1 protection control protocol, to restore the normal protection function of the equipment.

Procedure
Step 1 In the NE Explorer, select Link Configuration from the Function Tree, click the N+1 Protection tab. Select the N+1 protection group and click Start Protocol. Step 2 A prompt is displayed indicating that the operation is successful. Click OK. Step 3 Click Query and the current protocol status is displayed. ----End

Issue 02 (2010-09-24)

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

12-23

12 Configuring Network Level Protection

iManager U2000 Unified Network Management System Operation Guide for RTN NE Management

Postrequisite
NOTE

Before maintaining the equipment, disable the N+1 protection control protocol, to avoid the protection switching caused by the equipment maintenance.

l l l

In the NE Explorer, select Configuration > N+1 Protection from the Function Tree. Select the IF N+1 protection group and click Stop Protocol. A prompt is displayed indicating that the operation is successful. Click OK. Click Query and the current protocol status is displayed.

12.2.4.5 Verifying the N+1 Protection Switching


On the U2000, you can perform the external switching commands such as the clear switching, lockout of switching and forced switching, to meet the requirements in certain scenarios.

Prerequisite
l l You must be an NM user with "NE operator" authority or higher. The N+1 protection group must be created.

Context
The external switching commands are as follows: clear switching, lockout of protection, forced switching to protection, manual switching to protection, and exercise switching. l l Clear switching: This command can be used to clear the forced switching, manual switching, lockout of switching, and exercise switching. Lockout of protection: No service, including the normal and extra services, is allowed to be switched from the