Commissioning and Configuration Guide(V100R003C01_01)

OptiX OSN 1800 Compact Multi-Service Edge Optical Transport Platform V100R003C01

Commissioning and Configuration Guide Issue

01

Date

2011-10-20

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2011-10-20)

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

i

OptiX OSN 1800 Compact Multi-Service Edge Optical Transport Platform Commissioning and Configuration Guide

About This Document

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

Version

OptiX OSN 1800

V100R003C01

iManager U2000

V100R006C00

iManager U2000 Web LCT

V100R006C00

Intended Audience The intended audiences of this document are: l

Installation and Commissioning Engineer

l

Data Configuration Engineer

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

Description Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results.

Issue 01 (2011-10-20)


ii


Symbol

About This Document

Description Indicates a tip that may help you solve a problem or save you time. Provides additional information to emphasize or supplement important points of the main text.

GUI Conventions Convention

Description

Boldface

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

>

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

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

Updates in Issue 01 (2011-10-20) Based on Product Version V100R003C01 This issue is the first official release for OptiX OSN 1800 V100R003C01. Compared with the OptiX OSN 1800 V100R003C00, the manual of this issue provides the following updates. Update

Description

Configuring Protection Schemes

l Configuring ODUk SNCP Protection is added.

Configuring Board Parameters

l LDX Parameters is add.

Basic Concepts

l Board Model is added.

l Configuring Port Protection is modified.

l ODUflex is added. Configuring Services on Boards Issue 01 (2011-10-20)

l LQM Service Configuration is added. l LDGF2 Service Configuration is added.


iii


Update

Description

Testing Protection Switching

l Testing ODUk SNCP Switching is added. l Testing SNCP Switching is modified.

Whole manual

Some bugs are fixed.

About This Document

l Testing Port Protection Switching is modified.

Updates in Issue 03 (2011-08-20) Based on Product Version V100R003C00 This issue is the third official release for OptiX OSN 1800 V100R003C00. Compared with the issue 02, the manual of this issue for OptiX OSN 1800 V100R003C00 provides the following updates. Update

Description

Whole manual


Updates in Issue 02 (2011-03-15) Based on Product Version V100R003C00 This issue is the second official release for OptiX OSN 1800 V100R003C00. Compared with the issue 01, the manual of this issue for OptiX OSN 1800 V100R003C00 provides the following updates. Update

Description

Whole manual

l The topic "Commissioning and Configuring the Network" is replaced with Basic Configurations. l Some contents in the topic "Commissioning and Configuring the Network" are added to the new topic Service Configurations. l Some contents in the topic "Commissioning and Configuring the Network" are added to the new topic Follow-up Operations (Including Data Backup). l The ELOM board is added.

Service Configurations

l Basic Concepts is added. l Configuring Services on Boards is added. l Configuring E-LAN Services is added.

Issue 01 (2011-10-20)


iv


Update

Description

Reference Operations for the Commissioning and Configuration

l Adding Ports is added.

About This Document

l Deleting Ports is added. l Changing Port Types is added.

Updates in Issue 01 (2010-12-17) Based on Product Version V100R003C00 The updated contents are as follows: l

New information: – Configuring master and slave shelves – Configuring OSI over DCC – Connecting to the SCC board through a serial port – Configuring the LEM18 board – Configuring the Ethernet line services and the Ethernet LAN services – Configuring WDM trails – Configuring ERPS protection – Testing ERPS switching – Basic concepts regarding Ethernet services – Creating a VLAN group – Configuring the aging time for MAC addresses – Configuring port mirroring

l

Modification: – Requirements on optical power commissioning – User interfaces of the iManager U2000 and Web LCT – Glossary


The description of the GE(GFP-T) service supporting the LPT function is added.

l


Issue 01 (2011-10-20)


v


About This Document


The section "Configuring the LDE Board" is updated.

l



The section "Configuring Board Parameters" is updated.

l

The section "Configuring PRBS Test" is deleted and the corresponding contents are added in the section "PRBS Error Detection Function" in Feature Description.

l


Updates in Issue 01 (2010-03-05) Based on Product Version V100R002C00 Initial commercial release.

Issue 01 (2011-10-20)


vi


Contents

Contents About This Document.....................................................................................................................ii 1 Guide to This Document..............................................................................................................1 2 List of Tasks for Commissioning and Configuration During Deployment......................3 3 Preparations....................................................................................................................................8 3.1 Preparing Documents.........................................................................................................................................9 3.2 Preparing Tools, Equipment, and Materials.....................................................................................................10

4 Commissioning Optical Power.................................................................................................12 4.1 Commissioning a System Without Optical Amplifiers....................................................................................13 4.2 Commissioning a System with Optical Amplifiers..........................................................................................15 4.3 Checking the Optical Power Commissioning Results......................................................................................19

5 Basic Configurations...................................................................................................................20 5.1 Searching for and Creating NEs.......................................................................................................................22 5.2 Creating Optical NEs........................................................................................................................................25 5.3 Changing the ID and Name of an NE...............................................................................................................26 5.4 Configuring Master and Slave Shelves............................................................................................................28 5.5 Changing the IP Address of an NE...................................................................................................................33 5.6 Configuring Ethernet Extended ECC...............................................................................................................34 5.7 Configuring IP over DCC.................................................................................................................................39 5.8 Configuring OSI over DCC..............................................................................................................................40 5.9 Connecting to the SCC Board Through a Serial Port.......................................................................................43 5.10 Configuring Board Parameters.......................................................................................................................44 5.10.1 ELOM Parameters.................................................................................................................................44 5.10.2 LDE Parameters.....................................................................................................................................52 5.10.3 LDGF Parameters..................................................................................................................................56 5.10.4 LDGF2 Parameters................................................................................................................................59 5.10.5 LDX Parameters....................................................................................................................................63 5.10.6 LEM18 Parameters................................................................................................................................67 5.10.7 LOE Parameters.....................................................................................................................................74 5.10.8 LQG Parameters....................................................................................................................................79 5.10.9 LQM Parameters....................................................................................................................................83 5.10.10 LQM2 Parameters................................................................................................................................92 Issue 01 (2011-10-20)


vii


Contents

5.10.11 LQPL/LQPU Parameters...................................................................................................................103 5.10.12 LSPL/LSPU Parameters....................................................................................................................107 5.10.13 LSPR Parameters...............................................................................................................................109 5.10.14 LSX Parameters.................................................................................................................................110 5.10.15 LWX2 Parameters.............................................................................................................................115 5.10.16 TSP Parameters..................................................................................................................................119 5.10.17 SCC Parameters.................................................................................................................................123 5.11 Configuring Protection Schemes..................................................................................................................124 5.11.1 Configuring SW SNCP Protection......................................................................................................124 5.11.2 Configuring SNCP Protection.............................................................................................................128 5.11.3 Configuring ODUk SNCP Protection..................................................................................................128 5.11.4 Configuring Port Protection.................................................................................................................129 5.11.5 Configuring ERPS Protection..............................................................................................................135 5.12 Synchronizing the NE Time with the NMS Time........................................................................................138 5.13 Starting NE Performance Monitoring...........................................................................................................139 5.14 Checking Configurations in the Commissioning Process............................................................................141

6 Service Configurations.............................................................................................................143 6.1 Basic Concepts...............................................................................................................................................144 6.1.1 Overview...............................................................................................................................................144 6.1.2 Cross-Connection Types........................................................................................................................144 6.1.3 Cross-Connection Ability......................................................................................................................146 6.1.4 Formats of Ethernet Frames..................................................................................................................147 6.1.5 External Ports and Internal Ports...........................................................................................................150 6.1.6 Auto-Negotiation...................................................................................................................................150 6.1.7 Flow Control..........................................................................................................................................151 6.1.8 Tag Attributes........................................................................................................................................152 6.1.9 Bridges...................................................................................................................................................153 6.1.10 VLAN Group.......................................................................................................................................156 6.1.11 Board Model (Standard Mode and Compatible Mode).......................................................................156 6.1.12 ODUflex..............................................................................................................................................157 6.2 Configuring Services on Boards.....................................................................................................................159 6.2.1 ELOM Service Configuration...............................................................................................................160 6.2.2 LEM18 Service Configuration..............................................................................................................173 6.2.3 LQG Service Configuration...................................................................................................................177 6.2.4 LQM2 Service Configuration................................................................................................................182 6.2.5 TSP Service Configuration....................................................................................................................196 6.2.6 LQM Service Configuration..................................................................................................................202 6.2.7 LDGF2 Service Configuration..............................................................................................................209 6.3 Configuring WDM Services...........................................................................................................................215 6.3.1 Configuring Cross-Connection Service.................................................................................................215 6.3.2 Configuring Services in Service Package Mode...................................................................................217 6.4 Configuring EPL/EVPL Services...................................................................................................................220 Issue 01 (2011-10-20)


viii


Contents

6.4.1 EPL/EVPL Service Overview...............................................................................................................220 6.4.2 Configuring EPL Services.....................................................................................................................222 6.4.3 Configuring EVPL Services..................................................................................................................224 6.5 Configuring EPLAN/EVPLAN Services.......................................................................................................227 6.5.1 EPLAN/EVPLAN Service Overview....................................................................................................227 6.5.2 Configuring EPLAN Services...............................................................................................................230 6.5.3 Configuring EVPLAN Services (IEEE 802.lq Bridge).........................................................................232 6.5.4 Configuring EVPLAN Services (IEEE 802.laq Bridge).......................................................................234 6.6 Configuring SDH Service...............................................................................................................................238

7 Follow-up Operations (Including Data Backup).................................................................240 7.1 Creating Fibers...............................................................................................................................................242 7.2 Configuring WDM Trails...............................................................................................................................243 7.2.1 Searching WDM Trails..........................................................................................................................243 7.2.2 Creating WDM Trails............................................................................................................................245 7.2.3 Managing WDM Trails.........................................................................................................................247 7.3 Backing Up the NE Database to the SCC Board............................................................................................248 7.4 Checking Optical Power of Boards................................................................................................................249 7.5 Querying Bit Errors Before and After FEC....................................................................................................252 7.6 Viewing Current Alarms on an NE and Removing Abnormal Alarms..........................................................254 7.7 Testing Protection Switching..........................................................................................................................256 7.7.1 Testing SW SNCP Switching................................................................................................................256 7.7.2 Testing SNCP Switching.......................................................................................................................259 7.7.3 Testing ODUk SNCP Switching...........................................................................................................261 7.7.4 Testing Port Protection Switching.........................................................................................................264 7.7.5 Testing ERPS Protection.......................................................................................................................265 7.8 Querying and Saving the Networkwide Optical Power and Alarm Data.......................................................266 7.9 Backing Up NE Data to the NMS Server or Client........................................................................................267

A Handling Common Commissioning Problems..................................................................269 A.1 The Receive Optical Power Is Normal But the LDGF Board Reports an OTU1_LOF Alarm.....................270 A.2 The Receive Optical Power Is Normal But the LDGF Board Reports a LINK_ERR Alarm........................271 A.3 The Receive Optical Power is Normal But an OTU Board Reports an REM_SF Alarm.............................271 A.4 The Optical Path Is Reachable But the NE Cannot Be Logged in Remotely................................................272

B Reference Operations for the Commissioning and Configuration.................................274 B.1 Creating a VLAN Group................................................................................................................................277 B.2 Configuring the Aging Time for MAC Addresses........................................................................................278 B.3 Configuring Port Mirroring............................................................................................................................279 B.4 Obtaining NE IP Addresses at the Site..........................................................................................................279 B.5 Creating a Single NE.....................................................................................................................................280 B.6 Checking the NE Software Version...............................................................................................................282 B.7 Creating an NE User......................................................................................................................................282 B.8 Switching a Logged-In NE User....................................................................................................................284 Issue 01 (2011-10-20)


ix


Contents

B.9 Modifying the Optical NE Name...................................................................................................................285 B.10 Modifying GNE Parameters........................................................................................................................285 B.11 Changing the GNE for NEs.........................................................................................................................286 B.12 Changing a GNE to a Normal NE................................................................................................................287 B.13 Changing a Normal NE to a GNE................................................................................................................288 B.14 Deleting NEs................................................................................................................................................288 B.15 Enabling the Proxy ARP..............................................................................................................................289 B.16 Configuring the IP Static Route for an NE..................................................................................................290 B.17 Querying the OSPF Protocol Status.............................................................................................................291 B.18 Configuring the NE Data.............................................................................................................................291 B.18.1 Configuring the NE Data Manually....................................................................................................291 B.18.2 Uploading the NE Data.......................................................................................................................292 B.19 Configuring Boards......................................................................................................................................293 B.19.1 Adding Boards....................................................................................................................................293 B.19.2 Deleting Boards..................................................................................................................................294 B.20 Adding Ports................................................................................................................................................294 B.21 Deleting Ports...............................................................................................................................................295 B.22 Changing Port Types....................................................................................................................................295 B.23 Configuring the Standard NTP Key.............................................................................................................296 B.24 Synchronizing the NE Time with the Standard NTP Server Time..............................................................297 B.25 Setting Automatic Synchronization of the NE Time with the NMS Time..................................................298 B.26 Performance Management...........................................................................................................................298 B.26.1 Setting the Board Performance Threshold..........................................................................................299 B.26.2 Setting Performance Monitoring Parameters of a Board....................................................................299 B.26.3 Setting Performance Monitoring Parameters of an NE......................................................................300 B.26.4 Resetting Board Performance Registers.............................................................................................300 B.27 Modifying the Services Configuration.........................................................................................................301 B.27.1 Activating Cross-Connections............................................................................................................301 B.27.2 Deactivating Cross-Connection Service.............................................................................................302 B.27.3 Deleting Cross-Connections...............................................................................................................303 B.27.4 Converting an Unprotected Service to an SNCP Service...................................................................304 B.27.5 Converting an SNCP Service to an Unprotected Service...................................................................305 B.28 Switching the Working Mode of the LQM2................................................................................................307 B.29 Backing Up and Restoring the NE Data......................................................................................................309 B.29.1 Comparison of NE Data Backup and Restoration Methods...............................................................309 B.29.2 Restoring the NE Database from the SCC Board...............................................................................311 B.29.3 Recovering Device Data from the NMS Server or the NMS Client...................................................311 B.30 Creating Fiber Connections in List Mode....................................................................................................312

C Parameter Reference.................................................................................................................314 C.1 NE Attributes.................................................................................................................................................315 C.2 Attributes of NE Users...................................................................................................................................316 C.3 NE Time Synchronization..............................................................................................................................319 Issue 01 (2011-10-20)


x


Contents

C.4 WDM Cross-Connection Configuration........................................................................................................321 C.5 Port Protection Parameters.............................................................................................................................321 C.6 SNCP Service Control Parameters.................................................................................................................324

D Glossary......................................................................................................................................330

Issue 01 (2011-10-20)


xi


1

1 Guide to This Document

Guide to This Document

This document helps you commission and configure the OptiX OSN 1800 equipment easily and effectively. Organized according to the tasks involved in the commissioning and configuration of the OptiX OSN 1800 equipment, this document guides you to complete the commissioning and configuration of the OptiX OSN 1800 equipment. Before reading this document, you are advised to master the following knowledge: l

Basic knowledge of the OptiX OSN 1800 equipment Read the OptiX OSN 1800 product manuals, such as Product Description, Hardware Description, and Feature Description.

l

Basic knowledge of installing and operating the iManager U2000 and iManager U2000 Web LCT Read manuals, such as Installation Guide and Operation Guide for the iManager U2000 and Web LCT User Guide for the iManager U2000 Web LCT.

After mastering the preceding knowledge, read this document as follows: 1.

See to have a general idea of the tasks involved in the commissioning and configuration of the OptiX OSN 1800 equipment and sequence of the tasks. Generally, you do not need to perform all tasks listed in for a network. Instead, you can perform the necessary tasks according to the actual network configuration and networking planning and design. If you are experienced in commissioning and configuring the OptiX OSN 1800 equipment, have mastered the commissioning and configuration knowledge, and can use the commissioning tools skillfully, you can take this document as reference.

2.

To understand the specific operations and precautions of a task listed in , you can click the matching link of the task to access the page that describes the details about the task. The operation methods of how a task is performed by using multiple commissioning tools are provided. In an actual project, only one commissioning tool is used. Therefore, you can perform the task according to the relevant description of the commissioning tool. The operation methods of different commissioning tools are similar. They serve reference for each other in actual commissioning. Certain tasks can be performed in various methods on a commissioning tool. This document describes only the most common method. For other operation methods, see Reference Information of the tasks. When a task is complete, see for the next one.

Issue 01 (2011-10-20)


1


3.

1 Guide to This Document

If you need to know more about a task, for example, optional operation methods of the task, see Reference Information of the task. Reference Information describes the handling process of common problems, relevant operations, examples, and parameter description associated with the task. NOTE

You can also find the contents in Reference Information in the appendix of this document. Nevertheless, you are recommended to read the contents from Reference Information of each task. This helps you to better understand the relationships between operations.

Issue 01 (2011-10-20)


2


2

2 List of Tasks for Commissioning and Configuration During Deployment

List of Tasks for Commissioning and Configuration During Deployment

Complete the deployment of an OptiX OSN 1800 network according to the tasks listed in this section. Perform the tasks in sequence; otherwise, NEs may be unreachable and you may need to handle problems on site. You can perform the commissioning and configuration during deployment of the OptiX OSN 1800 equipment by using either the iManager U2000 (U2000 for short) or the OptiX iManager U2000 Web LCT (Web LCT for short). All the operations that can be performed on the Web LCT can be performed on the U2000. Compared with U2000, the Web LCT has lower requirements on the computer hardware and can be started quickly. In actual commissioning, you can omit the tasks that are supported only by the U2000 when performing the commissioning and configuration on the Web LCT. After performing the commissioning and configuration on the Web LCT, you can configure the network-level functions on the U2000. Table 2-1 lists the tasks for the commissioning and configuration of the OptiX OSN 1800 equipment during deployment. Table 2-1 List of tasks for the commissioning and configuration of the OptiX OSN 1800 equipment during deployment

Issue 01 (2011-10-20)

No.

Task

Mandato ry/ Optional

Tool

1

Prepare the reference documents for the commissioning. The reference documents include the engineering design documents, and blank station bar code labels.

Mandatory

Template and designing tools

2

Prepare tools, meters, and materials required for the commissioning. Download and install the Web LCT or U2000.

Mandatory

None

3

Complete commissioning the optical power. Then reclaim and keep properly the station bar code return table.

Mandatory

None


3


Issue 01 (2011-10-20)


No.

Task


Tool

4

Connect NEs to the Web LCT or U2000. Start and log in to the Web LCT or U2000. Then, search and create the NEs on the Web LCT or U2000.

Mandatory

Web LCT or U2000

5

Create optical NEs on the U2000.

Mandatory on the U2000

U2000

6

Query the SCC electronic label of an NE. Then find the NE in the station bar code return table according to the queried bar code to determine the location of the NE. Then change the ID and name of the NE according to the NE ID planning provided by the customer.

Mandatory

Web LCT or U2000

7

Change the IP address of an NE according to the IP address planning provided by the customer.

Mandatory for gateway NEs and optional for other NEs

Web LCT or U2000

8

Configuring Master and Slave Subracks.

Optional

Web LCT or U2000

9

When the network adopts HWECC communication, configure Ethernet extended ECC.

Unavailabl Web LCT or e for the U2000 masterslave subrack mode. Mandatory for the nonmasterslave mode when the number of NEs that adopt ECC extended communic ation exceeds nine and optional for other situations


4


No.


Task


Tool

When the network adopts IP over DCC communication, configure IP over DCC.

Optional

Web LCT or U2000

When the network adopts OSI over DCC communication, configure OSI over DCC. 10

When the SCC board of an NE connects to an external AC power supply, an outdoor cabinet, or a sensor system such as the access control or temperature control system by using a serial port, you must set serial port connection of the NE.

Optional

Web LCT or U2000

11

Configure the parameters of the ELOM, LDE, LDGF, LDGF2, LDX, LEM18, LOE, LQG, LQM, LQM2, LQPL/LQPU, LSPL/LSPU, LSPR, LSX, LWX2, TSP, and SCC boards.

Mandatory

Web LCT or U2000

12

Configure services.

Mandatory according to the network design and actual board configurati on

Web LCT or U2000

l Configure WDM services. – In the case of the TSP, LQM2 or LQG board, configure cross-connections for each NE. – In the case of the LWX2, LQM2, or LQM board, you can use the service package mode to quickly configure services. l Configure Ethernet services, which are supported only by the LEM18 board. – Configure EPL/EVPL Services and EPLAN/EVPLAN Services based on the service planning. l Configure SDH services and protection: For the TSP board, configure SDH services and configure SNCP protection.

Issue 01 (2011-10-20)

13

Create optical fibers in either graphic mode or list mode on the U2000.


U2000

14

Configure WDM trails.


U2000


5



No.

Task


Tool

15

Configure protection schemes:

Mandatory according to the network design and actual board configurati on

Web LCT or U2000

l Configure port protection, including intraboard 1+1 protection, optical line protection, client 1+1 protection. l For the LQM2 or LQG board, configure SW SNCP protection. l For the TSP board, configure SNCP protection. l For the F2ELOM, F2LQM, F2LQM2, F2LDGF2, F2LSX, F1LDX board, configure ODUk SNCP protection. l For the LEM18 board, configure ERPS protection. 16

Synchronize the NE time with the NMS time.

Mandatory

Web LCT or U2000

17

Enable the NE performance monitoring.

Mandatory

Web LCT or U2000

18

Check the configuration to ensure that the network configuration is correct.

Mandatory

Web LCT or U2000

19

Back up the NE database to the SCC board.


U2000

20

Query the optical power. Check and ensure that the optical power is normal.

Mandatory

Web LCT or U2000

21

Query the bit errors. Ensure that the bit errors before and after FEC are normal.

Mandatory

Web LCT or U2000

22

Query the current alarms of an NE. Analyze and remove abnormal alarms.

Mandatory

Web LCT or U2000

23

Test and verify that the protection switching function is normal:

Mandatory if protection is configured

Web LCT or U2000

Mandatory

U2000

l Issue manual switching commands to test the port protection switching, SW SNCP protection , ODUk SNCP protection and SNCP protection. l Simulate a port fault and test ERPS protection switching. 24

Issue 01 (2011-10-20)

Query and save the networkwide optical power and alarm data.


6


Issue 01 (2011-10-20)


No.

Task


Tool

25

Back up the equipment data to the NMS server or client.

Mandatory

U2000


7


3 Preparations

3

Preparations

About This Chapter Before the deployment, collect the network data and understand the network design and configuration. In the process of installing the equipment, guide the hardware installation engineers to connect fibers and install optical attenuators as required. Before the commissioning and configuration, prepare the commissioning tools and reference documents for the commissioning. 3.1 Preparing Documents For a deployment of the OptiX OSN 1800 equipment, you need to prepare documents, including station bar code return table, engineering design documents, and product manuals, according to the actual project. 3.2 Preparing Tools, Equipment, and Materials You are recommended to use the Web LCT for the commissioning and configuration of the OptiX OSN 1800 equipment. The version of the commissioning tool must match the equipment version.

Issue 01 (2011-10-20)


8


3 Preparations

3.1 Preparing Documents For a deployment of the OptiX OSN 1800 equipment, you need to prepare documents, including station bar code return table, engineering design documents, and product manuals, according to the actual project.

Station Bar Code Return Table The station bar code return table is used to collect the bar codes of the sets of equipment installed at a station. After all sets of equipment at a station are installed, you need to record the bar codes of the equipment in the station bar code return table. The station bar code return table shows the mapping relationships between bar codes and station names. Therefore, it must be kept properly for future identifying the station where an NE is located when the ID and name of the NE are changed according to the customer planning.

Engineering Design Documents The engineering design documents are important inputs for equipment commissioning. Generally, the following contents are covered: l

Network diagrams: describe the module types, number of add and drop wavelengths, NE types and quantity, and NE IDs of each station, distance between adjacent stations, line attenuation between stations, and network topology.

l

Amplifier configuration diagrams: describe the amplifier configuration and line attenuation at each station.

l

Wavelength allocation diagrams: describe the wavelength numbers at each station, service relationships between stations (add, drop, or pass-through), and wavelength protection relationships.

l

Fiber connection diagrams: describe the internal and external fiber connection relationships, and slots, optical interfaces on the chassis and ODF terminals at each station.

Product Manuals The product manuals of the OptiX OSN 1800 equipment cover the equipment functions, features, and guides to the installation, commissioning, configuration, maintenance, and troubleshooting of the equipment. In the equipment deployment phase, you are recommended to read this manual, that is, OptiX OSN 1800 Compact Multi-Service Edge Optical Transport Platform Commissioning and Configuration Guide. The reference manuals are as follows: l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Product Description

l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Hardware Description

l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Quick Installation and Commissioning Guide

l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Feature Description

Issue 01 (2011-10-20)


9


3 Preparations

l

OptiX OSN 1800 Compact Multi-Service Edge Optical Transport Platform Alarms and Performance Events Reference

l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Troubleshooting

l

OptiX OSN 1800 Compact Multi-service Edge Transport Platform Parts Replacement

You can log in to the Web site http://support.huawei.com to download the product manuals of the OptiX OSN 1800 equipment. The path is Documentation > Product catalog > Optical Network > WDM > OptiX OSN 1800.

3.2 Preparing Tools, Equipment, and Materials You are recommended to use the Web LCT for the commissioning and configuration of the OptiX OSN 1800 equipment. The version of the commissioning tool must match the equipment version.

Commissioning Tool You can use either the U2000 or the Web LCT for the commissioning and configuration of the OptiX OSN 1800 equipment. Compared with the U2000, the Web LCT has lower requirements on the computer hardware and can be started quickly. Therefore, the Web LCT is recommended at the commissioning and configuration phases. The Web LCT, however, does not support query or configuration of network-level functions. Therefore, the query and configuration of network-level functions must be performed on the U2000. You can log in to the Web site http://support.huawei.com to download the required version of the U2000 and Web LCT. The path is Software Center > Version Software > Network OSS&Service > iManager U2000. NOTE

The versions of the U2000 and Web LCT must match the version of the equipment. NOTE

When you use the U2000 for the commissioning and configuration, you must be an NMS user with "NE operator" authority or higher.

Commissioning Meters An optical power meter and an optical spectrum analyzer are mainly used for optical power commissioning. The optical spectrum analyzer may be used only for commissioning of a network that is configured with optical amplifier (OA) boards. The optical power meter can be used for testing the total optical power of multiplexed signals and optical power of the optical transponder unit (OTU) boards. The optical spectrum analyzer can be used for testing the optical power, optical signal-to-noise ratio (OSNR), and center wavelength of a single wavelength of the multiplexed signals. You are required to test the optical power of a single wavelength of the multiplexed signals by using the optical spectrum analyzer because the test result is more accurate and the impact of the noise does not need to be considered. The meters must be calibrated before being used. Issue 01 (2011-10-20)


10


3 Preparations

Commissioning Materials The following materials may be used for optical power commissioning: fiber jumpers (FC/PCFC/PC, LC/PC-LC/PC, and LC/PC-FC/PC; two for each type), FOAs (3 dB, 5 dB, 7 dB, 10 dB, and 15 dB), flanges, fiber cleaning tissues or fiber cleaning boxes, and compressed gas duster.

Issue 01 (2011-10-20)


11


4

4 Commissioning Optical Power

Commissioning Optical Power

About This Chapter The optical power must be first commissioned in the deployment commissioning to ensure normal communication between all NEs and normal optical power received by each board. If the actual line attenuation is consistent with the design attenuation, the optical power is supposed to be within the normal range after the hardware installation engineers install the FOAs correctly according to the engineering design documents. 4.1 Commissioning a System Without Optical Amplifiers When commissioning a system without optical amplifiers (OAs), pay attention to the receive optical power of OTU boards. 4.2 Commissioning a System with Optical Amplifiers When commissioning the optical power of a system with optical amplifiers (OAs), pay attention to the output optical power of OAs, the receive optical power of corresponding OTU boards, and the input optical power of the DCM module. 4.3 Checking the Optical Power Commissioning Results When optical power commissioning is complete, you need to check the optical power commissioning results.

Issue 01 (2011-10-20)


12



4.1 Commissioning a System Without Optical Amplifiers When commissioning a system without optical amplifiers (OAs), pay attention to the receive optical power of OTU boards.

General Requirements The general requirements for commissioning the optical power of a system without OAs are as follows: l

The optical power after commissioning must be within the permitted range.

l

A certain optical power margin must be reserved to ensure that optical power fluctuation in a certain range does not affect the existing services.

Requirements on OTU Optical Power The output optical power of an OTU board must conform to the optical power specifications of the OTU board. For details on the optical power specifications of the OTU board, see the Hardware Description. After commissioning, the receive optical power of the OTU board must satisfy the following formula: Lower threshold of the receive optical power ≤ Receive optical power of the OTU board ≤ Upper threshold of the receive optical power. It is recommended that the receive optical power of an OTU board after commissioning is equal to the average value of the upper and lower thresholds in practical application. The optical power on the WDM side of the OTU board must satisfy the following formulas: l

Lower threshold of the receive optical power = Receiver sensitivity + 3 dB

l

Upper threshold of the receive optical power = Receiver overload point - 3 dB

The optical power on the client side of the OTU board must satisfy the following formulas: l


l


General Commissioning Methods In general, commission a system without OAs along the signal flow, that is, from the upstream direction to the downstream direction, according to the requirements on the OTU optical power. Measure the receive and transmit optical power of an OTU board by using an optical power meter, or query the receive and transmit optical power of the OTU board on the Web LCT or U2000.

Issue 01 (2011-10-20)


13



CAUTION In the commissioning process, ensure that the input optical power of an OTU board (either the WDM or client side) is lower than the optical power at the overload point to prevent the receiver optical module from being damaged or prevent the existing services from being affected. Exercise caution especially when an APD receiver optical module is used because the overload point of such an optical module is only -9 dBm. Hence, connect a fiber loosely or do not connect a fiber to the input optical port on the OTU board before measuring the actual input optical power.

Figure 4-1 Example of a system without OAs A O O T T U U B A

OTU

A

OTU

M U X

D U X

M U X

D U X

B

OTU

B

OTU

If the receive optical power on the WDM side of the OTU (recorded as P1) fails to meet the optical power requirement, do as follows: l

If P1 is higher than the upper threshold of the receive optical power, attach an appropriate fixed optical attenuator to the receive optical port (point B in Figure 4-1) on the WDM side of the OTU board to ensure that P1 meets the optical power requirement.

l

If P1 is lower than the lower threshold of the receive optical power, substitute a fixed optical attenuator with lower attenuation for the existing fixed optical attenuator or remove the fixed optical attenuator attached to the receive optical port (point B in Figure 4-1) on the WDM side of the OTU board. If P1 still fails to meet the optical power requirement after the fixed optical attenuator is removed, check whether the fiber attenuation on the line is proper and whether the network design data is correct.

If the receive optical power on the client side of the OTU (recorded as P2) fails to meet the optical power requirement, do as follows: l

If P2 is higher than the upper threshold of the receive optical power, attach an appropriate fixed optical attenuator to the receive optical port (point A in Figure 4-1) on the client side of the OTU board to ensure that P2 meets the optical power requirement.

l

If P2 is lower than the lower threshold of the receive optical power, substitute a fixed optical attenuator with lower attenuation for the existing fixed optical attenuator or remove the fixed optical attenuator attached to the receive optical port (point A in Figure 4-1) on the client side of the OTU board. If P2 still fails to meet the optical power requirement after the fixed optical attenuator is removed, check whether the transmit optical power of the upstream equipment is within the permitted range, whether the fiber attenuation on the line is proper, and whether the network design data is correct.

Issue 01 (2011-10-20)


14



If the output optical power of the OTU board fails to meet the optical power requirement on OTU boards, replace the corresponding optical module.

Tools, Equipment, and Materials Optical power meter, Web LCT or U2000, fiber jumpers (two FC/PC-FC/PC, LC/PC-LC/PC, and LC/PC-FC/PC fiber jumpers), several fixed optical attenuators (3 dB, 5 dB, 7 dB, 10 dB, and 15 dB), fiber adapters, fiber cleaning tissue or cassette cleaner, and compressed air cleaner.

4.2 Commissioning a System with Optical Amplifiers When commissioning the optical power of a system with optical amplifiers (OAs), pay attention to the output optical power of OAs, the receive optical power of corresponding OTU boards, and the input optical power of the DCM module.

General Requirements The general requirements for commissioning the optical power of a system with OAs are as follows: l

The optical power after commissioning must be within the permitted range.

l

A certain optical power margin must be reserved to ensure that optical power fluctuation in a certain range does not affect the existing services.

l

The optical power after commissioning must meet the requirements on system expansion.

Requirements on OTU Optical Power The output optical power of an OTU board must conform to the optical power specification of the OTU board. For details on the specifications of the OTU board, see the Hardware Description. After commissioning, the receive optical power of the OTU board must satisfy the following formula: Lower threshold of the receive optical power ≤ Receive optical power of the OTU board ≤ Upper threshold of the receive optical power. In practical application, it is recommended to commission the optical power according to the following formula: Receive optical power of an OTU board = Average value of the upper and lower receive optical power thresholds + 2 dB. The optical power on the WDM side of the OTU board (PIN receiver optical module) must satisfy the following formulas: l


l


The optical power on the WDM side of the OTU board (APD receiver optical module) must satisfy the following formulas: l


l


The optical power on the client side of the OTU board must satisfy the following formulas: l Issue 01 (2011-10-20)

Lower threshold of the receive optical power = Receiver sensitivity + 2 dB Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

15


l



Requirements on Multiplexer Board Optical Power Commission the optical power of each wavelength before the wavelengths are multiplexed (input optical power of a multiplexer board) according to the following formula: Average optical power of a single wavelength - 2 dB ≤ Optical power of a single wavelength ≤ Average optical power of a single wavelength + 2 dB.

Requirements on OA Optical Power The average output optical power of the wavelengths of an OA must be equal to the nominal output optical power for a single wavelength. In this case, the following requirements must be met: l

The average output optical power of the wavelengths of an OA is measured by connecting an optical spectrum analyzer to the OUT optical port on the OA.

l

Nominal output optical power for a single wavelength = Maximum total optical power of the OA - 10lgN (N represents the maximum number of wavelengths permitted by the system). For example, the maximum total optical power of the OA is 17 dBm. If the system is designed as a 40-channel system, the nominal output optical power for a single wavelength is 1 dBm as calculated by using the preceding formula.

The output optical power of a single wavelength of the OA should be equal to or close to the nominal output optical power for a single wavelength.

Requirements on DCM Optical Power If a DCM module is configured in a system, the optical power of a single wavelength input to the DCM module must be equal to or lower than -3 dBm.

General Commissioning Methods In general, commission a system with OAs along the signal flow, that is, from the upstream direction to the downstream direction, according to the requirements on the OA optical power, OTU optical power, and DCM optical power. The optical power of an OTU board is commissioned in the same way regardless of in a system with OAs or a system without OAs. For the detailed methods of commissioning the optical power of an OTU board, see 4.1 Commissioning a System Without Optical Amplifiers.

CAUTION In the commissioning process, ensure that the input optical power of an OTU board (either the WDM or client side) is lower than the optical power at the overload point to prevent the receiver optical module from being damaged or prevent the existing services from being affected. Exercise caution especially when an APD receiver optical module is used because the overload point of such an optical module is only -9 dBm. Hence, do not connect a fiber or connect a fiber loosely to the input optical port on the OTU board before measuring the actual input optical power.

Issue 01 (2011-10-20)


16



Figure 4-2 Example of a system with OAs A O O T T U U B G

E

A A

OTU C OTU C

M U X 1

D

OA2

D U X 1

M U X 2

F

OA3

D U X 2

B

OTU

B

OTU

OA1

Connect an optical spectrum analyzer to the OUT optical port on an OA, and then measure the output optical power of a single wavelength and the average output optical power of the wavelengths of the OA. If the output optical power of a single wavelength of the OA fails to meet the optical power requirement, adjust the optical attenuator at the WDM-side output optical port on the upstream OTU board or adjust the optical attenuator at the input optical port on the OA to ensure that the optical power of the OA meets the optical power requirements. See Figure 4-2. In the case of OA1, do as follows: l

If the average output optical power of wavelengths is higher than the nominal output optical power for a single wavelength, increase the attenuation of the optical attenuator at the input optical port (point as D in Figure 4-2) on the OA to ensure that the average optical power of wavelengths is equal to the nominal output optical power for a single wavelength.

l

If the average output optical power of wavelengths is lower than the nominal output optical power for a single wavelength, decrease the attenuation of the optical attenuator at the input optical port (point as D in Figure 4-2) on the OA to ensure that the average optical power of wavelengths is equal to the nominal output optical power for a single wavelength.

l

In the case of the output optical power of a specific wavelength, adjust the optical attenuator at the output optical port (point C in Figure 4-2) on the corresponding OTU board to ensure that the output optical power of this wavelength from the OA is equal to or close to the nominal output optical power for a single wavelength.

In the case of OA2, adjust the optical attenuator at point E in Figure 4-2 to ensure that the average optical power of wavelengths is equal to the nominal output optical power for a single wavelength. If the average output optical power of wavelengths cannot be equal to the nominal output optical power for a single wavelength after the attenuation is adjusted to 0, remove the optical attenuator. If the optical power requirement is still not met, check whether the network design data is correct. In the case of OA3, adjust the input optical power of the MUX2 board at the upstream station, and then adjust the optical attenuator at point F in Figure 4-2 to ensure that the average output optical power of wavelengths of the OA is equal to the nominal output optical power for a single Issue 01 (2011-10-20)


17



wavelength. The methods of commissioning the input optical power of the MUX2 board are as follows: 1.

Measure the optical power of each pass-through wavelength at the input optical port on the MUX2 board and then calculate the average optical power of these pass-through wavelengths. In the case of a multiplexed pass-through wavelength, measure the average optical power by using an optical spectrum analyzer. In the case of a single pass-through wavelength, measure the optical power of this pass-through wavelength directly by using an optical power meter.

2.

Measure the optical power of a single add wavelength at the input optical port on the MUX2 board and calculate the average optical power of a single add wavelength.

3.

Do as follows to adjust the optical power of corresponding wavelengths: l If the average optical power of a single pass-through wavelength is lower than the average optical power of a single add wavelength, adjust the optical attenuator at point G in Figure 4-2 to ensure that the optical power of a single add wavelength satisfies the following formula: Average optical power of a single pass-through wavelength - 2 dB ≤ Optical power of a single add wavelength ≤ Average optical power of a single passthrough wavelength + 2 dB. l If the average optical power of a single pass-through wavelength is higher than the average optical power of a single add wavelength, install one optical attenuator on each pass-through channel between the DUX1 and MUX2 boards to ensure that the average optical power of a single pass-through wavelength is equal to the average optical power of a single add wavelength. In addition, adjust the attenuation of the optical attenuators at the output optical interfaces on other OTU boards used to add wavelengths. This is to ensure that the optical power of a single add wavelength satisfies the following formula: Average optical power of a single pass-through wavelength - 2 dB ≤ Optical power of a single add wavelength ≤ Average optical power of a single pass-through wavelength + 2 dB. NOTE

If you want to install fixed optical attenuators (FOAs) on the pass-through channels between the DUX1 and MUX2 boards, install the FOAs with the minimum attenuation under the condition that the average optical power of a single pass-through wavelength is equal to or lower than the average optical power of a single add wavelength, ensuring the minimum loss of pass-through wavelengths. In this case, the optical power of a single add wavelength must also satisfy the following formula: Average optical power of a single pass-through wavelength - 2 dB ≤ Optical power of a single add wavelength ≤ Average optical power of a single pass-through wavelength + 2 dB. TIP

If the OPU/OBU board is configured with SFP EVOA, the attenuation value can be adjusted on the NMS.

If a DCM module is configured in the system, measure the total input optical power of the DCM module by using an optical power meter. Then, calculate and ensure that the actual input optical power of a single wavelength is equal to or lower than -3 dBm.

Tools, Equipment, and Materials Optical power meter, optical spectrum analyzer, Web LCT or U2000, fiber jumpers (two FC/ PC-FC/PC, LC/PC-LC/PC, and LC/PC-FC/PC fiber jumpers), several fixed optical attenuators (3 dB, 5 dB, 7 dB, 10 dB, and 15 dB), fiber adapters, fiber cleaning tissue or cassette cleaner, and compressed air cleaner.

Issue 01 (2011-10-20)


18



4.3 Checking the Optical Power Commissioning Results When optical power commissioning is complete, you need to check the optical power commissioning results.

Prerequisite The optical power commissioning must be complete.

Tools, Equipment, and Materials Web LCT or U2000

Procedure Step 1 Check whether communication of all stations on the network is normal. For the checking methods, see 5.1 Searching for and Creating NEs. If communication of an NE is interrupted or the NE is abnormal, check whether the fiber connection is correct onsite. Step 2 Check whether alarms indicating excessively high or low optical power, or bit error threshold crossing exist on the network. For the checking and handling methods, see 7.6 Viewing Current Alarms on an NE and Removing Abnormal Alarms. Step 3 Check whether before-FEC and after-FEC bit errors of the boards that support the FEC function are normal. For the checking methods, see 7.5 Querying Bit Errors Before and After FEC. Step 4 See the preceding procedure to check and ensure that all optical power values on the network are normal, and then save the networkwide optical power data. For the operation methods, see 7.8 Querying and Saving the Networkwide Optical Power and Alarm Data. ----End

Issue 01 (2011-10-20)


19


5 Basic Configurations

5

Basic Configurations

About This Chapter 5.1 Searching for and Creating NEs You can search for and create NEs when the NEs are connected to the NMS computer and the communication between NEs and the NMS is normal. 5.2 Creating Optical NEs On the U2000 the WDM equipment is allocated to different optical NEs for management. 5.3 Changing the ID and Name of an NE The ECC protocol uses an NE ID to uniquely identify an NE. When planning the network, you must assign a unique ID for each NE. If an NE ID conflicts with another one, ECC routing collision is caused. In this case, certain NEs cannot be managed. 5.4 Configuring Master and Slave Shelves Generally, master and slave shelves are configured before delivery and you only need to check the cable connections between the master and slave shelves before uploading NE data to the NMS during deployment commissioning. If no information about slave shelves is displayed after NE data is loaded, manually configure master and slave shelves. 5.5 Changing the IP Address of an NE If a network uses HWECC for communication, you need to change the IP address of a gateway NE according to customer planning and you do not need to change the IP addresses of nongateway NEs. If the network uses IP over DCC for communication, you need to change the IP addresses of all NEs according to customer planning. 5.6 Configuring Ethernet Extended ECC In master-slave subrack mode, you do not need to configure the Ethernet extended ECC. In nonmaster-slave subrack mode, when there is no OSC or ESC communication between two or more NEs, the Ethernet ports of the NEs can be used to achieve the extended ECC communication. By default, the OptiX OSN 1800 series NEs take the auto-extended ECC communication. When the number of NEs that use the extended ECC communication exceeds nine, you must set the extended ECC communication to specified mode. 5.7 Configuring IP over DCC

Issue 01 (2011-10-20)


20



When the network planning adopts the IP over DCC mode for communication, you need to configure the DCC channel and check whether the IP routes are correct in the commissioning and configuration. 5.8 Configuring OSI over DCC When a network adopts OSI over DCC for communication, configure DCC channels and the protocol parameters of each OSI layer on each NE to ensure normal DCN communication. 5.9 Connecting to the SCC Board Through a Serial Port When the SCC board of an NE connects to an external AC power supply, an outdoor cabinet, or a sensor system such as the access control or temperature control system through a serial port, you must set the serial port on the NE to ensure normal communication between the SCC board and the external equipment. 5.10 Configuring Board Parameters Different boards implement different functions, and therefore you need to configure different parameters in the commissioning and configuration for deployment. Set parameters appropriately for each board according to the actual network. 5.11 Configuring Protection Schemes When commissioning and configuring a network, you need to configure protection schemes based on the network and service planning. 5.12 Synchronizing the NE Time with the NMS Time With the time synchronization function, the NE time is kept consistent with the NMS time. In this way, the NMS is able to record the correct time when alarms and abnormal events are reported by NEs. 5.13 Starting NE Performance Monitoring Enabling the performance monitoring function is a precondition for querying the performance events. If the current NE time is in the performance monitoring time range as set before, the NE monitors its performance events automatically. If the performance monitoring time range is not set or if the current NE time is not within the performance monitoring time range, the NE does not monitor its performance events. 5.14 Checking Configurations in the Commissioning Process Correct setting of each system parameter is the precondition for ensuring normal network operation.

Issue 01 (2011-10-20)


21



5.1 Searching for and Creating NEs You can search for and create NEs when the NEs are connected to the NMS computer and the communication between NEs and the NMS is normal.

Prerequisite Communication between the NMS computer and NEs must be normal. The IE proxy must be canceled.


Procedure on the Web LCT 1.

Connect an NE to the NMS computer directly or through a local area network (LAN) by using a network cable. In the case of non-master-slave subrack mode, connect the network cable to the ETH1 or ETH2&OAM optical port on the SCC board. In the case of masterslave subrack mode, connect the network cable to only the ETH1 optical port on the SCC board of the master subrack with subrack ID .

2.

Change the IP address of the NMS computer to ensure that the IP address of the NMS computer and the IP addresses of the NEs are in the same network segment. The IP address of the NMS computer must be different from the IP address used by an NE or a computer on the current LAN. Generally, set the IP address of the NMS computer to 129.9.0.N, in which N represents an integer ranging from 1 to 255 and the subnet mask to 255.255.0.0. You do no need to set the default gateway. The default IP addresses of the NEs are in the network segment of 129.9.255.255. To obtain the IP address of an NE at a site, see B.4 Obtaining NE IP Addresses at the Site.

3.

Start the server and client of the Web LCT, and then log in to the Web LCT. Both the user name and password for logging in to the Web LCT are admin.

4.

Search for all NEs in normal communication state. Then log in to the NEs. (1) Click NE Search > Advanced Search in the NE List. The Search NE dialog box is displayed. (2) Click Manage Domain. The Manage Domain Search dialog box is displayed. (3) Click Add, and the New Domain dialog box is displayed. (4) Set Domain Type to GNE IP Domain or GNE IP Address, and enter an IP address in the Domain Address field. (5) Click OK. NOTE

You can repeat step 3 through 5 to add multiple search domains.

(6) Click Cancel to exit the Manage Domain Search dialog box. (7) Select appropriate network segment IP addresses within the Domain and click Search. Issue 01 (2011-10-20)


22



NOTE

l The NE search function searches out only the NEs in the specified network segment. l When the search is in progress, you can click End Search.

(8) After the search is complete, select an NE from the list and click Add NE. A prompt message is displayed, indicating that the NE is successfully added. Click OK. (9) Select the NE that you want to log in and click NE Login in the lower right corner or right-click the NE and choose NE Login. In the NE Login dialog box that is displayed, enter lct and password in the User Name and Password fields, and then click OK. TIP

You can select multiple NEs at a time by concurrently pressing Shift. If you select the Use same user name and password to login check box, you can log in to multiple NEs at a time by entering the user name and password only in the first line. If you select the Use the user name and password that was used last time check box, you do not need to enter the use name and password and the system automatically uses the user name and password for login last time.

Procedure on the U2000 1.

Ensure that communication between the NMS computer and NEs is normal. Then start and log in to the U2000 server and client. Both the default user name and password for logging in to the U2000 are admin.

2.

Search for all NEs in normal communication state. Then log in to the NEs. The default IP addresses of the NEs are in the network segment of 129.9.255.255. (1) Choose File > Discovery > NE... from the Main Menu. The NE Discovery window is displayed. (2) Select the Transport NE Search tab. (3) Select the search mode from the drop-down list of Search Mode. l Sets the Search Mode as Search for NE. a.

In the Search Domain dialog box, click Add and the Input Search Domain dialog box is displayed.

b.

Set Address Type to IP Address Range of GNE, IP Address of GNE, or NSAP Address, and enter Search Address, User Name, and Password. Then, click OK. NOTE

You can repeat the above steps to add more search domains. You can delete the system default search domain. l If you use IP address to search for NEs: l only the NEs (not across routers) in the same network segment can be searched out in normal conditions if you select the IP Address Range of GNE because broadcasting is usually disabled for the routers in the network (to prevent network storm). l search out the NEs in the network segment by using the IP Address of GNE if you need to search for the NEs across routers. l If you search for NEs by using the NSAP address, you can only select NSAP Address.

c.

In the Search for NE dialog box, you can perform the following operations: – Select Create NE after search, and enter NE user and Password.

Issue 01 (2011-10-20)


23



NOTE

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

– Select Upload after being created, so that the NE data can be uploaded to the U2000 after the NE is 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.

l Sets the Search Mode is IP auto discovery. NOTE

If you fail to enter a network segment correctly, enable IP auto discovery. After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEs related to the GNE.

CAUTION In the case of NEs that are connected to the NMS through the router, these NEs cannot be searched out by IP auto discovery. They can be searched out only by network segment. (4) Click Next and the Result area is displayed. TIP

You can select the Display uncreated NEs to only display the uncreated NEs.

(5) Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users can check against the Bar Code List by the value of Bar Code, and then modify the NE Name, Extend NE ID, Base NE ID, and IP Address fields accordingly. NOTE

The Bar Code List is provided by the hardware installation personnel to the software commissioning personnel. The list contains the bar codes of stations.

(6) Optional: If you select only Search for NE, after the U2000 completes the search, you can select the uncreated NEs from the Relust list and click Create. The Create dialog box is displayed. Enter the NE User and Password. Click OK. (7) Optional: Select the NEs from the Result list and click Set Gateway NE. The Set Gateway NE dialog box is displayed. Enter the message, and click OK. 3.

If the data of an NE is not uploaded to the NE when the NE is created, upload the NE data to ensure that the data on the NE is consistent with that on the NMS. (1) In the Main Menu, choose Configuration > NE Configuration Data Management. . In Configuration Data (2) In the left topology tree, select a created NE and click Management List, select an NE whose NE Status is Unconfigured. (3) Click Upload. The Confirm dialog box is displayed. Click OK to start the upload. (4) When the upload is complete, the Operation Result dialog box is displayed. Click Close.

Issue 01 (2011-10-20)


24



Reference Information l

Obtaining the IP Address of an NE On Site If you fail to query the IP address of an NE on the U2000 or Web LCT on site, see this section to obtain the IP address of an NE.

l

Creating a Single NE If you have obtained the ID of an NE, you can create the NE manually.

l

Creating an NE User The user names for logging in to an NE must be different. You can create an NE user as required.

l

Switching a Login NE User You can switch a login NE user without logging out of the U2000 or Web LCT.

l

Configuring NE Data You can configure the NE data in upload or manual mode.

l

Checking the Software Version of an NE After the NE data is configured, you can see this section to query the software version of an NE.

l

Parameter: NE Attributes Describes the parameters associated with NE attributes.

l

Parameter: NE User Attributes Describes the parameters associated with NE user attributes.

Follow-up Procedure See List of Tasks for Commissioning and Configuration During Deployment for the subsequent task.

5.2 Creating Optical NEs On the U2000 the WDM equipment is allocated to different optical NEs for management.

Tools, Equipment, and Materials You can create optical NEs only on the U2000.


Right-click in the Main Topology and choose New > NE.

2.

In the Create NE dialog box that is displayed, click corresponding to Optical NE in the left pane, and then select the type of the optical NE that you want to create.

3.

Click Basic Attributes and enter the attributes such as the optical NE name according to the customer's planning.

4.

Click Resource Division and select an NE or a board from the idle optical NEs, and then click

Issue 01 (2011-10-20)

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

25



TIP

To re-allocate the resources of an optical NE that has been created, right-click the optical NE and choose Object Attribute. Click the Resource Division tab, select an NE or a board from the list on the left, and then click

to allocate the NE or board to the optical NE.

5.

Click OK.

6.

Click the Main Topology to create the optical NE icon.


Changing the Name of an Optical NE See this section to change the name of an optical NE independently.


5.3 Changing the ID and Name of an NE The ECC protocol uses an NE ID to uniquely identify an NE. When planning the network, you must assign a unique ID for each NE. If an NE ID conflicts with another one, ECC routing collision is caused. In this case, certain NEs cannot be managed.

Prerequisite The NE communication must be normal.


Precautions

CAUTION NE ID conflict leads to unreachable of NEs. Therefore, the ID of an NE must be unique on the network. NOTE

If the IP address of an NE is not changed before you change the NE ID, the IP address of the NE varies with the NE ID. Once the IP address of the NE is changed, the association between the NE ID and IP address is deleted automatically. TIP

If an NE is unreachable after the NE ID is changed, you can change the name of the NE only after searching for and logging in to the NE again. Therefore, you are recommended to change the NE name before changing the NE ID.

Issue 01 (2011-10-20)


26




Query the manufacturer information about the SCC board. (1) In the Function Tree in the NE Explorer, choose Report > Board Detail Information Report. (2) The Query dialog box is displayed to show the query progress.

2.

Obtain the bar code of the chassis from the queried information about the SCC board. The following figure shows the bar code of the chassis.

3.

Find the bar code of the chassis in the station bar code return table to determine the position and name of the station where the login NE is located. Then determine the ID and name of the NE according to the NE ID and name planning provided by the customer.

4.

Change the name of the NE. (1) In the NE Explorer, select the NE and choose Configuration > NE Attribute from the Function Tree. (2) Enter Name of the NE according to the customer planning, and then click Apply. NOTE

You can enter an NE name with a maximum of 64 characters consisting of letters, symbols, and numbers, excluding special characters that are not allowed on the interface, such as |, :, *, ?, ", <, and >.

5.

Change the ID of the NE. After you change the ID of the NE, the NE will be unreachable to the NMS. (1) In the NE Explorer, choose Configuration > NE Attribute from the Function Tree. (2) Click Modify NE ID. In the Modify NE ID dialog box that is displayed, enter values in the New ID and New Extended ID fields, and then click OK. (3) A warning dialog box is displayed, click Yes. A dialog box indicating that the operation is successful is displayed, click Close to complete changing the NE ID. At this time, the NE is unreachable.

6.

Navigate to NE List and delete the unreachable NE. Search for and create NEs again. TIP

When you search for the NEs again, the NE IDs displayed on the interface are the NE IDs after change. The NE names, however, change to the new NE names automatically only after you create and log in to the NEs again. NOTE

For details about searching for and creating NEs, see 5.1 Searching for and Creating NEs.


Query the manufacturer information about the SCC board. (1) In the Main Menu, choose Inventory > Project Document > Board Manufacturer Information. (2) Select the SCC board that you want to query in the left NE node, and then click . (3) The Query dialog box is displayed to show the query progress. When the query is complete, an operation result dialog box is displayed. Click Close.

2.

Issue 01 (2011-10-20)

Obtain the bar code of the chassis from the queried information about the SCC board. The following figure shows the bar code of the chassis. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

27



3.

Find the bar code of the chassis in the station bar code return table to determine the position and name of the station where the login NE is located. Then determine the ID and name of the NE according to the NE ID and name planning provided by the customer.

4.

Change the name of the NE. (1) In the NE Explorer, select the NE and choose Configuration > NE Attribute from the Function Tree. (2) Enter Name of the NE according to the customer planning, and then click Apply. NOTE

You can enter an NE name with a maximum of 64 characters consisting of letters, symbols, and numbers, excluding special characters that are not allowed on the interface, such as |, :, *, ?, ", <, and >.

(3) A dialog box indicating that the operation is successful is displayed. Click Close. 5.

Change the ID of the NE. (1) In the NE Explorer, choose Configuration > NE Attribute from the Function Tree. (2) Click Modify NE ID. In the Modify NE ID dialog box that is displayed, enter values in the New ID and New Extended ID fields, and then click OK. (3) A warning dialog box is displayed, click Yes. A dialog box indicating that the operation is successful is displayed, click Close to complete changing the NE ID. At this time, the NE is unreachable.


Deleting NEs You may need to delete an NE after the ID or IP address of the NE is changed. In this case, see this section to delete the NE.

l

Creating an NE User The user names for logging in to an NE must be different. You can create an NE user as required.

l

Switching a Login NE User You can switch a login NE user without logging out of the U2000 or Web LCT.

l

Parameter: NE Attributes Describes the parameters associated with NE attributes.

l

Parameter: NE User Attributes Describes the parameters associated with NE user attributes.


5.4 Configuring Master and Slave Shelves Generally, master and slave shelves are configured before delivery and you only need to check the cable connections between the master and slave shelves before uploading NE data to the NMS during deployment commissioning. If no information about slave shelves is displayed after NE data is loaded, manually configure master and slave shelves. Issue 01 (2011-10-20)


28



Prerequisite The NE ID must be set. The master and slave shelves are correctly connected by means of cables and the communication between the master and slave shelves are normal. The communication between the NMS and the NE must be normal.


Ring Network When OSC modules are required, they can be configured on a ring network, as shown in Figure 5-1. Compared with a chain network, a ring network has higher reliability. Figure 5-1 Ring network NMS

Master shelf

Slave shelf 1 SCC

Slave shelf 2 SCC

Slave shelf 3 SCC

ETH1 ETH2&OAM RM2/TM2

ETH2& OAM RM2/ TM2 ETH1 ETH2& OAM ETH1 ETH2& OAM

Network cable

Slave shelf 6 SCC

Slave shelf 5 SCC

Slave shelf 4 SCC

ETH1 ETH2&OAM

ETH1 ETH2&OAM

ETH1 ETH2&OAM

Fiber

Master shelf ID: 0

Slave shelf 1 ID: 1

Slave shelf 2 ID: 2

Slave shelf 4 ID: 4

Slave shelf 5 ID: 5

Slave shelf 6 ID: 6

Slave shelf 3 ID: 3

Chain Network A chain network can be configured with or without OSC modules. Issue 01 (2011-10-20)


29


l


When OSC modules are configured, the chain network is as shown in Figure 5-2. Figure 5-2 Chain network 1 NMS

ETH2& OAM

RM2/ ETH1 TM2 Master shelf SCC

ETH2& OAM ETH1

RM2/ TM2 ETH1

Slave shelf 2 SCC

Slave shelf 1 SCC

ETH2& OAM ETH1

Fiber

l

Slave shelf 3 SCC

ETH2& OAM ETH1

Slave shelf 5 SCC

Slave shelf 6 SCC

ETH2& OAM

ETH2& OAM

Slave shelf 4 SCC Network cable

Master shelf ID: 0

Slave shelf 1 ID: 1

Slave shelf 2 ID: 2

Slave shelf 4 ID: 4

Slave shelf 5 ID: 5

Slave shelf 6 ID: 6

Slave shelf 3 ID: 3

When no OSC module is configured, if there are only the master shelf and slave shelf 1, the chain network is as shown in Figure 5-3. If there are multiple slave shelves, the chain network is as shown in Figure 5-4. Figure 5-3 Chain network 2 NMS

ETH1

ETH2& OAM Master shelf SCC

ETH2& OAM Slave shelf 1 SCC

Network cable Master shelf ID: 0

Issue 01 (2011-10-20)

Slave shelf 1 ID: 1


30



Figure 5-4 Chain network 3 NMS

ETH1

ETH2& OAM ETH1 Master shelf SCC

ETH2& OAM ETH1

ETH2& OAM ETH1

Slave shelf 2 SCC

Slave shelf 3 SCC

ETH2& OAM ETH1 Slave shelf 1 SCC

ETH2& OAM Slave shelf 4 SCC

ETH2& OAM ETH1

Slave shelf 6 SCC

ETH2& OAM

Slave shelf 5 SCC Network cable

Master shelf ID: 0

Slave shelf 1 ID: 1

Slave shelf 2 ID: 2

Slave shelf 4 ID: 4

Slave shelf 5 ID: 5

Slave shelf 6 ID: 6

Slave shelf 3 ID: 3

NOTE

ETH1 ports in the master shelf and slave shelf 1 cannot be used for cascading the master shelf and slave shelves.

In the case of the OptiX OSN 1800, the bar codes and shelf IDs are identified on the chassis labels. The shelf IDs refer to the IDs of physical shelves and are one-to-one corresponding to bar codes of chassis. The ID of the master shelf is 0, and the ID of a slave shelf ranges from 1 to 6.

Precautions

CAUTION l You need to back up the NE database before performing a warm reset on the SCC board of a master shelf. l If the master shelf connected to a slave shelf is changed, you need to reset the SCC board of the slave shelf. A warm rest is recommended. l If the communication between the master shelf and the slave shelf fails, do not perform any configurations on the boards of the slave shelf.

Procedure on the Web LCT or U2000 1.

Add a logical slave shelf. You need to specify an ID for the required logical slave shelf.

Issue 01 (2011-10-20)


31



(1) In the Main Topology, double-click an optical NE and then choose the NE from the left pane of the NE Panel. (2) Right-click in the upper side of the right pane and choose Add Slave Shelf from the shortcut menu. The Add Slave Shelf dialog box is displayed. (3) In the Add Slave Shelf dialog box, set parameters and then click OK. (4) The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. 2.

Associate a physical shelf. To associate a physical shelf is to establish one-to-one mapping between the ID of a logical shelf and the bar code of the chassis. The ID of a physical shelf is modified based on the ID of the specified logical shelf. Therefore, when a physical shelf is associated, the ID of the shelf is modified. If the ID of the associated logical shelf is inconsistent with the shelf ID on the chassis label, you need to modify the shelf ID on the chassis label so that future installation and maintenance personnel will not be midguided. NOTE

Note that the shelf ID must match cable connection between the master and slave shelf. You need to check whether the current cable connection needs to be modified when associating a physical shelf. For example, assume that the ID of the slave shelf connected to the input or output optical port RM2 or TM2 of the OSC on the master shelf is 1. When changing the ID of the slave shelf or changing the ID of another slave shelf to 1, you need to change the physical fiber connections.

(1) In the Main Topology, double-click an optical NE and then choose the NE from the left pane of the NE Panel. (2) Choose the required slave shelf from the upper side of the slot layout in the right pane. Right-click the shelf and then choose Associate the Physical Shelves from the shortcut menu. (3) Click OK in the displayed Confirm dialog box, the Associate the physical shelves dialog box is displayed. (4) Select the bar code of the physical slave shelf whose ID needs to be changed from the Physical Shelves Code drop-down list, and then click OK. The ID of the physical slave shelf is changed to that of the logical slave shelf. 3.

Optional: Change names of the master and slave shelves. (1) In the Main Topology, double-click an optical NE and then choose the NE from the left pane of the NE Panel. (2) Choose the required master or slave shelf from the upper side of the slot layout in the right pane. Right-click the shelf and then choose Modify Shelf Attribute from the shortcut menu to display the Modify Shelf Attribute dialog box. (3) Change the Shelf name and click OK.

Reference Information See the Feature Description for more information about master and slave shelves.

Follow-up Procedure See List of Tasks for Commissioning and Configuration During Deployment for the subsequent task. Issue 01 (2011-10-20)


32



5.5 Changing the IP Address of an NE If a network uses HWECC for communication, you need to change the IP address of a gateway NE according to customer planning and you do not need to change the IP addresses of nongateway NEs. If the network uses IP over DCC for communication, you need to change the IP addresses of all NEs according to customer planning.

Prerequisite The NE communication must be normal.


Precautions

CAUTION If the IP address of the NE and that of the computer where the U2000 or Web LCT server is located are in different network segments, the communication between the U2000 or Web LCT and the NE is interrupted. In this case, you need to configure the IP address of the NE and that of the computer where the U2000 or Web LCT server is located so that the two IP addresses are in the same network segment to recover the communication. Due to the restriction of the SQL database, after changing the IP address of the computer where the U2000 or Web LCT server is located, you need to close the client and server of the U2000 or Web LCT. Then restart the computer and the server and client of the U2000 or Web LCT.


In the NE Explorer, select Communication > Communication Parameters from Function Tree.

2.

Enter the IP address in the IP:, and click Apply.

3.

Click OK after the warning dialog box pops up.

4.

Click OK after the warning dialog box about communication interruption between NEs pops up.

5.

Click Close after the Result dialog box is displayed. NOTE

If the IP address of the NE and the IP address of the Web LCT server are in the same network segment after you change the IP address of the NE, the communication between the Web LCT and the NE is normal. If the IP address of the NE and the IP address of the Web LCT server are in the different network segment after you change the IP address of the NE, the communication between the Web LCT and the NE is abnormal. Navigate to NE List and delete the NE whose IP address is changed and communication is abnormal. You need to configure the IP address of the computer where the Web LCT server is located and that of the NE so that the two IP addresses are in the same network segment to recover the communication. Search for and create NEs again. For details about searching for and creating NEs, see 5.1 Searching for and Creating NEs.

Issue 01 (2011-10-20)


33




In the NE Explorer, select Communication > Communication Parameters from Function Tree.

2.

Enter the IP address in the IP:, and click Apply.

3.

Click OK after the warning dialog box pops up.

4.

Click OK after the warning dialog box about communication interruption between NEs pops up.

5.

Click Close after the Result dialog box is displayed. NOTE

You cannot log in to the NE after you change the IP address of the NE on the U2000. To log in to the NE, delete the original NE and create the NE again.


Modifying Gateway NE Parameters In addition to the IP address, you need to modify other parameters of a gateway NE according to the network condition. In this case, see this section to modify the parameters of a gateway NE.

l

Changing the Affiliated Gateway NE of an NE To adjust the DCN network structure, you may need to change the affiliated gateway NEs of certain NEs.


5.6 Configuring Ethernet Extended ECC In master-slave subrack mode, you do not need to configure the Ethernet extended ECC. In nonmaster-slave subrack mode, when there is no OSC or ESC communication between two or more NEs, the Ethernet ports of the NEs can be used to achieve the extended ECC communication. By default, the OptiX OSN 1800 series NEs take the auto-extended ECC communication. When the number of NEs that use the extended ECC communication exceeds nine, you must set the extended ECC communication to specified mode.

Prerequisite The communication between NEs must be normal.


Background Information The extended ECC communication has the following two modes: l

Issue 01 (2011-10-20)

Automatic mode: Extended ECC connections are established automatically. This mode is convenient but extra connections are established. Therefore, the resource utilization ratio Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

34



is low and this mode is recommended to be used when the number of NEs is smaller than nine. l

Specified mode: Extended ECC connections are established according to the specified server and client. In this mode, the connections are reliable and the bandwidth utilization ratio is high. In normal cases, use the specified mode to establish extended ECC connections. An NE cannot operate in both modes at the same time to establish extended ECC communication with another NE.

In the case of Ethernet extended ECC, a server NE can be connected to a maximum of eight client NEs and a client NE can serve as the server NE of another extended ECC group. Generally, set an NE that is not configured with the supervisory channel (ESC or OSC) as a client NE and an NE that is configured with the supervisory channel (ESC or OSC) as a server NE. You can set the ECC extended mode on site or remotely. When setting the ECC extended mode remotely, you need to set client NEs first and then server NEs under the condition that communication between NEs and the NMS is normal. When setting the ECC extended mode remotely, set an NE without the supervisory channel (ESC or OSC) first and then an NE with the supervisory channel (ESC or OSC). In the case of an NE without the supervisory channel, the NE is unreachable and communication between the NMS and the NE fails after the ECC extended mode is set remotely. The communication is restored automatically after an NE with the supervisory channel at the same station as the NE without the supervisory channel is set. For example, a station has ten NEs. The supervisory channel (ESC or OSC) is configured on NE A. Figure 5-5 shows the network topology. Table 5-1 provides the IP addresses of the NEs and the ECC setting plan. NE A is the server NE. NE I is a client NE of NE A and the server NE of NE J. Figure 5-5 NE connections at a station

DCN

A

B

C

D

J

I

H

G

E

F

NOTE

NEs at the station are cascaded by network cables.

Issue 01 (2011-10-20)


35



Table 5-1 ECC setting plan NE Name

NE IP Address

Configuration on the Server

Configuration on the Client

IP Address

Port

Opposite IP Address

Port

A

10.0.0.1

0.0.0.0

1601

-

-

B

10.0.0.2

-

-

10.0.0.1

1601

C

10.0.0.3

-

-

10.0.0.1

1601

D

10.0.0.4

-

-

10.0.0.1

1601

E

10.0.0.5

-

-

10.0.0.1

1601

F

10.0.0.6

-

-

10.0.0.1

1601

G

10.0.0.7

-

-

10.0.0.1

1601

H

10.0.0.8

-

-

10.0.0.1

1601

I

10.0.0.9

0.0.0.0

1602

10.0.0.1

1601

J

10.0.0.10

-

-

10.0.0.9

1602

When setting the extended ECC communication mode at the station remotely, observe the following sequence: J → I client → H, G, F, E, D, C, and B → A server → I server During the configuration, the status of the communication between the NMS and NEs changes frequently. l

After the setting on NE J is complete, the communication between the NMS and NE J fails.

l

After the setting on NE I client is complete, the communication between the NMS and NE I fails.

l

After the settings on NEs H, G, F, E, D, C, and B are complete, the communication between the NMS and NEs H, G, F, E, D, C, and B fails.

l

After the setting on NE A server is complete, the communication between the NMS and NEs B, C, D, E, F, G, H and I is restored automatically.

l

After the setting on NE I server is complete, the communication between the NMS and NE J is restored automatically.

Issue 01 (2011-10-20)


36



Precautions

CAUTION When setting the ECC extended mode remotely, ensure that the configuration sequence is correct. That is, modify the ECC extended mode of opposite non-gateway NEs first and then the ECC extended mode of the gateway NE. Otherwise, the communication between the NMS and the unreachable NE cannot be restored automatically. In this case, onsite resetting is required.

CAUTION Do not set the extended ECC mode for the communication between gateway NEs of subnets. In addition, you are recommended not to set a gateway NE but an NE closest to the gateway NE as a server NE.

CAUTION To ensure normal communication, the ECC extended mode of the NEs that adopt the Ethernet extended ECC communication must match. The match requirements are as follows: l If you set the ECC extended mode to automatic mode for an NE, you need to set the ECC extended mode also to automatic mode for the opposite NE. l If you set the ECC extended mode to specified mode for an NE, you need to set the ECC extended mode also to specified mode for the opposite NE. In addition, the two NEs must be of the client-server relationship. That is, if an NE serves as the server, the opposite NE must be the client. NOTE

When setting the ECC extended mode remotely, you are recommended to work out the ECC setting plan in advance to ensure that the settings are correct.


Query and record the IP addresses of the server NEs specified in ECC planning. (1) In the NE Explorer, select the NE and choose Communication > Communication Parameters from the Function Tree. (2) Click Refresh. Then view the current IP address of the NE.

2.

Correctly plan the sequence for setting extended ECC modes on NEs, and then set the ECC extended modes for client and server NEs by strictly complying with the sequence. (1) In the NE Explorer, select the NE and choose Communication > ECC Management from the Function Tree. (2) Click Query and check the current ECC mode of the NE. (3) In the right function panel, set ECC Extended Mode to Specified mode.

Issue 01 (2011-10-20)


37



l For a client NE, set extended ECC according to steps 2.4 and 2.5. l For a server NE, set extended ECC according to steps 2.6 and 2.7. l For an NE that serves as both client and server, set extended ECC for the client according to steps 2.4 and 2.5 and for the server according to steps 2.6 and 2.7. (4) In the Set Client area, enter the IP address and port number of the server NE in the Opposite IP field and Port fields respectively. NOTE

l The IP address of each NE must be unique and on the same subnet. l A client NE can serve as the server NE for NEs at a lower level. In this case, the server and client ports of the NE must be different. That is, the port number that is set in the Set Client area is used for the communication between the NE and the server NE and must be different from the port number set for the server of the NE. l The port number is in the range of 1601 to 1699, for example, 1610.

(5) Click Apply in the Set Client area to complete the setting of the extended ECC on the client NE. NOTE

If the client NE is set remotely, the NE is unreachable and the communication between the NMS and NE fails. After the ECC extended mode on the server NE of the client NE is set correctly, the communication restores automatically.

(6) In the Set Server area, enter the port number that is the same as the port of the client NE in the Port field. NOTE

l The port number is used by the local NE for communication with the client NE. l The port number of the server NE must be the same as the port number of the client NE.

(7) Click Apply in the Set Server area to complete the setting of the extended ECC on the server NE. 3.

Optional: Disable the DCN function of the vacant slots. (1) In the NE Explorer, select the NE and choose Communication > DCC Managementfrom the Function Tree. (2) Choose the DCC Parameters tab, and set DCC Status of Vacant Slot to Disabled. (3) Click Apply. NOTE

If they are required in a subsequent phase, insert the board into the subrack and add the logical board. And then, enable the DCN channel of the board in DCC Management tab.


Obtaining the IP Address of an NE Onsite If you fail to query the IP address of an NE on the U2000 or Web LCT on site, see this section to obtain the IP address of an NE.



38



5.7 Configuring IP over DCC When the network planning adopts the IP over DCC mode for communication, you need to configure the DCC channel and check whether the IP routes are correct in the commissioning and configuration.

Prerequisite The communication between NEs must be normal. The IDs and IP addresses of NEs must be set. The communication between the NMS and NEs must be normal.



Create a DCC channel. When creating a DCC channel, you need to specify the interface, channel type, and protocol of the channel. When configuring IP over DCC: l Select a line interface or an external clock interface as the port of the DCC channel according to actual network planning. l Set the channel type to the same as the channel used by the interconnected third-party equipment. If a network consists of only the OptiX OSN 1800 equipment, it is recommended to use the default channel type (GCC0) for OTU boards. l Set the protocol type to TCP/IP. NOTE

If a DCC channel is available, change Protocol Type of the channel to TCP/IP.

(1) In the NE Explorer, select the NE and choose Communication > DCC Management from the Function Tree. (2) Click the DCC Management tab and click Create. (3) In the displayed dialog box, set the Port, Channel, and Protocol Type fields. (4) Click Apply to complete configuring the DCC channel of the NE. 2.

Query IP routes. Check whether the IP routes and their parameters in the routing table are the same as planed. In normal situation, a gateway NE must have the routes to the IP addresses of all the nongateway NEs that are managed by the gateway NE and the route to the Web LCT or U2000 server. (1) In the NE Explorer, select an NE and choose Communication > IP Stack Protocol Management from the Function Tree. (2) Click the IP Route Management tab, and then view the IP routes.

3. Issue 01 (2011-10-20)

Optional: Disable the DCN function of the vacant slots. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

39



(1) In the NE Explorer, select the NE and choose Communication > DCC Managementfrom the Function Tree. (2) Choose the DCC Parameters tab, and set DCC Status of Vacant Slot to Disabled. (3) Click Apply. NOTE



Enabling the Proxy ARP Generally, the NMS accesses NEs on the entire network through gateway NEs. To enable the NMS to access remote NEs directly through the IP network layer, you need to first enable the proxy ARP function of a gateway NE, and then configure a static route to the NMS on each remote NE.

l

Configuring the IP Static Route for an NE You need to enable the proxy ARP function of the gateway NE of an NE before configuring the IP static route for the NE.

l

Querying the OSPF Protocol Status If certain IP routes are unavailable, contact Huawei engineers to adjust the OSPF protocol parameters used by the NEs. Ensure that the OSPF function is available to all the NEs.


5.8 Configuring OSI over DCC When a network adopts OSI over DCC for communication, configure DCC channels and the protocol parameters of each OSI layer on each NE to ensure normal DCN communication.

Prerequisite The NE ID must be set. The communication between NEs must be normal. The communication between the NMS and NEs must be normal.


Issue 01 (2011-10-20)


40



Precautions

CAUTION Remote NEs will be unreachable to the NMS in the configuration process of OSI over DCC. Therefore, configure the NEs one by one according to the sequence from far to near when remotely configuring OSI over DCC.


Change the protocol type and set the LAPD role for each DCC channel. Set the physicallayer and data link-layer protocol parameters of the OSI protocol stack. When a network adopts OSI over DCC for communication, set the protocol type of a DCC channel to OSI and set the LAPD role at one end of a DCC channel to User and the LAPD role at the other end to Network. When creating a DCC channel, specify the port, channel type, protocol type, and LAPD roles of the DCC channel. When configuring OSI over DCC, take the following precautions: l Select a line port as the resident port of a DCC channel based on the actual network planning. l Set the channel type to the same as the channel type set on the interconnected thirdparty equipment. If a network consists of only the OptiX OSN 1800 equipment, it is generally recommended to set the channel type of an OTU board to the default value GCC0. l Set the protocol type to OSI. l For the two ends of a DCC channel, set the LAPD role to User at one end and to Network at the other end. Generally, DCC channels have been automatically created. If DCC channels are deleted, you can create them again. (1) In the NE Explorer, select the NE and choose Communication > DCC Management from the Function Tree. (2) Click the DCC Management tab and click Create. (3) In the displayed dialog box, set the Port, Channel, and Protocol Type fields. (4) Click Apply to complete configuring the DCC channel of the NE.

2.

Set the node type of an NE and the network-layer protocol parameters of the OSI protocol stack based on the network planning. The node type of an NE can be ES, L1, and L2. l The default node type of an NE is L1. l If inter-domain routing is required, change the node type of an NE to L2. Generally, set two L2 NEs (whose node types are L2) in a domain so that the two NEs function as mutual backup. TIP

All gateway NEs (GNEs) are L2 NEs.

For convenient network expansion, it is not recommended to set the node type of an NE to ES. Issue 01 (2011-10-20)


41



(1) Select an NE in the NE Explorer. Choose Communication > OSI Management from the Function Tree. (2) Click the Network Layer Parameters tab and set the CLNS role. (3) Click Apply and click OK in the Confirm dialog box. A message is displayed indicating that the SCC board will be reset. (4) Click Close in the Operation Result dialog box. 3.

Set the network service access point (NSAP) domain address of each NE and the transportlayer protocol parameters of the OSI protocol stack based on the network planning. The NSAP domain addresses of NEs in the same L1 domain must be the same. If a GNE communicates with the NMS by using the TP4 protocol of the OSI protocol stack, the communication between the GNE and the NMS will be interrupted after you change the NSAP domain address of an NE. Therefore, it is recommended to set the communication mode between a GNE and the NMS to IP gateway mode, and then change the communication mode to TP4 after configuring the NSAP domain address of each NE. (1) In the NE Explorer, Select Communication > Communication Parameters from Function Tree. (2) Enter the NSAP address, and click Apply. (3) Click OK after the Warning dialog box pops up. (4) Click OK after the dialog box about communication interruption between NEs pops up. (5) Click Close after the Result dialog box is displayed.

4.

Set a GNE to the OSI GNE based on the network planning. When setting a GNE to the OSI GNE, specify the NSAP address and transport service access point (TSAP) of the GNE. TSAP is the port number that is used by the GNE for the TP4 protocol communication. The default value of TSAP is 8888 and cannot be changed. After setting a GNE to the OSI GNE, start the NMS or router connected to the GNE and set the relevant OSI protocol parameters for the NMS or router to ensure normal communication between the GNE and the NMS or router. Generally, it is recommended to set a GEN to the IP GNE, reducing configurations on the interconnected NMS or router. (1) Choose Administration > DCN Management from the Main Menu. (2) Close the displayed Filter NE dialog box. Click the GNE tab. (3) Select the GNE to be modified in the displayed Filter GNE dialog box. The NE is shown in list of GNE tab. (4) Select the NE in the list, right-click and choose Modify GNE from the shortcut menu. (5) In the Modify GNE dialog box displayed, set the parameters. (6) Click OK. In the Warning dialog box that is displayed, click OK.

5.

Query the OSI routes and check whether the OSI routes and their parameters in the routing table are the same as planed. (1) In the NE Explorer, select an NE and choose Communication > IP Stack Protocol Management from the Function Tree. (2) Click the IP Route Management tab, and then view the IP routes. In normal cases: l The L1 routing table of an L1 NE contains routes to all NEs in the local domain.

Issue 01 (2011-10-20)


42



l The L1 routing table of an L2 NE contains routes to all NEs in the local domain and the L2 routing table of the L2 NE contains routes to all other L2 NEs. l A GNE has the route to the NMS and the routes to all L2 NEs in the domain where the NMS is located. l A GNE has the routes to all non-GNEs. 6.

Optional: Disable the DCN function of the vacant slots. (1) In the NE Explorer, select the NE and choose Communication > DCC Managementfrom the Function Tree. (2) Choose the DCC Parameters tab, and set DCC Status of Vacant Slot to Disabled. (3) Click Apply. NOTE


Reference Information See the Feature Description to understand more about OSI over DCC.


5.9 Connecting to the SCC Board Through a Serial Port When the SCC board of an NE connects to an external AC power supply, an outdoor cabinet, or a sensor system such as the access control or temperature control system through a serial port, you must set the serial port on the NE to ensure normal communication between the SCC board and the external equipment.

Prerequisite Power cables for connecting external equipment to the SCC board must be proper.


Background Information Different serial ports are used by the SCC board to connect to different sets of external equipment: l

Use the ETH2&OAM port to connect to an external AC power supply.

l

Use the SW&RS485 port to connect to an outdoor cabinet or a sensor system such as the access control or temperature control system.

Select a proper connection mode for the external equipment as follows: l Issue 01 (2011-10-20)

Select AC external power supply for an external AC power supply. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

43



l

Select Outdoor cabinet power supply for an outdoor cabinet.

l

Select Switch for a sensor system such as the access control or temperature control system.


In the NE Explorer, select an NE and choose Communication > Access Control.

2.

In the Serial Port Access Control area, select the required object.

3.

Click Apply to complete the settings.

Reference Information See Quick Installation and Commissioning Guide to understand the detailed procedure for installing serial port cables.


5.10 Configuring Board Parameters Different boards implement different functions, and therefore you need to configure different parameters in the commissioning and configuration for deployment. Set parameters appropriately for each board according to the actual network. The section describes only the parameter values that you need to configure in the commissioning and configuration for deployment. For the specific functions and working principles of the boards, see the Hardware Description.

5.10.1 ELOM Parameters Prerequisite You must have logged in to the NE where the board resides.


Precautions When gray optical modules are used on the WDM side of a board, change the port type to Line Side Grey Optical Port on the U2000. For details, see Changing Port Types.

Navigation Path 1.

In the NE Explorer, select the board and then choose Configuration > WDM Interface from the Function Tree.

2.

Select a proper navigation path according to the parameters. The details are as follows:

Issue 01 (2011-10-20)


44



l In the case of a parameter at channel level, select By Board/Port(Channel), choose Channel from the drop-down list, and click the Basic Attributes or Advanced Attributes tab. Then, you can query or set the corresponding parameter. l In the case of a parameter at board level, select By Board/Port(Channel) and choose Board from the drop-down list. Then, you can query or set the corresponding parameter. NOTE

You can also select By Function and then choose the required parameter from the drop-down list.

Background Information Timeslots can be set for services when the ELOM(COMP) board works in 1*AP8 ODU1 mode or when the TNF2ELOM board works in 1*AP8 common mode and the ports on the board work in ODU1 convergence mode. The number of timeslots that are occupied by services varies according to service types. Each ODU1 service requires 16 timeslots; therefore, the total number of timeslots occupied by all client-side services that are converged into an ODU1 service must be 16 or smaller. Table 5-2 lists the number of timeslots required by common services. Table 5-2 Number of timeslots required by common services Service Type

Number of Timeslots Required

Service Type


GE(GFP_T)/GE (TTT-AGMP)

7

FICON

6

STM-1

1

FICON EXPRESS

12

STM-4

4

ESCON

2

STM-16

16

DVB-ASI

2

FC200

12

SDI

3

FC100

6

HDSDI

12

FE

1

HDSDI14835

12

OTU1

16

-

-

Precautions

CAUTION If you delete a logical ELOM board and configure it again on the NMS, the original configuration of the board is deleted and the default configuration is restored.

Issue 01 (2011-10-20)


45



Parameter Description Field

Value

Description

Board Working Mode

F2ELOM(COMP):

F2ELOM(COMP):

l 1*AP8 ODU1 mode, 1*AP4 ODU1 mode, 1*AP1 ODU2 mode, 1*AP2 ODU2 mode, 1*AP8 ODU0&ODU1 mode

l 1*AP8 ODU1 mode: The ELOM board supports ODU1 service encapsulation and the received client services can be mapped into one ODU1 service.

l Default: 1*AP4 ODU1 mode F2ELOM(STND): l 1*AP8 general mode, 1*AP1 ODU2 mode, 1*AP2 ODUflex mode l Default: 1*AP8 general mode

l 1*AP4 ODU1 mode: The ELOM board supports ODU1 service encapsulation but the received client services must be mapped into different ODU1 services. l 1*AP1 ODU2 mode: The ELOM board supports access of one client service and maps the client service into one ODU2 service. l 1*AP2 ODU2 mode: The ELOM board supports access of two client services and maps the two client services into one ODU2 service. l 1*AP8 ODU0&ODU1 mode: The ELOM board supports access of eight client services and maps the eight client services into ODU0 and ODU1 service. F2ELOM(STND): l 1*AP8 general mode: The ELOM board supports ODU0, ODU1 and ODUflex service encapsulation. l *AP1 ODU2 mode: The ELOM board supports ODU2 service encapsulation. l 1*AP2 ODUflex mode: The ELOM board supports ODUflex service encapsulation. CAUTION The signal flow and functions of the ELOM board vary according to the working modes. Switching between different working modes will interrupt services that are running in the current working mode.

Issue 01 (2011-10-20)


46



Field

Value

Description

Port Working Mode

F2ELOM(COMP):

For F2ELOM(COMP), this parameter is valid when Board Working Mode is set to 1*AP8 ODU0&ODU1 mode.

l ODU1 nonconvergence mode (OTU1/ Any->ODU1), ODU0 nonconvergence mode (Any>ODU0), None (Not for Ports) l Default: ODU1 non-convergence mode (OTU1/ Any->ODU1) F2ELOM(STND): l ODU0 nonconvergence mode (Any>ODU0), ODU1 convergence mode (n*Any>ODU1), ODU1 non-convergence mode (OTU1/ Any->ODU1), ODUflex nonconvergence mode (Any>ODUflex), None (Not for Ports)

l ODU1 non-convergence mode (OTU1/Any>ODU1): client services are mapped into ODU1 services. l ODU0 non-convergence mode (Any->ODU0): client services are mapped into ODU0 services. l None (Not for Ports): reserved mode. For F2ELOM(STND), this parameter is valid when Board Working Mode is set to 1*AP8 general mode. l ODU0 non-convergence mode (Any->ODU0): client services are mapped into different ODU0 services. l ODU1 convergence mode (n*Any->ODU1): client services are mapped into one ODU1 services. l ODU1 non-convergence mode (OTU1/Any>ODU1): client services are mapped into different ODU1 services. l ODUflex non-convergence mode (Any>ODUflex): client services are mapped into different ODUflex services. l None (Not for Ports): reserved mode.

l The default mode of ports 201, 203, 205, and 207 is ODU1 nonconvergence mode. The default mode of ports 202, 204, 206, and 208 is None (not for ports).

Issue 01 (2011-10-20)


47



Field

Value

Description

Service Type

None, FE, GE(TTTAGMP), GE(GFP-T), 10GE_LAN, FC-100, FC-200, FC-400, FC-800, Infiniband 2.5G, CPRI2, CPRI3, 10GE WAN, STM-64, FC1200, DVB-ASI, HD-SDI, 3G-SDI, CPRI6, CPRI7, FC1200, FICON 10G, STM-1, STM-4, STM-16, FICON, FICON EXPRESS, ESCON, OTU-1

The Service Type parameter sets the type of the service accessed at the optical interface on the client side. NOTE l After you configure a cross-connection for the board, setting the Service Type field fails if the service type selected during cross-connection configuration is different from the value you set for Service Type. In this case, you need to delete the cross-connection and set the Service Type field again. l The service type supported by the ELOM board varies according to the value of Working Mode. l Only the ELOM(COMP) board supports Infiniband 2.5G services and only the ELOM(STND) board supports 10GE WAN, STM-64, FC1200, DVB-ASI, HD-SDI, 3G-SDI, CPRI6, and CPRI7 services.

Default: l The default service type for optical ports 3 (RX1/TX1), 5 (RX3/TX3), 7 (RX5/TX5) and 9 (RX7/TX7) is OTU-1. l The default service type for other optical ports is None. Port Mapping

Bit Transparent Mapping (11.1 G), MAC Transparent Mapping (10.7 G) Default: Bit Transparent Mapping (11.1 G)

This parameter is valid when Service Type is set to 10GE LAN. l When a board is used to transparently transmit synchronous Ethernet services, this parameter must be set to Bit Transparent Mapping (11.1 G). l Select Bit Transparent Mapping (11.1 G) when there are OTU2e signals on the WDM side. l Select MAC Transparent Mapping (10.7 G) when there are OTU2 signals on the WDM side. NOTE l Port mapping of the two boards that are interconnected with each other must be consistent.

Issue 01 (2011-10-20)


48



Field

Value

Description

Channel Use Status

Used, Unused

l Set this parameter to Unused when a channel that is not used.

Default: Used

l Set this parameter to Used when a channel that is used. For example, if the ELOM board works in 1*AP2 ODU2 mode, set the status of the TX1/RX1 optical port to Used and the status of the TX5/RX5 optical port to Unused when only the TX1/RX1 optical port receives services. Automatic Laser Shutdown

Enabled, Disabled

l The default value is recommended.

Default: Enabled

l On the WDM side, this automatic laser shutdown function is not supported and therefore cannot be set or query.

Hold-Off Time of Automatic Laser Shutdown

0s to 2s, with a step of 100 ms.

The default value is recommended.

Laser Status

ON, OFF

Default: 0s

Default: l WDM side: ON l Client side: OFF

The default value is recommended. In practical application, set this parameter according to the scenario where the board is used. CAUTION When NEs communicate with each other through the electric supervisory channel (ESC) of ELOM, the NEs will be unreachable if all the lasers at ports IN1/OUT1 and IN2/OUT2 on the WDM side of the ELOM board are disabled.

FEC Working Enabled, Disabled State Default: Enabled

l Enabled is recommended.

FEC Mode

This parameter is available only when you set FEC Working State to Enabled.

FEC, EFEC Default: FEC

l FEC Working State of the two interconnected OTU boards must be consistent.

l The default value is recommended. To improve the error correction capability, set this parameter to EFEC. l FEC Mode of the two boards that are interconnected on the WDM side must be consistent. Otherwise, services are interrupted. NOTE The actual value is AFEC-2, but EFEC is displayed on the NMS.

Issue 01 (2011-10-20)


49



Field

Value

Description

Optical Interface Loopback

Non-Loopback, Inloop, Outloop

Set this parameter to Non-Loopback when a network works normally. It can be set to Inloop or Outloop to help locate a faulty point in a test or a process of removing a fault on a network. However, it must be set to Non-Loopback right after the test is complete or the fault is removed.

Default: NonLoopback

When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. Optical Interface Attenuation Ratio (dB)

0 to 20 Default: 20

parameter provides an option to set the optical power attenuation of a board channel so that the optical power of the output signals at the transmit end is within the preset range. NOTE This parameter is only supported by the F2ELOM (STND).

Max. Attenuation Ratio (dB)

20 Default: 20

parameter provides an option to query the maximum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the F2ELOM (STND).

Min. Attenuation Ratio (dB)

0 Default: 0

parameter provides an option to query the minimum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the F2ELOM (STND).

Max. Packet Length

1518-9600

SD Trigger Condition

SM_BIP8_SD, PM_BIP8_SD, B1_SD

Default: 9600

Default: None

Issue 01 (2011-10-20)

This parameter is valid only when Service Type is set to 10GE LAN, and when Port Mapping is set to MAC Transparent Mapping (10.7 G). It is recommended that you use the default value. This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions.


50



Field

Value

Description

LPT Enabled

Enabled, Disabled

The board supports the LPT function only when Service Type is set to FE, GE(TTT-AGMP), GE (GFP-T) or 10GE LAN.

Default: Disabled

l The LPT function can work only with intraboard 1+1 protection or ODUk SNCP protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter. PRBS Test Status

Enabled, Disabled Default: /

l Retain the default value when a network works normally. l Set this parameter to Enabled for the auxiliary board if you need to perform a PRBS test during deployment commissioning. Set this parameter to Disabled after the test is complete.

ODU Timeslot Configuratio n Mode

Assign random, Assign consecutive Default: Assign random

l In Assign consecutive mode, the service mapping path can be as follows: ODU0 –> ODU1 –> ODU2 or ODU1–>ODU2. l In Assign random mode, the service mapping path can be as follows: ODU0–>ODU2 or ODUflex–>ODU2. NOTE This parameter is supported only when the ELOM(STND) board works in 1*AP8 general mode.

Planned Wavelength No./ Wavelength (nm)/ Frequency (THz)

The parameter format is as follows: wavelength No./ optical port wavelength/ frequency, for example, 60/1552.52/193.100.

This parameter is used to set the wavelength and frequency only when the board uses TXFP modules on the WDM side.

Default: / Planned Band Type

C, CWDM

Band Type/ Wavelength No./ Wavelength (nm)/ Frequency (THz)

The parameter format is as follows: band type/wavelength No./ optical port wavelength/ frequency, for example, C/ 11/1471.00/208.170.

Default: C

This parameter is available only when the board uses TXFP modules and must be set to C. This parameter is for query only.

Default: /

Issue 01 (2011-10-20)


51



Field

Value

Description

Band Type

C, CWDM

This parameter is for query only.

Default: / Optical Interface/ Channel

-

-

Optical Interface Name

-

-

5.10.2 LDE Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.

Select a proper navigation path according to the parameters. The details are as follows: l In the case of a parameter at channel level, select By Board/Port(Channel), choose Channel from the drop-down list, and click the Basic Attributes or Advanced Attributes tab. Then, you can query or set the corresponding parameter. l In the case of a parameter at board level, select By Board/Port(Channel) and choose Board from the drop-down list. Then, you can query or set the corresponding parameter. NOTE


Issue 01 (2011-10-20)


52




Value

Description

Board Mode

ODU0 Mode, NonODU0 Mode

l In Non-ODU0 Mode, services are encapsulated directly into ODU1 signals rather than into ODU0 signals first.

Default: Non-ODU0 Mode

l In the case of the boards that are interconnected on the WDM side and require encapsulation at ODU0 level, set this parameter to ODU0 Mode. In this mode, services are encapsulated into ODU0 signals first and then into ODU1 signals. CAUTION Switching between different working modes on a board interrupts the services.

Service Type

l When Board Mode is set to Non-ODU0 Mode, the following services are supported: GE (GFP_T), EPON_OLT, EPON_ONU, and None.

In case of GE services, select a proper service type according to the source of the GE services.

l When Board Mode is set to ODU0 Mode, the following services are supported: GE (GFP_T), GE (TTT-AGMP), and NONE.

– When a board is used in asynchronous mode, this parameter must be set to GE(GFP_T).

Default: GE(GFP_T)

l When Board Mode is set to Non-ODU0 Mode, this parameter should be set to GE (GFP_T). l When Board Mode is set to ODU0 Mode, – When a board is used to transparently transmit synchronous Ethernet services, this parameter must be set to GE(TTT-AGMP).

In case of EPON services, select a proper service type according to the optical module type. l When the board is configured with an OLT optical module (to interconnect with the ONU side of PON equipment), set this parameter to EPON_ONU. l When the board is configured with an ONU optical module (to interconnect with the OLT side of PON equipment), set this parameter to EPON_OLT. NOTE When the service type changes between EPON_ONU and EPON_OLT, the service type of a channel carrying EPON services must be set to GE(GFP_T) or NONE first. For example, when the board receives four EPON services, the service type must be changed from EPON_ONU to EPON_OLT. In this case, you must set the service types of the four channels to GE(GFP_T) or None before you change the service type to EPON_OLT.

If no services are received at the board, you can set this parameter to None. In this case, the board does not report electrical-layer alarms on the channel.

Issue 01 (2011-10-20)


53



Field

Value

Description

Synchronous/ Asynchronou s Mode

Synchronous Mode, Asynchronous Mode

This parameter is valid only when Board Mode is set to ODU0 Mode.

Default: Asynchronous Mode

l When Service Type is GE(TTT-AGMP), it is recommended to set this parameter to Synchronous Mode, providing better performance for transparent transmission of clock. l When Service Type is GE(GFP_T), retain the default value for this parameter. The boards that are interconnected with each other must be in the same mode for transparent transmission of clock.

ALS Overhead Use Mode

Standard Mode, Compatible Mode (52TOM) Default: Standard Mode

Channel Use Status

Used, Unused Default: Used

This parameter is valid only when Board Mode is set to ODU0 Mode. l Generally, retain the default value for this parameter. l When the LDE board is interconnected with the TN52TOM board for NG WDM products, set this parameter to Compatible Mode (52TOM). l Set this parameter to Unused when a channel that is not used. l Set this parameter to Used when a channel that is used.

Automatic Laser Shutdown

Enabled, Disabled


Default: Enabled for client-side optical ports.





Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LDE board, do not disable the WDM-side lasers on the LDE board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.

Issue 01 (2011-10-20)


54


Field

Value



Description l Enabled is recommended. l FEC Working State of the two interconnected OTU boards must be consistent. NOTE When the client-side optical port on the LDE board receives EPON services, this parameter is unavailable.


Non-Loopback, Inloop, Outloop Default: NonLoopback

Set this parameter to Non-Loopback when a network works normally. It can be set to Inloop or Outloop to help locate a faulty point in a test or a process of removing a fault on a network. However, it must be set to Non-Loopback right after the test is complete or the fault is removed. When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. NOTE The parameter can be set to Inloop or Outloop only when the GE service is accessed.


SM_BIP8_SD, PM_BIP8_SD Default: None

LPT Enabled

Enabled, Disabled Default: Disabled

This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. This parameter is valid when Service Type is set to GE(GFP-T) or GE(TTT-AGMP). l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.




Default: / Band Type

C, CWDM


Default: / Optical Interface/ Channel Issue 01 (2011-10-20)

-

-


55



Field

Value

Description


-

-

5.10.3 LDGF Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.



Precautions TIP

In the case of the LDGF board, you can connect a portable computer to the FE port by using a network cable when the FE port is in Used state. Then issue the ping command for connecting to the opposite client equipment to check whether a normal connection can be established on the channel.

Issue 01 (2011-10-20)


56




Value

Description

Service Type

GE, GE(GFP-T)

l Usually, GE(GFP-T) is recommended. In this mode, the transmission delay is small and all control protocol packets are transparently transmitted.

Default: GE(GFP-T)

l In other cases, set this parameter to GE according to the service encapsulation mode. l Service types of the two boards that are interconnected with each other must be consistent. Channel Use Status


l Set this parameter to Unused when a channel that is not used. l Set this parameter to Used when a channel that is used.


Enabled, Disabled







Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LDGF board, do not disable the WDM-side lasers on the LDGF board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.


Issue 01 (2011-10-20)

l Enabled is recommended. l FEC Working State of the two interconnected OTU boards must be consistent.


57



Field

Value

Description





When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. SD Trigger Condition


This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions.

Max. Packet Length

1518-9600

This parameter is valid only when Service Type is set to GE. The default value is recommended.

AutoNegotiation of GE

Enabled, Disabled

Default: 9600

Default: Disabled

The Auto Negotiation parameter is available only when the Service Type parameter is set to GE. l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group.

Intelligent Fiber Status

Enabled, Disabled Default: Enabled

When a link is faulty, and the fault state must be transparently transmitted to the interconnected client-side equipment, the IF function needs to be enabled. l This parameter is valid only when Service Type of the optical port is set to GE. l This parameter is invalid after the LPT function of the board is enabled.

LPT Enabled


This parameter is valid when Service Type is set to GE or GE(GFP-T). l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.

Issue 01 (2011-10-20)


58



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

5.10.4 LDGF2 Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.

Select a proper navigation path according to the parameters. The details are as follows: l In the case of a parameter at channel level, select By Board/Port(Channel), choose Channel from the drop-down list, and click the Basic Attributes or Advanced Attributes tab. Then, you can query or set the corresponding parameter. l In the case of a parameter at board level, select By Board/Port(Channel) and choose Board from the drop-down list. Then, you can query or set the corresponding parameter.

Issue 01 (2011-10-20)


59



NOTE



Value

Description

Board Working Mode

2 x AP2 ODU0 mode, 2 x AP2 ODU1 mode

l 2 x AP2 ODU0 mode: The ELOM board supports ODU0 service encapsulation.

Default: 2 x AP2 ODU1 mode

l 2 x AP2 ODU1 mode: The ELOM board supports ODU1 service encapsulation. NOTE This parameter is only supported by the TNF2LDGF2.

Service Type

TNF1LDGF2: l GE, GE(GFP-T) l Default: GE(GFPT) TNF2LDGF2: l GE(TTT-AGMP), GE(GFP-T)

Channel Use Status

l Set this parameter according to the service encapsulation mode. Usually, GE(GFP-T) is recommended. In this mode, the transmission delay is small and all control protocol packets are transparently transmitted. l Service types of the two boards that are interconnected with each other must be consistent.

l Default: GE(GFPT)

l For the TNF2LDGF2 board, GE(TTT-AGMP) is supported only when the board works in 2*AP2 ODU0 mode.

Used, Unused


Default: Used

l Set this parameter to Used when a channel that is used.

Issue 01 (2011-10-20)


Enabled, Disabled







Default: 0s


60



Field

Value

Description

Laser Status

ON, OFF

l Usually, this parameter is set to ON for every WDM-side optical port.


l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LDGF2 board, do not disable the WDM-side lasers on the LDGF2 board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.







When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. SD Trigger Condition



Max. Packet Length

1518-9600


Default: 9600

NOTE This parameter is only supported by the TNF1LDGF2.

Issue 01 (2011-10-20)


61



Field

Value

Description


Enabled, Disabled

The Auto Negotiation parameter is available only when the Service Type parameter is set to GE.

Default: Disabled

l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group. NOTE This parameter is only supported by the TNF1LDGF2.



When a link is faulty, and the fault state must be transparently transmitted to the interconnected client-side equipment, the IF function needs to be enabled. l This parameter is valid only when Service Type of the optical port is set to GE. l This parameter is invalid after the LPT function of the board is enabled. NOTE This parameter is only supported by the TNF1LDGF2.

LPT Enabled


This parameter is valid when Service Type is set to GE or GE(GFP-T). l The LPT function can work only with intraboard 1+1 protection or ODUk SNCP protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.

PRBS Test Status


l Retain the default value when a network works normally. l Set this parameter to Enabled for the auxiliary board if you need to perform a PRBS test during deployment commissioning. Set this parameter to Disabled after the test is complete. NOTE This parameter is only supported by the TNF1LDGF2.

Issue 01 (2011-10-20)


62



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

5.10.5 LDX Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.


Issue 01 (2011-10-20)


63



NOTE



Value

Description

Service Type

10GE LAN, 10GE WAN, FC-1200, FICON 10G, FC-800, FICON 8G, STM-64

Select a proper value according to the received services.

Default: 10GE LAN Port Mapping

Bit Transparent Mapping (11.1 G), MAC Transparent Mapping (10.7 G) Default: Bit Transparent Mapping (11.1 G)

This parameter is valid when Service Type is set to 10GE LAN. l When a board is used to transparently transmit synchronous Ethernet services, this parameter must be set to Bit Transparent Mapping (11.1 G). l Select Bit Transparent Mapping (11.1 G) when there are OTU2e signals on the WDM side. l Select MAC Transparent Mapping (10.7 G) when there are OTU2 signals on the WDM side. NOTE Bit Transparent Mapping (11.1 G): Supports transparent bit (11.1 G) transport for 10GE LAN signals. In this port mapping mode, transmission of signals are achieved by increasing the OTU frame frequency. This ensures the encoding gain and correction capability of FEC. In this mode, the bit rate is 11.1 Gbit/s, which is higher than the standard bit rate of OTU2 signals. MAC Transparent Mapping (10.7 G): In this port mapping mode, 10GE LAN signals are encapsulated in the GFP-F format and then are mapped into standard OTU frames. This mode supports transparent transmission of only client 10GE MAC frames. In this mode, the signals are encapsulated in standard OTU2 frames and the bit rate of the signals is 10.71 Gbit/s. In addition, the FEC/AFEC code pattern is applicable to 10GE LAN services in this mode. Originally, the FEC code pattern is intended for 10G SDH services. NOTE l Port mapping of the two boards that are interconnected with each other must be consistent.


Issue 01 (2011-10-20)



64



Field

Value

Description

FEC Mode

FEC, EFEC


Default: FEC

l The default value is recommended. To improve the error correction capability, set this parameter to EFEC. l FEC Mode of the two boards that are interconnected on the WDM side must be consistent. Otherwise, services are interrupted. NOTE The actual value is AFEC-2, but EFEC is displayed on the NMS. Users only can set the FEC mode for WDM-side ports .

Channel Use Status




Enabled, Disabled







Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LDX board, the following situations occur when neither a standby channel is available nor protection is configured: l When the LDX board is used for transparently transmitting the 10 Gbit/s optical signals, the NE becomes unreachable after the lasers at the IN and OUT optical ports on the LDX board are disabled.

Issue 01 (2011-10-20)


65



Field

Value

Description





When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. Max. Packet Length

1518-9600



Default: 9600

Default: None LPT Enabled


This parameter is valid when Service Type is set to 10GE LAN and Port Mapping is set to MAC Transparent Mapping (10.7 G). The default value is recommended. This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. This parameter is valid when Service Type is set to 10GE LAN. l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.

PRBS Test Status







Issue 01 (2011-10-20)

C, CWDM Default: C

This parameter is available only when the board uses TXFP modules and must be set to C.


66



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

5.10.6 LEM18 Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path Do as follows to set WDM-side port parameters on the LEM18 board: 1.


2.

Select a proper navigation path according to the parameters. The details are as follows: l In the case of a parameter at channel level, select By Board/Port(Channel), choose Channel from the drop-down list, and click the Basic Attributes or Advanced Attributes tab. Then, you can query or set the corresponding parameter.

Issue 01 (2011-10-20)


67



l In the case of a parameter at board level, select By Board/Port(Channel) and choose Board from the drop-down list. Then, you can query or set the corresponding parameter. NOTE


Do as follows to set Ethernet port parameters on the LEM18 board: 1.

In the NE Explorer, select the board and choose Configuration > Ethernet Interface Management > Ethernet Interface.

2.

For an external port, select External Port to display the Basic Attributes, Tag Attributes, Network Attributes, or Advanced Attributes tab. Then query or set parameters on the corresponding tab.

3.

For an internal port, select Internal Port to display the Tag Attributes, Network Attributes, or Advanced Attributes tab. Then query or set parameters on the corresponding tab.

Parameter Description (WDM-Side Ports) Field

Value

Description

Service Type

GE, FE, 10GE LAN

Service Type of the two boards that are interconnected with each other must be consistent.

Default: l The default service type at the TX1/RX1 to TX2/ RX2 port is 10GE LAN. l The default service type at the TX3/RX3 to TX18/RX18 port is GE. Board Mode

OTN Mode, 10GE Mode

Board Mode of the two boards that are interconnected with each other must be consistent.

Default: OTN Mode

l OTN Mode: The IN1/OUT1 and IN2/OUT2 ports output OTU2 signals and can receive and process OTU2 signals only. l 10GE Mode: The IN1/OUT1 and IN2/OUT2 ports output 10GE LAN signals and can receive and process 10GE LAN signals only. l When Board Mode is changed, signal output at the IN1/OUT1 and IN2/OUT2 ports immediately changes.

Channel Use Status



Issue 01 (2011-10-20)


68



Field

Value

Description

Laser Status

ON, OFF

Lasers at all ports are generally set to ON.

Default: ON

CAUTION When NEs communicate with each other through the electric supervisory channel (ESC) and Board Mode of the LEM18 board is set to OTN Mode, the NEs will be unreachable if all the lasers at ports IN1/OUT1 and IN2/ OUT2 on the WDM side of the LEM18 board are disabled.


Enabled, Disabled






LPT Enabled

Default: Disabled This parameter is for query only.

Default: 0s

Default: None


Enabled, Disabled


Default: Disabled Synchronous Clock Enabled


Select the required clock port and set its status to Enabled. Users can enable a maximum of six ports and they are 3(IN1/OUT1), 4(IN2/OUT2), 5(TX1/RX1), 6 (TX2/RX2), and two of ports 7(TX3/RX3) to 22 (TX18/RX18).


This parameter is valid only when the Board Mode is set to OTN Mode. l Enabled is recommended. l FEC Working State of the two interconnected OTU boards must be consistent.

FEC Mode

Issue 01 (2011-10-20)

FEC

This parameter is valid only when the Board Mode is set to OTN Mode. It is always set to FEC and cannot be changed.


69



Field

Value

Description





When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. Band Type/ Wavelength No./ Wavelength (nm)/ Frequency (THz)




C, CWDM



-

-


-

-

Parameter Description (Ethernet Ports) Table 5-3 Basic Attributes Field

Value

Description

Port

OTN mode: PORT5 to PORT22

Select a proper port based on actual services.

10GE mode: PORT3 to PORT22 Enabled/ Disabled

Issue 01 (2011-10-20)


The attributes of a port take effect only after the port is enabled. If a port is disabled, the attributes of the port will be invalid and the service at this port will be interrupted.


70



Field

Value

Description

Working Mode

10GE optical port: 10G Full_Duplex LAN. Default: 10G Full_Duplex LAN.

Set this parameter based on actual physical port types and service configurations. The value of this parameter must be consistent with the working mode of the client equipment.

GE optical/electrical port: AutoNegotiation, 1000M Full_Duplex. Default: AutoNegotiation. FE optical port: 100M Full_Duplex. Default: 100M Full_Duplex. FE electrical port: Auto-Negotiation, 10M Half_Duplex, 10M Full_Duplex, 100M Half_Duplex, 100M Full_Duplex. Default: AutoNegotiation. Maximum Frame

1518–9600 Default: 1522

Set this parameter according to actual service configurations. It is recommended that the value be equal to or greater than the user-defined maximum frame length for transmitting data flows.

Port Physical Parameters

Enabled/Disabled, Working Mode, Flow Control, MAC LoopBack, PHY LookBack


MAC LoopBack




When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses.

Issue 01 (2011-10-20)


71



Field

Value

Description

PHY LoopBack




When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses.

Table 5-4 Flow Control Field

Value

Description

Port

OTN mode: PORT5 to PORT22

Select a proper port based on actual services.

10GE mode: PORT3 to PORT22 Autonegotiati on Flow Control Mode

Disabled, Enable Dissymmetric Flow Control, Enable Symmetric Flow Control, Enable Symmetric/ Dissymmetric Flow Default: Disabled

This parameter is available only when the working mode of an Ethernet port is auto-negotiation. l Disabled: The flow control function is disabled in both the transmit and receive directions. l Enable Dissymmetric Flow Control: Flow control frames cannot be received but can be transmitted. l Enable Symmetric Flow Control: Only PAUSE frames can be transmitted and received. l Enable Symmetric/Dissymmetric Flow: The auto-negotiation mechanism determines whether to enable symmetric or asymmetric flow control.

NonAutonegotiati on Flow Control Mode

Disabled, Enable Symmetric Flow Control, Send Only, Receive Only

This parameter is available only when the working mode of an Ethernet port is non-autonegotiation.

Default: Disabled

l Enable Symmetric Flow Control: In nonautonegotiation mode, flow control frames can be transmitted and received.

l The flow control function is disabled in both the transmit and receive directions of a port.

l Send Only: In non-autonegotiation mode, flow control frames can be transmitted only. l Receive Only: In non-autonegotiation mode, flow control frames can be received only.

Issue 01 (2011-10-20)


72



Table 5-5 TAG Attributes Field

Value

Description

Port

OTN mode: PORT5PORT22 or VCTRUNK1VCTRUNK3

Select a proper port based on actual services. NOTE Do not select PORT5 and VCTRUNK3 at the same time.

10GE mode: PORT3-PORT22 or VCTRUNK3 TAG

Tag Aware, Access, Hybrid

This parameter is valid only when Port Attributes is set to UNI.

Default: Tag Aware

Set this parameter based on VLAN IDs carried by supported services and types of required Ethernet services.

Default VLAN ID

1 to 4095

Specifies a default VLAN ID for an untagged packet.

Default: 1

NOTE This parameter is invalid when TAG is set to Tag Aware.

VLAN Priority

0 to 7

Indicates the priority of Default VLAN ID at a port. The priority ascends with the parameter value.

Default: 0

NOTE This parameter is invalid when TAG is set to Tag Aware.

Entry Detection


Determines whether a port detects packets based on the TAG of a port.

Table 5-6 Network Attributes Field

Value

Description

Port



10GE mode: PORT3PORT22 or VCTRUNK3

Issue 01 (2011-10-20)


73



Field

Value

Description

Port Attributes

UNI, C-Aware, SAware

l UNI: The TAG parameter can be set to Tag Aware, Access, or Hybrid.

Default: UNI

l C-Aware: The TAG parameter is invalid. In addition, a port identifies the external VLAN of a tagged packet as a C-VLAN and transparently transmits untagged packets. l S-Aware: The TAG parameter is invalid. In addition, a port identifies the external VLAN of a tagged packet as an S-VLAN and discards untagged packets. NOTE l For EPL services, the default value is UNI. l For QinQ services, this parameter can only be set to C-Aware and S-Aware.

Table 5-7 Advanced Attributes Field

Value

Description

Port



10GE mode: PORT3PORT22 or VCTRUNK3 Enabling Broadcast Packet Suppression

Enabled, Disabled

Broadcast Packet Suppression Threshold

10% to 100%

Default: Disabled

Default: 30%

When this parameter is set to Enabled, broadcast packets are suppressed if the ratio (the bandwidth value of the current port that broadcast packets occupy to the total bandwidth value of the port) is greater than the Broadcast Packet Suppression Threshold value, so that the bandwidth ratio of the current port that broadcast packets occupy is lower than the threshold value. This parameter functions with the Enabling Broadcast Packet Suppression.

5.10.7 LOE Parameters

Issue 01 (2011-10-20)


74



Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.



Issue 01 (2011-10-20)


75




Value

Description

Service Type

None, GE, GE(GFPT), EPON_OLT, EPON_ONU

In case of GE services:

Default: GE(GFP-T)

l Usually, GE(GFP-T) is recommended. In this mode, the transmission delay is small and all control protocol packets are transparently transmitted. l In other cases, set this parameter to GE according to the service encapsulation mode. In case of EPON services: l When the board is configured with an OLT optical module (to interconnect with the ONU side of PON equipment), set this parameter to EPON_ONU. l When the board is configured with an ONU optical module and (to interconnect with the OLT side of PON equipment), set this parameter to EPON_OLT. NOTE When the service type changes between EPON_ONU and EPON_OLT, the service type of a channel carrying EPON services must be set to GE(GFP-T) or NONE first. For example, when the board receives four EPON services, the service type must be changed from EPON_ONU to EPON_OLT. In this case, you must set the service types of the four channels to GE(GFP-T) or None before you change the service type to EPON_OLT.

If no services are received at the board, you can set the service type to None. In this case, the board does not report electrical-layer alarms on the channel. Port Mapping

GFP_OTU2, SDH_OTU2 Default: GFP_OTU2

The default value is recommended. Different service types are supported in the two mapping modes. l GFP_OTU2: None, GE(GFP-T), EPON_OLT, and EPON_ONU are supported. l SDH_OTU2: GE and GE(GFP-T) are supported. NOTE l Port mapping of the two boards that are interconnected with each other must be consistent. l The value of this parameter can be changed only after the service type is set to GE(GFP-T). l When the LOE board is interconnected with the LOG board for NG WDM products, set this parameter to SDH_OTU2.

Issue 01 (2011-10-20)


76



Field

Value

Description

Board Mode

Common Mode, Optical Electrical Separate Mode


Default: Common Mode Channel Use Status


l This parameter must be set to Optical Electrical Separate Mode when the board needs to be compatible with NE software of an old version. In this mode, the logical optical port 201 is available. l Set this parameter to Unused when a channel that is not used. l Set this parameter to Used when a channel that is used.


Enabled, Disabled







Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LOE board, do not disable the WDM-side lasers on the LOE board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.


Issue 01 (2011-10-20)



77



Field

Value

Description





When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. NOTE The parameter can be set to Inloop or Outloop only when GE Service is accessed.

Max. Packet Length

1518-9600


Enabled, Disabled

Default: 9600

Default: Disabled

This parameter is valid only when Service Type is set to GE. The default value is recommended. The Auto Negotiation parameter is available only when the Service Type parameter is set to GE. l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group.






Issue 01 (2011-10-20)



78



Field

Value

Description

LPT Enabled

Enabled, Disabled

This parameter is valid when Service Type is set to GE or GE(GFP-T).

Default: Disabled

l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter. Planned Wavelength No./ Wavelength (nm)/ Frequency (THz)




C, CWDM



Default: C



C, CWDM



-

-


-

-

5.10.8 LQG Parameters Prerequisite You must have logged in to the NE where the board resides. Issue 01 (2011-10-20)


79




Navigation Path 1.


2.




Value

Description

Service Type

GE, GE(GFP-T)

l Set this parameter to a proper value according to the service type of the interconnected board. If Service Type needs to be changed from GE to GE(GFP-T), set Port Mapping to Encapsulated to OTU5G before you change Service Type to GE(GFP-T). In case of GE (GFP-T) services, Port Mapping must be set to Encapsulated to OTU5G.

Default: GE

NOTE After you configure a cross-connection for the board, if the service type that you select when configuring the cross-connection is different from the value you set for the Service Type field, setting the Service Type field fails. In this case, you need to delete the cross-connection and set the Service Type field again.

Port Mapping

Channel Use Status

Encapsulated to FEC5G, Encapsulated to OTU5G

The default value is recommended. Different service types are supported in the two mapping modes.

Default: Encapsulated to FEC5G

l Encapsulated to OTU5G: GE and GE(GFP-T) are supported.

Used, Unused


Default: Used

l Encapsulated to FEC5G: GE is supported.

NOTE Port Mapping of the two boards that are interconnected with each other must be consistent and Service Type of their WDM-side optical ports must be consistent.

l Set this parameter to Used when a channel that is used. Issue 01 (2011-10-20)


80



Field

Value

Description


Enabled, Disabled







Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LQG board, do not disable the WDM-side lasers on the LQG board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.








Issue 01 (2011-10-20)

1518-9600 Default: 9600



81



Field

Value

Description


Enabled, Disabled


Default: Disabled

l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group.





SM_BIP8_SD, PM_BIP8_SD, B1_SD Default: None

LPT Enabled


This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. This parameter is valid when Service Type is set to GE. l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.




Default: Band Type

C, CWDM


Default: /

Issue 01 (2011-10-20)


82



Field

Value

Description

Optical Interface/ Channel

-

-


-

-

5.10.9 LQM Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.



Background Information The service processing chip of the LQM board provides 16 timeslots for receiving services. Different types of services require different number of timeslots. The total number of timeslots for the services received at the LQM board must be smaller than the maximum number of timeslots that the service processing chip can provide. In addition, the total number of timeslots for the services configured at the TX1/RX1, TX2/RX2, TX3/RX3, and TX4/RX4 ports must be not greater than 16. Table 5-8 lists the number of timeslots required by common services. Issue 01 (2011-10-20)


83



Table 5-8 Number of timeslots required by common services Service Type


Service Type


GE/GE(GFP_T)/GE (TTT-AGMP)

7

FICON

6

STM-1

1

FICON EXPRESS

12

STM-4

4

ESCON

2

STM-16

16

DVB-ASI

2

FC200

12

SDI

3

FC100

6

HDSDI

12

FE

1

HDSDI14835

12

FC100_SLICE

8

OTU1

16

FC200_SLICE

16

FICON_SLICE

8

FICON_EXPRESS_ SLICE

16

GE_SLICE

12

In case of GE services, the committed information rate can be configured to change the number of timeslots required. Table 5-9 lists the number of timeslots required by GE services at different bandwidths. Table 5-9 Number of timeslots required by GE services Bandwidth (Mbit/ s)


Bandwidth (Mbit/ s)


931-1000

7

311-465

3

776-930

6

156-310

2

621-775

5

1-155

1

466-620

4

-

-

The TNF1LQM board supports slice services, such as GE_SLICE, FC100_SLICE, FC200_SLICE, FICON_SLICE, and FICON_EXPRESS_SLICE. Compared with common services, slice services feature better performance in transparent transmission of clock but require more timeslots. In practical application, select a proper service type according to the actual conditions. For example, when the LQM board is used to receive FC100 services, select FC100_SLICE if better performance in transparent transmission of clock is required and timeslots are sufficient. Otherwise, select FC100 so that more timeslots can be used to receive other types of services. Issue 01 (2011-10-20)


84



Precautions

CAUTION If you delete a logical LQM board and configure it again on the NMS, the original configuration of the board is deleted and the default configuration is restored.


Value

Description

Board Working Mode

1 x AP4 ODU1 mode, 1 x AP2 ODU0 mode, 1 x AP2 relay mode

l 1 x AP4 ODU1 mode: Supports ODU1 service encapsulation .

Default: 1 x AP4 ODU1 mode

l 1 x AP2 ODU0 mode: Supports ODU0 service encapsulation. l 1 x AP2 relay mode: Supports regeneration of two OTU1 services. NOTE This parameter is only supported by the TNF2LQM.

Port Working Mode

Issue 01 (2011-10-20)

ODU1 convergence mode (n*Any>ODU1), ODU1 nonconvergence mode (OTU1/Any>ODU1)

l ODU1 convergence mode (n*Any->ODU1): client services are mapped into one ODU1 services.

Default: ODU1 convergence mode (n*Any->ODU1)

NOTE This parameter is only supported by the TNF2LQM.

l ODU1 non-convergence mode (OTU1/Any>ODU1): client services are mapped into different ODU1 services.


85



Field

Value

Description

Service Type

TNF1LQM:

The Service Type parameter sets the type of the service accessed at the optical interface on the client side.

l OTU-1, DVBASI, SDI, HDSDI, HDSDI14835, ESCON, FC-100, FC-100 (slice), FC-200, FC-200 (slice), FE, FICON, FICON express, FICON express (slice), FICON (slice), GE, GE(GFP-T), GE_SLICE, STM-1, STM-4, STM-16, None

NOTE For the TNF1LQM board, the encapsulation mode is GFPF when Service Type is set to GE. The service type supported by the TNF2LQM board varies according to the value of Working Mode. For the TNF2LQM board, GE(TTT-AGMP) is supported only when the board works in 1*AP2 ODU0 mode.

l Default: OTU-1 (in the case of the TX1/RX1 port) or None (in the case of the other ports) TNF2LQM: l OTU-1, DVBASI, SDI, HDSDI, HDSDI14835, ESCON, FC-100, FC-200, FE, FICON, FICON express, GE(TTTAGMP), GE (GFP-T), CPRI2, CPRI3, STM-1, STM-4, STM-16, None l Default: OTU-1 (in the case of the TX1/RX1 port) or None (in the case of the other ports)

Issue 01 (2011-10-20)


86



Field

Value

Description

Channel Use Status

Used, Unused


Default: Used

l Set this parameter to Used when a channel that is used. For example, when the TNF1LQM board is used for regenerating OTU1 signals, set Channel Use Status to Unused for the TX2/RX2, TX3/RX3, TX4/RX4, and IN2/OUT2 ports and to Used for the TX1/RX1 and IN1/OUT1 ports.

Issue 01 (2011-10-20)


87



Field

Value

Description


TNF1LQM:


l Enabled, Disabled


l Default: Disabled in the case of TX1/ RX1 ports, Enabled in the case of the other client-side optical ports. TNF2LQM: l Enabled, Disabled l Default: – 1*AP4 ODU1 mode: Enabled in the case of all the client-side optical ports. – 1*AP2 ODU0 mode: Enabled in the case of TX1/ RX1 and TX2/ RX2 ports, Disabled in the case of the other clientside optical ports. – 1*AP2 regeneration mode: Disabled in the case of TX1/ RX1 and TX2/ RX2 ports, Enabled in the case of the other clientside optical ports.


Issue 01 (2011-10-20)



Default: 0s


88



Field

Value

Description

Laser Status

ON, OFF



l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. In practical application, set this parameter according to the scenario where the board is used. For example, when the TNF1LQM board is used for regenerating OTU1 signals, set Laser Status to ON for the TX1/RX1 and IN1/OUT1 port and to OFF for the TX2/RX2, TX3/RX3, TX4/RX4, and IN2/OUT2 optical ports. CAUTION If communication between NEs is achieved through only ESC provided by the LQM board, the following situations occur when neither a standby channel is available nor protection is configured: l When the LQM board is used for converging four services at Any rate, the NE becomes unreachable after the WDM-side lasers on the LQM board are disabled. l When the TNF1LQM board is used for regenerating OTU1 signals, the NE becomes unreachable after the lasers at the TX1/RX1 and IN1/OUT1 ports on the TNF1LQM board are disabled.



Optical Interface Attenuation Ratio (dB)

parameter provides an option to set the optical power attenuation of a board channel so that the optical power of the output signals at the transmit end is within the preset range.

0 to 20 Default: 20


NOTE This parameter is only supported by the TNF2LQM.


20 Default: 20

parameter provides an option to query the maximum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the TNF2LQM.


0 Default: 0

parameter provides an option to query the minimum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the TNF2LQM.

Issue 01 (2011-10-20)


89



Field

Value

Description

Guaranteed Bandwidth for ClientSide GE Service (M)

1-1000

l Users determine the guaranteed bandwidth for GE services based on the needs. This parameter needs to be configured only for GE services.

Default: 1000

l The value of the Guaranteed Bandwidth for Client-Side GE Service (M) parameter must be greater than the actual service bandwidth of users. Only in this case, no packet loss can be ensured. l Retain the default value when timeslots are sufficient. l When timeslots are insufficient, decrease the committed information rate (CIR) of GE services to decrease the number of required timeslots. This is to ensure that the total number of timeslots is within the required range. For example, when the TX1/RX1, TX2/RX2, TX3/ RX3, and TX4/RX4 ports are used to receive GE services, the CIR can be set to 620 Mbit/s. In this case, each GE service uses four timeslots. Hence, the total number of timeslots required by the services received at the TX1/RX1, TX2/ RX2, TX3/RX3, and TX4/RX4 ports is not greater than 16. NOTE This parameter is only supported by the TNF1LQM.



Set this parameter to Non-Loopback when a network works normally. It can be set to Inloop or Outloop to help locate a faulty point in a test or a process of removing a fault on a network. However, it must be set to Non-Loopback right after the test is complete or the fault is removed. When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses.

Max. Packet Length

1518-9600 Default: 9600

l This parameter is valid only when Service Type is set to GE or FE. l The default value is recommended. NOTE This parameter is only supported by the TNF1LQM.

Issue 01 (2011-10-20)


90



Field

Value

Description


Enabled, Disabled


Default: Disabled

l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group. NOTE This parameter is only supported by the TNF1LQM.



When a link is faulty, and the fault state must be transparently transmitted to the interconnected client-side equipment, the IF function needs to be enabled. l This parameter is valid only when Service Type of the optical port is set to GE. l This parameter is invalid after the LPT function of the board is enabled. NOTE This parameter is only supported by the TNF1LQM.



LPT Enabled


This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. This parameter is valid when Service Type is set to GE or GE(GFP-T). l The LPT function can work only with intraboard 1+1 protection or ODUk SNCP protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.

PRBS Test Status



Issue 01 (2011-10-20)


91



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

5.10.10 LQM2 Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path 1.


2.


Issue 01 (2011-10-20)


92



NOTE


Background Information The LQM2 board has two service processing chips, each of which provides 16 timeslots for receiving services. Different types of services require different number of timeslots. The total number of timeslots for the services received at the LQM2 board must be smaller than the maximum number of timeslots that the service processing chip can provide. l

In 2LQM mode, the total number of timeslots for the services configured at the TX1/RX1, TX2/RX2, TX3/RX3, and TX4/RX4 ports must be not greater than 16 and the total number of timeslots for the services configured at the TX5/RX5, TX6/RX6, TX7/RX7, and TX8/ RX8 ports must be not greater than 16.

l

In AP8 mode, the total number of timeslots for the services configured at all client-side ports must be not greater than 16.

Table 5-10 lists the number of timeslots required by common services. Table 5-10 Number of timeslots required by common services Service Type


Service Type


GE/GE(GFP_T)/GE (TTT-AGMP)

7

FICON

6

STM-1

1

FICON EXPRESS

12

STM-4

4

ESCON

2

STM-16

16

DVB-ASI

2

FC200

12

SDI

3

FC100

6

HDSDI

12

FE

1

HDSDI14835

12

FC100_SLICE

8

OTU1

16

FC200_SLICE

16

FICON_SLICE

8

FICON_EXPRESS_ SLICE

16

GE_SLICE

12

In case of GE services, the committed information rate can be configured to change the number of timeslots required. Table 5-11 lists the number of timeslots required by GE services at different bandwidths.

Issue 01 (2011-10-20)


93



Table 5-11 Number of timeslots required by GE services Bandwidth (Mbit/ s)


Bandwidth (Mbit/ s)


931-1000

7

311-465

3

776-930

6

156-310

2

621-775

5

1-155

1

466-620

4

-

-

The TNF1LQM2 board supports slice services, such as GE_SLICE, FC100_SLICE, FC200_SLICE, FICON_SLICE, and FICON_EXPRESS_SLICE. Compared with common services, slice services feature better performance in transparent transmission of clock but require more timeslots. In practical application, select a proper service type according to the actual conditions. For example, when the LQM2 board is used to receive FC100 services, select FC100_SLICE if better performance in transparent transmission of clock is required and timeslots are sufficient. Otherwise, select FC100 so that more timeslots can be used to receive other types of services.

Precautions

CAUTION If you delete a logical LQM2 board and configure it again on the NMS, the original configuration of the board is deleted and the default configuration is restored.

Issue 01 (2011-10-20)


94




Value

Description

Board Working Mode

l TNF1LQM2:

TNF1LQM2:

– AP8 Mode, 2LQM Mode – Default: 2LQM Mode l TNF2LQM2:

l 2LQM Mode: the LQM2 board is used for converging double four services at Any rate or regenerating two channels of OTU1 signals. In this mode, two channels of signals are sent on the WDM side in a single-fed and single receiving manner.

– 1*AP8 ODU1 mode, 2*AP4 ODU1 mode, 2*AP2 ODU0 mode, 2*AP3 ODU1 mode

l AP8 Mode: the LQM2 board is used for converging eight services at Any rate or regenerating one channel of OTU1 signals. In this mode, signals are sent by optical ports on the WDM side in a dual fed and selective receiving manner.

– Default: 2*AP4 ODU1 mode

TNF2LQM2: l 1 x AP8 ODU1 mode: the LQM2 board is used for converging eight services at Any rate and ODUk (k=1) SNCP protection is supported. In this mode, signals are sent by optical ports on the WDM side in a dual fed and selective receiving manner. l 2 x AP4 ODU1 mode: the LQM2 board is used for converging double four services at Any rate and ODUk (k=1) SNCP protection is supported. In this mode, two channels of signals are sent on the WDM side in a singlefed and single receiving manner. l 2 x AP2 ODU0 mode: the LQM2 board is used for converging double two services at Any rate and ODUk (k=0) SNCP protection is supported. In this mode, signals are sent by optical ports on the WDM side in a dual fed and selective receiving manner. l 2 x AP3 ODU1 mode: the LQM2 board is used for converging double three services at Any rate and ODUk (k=1) SNCP protection is supported. In this mode, signals are sent by optical ports on the WDM side in a dual fed and selective receiving manner. NOTE Before changing the working mode of the LQM2 board, ensure that no cross-connection or service is configured on the board. If a cross-connection or service is configured on the board, delete the crossconnection or service and set Service Type to None before you change the working mode of the board.

Issue 01 (2011-10-20)


95


Field

Value


Description CAUTION Switching between different working modes on a board interrupts the existing services.

Port Working Mode

ODU1 convergence mode (n*Any->ODU1), ODU1 non-convergence mode (OTU1/Any>ODU1) Default: ODU1 convergence mode (n*Any->ODU1)

l ODU1 convergence mode (n*Any->ODU1): client services are mapped into ODU1 services. l ODU1 non-convergence mode (OTU1/Any>ODU1): client services are mapped into ODU1 services. NOTE This parameter is valid when Board Working Mode is set to 1*AP8 ODU1 mode, 2*AP4 ODU1 mode or 2*AP3 ODU1 mode. NOTE This parameter is only supported by the TNF2LQM2.

Service Type

TNF1LQM2: l OTU-1, DVB-ASI, SDI, HDSDI, HDSDI14835, ESCON, FC-100, FC-100 (slice), FC-200, FC-200 (slice), FE, FICON, FICON express, FICON express (slice), FICON (slice), GE, GE(GFPT), GE_SLICE, STM-1, STM-4, STM-16, None l Default: OTU-1 (in the case of the TX1/ RX1 port) or None (in the case of the other ports)

The Service Type parameter sets the type of the service accessed at the optical interface on the client side. NOTE l After you configure a cross-connection for the board, setting the Service Type field fails if the service type selected during cross-connection configuration is different from the value you set for Service Type. In this case, you need to delete the cross-connection and set the Service Type field again. l For the TNF1LQM2 board, the encapsulation mode is GFP-F when Service Type is set to GE. l The service type supported by the LQM2 board varies according to the value of Working Mode. l For the TNF2LQM2 board, GE(TTT-AGMP) is supported only when the board works in 2*AP2 ODU0 mode.

TNF2LQM2: l OTU-1, DVB-ASI, SDI, HDSDI, HDSDI14835, ESCON, FC-100, FC-200, FE, FICON, FICON express, GE (TTT-AGMP), GE (GFP-T), CPRI2, CPRI3, STM-1, STM-4, STM-16, None l Default: None Issue 01 (2011-10-20)


96



Field

Value

Description

Channel Use Status

Used, Unused


Default: Used

l Set this parameter to Used when a channel that is used. Examples are as follows: l When the LQM2 board is used for converging services at Any rate, set Channel Use Status to Used for all WDM-side optical ports and set this parameter for all client-side optical ports according to the actual network design. l When the TNF1LQM2 board is used for regenerating two OTU1 services (2LQM mode), set Channel Use Status to Used for the TX1/RX1, IN1/OUT1, TX5/RX5, and IN2/OUT2 optical ports and to Unused for the other optical ports. l When the TNF1LQM2 board is used for regenerating one OTU1 service (AP8 mode), set Channel Use Status to Used for the TX1/ RX1, and IN1/OUT1 optical ports and to Unused for the other optical ports.

Issue 01 (2011-10-20)


97



Field

Value

Description


Enabled, Disabled


Default: Disabled (in the case of TX1/RX1, and TX5/RX5 ports), Enabled (in the case of the other client-side optical ports), or Disabled (in the case of WDM-side optical ports)


TNF1LQM2: l Enabled, Disabled l Default: – 2LQM mode: Disabled in the case of TX1/RX1 and TX5/RX5 ports, Enabled in the case of the other client-side optical ports. – AP8 mode: Disabled in the case of TX1/RX1 ports, Enabled in the case of the other client-side optical ports. TNF2LQM2: l Enabled, Disabled l Default: – 1*AP8 ODU1 mode: Enabled in the case of all the client-side optical ports. – 2*AP4 ODU1 mode: Enabled in the case of all the client-side optical ports. – 2*AP2 ODU0 mode: Enabled in the case of TX1/ RX1, TX2/RX2, TX5/RX5 and TX6/RX6 ports, Issue 01 (2011-10-20)


98


Field

Value


Description

Disabled in the case of the other client-side optical ports. – 2*AP3 ODU1 mode: Enabled in the case of TX1/ RX1 to TX6/RX6 ports, Disabled in the case of the other client-side optical ports. Hold-Off Time of Automatic Laser Shutdown

Issue 01 (2011-10-20)



Default: 0s


99



Field

Value

Description

Laser Status

ON, OFF

The default value is recommended. In practical application, set this parameter according to the scenario where the board is used. Examples are as follows:


l When the LQM2 board is used for converging services at Any rate, set Laser Status to On for all WDM-side optical ports. Automatic Laser Shutdown of client-side optical ports is set to Enabled. Hence, lasers on client-side optical ports is enabled or disabled automatically according to the signal receiving conditions at the WDM-side optical ports on the local board and the signal receiving conditions at the client-side optical ports on the opposite board. That is, you do not need to set this parameter manually. l When the TNF1LQM2 board is used for regenerating two OTU1 services (2LQM mode), set Laser Status to On for the TX1/ RX1, IN1/OUT1, TX5/RX5, and IN2/OUT2 optical ports and to Off for the other optical ports. l When the TNF1LQM2 board is used for regenerating one OTU1 service (AP8 mode), set Laser Status to On for the TX1/RX1, and IN1/OUT1 optical ports and to Off for the other optical ports. CAUTION If the communication between NEs is achieved through only the ESC provided by the LQM2 board, the following situations occur when neither a standby channel is available nor protection is configured: l The NE becomes unreachable after the WDMside lasers on the LQM2 board are disabled when the LQM2 board is used for converging services at Any rate. l The NE becomes unreachable after the lasers at the TX1/RX1, IN1/OUT1, TX5/RX5, and IN2/ OUT2 optical ports on the TNF1LQM2 board are disabled when the TNF1LQM2 board is used for regenerating two OTU1 services (2LQM mode). l The NE becomes unreachable after the lasers at the TX1/RX1, and IN1/OUT1 optical ports on the TNF1LQM2 board are disabled when the TNF1LQM2 board is used for regenerating one OTU1 service (AP8 mode).


Issue 01 (2011-10-20)



100



Field

Value

Description

Optical Interface Attenuation Ratio (dB)

0 to 20

parameter provides an option to set the optical power attenuation of a board channel so that the optical power of the output signals at the transmit end is within the preset range.

Default: 20

NOTE This parameter is only supported by the TNF2LQM2.


20 Default: 20

parameter provides an option to query the maximum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the TNF2LQM2.


0 Default: 0

parameter provides an option to query the minimum attenuation rate allowed by the current optical port of a board. NOTE This parameter is only supported by the TNF2LQM2.

Guaranteed Bandwidth for ClientSide GE Service (M)

1-1000 Default: 1000

l Users determine the guaranteed bandwidth for GE services based on the needs. This parameter needs to be configured only for GE services. l The value of the Guaranteed Bandwidth for Client-Side GE Service (M) parameter must be greater than the actual service bandwidth of users. Only in this case, no packet loss can be ensured. l Retain the default value when timeslots are sufficient. l When timeslots are insufficient, decrease the committed information rate of GE services to decrease the number of timeslots required. This is to ensure that the total number of timeslots is within the required range. For example, when the TX1/RX1, TX2/RX2, TX3/RX3, and TX4/RX4 ports are used to receive GE services, the CIR can be set to 620 Mbit/s. In this case, each GE service uses four timeslots. Hence, the total number of timeslots required by the services received at the TX1/RX1, TX2/RX2, TX3/RX3, and TX4/RX4 ports is not greater than 16. NOTE This parameter is only supported by the TNF1LQM2.

Issue 01 (2011-10-20)


101



Field

Value

Description



Set this parameter to Non-Loopback when a network works normally. It can be set to Inloop or Outloop to help locate a faulty point in a test or a process of removing a fault on a network. However, it must be set to NonLoopback right after the test is complete or the fault is removed.

Default: Non-Loopback


1518-9600 Default: 9600

l This parameter is valid only when Service Type is set to GE or FE. l The default value is recommended. NOTE This parameter is only supported by the TNF1LQM2.



The Auto Negotiation parameter is available only when the Service Type parameter is set to GE. l It is recommended to set this parameter to Disabled. l If the equipment of the customer adopts the auto negotiation, the value of the Auto Negotiation parameter must be consistent with the value of the Auto Negotiation parameter of the equipment of the customer. l The Auto Negotiation parameter must be consistent for the OTUs in the same protection group. NOTE This parameter is only supported by the TNF1LQM2.



When a link is faulty, and the fault state must be transparently transmitted to the interconnected client-side equipment, the IF function needs to be enabled. l This parameter is valid only when Service Type of the optical port is set to GE. l This parameter is invalid after the LPT function of the board is enabled. NOTE This parameter is only supported by the TNF1LQM2.



Issue 01 (2011-10-20)



102



Field

Value

Description

LPT Enabled

Enabled, Disabled

This parameter is valid when Service Type is set to GE or GE(GFP-T).

Default: Disabled

l The LPT function can work only with intraboard 1+1 protection or ODUk SNCP protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter. PRBS Test Status




The parameter format is as follows: band type/ wavelength No./optical port wavelength/ frequency, for example, C/11/1471.00/208.170.

Band Type

C, CWDM


Default: / This parameter is for query only.


-

-


-

-

5.10.11 LQPL/LQPU Parameters Prerequisite You must have logged in to the NE where the board resides.


Issue 01 (2011-10-20)


103




Navigation Path 1.


2.




Value

Description

Service Type

GPON, OTU1, STM-16

Select a value according to the actual type of service that is carried.

Default: OTU1 Channel Use Status



Issue 01 (2011-10-20)


Enabled, Disabled







Default: 0s


104



Field

Value

Description

Laser Status

ON, OFF



l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LQPL/ LQPU board, the following situation occurs when neither a standby channel is available nor protection is configured: the NEs are unreachable after the lasers on the WDM side of the LQPL/LQPU board are disabled.



FEC Mode




l The default value is recommended. To improve the error correction capability, set this parameter to EFEC. l FEC Mode of the two boards that are interconnected on the WDM side must be consistent. Otherwise, services are interrupted. NOTE When the client-side optical port on the board receives GPON services, FEC Mode cannot be set to EFEC. The actual value is AFEC-2, but EFEC is displayed on the NMS.

NonIntrusive Monitoring Status

Issue 01 (2011-10-20)


You can set this parameter when the SDH service is transmitted. It is recommended to retain the default value.


105



Field

Value

Description



You can set this parameter to Inloop or Outloop for an optical port only when you set Service Type to STM-16 or OTU1 for the optical port.

Default: Non-Loopback

Set this parameter to Non-Loopback when a network works normally. It can be set to Inloop or Outloop to help locate a faulty point in a test or a process of removing a fault on a network. However, it must be set to Non-Loopback right after the test is complete or the fault is removed. When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. SD Trigger Condition


PRBS Test Status


This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. l Retain the default value when a network works normally. l Set this parameter to Enabled for the auxiliary board if you need to perform a PRBS test during deployment commissioning. Set this parameter to Disabled after the test is complete.

Issue 01 (2011-10-20)



Planned Band Type

C, CWDM


The parameter format is as follows: band type/wavelength No./optical port wavelength/ frequency, for example, C/ 11/1471.00/208.170.


Default: /

Default: C


Default: -


106



Field

Value

Description

Band Type

C, CWDM



-

-


-

-

5.10.12 LSPL/LSPU Parameters Prerequisite You must have logged in to the NE where the board resides.


Navigation Path 1.


2.




Value

Description

Channel Use Status

Used, Unused


Default: Used


Issue 01 (2011-10-20)


107



Field

Value

Description


Enabled, Disabled







Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LSPL/LSPU board, do not disable the WDM-side lasers on the LSPL/LSPU board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.










Default: Band Type

C, CWDM


Default: /

Issue 01 (2011-10-20)

Optical Interface/ Channel

-

-


-

-


108



5.10.13 LSPR Parameters Prerequisite You must have logged in to the NE where the board resides.


Navigation Path 1.


2.




Value

Description

Channel Use Status

Used, Unused


Default: Used


Issue 01 (2011-10-20)


Enabled, Disabled







Default: 0s


109



Field

Value

Description

Laser Status

ON, OFF



l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. CAUTION If the communication between NEs is achieved through only the ESC provided by the LSPR board, do not disable the WDM-side lasers on the LSPR board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.




Default: Band Type

C, CWDM



-

-


-

-

5.10.14 LSX Parameters Prerequisite You must have logged in to the NE where the board resides.


Precautions When gray optical modules are used on the WDM side of a board, change the port type to Line Side Grey Optical Port on the U2000. For details, see Changing Port Types. Issue 01 (2011-10-20)


110



Navigation Path 1.


2.




Value

Description

Service Type

TNF1LSX:

Select a proper value according to the received services.

10GE LAN, OTU-2, OTU-2e, STM-64 Default: OTU-2 TNF2LSX: 10GE LAN, 10GE WAN, FC-1200, FICON 10G, FC-800, FICON 8G, STM-64

NOTE TNF1LSX: The processing of the 10GE WAN service and the STM-64 service is the same. Therefore, when the 10GE WAN service is transmitted, you can configure it as the STM-64 service on the U2000.

Default: 10GE LAN

Issue 01 (2011-10-20)


111



Field

Value

Description

Port Mapping

Bit Transparent Mapping (11.1 G), MAC Transparent Mapping (10.7 G)

This parameter is valid when Service Type is set to 10GE LAN.

Default: Bit Transparent Mapping (11.1 G)

l When a board is used to transparently transmit synchronous Ethernet services, this parameter must be set to Bit Transparent Mapping (11.1 G). l Select Bit Transparent Mapping (11.1 G) when there are OTU2e signals on the WDM side. l Select MAC Transparent Mapping (10.7 G) when there are OTU2 signals on the WDM side. NOTE Bit Transparent Mapping (11.1 G): Supports transparent bit (11.1 G) transport for 10GE LAN signals. In this port mapping mode, transmission of signals are achieved by increasing the OTU frame frequency. This ensures the encoding gain and correction capability of FEC. In this mode, the bit rate is 11.1 Gbit/s, which is higher than the standard bit rate of OTU2 signals. MAC Transparent Mapping (10.7 G): In this port mapping mode, 10GE LAN signals are encapsulated in the GFP-F format and then are mapped into standard OTU frames. This mode supports transparent transmission of only client 10GE MAC frames. In this mode, the signals are encapsulated in standard OTU2 frames and the bit rate of the signals is 10.71 Gbit/s. In addition, the FEC/AFEC code pattern is applicable to 10GE LAN services in this mode. Originally, the FEC code pattern is intended for 10G SDH services. NOTE l Port mapping of the two boards that are interconnected with each other must be consistent.



FEC Mode




l The default value is recommended. To improve the error correction capability, set this parameter to EFEC. l FEC Mode of the two boards that are interconnected on the WDM side must be consistent. Otherwise, services are interrupted. NOTE The actual value is AFEC-2, but EFEC is displayed on the NMS. Users cannot set the FEC mode for client-side ports when they are used to receive and transmit OTU2/OTU2e services; they can set the FEC mode for WDM-side ports.

Issue 01 (2011-10-20)


112



Field

Value

Description

Channel Use Status

Used, Unused


Default: Used

l Set this parameter to Used when a channel that is used. Automatic Laser Shutdown

TNF1LSX:


Enabled, Disabled


Default: Disabled for client-side optical ports. TNF2LSX: Enabled, Disabled Default: Enabled for client-side optical ports.



Laser Status

TNF1LSX:

In practical application, set this parameter according to the scenario where the board is used. For example, when the TNF1LSX board is used for regenerating OTU2 or OTU2e signals, set Automatic Laser Shutdown to Disabled for RX/ TX optical ports. The default value is recommended.

Default: 0s

ON, OFF Default: l WDM side: ON l Client side: ON TNF2LSX: ON, OFF Default: l WDM side: ON l Client side: OFF

l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. In practical application, set this parameter according to the scenario where the board is used. For example, when the TNF1LSX board is used for regenerating OTU2 or OTU2e signals, set Laser Status to On for RX/TX and IN/OUT optical ports. CAUTION If the communication between NEs is achieved through only the ESC provided by the LSX board, the following situations occur when neither a standby channel is available nor protection is configured: l When the TNF1LSX board is used for regenerating OTU2 or OTU2e signals, the NE becomes unreachable after the lasers at the RX/TX and IN/OUT optical ports on the TNF1LSX board are disabled. l When the TNF1LSX/TNF2LSX board is used for transparently transmitting the 10 Gbit/s optical signals, the NE becomes unreachable after the lasers at the IN and OUT optical ports on the TNF1LSX/ TNF2LSX board are disabled.

Issue 01 (2011-10-20)


113



Field

Value

Description

NonIntrusive Monitoring Status

Enabled, Disabled

This parameter is valid when the board is used to receive SDH services. The default value is recommended.



Default: Disabled

NOTE Only TNF1LSX supports this parameter.



Max. Packet Length

1518-9600



Default: 9600

Default: None LPT Enabled


This parameter is valid when Service Type is set to 10GE LAN and Port Mapping is set to MAC Transparent Mapping (10.7 G). The default value is recommended. This parameter is valid only when the SD Trigger Flag is set to Enable. all the alarms can be set as the SD switching conditions. This parameter is valid when Service Type is set to 10GE LAN. l The LPT function can work only with intraboard 1+1 protection and cannot work with any other protection. l Set this parameter to Enabled when you want to enable the LPT function; otherwise, keep the default value for this parameter.

PRBS Test Status



Issue 01 (2011-10-20)


114



Field

Value

Description





C, CWDM



Default: C


Default: Band Type

C, CWDM



-

-


-

-

5.10.15 LWX2 Parameters Prerequisite You must have logged in to the NE where the board resides.


Precautions When gray optical modules are used on the WDM side of a board, change the port type to Line Side Grey Optical Port on the U2000. For details, see Changing Port Types. Issue 01 (2011-10-20)


115



Navigation Path 1.


2.



Background Information Table 5-12 describes the service rates of common service types. Table 5-12 Service rates of common service types Service Type OTN

Service Rate (Mbit/s) OTU1

2667.0

STM-16

2488.3

STM-4

622.2

SDH

STM-1

155.5

SAN

FC200

2125.0

FC100

1062.5

FC50

531.2

FC25

255.6

GE

1250.0

FE

125.0

Ethernet

ESCON

200.0

FICON

1062.0

FICON EXPRESS

2124.0

DVB-ASI

270.0

SDI

270.0

HD-SDI

1485.0 or 1483.5

CPRI

2457.6 1228.8

Issue 01 (2011-10-20)


116


Service Type


Service Rate (Mbit/s) 614.4


Value

Description

Client Side Service Bearer Rate (M)

Any rate in the range of 42 Mbit/s to 2.67 Gbit/s rate excluding the ranges of 400 Mbit/s to 500 Mbit/s, 800 Mbit/s to 1000 Mbit/s, and 1.6 Gbit/s to 2.0 Gbit/s

Select a proper service type according to the actually received services or enter a service rate directly. The service rate must be accurate to 0.1 Mbit/s. For example, when the board is used to receive STM-16 services, you need to enter 2488.3.

Default: 2667.0 Mbit/ s

Channel Use Status


NOTE After you set Client Service Bearer Rate (M) for the RX1/TX1 and the RX2/TX2 optical ports, the service rates are automatically updated at the corresponding IN1/ OUT1 and IN3/OUT3 optical ports. That is, you do not need to set Client Service Bearer Rate (M) for the IN1/ OUT1 and IN3/OUT3 optical ports. When setting the service rates at the IN1/OUT1 and IN3/OUT3 optical ports, make sure that the service rates on the client and WDM sides of the same channel are the same. That is, the service rate at the RX1/TX1 optical ports must be the same as that at the corresponding IN1/OUT1 optical ports; the service rate at the RX2/TX2 optical ports must be the same as that at the corresponding IN3/OUT3 optical ports.



Enabled, Disabled



l On the WDM side, this automatic laser shutdown function is not supported and therefore cannot be set or query. In practical application, set this parameter according to the scenario where the board is used. For example, when the LWX2 board functions as a regeneration board, set Automatic Laser Shutdown to Disabled for the IN1/OUT1, IN3/ OUT3, RX1/TX1, and RX2/TX2 optical ports. NOTE When OTU1 services are received on the client side, the ALS function is disabled on the LWX2 board. That is, all lasers stay in enabled state.

Issue 01 (2011-10-20)


117



Field

Value

Description




Laser Status

ON, OFF

Default: 0s


l Usually, this parameter is set to ON for every WDM-side optical port. l In the case of client-side optical ports, retain the default value because Automatic Laser Shutdown is usually set to Enabled. In practical application, set this parameter according to the scenario where the board is used. Examples are as follows: l When the LWX2 board is used as a regeneration board, set Laser Status to On for the IN1/ OUT1, IN3/OUT3, RX1/TX1, and RX2/TX2 optical ports. l When the LWX2 board is used as a transparent transmission board, set Laser Status to On for the IN1/OUT1, and IN3/OUT3 optical ports. Automatic Laser Shutdown of the RX1/TX1, and RX2/TX2 optical ports is set to Enabled. Hence, lasers on client-side optical ports are enabled and disabled automatically according to the signal receiving conditions. That is, you do not need to set this parameter manually. CAUTION If the LWX2 board is used as a regeneration board between NEs and NEs communicates with each other through only the ESC provided by the OTU regenerated on the LWX2 board, do not disable the lasers on the LWX2 board. Otherwise, NEs become unreachable when neither a standby channel is available nor protection is configured.




Issue 01 (2011-10-20)


118



Field

Value

Description

PRBS Test Status

Enabled, Disabled

l Retain the default value when a network works normally.

Default: /

l Set this parameter to Enabled for the auxiliary board if you need to perform a PRBS test during deployment commissioning. Set this parameter to Disabled after the test is complete. Band Type/ Wavelength No./ Wavelength (nm)/ Frequency (THz)



Default: Band Type

C, CWDM



-

-


-

-

5.10.16 TSP Parameters Prerequisite You must have logged in to the NE where the board resides.



Navigation Path Select the board in the NE Explorer. Select a proper navigation path according to port type. The details are as follows: Issue 01 (2011-10-20)


119



l

To set a parameter supported by the IN1/OUT1 or IN2/OUT2 optical port, such as Channel Use Status, Laser Status, and Service Type, choose Configuration > WDM Interface from the Function Tree. Select By Board/Port(Channel), choose Channel from the dropdown list, and click the Basic Attributes or Advanced Attributes tab.

l

To set a parameter supported by the RX1/TX1 or RX2/TX2 port, such as Laser Switch, choose Configuration > SDH Interface from the Function Tree.

l

To set a parameter supported by the E1/T1 port, such as E1/T1 Mode, choose Configuration > PDH Interface from the Function Tree.

Parameter Description (WDM Interface) Field

Value

Description

Service Type

STM-1, STM-4

Select a value according to the service rate on the WDM side.

Default: STM-1

The parameter settings are supported only by the 251 (LP1/LP1) and 252 (LP2/LP2) logical ports on the WDM side. Channel Use Status



Laser Status

ON, OFF Default: ON

It is recommended to set this parameter to ON for all optical ports. CAUTION If the communication between NEs is achieved through only the ESC provided by the TSP board, the following situation occurs when neither a standby channel is available nor protection is configured: the NEs are unreachable after the lasers on the WDM side of the TSP board are disabled.

E1/T1 Mode

E1, T1 Default: E1

Select a value according to the actual type of service that the E1/T1 port carries. Only the TSPB board supports switchover between the E1 and T1 services. When you set the E1/T1 mode, the E1/T1 modes at logical ports 5-25 on the client side are automatically changed to the mode that you set.




Issue 01 (2011-10-20)


120



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

Parameter Description (SDH Interface) Field

Value

Description

Laser Switch

On, Off

It is recommended to set this parameter to On for all optical ports.

Default: On VC4 Path

NE ID-subrack IDslot-board nameoptical port number-channel ID

Displays the number of a VC4 channel.

VC4 Loopback




When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. VC12 Channel

Issue 01 (2011-10-20)

NE ID-subrack IDslot-board nameoptical port number-channel ID

Displays the number of a VC12 channel.


121



Field

Value

Description

Port

NE ID-subrack IDslot-board nameoptical port number

Displays the number of a port on the board.


-

-

Parameter Description (PDH Interface) Field

Value

Description

E1/T1 Mode

E1, T1

Select a value according to the actual type of service that the E1/T1 port carries. Only the TSPB board supports switchover between the E1 and T1 services.

Default: E1

When you set the E1/T1 mode, the E1/T1 modes at logical ports 5-25 on the client side are automatically changed to the mode that you set. Board

NE ID-subrack IDslot-board name

Displays the name of the board.

Port

NE ID-subrack IDslot-board namechannel ID

Displays the E1/T1 channel of the board.

Port Name

1 to 21

Displays the E1/T1 channel ID.

Tributary Loopback




When Automatic Disabling of NE Function is set to the default value Enabled, the loopback setting is automatically cancelled after Auto Disabling Time (default: 5 minutes) elapses. Re-timing Mode

Issue 01 (2011-10-20)

Normal, Re-timing Mode of Tributary Clock, Re-timing Mode of Crossconnect Clock

l Normal: The re-timing function is not enabled.

Default: Normal

l Re-timing Mode of Cross-connect Clock: The cross-connect (external) clock is used as the reference clock for retiming.

l Re-timing Mode of Tributary Clock: A tributary clock is used as the reference clock for retiming.


122



5.10.17 SCC Parameters Prerequisite You must have logged in to the NE where the board resides.

Tools, Meters, and Materials Web LCT or U2000

Navigation Path 1.


2.

Select a proper navigation path according to the parameters. The details are as follows: l Select By Board/Port(Channel), and click the Basic Attributes or Advanced Attributes tab. Then, you can query or set the corresponding parameter. NOTE



Value

Description

Channel Use Status

Used, Unused

l If the OSC channel is not configured or used in the network planning, set the Channel Use Status field to Unused for the TM1/RM1 and TM2/RM2 optical ports.

Default: Used

l If the OSC channel is configured and used in the network planning, set the Channel Use Status field to Used for the TM1/RM1 and TM2/RM2 optical ports. Laser Status

ON, OFF Default: l WDM side: ON l Client side: OFF

l If the OSC channel is not configured or used in the network planning, set the Laser Status field to OFF for the TM1/RM1 and TM2/RM2 optical ports. l If the OSC channel is configured and used in the network planning, set the Laser Status field to ON for the TM1/RM1 and TM2/RM2 optical ports. CAUTION If the communication between NEs is achieved through only the OSC, the NEs are unreachable after the lasers at the TM1/RM1 and TM2/RM2 optical ports on the SCC board are disabled.

Issue 01 (2011-10-20)


123



Field

Value

Description




Default: Band Type

C, CWDM



-

-


-

-

5.11 Configuring Protection Schemes When commissioning and configuring a network, you need to configure protection schemes based on the network and service planning.

5.11.1 Configuring SW SNCP Protection SW SNCP protection can be implemented by using convergence OTU boards that support crossconnections. This type of OTU boards includes the LQM2 and LQG boards.

Prerequisite You must have logged in to an NE. The NE must be configured with boards that support SW SNCP protection.


Precautions NOTE

SW SNCP protection must be configured at both the sink and source. At the source, you need to configure cross-connections to implement dual transmitting; at the sink, you need to configure cross-connections to implement selective receiving.

Issue 01 (2011-10-20)


124




On the source NE of SW SNCP protection, configure two cross-connections for dually transmitting a service. To implement dual transmitting on the source NE of SW SNCP protection, you need to configure two cross-connections, which share the same source but have different sinks. An example is as follows (1U chassis): l Source: 1-LQM2-3(RX1/TX1)-1; sink: 1-LQM2-201(LP1/LP1)-1 (this is a unidirectional cross-connection) l Source: 1-LQM2-3(RX1/TX1)-1; sink: 4-LQM2-201(LP1/LP1)-1 (this is a unidirectional cross-connection) (1) In the NE Explorer, select the NE and choose Configuration > Electrical CrossConnection Service Management from the Function Tree. (2) Click the Electrical Cross-Connection Configuration tab. Click New and the Create Cross-Connection Service dialog box is displayed. (3) Select corresponding values for Service Level and Service Type and set other parameters for the service. (4) Click OK and the created cross-connection is displayed in the user interface.

2.

On the sink NE of SW SNCP protection, configure cross-connections for selectively receiving a service. Two cross-connections must be configured for Working Service and Protection Service. The two cross-connections have different sources but share the same sink. An example is as follows (1U chassis): l Source: 1-LQM2-201(LP1/LP1)-1; sink: 1-LQM2-3(RX1/TX1)-1 l Source: 4-LQM2-201(LP1/LP1)-1; sink: 1-LQM2-3(RX1/TX1)-1 NOTE

When configuring the cross-connections, you need to configure only the source for Protection Service but need to configure source and sink for Working Service.

Table 5-13 Requirements for setting key parameters of SW SNCP protection

Issue 01 (2011-10-20)

Parameter Name

SW SNCP Protection

Protection Type

SW SNCP

SNCP Type

Unavailable

Service Type

GE

OTN Level

Unavailable

Revertive Mode

Non-revertive

WTR Time (s)

Unavailable

Working Channel Delay Time (100ms)

0

Protection Channel Delay Time (100ms)

0

SD Trigger Flag

Disabled


125



NOTE

The values listed in Table 5-13 are recommended values. Set the parameters properly according to engineering requirements in practical application.

(1) In the NE Explorer, select the NE and then choose Configuration > Electrical CrossConnection Service Management from the Function Tree. (2) Click the Electrical Cross-Connection Configuration tab. Click Create SNCP. The Create SNCP dialog box is displayed. Set the parameters for SNCP protection. (3) Click OK. Then, the protection group is created and displayed in the user interface.


On the source NE of SW SNCP protection, configure two cross-connections for dually transmitting a service. To implement dual transmitting on the source NE of SW SNCP protection, you need to configure two cross-connections, which share the same source but have different sinks. An example is as follows (1U chassis): l Source: 1-LQM2-3(RX1/TX1)-1; sink: 1-LQM2-201(LP1/LP1)-1 (this is a unidirectional cross-connection) l Source: 1-LQM2-3(RX1/TX1)-1; sink: 4-LQM2-201(LP1/LP1)-1 (this is a unidirectional cross-connection) (1) In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. (2) Click the WDM Cross-Connection Configuration tab. Click New and the Create Cross-Connection Service dialog box is displayed. (3) Select corresponding values for Level and Service Type and set other parameters for the service. (4) Click OK. A prompt appears telling you that the operation was successful. (5) Click Close.

2.

On the sink NE of SW SNCP protection, configure cross-connections for selectively receiving a service. Two cross-connections must be configured for Working Service and Protection Service. The two cross-connections have different sources but share the same sink. An example is as follows (1U chassis): l Source: 1-LQM2-201(LP1/LP1)-1; sink: 1-LQM2-3(RX1/TX1)-1 l Source: 4-LQM2-201(LP1/LP1)-1; sink: 1-LQM2-3(RX1/TX1)-1 NOTE

When configuring the cross-connections, you need to configure only the source for Protection Service but need to configure source and sink for Working Service. NOTE

If cross-connections that are used to implement dual feeding of a service are not configured on the NE, set Direction to Bidirectional when configuring SW SNCP protection and at the same time configure the attributes of dual fed and selective receiving feature. If cross-connections that are used to implement dual feeding of a service are configured on the NE, set Direction to Unidirectional when configuring SW SNCP protection.

Issue 01 (2011-10-20)


126



Table 5-14 Requirements for setting key parameters of SW SNCP protection Parameter Name

SW SNCP Protection

Protection Type

SW SNCP

SNCP Type

Unavailable

Service Type

GE

OTN Level

Unavailable

Revertive Mode

Non-revertive

WTR Time (s)

Unavailable


0


0

SD Trigger Flag

Disabled

NOTE

The values listed in Table 5-14 are recommended values. Set the parameters properly according to engineering requirements in practical application.

(1) In the NE Explorer, select the NE and then choose Configuration > WDM Service Management from the Function Tree. (2) Click Create SNCP Service. The Create SNCP Service dialog box is displayed. Set the parameters for SNCP protection. (3) Click OK. Then, the protection group is created and displayed in the user interface.


Delete a cross-connection See this section to learn how to delete a cross-connection.

l

Convert a service with SNCP protection into a service with no protection A service with SNCP protection can be converted into a service with no protection.

l

WDM cross-connection configuration See this section to learn how to set the parameters for configuring a WDM cross-connection.

l

SNCP service control See this section to learn how to set the parameters for controlling services with SNCP protection.



127



5.11.2 Configuring SNCP Protection SNCP protection can be supported by TSP board.

Prerequisite You must have logged in to an NE. The NE must be configured with boards that support SNCP protection.



In the NE Explorer, select the NE and then choose Configuration > SDH Service Configuration from the Function Tree.

2.

Click Create SNCP Service. The Create SNCP Service dialog box is displayed.

3.

Set the SNCP protection parameters, click OK.

4.

Click Close in the Operation Result dialog box. Then, the protection group is created and displayed in the user interface.


5.11.3 Configuring ODUk SNCP Protection ODUk SNCP protection can be supported by F2ELOM, F2LQM, F2LQM2, F1ELQM, F2LDGF2, F2LSX, F1LDX boards.

Prerequisite You must have logged in to an NE. The NE must be configured with boards that support SNCP protection.



In the NE Explorer, select the NE and then choose Configuration > WDM Service Management from the Function Tree.

2.

Click Create SNCP Service. The Create SNCP Service dialog box is displayed. Set the parameters for SNCP protection.

3.

Click OK. Then, the protection group is created and displayed in the user interface.

Issue 01 (2011-10-20)


128





l



5.11.4 Configuring Port Protection On the port protection user interface, you can configure intra-board 1+1 protection, optical line protection, client 1+1 protection, and 1+1 optical channel protection. Configure protection of an appropriate type according to the network design.

Prerequisite You must have logged in to an NE. The NE must be configured with boards that support port protection.


Background Information Observe the differences between intra-board 1+1 protection, optical line protection, client 1+1 protection, and 1+1 optical channel protection when configuring them. Table 5-15 lists the differences between these protection types.

Issue 01 (2011-10-20)


129



Table 5-15 Differences between different port protection types Protection Type Configuration Precaution Intra-board 1+1 protection

l The protection must be configured on both the sink and source NEs. l The client-side service attributes of the working and protection channels must be the same. Otherwise, services are unavailable. l In the case of the intra-board 1+1 protection by using an OTU with the dual fed and selective receiving function, Channel Use Status of a WDM-side optical port must be set to Used. Each of the WDM-side optical interfaces on the OTU can be configured as the working channel. When the protection group is deleted, the service is forcibly switched to optical port 1 (IN1/OUT1) or optical port 3 (IN3/OUT3). l The NE will be unreachable by the NMS after the protection group is deleted if the following conditions are met: (1) Communication between NEs is implemented by using an ESC channel. (2) There is no standby channel. (3) Optical interfaces IN1 and IN3 receive no light.

Optical line protection

l The protection must be configured on both the sink and source NEs.

client 1+1 protection

l The protection must be configured on both the sink and source NEs.

1+1 optical channel protection

l In the case of wavelength protection, the working OTU board and the protection OTU board are installed in different subracks. You are recommended to install the OLP board in the chassis where the working OTU board resides.

l The working and protection channels at the receive end of the OLP board must have the same receive optical power. The variance threshold between primary and secondary input power is 5 dB by default.

l The working and protection OTU boards must be of the same type.

l The working and protection OTU boards must be of the same type. l The boards support protection only in the scenario where GE services are accessed.

For details about the preceding protection types, see the Feature Description.

Precautions

CAUTION Before configuring protection involving the OLP board, set Initial Variance Value Between Primary and Secondary Input Power (dB) of the current optical port on the OLP board in the WDM interface attribute window. That is, set the initial difference between the input optical power of channel 1 and the input optical power of channel 2. For example, if the input optical power of channel 1 is -6 dBm and the input optical power of channel 2 is -5 dBm, set the value of Initial Variance Value Between Primary and Secondary Input Power (dB) to 1 dB.

Issue 01 (2011-10-20)


130




Create port protection based on network planning. (1) In the NE Explorer, select the NE and then choose Configuration > Port Protection from the Function Tree. (2) In the Port Protection window, click New.Then, the Creating a protection group will interrupt services used by the protection. Are you sure to continue? dialog box is displayed. Click OK. (3) Set parameters for the selected protection type. Click OK to display a dialog box. (4) Click OK to complete the protection configuration. Then, the protection group is created and displayed in the user interface. Table 5-16 Requirements for setting parameters of different protection types Parameter Name

Issue 01 (2011-10-20)


Intra-board 1+1 protection


Implemented by Using OTU Boards with the Dual Fed and Selective Receiving Function

Implemente d by Using OLP Boards and OTU Boards with the Single Fed and Single Receiving Function

Protection type Optical line protection

Intra-board 1 +1 protection

Intra-board 1 +1 protection


NE with the Working Channel

The NE where the OLP board resides. For example, NE7201.

The NE where the OTU board resides. For example, NE7201.


The NE where the working OTU board resides. For example, NE7201.

Board with Working Channel

OLP board, for example, 4OLP

OTU board, for example, 1LQM2


Working OTU board, for example, 1LWX2

Working Channel

The working channel on the OLP board. For example, 1 (RI1/TO1).

The working channel on the OTU board, namely, a WDM-side optical port. For example, 1 (IN1/OUT1).

The working channel on the OLP board. For example, 1 (RI1/TO1).

A client-side optical port on the working OTU board. For example, 1 (RX1/TX1).


131


Issue 01 (2011-10-20)


Parameter Name


Intra-board 1+1 protection Implemented by Using OTU Boards with the Dual Fed and Selective Receiving Function


NE with Protection Channel




The NE where the protection OTU board resides. For example, NE7201.

Board with Protection Channel


OTU board, for example, 1LQM2


Protection OTU board, for example, 3LWX2

Protection Channel

The protection channel on the OLP board. For example, 2 (RI2/TO2).

The protection channel on the OTU board, namely, a WDM-side optical port. For example, 2 (IN2/OUT2).

The protection channel on the OLP board. For example, 2 (RI2/TO2).

A client-side optical port on the protection OTU board. For example, 1 (RX1/TX1).

NE with Control Channel/ Monitoring Channel

Unavailable

Unavailable


Unavailable



NOTE If the protection is Intra-subrack client 1+1, the parameter should be set to the NE where the OLP board resides. This NE generally houses the working OTU board. For example, NE7201.

132


Issue 01 (2011-10-20)


Parameter Name




Board with Control Channel/ Monitoring Channel

Unavailable

Unavailable

OTU board, for example, 1LOE

Unavailable

Control Channel/ Monitoring Channel

Unavailable

A WDM-side optical port on the OTU board. For example, 1 (IN1/OUT1).

Unavailable


0

0

Unavailable

0


0

0

Unavailable

0

Control Channel/ Monitoring Channel Delay Time (100ms)

Unavailable

Unavailable

0

Unavailable

Revertive Mode

Non-revertive

Non-revertive

Unavailable

Non-revertive

WTR Time (s)

Unavailable

Unavailable

Unavailable

Unavailable

Unavailable



NOTE If the protection is Intra-subrack client 1+1, the parameter should be set to OLP board, for example, 1OLP.

NOTE If the protection is Intra-subrack client 1+1, the parameter should be set to Optical interface 1 (RI1/TO1) on the OLP board.

133



Parameter Name




SD Trigger Flag

Disabled

Disabled

Disabled


Disabled

NOTE

The values listed in Table 5-16 are recommended values. Set the parameters properly according to engineering requirements in practical application. NOTE

In the case of the intra-board 1+1 protection implemented by using the OLP board and the OTU board with single fed and single receiving function, the Revertive Mode field is unavailable. In the case of other protection types, if you set the Revertive Mode field to Revertive, you also need to set the WTR Time (s) field. The value of the WTR Time (s) field ranges from 300 to 720. The default value is 600. TIP

After the protection is configured, select a protection group in the Port Protection window. In the right lower corner, you can click Delete to delete the protection group or click Modify to modify the parameters of the protection group.

CAUTION Deleting a protection group can make an NE unreachable. 2.

Optional: When configuring the intra-board 1+1 protection implemented by using OTU boards with the dual fed and selective receiving function, add an optical port if an optical port is idle but cannot be selected. (1) In the NE Explorer, right-click the board and then choose Path View. (2) Right-click a blank space on the right of the Path View window, and then choose Add Port. The Add Port dialog box is displayed. (3) Select the port and port type. Click OK.

Issue 01 (2011-10-20)


134



CAUTION Do not delete a port or change the port type unless required. l Services are interrupted after a port is deleted. l If the type of services received at a port is inconsistent with the default service type supported by the board, changing the port type results in a service interruption. l In the case of the LQM and LQM2 boards, after the port type is changed, the service type on the port is changed into None.


Deleting Ports A port can be deleted if the port is set incorrectly.

l

Changing Port Types The type of a port can be changed if the port is set incorrectly.

l

Port protection See this section to learn how to set the parameters used for configuring port protection.


5.11.5 Configuring ERPS Protection In an Ethernet ring network, ERPS protection can be configured for EVPL, EPLAN, and EVPLAN services. ERPS protection must be configured for each node in an Ethernet ring network.

Prerequisite WDM interface and Ethernet interface parameters on a board must be configured.


Background Information For details on ERPS protection, see the Feature Description.

Procedure on the U2000 or Web LCT 1.

In the NE Explorer, select the NE and select an Ethernet board. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree.

2.

Click New. The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.

3.

The protection parameters should be set according to network planning.

Issue 01 (2011-10-20)


135



Field

Value

Remarks

ERPS ID

1-4

Specifies the ERPS protection group ID. For example, 1. The EPRS IDs for all nodes in a ring network must be same.

East Port

PORT5-PORT22, VCTRUNK1VCTRUNK3

When a board is connected to an Ethernet ring network configured with protection, there are east and west ports on a board. This parameter indicates the east port of the board.

West Port


When a board is connected to an Ethernet ring network configured with protection, there are east and west ports on a board. This parameter indicates the west port of the board.

RPL Owner Ring Node Flag

Yes, No

Sets whether a node is an RPL owner. If a node is an RPL owner, set this parameter to Yes. If the node is not an RPL owner, set this parameter to No. For one ring network, specify one node as an RPL owner.


Specifies the RPL port for an RPL owner node.

Control VLAN

1-4094

Specifies the VLAN ID for packets that carry the ring network automatic protection switching (R-APS) protocol. The control VLAN ID cannot be the same as the service VLAN ID.

Destination Node

01-19-A7-00-00-01

Indicates the MAC address of the destination node. The default destination MAC address of an R-APS packet is 01-19-A7-00-00-01.

RPL Port

This parameter is valid only when RPL Owner Ring Node Flag is set to Yes and the RPL port must be the east port or the west port.

4.

Click OK. After the operation succeeds, the Operation Result dialog box is displayed. Click Close.

5.

Set other protection parameters according to the network plan.

Issue 01 (2011-10-20)


136


Field

Value 0-10000. Step length: 100.

Hold-Off Time(ms)

Default: 0

Guard Time(ms)

10-2000. Step length: 10.

WTR Time(mm:ss)


Remarks Displays and sets the holdoff time for ERPS.

Default: 500

Displays and sets the guard time for ERPS. During the guard time, the received RAPS message is discarded. When the guard time expires, the received R-APS message is forwarded directly.

05:00-12:00

Displays and sets the WTR time for ERPS.

Default: 05:00 Packet Transmit Interval(s)

1-10 Default: 5

Displays the transmit interval for R-APS messages.

Entity Level

0-7

Displays and sets the entity level.

Default: 4

6.

Last Switching Request

Raps (NR), Raps (NR, RB), WTR, WTR Expires, Raps (SF), Local SF, Local Clear SF, Initial Request

Displays the last switching request.

RB Status

noRB, RB

Displays the RB status of the message received at the current node.

DNF Status

noDNF, DNF

Displays the DNF status of the message received at the current node.

Status of State Machine

Idle, Protection

Displays the status of the state machine at the current node.

Node Carried with Current Packet

For example, 01-19A7-00-00-01

Displays the MAC address in the message received at the current node, that is, the MAC address of the source node of the switching request.

Click Apply. Then, the ERPS protection configuration at a node is complete.


Issue 01 (2011-10-20)


137



5.12 Synchronizing the NE Time with the NMS Time With the time synchronization function, the NE time is kept consistent with the NMS time. In this way, the NMS is able to record the correct time when alarms and abnormal events are reported by NEs.

Prerequisite You must have logged in to an NE.


Background Information When NEs report alarms and abnormal events to the NMS, the generation time of such alarms and events is based on the NE time. If the NE time is incorrect, the generation time of the alarms recorded in the NMS is also incorrect, which may cause troubles in fault locating. The same case happens to the generation time of abnormal events that are recorded in the NE security log. To prevent the preceding problem, the NMS provides the function of synchronizing the NE time with the NMS time to ensure that the NE time is correct. With this function, all NEs can be synchronized with the NMS time manually or automatically. In this manner, all the NEs use the NMS time as the standard time. The NMS server time refers to the time of the computer system where the NMS server resides. This function features easy operation and applies to a network with relatively low requirement for time accuracy. Synchronizing NE time with the NMS time does not affect the existing services. Before synchronizing the NE time with the NMS time, make sure that the time of the computer system where the Web LCT/U2000 server resides is correct. If you need to change the computer system time, first exit the Web LCT/U2000. Then, restart the Web LCT/U2000 after re-setting the computer system time.


In the NE Explorer, select the NE. Choose Configuration > NE Time Synchronization from the Function Tree.

2.

Set Synchronous Mode to NM and then click Apply.

3.

Right-click the NE and then choose Synchronize with NM Time. In this manner, the NE time is synchronized with the NMS time immediately.


In the NE Explorer, select the NE. Choose Configuration > NE Time Synchronization from the Function Tree. The Result dialog box is displayed. Click Close.

2.

Right-click the NE and then choose Synchronize with NM Time. A dialog box is displayed. Click Yes.

3.

The Result dialog box is displayed. Click Close. In this manner, the NE time is synchronized with the NMS time immediately.

Issue 01 (2011-10-20)


138




Setting Automatic Synchronization of the NE Time with the NMS Time See this section to learn how to set automatic synchronization of the NE time with the NMS time.

l

Parameters for Synchronizing NE Time See this section to learn how to set the parameters associated with NE time synchronization.


5.13 Starting NE Performance Monitoring Enabling the performance monitoring function is a precondition for querying the performance events. If the current NE time is in the performance monitoring time range as set before, the NE monitors its performance events automatically. If the performance monitoring time range is not set or if the current NE time is not within the performance monitoring time range, the NE does not monitor its performance events.

Prerequisite The NE time must be synchronized with the NMS time. You must have logged in to an NE.


Precautions NOTE

The start time for monitoring NE performance must be later than the current time of the NMS and NE. If you need to monitor the performance immediately, set the start time just a little later than the current time of the NMS and NE. The end time must be later than the start time or you can keep the end time field blank.


In the NE Explorer, click the NE and choose Performance > NE Performance Monitor Time from the Function Tree. In NE Performance Monitor Time, select the desired NE. NOTE

An NE must be selected at this step. Otherwise, it is impossible for you to proceed with the task.

2.

In the Set 15-Minute Monitoring field, select Enabled and click behind the From field to set the start time for monitoring the 15-minute performance of the NE. TIP

The method of setting the time is as follows: In the hour, minute, or second time control, right-click the time to increase it, or press Shift and right-click the time to decrease it.

Issue 01 (2011-10-20)


139



3.

In the Set 24-Hour Monitoring field, select Enabled and click behind the From field to set the start time for monitoring the 24-minute performance of the NE.

4.

Click Apply to apply the settings.


Choose Performance > Set NE Performance Monitoring Time from the Main Menu of the U2000.

2.

Select an NE in the left-hand pane, and click

3.

Select the desired NE in the right-hand pane.

4.

Select the check box 15-Minute, and click radio button Enabled; or select the check box 24-Hour, and click radio button Enabled.

5.

behind From field, select the date, and enter the time to set the beginning Click the time and end time for monitoring.

.

NOTE

The start time must be later than the current time of the NMS and NE. If you need to monitor the performance immediately, set the start time just a little later than the current time of the NMS and NE. To set the end time, select the check box before To first. The end time must be later than the start time. If the check box before To is not selected, it indicates that the monitoring function is enabled all the time.

6.

Click Apply. The Warning dialog box is displayed, click OK.

7.

In the Result dialog box displayed, click Close to finish the operation.


Set performance thresholds for a specified board When an NE detects that a certain performance value exceeds the specified threshold, the NE reports a corresponding performance event. See this section to learn how to change the performance threshold of a specified board.

l

Set performance monitoring parameters of a board The Web LCT/U2000 can monitor the performance of all boards on a network. The automatic reporting of detected performance values, however, is disabled by default. You can change the default setting as required.

l

Set performance monitoring parameters of an NE Set the performance monitoring parameters of a specified NE properly and then enable the NE performance monitoring function. By doing so, you can obtain detailed description of performance records during the operation of the NE. This facilitates monitoring of the existing services and the equipment status.

l

Reset the performance register of a board After a network test or fault recovery, you need to reset the performance register of a board as required before the board is put into operation. This is to start a new performance monitoring period.



140



5.14 Checking Configurations in the Commissioning Process Correct setting of each system parameter is the precondition for ensuring normal network operation. Check the configurations of NEs and boards according to Table 5-17 and rectify inappropriate configurations, for example incorrect parameter settings and incomplete parameter settings. Table 5-17 Configuration checklist N o.

Item

Associated Operation

1

Communication between NEs on the network is normal and login to an NE is successful.

Searching and Creating NEs

2

NE IDs and names are changed properly according to the customer planning requirements.

Changing NE IDs and Names

3

NE IP addresses are changed properly according to the customer planning requirements.

Changing NE IP Addresses

4

When the network uses the HWECC communication protocol, a proper extended ECC communication mode is selected when the number of NEs that adopt the extended ECC communication exceeds nine.

Setting the Ethernet Extended ECC Communication

When the network uses IP over DCC communication protocol, the IP over DCC protocol is configured properly.

Configuring IP over DCC Configuring OSI over DCC

When the network uses OSI over DCC communication protocol, the OSI over DCC protocol is configured properly. 5

Attributes of every interface on a board are set properly.

Configuring Board Parameters

6

The protections are configured properly for a planned optical port.

Configuring Port Protection Configuring SW SNCP Protection Configuring SNCP Protection Configuring ODUk SNCP Protection

7

Issue 01 (2011-10-20)

All NEs are synchronized with the NMS time and NE performance monitoring can be enabled normally.


Synchronizing the NE Time with the NMS Time Enabling NE Performance Monitoring

141



TIP

In the actual commissioning and configuration process, you are recommended to check the configurations of an NE after configuring the NE.

See List of Tasks for Commissioning and Configuration During Deployment for the subsequent task.

Issue 01 (2011-10-20)


142


6

6 Service Configurations

Service Configurations

About This Chapter 6.1 Basic Concepts This topic describes basic concepts involved in service configurations. 6.2 Configuring Services on Boards The services that can be configured vary according to boards. The topic describes service configurations on some boards that provide comprehensive functions. 6.3 Configuring WDM Services After setting board parameters, you need to configure WDM service grooming for boards that support cross-connections based on WDM services and protection planning. 6.4 Configuring EPL/EVPL Services EPL/EVPL services belong to Ethernet services and are carried in WDM service signals. 6.5 Configuring EPLAN/EVPLAN Services EPLAN/EVPLAN services belong to Ethernet services and are carried in WDM service signals. 6.6 Configuring SDH Service The TSP board supports configuration of SDH service.

Issue 01 (2011-10-20)


143



6.1 Basic Concepts This topic describes basic concepts involved in service configurations.

6.1.1 Overview Before configuring services, you need to be familiar with the function module that processes each type of services. In general, Figure 6-1 shows the abstract configuration model of service processing on WDM equipment. Figure 6-1 Abstract configuration model RX1/TX1 RXn/TXn

Optical module

Service processing module

Any crossconnect module

ODUk crossconnect module

OTN

Optical IN/OUT module

NOTE

In practice, boards support only part of the functions included in the configuration model.

Ethernet services, SDH services, and WDM services are processed by different function modules. l

Ethernet services are processed by the service processing module (the L2 switching module) as shown in Figure 6-1. Ethernet services are classified into E-Line services and E-LAN services. For details, see 6.4.1 EPL/EVPL Service Overview and 6.5.1 EPLAN/ EVPLAN Service Overview.

l

SDH services are processed by the service processing module (the SDH timeslot mapping module) as shown in Figure 6-1.

l

WDM services are processed by the Any cross-connect module and ODUk cross-connect module as shown in Figure 6-1. Services can be processed in more and more modes as WDM equipment is developing. The concept of WDM services is also changing. WDM services at first include Any cross-connections only and later also include ODUk crossconnections. In practice, an Any cross-connection, an ODUk cross-connection, and an electrical cross-connection are used instead of a WDM service which is a general name.

To ensure that equipment processes services properly, configure services by equipment type. For boards that can transmit and receive different types of services, set the service types as required before configuring the services. The service type setting is the prerequisite to service configurations. Note that you need to differentiate between service type setting and service configurations.

6.1.2 Cross-Connection Types Before configuring WDM services, you need to be familiar with basic types of crossconnections. Cross-connections on WDM equipment can be classified into two types: optical crossconnections and electrical cross-connections. Optical cross-connections cross-connect optical Issue 01 (2011-10-20)


144



signals and are not related to the types of carried services; electrical cross-connections crossconnect electrical signals and are closely related to the types of carried services. Electrical cross-connections can be classified in different ways. l

Electrical cross-connections can be classified into Any cross-connections and ODUk crossconnections according to cross-connection levels and granularities. In practice, there is a mapping relationship between Any cross-connections and types of the carried services. That is, Any cross-connections carry a specified type of services. For example, if an Any cross-connection carries GE services, it is also referred to as a GE cross-connection.

l

Electrical cross-connections can be also classified into intra-board cross-connections and inter-board cross-connections according to their positions. – Intra-board cross-connections: Services signals are still on a board after they are processed by a cross-connect unit in the board. As shown in Figure 6-2, crossconnections between channel 1 of client-side port 5 (RX3/TX3) on a board and channel 1 of WDM-side port 201 (LP1/LP1) on the same board are referred to as intra-board cross-connections. Figure 6-2 Intra-board cross-connections 3(RX1/TX1)-1 5(RX3/TX3)-1

201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3

6(RX4/TX4)-1

201(LP1/LP1)-4

4(RX2/TX2)-1

1(IN1/OUT1)-1

When ports or channels at the two ends of cross-connections are corresponded according to the arrangement sequence, the cross-connections are also referred to as direct crossconnections. See Figure 6-3. Figure 6-3 Direct cross-connections A 3(RX1/TX1)-1 5(RX3/TX3)-1

201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3

6(RX4/TX4)-1

201(LP1/LP1)-4

4(RX2/TX2)-1

1(IN1/OUT1)-1

– Inter-board cross-connections: Service signals are transmitted to the cross-connect unit on another board after they are processed by the cross-connect unit on a board. See Figure 6-4.

Issue 01 (2011-10-20)


145



Figure 6-4 Inter-board cross-connections A 3(RX1/TX1)-1 5(RX3/TX3)-1

201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3

6(RX4/TX4)-1

201(LP1/LP1)-4

3(RX1/TX1)-1 5(RX3/TX3)-1

201(LP1/LP1)-1 201(LP1/LP1)-2 201(LP1/LP1)-3

6(RX4/TX4)-1

201(LP1/LP1)-4

4(RX2/TX2)-1

1(IN1/OUT1)-1

B 4(RX2/TX2)-1

1(IN1/OUT1)-1

TIP

When SNCP protection implemented by cross-connections (this SNCP protection is referred to as SNCP services in some scenarios) is configured, cross-connections with the same source but different sinks are configured at the source end of the SNCP protection (services are dually fed) and cross-connections with the same sink but different sources are configured at the sink end (services are selectively received).

6.1.3 Cross-Connection Ability The product provides the service grooming within the NE through the cross-connection bus. As a result, the product can save the wavelength resource, lower the networking cost and make the network more flexible. The cross-connection ability depends on the cross-connection bus type, which is different in the two types of chassis. The OptiX OSN 1800 I chassis has a low service access capacity, and its cross-connection bus is simple. It grooms electrical layer signals as a service access node on the edge, and improves the utilization of wavelength resources at the access layer. The OptiX OSN 1800 II chassis has a large service access capacity, and its cross-connection bus is complex. It grooms electrical layer signals as a service convergence node, and enhances the network flexibility. NOTE

This section describes the cross-connection capability of the backpanel. Different boards may have different cross-connection capacities and support different cross-connection slots. For details, see section Function and Features in the Hardware Description.

OptiX OSN 1800 I Figure 6-5 shows the cross-connection capacities among the four slots of the OptiX OSN 1800 I chassis. The cross-connection capacities are different.

Issue 01 (2011-10-20)


146



SLOT 5

(SLOT 6)

Figure 6-5 Cross-connection ability of the OptiX OSN 1800 I chassis

SLOT 3

SLOT 4

SLOT 1

（SLOT 2）

Supports eight pairs of cross-connections of Any services Supports one pair of cross-connections of Any services.

OptiX OSN 1800 II Figure 6-6 shows the cross-connection capacities among the eight slots of the OptiX OSN 1800 II chassis. The cross-connection capacities are different.

SLOT 11

SLOT 10 SLOT 9

Figure 6-6 Cross-connection ability of the OptiX OSN 1800 II chassis

SLOT 7

SLOT 8

SLOT 5

SLOT 6

SLOT 3

SLOT 4

SLOT 1

SLOT 2

Supports eight pairs of cross-connections of Any services. Supports one pair of cross-connections of Any services.

6.1.4 Formats of Ethernet Frames To implement the VLAN and QinQ functions, the IEEE 802.1q and IEEE 802.1ad protocols define different formats of the Ethernet frames, which contain different VLAN information. To implement the VLAN function, the IEEE 802.1q protocol defines the Ethernet frame format that contains the VLAN information. Compared with the ordinary Ethernet frame, the frame with the format defined by the IEEE 802.1q protocol is added with a four-byte header. To implement VLAN nesting (QinQ), the IEEE 802.1ad protocol defines two VLAN tag types. See Figure 6-7. The VLAN tag types are defined to differentiate the services on the client side and the services on the supplier service side. l

Issue 01 (2011-10-20)

The VLAN tag used on the client side is represented as C-VLAN, of which the frame format is the same as the frame format defined by the IEEE 802.1q protocol. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

147


l


The VLAN tag used on the supplier service side is represented as S-VLAN.

Figure 6-7 Formats of Ethernet frames 802.1q frame format Destination Source MAC Address MAC Address 6 bytes

VLAN

6 bytes

Length/Type

Data

FCS Check Character

2 bytes

Variable length

4 bytes

Length/Type

Data

FCS Check Character

2 bytes

Variable length

4 bytes

4 bytes

Format of the frame with one C-VLAN tag Destination Source MAC Address MAC Address 6 bytes

C-VLAN

6 bytes

4 bytes

Format of the frame with one S-VLAN tag nested with one C-VLAN tag Destination Source MAC MAC Address Address 6 bytes

S-VLAN

6 bytes

C-VLAN

4 bytes

4 bytes

Length/Type 2 bytes

Data

FCS Check Character

Variable length

4 bytes

The length of the data field is variable. maximum length of the data field depends on the maximum frame length that the ports of the equipment support. The four-byte S-VLAN or C-VLAN field is divided into two sub-fields: the tag protocol ID (TPID) and the tag control Information (TCI). Both the TPID and TCI consist of two bytes. See Figure 6-8. Figure 6-8 Positions of the TPID and TCI in the frame structure S-VLAN

Destination Source MAC TPID MAC Address Address 6 bytes

l

TCI

C-VLAN TPID

TCI

6 bytes 2 2 bytes 2 bytes 2 bytes 2bytes

Length/Type 2 bytes

Data Variable length

FCS Check Character 4 bytes

TPID structure

The TPID consists of two bytes and indicates the VLAN tag type. TPID of the C-VLAN is always 0x8100 whereas the TPID of the S-VLAN can be customized. Refer to Table 6-1.

Issue 01 (2011-10-20)


148



Table 6-1 Tag types defined by using the TPID Tag Type

Name

Value

C-VLAN Tag

802.1q Tag Protocol Type

0x8100

S-VLAN Tag

802.1q Service Tag Type

Customizable

NOTE

The IEEE 802.1ad specifies the TPID of the S-VLAN to 0x88a8. In actual application, the setting of TPID for the S-VLAN tag varies according to the equipment manufacturer. To ensure compatibility between interconnected equipment, it is recommended that you set the TPIDs of the S-VLAN tags of the interconnected equipment to the same value within 0X600–FFFF.

l

TCI structure

The TCI structure of the S-TAG is basically the same as the TCI structure of the C-TAG. VLAN ID (VID) field consists of 12 bits and ranges from 0 to 4095. The difference is that the TCI of the S-TAG contains the drop eligible (DE) indication and works with the priority code point (PCP) to indicate the priority of the S-TAG frame. The TCI structures of the C-TAG and S-TAG are shown in Figure 6-9 and Figure 6-10. Figure 6-9 TCI structure of the C-TAG Octets:

1

2 PCP

Bits:

8

VID

CFI 6

5

4

VID 1

8

1

The TCI field of the C-TAG consists of the following bytes: l

PCP: three bits

l

CFI: one bit

Figure 6-10 TCI structure of the S-TAG Octets:

1

2 PCP

Bits:

8

VID

DE 6

5

4

VID 1

8

1

The TCI field of the S-TAG consists of the following bytes: l

PCP: three bits

l

DE: one bit

l

VID: 12 bits

Issue 01 (2011-10-20)


149



6.1.5 External Ports and Internal Ports External ports on Ethernet boards are used to access the services on the user side. Internal ports on Ethernet boards are used to encapsulate and map the services into the transmission network for transparent transmission. External ports on Ethernet boards (that is, external physical ports) are also referred to as PORT ports, client-side ports, or user-side ports, which are used to access Ethernet services on the user side. Internal ports on Ethernet boards (that is, internal VCTRUNKs) are also referred to as systemside ports or backplane-side ports in certain cases, which are used to encapsulate and map services into the WDM side. Figure 6-11 External ports and internal ports on Ethernet boards External port

VCTRUNK port

Interface module

Service processing module

Encapsulation/ Mapping module

Interface conversion module

6.1.6 Auto-Negotiation The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network. This function also allows the network equipment to receive similar information that the opposite end may transfer. The working modes of the interconnected ports on the equipment at both ends must be the same. Otherwise, the services are unavailable. If the working mode of the port of the equipment on the opposite side is full duplex and if the working mode of the port on the local equipment is auto-negotiation, the local equipment works in the half-duplex mode. That is, the working modes of the interconnected ports at both ends are different, and thus packets may be lost. Hence, when the working mode of the port of the equipment on the opposite side is full duplex, you need to set working mode of the port on the local equipment to full duplex. NOTE

When the interconnected ports on both sides work in the auto-negotiation mode, the equipment on both sides can negotiate the flow control through the auto-negotiation function.

The auto-negotiation function uses fast link pulses (FLPs) and normal link pulses (NLPs) to transfer information of the working mode so that no packet or upper layer protocol overhead needs to be added.

Issue 01 (2011-10-20)


150



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

Auto-Negotiation Flow Control When the Ethernet port works in the auto-negotiation mode, you can adopt the auto-negotiation flow control function. The auto-negotiation flow control modes include the following: l

Enable dissymmetric flow control The port can transmit PAUSE frames in the case of congestion but cannot process the received PAUSE frames.

l

Enable symmetric flow control The port can transmit PAUSE frames and process the received PAUSE frames.

l

Enable symmetric/dissymmetric flow control The port has the following abilities: – Transmits and processes PAUSE frames. – Transmits PAUSE frames but cannot process the received PAUSE frames. – Processes the received PAUSE frames but cannot transmit PAUSE frames.

l

Disable The port does not support the non-auto-negotiation flow control function.

Non-Auto-Negotiation Flow Control When the Ethernet port works in a fixed working mode, you can adopt the non-auto-negotiation flow control function. The non-auto-negotiation flow control modes include the following: l

Send only The port can transmit PAUSE frames in the case of congestion but cannot process the received PAUSE frames.

l

Receive only The port can process the received PAUSE frames but cannot transmit PAUSE frames in the case of congestion.

l

Send and receive The port can transmit PAUSE frames and process the received PAUSE frames.

l

Disable The port does not support the non-auto-negotiation flow control function.

Issue 01 (2011-10-20)


151



Realization Principle The realization principle of the flow control function is described as follows: 1.

When congestion occurs in the receive queue of an Ethernet port (the data in the receive buffer exceeds a certain threshold) and the port is capable of sending PAUSE frames, the port sends a PAUSE frame to the opposite end. The pause-time value in the frame is N (0
2.

If the Ethernet port at the opposite end is capable of processing PAUSE frames, this Ethernet port stops sending data within a specified period of time N (the unit is the time required for sending 512 bits) after receiving the PAUSE frame.

3.

If the congestion at the receive port is cleared (the data in the receive buffer is below a certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose pause-time is 0 to notify the opposite end to send data.

IEEE 802.3 defines the format of the PAUSE frame as follows: l

Destination address: 01-80-C2-00-00-01 (multicast address)

l

Source address: MAC address of the source port

l

Type/Length: 88-08 (MAC control frame)

l

MAC control code: 00-01 (PAUSE frame)

l

MAC control parameter: pause-time (two bytes)

Figure 6-12 Structure of the PAUSE frame 01-80-C2-00-00-01

6 octets

XX-XX-XX-XX-XX-XX

6 octets

Type/Length

88-08

2 octets

MAC control opcode

00-01

2 octets

MAC control parameter (pause-time)

XX-XX

2 octets

Destination address Source address

Reserved

6.1.8 Tag Attributes In a virtual LAN, the tag attribute of an Ethernet port indicates how the port processes Ethernet packets. Ethernet packets are classified into tagged and untagged packets in 802.1q. A four-byte field is added to the Ethernet frame header of a tagged packet. The 802.1q-compliant field is used to identify the VLAN ID. An untagged packet does not have such a four-byte field. An Ethernet port has the following three types, which are Tag aware, Access and Hybrid. Issue 01 (2011-10-20)


152



See Table 6-2 for details on how an Ethernet board processes tagged and untagged packets at the ingress. Table 6-2 Processing policy at ingress Port Type

Tagged Packet

Untagged Packet

Tag aware

Transparently transmitted

Discarded

Access

Discarded

Added with the default VLAN tag

Hybrid


Added with the default VLAN tag

See Table 6-3 for details on how an Ethernet board processes tagged and untagged packets at the egress. Table 6-3 Processing policy at egress Port Type

Tagged Packet

Untagged Packet

Tag aware


-

Access

The VLAN tag is removed

-

Hybrid

The VLAN tag is removed if it is the same as the default tag for the port

-

Transparently transmitted if the VLAN tag is different from the default tag for the port

As shown in Table 6-2 and Table 6-3, in an actual network, you need to set the port type for the Ethernet board of an NE according to the Tag attribute of the messages sent from the userside equipment. If the user-side equipment sends the Untag message, set the external port to Access and set the internal port to Tag aware. If the user-side equipment sends the Tag message, set the external port to Tag aware and set the internal port to Tag aware. For example, if the source equipment of a service does not support Tag messages but the sink equipment supports Tag messages, you need to set the external port of the Ethernet board that resides on the NE connected to the source to Access, and set the external port of the Ethernet board that resides on the NE connected to the sink to Tag aware. Set the internal ports of the Ethernet board that resides on the NEs connected to the source and the sink to Tag aware.

6.1.9 Bridges Bridge is the functional unit that is used to implement the interconnection between two or more LANs. Various bridge (VB) is the unique concept for Huawei products. For Ethernet data boards that have the Layer 2 switching capability, the switching domain can be divided into multiple subIssue 01 (2011-10-20)


153



switching domains. As a result, if no services are interconnected, different VBs cannot access each other. Each VB has an independent configuration mode and uses an independent VLAN. Different VBs can use the same VLAN. By configuring the mounting relationship, you can mount multiple external ports and VCTRUNK ports to the same VB. Figure 6-13 shows the relationship between the VBs, external ports, and VCTRUNK ports. Figure 6-13 Relationship between the VBs, external ports, and VCTRUNKs VB1 PORT1

VCTRUNK1

PORT2

VCTRUNK2

PORT3

VCTRUNK3

VB2 PORT4

VCTRUNK4

PORT5

VCTRUNK5

PORT6

VCTRUNK6

Types of Bridges As listed in Table 6-4, Ethernet boards support three types of bridges. Table 6-4 Types of bridges supported by Ethernet boards

Issue 01 (2011-10-20)

Bridge Type

Bridge Switch Mode

Bridge Learning Mode

Ingress Filter

IEEE 802.1d MAC bridge

SVL/Ingress Filter Disable

SVL

Disabled

IEEE 802.1q virtual bridge

IVL/Ingress Filter Enable

IVL

Enabled

IEEE 802.1ad provider bridge

1

SVL/Ingress Filter Disable

SVL

Disabled

2

IVL/Ingress Filter Enable

IVL

Enabled


154



l

IEEE 802.1d MAC bridge: The IEEE 802.1d MAC bridge does not check the contents of the VLAN tags in the data frames. It performs Layer 2 switching based on the destination MAC addresses of the data frames.

l

IEEE 802.1q bridge: The IEEE 802.1q bridge supports isolation by using one layer of VLAN tags. This bridge checks the contents of the VLAN tags in the data frames and performs Layer 2 switching based on the destination MAC addresses and VLAN IDs.

l

The IEEE 802.1ad bridge: The IEEE 802.1ad bridge supports data frames with two layers of VLAN tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and supports only the mounted ports whose attributes are C-Aware or S-Aware. This bridge supports the following switching modes: 1.

This bridge does not check the contents of the VLAN tags in the data frames. It performs Layer 2 switching based on the destination MAC addresses of the data frames.

2.

This bridge checks the contents of the VLAN tags in the data frames and performs Layer 2 switching based on the destination MAC addresses and the S-VLAN IDs of the data frames.

MAC Address Learning To forward Layer 2 switching services, a bridge must learn the MAC addresses of the services. A bridge can learn MAC addresses in shared VLAN learning (SVL) mode or independence VLAN learning (IVL) mode. l

When a bridge learns MAC addresses in SVL mode, it creates an entry in the MAC address table based on the source MAC address and the source port of a data frame. This entry is valid to all VLANs

l

When a bridge learns MAC addresses in IVL mode, it creates an entry in the MAC address table based on the source MAC address of a data frame, the VLAN ID contained in the data frame, and the source port of the data frame. This entry is valid only to the VLAN identified by the VLAN ID contained in the data frame.

MAC Address Table Entries in the MAC address table indicate the corresponding relationship between the MAC addresses and the ports. MAC address table contains the following entries: l

Dynamic entry Indicates the entry that the bridge obtains by adopting the SVL/IVL learning mode. The dynamic entry ages and is even lost after the Ethernet switching board is reset.

l

Static entry Indicates the entry corresponding to the MAC address and the port that the network administrator manually adds to the MAC address table on the NMS. The static entry does not age and is not lost after the Ethernet switching board is reset.

l

Blackhole entry Indicates the entry used to discard the data frame that contains the specified destination MAC address, and is also referred to as the MAC address disable entry. The blackhole entry is configured by the network administrator. This entry does not age and is not lost after the Ethernet switching board is reset.

Issue 01 (2011-10-20)


155



NOTE

l If a routing entry is not updated within a specific period of time, that is, if the MAC address fails to be learned because the new data frame from the MAC address is not received, this routing entry is automatically deleted. This mechanism is considered as aging, and this period of time is considered as the aging time. The aging time of the MAC address table is five minutes by default and can be set by using the NMS. l A limited number of MAC addresses can be learned at a time.

Hub/Spoke Generally, the central station and non-central stations can access each other but the non-central stations cannot access each other in the case of convergence services. Hence, the ports mounted to the bridge need to be defined as Hub ports or Spoke ports. l

Hub port Hub ports can access each other. Hub ports and Spoke ports can also access each other.

l

Spoke port Spoke ports cannot access each other. Hub ports and Spoke ports can access each other.

The mounted ports are Hub ports by default.

6.1.10 VLAN Group Certain VLANs with consecutive VLAN IDs are allocated to the same VLAN group. Generally, these VLANs are of the same service type. U2000 or Web LCT creates services operations on the VLAN specified with the first VLAN ID in a VLAN group so that other VLANs in the VLAN group are applied with the same configuration.

6.1.11 Board Model (Standard Mode and Compatible Mode) Starting from V100R003C01, some boards support new board models. To distinguish new models from existing models, the new board models are marked as standard mode and the existing board models are marked as compatible mode. Compared with the compatible mode, the standard mode facilitates operations and reduces maintenance costs. Service configurations on the NMS vary according to board models.

Boards Supporting Standard Mode Table 6-5 lists the boards that support standard mode, the names of the boards in different modes, and the availability of the boards on different types of equipment. Table 6-5 Names displayed on the NMS and availability on different types of equipment

Issue 01 (2011-10-20)

Physical Board

Name in Standard Mode (Standard Mode, adding logical board)

Name in Compatible Mode (Compatible Mode, adding logical board)

F2LSX

F2LSX

LSX

F2LQM

F2LQM

LQM


156



Physical Board

Name in Standard Mode (Standard Mode, adding logical board)

Name in Compatible Mode (Compatible Mode, adding logical board)

F2LQM2

F2LQM2

LQM2

F2ELOM

F2ELOM

ELOM

F2LDGF2

F2LDGF2

LDGF2

F1LDX

F1LDX

-

NOTE

l The F1LDX boards support only the standard mode. l The standard mode is applicable only to the boards listed in the table above. The boards not listed in the table support only the compatible mode.

6.1.12 ODUflex Starting from V100R003C01, the equipment supports the ODUflex (ODUk with variable bandwidth) technology, which enables users to flexibly configure the container capacity based on service sizes, leveraging line bandwidth.

Applicable Boards OptiX OSN 1800 supports ODUflex that is applicable to the following boards: l

F2ELOM NOTE

The F2ELOM board support ODUflex only when they work in Standard Mode and ODU Timeslot Configuration Mode is set to Assign random.

ODUflex Involved Operations The following describes the GUIs for creating services involving ODUflex on the NMS and the navigation paths. Table 6-6 GUIs and navigation paths

Issue 01 (2011-10-20)

GUI on the NMS

Description

Navigation Path

WDM Interface

When the board where you want to create services is a line board or the LOA board and the services need to be encapsulated into ODUflex services, set ODU Timeslot Configuration Mode to Assign random.

In the NE Explorer, select the required board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree.


157



GUI on the NMS

Description

Navigation Path

Create CrossConnection Service

When Level is set to ODUflex, you must set ODUflex Timeslots.

In the NE Explorer, select the required NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New.

NOTE

l The value of ODUflex Timeslots is in the range of 3-7, which indicates that the service rate supported by ODUflex is in the range of 3.75 Gbit/s (3 x 1.25 Gbit/s) to 8.75 Gbit/s (7 x 1.25 Gbit/s). l The rule for calculating the value of ODUflex Timeslots is as follows: Value = Service rate mapping the service type configured at a port/Bandwidth of each TS subtimeslot (1.25 Gbit/s). If the value is not an integer, the value is the quotient plus 1. For example, if an FC400 service is received, the value of ODUflex Timeslots is 4 (4.25 Gbit/s/1.25 Gbit/s = 3.4, 3 + 1 = 4).

ODUflex Configuration Procedure Figure 6-14 shows the ODUflex configuration flowchart. Figure 6-14 ODUflex configuration flowchart 1

Configure the port working mode

2

Configure the timeslot configuration mode

3

Configure the service type

4

Configure crossconnections

Table 6-7 describes the ODUflex configuration procedure.

Issue 01 (2011-10-20)


158



Table 6-7 Configuration procedure No. 1

Action

Involved Board

Description

Configure the port working mode.

F2ELOM

l Parameter settings: Set Port Working Mode to ODUflex non-convergence mode. NOTE Before setteing Port Working Mode, ensure Service Type of the port is NULL.

l Operation description: In the NE Explorer, select the required board and choose Configuration > Working Mode from the Function Tree. In the displayed window. 2

3

Configure the timeslot configuration mode.

F2ELOM

Configure the service type.

F2ELOM

l Parameter settings: Set ODU Timeslot Configuration Mode to Assign random for the required ports. l Operation description: In the NE Explorer, select the required board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. l Parameter settings: Set the service type based on the service plan. l Operation description: Choose Configuration > WDM Interface from the Function Tree.

5

Configure crossconnections.

F2ELOM: crossconnections from LP ports to the WDM side

l Parameter settings: – Set Level to ODUflex and select the source slot, sink slot, source optical port, sink optical port, source optical channel, and sink optical channel. – Set ODUflex Timeslots based on the service type that you set in step 3. See the note below Table 6-6 to calculate the value. l Operation description: In the NE Explorer, select the required NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click New.

6.2 Configuring Services on Boards The services that can be configured vary according to boards. The topic describes service configurations on some boards that provide comprehensive functions.

Issue 01 (2011-10-20)


159



6.2.1 ELOM Service Configuration Physical and Logical Ports This section describes the display of ports on the board and provides the port models and the configuration steps for this board.

Display of Optical Ports Table 6-8 lists the sequence number displayed on an NMS of the optical port on the ELOM board front panel. Table 6-8 Display of the ELOM optical ports Optical Ports on the Front Panel

Optical Port Displayed on the U2000

IN1/OUT1

1

IN2/OUT2

2

RX1/TX1

3

RX2/TX2

4

RX3/TX3

5

RX4/TX4

6

RX5/TX5

7

RX6/TX6

8

RX7/TX7

9

RX8/TX8

10

NOTE

An optical port number displayed on the U2000 indicates a pair of actual optical ports, one for transmitting signals, and the other for receiving signals.

Port Models of ELOM(COMP) l

Issue 01 (2011-10-20)

1*AP8 ODU1 mode


160



Figure 6-15 Port model for the ELOM(COMP) board working in 1*AP8 ODU1 mode

3(RX1/TX1) 4(RX2/TX2) 5(RX3/TX3)

ODU1 201(ClientLP1/ClientLP1)-1

51

201(ClientLP1/ClientLP1)-8 203(ClientLP3/ClientLP3)-1 1(IN1/OUT1)

6(RX4/TX4) 7(RX5/TX5) 8(RX6/TX6) 9(RX7/TX7) 10(RX8/TX8)

203(ClientLP3/ClientLP3)-8 205(ClientLP5/ClientLP5)-1

ODU2

OTU2 2(IN2/OUT2)


207(ClientLP7/ClientLP7)-8

: Service cross-connection, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS : Client-side services : WDM-side services

NOTE

The client-side signals received at client-side optical ports 3–10 (RX1/TX1 to RX8/TX8) can be cross-connected to any 8 channels among 32 channels of logical ports 201–207.

– Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3–10 (RX1/TX1 to RX8/TX8). – Alarms and performance events related to ODU1 electrical-layer overheads are reported through channel 1 of logical ports 201, 203, 205, and 207. – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channels 1 and 2 of logical port 51. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2). l

Issue 01 (2011-10-20)

1*AP4 ODU1 mode


161



Figure 6-16 Port model for the ELOM(COMP) board working in 1*AP4 ODU1 mode ODU1 3(RX1/TX1)


5(RX3/TX3)


51

1(IN1/OUT1) ODU2

7(RX5/TX5)


9(RX7/TX7)


OTU2 2(IN2/OUT2)

: Virtual channel, which does not need to be configured on the NMS : Client-side services : WDM-side services

– When the client services are not OTU1: – Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3, 5, 7, and 9 (RX1/TX1, RX3/TX3, RX5/TX5 and RX7/TX7). – The downstream ODU1 alarms and performance events are reported through channel 1 of logical ports 201, 203, 205, and 207. – When the client services are OTU1: – The upstream OTU1 and ODU1 alarms and performance events are reported through channel 1 of client-side optical ports 3, 5, 7, and 9 (RX1/TX1, RX3/TX3, RX5/TX5 and RX7/TX7). – The downstream ODU1 alarms and performance events are reported through channel 1 of logical ports 201, 203, 205, and 207. – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channels 1 and 2 of logical port 51. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2). l

Issue 01 (2011-10-20)

1*AP1 ODU2 mode


162



Figure 6-17 Port model for the ELOM(COMP) board working in 1*AP1 ODU2 mode 201(ClientLP1/ClientLP1)-1

1(IN1/OUT1) 3(RX1/TX1)

ODU2

OTU2 2(IN2/OUT2)


– Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical port 3 (RX1/TX1). – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through logical port 201. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2). l

1*AP2 ODU2 mode Figure 6-18 Port model for the ELOM(COMP) board working in 1*AP2 ODU2 mode 201(ClientLP1/ClientLP1)-1 3(RX1/TX1)

1(IN1/OUT1) ODU2

OTU2 2(IN2/OUT2)

7(RX5/TX5)


Issue 01 (2011-10-20)


163



– Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3 and 7 (RX1/TX1 and RX5/TX5). – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through logical port 201. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2). l

1*AP8 ODU0&ODU1 mode

Figure 6-19 Port model for the ELOM(COMP) board working in 1*AP8 ODU0&ODU1 mode ODU0 3(RX1/TX1)


4(RX2/TX2)


5(RX3/TX3)


6(RX4/TX4)


51(LP1/LP1)-7169 51(LP1/LP1)-7170 51(LP1/LP1)-7171 51(LP1/LP1)-7172

51(LP1/LP1)-7174 7(RX5/TX5)

1(IN1/OUT1)

51(LP1/LP1)-7173


51(LP1/LP1)-7175

8(RX6/TX6)


51(LP1/LP1)-7176 ODU1

9(RX7/TX7)


10(RX8/TX8)


ODU2

OTU2 2(IN2/OUT2)



NOTE

The signals received at logical ports 201–208 can be cross-connected to any 8 channels among the 12 channels at optical port 52, but the total bandwidth cannot exceed 10.3 Gbit/s.

– When the client services are not OTU1: – Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3–10 (RX1/TX1 to RX8/TX8). – The downstream ODU0/ODU1 alarms and performance events are reported through channel 1 of logical ports 201 to 208. – When the client services are OTU1: – The upstream OTU1 and ODU1 alarms and performance events are reported through channel 1 of client-side optical ports 3 (RX1/TX1), 5 (RX3/TX3), 7 (RX5/TX5) and 9 (RX7/TX7). – The downstream ODU1 alarms and performance events are reported through channel 1 of logical ports 201, 203, 205, and 207. – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channels 1 and 2 of logical port 51.

Issue 01 (2011-10-20)


164



– Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 (IN1/ OUT1) and 2 (IN2/OUT2).

Port Models of ELOM(STND) l

1*AP8 general mode

Figure 6-20 Port model for the ELOM(STND) board working in 1*AP8 general mode

3(TX1/RX1) 4(TX2/RX2) 5(TX3/RX3) 6(TX4/RX4)


ODU0( 7681)

ODU1( 8705)

ODU0( 7688)

ODU1( 8708) ODU0( 7169)

1

ODU2

201

OTU2

1(IN1/OUT1)

OTU2

2(IN2/OUT2)

ODU0( 7176) ODUfle x(8193)

ODU0/ODU1 /ODUflex

202 ODUfle x(8196)

ODU0/ODU1 /ODUflex

2

7(TX5/RX5)

ODU0( 7681)

ODU1( 8705)

ODU0( 7688)

ODU1( 8708) ODU0( 7169)

8(TX6/RX6) 9(TX7/RX7)

208(LP8/LP8)-1

10(TX8/RX8)

208(LP8/LP8)-8

208 ODU0/ODU1 /ODUflex

ODU2 ODU0( 7176) ODUfle x(8193) ODUfle x(8196)

: Active service cross-connection, which needs to be configured on the NMS : Client-side services : WDM-side services

– Ports 201 to 208 can be set to ODU0 non-convergence mode (Any->ODU0), ODU1 convergence mode (n*Any->ODU1), ODU1 non-convergence mode (OTU1/Any>ODU1), ODUflex non-convergence mode (Any->ODUflex), or None (not for ports) mode. The default mode of ports 201, 203, 205, and 207 is ODU1 non-convergence mode. The default mode of ports 202, 204, 206, and 208 is None (not for ports). – After power is supplied to the board, straight-through cross-connections are configured from channel 1 at ports 3(TX1/RX1)-10(TX8/RX8) to channel 1 at ports 201-208 by default. When a port works in ODU1 convergence mode (n*Any->ODU1) mode, you can configure cross-connections from channel 1 at any port among ports 3(TX1/ RX1)-10(TX8/RX8) to any of the eight channels at the port. – OTU1 services can be received only through ports 3(TX1/RX1), 5(TX3/RX3), 7(TX5/ RX5), and 9(TX7/RX7) on the client side. – The upstream OTU1 and ODU1 alarms and performance events are reported through channel 1 of corresponding client-side optical ports. – The downstream ODU1 alarms and performance events are reported through channels 8705-8708 at optical ports 1 and 2. – When the client services are not OTU1: Issue 01 (2011-10-20)


165



– Alarms and performance events related to client signal overheads are reported through channel 1 of corresponding client-side optical ports. – ODU0 alarms and performance events are reported through channels 7169-7176 or channels 7681-7688 at optical ports 1 and 2. ODU1 alarms and performance events are reported through channels 8705-8708 at optical ports 1 and 2. ODUflex alarms and performance events are reported through channels 8193-8196 at optical ports 1 and 2. – When ODUk cross-connections are configured, the channel IDs vary according to ODUk mapping paths. The following table lists the mapping between channel IDs and mapping paths. Mapping Path

Channel ID

ODU0->ODU1->ODU2a

7681-7688

ODU0->ODU2

7169-7176

ODU1->ODU2

8705-8708

ODUflex->ODU2

8193-8196

a: Eight ODU0 channels are encapsulated into four ODU1 channels in sequence with each ODU1 channel containing two ODU0 channels. For example, ODU0 channels 7681 and 7682 are encapsulated into ODU1 channel 8705 and ODU0 channels 7683 and 7684 are encapsulated into ODU1 channel 8706. – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channel 1 of WDM-side optical ports 1 (IN1/OUT1) and 2 (IN2/ OUT2). – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 (IN1/ OUT1) and 2 (IN2/OUT2). NOTE

The total bandwidth for services received at ports 201(LP1/LP1)-208(LP8/LP8) cannot exceed 10 Gbit/s if intra-board 1+1 protection is configured. If intra-board 1+1 protection is not configured, the total bandwidth can reach 20 Gbit/s.

l

Issue 01 (2011-10-20)

1*AP1 ODU2 mode


166



Figure 6-21 Port model for the ELOM(STND) board working in 1*AP1 ODU2 mode 1

201 ODU2

3(RX1/TX1)

ODU2

OTU2

1(IN1/OUT1)

OTU2

2(IN2/OUT2)

2 ODU2

: Active service cross-connection, which needs to be configured on the NMS : Standby service cross-connection, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS : Client-side services : WDM-side services

– Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3 (RX1/TX1). – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channel 1 of WDM-side optical ports 1 (IN1/OUT1) and 2 (IN2/ OUT2). – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 (IN1/ OUT1) and 2 (IN2/OUT2). – Intra-board 1+1 protection or ODU2 SNCP protection can be configured on the WDM side. l

Issue 01 (2011-10-20)

1*AP2 ODUflex mode


167



Figure 6-22 Port model for the ELOM(STND) board working in 1*AP2 ODUflex mode 1

201

3(RX1/TX1)

ODUflex (8193) ODUflex

ODU2

OTU2

1(IN1/OUT1)

ODUflex (8196)

2

205 ODUflex (8193) 7(RX5/TX5)

ODU2

ODUflex

OTU2

2(IN2/OUT2)

ODUflex (8196)


– Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3 (RX1/TX1) and 7 (RX5/TX5). – Alarms and performance events related to OTU2/ODU2 electrical-layer overheads are reported through channel 1 of WDM-side optical ports 1 (IN1/OUT1) and 2 (IN2/ OUT2). – Alarms and performance events related to ODUflex electrical-layer overheads are reported through channel 8193 - 8196 of WDM-side optical ports 1 (IN1/OUT1) and 2 (IN2/OUT2). – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 (IN1/ OUT1) and 2 (IN2/OUT2). – Intra-board 1+1 protection or ODUflex SNCP protection can be configured on the WDM side.

Board Configuration This section describes the cross-connections and provides the configuration steps for this board on the NMS.

Cross-Connections When working in ODU1 aggregation mode, the ELOM board supports intra-board crossconnections of the received Any services. When working in 1*AP8 ODU0&ODU1 mode, the ELOM board supports intra-board cross-connections of the ODU0 and ODU1 services. The board provides intra-board cross-connections of the services after required timeslots are configured. Figure 6-23 and Figure 6-24 show an example in which intra-board crossconnections are configured on the ELOM board.

Issue 01 (2011-10-20)


168



Figure 6-23 Cross-connections on the ELOM board (1*AP8 ODU1 mode) Client Side

WDM Side 3(TX1/RX1) 4(TX2/RX2) 5(TX3/RX3) 6(TX4/RX4) 7(TX5/RX5) 8(TX6/RX6)

201(ClientLP1/ClientLP1)-1 1

201(ClientLP1/ClientLP1)-8 203(ClientLP3/ClientLP3)-1 203(ClientLP3/ClientLP3)-8 205(ClientLP5/ClientLP5)-1

9(TX7/RX7)


10(TX8/RX8)


51(LP1/ LP1)-1

1(IN1/OUT1)

51(LP1/ LP1)-2

2(IN2/OUT2)

Figure 6-24 Cross-connections on the ELOM board (1*AP8 ODU0&ODU1 mode) Client Side

l

51(LP1/LP1)-7169

3(TX1/RX1)


51(LP1/LP1)-7170

4(TX2/RX2)

202(ClientLP2/ClientLP2)-1 1

51(LP1/LP1)-7171

5(TX3/RX3)


6(TX4/RX4)


51(LP1/LP1)-7174

7(TX5/RX5)


51(LP1/LP1)-7175

WDM Side

51(LP1/LP1)-7172 51(LP1/LP1)-7173

1(IN1/OUT1)

51(LP1/LP1)-7176

8(TX6/RX6)


9(TX7/RX7)


51(LP1/LP1)-8706

10(TX8/RX8)


51(LP1/LP1)-8707

2(IN2/OUT2)

51(LP1/LP1)-8705

51(LP1/LP1)-8708

Intra-board cross-connections – In 1*AP8 ODU1 mode, client signals are cross-connected to channels 1-8 of logical ports 201, 203, 205, 207. An example is shown as (1) in Figure 6-23. – In 1*AP8 ODU0&ODU1 mode, ODU0 signals of logical ports 201-208 are crossconnected to channels 7169-7176 of logical ports 51, ODU1 signals of logical ports 201-208 are cross-connected to channels 8705-8708 of logical ports 51. An example is shown as (1) in Figure 6-24.

Configuration Procedure of ELOM(COMP) 1.

Set board working mode. l In the NE Explorer, select the ELOM board and then choose Configuration > Working Mode from the Function Tree. l select the corresponding mode in Board Working Mode as required. l Optional: Select the working mode for each port in Port Working Mode.

Issue 01 (2011-10-20)


169



NOTE

You need to set the working mode for each port only when Board Working Mode is 1*AP8 ODU0&ODU1 mode.

2.

Set port parameters. l Set the service type for the client-side optical ports 3 (RX1/TX1)-10 (RX8/TX8). l Set ODU Timeslot Configuration Mode based on the requirements for service mapping paths. For details on the configurations, see 5.10.1 ELOM Parameters.

3.

Optional: When Board Working Mode is set to 1*AP8 ODU1 mode for the ELOM board, cross-connections from the client-side optical ports to logical ports 201, 203, 205 and 207 must be configured. When configuring cross-connections, set Level to Any and Service Type to the same value as that in the WDM interface. l Configure intra-board cross-connections. For details, see (1) in Figure 6-23. Table 6-9 ELOM intra-board cross-connections (1*AP8 ODU1 mode) Lev el

Ser vice Typ e

Source Optical Port

Source Optical Channel

Sink Optical Port

Sink Optical Channel

Any

ST M-1 , ST M-4 ...

3 (TX1/ RX1) to 10 (RX8/ TX8)

1

201 (ClientLP1/ ClientLP1)

1 to 8

203 (ClientLP3/ ClientLP3) 205 (ClientLP5/ ClientLP5) 207 (ClientLP7/ ClientLP7)

4.

Optional: When Board Working Mode is set to 1*AP8 ODU0&ODU1 mode for the ELOM board, cross-connections from the logical ports 201-208 to logical ports 51 must be configured. When configuring cross-connections. l Configure intra-board cross-connections. For details, see (1) in Figure 6-24.

Issue 01 (2011-10-20)


170



Table 6-10 ELOM intra-board cross-connections (1*AP8 ODU0&ODU1 mode) Lev el

Ser vice Typ e

Source Optical Port


Sink Optical Port


Any

OD U0

201 (ClientLP 1/ ClientLP1 ) to 208 (ClientLP 8/ ClientLP8 )

1

51(LP1/LP1)

7169 to 7176

Any

OD U1

201 (ClientLP 1/ ClientLP1 ) to 208 (ClientLP 8/ ClientLP8 )

1

51(LP1/LP1)

8705 to 8708

Configuration Procedure of ELOM(STND) 1.

Set board working mode. l In the NE Explorer, select the ELOM board and then choose Configuration > Working Mode from the Function Tree. l select the corresponding mode in Board Working Mode as required. l Optional: Select the working mode for each port in Port Working Mode. NOTE

You need to set the working mode for each port only when Board Working Mode is 1*AP8 general mode.

2.

Set port parameters. l Set the service type for the client-side optical ports 3 (RX1/TX1)-10 (RX8/TX8). For details on the configurations, see 5.10.1 ELOM Parameters.

3.

Configure intra-board pass-through services. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click New. In the Create Cross-Connection Service window that is displayed, set related parameters. The detailed configuration is as follows: l 1*AP8 general mode

Issue 01 (2011-10-20)


171



Table 6-11 Configuration for intra-board pass-through services on the ELOM board Level

Source Board (ELOM)

Sink Board (ELOM)

Source Optical Port b


Sink Optical Port b


GE (GFP_ T), or Any

3(TX1/RX1)

1

201(LP1/LP1)

1

GE (GFP_ T), or Any

4(TX2/RX2)

1

202(LP2/LP2)

1

GE (GFP_ T), or Any

5(TX3/RX3)

1

203(LP3/LP3)

1

GE (GFP_ T), or Any

6(TX4/RX4)

1

204(LP4/LP4)

1

GE (GFP_ T), or Any

7(TX5/RX5)

1

205(LP5/LP5)

1

GE (GFP_ T), or Any

8(TX6/RX6)

1

206(LP6/LP6)

1

GE (GFP_ T), or Any

9(TX7/RX7)

1

207(LP7/LP7)

1

GE (GFP_ T), or Any

10(TX8/RX8)

1

208(LP8/LP8)

1

a

a: When Level is set to ANY, you need to set Service Type. The Service Type setting must be the same as the service type specified in the WDM Interface window. b: When Port Working Mode is set to ODU1 convergence mode, a source optical port can be cross-connected to any sink optical port. l 1*AP1 ODU2 mode

Issue 01 (2011-10-20)


172



In this mode, you do not need to configure intra-board pass-through or cross-connection services. l 2*AP2 ODUflex mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. 4.

Configure ODUk SNCP protection. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click Create SNCP Service. In the Create SNCP Service window that is displayed, set related parameters. Table 6-12 Configuration for SNCP protection on the ELOM board Item

1*AP8 general mode

1*AP1 ODU2 mode

1*AP2 ODUflex mode

Protection Type

ODUK SNCP

ODUK SNCP

ODUK SNCP

Service Type

ODU0, ODU1, ODUflex

ODU2

ODUflex

Worki ng Servic e

Source Optical Port

1(IN1/OUT1)

1(IN1/OUT1)

1(IN1/OUT1)

Source Optical Channel a

-

-

-

Sink Optical Port

201(LP1/ LP1) to 208 (LP8/LP8)

201(LP1/LP1)

205(LP5/LP5)


1

1

1

Source Optical Port

2(IN2/OUT2)

2(IN2/OUT2)

2(IN2/OUT2)


-

-

-

Protec tion Servic e

a: To select an optical channel, click the button behind Source Slot. Mapping paths for services are automatically displayed in Source Optical Channel based on the Service Type and channel settings.

6.2.2 LEM18 Service Configuration Issue 01 (2011-10-20)


173



Physical and Logical Ports This section describes how the ports on the LEM18 board front panel are displayed on the NMS and how to configure services for this board.

Display of Ports Table 6-13 lists the sequence numbers of the ports on the LEM18 board front panel displayed on the U2000. Table 6-13 Display of the LEM18 ports Port on the Front Panel

Port Displayed on the NMS

Layer 2 External Port

Layer 2 Internal Port

IN1/OUT1

3

PORT3

VCTRUNK1

IN2/OUT2

4

PORT4

VCTRUNK2

TX1/RX1

5

PORT5

VCTRUNK3

TX2/RX2

6

PORT6

/

…

…

…

/

TX18/RX18

22

PORT22

/

NOTE

l An optical port displayed on the NMS indicates a pair of actual optical ports, one for transmitting signals and the other for receiving signals. l The Layer 2 logical ports that map ports IN1/OUT1 and IN2/OUT2 vary according to board modes. When the board works in OTN mode, the mapping Layer 2 logical ports are internal ports VCTRUNK1 and VCTRUNK2; when the board works in 10GE mode, the mapping Layer 2 logical ports are external ports PORT3 and PORT4. l PORT5 and VCTRUNK3 share the same virtual port and only one port is valid at a time. PORT5 is valid by default. When VCTRUNK3 is used, VCTRUNK3 can be displayed on the NMS only when TX1/RX1 is deleted from the NMS. l VCTRUNK3 is used only to enable cascading of boards housed in paired slots.

Port Model l

OTN mode The port model for LEM18 board in OTN mode is shown in Figure 6-25.

Issue 01 (2011-10-20)


174



Figure 6-25 Port model for the LEM18 board working in OTN mode Backplane

VCTRUNK3 5(RX1/TX1)

PORT5

6(RX2/TX2)

PORT6 PORT7

8(RX4/TX4)

PORT8

9(RX5/TX5)

PORT9

10(RX6/TX6)

PORT10

11(RX7/TX7)

PORT11

VCTRUNK1

ODU2

OTU2

3(IN1/OUT1)

VCTRUNK2

ODU2

OTU2

4(IN2/OUT2)

……

……

7(RX3/TX3)

22(RX18/TX18)

PORT22

: Client-side services : WDM-side services : Ethernet service link, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS One-in-two module, which selects signals from only one of the two virtual ports (VCTRUNK3 and PORT5). The service to be received needs to be configured on the NMS.

– Alarms and performance events related to client signal overheads are reported through ports VCTRUNK1 to VCTRUNK3 or channel 1 of client-side optical ports 5-22 (RX1/ TX1 to RX18/TX18). – Alarms and performance events related to OTN electrical-layer overheads are reported through channel 1 of optical ports 3 (IN1/OUT1) and 4 (IN2/OUT2). – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 3 (IN1/ OUT1) and 4 (IN2/OUT2). l

10GE mode The port model for LEM18 board in 10GE mode is shown in Figure 6-26.

Issue 01 (2011-10-20)


175



Figure 6-26 Port model for the LEM18 board working in 10GE mode 3(IN1/OUT1)

PORT3

4(IN2/OUT2)

PORT4

Backplane

VCTRUNK3 5(RX1/TX1)

PORT5

6(RX2/TX2)

PORT6

7(RX3/TX3)

PORT7

8(RX4/TX4)

PORT8

9(RX5/TX5)

PORT9

……

……

……

22(RX18/TX18)

PORT22

: Client-side services : Ethernet service link, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS One-in-two module, which selects signals from only one of the two virtual ports (VCTRUNK3 and PORT5). The service to be received needs to be configured on the NMS.

Alarms and performance events related to client signal overheads are reported through port VCTRUNK3 or channel 1 of client-side optical ports 3 (IN1/OUT1), 4 (IN2/OUT2), and 5-22 (RX1/TX1 to RX18/TX18).

Board Configuration This section describes how the ports on the LEM18 board front panel are displayed on the NMS and how to configure services for this board.

Configuration Procedure 1.

Issue 01 (2011-10-20)

Set the optical port parameters of the board. Exercise caution when setting the following parameters. Parameter

Description

Board Mode

The default value is OTN mode. If the board is not used in OTN application scenarios, set this parameter to 10GE mode.


176



Parameter

Description

Service Type

Set the service type for client-side ports RX1/TX1 to RX18/TX18 based on the actual service that is received.

For details on the description and configuration method of the parameters, see 5.10.6 LEM18 Parameters. 2.

Optional: When port VCTRUNK3 is used to enable board cascading, delete port 5 (RX1/ TX1) and then port VCTRUNK3 will be valid automatically. For details, see B.21 Deleting Ports.

3.

Set the Ethernet port parameters of the board. Exercise caution when setting the following parameters. Classific ation

Paramet er

Description

Basic attributes

Enabled/ Disabled

Set this parameter to Enabled for ports in use.

Working Mode

Set the working mode to a value consistent with the working mode of the client equipment.

Maximum Frame

The value must be equal to or greater than the user-defined maximum frame length for transmitting data flows.

Network attributes

Port Attributes

Set this parameter to C-Aware or S-Aware when the QinQ technology is used for processing data packets.

Tag attributes

TAG

When Port Attributes is UNI, set this parameter to a proper value based on the VLAN tag contained in the data packets.

For details on the description and configuration method of the parameters, see 5.10.6 LEM18 Parameters. 4.

Configure Ethernet services, including EPL, EVPL, EPLAN and EVPLAN services. For details, see 6.4 Configuring EPL/EVPL Services and 6.5 Configuring EPLAN/ EVPLAN Services.

6.2.3 LQG Service Configuration Physical and Logical Ports This section describes the display of ports on the board and provides the configuration rules for this board on the NMS.

Display of Ports Table 6-14 lists the sequence number displayed in an NMS system of the ports on the LQG board front panel. Issue 01 (2011-10-20)


177



Table 6-14 Display of the LQG ports Ports on the Front Panel

Port Displayed on the U2000

IN1/OUT1

1

IN2/OUT2

2

TX1/RX1

3

TX2/RX2

4

TX3/RX3

5

TX4/RX4

6

NOTE


Port model Figure 6-27 shows the port model on the LQG board. Figure 6-27 Schematic diagram of the cross-connect ports on the LQG board

3(RX1/TX1)

201(LP/LP)-1

4(RX2/TX2)

201(LP/LP)-2

5(RX3/TX3)

201(LP/LP)-3

6(RX4/TX4)

201(LP/LP)-4

1(IN1/OUT1) ODU5G

OTU5G 2(IN2/OUT2)

: Client-side services : WDM-side services : Service cross-connection, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS

l

Alarms and performance events related to client signal overheads are reported through channel 1 of client-side optical ports 3-6 (RX1/TX1, RX2/TX2, RX3/TX3, and RX4/TX4).

l

Alarms and performance events related to OTN electrical-layer overheads are reported through channels 1 and 2 of logical port 201.

l

Alarms related to the WDM-side optical module and OTN optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2).

Issue 01 (2011-10-20)


178



Cross-Connect Ports The LQG board supports inter-board cross-connections and intra-board cross-connections of GE optical signals. This board implements service cross-connections through its cross-connect module. Figure 6-28 shows the cross-connections implemented on the LQG board. Figure 6-28 Example of cross-connections of the LQG board 3(TX1/RX1)

2

4(TX2/RX2) Client Side

1(IN1/OUT1)

201(LP/LP)-2 ODU5G

5(TX3/RX3) 6(TX4/RX4)

201(LP/LP)-1 OTU5G

201(LP/LP)-3 1 201(LP/LP)-4

3(TX1/RX1)

201(LP1/LP1)-1

4(TX2/RX2)

201(LP1/LP1)-2

Client Side 7(TX5/RX5)

201(LP1/LP1)-5

8(TX6/RX6)

201(LP1/LP1)-6

WDM Side 2(IN2/OUT2)

LQG

1(IN1/OUT1)

ODU1

OTU1


Another board

Another board: LQG or LQM2. The figure uses the LQM2 board in AP8 mode as an example.

l

Inter-board cross-connection – The GE optical signals on the client side of the LQG board are cross-connected to the WDM-side ports 201 of LQM2 board or another LQG board. For details, see (1) in Figure 6-28.

l

Intra-board cross-connection – The client-side GE optical signals of the LQG board are cross-connected to the WDMside ports 201 of this board. For details, see (2) in Figure 6-28.

Board Configuration This section describes the display of ports on the board and provides the configuration rules for this board on the NMS.

Cross-Connect Ports The LQG board supports inter-board cross-connections and intra-board cross-connections of GE optical signals. This board implements service cross-connections through its cross-connect module. Figure 6-29 shows the cross-connections implemented on the LQG board.

Issue 01 (2011-10-20)


179



Figure 6-29 Example of cross-connections of the LQG board 3(TX1/RX1)

2

4(TX2/RX2) Client Side

1(IN1/OUT1)

201(LP/LP)-2 OTU5G

ODU5G

5(TX3/RX3) 6(TX4/RX4)

201(LP/LP)-1

201(LP/LP)-3 1 201(LP/LP)-4

3(TX1/RX1)

201(LP1/LP1)-1

4(TX2/RX2)

201(LP1/LP1)-2

7(TX5/RX5)

201(LP1/LP1)-5

8(TX6/RX6)

201(LP1/LP1)-6

Client Side


LQG

1(IN1/OUT1)

ODU1

OTU1


Another board

Another board: LQG or LQM2. The figure uses the LQM2 board in AP8 mode as an example.

l

Inter-board cross-connection – The GE optical signals on the client side of the LQG board are cross-connected to the WDM-side ports 201 of LQM2 board or another LQG board. For details, see Figure 6-29.

l

1

in

Intra-board cross-connection – The client-side GE optical signals of the LQG board are cross-connected to the WDMside ports 201 of this board. For details, see

2

in Figure 6-29.


Set board parameters. l Set the service types at ports 3 to 6 (that is, TX1/RX1 to TX4/RX4) on the client side. The service types are set at the IN1/OUT1 port to GE or GE (GFP-T). For details on the configurations and other parameters, see 5.10.8 LQG Parameters.

2.

Configure cross-connections. The Level should be set the same value as Service Type of the WDM-side ports. l Configure inter-board cross-connections. For details, see

Issue 01 (2011-10-20)


1

in Figure 6-29.

180



Table 6-15 LQG inter-board cross-connections L e v e l

Source board (LQG)

Sink board (LQM2 in AP8 mode)

Sink board (LQM2 in 2LQM mode)

Sink board (another LQG)

Source Optical Port

Sou rce Opt ical Cha nne l

Sink Optical Port

Sink Optic al Chan nel

Sink Optic al Port


Sink Optic al Port


G E

3(TX1/ RX1)

1

201(LP1/ LP1)

1, 2, 5, 201 6 (LP1/ LP1)

1, 2

201 (LP1/ LP1)

1 to 4

1, 2

201 (LP1/ LP1)

1 to 4

4(TX2/ RX2)

202 (LP2/ LP2)

5(TX3/ RX3) 6(TX4/ RX4) G E ( G F P T )

3(TX1/ RX1)

1

201(LP1/ LP1)

4(TX2/ RX2)

1, 2, 5, 201 6 (LP1/ LP1) 202 (LP2/ LP2)

5(TX3/ RX3) 6(TX4/ RX4)

l Configure intra-board cross-connections. For details, see

2

in Figure 6-29.

Table 6-16 LQG intra-board cross-connections Level

GE

Source board (LQG)

Sink board (LQG)

Source Optical Port


Sink Optical Port


3(TX1/RX1)

1

201(LP1/LP1)

1 to 4

4(TX2/RX2) 5(TX3/RX3) 6(TX4/RX4)

Issue 01 (2011-10-20)


181


Level

GE (GFPT)


Source board (LQG)

Sink board (LQG)

Source Optical Port


Sink Optical Port


3(TX1/RX1)

1

201(LP1/LP1)

1 to 4

4(TX2/RX2) 5(TX3/RX3) 6(TX4/RX4)

For details on the configurations, see 6.3.1 Configuring Cross-Connection Service.

6.2.4 LQM2 Service Configuration Physical and Logical Ports This section describes the display of ports on the board and provides the configuration rules for this board on the NMS.

Display of Ports Table 6-17 lists the sequence number displayed on the U2000 of the port on the LQM2 board front panel. Table 6-17 Display of the LQM2 ports

Issue 01 (2011-10-20)

Ports on the Front Panel


IN1/OUT1

1

IN2/OUT2

2

TX1/RX1

3

TX2/RX2

4

TX3/RX3

5

TX4/RX4

6

TX5/RX5

7

TX6/RX6

8

TX7/RX7

9

TX8/RX8

10


182



NOTE

l An EVOA optical module can be installed at any client-side port on the TNF2LQM2 board. When an EVOA module is installed at a client-side port, the attenuation of the EVOA optical module is configured at the client-side port, and the related alarms are also reported at the client-side port. l An optical port number displayed on the U2000 indicates a pair of actual optical ports, one for transmitting signals, and the other for receiving signals.

Port model of TNF1LQM2 board l

AP8 mode Figure 6-30 shows the port model of the LQM2 board in AP8 mode.

Figure 6-30 Port model of the LQM2 board (AP8 mode)

5(RX3/TX3)

201(LP1/LP1)-3

6(RX4/TX4)

201(LP1/LP1)-4

3(RX1/TX1)

201(LP1/LP1)-1

4(RX2/TX2)

201(LP1/LP1)-2

7(RX5/TX5)

201(LP1/LP1)-5

8(RX6/TX6)

201(LP1/LP1)-6

9(RX7/TX7)

201(LP1/LP1)-7

10(RX8/TX8)

201(LP1/LP1)-8

1(IN1/OUT1) ODU1

OTU1 2(IN2/OUT2)


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-10 (RX1/TX1 to RX8/TX8). – Alarms and performance events related to OTN electrical-layer overheads are reported on channels 1 and 2 of logical port 201. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2). l

2LQM mode Figure 6-31 shows the port model of the LQM2 board in 2LQM mode.

Issue 01 (2011-10-20)


183



Figure 6-31 Port model of the LQM2 board (2LQM mode)

5(RX3/TX3)

201(LP1/LP1)-3

6(RX4/TX4)

201(LP1/LP1)-4

3(RX1/TX1)

201(LP1/LP1)-1

4(RX2/TX2)

201(LP1/LP1)-2

7(RX5/TX5)

202(LP2/LP2)-1

8(RX6/TX6)

202(LP2/LP2)-2

9(RX7/TX7)

202(LP2/LP2)-3

10(RX8/TX8)

202(LP2/LP2)-4

ODU1

OTU1

1(IN1/OUT1)

ODU1

OTU1

2(IN2/OUT2)


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-10 (RX1/TX1 to RX8/TX8). – Alarms and performance events related to OTN electrical-layer overheads are reported on channel 1 of logical ports 201 and 202. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2).

Port model of TNF2LQM2 board The TNF2LQM2 board can work in four different modes: 1 x AP8 ODU1 mode, 2 x AP4 ODU1 mode, 2 x AP2 ODU0 mode, 2 x AP3 ODU1 mode. l

1 x AP8 ODU1 mode Figure 6-32 shows the port model of the TNF2LQM2 board in 1 x AP8 ODU1 mode.

Issue 01 (2011-10-20)


184



Figure 6-32 Port model of the TNF2LQM2 board (1 x AP8 ODU1 mode) 5(RX3/TX3)

201(LP1/LP1)-3

6(RX4/TX4)

201(LP1/LP1)-4

3(RX1/TX1)

201(LP1/LP1)-1

4(RX2/TX2)

201(LP1/LP1)-2

7(RX5/TX5)

201(LP1/LP1)-5

8(RX6/TX6)

201(LP1/LP1)-6

9(RX7/TX7)

201(LP1/LP1)-7

10(RX8/TX8)

201(LP1/LP1)-8

201

1 ODU1

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

2

ODU1

ODU1


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-10 (RX1/TX1 to RX8/TX8). – Alarms, performance events, and configurations related to OTU1/ODU1 overheads are reported on channel 1 of optical ports 1 and 2. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 (IN1/OUT1) and 2 (IN2/OUT2). – The 201 port supports ODU1 convergence mode and ODU1 non-convergence mode. It works in ODU1 convergence mode by default. l


Issue 01 (2011-10-20)


185



Figure 6-33 Port model of the TNF2LQM2 board (2 x AP4 ODU1 mode) 5(RX3/TX3)

201(LP1/LP1)-3

6(RX4/TX4)

201(LP1/LP1)-4

3(RX1/TX1)

201(LP1/LP1)-1

4(RX2/TX2)

201(LP1/LP1)-2

7(RX5/TX5)

202(LP2/LP2)-1

8(RX6/TX6)

202(LP2/LP2)-2

9(RX7/TX7)

202(LP2/LP2)-3

10(RX8/TX8)

202(LP2/LP2)-4

201

ODU1

1

ODU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

2

202

ODU1

OTU1

ODU1


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-10 (RX1/TX1 to RX8/TX8). – Alarms, performance events, and configurations related to OTU1/ODU1 overheads are reported on channel 1 of optical ports 1 and 2. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2). – The 201 and 202 ports support ODU1 convergence mode and ODU1 non-convergence mode. They work in ODU1 convergence mode by default. l


Issue 01 (2011-10-20)


186



Figure 6-34 Port model of the TNF2LQM2 board (2 x AP2 ODU0 mode) 1 3(RX1/TX1)

201(LP1/LP1)-1

ODU0( 4353) ODU1

201(LP1/LP1)-2

OTU1

1(IN1/OUT1)

ODU0( 4354)

2 ODU0( 4353) ODU1 4(RX2/TX2)

202(LP2/LP2)-1 202(LP2/LP2)-2

7(RX5/TX5)

203(LP3/LP3)-1

OTU1

ODU0( 4354)

2(IN2/OUT2)

9 ODU0( 4353)

203(LP3/LP3)-2

ODU1

OTU1

9(TX7/RX7)

OTU1

10(TX8/RX8)

ODU0( 4354)

10 ODU0( 4353) ODU1 8(RX6/TX6)

204(LP4/LP4)-1

ODU0( 4354)

204(LP4/LP4)-2

: Active service cross-connection, which needs to be configured on the NMS : Standby service cross-connection, which needs to be configured on the NMS : Client-side services : WDM-side services

– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3(RX1/TX1), 4(RX2/TX2), 7(RX5/TX5), 8(RX6/ TX6). – Alarms, performance events, and configurations related to ODU0 signal overheads are reported on channels 4353 and 4354 of WDM-side optical ports. – Alarms, performance events, and configurations related to ODU1/OTU1 signal overheads are reported on channel 1 of optical ports 1, 2, 9, and 10. – Alarms, performance events, and configurations related to WDM-side optical modules and the optical layer are reported on channel 1 of WDM-side optical ports 1, 2, 9, and 10. – Cross-connections from ports 3(RX1/TX1), 4(RX2/TX2), 7(RX5/TX5), 8(RX6/TX6) to channel 1 of ports 201–204 need to be configured. When the board is interconnected with a TN52TOM board for NG WDM products, you can configure the crossconnections from optical ports 3(RX1/TX1), 4(RX2/TX2), 7(RX5/TX5), 8(RX6/TX6) to channel 2 of ports 201–204 to ensure channel ID consistency for the TN52TOM board. Issue 01 (2011-10-20)


187


l



Figure 6-35 Port model of the TNF2LQM2 board (2 x AP3 ODU1 mode) 1 ODU1

3(RX1/TX1)

4(RX2/TX2)

201 (LP1/LP1)

ODU1

5(RX3/TX3)

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

OTU1

9(TX7/RX7)

OTU1

10(TX8/RX8)

2 ODU1

9 ODU1

6(RX4/TX4) 7(RX5/TX5)

202 (LP2/LP2)

ODU1

8(RX6/TX6)

10 ODU1


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-8 (RX1/TX1 to RX6/TX6). – Alarms, performance events, and configurations related to OTU1/ODU1 signal overheads are reported on channel 1 of optical ports 1, 2, 9, and 10. – Alarms, performance events, and configurations related to WDM-side optical modules and the optical layer are reported on channel 1 of WDM-side optical ports 1, 2, 9, and 10. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 (IN1/ OUT1), 2 (IN2/OUT2), 9 (IN9/OUT9), 10 (IN10/OUT10). – The 201 and 202 ports support ODU1 convergence mode and ODU1 non-convergence mode. They work in ODU1 convergence mode by default.

Issue 01 (2011-10-20)


188




Service Package The TNF1LQM2 board supports two types of service packages, as shown in Table 6-18. Table 6-18 Configuration of the service packages of the TNF1LQM2 board Service Package Mode

Port

Accessed Service

Configuration Method

GE service package

3 (TX1/RX1)

GE

4 (TX2/RX2)

GE

5 (TX3/RX3)

Null

See 6.3.2 Configuring Services in Service Package Mode.

6 (TX4/RX4)

Null

7 (TX5/RX5)

Null

8 (TX6/RX6)

Null

9 (TX7/RX7)

Null

10 (TX8/RX8)

Null

3 (TX1/RX1)

GE

4 (TX2/RX2)

GE

5 (TX3/RX3)

STM-1

6 (TX4/RX4)

STM-1

7 (TX5/RX5)

Null

8 (TX6/RX6)

Null

9 (TX7/RX7)

Null

10 (TX8/RX8)

Null

GE/SDH(STM-1) service package

NOTE

Only TNF1LQM2 board supports service packages.

Cross-Connect Ports The LQM2 board supports inter-board cross-connections and intra-board cross-connections of optical services with rate lower than 1.25 Gbit/s. This board implements service crossconnections through its cross-connect module. Figure 6-36 and Figure 6-37 show the crossconnections implemented on the LQM2 board. Issue 01 (2011-10-20)


189



Figure 6-36 Example of cross-connections of the LQM2 board (AP8 mode of TNF1LQM2, 1 x AP8 ODU1 mode of TNF2LQM2) 3(TX1/RX1)

1

201(LP1/LP1)-1 201(LP1/LP1)-2

7(TX5/RX5)

201(LP1/LP1)-5

2(IN2/OUT2)

201(LP1/LP1)-6

LQM2

Client Side 2 8(TX6/RX6)

Client Side

1(IN1/OUT1)

4(TX2/RX2)

3

3(TX1/RX1)

201(LP/LP)-1

4(TX2/RX2)

201(LP/LP)-2

5(TX3/RX3)

201(LP/LP)-3

6(TX4/RX4)

201(LP/LP)-4

ODU1

WDM Side

OTU1

251(LP1/LP1)-1

1(IN1/OUT1)

252(LP2/LP2)-2

2(IN2/OUT2)

WDM Side

Another board

Another board: LQG, LQM2, or TSP. The 201 ports uses the LQG board as an example and the 251 ports uses the TSP board as an example.

Figure 6-37 Example of cross-connections of the LQM2 board (2LQM mode of TNF1LQM2, 2 x AP4 ODU1 mode of TNF2LQM2) 3(TX1/RX1)

1

ODU1

4(TX2/RX2)

201(LP1/LP1)-2

7(TX5/RX5)

202(LP2/LP2)-1

Client Side 2 8(TX6/RX6)

Client Side

201(LP1/LP1)-1

3

OTU1

1(IN1/OUT1)


ODU1

OTU1

202(LP2/LP2)-2

3(TX1/RX1)

201(LP/LP)-1

4(TX2/RX2)

201(LP/LP)-2

5(TX3/RX3)

201(LP/LP)-3

6(TX4/RX4)

201(LP/LP)-4

LQM2

251(LP1/LP1)-1

1(IN1/OUT1)

252(LP2/LP2)-1

2(IN2/OUT2)

WDM Side

Another board

Another board: LQG, LQM2, or TSP. The 201 ports uses the LQG board as an example and the 251 ports uses the TSP board as an example.

l

Intra-board cross-connection – The client-side optical services with rate lower than 1.25 Gbit/s are cross-connected to the WDM-side ports 201 of the LQM2 board. For details, see Figure 6-37.

Issue 01 (2011-10-20)


1

in Figure 6-36 and

190


l


Inter-board cross-connection – The GE signals on the client side of the LQM2 board are cross-connected to the WDMside ports 201 of the LQG board, or the optical services with rate lower than 1.25 Gbit/ s on the client side of the LQM2 board are cross-connected to the WDM-side ports 201 of another LQM2 board. For details, see

2

in Figure 6-36 and Figure 6-37.

– The STM-4/STM-1 signals on the WDM-side ports 201 or 202 of the LQM2 board are cross-connected to the WDM-side ports 251 and 252 of the TSP board. For details, see 3

in Figure 6-36 and Figure 6-37.

NOTE

Only the client-side optical ports 3 (RX1/TX1), 4 (RX2/TX2), 7 (RX5/TX5), and 8 (RX6/TX6) on the LQM2 board support the cross-connection function.

Configuration Procedure of TNF1LQM2 1.

Set board parameters. l In the NE Explorer, select the LQM2 board and then choose Configuration > WDM interface from the Function Tree. l select By Board/Port(Channel) and choose Board from the drop-down list, and select the corresponding mode in Board Mode as required. l Choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.10 LQM2 Parameters.

2.

Configure cross-connections. Set Level to Any and Service Type to the same value as that of the WDM-side ports. l Configure intra-board cross-connections. For details, see 6-37.

1

in Figure 6-36 and Figure

Table 6-19 LQM2 intra-board cross-connections (AP8 mode of TNF1LQM2, 1 x AP8 ODU1 mode of TNF2LQM2)

Issue 01 (2011-10-20)

Lev el

Ser vice Typ e

Source board (LQM2)

Sink board (LQM2)

Source Optical Port


Sink Optical Port


Any

ST M-1 , ST M-4 ... (the serv ice less than 1.25 Gbit /s)

3(TX1/ RX1)

1

201(LP1/LP1)

1, 2, 5, 6

4(TX2/ RX2) 7(RX5/ TX5) 8(RX6/ TX6)


191



Table 6-20 LQM2 intra-board cross-connections (2LQM mode of TNF1LQM2, 2 x AP4 ODU1 mode of TNF2LQM2) Lev el

Ser vice Typ e

Source board (LQM2)

Sink board (LQM2)

Source Optical Port


Sink Optical Port


Any

ST M-1 , ST M-4 ... (the serv ice less than 1.25 Gbit /s)

3(TX1/ RX1)

1

201(LP1/LP1)

1, 2

202(LP2/LP2)

4(TX2/ RX2) 7(RX5/ TX5) 8(RX6/ TX6)

l Configure inter-board cross-connections. For details, see Figure 6-37.

2

and

3

in Figure 6-36 and

Table 6-21 Inter-board cross-connections between LQM2 and LQG Lev el

Service Type

Source board (LQM2)

Sink board (LQG)

Source Optical Port


Sink Optical Port


Any

GE

3(TX1/ RX1)

1

201(LP1/LP1)

1 to 4

4(TX2/ RX2) 7(RX5/ TX5) 8(RX6/ TX6)

Issue 01 (2011-10-20)


192



Table 6-22 Inter-board cross-connections between LQM2 and another LQM2 L ev el

A ny

Ser vice Typ e

Source board (LQM2)

Sink board (another LQM2 in AP8 mode)

Sink board (another LQM2 in 2LQM mode)

Sourc e Optic al Port

Sourc e Optic al Chan nel

Sink Optical Port

Sink Opti cal Cha nnel

Sink Optical Port


ST M-1, ST M-4 ... (the servi ce less than 1.25 Gbit /s)

3 (TX1/ RX1)

1

201(LP1/LP1)

1, 2, 5, 6

201(LP1/ LP1)

1, 2

202(LP2/ LP2)

4 (TX2/ RX2) 7 (RX5/ TX5) 8 (RX6/ TX6)

Table 6-23 Inter-board cross-connections between LQM2 and TSP Lev el

Service Type

Source board (LQM2)

Sink board (TSP)

Source Optical Port


Sink Optical Port


Any

STM-1, STM-4

AP8 mode: 201(LP1/ LP1)

AP8 mode: 1, 2, 5, 6

251(LP1/LP1)

1

2LQM mode: 201 (LP1/LP1), 202(LP2/ LP2)

252(LP2/LP2)

2LQM mode: 1, 2


Configuration Procedure of TNF2LQM2 1.

Issue 01 (2011-10-20)

Set board working mode.


193



l In the NE Explorer, select the target TNF2LQM2 board. In the navigation tree, choose Configuration > Working Mode. Then select Board Working Mode as required. l Select Port Working Mode as required. NOTE

You need to set Port Working Mode only when Board Working Mode is set to 1*AP8 ODU1 mode, 2*AP4 ODU1 mode or 2*AP3 ODU1 mode.

2.

Set board parameters. l In the NE Explorer, select the F2LQM2 board. In the navigation tree, choose Configuration > WDM interface. l Choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.10 LQM2 Parameters.

3.

Configure intra-board and inter-board cross-connections. See 2.

4.

Configure intra-board pass-through services. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click New. In the Create Cross-Connection Service window that is displayed, set related parameters. The detailed configuration is as follows: l 1*AP8 ODU1 mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. l 2*AP4 ODU1 mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. l 2*AP2 ODU0 mode Table 6-24 Configuration for intra-board pass-through services on the TNF2LQM2 board Level

Source Board (LQM2)

Sink Board (LQM2)

Source Optical Port


Sink Optical Port


GE (GFP_ T), or Any

3(TX1/RX1)

1

201(LP1/LP1)

1b

GE (GFP_ T), or Any

4(TX2/RX2)

1

202(LP2/LP2)

1b

a

Issue 01 (2011-10-20)


194


Level


Source Board (LQM2)

Sink Board (LQM2)

Source Optical Port


Sink Optical Port


GE (GFP_ T), or Any

7(TX5/RX5)

1

203(LP3/LP3)

1b

GE (GFP_ T), or Any

8(TX6/RX6)

1

204(LP4/LP4)

1b

a

a: When Level is set to ANY, you need to set Service Type. The Service Type setting must be the same as the service type specified in the WDM Interface window. b: When the TNF2LQM board is interconnected with the TN52TOM board intended for NG WDM products, set Sink Optical Channel as optical channel 2 for the TNF2LQM board so that services are over the same channel between the two boards.

l 2*AP3 ODU1 mode Table 6-25 Configuration for intra-board pass-through services on the TNF2LQM2 board Level

Source Board (LQM2)

Sink Board (LQM2)

Source Optical Port


Sink Optical Port


GE (GFP_ T), or Any

3(TX1/RX1), 4 (TX2/RX2)

1

201(LP1/LP1)

1b

GE (GFP_ T), or Any

7(TX5/RX5), 8 (TX6/RX6)

1

202(LP2/LP2)

1b

a

a: When Level is set to ANY, you need to set Service Type. The Service Type setting must be the same as the service type specified in the WDM Interface window.

5.

Configure ODUk SNCP protection. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click Create SNCP Service. In the Create SNCP Service window that is displayed, set related parameters.

Issue 01 (2011-10-20)


195



Table 6-26 Configuration for SNCP protection on the TNF2LQM2 board Item

1*AP8 ODU1 mode

2*AP2 ODU0 mode

2*AP3 ODU1 mode

Protection Type

ODUK SNCP

ODUK SNCP

ODUK SNCP

Service Type

ODU1

ODU0

ODU1

Worki ng Servic e

Source Optical Port

1(IN1/OUT1)

1(IN1/OUT1)

1(IN1/OUT1)

9(RX7/TX7)

9(RX7/TX7)


-

-

-

Sink Optical Port

201(LP1/ LP1)

201(LP1/LP1), 202 (LP2/LP2)

201(LP1/LP1)


1

1

1

Source Optical Port

2(IN2/OUT2)

2(IN2/OUT2)

2(IN2/OUT2)

10(RX8/TX8)

10(RX8/TX8)


-

-

-

Protec tion Servic e

202(LP2/LP2)

203(LP3/LP3), 204 (LP4/LP4)


NOTE

When the board works in 2*AP4 ODU1 mode, the ODUk SNCP is not supported.

6.2.5 TSP Service Configuration Physical and Logical Ports This section describes the display of ports on the TSP board and provides the configuration rules for this board on the U2000.

Issue 01 (2011-10-20)


196



Display of Ports Table 6-27 lists the sequence number displayed on the U2000 of the port on the TSP board front panel. Table 6-27 Display of the TSP ports Ports on the Front Panel


IN1/OUT1

1

IN2/OUT2

2

TX1/RX1

3

TX2/RX2

4

E1/T1 (1)

5

E1/T1 (2)

6

...

...

E1/T1 (21)

25

Port model Figure 6-38 shows the port model of the TSP board. Figure 6-38 Port model of the TSP board 3(RX1/TX1) 4(RX2/TX2) 201(LP201/LP201)

251(LP1/LP1)-1

5(E1/T1-1) 1(IN1/OUT1)-1 6(E1/T1-2) 2(IN2/OUT2)-1

7(E1/T1-3) 8(E1/T1-4)

202(LP202/LP202)

252(LP2/LP2)-1

9(E1/T1-5)

…… 25(E1/T1-21)

: Client-side services : WDM-side services : Service cross-connection, which needs to be configured on the NMS : Virtual channel, which does not need to be configured on the NMS : SDH timeslot mapping, which needs to be configured on the NMS

Issue 01 (2011-10-20)


197



l

Alarms and performance events related to client-side signal overheads are reported through channel 1 of client-side optical ports 3 (RX1/TX1) and 4 (RX2/TX2).

l

Alarms and performance events related to tributary-side signal overheads are reported through tributary-side electrical ports 5 (E1/T1-1) to 25 (E1/T1-21).

l

If the types of services at optical ports 251 (LP1/LP1) and 252 (LP2/LP2) are set to STM-4, alarms and performance events related to SDH electrical-layer overheads are reported through channels 1–4 of logical ports 201 and 202 in the board model. If the types of services at optical ports 251 (LP1/LP1) and 252 (LP2/LP2) are set to STM-1, alarms and performance events related to SDH electrical-layer overheads are reported through channel 1 of logical ports 201 and 202 in the board model.

l

Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported through channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/OUT2).

Board Configuration This section describes the display of ports on the TSP board and provides the configuration rules for this board on the U2000.

Cross-Connections The TSP board supports inter-board cross-connections of STM-4/STM-1 signals and intra-board cross-connections of VC-4/VC-12 signals. This board implements service cross-connections through its cross-connect module. Figure 6-39 shows the cross-connections implemented on the TSP board. Figure 6-39 Example of cross-connections on the TSP board 5 3(TX1/RX1)

Client Side

6 4(TX2/RX2)

251(LP1/LP1)

201(LP201/LP201)

2

1(IN1/OUT1)

WDM Side

5(E1/T1)

202(LP202/LP202)

6(E1/T1) 7(E1/T1)

252(LP2/LP2)

3

4

2(IN2/OUT2)

Tributary Side 1

TSP

25(E1/T1)

3(TX1/RX1)

201(LP1/LP1)-1

4(TX2/RX2)

201(LP1/LP1)-2

Client Side

l Issue 01 (2011-10-20)

7(TX5/RX5)

201(LP1/LP1)-5

8(TX6/RX6)

201(LP1/LP1)-6

1(IN1/OUT1)

ODU1

WDM Side

OTU1 2(IN2/OUT2)

LQM2

Inter-board cross-connection Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

198



– The STM-4/STM-1 signals on the WDM side of the TSP board are cross-connected to the cross-connect ports on the client side of the LQM2 board. For details, see Figure 6-39. l

1

in

Intra-board cross-connection – The tributary-side VC-12 signals are cross-connected to the client side of the TSP board. For details, see

2

in Figure 6-39.

– The tributary-side VC-12 signals are cross-connected to the WDM side of the TSP board. For details, see

3

and

4

in Figure 6-39.

– The client-side VC4/VC-12 signals are cross-connected to the WDM side of the TSP board. For details, see

5

and

6

in Figure 6-39.

NOTE

In addition, the TSP board can pass through services without using its cross-connect module. For example, the services received from optical port 3 (TX1/RX1) can be directly transmitted by optical port 4 (TX2/ RX2); the services received from optical port 1 (IN1/OUT1) can be directly transmitted by optical port 2 (IN2/OUT2).


Set board parameters. l Set the types of the services at the 251/252 (LP1/LP2)-1 port on the WDM side to STM-1 or STM-4. The settings of the service types at ports 251 (LP1/LP1)-1 and 252 (LP2/ LP2)-1 take effect simultaneously and the service types are the same. l Set the service mode to E1 or T1 for PDH ports 5 (E1/T1-1) to 25 (E1/T1-21). Note that the service modes at the ports must be the same. For details on the configurations and other parameters, see 5.10.16 TSP Parameters.

2.

Configure intra-board SDH timeslot mapping relationships. l Configure timeslot mapping from the tributary side to the client side. For details, see 2

in Figure 6-39.

Table 6-28 Timeslot mapping relationship from the tributary side to the client side of the TSP board Lev el

VC12

Issue 01 (2011-10-20)

Source board (TSP)

Sink board (TSP)

Source Port

Source Timeslot Range

Sink Port

Sink Timeslot Range

5 to 25 (That is, E1/ T1-1 to E1/ T1-21. When configuring the ports, you must select TSP on the NMS.)

-

3(RX1/TX1)

1 to 63

4(RX2/TX2)


199



l Configure timeslot mapping from the tributary side to the WDM side. For details, see 3

in Figure 6-39.

Table 6-29 Timeslot mapping relationship from the tributary side to the WDM side of the TSP board Lev el

Ser vice Typ e of WD M por ts

Source board (TSP)

Sink board (TSP)

Source Port


Sink Port

Sink Timeslot Range

VC12

ST M-1

5 to 25 (That is, E1/T1-1 to E1/T1-21. When configurin g the ports, you must select TSP on the NMS.)

-

201(LP201/LP201)

1 to 63

VC12

ST M-4

5 to 25 (That is, E1/T1-1 to E1/T1-21. When configurin g the ports, you must select TSP on the NMS.)

-

202(LP202/LP202)

201(LP201/LP201) 202(LP202/LP202)

1 to 4 x 63: 1 to 4 VC4 channels with each VC4 channel containin g 1 to 63 VC12 channels.

l Configure timeslot mapping from the client side to the WDM side. For details, see 5

Issue 01 (2011-10-20)

in Figure 6-39.


200



Table 6-30 Timeslot mapping relationship from the client side to the WDM side of the TSP board Lev el

Ser vice Typ e of WD M por ts

Source board (TSP)

Sink board (TSP)

Source Port


Sink Port

Sink Timeslot Range

VC4

ST M-4

3(RX1/ TX1)

1

201(LP201/LP201)

1 to 4

202(LP202/LP202)

4(RX2/ TX2) VC4

ST M-1

3(RX1/ TX1)

1

201(LP201/LP201)

1

202(LP202/LP202)

4(RX2/ TX2) VC12

ST M-4

3(RX1/ TX1)

1 to 63

201(LP201/LP201)

1 to 4 x 63: 1 to 4 VC4 channels with each VC4 channel containing 1 to 63 VC12 channels.

202(LP202/LP202)

4(RX2/ TX2)

VC12

ST M-1

3(RX1/ TX1)

1 to 63

201(LP201/LP201)

1 to 63

202(LP202/LP202)

4(RX2/ TX2)

NOTE

Set Level to VC12 only when the STM-1/STM-4 signals received at ports 3 (RX1/TX1) and 4 (RX2/ TX2) are encapsulated in VC12 channels; otherwise, services will be unavailable.

For details, see 6.6 Configuring SDH Service. 3.

Configure cross-connections. Set Level to Any and Service Type to the same value as that of the WDM ports. l Configure intra-board cross-connections. For details, see

Issue 01 (2011-10-20)


4

and

6

in Figure 6-39.

201



Table 6-31 TSP intra-board cross-connections Lev el

Service Type

Source board (TSP)

Sink board (TSP)

Source Optical Port

Source Optical Channe l

Sink Optical Port


Any

STM-1

251(LP1/ LP1)

1

1(IN1/OUT1)

1

2(IN2/OUT2)

252(LP2/ LP2) Any

STM-4

251(LP1/ LP1)

1

1(IN1/OUT1)

1

2(IN2/OUT2)

252(LP2/ LP2)

l Configure inter-board cross-connections. For details, see

1

in Figure 6-39.

Table 6-32 TSP inter-board cross-connections L e v el

S er vi ce T y p e

Source board (TSP)

Sink board (LQM2 in AP8 mode)

Sink board (LQM2 in 2LQM mode)

Source Optical Port

Sourc e Optic al Chan nel

Sink Optical Port


Sink Optical Port


A ny

S T M -1

251 (LP1/ LP1)

1

201(LP1/ LP1)

1, 2, 5, 6

201(LP1/ LP1)

1, 2

S T M -4

251 (LP1/ LP1)

A ny

202(LP2/ LP2)

252 (LP2/ LP2) 1

201(LP1/ LP1)

1, 2, 5, 6

252 (LP2/ LP2)

201(LP1/ LP1)

1, 2

202(LP2/ LP2)


6.2.6 LQM Service Configuration Issue 01 (2011-10-20)


202



Physical and Logical Ports This section describes the display of ports on the board and provides the configuration rules for this board on the NMS.

Display of Ports Table 6-33 lists the sequence number displayed in an NMS system of the ports on the LQM board front panel. Table 6-33 Display of the LQM ports Ports on the Front Panel


IN1/OUT1

1

IN2/OUT2

2

TX1/RX1

3

TX2/RX2

4

TX3/RX3

5

TX4/RX4

6

VO1/VI1

7

VO2/VI2

8

NOTE


Port model of TNF1LQM Figure 6-40 shows the port model of the TNF1LQM board. Figure 6-40 Port model of the TNF1LQM board 3(RX1/TX1)

201(LP1/LP1)-1

4(RX2/TX2)

201(LP1/LP1)-2

5(RX3/TX3)

201(LP1/LP1)-3

6(RX4/TX4)

201(LP1/LP1)-4

201 1(IN1/OUT1) ODU1

OTU1 2(IN2/OUT2)


Issue 01 (2011-10-20)


203



l

Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-6 (RX1/TX1 to RX4/TX4).

l

Alarms and performance events related to OTN electrical-layer overheads are reported on channels 1 and 2 of logical port 201.

l

Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/OUT1 and IN2/ OUT2).

l

Cross-connections are automatically generated and no configuration is required on the NMS.

Port model of TNF2LQM The TNF2LQM board can work in three different modes: 1 x AP4 ODU1 mode, 1 x AP2 ODU0 mode, 1 x AP2 regeneration mode. l

1 x AP4 ODU1 mode Figure 6-41 shows the port model of the TNF2LQM board in 1 x AP4 ODU1 mode.

Figure 6-41 Port model of the TNF2LQM board (1 x AP4 ODU1 mode) 1 3(RX1/TX1) ODU1 4(RX2/TX2)

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

ODU1 2

201(LP1/LP1) 5(RX3/TX3) ODU1 6(RX4/TX4)


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3-6 (RX1/TX1 to RX4/TX4). – Alarms, performance events, and configurations related to OTU1/ODU1 overheads are reported on channel 1 of optical ports 1 and 2. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2). Issue 01 (2011-10-20)


204



– The 201 port supports ODU1 convergence mode and ODU1 non-convergence mode. It works in ODU1 convergence mode by default. – Supports intra-board 1+1 protection and ODUk (k = 1) SNCP protection. – After the board is powered on, the cross-connection from the 201 port to optical port 1 is configured by default. After intra-board 1+1 protection is configured, the system will automatically configure the cross-connection from the 201 port to optical port 2. l

1xAP2 ODU0 mode Figure 6-42 shows the port model of the TNF2LQM board in 1 x AP2 ODU0 mode.

Figure 6-42 Port model of the TNF2LQM board (1 x AP2 ODU0 mode) 1 3(RX1/TX1)

201(LP1/LP1)-1 201(LP1/LP1)-2

ODU0( 4353) ODU1

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

ODU0( 4354)

2 ODU0( 4353) ODU1 4(RX2/TX2)

202(LP2/LP2)-1 202(LP2/LP2)-2

ODU0( 4354)


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3 and 4 (RX1/TX1 and RX2/TX2). – Alarms, performance events, and configurations related to ODU0 signal overheads are reported on channels 4353 and 4354 of WDM-side optical ports 1 and 2. – Alarms, performance events, and configurations related to ODU1/OTU1 overheads are reported on channel 1 of optical ports 1 and 2. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2). – Supports intra-board 1+1 protection and ODUk (k = 0) SNCP protection. – Cross-connections from optical ports 3 (RX1/TX1) and 4 (RX2/TX2) to channel 1 of ports 201 and 202 need to be configured. When the board is interconnected with a TN52TOM board for NG WDM products, you can configure the cross-connections from optical ports 3 (RX1/TX1) and 4 (RX2/TX2) to channel 2 of optical ports 201 and 202 to ensure channel ID consistency for the TN52TOM board. l Issue 01 (2011-10-20)

1 x AP2 regeneration mode Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

205



Figure 6-43 shows the port model of the TNF2LQM board in 1 x AP2 regeneration mode. Figure 6-43 Port model of the TNF2LQM board (1 x AP2 regeneration mode) 1

3(RX1/TX1)

OTU1

ODU1

ODU1

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

2

4(RX2/TX2)

OTU1

ODU1

ODU1


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 3 and 4 (RX1/TX1 and RX2/TX2). – Alarms, performance events, and configurations related to client ODU1/OTU1 signal overheads are reported on channel 1 of optical ports 3 and 4 (RX1/TX1 and RX2/TX2). – Alarms, performance events, and configurations related to ODU1/OTU1 overheads are reported on channel 1 of optical ports 1 and 2. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 and 2 (IN1/ OUT1 and IN2/OUT2).


Service Package The TNF1LQM board supports two types of service packages for the GE/STM-1 service, as shown in Table 6-34. Table 6-34 Configuration for service packages of the TNF1LQM board

Issue 01 (2011-10-20)

Service Package Mode

Port

Accessed Service


GE service package

3(TX1/RX1)

GE

4(TX2/RX2)

GE

See 6.3.2 Configuring Services in Service Package Mode.


206


Service Package Mode

GE/SDH(STM-1) service package


Port

Accessed Service

5(TX3/RX3)

Null

6(TX4/RX4)

Null

3(TX1/RX1)

GE

4(TX2/RX2)

GE

5(TX3/RX3)

STM-1

6(TX4/RX4)

STM-1


NOTE

Only TNF1LQM board supports service packages.

Configuration Procedure of TNF1LQM 1.

Set board parameters. l In the NE Explorer, select the LQM board. In the navigation tree, choose Configuration > WDM interface. l Select By Board/Port(Channel) and choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.9 LQM Parameters.

Configuration Procedure of TNF2LQM 1.

Set board working mode. l In the NE Explorer, select the target TNF2LQM board. In the navigation tree, choose Configuration > Working Mode. Then select Board Working Mode as required. l Select Port Working Mode as required. NOTE

You need to set Port Working Mode only when Board Working Mode is set to 1*AP4 ODU1 mode.

2.

Set board parameters. l In the NE Explorer, select the F2LQM board. In the navigation tree, choose Configuration > WDM interface. l Choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.9 LQM Parameters.

3.

Configure intra-board pass-through services. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click New. In the Create Cross-Connection Service window that is displayed, set related parameters. The detailed configuration is as follows:

Issue 01 (2011-10-20)


207



l 1*AP4 ODU1 mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. l 1*AP2 ODU0 mode Table 6-35 Configuration for intra-board pass-through services on the TNF2LQM board Level

Source Board (LQM)

Sink Board (LQM)

Source Optical Port


Sink Optical Port


GE (GFP_ T), or Any

3(TX1/RX1)

1

201(LP1/LP1)

1b

GE (GFP_ T), or Any

4(TX2/RX2)

1

202(LP2/LP2)

1b

a

a: When Level is set to ANY, you need to set Service Type. The Service Type setting must be the same as the service type specified in the WDM Interface window. b: When the TNF2LQM board is interconnected with the TN52TOM board intended for NG WDM products, set Sink Optical Channel as optical channel 2 for the TNF2LQM board so that services are over the same channel between the two boards.

l 1*AP2 relay mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. 4.

Configure ODUk SNCP protection. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click Create SNCP Service. In the Create SNCP Service window that is displayed, set related parameters. Table 6-36 Configuration for SNCP protection on the TNF2LQM board

Issue 01 (2011-10-20)

Item

1*AP4 ODU1 mode

1*AP2 ODU0 mode

Protection Type

ODUK SNCP

ODUK SNCP

Service Type

ODU1

ODU0

Working Service

1(IN1/OUT1)

1(IN1/OUT1)

Source Optical Port


208


Item

Protection Service


1*AP4 ODU1 mode

1*AP2 ODU0 mode


-

-

Sink Optical Port

201(LP1/LP1)

201(LP1/LP1), 202(LP2/LP2)


1

1

Source Optical Port

2(IN2/OUT2)

2(IN2/OUT2)


-

-


6.2.7 LDGF2 Service Configuration Physical and Logical Ports This section describes the display of ports on the board.

Display of Ports Table 6-37 lists the sequence number displayed in an NMS system of the ports on the LDGF2 board front panel. Table 6-37 Display of the LDGF2 ports

Issue 01 (2011-10-20)

Ports on the Front Panel


IN1/OUT1

1

IN2/OUT2

2

IN3/OUT3

3

IN4/OUT4

4

TX1/RX1

5

TX2/RX2

6

TX3/RX3

7

TX4/RX4

8


209



NOTE


Port model of TNF1LDGF2 board Figure 6-44 Port model of the TNF1LDGF2 board

1(IN1/OUT1)

5(RX1/TX1) 201 (LP1/LP1)

ODU1

OTU1 2(IN2/OUT2)

6(RX2/TX2)

7(RX3/TX3)

3(IN3/OUT3) 202 (LP2/LP2)

ODU1

OTU1 4(IN4/OUT4)

8(RX4/TX4)


l

Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 5-8 (RX1/TX1 to RX4/TX4).

l

Alarms and performance events related to OTN electrical-layer overheads are reported on channels 1 and 2 of logical ports 201 and 202.

l

Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 (IN1/OUT1) to 4 (IN4/ OUT4).

l

Cross-connections are automatically generated and no configuration is required on the NMS.

Port model of TNF2LDGF2 board The TNF2LDGF2 board can work in two different modes: 2 x AP2 ODU0 mode, 2 x AP2 ODU1 mode. l

Issue 01 (2011-10-20)

2 x AP2 ODU0 mode


210



Figure 6-45 Port model of the TNF2LDGF2 board (2 x AP2 ODU0 mode) 1 5(RX1/TX1)

201(LP1/LP1)-1

ODU0( 4353) ODU1

201(LP1/LP1)-2

OTU1

1(IN1/OUT1)

OTU1

2(IN2/OUT2)

OTU1

3(IN3/OUT3)

OTU1

4(IN4/OUT4)

ODU0( 4354)

2 ODU0( 4353) ODU1 6(RX2/TX2)

202(LP2/LP2)-1

ODU0( 4354)

202(LP2/LP2)-2 7(RX3/TX3)

203(LP3/LP3)-1 203(LP3/LP3)-2

3 ODU0( 4353) ODU1 ODU0( 4354)

4 ODU0( 4353) ODU1 8(RX4/TX4)

204(LP4/LP4)-1

ODU0( 4354)

204(LP4/LP4)-2


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 5-8 (RX1/TX1 to RX4/TX4). – Alarms, performance events, and configurations related to ODU0 signal overheads are reported on channels 4353 and 4354 of WDM-side optical ports. – Alarms, performance events, and configurations related to ODU1/OTU1 signal overheads are reported on channel 1 of optical ports 1, 2, 3, and 4. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 (IN1/OUT1) to 4 (IN4/OUT4). – Supports intra-board 1+1 protection and ODUk (k = 0) SNCP protection. – Cross-connections from ports 5–8 (RX1/TX1–RX4/TX4) to channel 1 of ports 201– 204 need to be configured. When the board is interconnected with a TN52TOM board for NG WDM products, you can configure the cross-connections from optical ports 5– 8 (RX1/TX1–RX4/TX4) to channel 2 of ports 201–204 to ensure channel ID consistency for the TN52TOM board. Issue 01 (2011-10-20)


211


l


2 x AP2 ODU1 mode

Figure 6-46 Port model of the TNF2LDGF2 board (2 x AP2 ODU1 mode) 1

5(RX1/TX1) ODU1 201 (LP1/LP1)

ODU1

OTU1

1(IN1/OUT1)

2 ODU1

OTU1

2(IN2/OUT2)

OTU1

3(IN3/OUT3)

OTU1

4(IN4/OUT4)

6(RX2/TX2)

3

7(RX3/TX3) ODU1 202 (LP2/LP2)

ODU1

4 ODU1

8(RX4/TX4)


– Alarms and performance events related to client signal overheads are reported on channel 1 of client-side optical ports 5-8 (RX1/TX1 to RX4/TX4). – Alarms, performance events, and configurations related to OTU1/ODU1 signal overheads are reported on channel 1 of optical ports 1, 2, 3, and 4. – Alarms related to the WDM-side optical module and optical-layer alarms and performance events are reported on channel 1 of WDM-side optical ports 1 (IN1/OUT1) to 4 (IN4/OUT4). – Supports intra-board 1+1 protection and ODUk (k = 1) SNCP protection.

Board Configuration This section describes the display of ports on the board.

Configuration Procedure of TNF1LDGF2 1. Issue 01 (2011-10-20)

Set board parameters. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

212



l In the NE Explorer, select the LDGF2 board. In the navigation tree, choose Configuration > WDM interface. l Select By Board/Port(Channel) and choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.4 LDGF2 Parameters.

Configuration Procedure of TNF2LDGF2 1.

Set board parameters. l In the NE Explorer, select the LDGF2 board. In the navigation tree, choose Configuration > WDM interface. l Select By Board/Port(Channel) and choose Board from the drop-down list, and select the corresponding mode in Board Mode as required. l Choose Channel from the drop-down list, and set the service type for client-side ports. For details on the configurations and other parameters, see 5.10.4 LDGF2 Parameters.

2.

Configure intra-board pass-through services. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click New. In the Create Cross-Connection Service window that is displayed, set related parameters. The detailed configuration is as follows: l 2*AP2 ODU0 mode Table 6-38 Configuration for intra-board pass-through services on the TNF2LDGF2 board Source Board (LDGF2)

Sink Board (LDGF2)

Source Optical Port


Sink Optical Port


GE (TTTAGMP) , GE (GFP_ T)

5(TX1/RX1)

1

201(LP1/LP1)

1b


6(TX2/RX2)

1

202(LP2/LP2)

1b

Level a

Issue 01 (2011-10-20)


213



Source Board (LDGF2)

Sink Board (LDGF2)

Source Optical Port


Sink Optical Port



7(TX3/RX3)

1

203(LP3/LP3)

1b


8(TX4/RX4)

1

204(LP4/LP4)

1b

Level a

a: The Level setting must be the same as the service type specified in the WDM Interface window. b: When the TNF2LDGF2 board is interconnected with the TN52TOM board intended for NG WDM products, set Sink Optical Channel as optical channel 2 for the TNF2LDGF2 board so that services are over the same channel between the two boards. l 2*AP2 ODU1 mode In this mode, you do not need to configure intra-board pass-through or cross-connection services. 3.

Configure ODUk SNCP protection. l In the NE Explorer, select the target NE. In the navigation tree, choose Configuration > WDM Service Management. l Click Create SNCP Service. In the Create SNCP Service window that is displayed, set related parameters. Table 6-39 Configuration for SNCP protection on the TNF2LDGF2 board

Issue 01 (2011-10-20)

Item

2*AP2 ODU0 mode

2*AP2 ODU1 mode

Protection Type

ODUK SNCP

ODUK SNCP

Service Type

ODU0

ODU1

Working Service

Source Optical Port

1(IN1/OUT1)

1(IN1/OUT1)

3(IN3/OUT3)

3(IN3/OUT3)


-

-


214


Item Sink Optical Port


2*AP2 ODU0 mode

2*AP2 ODU1 mode

201(LP1/LP1), 202 (LP2/LP2)

201(LP1/LP1) 202(LP2/LP2)

203(LP3/LP3), 204 (LP4/LP4)

Protectio n Service


1

1

Source Optical Port

2(IN2/OUT2)

2(IN2/OUT2)

4(IN4/OUT4)

4(IN4/OUT4)


-

-


6.3 Configuring WDM Services After setting board parameters, you need to configure WDM service grooming for boards that support cross-connections based on WDM services and protection planning.

6.3.1 Configuring Cross-Connection Service Configuring cross-connections is mandatory for deploying services and also a method of grooming services. The TSP, LQG and LQM2 boards support configuration of crossconnections and the methods of configuring cross-connections on the two boards are the same. By default, a cross-connection created on the is a direct cross-connection.

Prerequisite You must have logged in to the NE. Service types must be set for WDM optical interfaces on the board.


Precautions

CAUTION When configuring a cross-connection, ensure that the WDM-side path numbers at the transmit and receive ends are consistent. Otherwise, the service cannot be available.

Issue 01 (2011-10-20)


215



CAUTION When the board that supports cross-connection carries electrical interface services, non-straightthrough cross-connections cannot be configured for the electrical interface services on the board. TIP

When configuring cross-connections for a service, you need to configure one cross-connection on the NE where this service is added and another cross-connection on the NE where this service is dropped. When you need to configure cross-connections for multiple services on a network, select either of the following methods to configure the cross-connections for all these services: l On a per-NE basis: Configure cross-connections on one NE and then on another NE. In this manner, configure cross-connections on all NEs on the network in turn. l On a per-service basis: Configure cross-connections for one service and then for another service. In this manner, configure cross-connections for all services in turn. NOTE

In the case of the TSP board, when configuring a cross-connection, set Level to Any. In addition, set the service type to STM-1 or STM-4 as required and select 251(LP1/LP1) or 252(LP2/LP2) as the LP optical port.


In the NE Explorer, select the NE and choose Configuration > Electrical CrossConnection Service Management from the Function Tree.

2.

Click the Electrical Cross-Connection Configuration tab. Click New and the Create Cross-Connection Service dialog box is displayed.

3.

Select corresponding values for Service Level and Service Type and set other parameters for the service.

4.

Click OK and the created cross-connection is displayed in the user interface.


In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree.

2.

Click the WDM Cross-Connection Configuration tab. Click New and the Create CrossConnection Service dialog box is displayed.

3.

Select corresponding values for Level and Service Type and set other parameters for the service.

4.

Click OK. A prompt appears telling you that the operation was successful.

5.

Click Close.



l


Issue 01 (2011-10-20)


216



6.3.2 Configuring Services in Service Package Mode The service package module enables you to configure services on an NE in a one-click manner. This configuration method is easier and quicker. The OptiX OSN 1800 supports two types of service packages: GE service package and GE/STM-1 integrated service package. The LQM, LQM2, and LWX2 boards support the function of configuring services in service package mode.

Prerequisite You must have logged in to the NE where the LQM, LQM2, or LWX2 board resides.


Background Information You can select the required service package during the deployment. Then, you can run the commands in the service package to configure services and query information the service package. You can run a command to manually apply a service package to an NE. In this manner, the services on all the service boards on this NE are configured automatically. In the process of applying a service package to an NE, the original configurations on the NE are deleted and the configuration commands are then executed. A service package actually contains a series of configuration commands. Some of these configuration commands are used for configuring crossconnections, and the other are used for configuring service types for optical interfaces. There is an exception that a service rate other than service type is configured for an optical port in the case of the LWX2 board. Table 6-40 lists the service configurations for the LQM board in service package mode. Table 6-40 Service configurations for the LQM board in service package mode Service Package Type

3(TX1/RX1)

4(TX2/RX2)

5(TX3/RX3)

6(TX4/RX4)

GE bypass

GE

GE

Null

Null

GE/STM1 hybrid

GE

GE

STM-1

STM-1

Table 6-41 lists the service configurations for the LQM2 board in service package mode. Table 6-41 Service configurations for the LQM2 board in service package mode

Issue 01 (2011-10-20)

Service Packag e Type

3(TX1/ RX1)

4(TX2/ RX2)

5(TX3/ RX3)

6(TX4/ RX4)

7(TX5/ RX5)

8(TX6/ RX6)

9(TX7/ RX7)

10 (TX8/ RX8)

GE bypass

GE

GE

Null

Null

Null

Null

Null

Null


217



Service Packag e Type

3(TX1/ RX1)

4(TX2/ RX2)

5(TX3/ RX3)

6(TX4/ RX4)

7(TX5/ RX5)

8(TX6/ RX6)

9(TX7/ RX7)

10 (TX8/ RX8)

GE/ STM1 hybrid

GE

GE

STM-1

STM-1

Null

Null

Null

Null

Table 6-42 lists the service configurations for the LWX2 board in service package mode. Table 6-42 Service configurations for the LWX2 board in service package mode Service Package Type

5(TX1/RX1)

6(TX2/RX2)

GE bypass

GE

GE

GE/STM1 hybrid

GE

GE

Precautions

CAUTION In the case of the LQM2 board, after the configuration commands in a service package are executed, a direct cross-connection between optical port 3 and optical port 4 is configured automatically. In the case of the LWX2 and LQM boards, the configuration commands in a service package cannot be used to create any cross-connection.

CAUTION Precautions for configuring services in service package mode l Service packages do not support expansion based on the existing services. If expansion is required, you need to delete the existing services before configuring services in service package mode. l In the process of applying a service package to an NE, the configurations on all boards on this NE are deleted and the service package is then implemented. l If the NE is reset in the process of configuring scripts, you need to restart the service package before you configure services.

Issue 01 (2011-10-20)


218



CAUTION In the case of the LQM2 board, take the following precautions before configuring services in service package mode: l After configuring services in service package mode, if one of optical interfaces 3 to 6 on the LQM2 board needs to access another type of service, you need to reconfigure the service type manually for this optical port. Otherwise, the service is unavailable. l If the current working mode of the LQM2 board is the 2LQM mode, the working mode of the board automatically changes to AP8 after service types are configured for the board in service package mode.


Apply the correct service package to an NE according to network service planning. (1) Select the NE in the NE Explorer and choose Configuration > Service Package from the Function Tree. (2) Click Query to view the existing service package types. (3) Select Package Type according to the service planning requirement and then click Start. Then, the Performing this operation will interrupt services? Continue? dialog box is displayed. Click OK. A dialog box is displayed, indicating that the operation is successful. Click OK.

2.

Optional: To view the cross-connections created after the service package is configured, select the NE in the NE Explorer and then choose Configuration > Electrical CrossConnection Service Management from the Function Tree; to view the attributes of an optical port on the board, select the board in the NE Explorer and then choose Configuration > WDM Interface from the Function Tree.


Apply the correct service package to an NE according to network service planning. (1) Select the NE in the NE Explorer and choose Configuration > Service Package from the Function Tree. (2) Click Query to view the existing service package types. (3) Select Package Type according to the service planning requirement and then click Start. Then, the Performing this operation will interrupt services? Continue? dialog box is displayed. Click OK. A dialog box is displayed, indicating that the operation is successful. Click OK.

2.

After configuring the service package, upload the NE data. (1) In the Main Menu, choose Configuration > NE Configuration Data Management. . In Configuration Data (2) In the left topology tree, select a created NE and click Management List, select an NE whose NE Status is Unconfigured. (3) Click Upload. The Confirm dialog box is displayed. Click OK to start the upload. (4) When the upload is complete, the Operation Result dialog box is displayed. Click Close.

Issue 01 (2011-10-20)


219


3.


Optional: To view the cross-connections created after the service package is configured, select the NE in the NE Explorer and then choose Configuration > WDM Service Management from the Function Tree; to view the attributes of an optical port on the board, select the board in the NE Explorer and then choose Configuration > WDM Interface from the Function Tree.


Deleting Cross-Connections See this section to learn how to delete a cross-connection.

l

WDM Cross-Connection Configuration Parameters See this section to learn how to set the parameters used for configuring a WDM crossconnection.

6.4 Configuring EPL/EVPL Services EPL/EVPL services belong to Ethernet services and are carried in WDM service signals.

6.4.1 EPL/EVPL Service Overview EPL/EVPL services include Ethernet private line (EPL) services and Ethernet virtual private line (EVPL) services.

EPL Services Two nodes are used to access EPL services and implement transparent transmission of the Ethernet services to the users. Service of one user occupies one VCTRUNK and need not share the bandwidth with the services of the other users, as shown in Figure 6-47. Therefore, in the case of EPL services, a bandwidth is exclusively occupied by the service of a user and the services of different users are isolated. In addition, the extra QoS scheme and security scheme are not required. Figure 6-47 EPL services

NE2

NE1 B

PORT2

PORT2 PORT1

VCTRUNK2 VCTRUNK1

A

TRUNKLINK2

VCTRUNK2

TRUNKLINK1

VCTRUNK1

B'

PORT1

A'

EVPL Services In the case of EVPL services, services of different users share the bandwidth. Therefore, the VLAN/QinQ scheme needs to be used for differentiating services of different users. If the Issue 01 (2011-10-20)


220



services of different users need to be configured with different quality levels, you need to adopt the corresponding QoS scheme. EVPL services are classified into two types, depending on whether the PORT or VCTRUNK is shared. There are two types of EVPL services: l

PORT-shared EVPL services

l

VCTRUNK-shared EVPL services – VLAN tag-based convergence and distribution of EVPL services – QinQ technology-based convergence and distribution of EVPL services

PORT-shared EVPL services As shown in Figure 6-48, the services of different users are accessed through an external port (that is, PORT) at a station, and are then isolated from each other by using the VLAN IDs. Services are transmitted to other PORTs at different station through different VCTRUNKs. Figure 6-48 PORT-shared EVPL services VCTRUNK2

VCTRUNK2 TRUNKLINK2

VLAN22

NE1 NE3

PORT1

PORT2

A'' VLAN22

A VLAN11 TRUNKLINK1 VCTRUNK1

VCTRUNK1

PORT1 NE2

A'

VLAN11

VCTRUNK-shared EVPL services As shown in Figure 6-49, the services of different users are isolated by using the VLAN/QinQ scheme. Therefore, the services of different users can be transmitted in the same VCTRUNK. l

VLAN tag-based convergence and distribution of EVPL services Figure 6-49 VLAN tag-based convergence and distribution of EVPL services

NE2

NE1 VLAN22

B

PORT2

PORT2 PORT1

B'

VLAN22

PORT1 TRUNKLINK1

VLAN11

Issue 01 (2011-10-20)

A

VCTRUNK1

VCTRUNK1


A'

VLAN11

221


l


QinQ technology-based convergence and distribution of EVPL services The implementation principle of the QinQ technology-based EVPL services and the implementation principle of the VLAN tag-based EVPL services are similar. Users of VLAN tag-based EVPL services are identified by only one layer of VLAN IDs. Users of QinQ technology-based EVPL services are identified by multiple layers of VLAN IDs. In this manner, the number of VLANs is extended and more users can be identified. Figure 6-50 QinQ technology-based convergence and distribution of EVPL services Remove Tags

Add Tags

C-VLAN1

C-VLAN1 S-VLAN2

C-VLAN1 S-VLAN2 NE2

NE1 B A

C-VLAN1

B' A'

PORT2

PORT2 PORT1

PORT1 TRUNKLINK1 VCTRUNK1

C-VLAN1

C-VLAN1 S-VLAN1

VCTRUNK1

C-VLAN1 S-VLAN1

Add Tags

C-VLAN1 Remove Tags

6.4.2 Configuring EPL Services EPL services provide a solution for the point-to-point transparent transmission of Ethernet services over an exclusive bandwidth. EPL services are applied to the scenarios where the userside data communication equipment connected to the transmission network does not support VLANs or where the VLAN planning is kept secret from the network carrier.

Prerequisite The parameters of WDM interfaces and Ethernet interfaces on a board must be configured.



In the NE Explorer, select the board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.

2.

Click New at the bottom of the window. The Create Ethernet Line Service dialog box is displayed.

3.

Enter the attributes of the Ethernet private line service in the dialog box.

Issue 01 (2011-10-20)


222



Field

Value

Remarks

Service Type

EPL, EVPL (QinQ)

Select EPL for this parameter for other E-Line services except the QinQ technology-based EVPL services.

Default: EPL Direction

Unidirectional, Bidirectional Default: Bidirectional

Set this parameter based on the service transmission direction. Generally, set this parameter to Bidirectional.

Source Port

Internal or external port

Name of the source port.

Source CVLAN (e.g. 1,3-6)

1-4095

This parameter is not required when you configure EPL services.

Sink Port


Name of the sink port.

Sink CVLAN (e.g. 1, 3-6)

1-4095

This parameter is not required when you configure EPL services.

Default: -

Default: -

NOTE

The Source C-VLAN and Sink C-VLAN parameters specify the VLAN IDs of the services received at the source and sink ports respectively when configuring PORT-shared EVPL services and VCTRUNK-shared EVPL services based on VLAN tags.

4.

Click OK. The created Ethernet private line service is displayed on the interface.


Formats of Ethernet Frames Describes the formats of Ethernet frames that contain different VLAN information, as defined by the IEEE 802.1q and IEEE 802.1ad protocols.

l

External Ports and Internal Ports Describes the definition of external ports and internal ports on Ethernet boards.

l

Auto-Negotiation Describes the auto-negotiation function.

l

Flow Control Describes the flow control methods and implementation principle.

l

Tag Attributes Describes the tag attributes.

l

Bridges Describes the types and functions of various bridges.

l Issue 01 (2011-10-20)

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

223



Describes the basic concept of the VLAN group. l

Configuring the Aging Time for MAC Addresses Describes how to modify the MAC address aging time as required. Generally, retain the default value.

l

Configuring Port Mirroring Describes how to configure port mirroring to monitor and analyze packets received or transmitted at a port being observed.

6.4.3 Configuring EVPL Services EVPL services are applied to the scenario where multiple users share bandwidth. In this scenario, the VLAN or QinQ mechanism is used to identify data of different users.



Background Information With the bandwidth-sharing feature, EVPL services can be configured and applied flexibly. One typical application scenario is to implement the VLAN multicast function by configuring multiple unidirectional EVPL services. These EVPL services have the same source but different sinks, and are called a VLAN multicast group. Services in a VLAN multicast group are also called member services of the VLAN multicast group. The sink ports of the member services are also called member ports of the VLAN multicast group. The LEM18 board supports a maximum of 2048 member services in a VLAN multicast group. Take the following precautions when configuring member services of a VLAN multicast group: l

Only unidirectional services can be configured as the member services.

l

All member ports must have the same network attributes.

l

A member port cannot be added to a LAG group.

Users of PORT-shared EVPL services and VCTRUNK-shared EVPL services based on VLAN tags are identified by one layer of VLAN tags. Each such service is considered as an EPL service with the VLAN ID. Compared with EPL services with exclusive PORT or VCTRUNK ports, VLAN IDs must be specified at the shared PORT or VCTRUNK ports for PORT-shared EVPL services or VCTRUNK-shard EVPL services based on VLAN tags. For details about the configuration method, see 6.4.2 Configuring EPL Services. This section describes how to configure QinQ technology-based EVPL services. The QinQ technology is implemented by adding a layer of 802.1Q tags to 802.1Q packets. Therefore, the number of VLANs is increased to 4096 x 4096. With the development of the metro Ethernet and the requirement of fine operation, QinQ double tags can be implemented in other scenarios. The inner and outer tags can represent different information. The inner tag (namely the C-VLAN) represents the client and the outer tag (namely the S-VLAN) represents the service. Table 6-43 lists the operation types of the QinQ technology-based EVPL services, short for the EVPL (QinQ) services, supported by the OptiX OSN 1800. Issue 01 (2011-10-20)


224



Table 6-43 EVPL (QinQ) service operation types Operation Type

Description

Illustration

Add S-VLAN

Adds the S-VLAN to a PORT port as required.

Strip S-VLAN

Strips the S-VLAN from a PORT port as required.

Transparently transmit C-VLAN

Transparently transmits the CVLAN.

Transparently transmit S-VLAN

Transparently transmits the SVLAN.

Transparently transmit S-VLAN and C-VLAN

Transparently transmits the SVLAN and CVLAN.

Translate S-VLAN

Switches the SVLAN of a PORT port as required.

Data C-VLAN

Data C-VLAN S-VLAN

Data C-VLAN S-VLAN

Data C-VLAN

Data

C-VLAN

Data C-VLAN

Data

S-VLAN

Data

Data C-VLAN S-VLAN

Data

S-VLAN1

S-VLAN

Data C-VLAN S-VLAN

Data

S-VLAN2


In the NE Explorer, select the board and then choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Click the EPL Service tab.

2.

Click New at the bottom of the window. The Create Ethernet Line Service dialog box is displayed.

3.

Enter the attributes of the EVPL services in the dialog box. Field

Value

Remarks

Service Type

EPL, EVPL (QinQ)

Select EVPL(QinQ) for the QinQ technologybased EVPL services.

Default: EPL Direction

Unidirectional, Bidirectional Default: Bidirectional

Issue 01 (2011-10-20)

Set this parameter based on the service transmission direction. Generally, set this parameter to Bidirectional. However, set this parameter to Unidirectional when configuring member services of a VLAN multicast group.


225



Field

Value

Remarks

Operation Type

Add S-VLAN, Strip S-VLAN, Transparently transmit CVLAN, Transparently transmit SVLAN, Transparently transmit SVLAN and CVLAN, Translate SVLAN

Set this parameter based on the VLAN plan of the received service. For the description of different operation types, see Table 6-43. The value "Strip S-VLAN" is valid only for unidirectional services.

Default: Add SVLAN Source Port


Name of the source port.

Source CVLAN(e.g.1, 3-6)

1-4095

Set this parameter based on the received service. The value ranges from 1 to 4095.

Source SVLAN

1-4095

Sink Port


Name of the sink port.

Sink C-VLAN (e.g.1, 3-6)

1-4095

Set this parameter based on the received service. The value ranges from 1 to 4095.

Sink S-VLAN

1-4095

Default: -

Default: -

Default: -

Default: -

4.

Set the S-VLAN ID. The value ranges from 1 to 4095.

Set the S-VLAN ID. The value ranges from 1 to 4095.

Click OK. The created EVPL (QinQ) service is displayed in the window. NOTE

If the window does not display the created EVPL (QinQ) service, select Display QinQ Shared Service in the lower-right area of the window.



l


l Issue 01 (2011-10-20)

Auto-Negotiation Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

226



Describes the auto-negotiation function. l


l


l


l

VLAN Group Describes the basic concept of the VLAN group.

l

Creating VLAN Groups Describes how to create a VLAN group when you want to apply the same service configurations to specific VLANs or extend the number of VLANs.

l


l


6.5 Configuring EPLAN/EVPLAN Services EPLAN/EVPLAN services belong to Ethernet services and are carried in WDM service signals.

6.5.1 EPLAN/EVPLAN Service Overview EPLAN/EVPLAN services include Ethernet private local area network (EPLAN) and Ethernet virtual private local area network (EVPLAN) services.

EPLAN Services Currently, E-LAN services mainly refer to Ethernet private LAN (EPLAN) services. Based on the Layer 2 switching function, the EPLAN implements transmission of the accessed data based on the destination media access control (MAC) address of the data. The EPLAN services can be accessed from a minimum of two nodes. The services of different users do not need to share the bandwidth. That is, for EPLAN services, a bandwidth is exclusively occupied by the service of a user and the services of different users are separated. In addition, the extra QoS scheme and security scheme are not required. There is more than one node in EPLAN services, and therefore the nodes need to learn the MAC addresses and forward data based on MAC addresses. Therefore, Layer 2 switching is involved. See Figure 6-51.

Issue 01 (2011-10-20)


227



Figure 6-51 EPLAN services

PORT1

VB

VB NE3

NE 1

VCTRUNK1 PORT1

PORT1

VCTRUNK1 PORT1

NE 2

Department 2

Department 3 PORT1

IEEE 802.1d bridge VCTRUNK1

VB

VCTRUNK2

Department 1

PORT1 VCTRUNK

As shown in Figure 6-51, three branches of user F need to communicate with each other. On NE1, the IEEE 802.1d bridge is established to implement EPLAN services. IEEE 802.1d bridge can create the MAC address-based forwarding table, which is periodically updated by using the self-learning function of the system. Accessed data can be forwarded or broadcasted within the domain of the IEEE 802.1d bridge based on the destination MAC addresses. To avoid a broadcast storm, EPLAN services cannot be set as a ring. If the EPLAN services are set as a ring, the Multiple Spanning Tree Protocol (MSTP) must be started in the network.

EVPLAN Services EVPLAN services of different users need to share the bandwidth. Therefore, the VLAN/QinQ scheme needs to be used for differentiating the data of different users. If the services of different users need to be configured with different quality levels, you need to adopt the corresponding QoS scheme. EVPLAN services can be implemented by establishing the IEEE 802.1q bridge and the IEEE 802.1ad bridge. IEEE 802.1q bridge: The IEEE 802.1q bridge supports isolation by using one layer of VLAN tags. This bridge checks the contents of the VLAN tags in the data frames and performs Layer 2 switching based on the destination MAC addresses and VLAN IDs. As shown in Figure 6-52, three branches of user G need to communicate with each other. Services of user G need to be isolated from the services of user H. In this case, the operator needs to separately groom the VoIP services and HSI services, be established on NE1 to implement EVPLAN services.

Issue 01 (2011-10-20)


228



Figure 6-52 EVPLAN services (IEEE 802.1q bridge) VLAN11

VLAN11 PORT1 VB PORT2 VLAN22 VCTRUNK1

PORT1 PORT2 VLAN22 VCTRUNK1 VB

PORT1

NE3

NE 1

PORT1 PORT2

PORT2

Company A Department 2


NE 2 Company B Department 2

PORT2

PORT1


Company B Department 3

Company B Department 1 IEEE 802.1q bridge

VCTRUNK1 VLAN11

VB

VCTRUNK2 VLAN22

PORT1 PORT2 VCTRUNK

IEEE 802.1ad bridge: The IEEE 802.1ad bridge supports data frames with two layers of VLAN tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and supports only the mounted ports whose attributes are C-Aware or S-Aware. This bridge supports the following switching modes: l

This bridge does not check the contents of the VLAN tags in the data frames, and performs Layer 2 switching based on the destination MAC addresses of the data frames.

l

This bridge checks the contents of the VLAN tags in the data frames, and performs Layer 2 switching based on the destination MAC addresses and the S-VLAN IDs of the data frames.

As shown in Figure 6-53, the GE services from user M and the FE services from user N need to access network respectively. In this case, the operator needs to separately groom the GE services and FE services, and isolate the data on the transmission network side. On NE1, the IEEE 802.1ad bridge must be established to support the EVPLAN services.

Issue 01 (2011-10-20)


229



Figure 6-53 EVPLAN services (IEEE 802.1ad bridge) Service C-VLAN GE 10 FE 20 PORT1

Service C-VLAN GE 10 FE 20

VB

VB

Service S-VLAN GE 100 FE 200

NE3

NE 1

VCTRUNK1

VCTRUNK1

PORT1

PORT1 Service S-VLAN GE 100 FE 200

NE 2 PORT3

Department 4

Department 2

GE

VB

PORT2

FE

IEEE 802.1ad bridge S-VLAN 100 VCTRUNK1

PORT1

VCTRUNK2

Department 3

Department 1

IEEE 802.1ad bridge S-VLAN 200 VCTRUNK1

PORT3

VB

VCTRUNK2

PORT2 VCTRUNK

6.5.2 Configuring EPLAN Services EPLAN services are applied to point-to-multipoint scenarios and are generally configured at aggregation nodes in a network. For non-aggregation nodes, EPL or EVPL services are configured.




Create the IEEE 802.1d bridge. (1) In the NE Explorer, select the board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Select the Service Mount tab. (2) Click New at the bottom of the window. The Create Ethernet LAN Service dialog box is displayed. (3) Enter the attributes of the E-LAN service in the dialog box.

Issue 01 (2011-10-20)


230



Field

Value

Remarks

VB Name

A maximum of 16 English letters or numerals

This parameter is a character string used to describe the bridge. It is recommended that you set this parameter to a character string that contains the information about the detailed application of the bridge.

VB Type

IEEE 802.1d, IEEE 802.1q, IEEE 802.1ad

Select IEEE 802.1d for this parameter when configuring EPLAN services. The IEEE 802.1d MAC bridge learns and forwards the packets based on the MAC addresses of the user packets. The information in the VLAN tags of the user packets, however, is not considered in the learning and forwarding process. The IEEE 802.1d MAC bridge is used when the entire information of the VLANs used by the client cannot be learned or when the data between the VLANs of the client does not need to be separated.

Default: IEEE 802.1q

Bridge Switch Mode

SVL/Ingress Filter Disable, IVL/ Ingress Filter Enable Default: IVL/ Ingress Filter Enable

Set this parameter to SVL/Ingress Filter Disable for the IEEE 802.1d bridge. All the VLANs share the same MAC address table. That is, the bridge learns and forwards the packets based on the MAC address of the user packets only. The information in the VLAN tags of the user packets, however, is not considered in the learning and forwarding process.

(4) Click Configure Mount.... The Service Mount Configuration dialog box is displayed. (5) Select the ports that you want to mount to the bridge from Available Mounted Ports, and then click Forwarding Ports.

. The selected ports are displayed in Selected

(6) Click OK. The configured mounting ports are displayed in Service Mount. (7) Click OK. The created EPLAN services are displayed in the window. 2.

Change the Hub/Spoke attribute of the ports mounted to the bridge. (1) Select the created bridge and click the Service Mount tab. (2) Change the Hub/Spoke attribute of the mounted ports based on the service planning. l Ports of the Hub attribute can communicate with ports of the Spoke attribute. l Ports of the Hub attribute can communicate with each other. l Ports of the Spoke attribute cannot communicate with each other. TIP

In the window, you can also modify the port attributes such as the tag attribute, auto-negotiation mode, and port enable status of the ports mounted to the bridge.

(3) After setting the parameters, click Apply.

Issue 01 (2011-10-20)


231





l


l


l


l


l


l


l


l


6.5.3 Configuring EVPLAN Services (IEEE 802.lq Bridge) EVPLAN services are applied to multipoint-to-point scenarios and are generally configured at aggregation nodes in a network. For non-aggregation nodes, EPL or EVPL services are configured.




Establish the IEEE 802.1q bridge. (1) In the NE Explorer, select the board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the Service Mount tab. (2) Click New at the bottom of the window. The Create Ethernet LAN Service dialog box is displayed. (3) Enter the attributes of the Ethernet LAN service in the dialog box.

Issue 01 (2011-10-20)


232



Field

Value

Remarks

VB Name



VB Type


Set this parameter to IEEE 802.1q when configuring EVPLAN services (IEEE 802.1q bridge). The IEEE 802.1q bridge supports isolation by using one layer of VLAN tags. This bridge checks the contents of the VLAN tags that are in the data frames and performs Layer 2 switching according to the destination MAC addresses and VLAN IDs.


Bridge Switch Mode

IVL/Ingress Filter Enable, SVL/Ingress Filter Disable Default: IVL/ Ingress Filter Enable

Set the parameter to IVL/Ingress Filter Enable for the IEEE 802.1q bridge. The bridge checks the contents of the VLAN tags that are in the packets and performs Layer 2 switching according to the destination MAC addresses and the VLAN IDs of the packets.

(4) Click Configure Mount.... The Service Mount Configuration dialog box is displayed. (5) Select the ports that need to be mounted to the bridge forAvailable Mounted Ports. Click Ports.

. Then the selected ports are displayed in Selected Forwarding

(6) Click OK. The configured ports that are mounted to the bridge are displayed in Service Mount. (7) Click OK. The created Ethernet LAN services are displayed. 2.

Create a VLAN filtering table for each VLAN based on the VLAN design for the services. (1) Select the created bridge and click the VLAN Filtering tab. (2) Click New. (3) Enter the ID of the VLAN that needs a VLAN filtering table for VLAN ID. (4) Select the ports that are required to forward data from Available Forwarding Ports. Click Ports.


(5) Click Apply to complete creating the VLAN filtering table. (6) Create VLAN filtering tables for all VLANs by performing the preceding operations. Then click OK. 3.

Change the Hub/Spoke attribute of the ports mounted to the bridge. (1) Select the created bridge and click the Service Mount tab. (2) Change the Hub/Spoken attribute of a port mounted to the bridge based on the service plan.

Issue 01 (2011-10-20)


233



l Ports of the Spoke attribute can communicate with ports of the Hub attribute. l Ports in the Hub mode can communicate each other. l Ports in the Spoke mode cannot communicate each other. TIP

The attributes such as the tag attribute,the enable status of the auto-negotiation mode, and the enable status of the port of a port mounted to the bridge can be modified in the window.




l


l


l


l


l


l


l


l


6.5.4 Configuring EVPLAN Services (IEEE 802.laq Bridge) EVPLAN services are applied to multipoint-to-point scenarios and are generally configured at aggregation nodes in a network. For non-aggregation nodes, EPL or EVPL services are generally configured.


Tools, Equipment, and Materials Web LCT or U2000 Issue 01 (2011-10-20)


234



Background Information The IEEE 802.1ad bridge supports ports with the C-Aware and S-Aware attributes only. The C-Aware ports are used to add and strip the S-VLAN tags. The S-Aware ports are used to transparently transmit the S-VLAN tag. The IEEE 802.1ad bridge supports the following operation types: l

Adding the S-VLAN tag based on the port

l

Adding the S-VLAN tag based on the port and C-VLAN

l

Performing port mounting based on the port

l

Performing port mounting based on the port and the S-VLAN

When Bridge Switch Mode of the IEEE 802.1ad bridge is IVL/Ingress Filter Enable, the preceding four operation types are supported. When Bridge Switch Mode of the IEEE 802.1ad bridge is SVL/Ingress Filter Disable, only the first operation type (adding the S-VLAN tag based on the port) and the third operation type (performing port mounting based on the port) are supported. This section describes the four operaton types in the condition that Bridge Switch Mode of the IEEE 802.1ad bridge is IVL/Ingress Filter Enable l

Adding the S-VLAN based on the port: The packets that enter the C-Aware port are added with the preset S-VLAN tag, and are forwarded in the bridge according to the S-VLAN filtering table. Before the packets leave the C-Aware port, the S-VLAN tag is stripped.

l

Adding the S-VLAN tag based on the port and C-VLAN: Then entry detection is performed for the packets that enter the C-Aware port. Then, the corresponding S-VLAN tags are added to the packets according to the mapping between the C-VLAN tags and the S-VLAN tags of the packets. If the mapping relationship does not exist, the packets are discarded. After the S-VLAN tags are added, the packets enter the bridge, where the packets are forwarded according to the S-VLAN filtering table. Before the packets leave the C-Aware port, the S-VLAN tag is stripped. NOTE

l The same C-Aware port supports different C-VLAN tags being mapped to different S-VLAN tags, but does not support the same C-VLAN tag being mapping to multiple S-VLAN tags.

l

Performing port mounting based on the port: The packets that enter the S-Aware port are not filtered. Instead, the S-VLAN switch is performed directly. The packets must have the S-VLAN tags. Otherwise, the packets are discarded. When the packets leave the S-Aware port, the packets are transparently transmitted.

l

Performing port mounting based on the port and the S-VLAN: The entry filtering is performed according to the preset S-VLAN tag. The packets that do not belong to the SVLAN are discarded. Then, the packets are forwarded according to the S-VLAN filtering table. When the packets leave the S-Aware port, the packets are transparently transmitted.

In the case of the four operation types, the following conditions must be met before the packets leave a port: l

The port is contained in the S-VLAN filtering table that is created by the user.

l

The S-VLAN ID corresponding to the port must be specified when the user manually mounts the port to the bridge. – In the case of a C-VLAN port, the S-VLAN ID corresponding to the port is the S-VLAN ID that is added when the packets enter the port. – In the case of an S-VLAN port, the S-VLAN ID corresponding to the port is the SVLAN ID that is set when the user mounts the port to the bridge. If the S-Aware port

Issue 01 (2011-10-20)


235



is mounted based on the port, the S-VLAN ID is considered to contain all the legal SVLAN IDs.


Establish the IIEEE 802.1ad bridge. (1) In the NE Explorer, select the board and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Click the Service Mount tab. (2) Click New at the bottom of the window. The Create Ethernet LAN Service dialog box is displayed. (3) Enter the attributes of the Ethernet LAN service in the dialog box. Parameter

Value

Remarks

VB Name



VB Type


Set the parameter to IEEE 802.1aq when configuring EVPLAN services (IEEE 802.1aq bridge). The IEEE 802.1ad bridge supports packets with two layers of VLAN tags and adopts the outer S-VLAN tags to isolate services of different VLANs. It can be mounted to the ports whose attributes are C-Aware and S-Aware only.


Bridge Switch Mode

IVL/Ingress Filter Enable, SVL/Ingress Filter Disable Default: IVL/ Ingress Filter Enable

The IVL/Ingress Filter Enable and SVL/ Ingress Filter Disable modes can be adopted by the IEEE 802.1ad bridge. l IVL/Ingress Filter Enable: VLAN tags in the data frames received at the bridge are checked. Layer 2 switch is performed based on the destination MAC adresses and the S-VLAN ID of a data frame. l SVL/Ingress Filter Disable: VLAN tags in the data frames received at the bridge are not checked. Layer 2 switch is performed based on the destination MAC adresses of a data frame.

(4) Click Configure Mount.... A Service Mount Configuration dialog box is displayed. (5) Set service mounting attributes.

Issue 01 (2011-10-20)


236



Field

Value

Remarks

Operation Type

Add S-VLAN base for Port, Add S-VLAN base for Port and C-VLAN, Mount Port, Mount Port and base for Port and S-VLAN

Select the proper operation types based on received services at a port. For detailed description of operation types, see Background Information.

Default: Add SVLAN base for Port VB Port

The VB logical port number. For example, 1.

Set the number of the mounted VB port.

Mount Port

An internal or external port

Select the external port or internal port to be mounted.

C-VLAN

1-4095

Specifies the CVLAN ID of a service received at a port. The parameter is valid only when Operation Type is Add S-VLAN base for port and C-VLAN.

Default: -

S-VLAN

1-4095 Default: -

Specifies the S-VLAN ID to be identified or added in the services received at a port. The parameter is valid only when Operation Type is not Mount Port.

(6) Click Add Mount Port. The mounted ports are displayed in the window. (7) After mounting all ports, click OK. The created E-LAN services are displayed in the window. 2.

Create a VLAN filtering table for each S-VLAN based on the S-VLAN design for the services. (1) Select the created bridge and click the VLAN Filtering tab. (2) Click New. (3) Enter the ID of the VLAN that needs a VLAN filtering table for VLAN ID. (4) Select the ports that are required to forward data from Available Forwarding Ports. Click Ports.


(5) Click Apply to complete creating the VLAN filtering table. (6) Create VLAN filtering tables for all VLANs by performing the preceding operations. Then click OK. 3.

Change the Hub/Spoke attribute of the ports mounted to the bridge. (1) Select the created bridge and click the Service Mount tab.

Issue 01 (2011-10-20)


237



(2) Modify the Hub/Spoken attribute of a port mounted to the bridge according to service plan. l Ports of the Spoke attribute can communicate with ports of the Hub attribute. l Ports of the Hub attribute can communicate each other. l Ports of the Spoke attribute cannot communicate each other. TIP

The attributes such as the tag attribute,the enable status of the auto-negotiation mode, and the enable status of the port of a port mounted to the bridge can be modified in the window.




l


l


l


l


l


l


l


l


6.6 Configuring SDH Service The TSP board supports configuration of SDH service.

Prerequisite You must have logged in to the NE where the TSP board resides. Service types must be set for WDM optical interfaces on the board. Issue 01 (2011-10-20)


238




Background Information When configuring an SDH service, select a proper timeslot according to the service level. Table 6-44 lists the timeslots available for optical interfaces on the TSP board. Table 6-44 Timeslots available for optical interfaces on the TSP board Service Level

Timeslot for E1/ T1 Interface

Timeslot for TX1/ RX1 and TX2/RX2 Interfaces

Timeslot for IN1/OUT1 and IN2/OUT2 Interfaces

VC12

5-25

1-63

1-63

VC4

-

1

l When the service type is STM-1, the timeslot must be 1. l When the service type is STM-4, the timeslot ranges from 1 to 4.

NOTE

In the case of the TSP board, the default service type is STM-1.


In the NE Explorer, select the NE and then choose Configuration > Cross-Connection Configuration from the Function Tree.

2.

Click New on the right of the window, and the Create SDH Service dialog box is displayed.

3.

Set Level, Direction, Source, Source Port, Source VC4, Source Timeslot Range(e.g. 1,3–6), Sink, Sink Port, Sink VC4 and Sink Timeslot Range(e.g.1,3–6) according to the SDH service planning.

4.

Click OK.


In the NE Explorer, select the NE and then choose Configuration > SDH Service Configuration from the Function Tree.

2.

Click Create on the right of the window, and the Create SDH Service dialog box is displayed.

3.

Set Level, Direction, Source Slot, Source Timeslot Range, Sink Slot, Sink Timeslot Range and Activate Immediately according to the SDH service planning. Click OK. The Operation Result dialog box is displayed, indicating that the operation is successful. Click OK. NOTE

Activate Immediately is generally set to Active.

Issue 01 (2011-10-20)


239


7

7 Follow-up Operations (Including Data Backup)

Follow-up Operations (Including Data Backup)

About This Chapter 7.1 Creating Fibers Correct logical fiber connections enable users to understand the network structure easily and to locate faults rapidly during operation and maintenance of a network. In addition, correct and complete fiber connections are one of the prerequisites for configuring services using WDM trails. 7.2 Configuring WDM Trails The U2000 manages WDM trails by using functions such as creating, viewing, combining, separating, and deleting end-to-end WDM trails, and provides signal flow diagrams of the WDM trails to show the signal flows of the WDM trails. 7.3 Backing Up the NE Database to the SCC Board By backing up an NE database to an SCC board, you can ensure that the NE automatically restores to the normal state in case a power failure occurs. When you back up an NE database to an SCC board, you actually back up the NE data to the flash memory of the SCC board. After a power-off reset occurs on the NE, the SCC board automatically reads the configuration data from the flash memory and applies the data to the boards on this NE. 7.4 Checking Optical Power of Boards By checking the optical power of a board, you can ensure that the transmit and receive optical power of the board is within the normal range. When commissioning the OptiX OSN 1800, you can adjust the optical power of a board at the site by adding, replacing, or removing a fixed optical attenuator (FOA) or adjusting a variable optical attenuator (VOA) before an optical port. 7.5 Querying Bit Errors Before and After FEC The count of bit errors before and after FEC is a key specification for measuring the system operation quality. 7.6 Viewing Current Alarms on an NE and Removing Abnormal Alarms Viewing the current alarms on an NE helps you to intuitively and quickly locate an exception on the network. This helps you to identify a fault on the network. 7.7 Testing Protection Switching Issue 01 (2011-10-20)


240



In the commissioning or configuration phase, you can run a manual switching command to check whether protection switching can be performed normally. 7.8 Querying and Saving the Networkwide Optical Power and Alarm Data After commissioning a network, you need to query and save the optical power and alarm data of the entire network. This type of data can help you analyze and understand the operating status of the network in future. 7.9 Backing Up NE Data to the NMS Server or Client You can manually back up the data of one or more NEs of the same type to an NMS server or client.

Issue 01 (2011-10-20)


241



7.1 Creating Fibers Correct logical fiber connections enable users to understand the network structure easily and to locate faults rapidly during operation and maintenance of a network. In addition, correct and complete fiber connections are one of the prerequisites for configuring services using WDM trails.

Prerequisite Optical NEs, NEs, and logical boards must be created.

Tools, Equipment, and Materials The U2000 must be used.


Create fibers between NEs. (1) Click the shortcut icon

on the Main Topology and the cursor is displayed as "+" .

(2) Click the source NE of the fiber on the Main Topology. (3) Select the source board and source port in the Select Fiber/Cable Source dialog box displayed. (4) Click OK. The Main Topology is displayed and the cursor is displayed as "+" again. (5) Click the sink NE of the fiber in the Main Topology. (6) Select the sink board and sink port in the Select Fiber/Cable Sink dialog box displayed. (7) Click OK and enter the attributes of the fiber in the Create Fiber/Cable dialog box displayed. (8) Click OK. The created fiber is displayed between the source NE and the sink NE on the Main Topology. TIP

To delete a fiber, right-click a fiber that has been created and choose Delete.

2.

Create internal fibers of an NE. (1) Double-click an optical NE on the Main Topology. Click the Signal Flow Diagram tab. (2) In the Signal Flow Diagram, right-click in the blank area and choose Create Fiber from the shortcut menu. The cursor is displayed as "+". (3) Select the source board and port and click OK. The cursor is displayed as "+". (4) Select the sink board and port and click OK. TIP

When a wrong source or sink board or port is selected, right-click to cancel the operation and exit object selection.

(5) In the Create Fiber/Cable dialog box, enter the attributes of the fiber. (6) Click OK. Issue 01 (2011-10-20)


242



TIP

To delete a fiber, right-click a fiber that has been created and choose Delete.


Creating Fibers in List Mode You can also create fibers in list mode on the U2000. Creating fibers in list mode is not intuitive when compared with creating fibers in graphic mode; however, you can manage all fibers/cables through a same user interface when creating fibers in list mode.


7.2 Configuring WDM Trails The U2000 manages WDM trails by using functions such as creating, viewing, combining, separating, and deleting end-to-end WDM trails, and provides signal flow diagrams of the WDM trails to show the signal flows of the WDM trails. This section describes how to configure the WDM trails supported by the OptiX OSN 1800. For details about searching for, creating, and managing WDM trails, see the U2000 Help. NOTE

When the ELOM board works in 8*Any->ODU0_ODU1 mode, end-to-end configurations of services are not supported.

7.2.1 Searching WDM Trails After configuring services on an NE, search for WDM trails on the NE so that you can manage services based on WDM trails.

Prerequisite All fibers must be created properly. All required services must be configured properly on the NE.


Background Information The OptiX OSN 1800 supports searching for the following WDM trails on the U2000: l

Client trail

l

ODUk trail

l

OTUk trail

l

OCh trail

l

OMS trail

Issue 01 (2011-10-20)


243


l


OTS trail

Of these WDM trails, you can manage OTS trails directly without searching for them, because the OTS trail data is stored at the network layer when fibers are connected.

Precautions NOTE

In the process of searching and creating WDM trails, discrete services may be generated. You need to analyze and remove the discrete services to ensure that no discrete service exist on the network at last.


In the Main Menu, choose Service > WDM Trail > Search for WDM Trail to display the WDM Trail Search navigation.

2.

In the Advanced settings area, set various handling policies associated with trail searching.

NOTE

l When you search for WDM trails for the first time, it is recommended to select Query attributes of boards from the NE before searchingto obtain board attribute information such as the wavelengths on the board. For other items, retain the default values. l In the mode of searching for WDM trails by subnet, it is recommended that the selected subnet should be separate from the other portions of the network. That is, no fiber connection exists between the selected subnet and any other portion on the network.

3.

Issue 01 (2011-10-20)

Click Next to start searching for WDM trails. Wait until the status bar shows the end of the searching.


244



NOTE

l If certain cross-connections conflict with each other and thus fail to form an end-to-end trail, the information about these cross-connections is displayed in the search result when the searching is complete. You can rectify the problem according to the conflict information. l Certain cross-connections may conflict with each other when the network architecture is changed or a trail that may cause an interruption of service flows exists. You can determine whether conflicting cross-connections exist by deleting certain routing information such as deleting a cross-connection or a fiber

4.

Optional: Click Next to view the information about the conflicting trails. Right-click a trail, you can configure it with a management flag. NOTE

If you have selected Automatically create trails after searching in the search policies, skip this step. If you perform this step, the NMS will remove the trails that are not configured with management flags from the network in the next step. The deletion does not affect the actual services on the NE and the data of the NE saved on the NMS.

5.

Click Next to view all discrete services on the network. NOTE

The possible causes of discrete services and the method for removing discrete services are as follows: l The data on the NE is inconsistent with that on the NMS. In this case, upload the configuration data to the NMS. l Fibers are created inappropriately and the created fiber connections are inconsistent with the physical fiber connections. In this case, check and ensure that the fiber connections created on the NMS are consistent with the physical fiber connections between real equipment. l NE configuration data is incorrect and service configuration is incomplete. In this case, correct the NE configuration data and configure services completely.

6.

When the search is complete, click Finish. In the displayed dialog box indicating that the search is complete, click OK.


7.2.2 Creating WDM Trails You can create OCh, ODUk, or client trails by specifying the sources and sinks of the trails.

Prerequisite All fibers must be created properly. A trail at the corresponding server layer must be searched out or created. All the NEs on the trail must communicate with each other properly.

Tools, Equipment, and Materials The U2000 must be used. Issue 01 (2011-10-20)


245



Background Information Before creating a WDM trail, you need to search for or create a trail at the corresponding server layer. The details are as follows: l

Before creating an OCh trail, you need to search for an appropriate trail at the OMS server layer.

l

Before creating an ODUk trail, you need to search for an appropriate trail at the OTUk server layer.

l

Before creating a client trail, you need to search for or create an appropriate trail at the OCh and ODUk server layer.

When OCh trails exist, client trails can be directly created. The ODUk service-layer trails are created automatically. Note that client trails may exist on multiple ODUk service-layer trails of different levels in a scenario where the OptiX OSN 1800 is interconnected with other NG WDM series products. In this scenario, create all ODUk trails section by section before creating endto-end client trails. For example, part of a client trail exists on an ODU1 trail and the other part of the client trail exists on an ODU0 trail. In this scenario, create an ODU1 trail and an ODU0 trail for the client trail and then create the whole end-to-end client trail. For the OptiX OSN 1800, l

For boards or ports that do not support cross-connections, all the existing WDM trails are created automatically after searching WDM trials are complete. You do not need to create WDM trails.

l

For boards or ports that support cross-connections, – If the cross-connections on the boards or ports are correctly configured before WDM trails are searched out, all the existing WDM trails are created automatically after searching WDM trials are complete. You do not need to create WDM trails. – If cross-connections are not configured on the boards or ports before WDM trails are searched out, configure cross-connections by creating client trails after searching WDM trials. This method of creating trails is called "configuring services by creating trails".

Precautions NOTE

You can configure services by creating client trails for only boards that support the cross-connection function.


In the Main Menu, choose Service > WDM Trail > Create WDM Trail to display the Create WDM Trail navigation.

2.

Set Level, Rate, and Direction for the trail to be created.

Issue 01 (2011-10-20)


246


3.


Click Browse next to Source or Sink. In the displayed window, select the desired NE on the left and select the desired board in the board layout on the right. Then, select the desired optical port in Available Timeslots/Port. Click OK. In the case of the master/slave subrack mode, you can switch the NE panel views of the subracks by clicking the tabs on the top of the NE panel view.

4.

Optional: Click a server tail between the source and sink NEs. In the displayed dialog box, specify a route as the explicit route for the services. You can click the route again and cancel the selected explicit route in the displayed dialog box.

5.

Optional: Double-click another NE in the subnet to specify it as an excluded NE. The sign is shown on the NE. Double-click the NE again to cancel your selection.

6.

Optional: Click Specify Route Channel to display the Specify Route Channel dialog box. After selecting the working channel of the services, click OK.

7.

Click the General Attributes tab and then set the basic attributes such as name and ID of this trail on the tab page.

8.

Select the Activate the trail check box and click Apply to create this trail. A dialog box is displayed, indicating that the operation is successful. Click Close.

7.2.3 Managing WDM Trails You can manage WDM trails after searching out or creating the WDM trails.

Prerequisite All fibers must be created properly. WDM trails must be searched out or created. All the NEs on the trail must communicate with each other properly.


Background Information U2000 describes various WDM management functions, such as viewing WDM trails, modifying WDM trails, and maintaining WDM trails. You can perform WDM management as required. This section describes how to navigate to the specific window on the NMS for managing WDM trails. For details about WDM management functions and operations on the U2000, see the U2000 Help. Issue 01 (2011-10-20)


247




In the Main Menu, choose Service > WDM Trail > Manage WDM Trail.

2.

In the displayed Set Trail Browse Filter Criteria dialog box, specify filtering conditions. Click Filter All. The information about the trails that are filtered are displayed in the window. l If you need to filter all trails that meet the set filtering conditions, click Filter All. l If you need to add trails that meet new conditions to the existing trails, click Incremental Filter. l If you need to filter the existing trails according to new filtering conditions, click Secondary Filter.

3.

Right-click the trail that needs to be managed, and then perform required management operations.

7.3 Backing Up the NE Database to the SCC Board By backing up an NE database to an SCC board, you can ensure that the NE automatically restores to the normal state in case a power failure occurs. When you back up an NE database to an SCC board, you actually back up the NE data to the flash memory of the SCC board. After a power-off reset occurs on the NE, the SCC board automatically reads the configuration data from the flash memory and applies the data to the boards on this NE.

Prerequisite You must have logged in to an NE. The NE must be configured properly.


Precautions NOTE

After backing up an NE database to an SCC board, you can restore the NE database from the SCC board by performing a warm or cold reset on the SCC board.


In the Main Menu, choose Configuration > NE Configuration Data Management.

2.

Select the NE from the Function Tree, and then click

3.

In Configuration Data Management List, select an NE or multiple NEs of which the database you want to back up. Click Back Up NE Data and select Back Up Database to SCC. In the displayed confirmation dialog box, click OK.

4.

The Result dialog box is displayed. Click Close.

.

Reference Information l Issue 01 (2011-10-20)

Compare the methods of backing up and restoring NE data Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

248



The backup or restored NE database can be saved on the SCC board, NMS server, or NMS client. Different storage locations determine different backup and restoration methods. l

Restore the NE database from the SCC board When a database file is lost due to a factor such as NE maintenance or NE fault, you can restore the DRDB database that has been backed up in the flash memory of the SCC board.


7.4 Checking Optical Power of Boards By checking the optical power of a board, you can ensure that the transmit and receive optical power of the board is within the normal range. When commissioning the OptiX OSN 1800, you can adjust the optical power of a board at the site by adding, replacing, or removing a fixed optical attenuator (FOA) or adjusting a variable optical attenuator (VOA) before an optical port.

Prerequisite The performance monitoring function must be enabled. Fiber connections must be established properly and lasers must be enabled.

Tools, Equipment, and Materials The Web LCT or U2000 is used for querying the optical power of a board. The U2000 must be used for querying the optical power of the entire network.


Query the current optical power of the board. Check whether the input optical power for each optical port is in the range of Input Power Lower Threshold(dBm) and Input Power Upper Threshold(dBm). (1) In the NE Explorer, select the board whose optical power you need to query. Choose Configuration > Optical Power Management from the Function Tree. (2) Click Query to read the current optical power value from the NE.

2.

Rectify incorrect input optical power. l If the input optical power for an optical port is greater than Input Power Lower Threshold(dBm), add a FOA or replace the existing FOA before the optical port to ensure that the input optical power meets the design requirement. l If the input optical power value is smaller than Input Power Upper Threshold (dBm), do as follows: – Check the transmit optical power of the opposite board. If the transmit optical power of this board is abnormal, replace the transmitter on this board. – Check whether appropriate FOAs are installed on the link against the FOA installation table. – Check and clean the fiber endfaces and flanges on the ODF.

Issue 01 (2011-10-20)


249



– Check whether fiber jumpers are bent seriously or bundled too tightly. – If the attenuation of line fibers is excessive, recommend customers to rectify the line fibers or add an REG station to ensure that the actual line attenuation is smaller than the line attenuation specified in the design document. TIP

At the site, you can also use the following methods to determine whether the input optical power at an optical port on a board meets the design requirement: l Use an optical power meter to measure the input optical power at an optical port. Then, determine whether the input optical power is normal according to the permitted optical power range. l Check the status of the LED corresponding to this optical port, such as IN, IN1, IN2, IN3, IN4, RM1, or RM2, on the front panel of the board. l Always on (red): indicates that the receive optical power is excessively low. l Blink (red): indicates that the receive optical power is excessively high. l Always on (green): indicates that the receive optical power is normal.

3.

Check the value of Output Power(dBm) for each optical port on the board. The value must be within the specified range. If the value for an optical port is out of the specified range, replace the optical module at the optical port. For detailed specifications of a board, see the Hardware Description.


Query optical power networkwide. (1) Choose Configuration > Optical Power Management from the Main Menu of the U2000. (2) Select all the stations from the navigator on the left, click

.

(3) Click Query, in the Result dialog box, click Close. 2.

Customize an optical power management template. After customizing the template, you can determine whether the optical power is in the normal range by directly checking the template. For the OptiX OSN 1800, the Input Power Reference Upper Threshold(dBm) and Input Power Upper Threshold(dBm) fields have the same value, and the Input Power Reference Lower Threshold(dBm) and Input Power Lower Threshold(dBm) fields have the same value. (1) In the Main Menu, choose Configuration > Optical Power Management to display the Optical Power Management window. (2) Select the NEs in the NE list on the left of the window, and then click

.

(3) On the right of the window, click Query. In the displayed dialog box, click Close. (4) Right-click the title field and then choose Column Setting from the shortcut menu. In the displayed dialog box, select the desired parameters. Display or hide the selected parameters as required. You can also change the position where a parameter is displayed and customize the width of the display field and the parameter name. For example, in the case of a network with no optical amplifier (OA) boards, you are recommended to hide the Pump Max Output Power (dBm) and Pump Min Output Power (dBm) fields. After the setting, click OK. TIP

After clicking the title area, select a parameter field directly and then hide or display it as required.

Issue 01 (2011-10-20)


250



(5) Set Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm). The U2000 compares the obtained Input Power (dBm) with the Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm) values to determine whether the input optical power is normal. If Input Power (dBm) is in the range of Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm), the input optical power is normal. If the input optical power exceeds either of the preceding thresholds by less than 2 dB, the Input Power State field is displayed as warning alert; if the deviation is greater than 2 dB, the input power state is displayed as critical alert. The Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm) fields have no default values. If either of them is not set, the U2000 does not check for the input power state. NOTE

If the Input Power Reference Value (dBm) field is set but the Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm) fields are not set, the U2000 automatically generates Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm) according to Input Power Reference Value (dBm). In this case, the following formulas must be satisfied: l Input Power Reference Upper Threshold (dBm) = Input Power Reference Value (dBm) + 3dB l Input Power Reference Lower Threshold (dBm) = Input Power Reference Value (dBm) - 5dB To ensure that the U2000 displays a correct power state, you are recommended to set the Input Power Reference Upper Threshold (dBm) and Input Power Reference Lower Threshold (dBm) fields.

(6) Set Output Power Reference Value (dBm). Output Power Reference Value (dBm) must be set according to the output optical power specification of the optical module at the specified optical interface. The U2000 compares the obtained Output Power (dBm) with the preset Output Power Reference Value (dBm) to determine whether the output optical power is abnormal. If Output Power (dBm) deviates from Output Power Reference Value (dBm) by less than 2 dB, the U2000 displays Output Power State as normal; if the deviation is 2 dB to 4 dB, the U2000 displays Output Power State as Warning Alert; if the deviation is greater than 4 dB, the U2000 displays Output Power State as Critical Alert. (7) To save the customized template, choose Filter by Template > Save As. In the displayed dialog box, enter the template name and then click OK. The Result dialog box is displayed. Click Close. 3.

Issue 01 (2011-10-20)

Check the value of the Input Power State field. If the field is displayed as Critical Alert or Warning Alert, it indicates that the optical power of the specified optical port is outside of the normal range. In this case, proceed to analyze the problem. That is, rectify this problem in the same way as used to rectify such a problem by using the Web LCT.


251



TIP

You can also compare Input Power(dBm) of each optical port with Input Power Lower Threshold (dBm) and Input Power Upper Threshold(dBm). If the input optical power is outside of the range of Input Power Lower Threshold(dBm) and Input Power Upper Threshold(dBm), it indicates that the input optical power is abnormal.

4.

Check Output Power(dBm) for each optical port on the board according to the value of Output Power State. The output optical power must be within the specified range. If the output optical power at an optical port is outside of the specified range, replace the optical module at the optical port.


The receive optical power is normal but the LDGF board reports an OTU1_LOF alarm. In the case of a board with the dual fed and selective receiving function, if only optical port 2 or 4 is in normal state before the board is configured with protection, the ESC communication will be unavailable.

l

The receive optical power is normal but the LDGF board reports a LINK_ERR alarm. If an FE interface on the LDGF board does not access any service and the channel use status is set as used, the board will report a LINK_ERR alarm.

l

The receive optical power is normal but an OTU board reports an REM_SF alarm. If the OTU board at the remote end does not access any service on the client side, the OTU board at the local end will report an REM_SF alarm.

l

Commission optical power If a query operation shows that the optical power is abnormal, you may need to commission the optical power at the site. In this case, see this section to learn the method and procedure for commissioning optical power.


7.5 Querying Bit Errors Before and After FEC The count of bit errors before and after FEC is a key specification for measuring the system operation quality. Issue 01 (2011-10-20)


252



Prerequisite The performance monitoring function must be enabled and the current NE time must be within the specified performance monitoring time range. FEC Working State of an OTU board must be set to Enabled.


Precautions

CAUTION During the deployment commissioning, ensure that the bit errors before FEC meet the customer requirements and the bit errors after FEC is zero by taking into account the line attenuation and the configurations.


In the NE Explorer, select the desired board.

2.

Choose Performance > Current Performance from the Function Tree.

3.

In Performance Event Type, select the desired item and then click Query.

4.

View the current values in Performance Event and Performance Value.


Choose Performance > Browse WDM Performance from the Main Menu of the U2000, and then click the Current Performance Data tab.

2.

Select the option from the drop-down list next to Monitored Object Filter Criteria.

3.

In Monitor Period, select 15-Minute or 24-Hour.

4.

Select one or multiple boards in the left pane, and click the

5.

Click the Count tab. Select options under Performance Event Type, and select Display Zero Data for the Display Options.

6.

Click Query to query the performance value for bit error on the NE side.

7.

In the Operation Result dialog box, click Close to finish the operation.

.


Set performance thresholds for a specified board When an NE detects that a certain performance value exceeds the specified threshold, the NE reports a corresponding performance event. See this section to learn how to change the performance threshold of a specified board.

l Issue 01 (2011-10-20)

Set performance monitoring parameters of a board Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

253



The Web LCT/U2000 can monitor the performance of all boards on a network. The automatic reporting of detected performance values, however, is disabled by default. You can change the default setting as required. l

Set performance monitoring parameters of an NE Set the performance monitoring parameters of a specified NE properly and then enable the NE performance monitoring function. By doing so, you can obtain detailed description of performance records during the operation of the NE. This facilitates monitoring of the existing services and the equipment status.

l

Reset the performance register of a board After a network test or fault recovery, you need to reset the performance register of a board as required before the board is put into operation. This is to start a new performance monitoring period.


7.6 Viewing Current Alarms on an NE and Removing Abnormal Alarms Viewing the current alarms on an NE helps you to intuitively and quickly locate an exception on the network. This helps you to identify a fault on the network.

Prerequisite The NMS computer must communicate with the NE properly.

Tools, Equipment, and Materials Web LCT or U2000. When you need to view alarms on all NEs on the network, use the U2000.


Query the current alarms on an NE. (1) In the NE Explorer, select the NE and choose Alarm > Browse Alarms from the Function Tree. (2) In the displayed window, click the Browse Current Alarms tab.

2.

Analyze and handle the reported abnormal alarms. In the case of on-site maintenance, handle Critical and Major alarms before handling other abnormal alarms. Analyze and handle alarms one by one according to the network situations. According to network conditions, certain alarms are reported inevitably, whereas certain alarms cannot be reported. For example, in general no service is accessed on the WDM side during deployment commissioning. In this case, relevant alarms are reported inevitably. These alarms, however, are cleared automatically after real services are accessed on the client side. In the commissioning and configuration phases of deployment, you need to analyze every reported alarm. In general, focus on the following alarms:

Issue 01 (2011-10-20)


254



l Optical power low or high alarm l Temperature threshold-crossing alarm l Abnormal communication alarm l Bit error-related alarm l Abnormal service alarm To handle a reported alarm, see the Alarms and Performance Events Reference.


Query the current alarms on all NEs. (1) Click the current critical alarm indicator (red) in the upper right corner of the U2000 window. to browse the current network-wide critical alarms. NOTE

The figure in the center of the indicator indicates the number of the current critical alarms. When the indicator is surrounded by a square frame critical alarms to be acknowledged.

, it indicates that there are

(2) Click the current major alarm indicator (orange) in the upper right corner of the U2000 window to browse the current network-wide major alarms. NOTE

The figure in the center of the indicator indicates the number of the current major alarms. When the indicator is surrounded by a square frame alarms to be acknowledged.

, it indicates that there are major

(3) Click the current minor alarm indicator (yellow) in the upper right corner of the U2000 window to browse the current network-wide minor alarms. NOTE

The figure in the center of the indicator indicates the number of the current minor alarms. When the indicator is surrounded by a square frame alarms to be acknowledged.

, it indicates that there are minor

(4) Click the current warning alarm indicator (blue) in the upper right corner of the U2000 window to browse the current network-wide warning alarms. NOTE

The figure in the center of the indicator indicates the number of the current warning alarms. When the indicator is surrounded by a square frame warning alarms to be acknowledged.

2.

, it indicates that there are

Analyze and handle the reported abnormal alarms. In the case of on-site maintenance, handle Critical and Major alarms before handling other abnormal alarms. Analyze and handle alarms one by one according to the network situations. According to network conditions, certain alarms are reported inevitably, whereas certain alarms cannot be reported. For example, in general no service is accessed on the WDM side during deployment commissioning. In this case, relevant alarms are reported inevitably. These alarms, however, are cleared automatically after real services are accessed on the client side. In the commissioning and configuration phases of deployment, you need to analyze every reported alarm. In general, focus on the following alarms:

Issue 01 (2011-10-20)


255



l Optical power low or high alarm l Temperature threshold-crossing alarm l Abnormal communication alarm l Bit error-related alarm l Abnormal service alarm To handle a reported alarm, see the Alarms and Performance Events Reference.


The optical path is reachable but the NE cannot be logged in to remotely. In the case of a board with the dual fed and selective receiving function, if only optical port 2 or 4 is in normal state before the board is configured with protection, the ESC communication will be unavailable.

l

Commission optical power If a query operation shows that the optical power is abnormal, you may need to commission the optical power at the site. In this case, read this section to learn the method and procedure for commissioning optical power.


7.7 Testing Protection Switching In the commissioning or configuration phase, you can run a manual switching command to check whether protection switching can be performed normally.

7.7.1 Testing SW SNCP Switching After configuring SW SNCP protection, you can run a manual switching command to check whether the SW SNCP switching can be performed successfully.

Prerequisite The NMS computer must communicate with the NE properly. Protection groups must be configured correctly. The working and protection channels of a protection group on the network must be in normal state.


Issue 01 (2011-10-20)


256



Precautions

CAUTION In the case of revertive protection, services can be switched only to the protection channel by performing a manual switching.


In the NE Explorer, select the NE and choose Configuration > Subwavelength SNCP Service from the Function Tree.

2.

Click Query to view the values of the Channel Status and Revertive Mode fields of the working and protection cross-connections of all the existing SNCP protection groups on the NE. Regardless of the working or protection cross-connections, the value of the Channel Status field should be Normal. NOTE

If the value of the Channel Status field of a working or protection cross-connection is not Normal, check whether the channel corresponding to this cross-connection is in normal state. Proceed with the protection switching test after rectifying the fault.

3.

Right-click the desired protection group and choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time (mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE

When verifying the ODUk SNCP dual-ended switching, pay attention to the following points: l Ensure that Switching Mode is set to Bidirectional. l Ensure that both Current Channel of the local NE and that of the peer NE are the protection channel. l If manual or forced protection switching is performed, channel status can be restored only on the NE whose Switching Type is Near-End.

Issue 01 (2011-10-20)


257



NOTE

If the protection switching fails or an exception occurs in the protection switching process after you run a manual switching command, check whether the channel corresponding to the working or protection cross-connection is in normal state, and whether the protection group is in the switching state of higher priority, and whether the protection group and the working and protection crossconnections are configured properly. Proceed with the protection switching test after removing the fault.


In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click the SNCP Service Control tab.

2.

Click Query to view the status of all the existing protection groups on the NE. Regardless of the working or protection cross-connections, the value of the Channel Status field should be Normal. NOTE


3.

Click Function to display a drop-down list. Choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time(mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE

When verifying the ODUk SNCP dual-ended switching, pay attention to the following points: l Ensure that Switching Mode is set to Bidirectional. l Ensure that both Current Channel of the local NE and that of the peer NE are the protection channel. l If manual or forced protection switching is performed, channel status can be restored only on the NE whose Switching Type is Near-End. NOTE


Issue 01 (2011-10-20)


258





l

Convert a service with SNCP protection into a service with no protection A service with SNCP protection can be converted into a service with no protection.

l

WDM cross-connection configuration See this section to learn how to set the parameters used for configuring a WDM crossconnection.

l



7.7.2 Testing SNCP Switching After configuring SNCP protection, you can run a manual switching command to check whether the SNCP switching can be performed successfully.



Precautions



Issue 01 (2011-10-20)

In the NE Explorer, select the NE and choose Configuration > SNCP Service Control (SDH) from the Function Tree. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

259


2.


Click Query to view the values of the Current Status and Revertive Mode fields of the working and protection cross-connections of all the existing SNCP protection groups on the NE. Regardless of the working or protection cross-connections, the value of the Current Status field should be Normal. NOTE

If the value of the Current Status field of a working or protection cross-connection is not Normal, check whether the channel corresponding to this cross-connection is in normal state. Proceed with the protection switching test after rectifying the fault.

3.

Right-click the desired protection group and choose Manual to Working channel or Manual to Protection channel. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection Channel from the right-click menu, the protection switching should be performed successfully and the working crossconnection becomes the protection cross-connection. l After you choose Manual to Working Channel from the right-click menu, the protection switching should be performed successfully and the protection crossconnection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection Channel from the right-click menu, the protection switching should be performed successfully and the working crossconnection becomes the protection cross-connection. After the time specified in the WTR Time(mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE



In the NE Explorer, select the NE and choose Configuration > SNCP Service Control from the Function Tree.

2.



3.

Click Function to display a drop-down list. Choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive:

Issue 01 (2011-10-20)


260



l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time (mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE




l



7.7.3 Testing ODUk SNCP Switching After configuring ODUk SNCP protection, you can run a manual switching command to check whether the ODUk SNCP switching can be performed successfully.




261




In the NE Explorer, select the NE and choose Configuration > Subwavelength SNCP Service from the Function Tree.

2.

Click Query to view the values of the Channel Status and Revertive Mode fields of the working and protection cross-connections of all the existing SNCP protection groups on the NE. Regardless of the working or protection cross-connections, the value of the Channel Status field should be Normal. NOTE


3.

Right-click the desired protection group and choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time (mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE




In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. In the displayed window, click the SNCP Service Control tab.

2.

Click Query to view the status of all the existing protection groups on the NE.

Issue 01 (2011-10-20)


262



Regardless of the working or protection cross-connections, the value of the Channel Status field should be Normal. NOTE


3.

Click Function to display a drop-down list. Choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time(mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE





l




263



7.7.4 Testing Port Protection Switching In the case of intra-board 1+1 protection, optical line protection, client 1+1 protection, you can run a manual switching command in a same user interface.

Prerequisite The NMS computer must communicate with the NE properly. Protection groups must be configured correctly. The working and protection channels of a port protection group on the network must be in normal state.


Precautions



In the NE Explorer, select the NE and choose Configuration > SNCP Service Control from the Function Tree.

2.



3.

Click Function to display a drop-down list. Choose Manual to Working or Manual to Protection. Observe the changes in parameter values and determine whether protection switching can be performed successfully. When Revertive Mode of the protection group is set to Non-Revertive: l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. l After you choose Manual to Working from the right-click menu, the protection switching should be performed successfully and the protection cross-connection becomes the work cross-connection. When Revertive Mode of the protection group is set to Revertive:

Issue 01 (2011-10-20)


264



l After you choose Manual to Protection from the right-click menu, the protection switching should be performed successfully and the working cross-connection becomes the protection cross-connection. After the time specified in the WTR Time (mm:ss) field elapses, the protection cross-connection of the protection group automatically restores to the working cross-connection. NOTE



Port protection See this section to learn how to set the parameters for configuring port protection.


7.7.5 Testing ERPS Protection After completing configuration, you can verify the Ethernet ring protection switching (ERPS) protection by disconnecting involved fibers and then checking the service status on the ring network and alarm information.

Prerequisite You must be an NMS user with "NE operator" authority or higher. The Ethernet ring protection must be configured.



In the NE Explorer window, click the NE. Select the board to be tested, and choose Configuration > Ethernet Protection > ERPS Management from the Function Tree.

2.

In the lower right part of the ERPS Management window, click Query.

3.

In the query result, check whether Status of State Machine is Idle.

4.

Disconnect fibers connecting to the IN and OUT optical ports (east ports or west ports) to trigger ERPS switching.

5.

In the alarm list, check for the R_LOS alarm reported by the board, and the ERPS switching event reported by the NE.

6.

In the ERPS Management window, check whether Status of State Machine is Protection on the current NE.

Issue 01 (2011-10-20)


265



7.

Restore fiber connection. Query the alarm and performance event list. The R_LOS alarm reported by the board should be cleared. After the WTR time expires, the system should report that the ERPS status is Idle.

8.

In the ERPS Management window, check whether Status of State Machine is Idle.


7.8 Querying and Saving the Networkwide Optical Power and Alarm Data After commissioning a network, you need to query and save the optical power and alarm data of the entire network. This type of data can help you analyze and understand the operating status of the network in future.

Prerequisite The performance monitoring function must be enabled. Fiber connections must be established properly and lasers must be enabled.

Tools, Equipment, and Materials The U2000 must be used for querying the optical power and alarms of the entire network.


Query optical power networkwide. (1) Choose Configuration > Optical Power Management from the Main Menu of the U2000. (2) Select all the stations from the navigator on the left, click

.

(3) Click Query, in the Result dialog box, click Close. 2.

Check the optical power on the entire network and ensure that the optical power of all the equipment on the network is proper.

3.

Set the current optical power of the entire network to this reference value. This will facilitate future maintenance of the network. Click Reset Networkwide Reference Value. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. TIP

After all the commissioning and configuration tasks are performed during deployment, the optical power of the network obtained at the time when the network starts working is the reference value indicating the optimal performance of the network.

4.

Issue 01 (2011-10-20)

Click Save As. Select the path for saving the optical power report and enter the name for this report. After that, click Save. At this point, the optical power data of the entire network is saved on the specified path. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

266


5.


In the Main Menu, choose Fault > NE Alarm Synchronize. In the displayed NE Selector dialog box, select ROOT on the left and then click on the subnet.

to select all the NEs

NOTE

To save all the data of the current alarms, ensure that all the alarms can be displayed properly when setting alarm filter conditions.

6.

Click Save As. Select the path for saving the alarm data and enter the file name. After that, click OK. At this point, the data of the current alarms is saved on the specified path.


Check optical power of boards If the obtained optical power is outside of the normal range, see this section to learn how to rectify a problem with abnormal optical power.

l

Query current alarms on an NE and remove abnormal alarms If a query of alarms shows that abnormal alarms are generated at that time on the network, see this section to learn how to handle an abnormal alarm.


7.9 Backing Up NE Data to the NMS Server or Client You can manually back up the data of one or more NEs of the same type to an NMS server or client.

Prerequisite The path for saving the backup data and the TFTP/FTP/SFTP server must be configured and the TFTP/FTP/SFTP service must be started.

Tools, Equipment, and Materials The U2000 must be used when you back up NE data to an NMS server or client.

Precautions NOTE

Observe the following precautions when backing up NE data to an NMS server or client: l The backup operation can be performed to multiple NEs at the same time if these NEs are of the same type. l If you select a node of a certain NE type in the Navigation Tree, the Device View tab page displays the information and version information of all the NEs of this type. l The Backup Information tab page displays the information of the backup file.

Issue 01 (2011-10-20)


267




Choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.

2.

Right click the device(s) that you want to backup in the NE View table. NOTE

The Backup Information tab is unavailable when multiple devices are selected.

3.

Select Backup... to open the Backup dialog.

4.

Select the option NMS Server or NMS Client to backup the selected device information. NOTE

By default the NMS Server is selected. If the NMS Server is selected, the selected device information is stored on the NMS server.

5.

Optional: If the NMS Client is selected, click data have to be backed up.

to select the location where the device

6.

Click Start to start the backup operation for the selected device(s). On the NE View tab page, the backup progress is displayed.

7.

When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/ yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd" indicates the date when the backup is created, and "hhmmss" indicates the time when the backup is created.


Compare the methods of backing up and restoring NE data The backup or restored NE database can be saved on the SCC board, NMS server, or NMS client. Different storage locations determine different backup and restoration methods.

l

Restore NE data from the NMS server or client After backing up NE data to the NMS server or client, you can see this section to learn how to restore NE data from the NMS server or client.


Issue 01 (2011-10-20)


268


A

A Handling Common Commissioning Problems

Handling Common Commissioning Problems

This chapter describes the methods of analyzing and handling the most common problems happening in the deployment process. You need to analyze and handle problems according to actual situations. In the commissioning or configuration phase of deployment, alarms are generally generated when a problem happens. For example, alarms are generated if no service is received on the client side or if the configuration is incomplete. You need to analyze each alarm reported by equipment to determine which alarms do not reflect abnormal running status and which alarms indicate running status in the current engineering conditions. Abnormal alarms must be handled properly in the commissioning or configuration phase of deployment. Equipment may report various alarms. Different alarms have different causes. This chapter describes the common causes of the common alarms and the common methods of handling such alarms generated during deployment. There may be other causes of such alarms. Thus, analyze and handle alarms in the commissioning or configuration phase of deployment according to actual situations. For details on how to handle alarms of the OptiX OSN 1800, see the Alarms and Performance Events Reference. When reporting an alarm, the NMS also displays the position where the alarm is generated. Determine the slot, board name, and optical port where the alarm is generated according to the displayed position information. For example, 1-LDGF2-201(LP1/LP1)-OTU1:1. In the case of the LDGF2 board, 201(LP1/LP1) indicates the IN1 and IN2 optical interfaces, and 202(LP2/ LP2) indicates the IN3 and IN4 optical interfaces. The digit 1 at the end of the position information indicates the IN1 or IN3 optical port. If the digit is 2, it indicates the IN2 or IN4 optical port. That is, 1-LDGF2-201(LP1/LP1)-OTU1:1 indicates that the alarm is generated at the IN1 optical port on the LDGF2 board in slot 1. The indication of the position information for other boards is similar. A.1 The Receive Optical Power Is Normal But the LDGF Board Reports an OTU1_LOF Alarm A.2 The Receive Optical Power Is Normal But the LDGF Board Reports a LINK_ERR Alarm A.3 The Receive Optical Power is Normal But an OTU Board Reports an REM_SF Alarm A.4 The Optical Path Is Reachable But the NE Cannot Be Logged in Remotely

Issue 01 (2011-10-20)


269



A.1 The Receive Optical Power Is Normal But the LDGF Board Reports an OTU1_LOF Alarm Keywords LDGF, OTU1_LOF, LWX2 regeneration board

Symptom The receive optical power on the WDM side of the LDGF board is normal but the board reports an OTU1_LOF alarm. The LDGF board that reports an OTU1_LOF alarm works with the LWX2 regeneration board. Figure A-1 shows the network where the LDGF and LWX2 board are used. The ALS function of a laser on the LWX2 regeneration board is disabled and all lasers on this board are enabled. As shown in Figure A-1, the optical cable between the two LWX2 regeneration boards is unavailable. That is, the optical path between the two regeneration boards is absent. Thus, the downstream LWX2 regeneration board reports an R_LOS alarm. Figure A-1 LDGF board networking mode

IN1

OUT1 L D G F IN1 2

L W X 2

L W X 2

L D G OUT1 F

Cause Analysis The receive optical power on the WDM side of the LDGF board is normal but the board reports an OTU1_LOF alarm. This indicates that the frame structure of the received optical signals is invalid or the board is faulty. In general, the probability that the board is faulty is very small. Thus, you can first check whether the received optical signals are normal. As described previously, the upstream optical path is unavailable, and thus the downstream LWX2 regeneration board cannot receive valid optical signals. The lasers on the downstream LWX2 regeneration board, however, are forcibly enabled. Thus, the downstream LWX2 regeneration board transmits white light signals that have no frame structure. Thus, although optical power of the optical signals received by the LDGF, the LDGF board reports an OTU1_LOF alarm because the received optical signals have no frame structure.

Procedure After an analysis, this is normal for the LDGF board to an OTU1_LOF alarm in the current engineering situation. When the optical cable between the two LWX2 regeneration boards is Issue 01 (2011-10-20)


270



installed and the optical path between them are present, the OTU1_LOF alarm will be cleared automatically.

Reference Information None.

A.2 The Receive Optical Power Is Normal But the LDGF Board Reports a LINK_ERR Alarm Keywords LDGF, LINK_ERR

Symptom The receive optical power on the WDM side of the LDGF board is normal, the ETH port, however, reports the LINK_ERR alarm. No service gains access to the ETH port on the LDGF board where the alarm is reported.

Cause Analysis The LINK_ERR alarm indicates that valid links between two data ports fail to be established, however, the receive optical power on the WDM side of the LDGF board is normal and the line is normal. No service gains access to the ETH port on the LDGF board, and therefore valid links fail to be established and the LINK_ERR alarm is reported.

Procedure Under the current engineering condition, the situation is normal. 1.

If the ETH port on the LDGF board is planned to access services in the network planning, the alarm is cleared automatically after the ETH port accesses services normally.

2.

If the ETH port on the LDGF board is not planned to access services in the network planning, set the ETH channel to unused so that the channel does not detect the alarms that are irrelevant with normal network operation.


A.3 The Receive Optical Power is Normal But an OTU Board Reports an REM_SF Alarm Issue 01 (2011-10-20)


271



Keywords OTU, REM_SF, client-side service

Symptom As shown in Figure A-2, the receive optical power of the OTU board is normal but the client side of the OTU board at station A reports the REM_SF alarm. Figure A-2 Schematic diagram of the OTU board reporting the REM_SF alarm RX

TX

IN1

TX

O T OUT1 U

RX

OUT1 O T U IN1

A

B

Cause Analysis The REM_SF alarm indicates that the receive signals on the client side of the OTU board at the opposite station fail. At the deployment commissioning phase, no service gains access to the client side of the OTU board at station B, and therefore the alarm is reported.

Procedure After services gain access to the client side of the OTU board at station B, the alarm is cleared.


A.4 The Optical Path Is Reachable But the NE Cannot Be Logged in Remotely Keywords LDGF2, NE unreachable, remote login

Symptom The communication between stations A and B is achieved through only the ESC provided by the LDGF2 board. Because the optical fibers are not connected at the deployment commissioning phase, the optical paths of IN1/OUT1 on the LDGF2 board are unavailable. The optical paths Issue 01 (2011-10-20)


272



of IN2/OUT2, however, are normal. See Figure A-3. Station B cannot be logged in remotely at station A. Figure A-3 Schematic diagram of the network of the LDGF2 board IN1

OUT1 L D IN1 G F OUT2 2

L D OUT1 G IN2 F 2 OUT2

IN2

B

A

Cause Analysis The LDGF2 board receives ESC overhead bytes through the channels of IN1/OUT1. The optical paths of IN1/OUT1 on the LDGF2 board are unavailable. Therefore, the ESC overhead bytes fail to be received, communication between NEs fails to be established, and the NE fails to be logged in remotely.

Procedure Under the current engineering condition, establish normal communication routes according to the network planning: l

Configure intra-board 1+1 protection on the LDGF2 boards at stations A and B respectively to establish normal communication between the two stations by using the channels of IN2/ OUT2.

l

Restore the fiber connections.

Reference Information In the case of the OTU boards with the dual fed and selective receiving function, before the protection is configured, overhead bytes are received through only the channels of IN1/OUT1 or IN3/OUT3. If the optical paths of IN1/OUT1 or IN3/OUT3 are unavailable, the ESC communication fails even if the optical paths of IN2/OUT2 or IN4/OUT4 are normal. After the protection is configured, the ESC communication is normal even if only one channel is normal.

Issue 01 (2011-10-20)


273


B

B Reference Operations for the Commissioning and Configuration

Reference Operations for the

Commissioning and Configuration This chapter lists the reference operations for the commissioning and configuration. You can perform proper operations according to the network condition. B.1 Creating a VLAN Group The VLAN group can extend the number of supported VLAN flows. You can follow the procedure described in this section to create a VLAN group. B.2 Configuring the Aging Time for MAC Addresses You can configure the aging time for MAC addresses, to realize the dynamic address aging function. If the MAC addresses that do not appear again in the transport network during the aging time, the system considers that no information needs to be sent to these MAC addresses. The MAC addresses are deleted from the MAC address table, so that the MAC address table can contain more MAC addresses. B.3 Configuring Port Mirroring You can configure port mirroring to analyze only packets for mirrored ports. In this way, you can monitor all mirrored ports. This helps you to manage the ports. B.4 Obtaining NE IP Addresses at the Site In the case of onsite commissioning, if the U2000 or Web LCT is unavailable, you can obtain the IP address of an NE by running a command directly in the Windows operating system. B.5 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. Creating NEs one by one is applicable no matter what way of communication an NE adopts. The NEs that use serial ports to communicate do not support the NE search function and you must create them one by one. B.6 Checking the NE Software Version This topic describes how to check the NE software version. B.7 Creating an NE User To ensure NE data security, only the users with NE user authority can log in to the NEs. An NE user is able to perform operations on the NEs according to the assigned authority. The U2000/ Web LCT administrator is advised to create NE users before configuring services. B.8 Switching a Logged-In NE User Issue 01 (2011-10-20)


274



During a new deployment, after the root/lct NE user creates the NE, this user can create another NE user. You can log in to the NE with the new NE user name. B.9 Modifying the Optical NE Name You can change the optical NE name at any time as required with no effect on the running of the NE. B.10 Modifying GNE Parameters During the network optimization and adjustment, you may need to change the GNE type or the communication address. B.11 Changing the GNE for NEs When the number of NEs managed by a certain GNE exceeds a certain number (the number is usually 50 and varies depending on different types of equipment), change the GNE for certain NEs so that the communication between the U2000 and the NEs is not affected. B.12 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. B.13 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. B.14 Deleting NEs If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes all information of the NE from the U2000 but does not affect the running of the equipment. B.15 Enabling the 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 gateway NE, the gateway NE 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. B.16 Configuring the IP Static Route for an NE When dynamic routes fail to meet the planning requirements, create the corresponding static IP routes manually. B.17 Querying the OSPF Protocol Status Enable the OSPF protocol so that the routing information on the gateway NE can be automatically diffused to other NEs. B.18 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. B.19 Configuring Boards In the NE Panel, you can add a board and set port attributes for the board. B.20 Adding Ports Client-side ports and line-side ports of some OTU boards support color light and colorless light. You need to add different ports on the U2000 according to the SFP optical module used on the equipment. B.21 Deleting Ports This section describes how to delete a port. B.22 Changing Port Types Issue 01 (2011-10-20)


275



The client-side and line-side ports of the OTU board in the OptiX OSN 1800 equipment can be configured as color ports or grey ports. The port type needs to be set according to type of the optical modules or electrical SFP modules used in the equipment. B.23 Configuring the Standard NTP Key On the U2000, you can use the standard network time protocol (NTP) service to automatically synchronize the NE time with the standard NTP server time. To ensure that a reliable server is accessed, the NTP authentication function must be started. In this case, you need to set the key and password, which are authenticated together to check whether the server is reliable. B.24 Synchronizing the NE Time with the Standard NTP Server Time You can use the standard network time protocol (NTP) service to automatically synchronize the NE time with the standard NTP server time. B.25 Setting Automatic Synchronization of the NE Time with the NMS Time This section describes how to set automatic synchronization of the NE time with the NMS time. After you set automatic synchronization of the NE time with the NMS time, the NE time is automatically synchronized with the NMS time at specified intervals. B.26 Performance Management To ensure the normal functioning of the network, the network management and maintenance personnel should periodically check and monitor the network by taking proper performance management measures. B.27 Modifying the Services Configuration After a service is configured, you can modify or delete the configuration data of the service based on the following task sets. B.28 Switching the Working Mode of the LQM2 The default working mode of the LQM2 board is 2LQM Mode. When the working mode is switched to AP8 Mode, you need to configure the board and add the IN2/OUT2 optical port according to this section. B.29 Backing Up and Restoring the NE Data For the security of the NE data, you can back up and restore the NE data. B.30 Creating Fiber Connections in List Mode In Fiber/Cable Management, you can manage the fiber connections between NEs and inside NEs in a unified manner. Compared with the graphic mode, the creating fiber connections in the list mode is not visual. Hence, the list mode is applicable to the scenario where you create a few fiber connections only.

Issue 01 (2011-10-20)


276



B.1 Creating a VLAN Group The VLAN group can extend the number of supported VLAN flows. You can follow the procedure described in this section to create a VLAN group.

Prerequisite None.

Tools, Equipment, and Materials U2000 or Web LCT

Background Information The configuration principles are as follows: l

The VLAN group is of port attributes. It is valid only at the service input port. Both the PORT and VCTRUNK ports can be set as a VLAN group.

l

The configuration of a VLAN group is based on the C-VLAN.

l

When you create a VLAN group, if a service is configured for a member VLAN (a noninitial VLAN in the VLAN group), the VLAN group cannot be created. The service mentioned includes services that involve VLAN configuration, such as EPL service and flow configuration.

l

When you create a VLAN group, if a service is configured for the initial VLAN, the VLAN group can be created, but the service may be transiently interrupted.

l

Eight VLAN groups are supported by one port. The eight VLAN groups at the same port must have different VLAN values.

l

After you create the port VLAN group, if the VLAN ID of the services to be created is within the VLAN group, the services must be created based on the initial VLAN ID. If the VLAN ID is not within the port VLAN group, the services are unrestricted.

CAUTION Creating a VLAN group may affect the services.

Procedure on the U2000 or Web LCT Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click the VLAN Group tab. Step 3 Click New. In the dialog box displayed, configure the VLAN group parameters. l The value of Initial VLAN is in the range of 1 to 4095. The formula is as follows: Initial VLAN = p x 2n. n is an integer from 0 to 12. p is an integer from 1 to 2m. m + n <= 12. l The formula of VLAN Group Member Count depends on the value of the Initial VLAN. If the value of Initial VLAN is 1, VLAN Group Member Count = 2n - 1. If the value of Issue 01 (2011-10-20)


277



Initial VLAN is an integer other than 1, VLAN Group Member Count = 2n. The value of n is the same as that in the formula of the Initial VLAN. l For example, – If the value of n is 0, a VLAN group is actually a single VLAN. The value of VLAN Group Member Count is in the range of 1 to 4095. – If the value of n is 6 and the value of m is 1, the value of VLAN Group Member Count is in the range from 64 to 127. Step 4 Click Apply. A confirmation dialog box is displayed. Click OK. and the configuration is complete. The created port VLAN group is displayed in the user interface. ----End

B.2 Configuring the Aging Time for MAC Addresses You can configure the aging time for MAC addresses, to realize the dynamic address aging function. If the MAC addresses that do not appear again in the transport network during the aging time, the system considers that no information needs to be sent to these MAC addresses. The MAC addresses are deleted from the MAC address table, so that the MAC address table can contain more MAC addresses.

Prerequisite None.


Background Information If the aging time is too long, the MAC address table may save many outdated MAC address items. This may use up the resources of the MAC address table. As a result, the MAC address table may not be updated according to the change in the network. If the aging time is too short, the effective MAC address items may be deleted. As a result, packets that are broadcasted cannot find the destination MAC address and the performance of the network is affected.

Procedure on the U2000 or Web LCT Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree. Step 2 Double-click MAC Address Aging Time and the MAC Address Aging Time dialog box is displayed. Enter the value of the aging time. NOTE

MAC Address Aging Time supports three time units, including minute, hour, and day. The value ranges from 1 to 120. When the unit of the MAC Address Aging Time is set to day, the valid range is 1-12.

Issue 01 (2011-10-20)


278



Step 3 Click OK and then click Apply. ----End

B.3 Configuring Port Mirroring You can configure port mirroring to analyze only packets for mirrored ports. In this way, you can monitor all mirrored ports. This helps you to manage the ports.

Prerequisite The mirror listener port should contain no Ethernet service, and has not be aggregated.


Precautions NOTE

A mirror listener port cannot be configured with any service. The concatenation port mirroring function is not supported. For example, if VCTRUNK2 port is configured to listen to VCTRUNK1 port, you cannot configure any other ports to listen to VCTRUNK2 port.

Procedure on the U2000 or Web LCT Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > Port Mirroring from the Function Tree. Step 2 Optional: Click Query to query the status of port mirroring that you configure. Step 3 Click New and the Port Mirror Management window is displayed. Step 4 Set Mirror Listener Port, Uplink Listened Port, and Downlink Listened Port. NOTE

l You can set Uplink Listened Port or Downlink Listened Port, and the two ports cannot be set at the same time. l Do not select a port where services exist from the Mirror Listener Port drop-down list. Otherwise, creating port mirroring fails.

Step 5 Click OK. ----End

B.4 Obtaining NE IP Addresses at the Site In the case of onsite commissioning, if the U2000 or Web LCT is unavailable, you can obtain the IP address of an NE by running a command directly in the Windows operating system.

Prerequisite The NMS computer must run on Windows and must be connected to the NE directly by using an Ethernet cable. Issue 01 (2011-10-20)


279



Tools, Equipment, and Materials None.

Procedure Step 1 Set the IP address of the NMS computer to ensure that the NMS computer is located on the 129.9 network segment. For example, set the IP address to 129.9.0.254. Step 2 On the Windows, choose Start > Run and then enter cmd in the command line interface to enter the DOS system. In the DOS system, enter ping 129.9.255.255. Step 3 When the timeout response is complete, enter arp -a. Step 4 The IP address of the NE is displayed in the Internet Address column.

----End

B.5 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. Creating NEs one by one is applicable no matter what way of communication an NE adopts. The NEs that use serial ports to communicate do not support the NE search function and you must create them one by one.

Prerequisite l

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

l

The NE Explorer instance of the NEs must be created.

Tools, Equipment and Materials U2000 or Web LCT Issue 01 (2011-10-20)


280



Background Information For U2000: l

First create a GNE, and then create a non-gateway NE.

l

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.


Right-click in the blank space of the Main Topology and choose New > NE... from the shortcut menu. The Create NE dialog box is displayed.

2.

Select required NE from tree structure at left hand pane.

3.

Complete the following information: ID, Extended ID, Name and Remarks.

4.

To create a GNE, proceed to 5. To create a non-gateway NE, proceed to 6.

5.

Select Gateway from the Gateway Type drop-down list and set the IP address.

6.

Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which this NE is associated, from the Gateway drop-down list.

7.

Select the optical NE in Associated ONE to which the WDM NE is associated.

8.

Enter the NE User and Password. NOTE

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

9.

Click OK, the cursor is displayed as "+", click on the blank space of the physical view and the NE is created.

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


Click Add NE in the NE list. The Add NE dialog box is displayed.

2.

Set the NE Type to Europe, enter the NE ID and Extended ID.

3.

Select Gateway Type and set related parameters. l If the gateway type is IP Gateway, set IP Address and Port. l If the gateway type is Serial Port, set Port and Baud Rate. l If the gateway type is SSL Gateway, set IP Address and Port.

4.

Enter the User Name and the Password. NOTE

The default user name is lct and the default password is password.

5.

Click OK. One entry is added in the NE list. Usually the NE communicates normally and is in the Logged In state.

Postrequisite After an NE is created, if you fail to log in to the NE, possible causes are listed as follows: Issue 01 (2011-10-20)


281



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.

l

The password for the NE user is incorrect. Enter the correct password for the NE user.

l

The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

B.6 Checking the NE Software Version This topic describes how to check the NE software version.

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

Tools, Equipment and Materials U2000 or Web LCT

Background Information The NE software version refers to the version of the SCC board of the NE. NOTE

The SCC board refers to the system control and communication unit. The SCC board interoperates with the U2000 to manage the boards of the equipment and realize the communication between the equipment.


In the main topology, double-click the desired NE. The NE panel is displayed.

2.

In the Slot Layout, Right-click the SCC board and then choose SCC Version from the shortcut menu.

3.

In the Information dialog box, view the NE software version.

4.

Click OK.


In the Slot Layout, Right-click the SCC board and then choose SCC Version from the shortcut menu.

2.

In the dialog box, view the NE software version.

3.

Click OK.

B.7 Creating an NE User To ensure NE data security, only the users with NE user authority can log in to the NEs. An NE user is able to perform operations on the NEs according to the assigned authority. The U2000/ Web LCT administrator is advised to create NE users before configuring services.

Prerequisite l Issue 01 (2011-10-20)

You must be an NM user with "NE administrator" authority or higher. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

282


l


You must log in the NE to create an NE user.


Background Information The default NE user has the monitor level authority. To ensure NE data security, it is recommended that you assign NE users with different authorities as required.

Procedure on the U2000 Step 1 Choose Administration > NE Security Management > NE User Management from the Main Menu. Step 2 In the NE list on the left, select an NE and click indicating that the operation is successful. Click Close.

. The Result dialog box is displayed,

Step 3 Click Add and the Add NE User dialog box is displayed. Step 4 Enter the NE user name in the NE User field. NOTE

The NE user name must contain letters, or it can be a combination of letters, symbols and numerals. The NE user name contains at least 4, but not more than 16 characters.

Step 5 Select the User Level as needed. Step 6 In the NE User Flag field, select a user type according to the type of the terminal through which the user logs in to the NE. Step 7 Enter the password in the New Password field and enter it again in the Confirm Password field. NOTE

The password is a string of 6-16 characters. It can consist of letters, symbols and numerals, and must contain at least one letter and one numeral.

Step 8 In the NE Name field, select the NEs that this NE user is allowed to manage. Step 9 Click OK. Step 10 Click Query, and the Result dialog box is displayed. Click Close. All created users of the NE are displayed in NE User Management Table. ----End

Procedure on the Web LCT Step 1 In the NE Explorer, select the NE and choose Security > NE User Management from the Function Tree. Step 2 Click Create and the Add NE User dialog box is displayed. Step 3 Enter the NE user name in the NE User field. Issue 01 (2011-10-20)


283



Step 4 Select the User Level as needed. Step 5 Enter the password in the New Password field and enter it again in the Confirm Password field. NOTE

You also need to set the Whether the password is allowed to be modified immediately parameter. The password is a string of 6-16 characters. It can consist of letters, symbols and numerals, and must contain at least one letter and one numeral.

Step 6 Click OK. Step 7 Click Query, and the Operation Result dialog box is displayed. Click Close. All created users of the NE are displayed in NE User Management Table. ----End

B.8 Switching a Logged-In NE User During a new deployment, after the root/lct NE user creates the NE, this user can create another NE user. You can log in to the NE with the new NE user name.

Prerequisite l

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

l

The NE user must be created.

Background Information An NE user cannot log in to or manage an NE at the same time. After you use an NE user to log in to an NE through a U2000/Web LCT server, if you use the same NE user to log in to the same NE through another U2000/Web LCT server, the NE user is forced to log out from the first U2000/Web LCT server.



Choose Administration > NE Security Management > NE Login Management from the Main Menu, click the NE Login Management tab.

2.

Select the required NE from the NE list, and click

.

NOTE

When this button is used for the first time, or the configuration data is changed, or the selected object on the Object Tree on the left is changed, this button becomes in a red frame.

3.

Click Query to query the current NE user.

4.

In the NE Login Management Table, select the NE and click Switch NE User. In the Switch Current NE User dialog box, enter User and Password, and set Offline Switching.

Issue 01 (2011-10-20)


284



NOTE

If Offline Switching is selected, the system does not check the user name and password, and thus later login of the NE may fail, which causes the NE unreachable by the NMS. Therefore, it is recommended not to select Offline Switching.

5.

Click OK.


In the NE List, select one or more NEs that are logged in and click NE Logout. The NE status becomes Not Logged In.

2.

Click NE Login. The NE Login dialog box is displayed.

3.

Enter the User Name and the Password.

4.

Click OK. In the NE List, the Login Status changes to Logged In.

B.9 Modifying the Optical NE Name You can change the optical NE name at any time as required with no effect on the running of the NE.


Tools, Equipment and Materials U2000

Procedure 1.

Right-click an NE on the Main Topology and choose Object Attributes from the shortcut menu. The Attribute dialog box is displayed.

2.

In the NE Attribute tab, enter the new optical NE name and click OK.

3.

After the optical NE name is changed successfully, the optical NE is displayed by the new name on the Main Topology. NOTE

An NE name can contain a maximum of 64 letters, symbols, and numerals, but cannot contain the following special characters: | : * ? " < >.

B.10 Modifying GNE Parameters During the network optimization and adjustment, you may need to change the GNE type or the communication address.

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

Tools, Equipment and Materials U2000 Issue 01 (2011-10-20)


285



Precautions

CAUTION This is a potential service affecting operation. Specifically, it may interrupt the communication between a GNE and the U2000, and the communication between the GNE and the non-gateway NEs that are managed by the GNE. NOTE

l It is not recommended to change the Port No.. l In the case of IP GNE, make sure that the IP address of the GNE is in the same network segment as the IP address of the U2000. When the U2000 server and the GNE are in different network segments, you need to set the network port attributes of the router through which the U2000 server and the GNE are connected. In this way, the U2000 can log in to the GNE.


Choose Administration > DCN Management from the Main Menu.

2.

Close the displayed Filter NE dialog box. Click the GNE tab.

3.

Select the GNE to be modified in the displayed Filter GNE dialog box. The NE is shown in list of GNE tab.

4.

Select the NE in the list, right-click and choose Modify GNE from the shortcut menu.

5.

In the Modify GNE dialog box displayed, set the parameters.

6.

Click OK. In the Warning dialog box that is displayed, click OK.

B.11 Changing the GNE for NEs When the number of NEs managed by a certain GNE exceeds a certain number (the number is usually 50 and varies depending on different types of equipment), change the GNE for certain NEs so that the communication between the U2000 and the NEs is not affected.



Precautions

CAUTION This operation may interrupt the NE communication.

Issue 01 (2011-10-20)


286



Procedure 1.

In the Main Topology view, choose Administration > DCN Management from the Main Menu.

2.

Select an NE to be modified in the displayed Filter NE dialog box. The NE is shown in the list of the NE tab.

3.

Select the NE in the list. Double-click the Primary GNE1 field and select a GNE.

4.

Click OK.

5.

Click Refresh in the list window.

B.12 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.



Precaution

CAUTION This operation may interrupt the service.

Procedure 1.

In the Main Topology view, choose Administration > DCN Management from the main menu.

2.

Close the displayed Filter NE dialog box. Click the GNE tab.

3.

Select the GNE to be modified in the displayed Filter NE dialog box. The NE is shown in list of GNE tab.

4.

Right-click the GNE that you want to change in the list, and choose Delete GNE from the shortcut menu. Click OK in the Confirm and Reconfirm dialog box. Click Close in the Result dialog box.

Follow-up Procedure After changing the GNE to a normal NE, modify the attributes of the NE that uses the GNE and select another GNE.

Issue 01 (2011-10-20)


287



B.13 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.



Procedure 1.

In the Main Topology view, choose Administration > DCN Management from the main menu.

2.

Select an NE to be modified in the displayed Filter NE dialog box. The NE is shown in the list of the NE tab.

3.

Select the NE in the list, Right-click a normal NE under the NE Name field and choose Change to GNE from the shortcut menu.

4.

In the Change to GNE dialog box, select the Gateway Type, and enter the IP Address or NSAP Address.

5.

Click OK. Click OK in the Warning dialog box. Click Close in the Result dialog box. NOTE

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

B.14 Deleting NEs If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes all information of the NE from the U2000 but does not affect the running of the equipment.

Prerequisite You must be an NM user with "NM maintainer" authority or higher. Fibers and cables connected to the NE must be deleted.


Background Information When the NE is not logged in, you can delete the NE on the U2000.

Procedure on the U2000 1. Issue 01 (2011-10-20)

Delete a single WDM NE. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

288



(1) Choose an optical NE in the Main Topology. Right-click the NE in the left pane and then choose Delete from the shortcut menu. (2) In the Confirm dialog box that is displayed, click Yes. 2.

Delete NEs in batches. (1) Choose Configuration > NE Configuration Data Management from the Main Menu. The NE Configuration Data Management window is displayed. . The Configuration Data (2) In the left-hand pane, select multiple NEs and click Management List pane displays the configuration data of all the selected NEs. (3) Select the NEs to be deleted, right-click and choose Delete from the shortcut menu. The Delete the NE dialog box is displayed. (4) Click OK.


In the NE List, select the NE you wish to delete, and click Delete NE.

2.

Click OK.

B.15 Enabling the 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 gateway NE, the gateway NE 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.


Background Information When the U2000 and the gateway NE are directly connected through LAN and the IP addresses of the U2000 and the gateway NE are in the same network segment, when the remote NEs connect to the gateway NE through fibers, and when the IP addresses of the remote NEs, the gateway NE, and the U2000 are in the same subnet, there are requirements that the U2000 accesses the NEs on the entire network through the gateway NE and the upper layer application requirement of accessing remote NEs based on the IP network layer. To meet the upper layer application requirement of accessing remote NEs based on the IP network layer, you need to enable the proxy ARP of the gateway NE.

Procedure Step 1 In the NE Explorer, click the NE. Choose Communication > IP Stack Protocol Management from the Function Tree. Click the Proxy ARP tab. Step 2 Optional: Click Query. Step 3 Click Value and select Disabled or Enabled from the drop-down list. Step 4 Click Apply. Click Close in the Operation Result dialog box. ----End Issue 01 (2011-10-20)


289



Follow-up Procedure After you enable proxy ARP, you need to create a static route for each NE.

B.16 Configuring the IP Static Route for an NE When dynamic routes fail to meet the planning requirements, create the corresponding static IP routes manually.

Prerequisite You must be an NM user with "NE operator" authority or higher. The user must log in to the NE.

Procedure Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Click New. The system displays the Create an IP Route dialog box. Step 3 Set the parameters of the static IP route.


Parameters

Issue 01 (2011-10-20)

Parameter

Value Range

Default Value

Description

Destination Address

-

-

You can set this parameter to an IP address or an IP address range.

Subnet Mask

-

-

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


290



Parameter

Value Range

Default Value

Description

Gateway

-

-

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

NOTE

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

B.17 Querying the OSPF Protocol Status Enable the OSPF protocol so that the routing information on the gateway NE can be automatically diffused to other NEs.


Background Information The OSPF protocol is enabled by default.

Procedure Step 1 In the NE Explorer, click the NE. Choose Communication > IP Stack Protocol 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

Follow-up Procedure If the OSPF protocol is incorrect, please contact Huawei engineers to adjust the OSPF protocol parameters used by the NEs.

B.18 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.

B.18.1 Configuring the NE Data Manually By configuring NE data manually, you can configure the board slot information of an NE. Issue 01 (2011-10-20)


291



Prerequisite l

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

l

The NE must be created successfully.



Double-click the optical NE with unconfigured NE on the Main Topology. Then, doubleclick the unconfigured NE in the left-hand pane and the NE Configuration Wizard dialog box is displayed.

2.

Select Manual Configuration and click Next. The Confirm dialog box is displayed, indicating that manual configuration clears the data on the NE side.

3.

Click OK. The Confirm dialog box is displayed, indicating that manual configuration interrupts the service on the NE.

4.

Click OK. The Set NE Attribute dialog box is displayed.

5.

Optional: If you need to modify the NE Attribute, set NE Name, Equipment Type, NE Remarks, Shelf Type, and and so on.

6.

Click Next, and the NE slot window is displayed.

7.

Optional: Click Query Logical Information to query the logical boards of the NE.

8.

Optional: Click Query Physical Information to query the physical boards of the NE.

9.

Optional: Right-click on the slot to add a board.

10. Click Next to display the Send Configuration window. 11. Select Verify and Run as required and click Finish. NOTE

Verification involves running the verification command. Click Finish to deliver the configuration to the NE and complete the basic configurations for the NE. After the verification is successful, the NE starts to work normally.

12. On the Main Topology, double-click the optical NE where the NE configured previously is located. select the NE in the left pane of the window to view the board information of the NE. If the configured board information of the NE is displayed in the right pane, it indicates that the NE is configured successfully.

B.18.2 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.



292



Procedure 1.

In the Main Menu, choose Configuration > NE Configuration Data Management.

2.

. In Configuration Data In the left topology tree, select a created NE and click Management List, select an NE whose NE Status is Unconfigured.

3.

Click Upload. The Confirm dialog box is displayed. Click OK to start the upload.

4.

When the upload is complete, the Operation Result dialog box is displayed. Click Close.

B.19 Configuring Boards In the NE Panel, you can add a board and set port attributes for the board.

B.19.1 Adding Boards When manually configuring the NE data, you need to add boards on the NE Panel/Slot Layout.

Prerequisite l

For U2000, You must be an NM user with "NE operator" authority or higher.

l

The NE must be created.

l

There must be idle slot on the NE Panel Slot Layout.


Background Information The physical boards are the actual boards inserted in the shelf. A logical board refers to a board that is created on the U2000 or Web LCT. After a logical board is created, you can configure the relevant services. If the corresponding physical board is online, the configured services can be available.


In the Main topology, double-click the icon of the NE to open the NE Panel.

2.

Select the NE to be added in the left pane on the NE Panel after performing the preceding operation and choose the desire shelf.

3.

Right-click the selected idle slot. Select the board you want to add from the list.


In the NE Explorer, click Slot Layout.

2.

Select the shelf, right-click the selected idle slot. Select the board you want to add from the list. NOTE

For Web LCT, click Add Physical Boards. All the slots in which physical boards are configured, and the system automatically creates corresponding logical boards.

Issue 01 (2011-10-20)


293



B.19.2 Deleting Boards To modify the network configuration or the NE configuration, you may need to delete the boards from the NE Panel or Slot Layout.

Prerequisite l

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

l

The services and protection groups must be deleted.



Double-click the icon of the NE to open the NE Panel and choose the desire subrack.

2.

Right-click the board you want to delete and choose Delete from the shortcut menu. NOTE

When you delete the board, the inactive single-station optical cross-connections are also deleted.

3.

Click OK in the Delete Board dialog box.

4.

Click OK to delete the board.


In the NE Explorer, click Slot Layout. Click required subrack on which board you want to delete is present.

2.

Right-click the board you want to delete and choose Delete from the shortcut menu. NOTE

When you delete the board, the inactive single-station optical cross-connections are also deleted.

B.20 Adding Ports Client-side ports and line-side ports of some OTU boards support color light and colorless light. You need to add different ports on the U2000 according to the SFP optical module used on the equipment.

Prerequisite You must be an NM user with "NE operator" authority or higher. There are client-side ports or line-side ports that are not added on the U2000.



294



Context By default, each board is added with client side ports. To add ports, you need to delete the client side ports that are added by default on the U2000.


In the NE Explorer, right-click the board and then choose Path View.

2.

Right-click a blank space on the right of the Path View window, and then choose Add Port. The Add Port dialog box is displayed.

3.

Select the port and port type. Click OK.

B.21 Deleting Ports This section describes how to delete a port.

Prerequisite You must be an NM user with "NE operator" authority or higher. No service or protection has been configured at the port to be deleted.



In the NE Explorer, right-click a desired board, and then choose Path View.

2.

Select a port that you want to delete, right-click the port, and choose Delete Port.

B.22 Changing Port Types The client-side and line-side ports of the OTU board in the OptiX OSN 1800 equipment can be configured as color ports or grey ports. The port type needs to be set according to type of the optical modules or electrical SFP modules used in the equipment.

Prerequisite You must be an NM user with "NE operator" authority or higher. No service or protection has been configured at the port whose type is to be changed.


Procedure on the U2000 or Web LCT 1. Issue 01 (2011-10-20)

In the NE Explorer, right-click a desired board, and then choose Path View. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

295


2.


Select a port whose type you want change, right-click the port, and choose Modify Port from the shortcut menu. The Modify Port dialog box is displayed, and set Type to the desired port type. NOTE

If you need to modify the client-side port to Electrical Port, you must first delete the port, and then add the port. Otherwise the port cannot be modified successfully.

3.

In the displayed dialog box, select a new port type and click OK.

4.

Optional: In Path View, right-click the desired port, and click Delete Port.

5.

Optional: In Path View, right-click a blank space and select Add Port. In the Add Port dialog box displayed, set the Type of the port. Click OK to apply the configuration.

B.23 Configuring the Standard NTP Key On the U2000, you can use the standard network time protocol (NTP) service to automatically synchronize the NE time with the standard NTP server time. To ensure that a reliable server is accessed, the NTP authentication function must be started. In this case, you need to set the key and password, which are authenticated together to check whether the server is reliable.

Prerequisite l

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

l

The NE must support the standard NTP synchronization mode.


Context The NTP authentication of the NE must be the same as the standard NTP server. If the standard NTP server is configured with a key for authentication, the key of the NE must be the same as the key of the server.

Procedure 1.

In the Main Topology view, choose Configuration > NE Batch Configuration > NE Time Synchronization from the main menu. Click Standard NTP Key Management tab.

2.

In the Object Tree, select one or more NEs and click

3.

Click Close on the Result dialog box.

4.

Click Add and the Add Key and Password dialog box is displayed.

5.

Select the NE in the NE List pane, set Key ID and Password, and set Trusted to Yes. Then, click Apply.

6.

In the Result dialog box displayed, click Close.

Issue 01 (2011-10-20)


.

296



B.24 Synchronizing the NE Time with the Standard NTP Server Time You can use the standard network time protocol (NTP) service to automatically synchronize the NE time with the standard NTP server time.

Prerequisite l


l

The key and password of an NE must be set by using the standard NTP key management function.

l

The NE must support the standard NTP synchronization mode.


Context After you change the value of Synchronous Mode from NULL to Standard NTP, when the modification is delivered to the NE, the time synchronization may be successful though the encryption key is incorrect.

Procedure 1.

In the Main Topology view, choose Configuration > NE Batch Configuration > NE Time Synchronization from the main menu.

2.

In the Object Tree, select an NE and click the

3.

In the NE Time Synchronization tab, set the Synchronous Mode to Standard NTP.

4.

Set the Standard NTP Authentication to Enabled.

5.

Click Apply.

6.

In the displayed Result dialog box, click Close.

7.

In the pane at the bottom of the window, right-click, and then choose New from the shortcut menu to create a standard NTP server.

.

l If the Standard NTP Server Identifier is set to NE ID, enter the NE ID of the standard NTP server and Standard NTP Server Key. l If the Standard NTP Server Identifier is set to IP, enter the IP address of the standard NTP server and the Standard NTP Server Key. 8.

Click Apply to synchronize the NE time.

9.


10. Click Query. Make sure that the parameter values of the NTP server are the same as the ones set previously.

Issue 01 (2011-10-20)


297



B.25 Setting Automatic Synchronization of the NE Time with the NMS Time This section describes how to set automatic synchronization of the NE time with the NMS time. After you set automatic synchronization of the NE time with the NMS time, the NE time is automatically synchronized with the NMS time at specified intervals.

Prerequisite l

You must have logged in to an NE.

l


l

The NTP service must not be configured for the U2000 and NEs.



In the NE Explorer, select the NE. Choose Configuration > NE Time Synchronization from the Function Tree. The Result dialog box is displayed. Click Close.

2.

Set Synchronous Mode to NM, and click Apply. The Result dialog box is displayed. Click Close.

3.

Set Start Time and Period (days), and then click Apply. The Auto-Synchronization Settings dialog box is displayed. Click Yes. NOTE

Start Time cannot be earlier than the current time.

4.

The Result dialog box is displayed. Click Close


In the NE Explorer, select the NE. Choose Configuration > NE Time Synchronization from the Function Tree.

2.

Set Synchronous Mode to NM and then click Apply.

3.

Set Start Time and Period (days), and then click Apply. NOTE

Start Time cannot be earlier than the current time.

B.26 Performance Management To ensure the normal functioning of the network, the network management and maintenance personnel should periodically check and monitor the network by taking proper performance management measures.

Issue 01 (2011-10-20)


298



B.26.1 Setting the Board Performance Threshold The NE reports an event when it detects that a performance value exceeds the specified threshold. According to the requirement, you can set different performance thresholds for a board. On the U2000, if you have already created a performance threshold template, you can set performance thresholds for one or more boards at the same time.




In the NE Explorer, select a related board and choose Performance > Performance Threshold.

2.

In the Monitor Object pane, select the desired board, port, or channel.

3.

Set performance thresholds according to the requirement. NOTE

On the U2000, if you have already created a performance threshold template for the boards, click Use Template and select the desired template. Click Open.

4.

Optional: Click Default to restore the default settings.

5.

Click Apply.

6.

Click Query. Confirm that the value of Threshold value is the same as the value that is set.

B.26.2 Setting Performance Monitoring Parameters of a Board You can set the monitoring status and the automatic reporting status of monitored objects. The U2000/Web LCT monitors all the performance of board, but the automatic reporting feature is disabled by default. You can modify the value of the attribute according to the requirement.




In the NE Explorer, select a board and choose Performance > Performance Monitor Status from the Function Tree.

2.

Select a condition from the Monitored Object Filter Criteria drop-down list.

3.

Set the Monitor Status, 15-Minute Auto-Report and 24-Hour Auto-Report. Click Apply.

Issue 01 (2011-10-20)


299



4.


5.

Click Query. The displayed results are the same as the values that are set.

B.26.3 Setting Performance Monitoring Parameters of an NE By setting performance monitoring parameters of an NE properly and starting the performance monitoring for the NE, you can obtain the detailed performance record during the running of the NE. This facilitates the monitoring and analysis of the NE running status performed by maintenance personnel.

Prerequisite You must be an NM user with "NE operator" authority or higher. The NE time must be synchronized with the U2000/Web LCT server time.



In the Main Topology view, choose Performance > Set NE Performance Monitoring Time from the Main Menu.

2.

Select NEs from the NE list. Click

3.

Select one or more NEs, and set 15-minute and 24-hour performance monitor parameters according to the requirement.

.

(1) Select Enabled. (2) Set the start time and date. (3) Optional: Select To: check box, set the end time and date. NOTE

l The start time must be later than the current time of the network management system and the end time must be later than the start time. l If the end time is not set, this indicates that the performance monitoring starts from the start time and does not stop.

4.

Click Apply and then click Close in the Result dialog box.


In the NE Explorer, select the NE and choose Performance > NE Performance Monitor Time from the Function Tree.

2.

Set 15-minute and 24-hour performance monitor parameters as required. Click Apply.

3.

Click Query. The displayed results are the same as the values that are set.

4.

When the NE time is later than the monitoring time that is set, you can query the 15-minute and 24-hour performance monitoring of an NE normally.

B.26.4 Resetting Board Performance Registers After a network test or fault recovery but before the official operation, you need to reset the performance register so that the system enters a new performance monitoring period. Issue 01 (2011-10-20)


300






In the NE Explorer, select a board and choose Performance > Reset Board Performance Register from the Function Tree.

2.

Select the ports and registers that you want to reset and click Reset.

3.

Click OK in the Confirm dialog box. A prompt appears indicating that the operation is successful.

4.

Click Close.


In the NE Explorer, select a board and choose Performance > Reset Board Performance Register from the Function Tree.

2.

Select the registers that you want to reset.

3.

Click Reset and the confirmation dialog box is displayed. NOTE

All registers supported by the NE are provided as options for setting the register.

4.

Click OK.

B.27 Modifying the Services Configuration After a service is configured, you can modify or delete the configuration data of the service based on the following task sets.

B.27.1 Activating Cross-Connections Do as follows to apply cross-connections to a board.

Prerequisite You must be an NM user with "NE operator" authority or higher. The cross-connections must be created and inactive.



301



Procedure on the U2000 Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Click the WDM Cross-Connection Configuration tab. Step 3 Optional: Click Query to query the services on the NE. The Working cross-connection list displays all the created cross-connections. Step 4 Select one or more cross-connections in Inactive state (you can press Ctrl or Shift to select multiple cross-connections at the same time), right click and choose Activate. Then, the Confirm dialog box is displayed. Step 5 Click OK. The Result dialog box is displayed telling you that the operation was successful. Step 6 Click Close. In WDM Cross-Connection Configuration, Activation Status of the selected cross-connection(s) changes from Inactive to Active. ----End

B.27.2 Deactivating Cross-Connection Service To release the occupied channel resources, you need to deactivate cross-connections and then delete the cross-connections.



Precautions

CAUTION The deactivation operation may interrupt services.

Procedure on the U2000 Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Click the WDM Cross-Connection Configuration tab. Step 3 Optional: Click Query to query the services on the NE. The Working cross-connection list displays all the created cross-connections. Step 4 Select one or more cross-connections in Active state (you can press Ctrl or Shift to select multiple cross-connections at the same time), click Deactivate. Then, the Confirm dialog box is displayed. Issue 01 (2011-10-20)


302



Step 5 Click OK. The Result dialog box is displayed telling you that the operation was successful. Step 6 Click Close. In WDM Cross-Connection Configuration, Activation Status of the selected cross-connection(s) changes from Active to Inactive. ----End

B.27.3 Deleting Cross-Connections When you need to modify or re-configure cross-connections, you need to first delete them.

Prerequisite You must be an NM user with "NE operator" authority or higher. The cross-connections must be created and inactive.


Precautions

CAUTION Deleting cross-connections may interrupt services.

Procedure on the U2000 Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Click the WDM Cross-Connection Configuration tab. Click Query to query the information about the existing cross-connections. Step 3 Optional: Select the cross-connections to be deleted and click Deactivate. Step 4 Select the cross-connections to be deleted and click Delete. Step 5 In the Confirm dialog box that is displayed for two times, click OK and then click Close. In the Result dialog box. ----End

Procedure on the Web LCT Step 1 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree. Step 2 Click the Electrical Cross-Connection Configuration tab. Click Query to query the information about the existing cross-connections. Step 3 Optional: Select the cross-connections to be deleted and click Deactivate. Issue 01 (2011-10-20)


303



Step 4 Select the cross-connections to be deleted and click Delete. ----End

B.27.4 Converting an Unprotected Service to an SNCP Service SNCP protection provides the dual fed and selective receiving function and protection for crosssubnet services. You can convert an unprotected service to an SNCP-protected service (SNCP service for short) as required to improve service reliability.

Prerequisite You must be an NM user with "NE operator" authority or higher. A normal service must be created. When you convert a normal cross-connection service to an SNCP service, the protection path must be idle.


Procedure on the U2000 Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Select the WDM Cross-Connection Configuration tab, click Query to query the services on the NE. Step 3 Right-click the normal cross-connection service to be converted and choose Convert to SNCP Service from the shortcut menu. NOTE

Only unidirectional services can be converted to SNCP Service.

Step 4 In the Covert to SNCP Service dialog box displayed, configure the protection service. Enter the attributes for the protection service and click OK to convert the normal service to an SNCP service, and the protection service route is created. NOTE

You need to perform the operation on the source and sink NEs of the service or the NE that is set as a dual fed or selective receiving node that crosses protection subnets.

Step 5 Click New. In the Create Cross-Connection Service dialog box, create a unidirectional crossconnection from the sink board to the protection board. NOTE


Step 6 On the intermediate NE that protection services pass through, configure bidirectional passthrough services between line boards. Issue 01 (2011-10-20)


304



NOTE

You need to perform this operation on all the intermediate NEs that protection services pass through.

----End

Procedure on the Web LCT Step 1 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree. Step 2 Select the Electrical Cross-Connection Configuration tab, click Query to query the services on the NE. Step 3 Right-click the normal cross-connection service to be converted and choose To SNCP from the shortcut menu. NOTE

Only unidirectional services can be converted to SNCP Service.

Step 4 In the To SNCP dialog box displayed, configure the protection service. Enter the attributes for the protection service and click OK to convert the normal service to an SNCP service, and the protection service route is created. NOTE


Step 5 Click New. In the Create Cross-Connection Service dialog box, create a unidirectional crossconnection from the sink board to the protection board. NOTE


Step 6 On the intermediate NE that protection services pass through, configure bidirectional passthrough services between line boards. NOTE

You need to perform this operation on all the intermediate NEs that protection services pass through.

----End

B.27.5 Converting an SNCP Service to an Unprotected Service SNCP protection provides the dual fed and selective receiving function and protection for crosssubnet services. You can convert an SNCP-protected service (SNCP service for short) to an unprotected service as required to release the channel that has been occupied by the SNCP service.

Prerequisite You must be an NM user with "NE operator" authority or higher. An SNCP service must be created. Issue 01 (2011-10-20)


305




Precaution

CAUTION Converting an SNCP service to an unprotected service may interrupt the service.

Procedure on the U2000 Step 1 In the NE Explorer, select the NE and choose Configuration > WDM Service Management from the Function Tree. Step 2 Select the WDM Cross-Connection Configuration tab, click Query to query services of the NE. Step 3 Right-click on the desired SNCP service and choose SNCP Working Service Convert to NonProtection Service from the shortcut menu. In the prompt dialog box, click OK. In the Result dialog box, click Close. The protection service is deleted automatically, but you need to manually delete the cross-connection from the sink board to the protection board. NOTE

You can also choose SNCP Protection Service Convert to Non-Protection Service from the shortcut menu. In this case, the working service is deleted automatically, but you need to manually delete the unidirectional cross-connection from the sink board to the working board. Only unidirectional SNCP services can be converted to unprotected services.

Step 4 Right-click the unidirectional cross-connection from the sink board to the protection board, and choose Deactivate from the shortcut menu. In the Confirm dialog box subsequently, click OK. In the Result dialog box, click Close. Step 5 Right-click the unidirectional cross-connection that you deactivated and choose Delete from the shortcut menu. In the Confirm dialog box subsequently, click OK. In the Result dialog box, click Close. NOTE


Step 6 On the intermediate NE that protection services pass through, delete bidirectional pass-through services between line boards. NOTE

You need to perform this operation on all the intermediate NEs that protection services pass through. When choose SNCP Protection Service Convert to Non-Protection Service, you need to perform this operation on all the intermediate NEs that normal services pass through.

----End Issue 01 (2011-10-20)


306



Procedure on the Web LCT Step 1 In the NE Explorer, select the NE and choose Configuration > Electrical Cross-Connection Service Management from the Function Tree. Step 2 Select the Electrical Cross-Connection Configuration tab, click Query to query services of the NE. Step 3 Right-click on the desired SNCP service and choose SNCP Working Service Convert to NonProtection Service from the shortcut menu. In the prompt dialog box, click OK. The protection service is deleted automatically, but you need to manually delete the cross-connection from the sink board to the protection board. NOTE

You can also choose SNCP Protection Service Convert to Non-Protection Service from the shortcut menu. In this case, the working service is deleted automatically, but you need to manually delete the unidirectional cross-connection from the sink board to the working board. Only unidirectional SNCP services can be converted to unprotected services.

Step 4 Right-click the unidirectional cross-connection from the sink board to the protection board, and choose Delete from the shortcut menu. In the Confirm dialog box, click OK. Step 5 On the intermediate NE that protection services pass through, delete bidirectional pass-through services between line boards. NOTE

You need to perform this operation on all the intermediate NEs that protection services pass through. When choose SNCP Protection Service Convert to Non-Protection Service, you need to perform this operation on all the intermediate NEs that normal services pass through.

----End

B.28 Switching the Working Mode of the LQM2 The default working mode of the LQM2 board is 2LQM Mode. When the working mode is switched to AP8 Mode, you need to configure the board and add the IN2/OUT2 optical port according to this section.

Prerequisite You must be an NM user with "NE operator" authority or higher. The physical and logical LQM2 board must be configured.

Background Information This section describes how to configure the LQM2 board and add an optical port when the working mode of the board is switched from 2LQM Mode to AP8 Mode. When the working mode of the board is switched from AP8 Mode to 2LQM Mode, the configuration of the board is similar except that you do not need to add the IN2/OUT2 optical port.

Procedure Step 1 Delete the cross-connections on the LQM2 board: Issue 01 (2011-10-20)


307



1.

In the NE Explorer, click the NE and choose Configuration > WDM Service Management from the Function Tree. Click Query. The Working cross-connection field displays all the working cross-connections on the LQM2 board.

2.

Select all the working cross-connections on the LQM2 board, and then click Deactivate. Click OK. In the displayed prompt dialog box, click OK.

3.

A prompt is displayed, indicating that the operation is successful. Click Close.

4.

Select all the working cross-connections on the LQM2 board, Click Delete. In the displayed prompt dialog box, click OK.

5.


Step 2 Delete the service type on the LQM2 board: 1.

In the NE Explorer, select the LQM2 board and then choose Configuration > WDM Interface from the Function Tree.

2.

On the right of the user interface, select , and select Channel from the drop-down list. On the tab page, set Service Type of optical port 3 to optical port 10 to None, and then click Apply.

3.


Step 3 Add the IN2/OUT2 optical port of the LQM2 board: 1.

In the NE Explorer, right-click the LQM2 board and then choose Path View. The Path View window is displayed.

2.

Right-click the blank space on the right of the Path View window, and then choose Add Port.

3.

The Add Port dialog box is displayed. Click OK.

Issue 01 (2011-10-20)


308



----End

B.29 Backing Up and Restoring the NE Data For the security of the NE data, you can back up and restore the NE data.

B.29.1 Comparison of NE Data Backup and Restoration Methods You need to back up important NE data during daily maintenance. This ensures that the SCC board of the NE automatically restores to normal operation after the NE data in the DRDB database of the SCC board is lost or a power failure occurs on the equipment. This section describes several NE data backup and restoration methods. You can select the method as required.

Comparison of Backup and Restoration Methods The locations for backing up and restoring the NE database include the SCC board, CF card, local server and remote server. Different storage locations determine different types of backup and restoration methods. See Table B-1. Table B-1 Backup and restoration methods and application scenarios Backup and Restoration Method

Application Scenario

Back up/Restore the NE database to/from an SCC board

Backs up the NE data in the DRDB database of the SCC board to the flash database, when the SCC board does not have a CF card. During the restoration, after a warm reset or a cold reset on the SCC board, the SCC board reads the configuration from the flash database and issues the configuration to other boards.

Issue 01 (2011-10-20)


309



Backup and Restoration Method

Application Scenario

Back up/Restore the NE database to/from a CF card

Backs up the NE data in the DRDB database of the SCC board to the CF card. During the restoration, the database is restored from the CF card to the DRDB database of the SCC board. After a warm reset on the SCC board, the memory database on the SCC board is updated.

Back up/Restore the NE data to/from an NMS server

Stores the data in the computer where the NMS server resides. During restoration, you can select the backup file in the directory where the NE data is saved.

Back up/Restore the NE data to/from an NMS client

Stores the data in the computer where the NMS client resides. During restoration, you can select the backup file in the directory where the NE data is saved.

NE Database The NE configuration data is saved in the NE database. There are three types of NE databases as follows: l

MDB: Memory database. The data in a MDB database is changed when the configuration information is changed. The data is lost when the SCC board is reset or a power failure occurs.

l

DRDB: Dynamic random database. The data that is verified is automatically saved in the DRDB database. The data is lost when a power failure occurs.

l

FDB: Flash database. There are the FDB0 and FDB1 databases. The data need to be copied to the database manually and can be saved permanently.

When the NE configuration data is issued to the SCC board, it is saved in the MDB database. If the verification is successful, the SCC board automatically copies the contents in the MDB database to the DRDB database and issues the verified configuration data to the boards. You need to manually copy the DRDB database to the FDB database, as a backup of the DRDB database. When the NE is restarted after a power failure, the SCC board checks whether there is configuration data in the DRDB database. If yes, the data are restored from the DRDB database. If the data in the DRDB database is damaged, the data is restored from the FDB0 and FDB1 databases.

NE Configuration Data The NE configuration data refers to the information in the DRDB database of the NE, such as the board configuration, clock configuration and protection relationships of the NE. It is the instruction file of the NE and the key for the NE to perform normally in the entire network.

Issue 01 (2011-10-20)


310



NE Database Package The NE database package is a package that contains all database files on an NE and a file list that defines and manages those files. The NE database package and NE configuration data are the same data on the NE in different releases. You can perform the NE database package backup and restoration on the release 5.00.06 NE or the NE of later release.

B.29.2 Restoring the NE Database from the SCC Board When the database file is lost due to the NE maintenance or NE fault, you can restore the NE data from the DRDB database file that is already backed up to the Flash database on the SCC board.

Prerequisite l


l

You must log in to the NE as an NE user with system level authority.

l

The NE data from DRDB Database must be backed up to Flash database on the SCC board.


Procedure Step 1 Right-click the active SCC board in the NE panel, choose Warm Reset or Cold Reset. Click OK in the confirmed dialog box. NOTE

The reset modes for different SCC board are different. You need to choose the reset mode as required.


B.29.3 Recovering Device Data from the NMS Server or the NMS Client This operation describes how to recover the device data from the NMS Server or the NMS Client.

Prerequisite l

The FTP/TFTP/SFTP server is configured and the FTP/TFTP/SFTP service is started.

l

To perform the Recover operation from client, the SFTP server must be configured, and the SFTP service is started.

Background Information l

You cannot perform the Recover operation for multiple devices of different device types.

l

On selecting the device type in the device tree, all the device information related to the device type is displayed in the NE View table.

Issue 01 (2011-10-20)


311




Procedure 1.

In the Main Topology view, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.

2.

Right click the device(s) that you want to recover in the NE View table.

3.

Select Recover... to open the Recover dialog.

4.

In the File Name drop-down list, select the file to be recovered. If the backup file is not listed in the File Name drop-down list, select the file to be recovered, and turn to 6. If the backup file is not listed in the File Name drop-down list, click Browse... to select the backup file in the Select File dialog box, as shown below.

5.

Select NMS Server or NMS Client to recover the backup file for the selected device(s). By default NMS Server is selected. l If NMS Server is selected, you need to select the appropriate backup file from the NMS server. The selected backup file path is displayed in the File To Be Recovered field. l If NMS Client is selected, you need to click to select the backup file from the NMS Client. The selected backup file path is displayed in the File To Be Recovered field.

6.

Click OK. NOTE

The selected backup file path from the NMS Server or NMS Client is displayed in the File Name dropdown list.

7.

Click Start, the Operation Confirmation dialog box is displayed.

8.

In the Operation Confirmation dialog, click Yes to start the recover operation. The recover operation status is displayed in the NE View table.

Result After the device data is recovered, right click the device in the NE View table. Select Activation Database... to open the Activation Database dialog box, and then click Start to activate the device database. NOTE

If you do not activate the software within five minutes after the restoration is successfully complete, the U2000 automatically rolls back the software and cancels the restoration operation.

B.30 Creating Fiber Connections in List Mode In Fiber/Cable Management, you can manage the fiber connections between NEs and inside NEs in a unified manner. Compared with the graphic mode, the creating fiber connections in the list mode is not visual. Hence, the list mode is applicable to the scenario where you create a few fiber connections only.

Prerequisite l Issue 01 (2011-10-20)

You must be an NM user with "NE operator" authority or higher. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

312


l


The board on relevant NEs must be created.



Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu.

2.

Click Create, and the Bulk Create Fibers/Cables dialog box is displayed.

3.

Click Select Object, select all the NEs you need to create fiber/cable in the dialog box.

4.

Click OK.

5.

Click New in the Bulk Create Fibers/Cables dialog box.

6.

Double-click the setting area of each attributes. Set Direction, Source NE, Source Port, Sink NE and Sink Port.

7.

Click Apply. TIP

You can create multiple fibers/cables and set parameters in step 5, click Apply.

8.

Click Close on the Operation Result dialog box. Repeat Step 6-8 to create another fiber connection.

9.

Click Apply to complete the settings. The created fiber connections are displayed in the Fiber/Cable Information list.

10. Move the cursor to the fiber that is created and then information about the fiber is displayed. Read the information to check whether the fiber is created correctly.

Issue 01 (2011-10-20)


313


C

C Parameter Reference

Parameter Reference

C.1 NE Attributes In this user interface, you can view and set NE attributes, including NE ID, subrack type, and IP address. C.2 Attributes of NE Users In this user interface, you can manage NE users for the specific NE. You can query, add, delete and modify an NE user, and set password for the NE user. C.3 NE Time Synchronization In this user interface, you can set NE time, to keep it synchronized with the U2000 server time. C.4 WDM Cross-Connection Configuration In this user interface, you can configure the cross-connections of various WDM services. C.5 Port Protection Parameters In this user interface, you can create, configure and modify the port protection group. Port protection is used to switch the service to the protection port when the working port becomes faulty. It ensures service availability. A working port and the corresponding protection port are regarded as a port protection group. C.6 SNCP Service Control Parameters In this user interface, you can query and modify the attributes and status of an SNCP service.

Issue 01 (2011-10-20)


314



C.1 NE Attributes In this user interface, you can view and set NE attributes, including NE ID, subrack type, and IP address.

Parameters Field

Value

Description

ID

1 to 49135

Displays the unique ID of an NE on the NM for identifying an NE, which is the basis of communication between the NM and an NE.

Extended ID

1 to 254

For NE ID extension.

Default: 9

Click Extended ID for more information.

Name

For example: NE70

Displays the NE name, for the convenience of searching for the NE.

Remarks

-

Enters extra notes of the NE if desired.

Gateway Type

Non-gateway, Gateway

The gateway type of an NE decides the mode of communication between the NE and the NM.

Protocol

IP, OSI

Displays the protocol used for communication between the Gateway NE and the NM. The OptiX OSN 1800 series supports only the IP protocol.

IP Address

For example: 192.168.0.1

Displays the IP of the gateway NE.

Connection Mode

Common, Security SSL

Displays the mode of connection between the U2000 and the gateway NE. Click Connection Mode (NE Attributes) for more information.

Port

Issue 01 (2011-10-20)

Default: 1400


Displays the port of the gateway NE.

315



Field

Value

Description

Affiliated Gateway Protocol

IP

Displays the protocol used for communication between the affiliated Gateway NE and the NM.

C.2 Attributes of NE Users In this user interface, you can manage NE users for the specific NE. You can query, add, delete and modify an NE user, and set password for the NE user.

Parameters

Issue 01 (2011-10-20)

Field

Value

Description

NE user

Up to 8 characters can be supported.

The name of NE user.


Click NE User (NE User Management) for more information.

316



Field

Value

Description

User Level

Monitor level, Operation level, Maintenance level, System level, Debug level

The operations carried out by the NE user are classified into five levels, namely monitor level, operation level, maintenance level, system level and debug level from the lowest level to the highest. Each user of higher level can perform all the functions that a lower level user can do. For example, a operation level user has all the rights processed by a monitor level user. The detailed right settings for each level are: l Monitor level: all query commands, log in/out, and modification of its own password l Operation level: all settings for fault and performance, partial security settings, and partial configuration l Maintenance level: partial security settings, partial configuration, communication settings, and log management l System level: all security settings, all configuration. l Debug level: all security settings, all configuration, and all debug commands Click User Level (NE User Management) for more information.

Issue 01 (2011-10-20)


317



Field

Value

Description

NE User Flag

LCT NE user, EMS NE user, CMD NE user, General NE user

Different NE users are used for logging in to NEs through different network management systems. LCT NE user: NE user used when NEs are managed by LCT. EMS NE user: NE user used when NEs are managed by EMS. CMD NE user: NE user used when NEs are managed by CMD. General NE user: NE user used when NEs are managed by the network management system of any type. Click NE User Flag for more information.

Detailed Description

Up to 32 characters can be supported.

Displays the user description.

New Password

-

New password of the user. The password consists of 6-16 characters. It can be a combination of English characters, digits, space and underlines. Note that the password cannot be composed all by digits or all by letters. It cannot contain special characters.

Confirm Password

-

String, containing 6 to 16 characters. It must include one alphabetic and one numeric characters at least. The new password and the retyped one must be the same.

Whether the password is allowed to be modified immediately

Issue 01 (2011-10-20)

Yes, No


Sets whether the password is allowed to be modified immediately. This setting is supported only for release 5.0 NEs.

318



C.3 NE Time Synchronization In this user interface, you can set NE time, to keep it synchronized with the U2000 server time.

Parameters Field

Value

Description

NE Name

For example: NEW-NE2

Displays the name of the NE.

NE ID

Format: Extended ID-ID

Displays the ID of the NE.

Synchronous Mode

NM, NULL, Standard NTP

Displays the synchronization mode of NE Time. NM: Synchronize the NE time with the NM server time. NULL: No synchronization mode is used. Standard NTP: Synchronize the NE time with the standard NTP server time.

Standard NTP Authentication

Enabled, Disabled

Displays or sets whether the standard NTP authentication is enabled.

Server Enabled

ECC Server, Disabled

Displays or sets whether to set it to the NTP server and the type of the NTP server. When the ECC protocol is used for communication between NEs, the gateway NE is an ECC server. So, the Server Enabled parameter is set to ECC Server. While non-gateway NEs are ECC clients and the Server Enabled parameter is set to Disabled. When the IP protocol is used for communication between NEs, all NEs are IP clients and the Server Enabled parameter is set to Disabled. OptiX OSN 1800 series do not support.

Issue 01 (2011-10-20)


319



Field

Value

Description

Client Enabled

ECC Client, IP Client, Disabled

Displays or sets whether to set it to the NTP client and the type of the NTP client. When the IP protocol is used for communication between the NE and the NTP server, the NE is an IP client and the Client Enabled parameter are set to IP Client. OptiX OSN 1800 series do not support.

NE ID, IP address

Synchronous Server

Displays or sets the IP address or NE ID of the NTP synchronous server. If the client type is ECC Client, set it to the NE ID of the synchronous server. If the client type is IP Client, set it to the IP address of the synchronous server. OptiX OSN 1800 series do not support.

2 to 1440 Minutes

Polling Period (min)

Displays the period of synchronizing the NE time with the NTP server time. OptiX OSN 1800 series do not support.

The Number of Sampling

1 to 8

It indicates how many times the NTP server time will be sampled in a querying cycle. The NTP server time is the average of that sampled. OptiX OSN 1800 series do not support.

Issue 01 (2011-10-20)

NE Current Time

Format: dd/mm/yyyy hh:mm:ss

Displays the current time of the NE.

Daylight Saving Time

Yes, No

Displays whether to save the time in the daytime or not.


320



Field

Value

Description

Recent NE Synchronizatio n Time

Format: dd/mm/yyyy hh:mm:ss

The latest time when the NE was synchronized. If the difference between the current NE time and the latest time when the NE was synchronized is within two querying cycles, it indicates the NTP server is running normally. Otherwise, it indicates the NTP server is not running normally, and the color of the parameter box will change to the one that is for "Major Alarm".

C.4 WDM Cross-Connection Configuration In this user interface, you can configure the cross-connections of various WDM services.

Parameters

C.5 Port Protection Parameters In this user interface, you can create, configure and modify the port protection group. Port protection is used to switch the service to the protection port when the working port becomes faulty. It ensures service availability. A working port and the corresponding protection port are regarded as a port protection group.

Parameters Table C-1 Protection Group Parameters

Issue 01 (2011-10-20)

Field

Value

Description

Protection Group Name

For example: NE811-52910

Displays the protection group name.

Protection Type

Optical Line Protection, IntraBoard 1+1 Protection, Client 1+1 Protection, Inter-Subrack 1+1 Optical Channel Protection

Displays the protection type of the protection group.

NE with Working Channel

For example: NE811

Sets the NE of the working channel.

Board with Working Channel

For example: Shelf1-3-OLP

Sets the board of the working channel.


321



Field

Value

Description

Working Channel

For example: 1(RI1/TO1)

Sets and queries the working channel.

NE with Protection Channel

For example: NE811

Sets the NE of the protection channel.

Board with Protection Channel

For example: Shelf1-3-OLP

Sets the board of the protection channel.

Protection Channel

For example: 2(RI2/TO2)

Sets and queries the protection channel.

NE with Control Channel/ Detection Channel

For example: NE811

Sets the NE of the control channel/monitoring channel.

Board with Control Channel/ Detection Channel

For example: 1-LOE

Sets the board of the control channel/monitoring channel.

Restore Mode

Revertive, Non-Revertive

Indicates whether the service is automatically switched from the protection channel to the working channel after the working channel becomes normal.

Default: Non-Revertive

Revertive means that the service can be automatically switched. Non-Revertive means that the service is not switched to the working channel after the working channel becomes normal. NOTE In the case of the intra-board 1 +1 protection configured by using the OLP board, when the Monitoring Channel is configured, Revertive Mode can be only Non-revertive and cannot be configured.

WTR time (mm:ss)

05:00 to 12:00 Default: 10:00

The WTR time parameter indicates the waiting time before the services in the protection group switch back to the working channel if the working channel is recovered when the protection group works in the revertive mode. The WTR Time(mm:ss) is valid only when the value of Revertive Mode is set to Revertive.

Issue 01 (2011-10-20)


322



Field

Value

Description

SD Switching

Enable, Disable

The parameter determines if the SD switching function of the wavelength protection group takes effect.

Default: Disable

Switching Status

Idle, WTR, Manual to Working channel, Manual to Protection channel, Force to Working channel, Force to Protection channel, SD Switched, SF Switched, Locked, Unknown

Displays the current switching status of the protection group.

Table C-2 Channel Status Parameters

Issue 01 (2011-10-20)

Field

Value

Description

Protection Group Name

For example: NE811-52910

Displays the protection group name.

Current Channel

Work, Protection, Unknown

Displays the path of the current service.

Working Channel

NE name- Shelf1()Slot No.Board name- Optical port number (Optical port name)

Displays the working channel of the protection group.

Working Channel Status

Normal, SD, SF, Unknown

Displays the status of the working channel.

Working Channel Hold-Off Time

0-100

The Working Channel Hold-Off Time (100ms) parameter specifies the time period from the time that the system detects the switching condition in the working channel to the time that the switching is performed. This is to prevent protection switching from being performed repeatedly when the service state is unstable.

Control Channel/Detection Channel

NE name- Slot No.- Board name- Optical port number (Optical port name)

Default: 0


Displays the channel information of the Control Channel/Monitoring Channel.

323



Field

Value

Description

Control Channel/Detection Channel Hold-Off Time (100 ms)

0 to 100

Displays the hold-off time of the control board.

Protection Channel

NE name- Slot No.- Board name- Optical port number (Optical port name)

Displays the protection channel of the protection group.

Protection Channel Status

Normal, SD, SF, Unknown

Displays the status of the protection channel.

Protection Channel Hold-Off Time

0-100

The Protection Channel Hold-Off Time (100ms) parameter specifies the time period from the time that the system detects the switching condition in the protection channel to the time that the switching is performed.

NOTE This parameter cannot be set in optical line protection.

Default: 0

C.6 SNCP Service Control Parameters In this user interface, you can query and modify the attributes and status of an SNCP service.

Navigation Path 1.

In the NE Explorer, select an NE and choose Configuration > WDM Service Management from the navigation tree.

2.

In the lower portion of the WDM Cross-Connection Configuration window, click Create SNCP Service. The Create SNCP Service dialog box is displayed.

Parameters

Issue 01 (2011-10-20)

Field

Value

Description

Source Slot

Shelf ID (shelf name)-slot number-board name

Sets the source slot of the service.

Source Optical Port

Optical Port No.

Sets the source optical port of the service.

Source Optical Channel(e.g. 1, 3–6)

Optical Channel No.

Sets the source optical channel of the service.

Sink Slot

Shelf ID (shelf name)-slot number-board name

Sets the sink slot of the service.


324



Field

Value

Description

Sink Optical Port

Optical Port No.

Sets the sink optical port of the service.

Sink Optical Channel(e.g.1, 3–6)

Optical Channel No.

Sets the sink optical channel of the service.

Service Source

Source Slot Number-Source Board Name-Source Port Number-Source Optical Channel Number

Displays the source optical channel of the service.

Service Sink

Sink Slot Number-Sink Board Name-Sink Port Number-Sink Optical Channel Number

Displays the sink optical channel of the service.

Protection Type

SW SNCP, ODUk SNCP, MS SNCP

The Protection Type parameter provides users an option for choosing a required level for the newly created SNCP protection. The ODUk SNCP protection and SW SNCP protection protect services of different cross-connect granularities, which are ODUk and GE/ ANY respectively. If the protection type is changed, the relevant parameters must also be changed accordingly.

Default: SW SNCP

NOTE OptiX OSN 1800 series support SW SNCPand ODUK SNCP protection type only.

Service Type

l When Service Type is set to SW SNCP: GE, FE, OTU1, STM-1, STM-4, STM-16, FC100, FC200, FICON, FICON Express, HD-SDI, DVB-ASI, SDI, ESCON Default: GE

Sets the service type of the SNCP.

l When Service Type is set to ODUK SNCP: ODU0, ODU1, ODU2, ODUflex Default: ODU0

Issue 01 (2011-10-20)


325



Field

Value

Description

SNCP Type

SNC/I, SNC/S, SNC/N

The SNCP Type parameter specifies the monitoring mode of the ODUk SNCP protection.

Default: SNC/N

NOTE When you select Protection Type as ODUK SNCP, you can set this parameter. OptiX OSN 1800 series support SNC/I and SNC/N.

l When SNCP Type is set to SNC/I, this parameter is invalid

OTN Level

l When SNCP Type is set to SNC/N: PM, TCM1, TCM2, TCM3, TCM4, TCM5, TCM6. Default: PM

Sets the OTN level. NOTE When you select SNCP Type is SNC/N or SNC/S, you can set this parameter. OptiX OSN 1800 series do not support this parameter.

l When SNCP Type is set to SNC/S: TCM1, TCM2, TCM3, TCM4, TCM5, TCM6. Default: TCM1 Normal State, WTR State, Manual (from Protection to Working) Switching State, Manual (from Working to Protection) Switching State, Forced (from Protection to Working) Switching State, Forced (from Working to Protection) Switching State, SD Switching, SF Switching, Lockout

Current Status

The Current Status parameter displays the switching status of a protection group.

Default: None Revertive Mode

Revertive, Non-Revertive Default: Non-Revertive

Issue 01 (2011-10-20)


The Revertive Mode parameter provides users with an option for whether to switch back the services to the working channel from the protection channel automatically after the working channel is recovered.

326


Field


Value

Description

300-720

The WTR time (s) parameter indicates the waiting time before the services in the protection group switch back to the working channel if the working channel is recovered when the protection group works in the revertive mode.

Default: 600

Working Channel Hold-Off Time

0-100

Protection Channel Hold-Off Time

0-100

SD Switching

Enabled, Disabled

Default: 0

Default: 0

The Working Channel Hold-Off Time (100ms) parameter specifies the time period from the time that the system detects the switching condition in the working channel to the time that the switching is performed. This is to prevent protection switching from being performed repeatedly when the service state is unstable. The Protection Channel Hold-Off Time (100ms) parameter specifies the time period from the time that the system detects the switching condition in the protection channel to the time that the switching is performed. Sets the SD enabling status.

Default: Disabled

Issue 01 (2011-10-20)


327



Field

Value

Description

Direction

Unidirectional, Bidirectional

Sets the cross-connection direction.

Default: Unidirectional

l When Direction is Unidirectional, the boards in the ODUk SNCP protection group can only selectively receive signals. Therefore, two reverse electrical crossconnections must be created after the ODUk SNCP protection group is created. l When Direction is Bidirectional, the U2000 automatically creates two routes in the reverse direction. ODUflex Timeslots

3-7 Default: -

l When Service Type is ODUflex of the newly created service, set ODUflex Timeslots accordingly. l Set ODUflex Timeslots based on the service rate. The value ranges from 3 to 7, which means ODUflex includes the service rates in the range of 3.75 Gbit/s (3 x 1.25 Gbit/s) to 8.75 Gbit/s (7 x 1.25 Gbit/s). NOTE When Service Type is only set to ODUflex, this parameter is valid.

Issue 01 (2011-10-20)


328



Field

Value

Description

Switching Mode

Unidirectional, Bidirectional

Sets the protection switching mode.

Default: Unidirectional

l Unidirectional: Services in only one direction are switched. l Bidirectional: Services in both directions are switched. NOTE This parameter is valid only when Protection Type is set to ODUK SNCP .

Switching Type

Near-end, Far-end Default: Near-end

Indicates the end (the near end or the far end) that sends a bidirectional switching request. NOTE When Switching Mode is only set to Bidirectional, this parameter is valid.

Channel Status

Normal, SF, SD, Unknown

Displays the status of the working service or the protection service in a protection group.

Current Channel

Working Channel, Protection Channel, Delay Start

The Current Channel parameter indicates the type of the channel where the service is currently located in the SNCP protection group.

Default: /

Issue 01 (2011-10-20)


329


D Glossary

D

Glossary

A AC

See alternating current

access control list

A list of entities, together with their access rights, which are authorized to have access to a resource.

ACK

See acknowledgement

acknowledgement

A response sent by a receiver to indicate successful reception of information. Acknowledgements may be implemented at any level including the physical level (using voltage on one or more wires to coordinate transfer), at the link level (to indicate successful transmission across a single hardware link), or at higher levels.

ACL

See access control list

add/drop multiplexer

Network elements that provide access to all or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/ or dropped from (extracted) the STM-N signal as it passed through the ADM.

Add/drop wavelength

Add/drop wavelength refers to the wavelength that carries the add/drop services in the OADM equipment.

Address Resolution Protocol

Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and routers to determine the link layer addresses through ARP requests and ARP responses. The address resolution is a process in which the host converts the target IP address into a target MAC address before transmitting a frame. The basic function of the ARP is to query the MAC address of the target equipment through its IP address.

ADM

See add/drop multiplexer

administrative unit

The information structure which provides adaptation between the higher order path layer and the multiplex section layer. It consists of an information payload (the higher order VC) and an AU pointer which indicates the offset of the payload frame start relative to the multiplex section frame start.

Administrator

A user who has authority to access all the Management Domains of the EMLCore product. He has access to the whole network and to all the management functionalities.

ADSL

See asymmetric digital subscriber line

AGC

See automatic gain control

Issue 01 (2011-10-20)


330


D Glossary

AID

access identifier

AIS

See alarm indication signal

alarm

A message reported when a fault is detected by a device or by the network management system during the process of polling devices. Each alarm corresponds to a recovery alarm. After a recovery alarm is received, the status of the corresponding alarm changes to cleared.

alarm cable

The cable for generation of visual or audio alarms.

alarm cascading

The shunt-wound output of the alarm signals of several subracks or cabinets.

alarm cause

A single disturbance or fault may lead to the detection of multiple defects. A fault cause is the result of a correlation process which is intended to identify the defect that is representative of the disturbance or fault that is causing the problem.

alarm indication

On the cabinet of an NE, there are four indicators in different colors indicating the current status of the NE. When the green indicator is on, it indicates that the NE is powered on. When the red indicator is on, it indicates that a critical alarm is generated. When the orange indicator is on, it indicates that a major alarm is generated. When the yellow indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on the front panel of a board indicates the current status of the board.

alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. alarm mask

On the host, an alarm management method through which users can set conditions for the system to discard (not to save, display, or query for) the alarm information meeting the conditions.

alarm severity

The significance of a change in system performance or events. According to ITU-T recommendations, an alarm can have one of the following severities: Critical, Major, Minor, Warning.

alarm suppression

A function used not to monitor alarms for a specific object, which may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board.

alarm type

Classification of alarms with different attributes. There are six alarm types as following: Communication: alarm indication related with information transfer. Processing: alarm indication related with software or information processing Equipment: alarm indication related with equipment fault Service: alarm indication related with QoS of the equipment Environment: alarm related with the environment where the equipment resides, usually generated by a sensor Security: alarm indication related with security

ALC

See automatic level control

ALC link

A piece of end-to-end configuration information, which exists in the equipment (single station) as an ALC link node. Through the ALC function of each node, it fulfils optical power control on the line that contains the link.

ALC node

The ALC functional unit. It corresponds to the NE in a network. The power detect unit, variable optical attenuator unit, and supervisory channel unit at the ALC node work together to achieve the ALC function.

ALS

See automatic laser shutdown

alternating current

Electric current that reverses its direction of flow (polarity) periodically according to a frequency measured in hertz, or cycles per second.

Issue 01 (2011-10-20)


331


D Glossary

American National Standard Institute

An organization that defines U.S standards for the information processing industry. American National Standard Institute (ANSI) participates in defining network protocol standards.

American Standard Code for Information Interchange

American Standard Code for Information Interchange - the standard system for representing letters and symbols. Each letter or symbol is assigned a unique number between 0 and 127.

ANSI

See American National Standard Institute

antistatic floor

A floor that can quickly release the static electricity of the object contacting it to prevent accumulated static electricity

APD

See avalanche photodiode

APE

automatic power equilibrium

APID

access point identifier

application-specific integrated circuit

A special type of chip that starts out as a nonspecific collection of logic gates. Late in the manufacturing process, a layer is added to connect the gates for a specific function. By changing the pattern of connections, the manufacturer can make the chip suitable for many needs.

APS

See automatic protection switching

ARP

See Address Resolution Protocol

arrayed waveguide grating

A device, built with silicon planar lightwave circuits (PLC), that allows multiple wavelengths to be combined and separated in a dense wavelength-division multiplexing (DWDM) system.

ASCII

See American Standard Code for Information Interchange

ASE

amplified spontaneous emission

ASIC

See application-specific integrated circuit

ASON

See automatically switched optical network

asymmetric digital subscriber line

A technology for transmitting digital information at a high bandwidth on existing phone lines to homes and businesses. Unlike regular dialup phone service, ADSL provides continuously-available, "always on" connection. ADSL is asymmetric in that it uses most of the channel to transmit downstream to the user and only a small part to receive information from the user. ADSL simultaneously accommodates analog (voice) information on the same line. ADSL is generally offered at downstream data rates from 512 Kbps to about 6 Mbps.

Asynchronous Transfer Mode

A protocol for the transmission of a variety of digital signals using uniform 53 byte cells. A transfer mode in which the information is organized into cells; it is asynchronous in the sense that the recurrence of cells depends on the required or instantaneous bit rate. Statistical and deterministic values may also be used to qualify the transfer mode.

ATAG

autonomously generated correlation tag

ATM

See Asynchronous Transfer Mode

AU

See administrative unit

auto-negotiation

An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to automatically exchange information over a link about speed and duplex abilities.

Issue 01 (2011-10-20)


332


D Glossary

automatic gain control A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter, such as received signal level. automatic laser shutdown

A technique (procedure) to automatically shutdown the output power of laser transmitters and optical amplifiers to avoid exposure to hazardous levels.

automatic level control A well-known application in communication systems with a given input signal conditioned to produce an output signal as possible, while supporting a wide gain range and controlled gain-reduction and gain recovery characteristics. automatic protection switching

Capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic.

automatically switched A network which is based on technology enabling the automatic delivery of transport optical network services. Specifically, an ASON can deliver not only leased-line connections but also other transport services such as soft-permanent and switched optical connections. avalanche photodiode

A semiconductor photodetector with integral detection and amplification stages. Electrons generated at a p/n junction are accelerated in a region where they free an avalanche of other electrons. APDs can detect faint signals but require higher voltages than other semiconductor electronics.

AWG

See arrayed waveguide grating

B background block error ratio

The ratio of background block errors (BBE) to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs.

backup

A periodic operation performed on the data stored in the database for the purposes of database recovery in case that the database is faulty. The backup also refers to data synchronization between active and standby boards.

bandwidth

A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate.

BAS

See broadband access server

basic input/output system

A firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, and system setting information. The BIOS provides hardware setting and control functions for the computer.

bayonet-neillconcelman

A connector used for connecting two coaxial cables.

BBE

background block error

BBER

See background block error ratio

BC

See boundary clock

BDI

Backward Defect Indication

BEI

backward error indication

BER

See bit error rate

BIAE

backward incoming alignment error

Issue 01 (2011-10-20)


333


D Glossary

bill of material

Listing of all the subassemblies, parts and raw materials that go into the parent assembly. It shows the quantity of each raw material required to make the assembly. There are a variety of display formats for BOMS, including single level, indented, modular/ planning, transient, matrix and costed BOMs [APICs, CMSG].

BIOS

See basic input/output system

BIP

See bit-interleaved parity

BIP-8

See bit interleaved parity order 8

bit error

An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal.

bit error rate

Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network.

bit interleaved parity order 8

A frame is divided into several blocks with 8 bits (one byte)in a parity unit. Then arrange the blocks in matrix. Compute the number of "1" over each column. Then fill a 1 in the corresponding bit for the result if the number is odd, otherwise fill a 0.

bit-interleaved parity

A method of error monitoring. With even parity an X-bit code is generated by the transmitting equipment over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, etc. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the X-bit sequences in the covered portion of the signal. The covered portion includes the BIP-X.

BITS

See building integrated timing supply

BMC

best master clock

BNC

See bayonet-neill-concelman

BOM

See bill of material

boundary clock

A clock with a clock port for each of two or more distinct PTP communication paths.

BPDU

See bridge protocol data unit

BPS

board-level protection switching

bridge protocol data unit

The data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol (STP) topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology. The loops are then removed by shutting down selected bridges interfaces and placing redundant switch ports in a backup, or blocked, state.

bridging

The action of transmitting identical traffic on the working and protection channels simultaneously.

broadband access server

A server providing features as user access, connection management, address allocation and authentication, authorization and accounting. It also works as a router featuring effective route management, high forwarding performance and abundant services.

broadcast

A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address.

Issue 01 (2011-10-20)


334


D Glossary

broadcast service

The unidirectional services from one service source to multiple service sinks.

building integrated timing supply

In the situation of multiple synchronous nodes or communication devices, one can use a device to set up a clock system on the hinge of telecom network to connect the synchronous network as a whole, and provide satisfactory synchronous base signals to the building integrated device. This device is called BITS.

BWS

Backbone WDM System

C cable tie

The tape used to bind the cables.

capex

See capital expenditure

capital expenditure

Capital expenditures (CAPEX or capex) are expenditures creating future benefits. A capital expenditure is incurred when a business spends money either to buy fixed assets or to add to the value of an existing fixed asset with a useful life that extends beyond the taxable year. Capex are used by a company to acquire or upgrade physical assets such as equipment, property, or industrial buildings.

CAR

See committed access rate

CBS

See committed burst size

CC

See connectivity check

CCI

connection control interface

CCM

See continuity check message

CD

chromatic dispersion

CDMA

See Code Division Multiple Access

CE

See customer edge

CENELEC

See European Committee for Electrotechnical Standardization

central processing unit The computational and control unit of a computer. The CPU is the device that interprets and executes instructions. The CPU has the ability to fetch, decode, and execute instructions and to transfer information to and from other resources over the computer's main data-transfer path, the bus. centralized alarm system

The system that gathers all the information about alarms into a certain terminal console.

CF

See compact flash

CGMP

Cisco Group Management Protocol

channel

A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. The channel can be established through wire, radio (microwave), fiber or a combination of the three. The amount of information transmitted per second in a channel is the information transmission speed, expressed in bits per second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s (1012 bit/s).

channel spacing

The center-to-center difference in frequency or wavelength between adjacent channels in a WDM device.

CIR

See committed information rate

Issue 01 (2011-10-20)


335


D Glossary

CIST

Common and Internal Spanning Tree

CLEI

common language equipment identification

CLNP

connectionless network protocol

CLNS

connectionless network service

clock synchronization

Also called frequency synchronization, clock synchronization means that the signal frequency traces the reference frequency, but the start point need not be consistent.

clock synchronization A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588 compliant with V2 standard specifies the precision time protocol (PTP) in a measurement and control precision time protocol system. The PTP protocol ensures clock synchronization precise to sub-microseconds. clock tracing

The method to keep the time on each node being synchronized with a clock source in a network.

CM

See configuration management

CMEP

connection monitoring end point

CMI

coded mark inversion

coarse wavelength division multiplexing

A signal transmission technology that multiplexes widely-spaced optical channels into the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM does not support optical amplifiers and is applied in short-distance chain networking.

Code Division Multiple A communication scheme that forms different code sequences by using the frequency Access expansion technology. In this case, subscribers of different addresses can use different code sequences for multi-address connection. committed access rate

A traffic control method that uses a set of rate limits to be applied to a router interface. CAR is a configurable method by which incoming and outgoing packets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined.

committed burst size

committed burst size. A parameter used to define the capacity of token bucket C, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

committed information The rate at which a frame relay network agrees to transfer information in normal rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket. Common Object Request Broker Architecture

A specification developed by the Object Management Group in 1992 in which pieces of programs (objects) communicate with other objects in other programs, even if the two programs are written in different programming languages and are running on different platforms. A program makes its request for objects through an object request broker, or ORB, and thus does not need to know the structure of the program from which the object comes. CORBA is designed to work in object-oriented environments. See also IIOP, object (definition 2), Object Management Group, object-oriented.

compact flash

Compact flash (CF) was originally developed as a type of data storage device used in portable electronic devices. For storage, CompactFlash typically uses flash memory in a standardized enclosure.

concatenation

A process that combines multiple virtual containers. The combined capacities can be used a single capacity. The concatenation also keeps the integrity of bit sequence.

Issue 01 (2011-10-20)


336


D Glossary

Configuration Data

A command file defining hardware configurations of an NE. With this file, an NE can collaborate with other Nes in an entire network. Thus, configuration data is the key factor for normal running of an entire network.

configuration management

1. A network management function defined by the International Standards Organization (ISO). It involves installing, reinitializing & modifying hardware & software. 2. Configuration Management (CM) is a system for collecting the configuration information of all nodes in the network.

configure

To set the basic parameters of an operation object.

congestion

An extra intra-network or inter-network traffic resulting in decreasing network service efficiency.

connecting plate

A metallic plate which is used to combine two cabinets.

connection point

A reference point where the output of a trail termination source or a connection is bound to the input of another connection, or where the output of a connection is bound to the input of a trail termination sink or another connection. The connection point is characterized by the information which passes across it. A bidirectional connection point is formed by the association of a contradirectional pair.

connectivity check

Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically.

continuity check message

CCM is used to detect the link status.

convergence

1. A process in which multiple channels of low-rate signals are multiplexed into one or several channels of required signals. 2. It refers to the speed and capability for a group of networking devices to run a specific routing protocol. It functions to keep the network topology consistent.

convergence service

A service that provides enhancements to an underlying service in order to provide for the specific requirements of the convergence service user.

CORBA

See Common Object Request Broker Architecture

corrugated pipe

Used to protect optical fibers.

CPLD

Complex Programmable Logical Device

CPU

See central processing unit

CRC

See cyclic redundancy check

CSA

Canadian Standards Association

CSES

consecutive severely errored second

CSMA

carrier sense multiple access

CST

Common Spanning Tree

current alarm

An alarm not handled or not acknowledged after being handled.

current performance data

Performance data stored currently in a register. An NE provides two types of registers, namely, 15-minute register and 24-hour register, to store performance parameters of a performance monitoring entity. The two types of registers stores performance data only in the specified monitoring period.

Issue 01 (2011-10-20)


337


D Glossary

customer edge

A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the Service Provider (SP) network. A CE can be a router, switch, or host.

CWDM

See coarse wavelength division multiplexing

cyclic redundancy check

A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values.

D DAPI

destination access point identifiers

Data backup

A method that is used to copy key data to the standby storage area, to prevent data loss in the case of the damage or failure in the original storage area.

data communication network

A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF).

data communications channel

The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-M channel.

DBPS

distribute board protect system

DCC

See data communications channel

DCF

See dispersion compensation fiber

DCM

See dispersion compensation module

DCM frame

A frame which is used to hold the DCM (Dispersion Compensation Module).

DCN

See data communication network

DDF

See digital distribution frame

DDN

See digital data network

demultiplexer

A device that separates signals that have been combined by a multiplexer for transmission over a communications channel as a single signal.

dense wavelength division multiplexing

Technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths with specific frequency spacing as carriers, and allows multiple channels to transmit simultaneously in the same fiber.

device set

A collection of multiple managed devices. By dividing managed devices into different device sets, users can manage the devices by using the U2000 in an easier way. If an operation authority over one device set is assigned to a user (user group), the authority over all the devices in the device set is assigned to the user (user group), thus making it unnecessary to set the operation authority over all the devices in a device set separately. It is recommended to configure device set by geographical region, network level, device type, or another criterion.

DHCP

See Dynamic Host Configuration Protocol

Issue 01 (2011-10-20)


338


D Glossary

diamond-shaped nut

A type of nut that is used to fasten the wiring frame to the cabinet.

digital data network

A high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and the cross multiplex technology.

digital distribution frame

A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals.

digital subscriber line access multiplexer

A network device, usually situated in the main office of a telephone company that receives signals from multiple customer Digital Subscriber Line (DSL) connections and puts the signals on a high-speed backbone line using multiplexing techniques.

dispersion compensation fiber

A kind of fiber which uses negative dispersion to compensate for the positive dispersion of transmitting fiber to maintain the original shape of the signal pulse.

dispersion compensation module

A module, which contains dispersion compensation fibers to compensate for the dispersion of transmitting fiber.

Distance Vector Multicast Routing Protocol

An Internet gateway protocol mainly based on the RIP. The protocol implements a typical dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing datagrams with its neighbors.

distributed link aggregation group

The distributed link aggregation group (DLAG) is a board-level port protection technology used to detect unidirectional fiber cuts and to negotiate with the opposite end. In the case of a link down failure on a port or a hardware failure on a board, the services can automatically be switched to the slave board, thus realizing 1+1 protection for the inter-board ports.

DLAG

See distributed link aggregation group

DMUX; DEMUX

See demultiplexer

DNI

Dual Node Interconnection

domain

A logical subscriber group based on which the subscriber rights are controlled.

DQPSK

differential quadrature phase shift keying

DRDB

dynamic random database

DRZ

differential phase return to zero

DSCP

Differentiated Services Code Point

DSCR

dispersion slope compensation rate

DSLAM

See digital subscriber line access multiplexer

DSP

Digital Signal Processing

DTE

Data Terminal Equipment

DTMF

See dual tone multiple frequency

DTR

data terminal ready

dual tone multiple frequency

In telephone systems, multifrequency signaling in which standard set combinations of two specific voice band frequencies, one from a group of four low frequencies and the other from a group of four higher frequencies, are used.

dual-ended switching

A protection operation method which takes switching action at both ends of the protected entity (e.g. "connection", "path"), even in the case of a unidirectional failure.

Issue 01 (2011-10-20)


339


DVB

Digital Video Broadcasting

DVMRP

See Distance Vector Multicast Routing Protocol

DWDM

See dense wavelength division multiplexing

D Glossary

Dynamic Host Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol. Configuration Protocol A DHCP server provides configuration parameters specific to the DHCP client host requesting, generally, information required by the host to participate on the Internet network. DHCP also provides a mechanism for allocation of IP addresses to hosts.

E E2E

End to End

EAPE

enhanced automatic power pre-equilibrium

EBS

See excess burst size

ECC

See embedded control channel

EDFA

See erbium doped fiber amplifier

eDQPSK

enhanced differential quadrature phase shift keying

EFM

See Ethernet in the first mile

ejector lever

A lever for removing circuit boards from an electronic chassis.

electric supervisory channel

A technology realizes the communication among all the nodes and transmits the monitoring data in the optical transmission network. The monitoring data of ESC is introduced into DCC service overhead and is transmitted with service signals.

electromagnetic compatibility

Electromagnetic compatibility is the condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment.

electromagnetic interference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment.

electrostatic discharge

The sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field.

element management system

An element management system (EMS) manages one or more of a specific type of network elements (NEs). An EMS allows the user to manage all the features of each NE individually, but not the communication between NEs - this is done by the network management system (NMS).

embedded control channel

A logical channel that uses a data communications channel (DCC) as its physical layer, to enable transmission of operation, administration, and maintenance (OAM) information between NEs.

EMC

See electromagnetic compatibility

EMI

See electromagnetic interference

EMS

See element management system

enterprise system connection

A path protocol which connects the host with various control units in a storage system. It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.

EPL

See Ethernet private line

Issue 01 (2011-10-20)


340


D Glossary

EPLAN

See Ethernet private LAN service

erbium doped fiber amplifier

An optical device that amplifies the optical signals. The device uses a short length of optical fiber doped with the rare-earth element Erbium and the energy level jump of Erbium ions activated by pump sources. When the amplifier passes the external light source pump, it amplifies the optical signals in a specific wavelength range.

ESC

See electric supervisory channel

ESCON

See enterprise system connection

ESD

See electrostatic discharge

ESD jack

Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap.

eSFP

enhanced small form-factor pluggable

Ethernet

A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/ s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..

Ethernet in the first mile

Last mile access from the broadband device to the user community. The EFM takes the advantages of the SHDSL.b is technology and the Ethernet technology. The EFM provides both the traditional voice service and internet access service of high speed. In addition, it meets the users' requirements on high definition television system (HDTV) and Video On Demand (VOD).

Ethernet private LAN service

An Ethernet service type, which carries Ethernet characteristic information over a dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks.

Ethernet private line

A type of Ethernet service that is provided with dedicated bandwidth and point-to-point connections on an SDH, PDH, ATM, or MPLS server layer network.

Ethernet virtual private LAN service

An Ethernet service type, which carries Ethernet characteristic information over a shared bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks.

Ethernet virtual private line

An Ethernet service type, which carries Ethernet characteristic information over shared bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server layer networks.

ETS

European Telecommunication Standards

ETSI

European Telecommunications Standards Institute

ETSI 300mm cabinet

A cabinet which is 600mm in width and 300mm in depth, compliant with the standards of the ETSI.

European Committee for Electrotechnical Standardization

The European Committee for Electrotechnical Standardization was established in 1976 in Brussels. It is the result of the incorporation of two former organizations. It aims to reduce internal frontiers and trade barriers for electrotechnical products, systems and services.

EVOA

electrical variable optical attenuator

EVPL

See Ethernet virtual private line

EVPLAN

See Ethernet virtual private LAN service

Issue 01 (2011-10-20)


341


D Glossary

excess burst size

A parameter related to traffic. In the single rate three color marker (srTCM) mode, the traffic control is achieved by the token buckets C and E. Excess burst size is a parameter used to define the capacity of token bucket E, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

Extended ID

The number of the subnet that an NE belongs to, for identifying different network segments in a WAN. The extended ID and ID form the physical ID of the NE.

External cable

The cables and optical fibers which are used for connecting electrical interfaces and optical interfaces of one cabinet to interfaces of other cabinets or peripherals.

eye pattern

An oscilloscope display of synchronized pseudo-random digital data (signal amplitude versus time), showing the superposition of accumulated output waveforms.

F F1 byte

The user path byte, which is reserved for the user, but is typically special for network providers. The F1 byte is mainly used to provide the temporary data or voice path for special maintenance objectives. It belongs to the regenerator section overhead byte.

fast Ethernet

Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables), 100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical fibers).

fault

A failure to implement the function while the specified operations are performed. A fault does not involve the failure caused by preventive maintenance, insufficiency of external resources and intentional settings.

FBG

fiber Bragg grating

FC

See fiber channel

FDB

flash database

FDDI

See fiber distributed data interface

FE

See fast Ethernet

FEC

See forward error correction

fiber channel

A high-speed transport technology used to build storage area networks (SANs). Fiber channel can be on the networks carrying ATM and IP traffic. It is primarily used for transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair copper wires and coaxial cables. Fiber channel provides both connection-oriented and connectionless services.

fiber distributed data interface

A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for transmission rates of 100 megabits (100 million bits) per second on networks based on the token ring network.

fiber management tray A device used to coil up extra optical fibers.

Issue 01 (2011-10-20)


342


D Glossary

fiber patch cord

A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack.

fiber spool

A device used in coiling up an extra length of optical fibers.

Fiber trough

The trough that is used for routing fibers.

fiber/cable

Fiber & Cable is the general name of optical fiber and cable. It refers to the physical entities that connect the transmission equipment, carry transmission objects (user information and network management information) and perform transmission function in the transmission network. The optical fiber transmits optical signal, while the cable transmits electrical signal. The fiber/cable between NEs represents the optical fiber connection or cable connection between NEs. The fiber/cable between SDH NEs represents the connection relation between NEs. At this time, the fiber/cable is of optical fiber type.

field programmable gate array

A type of semi-customized circuit used in the Application Specific Integrated Circuit (ASIC) field. It is developed on the basis of the programmable components, such as the PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also overcomes the disadvantage of the original programmable components in terms of the limited number of gate arrays.

FIFO

See First in First out

File Transfer Protocol

A member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTP roles: one must be an FTP client and the other an FTP server.

First in First out

A stack management mechanism. The first saved data is first read and invoked.

Flow

An aggregation of packets that have the same characteristics. On the network management system or NE software, flow is a group of classification rules. On boards, it is a group of packets that have the same quality of service (QoS) operation. At present, two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist in the same port.

FMT

See fiber management tray

FOADM

fixed optical add/drop multiplexer

FOAs

fixed optical attenuator

Forced switch

For normal traffic signals, switches normal traffic signal to the protection section, unless an equal or higher priority switch command is in effect or SF condition exists on the protection section, by issuing a forced switch request for that traffic signal.

forward error correction

A bit error correction technology that adds the correction information to the payload at the transmit end. Based on the correction information, the bit errors generated during transmission are corrected at the receive end.

four-wave mixing

Four-Wave Mixing (FWM), also called four-photon mixing, occurs when the interaction of two or three optical waves at different wavelengths generates new optical waves, called mixing products or sidebands, at other wavelengths.

FPGA

See field programmable gate array

Issue 01 (2011-10-20)


343


frame

D Glossary

A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.

frame alignment signal A distinctive signal inserted in every frame or once in every n frames, always occupying the same relative position within the frame, and used to establish and maintain frame alignment. FTP

See File Transfer Protocol

full-duplex

A full-duplex, or sometimes double-duplex system, allows communication in both directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line telephone networks are full-duplex, since they allow both callers to speak and be heard at the same time. A good analogy for a full-duplex system would be a two-lane road with one lane for each direction.

G gain

The ratio between the optical power from the input optical interface of the optical amplifier and the optical power from the output optical interface of the jumper fiber, which expressed in dB.

gain flattening filter

Gain Flattening Filter (GFFs), also known as gain equalizing filters, are used to flatten or smooth out unequal signal intensities over a specified wavelength range. This unequal signal intensity usually occurs after an amplification stage (for example, EDFA and/or Raman). Typically, GFFs are used in conjunction with gain amplifiers to ensure that the amplified channels all have the same gain. A static spectral device that flattens the output spectrum of an erbium-doped fiber amplifier.

Gateway IP

When an NE accesses a remote network management system or NE, a router can be used to enable the TCP/IP communication. In this case, the IP address of the router is the gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP networks. An NE may have multiple IP addresses, for example, one IP address of the network and one IP address of the Ethernet port.

gateway network element

A network element that is used for communication between the NE application layer and the NM application layer

Gb

See gigabit

GCC

general communication channel

GCP

See GMPLS control plan

GE

See gigabit Ethernet

GE ADM

The technology can optimize GE service transport over WDM for Metro network. It owns the capability of GE service convergence and grooming and benefits to use the network resource more effectively.

generic framing procedure

A framing and encapsulated method which can be applied to any data type. It has been standardized by ITU-T SG15.

GFF

See gain flattening filter

GFP

See generic framing procedure

Issue 01 (2011-10-20)


344


D Glossary

gigabit

In data communications, a gigabit is one billion bits, or 1,000,000,000 (that is, 10^9) bits. It's commonly used for measuring the amount of data that is transferred in a second between two telecommunication points.

gigabit Ethernet

GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge (switch) or a router as the center, it gives full play to the performance and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that are private, causing the length of the links to be sufficient for backbone applications in a building and campus.

Global Positioning System

A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users.

GMPLS

generalized multiprotocol label switching

GMPLS control plan

The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei. The OptiX GCP applies to the OptiX OSN product series. By using this software, the traditional network can evolve into the ASON network. The OptiX OSN product series support the ASON features.

GNE

See gateway network element

GPS

See Global Positioning System

graphical user interface A visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen. grounding

The connection of sections of an electrical circuit to a common conductor, called the ground, which serves as the reference for the other voltages in the circuit.

GSSP

General Snooping and Selection Protocol

GUI

See graphical user interface

H Hardware loopback

A connection mode in which a fiber jumper is used to connect the input optical interface to the output optical interface of a board to achieve signal loopback.

HCS

See hierarchical cell structure

HDB

high density bipolar code

HDLC

See high level data link control

hierarchical cell structure

This is a term typically used to describe the priority of cells within a mixed environment. That is when Macro, Micro, and Pico cells may be viewed as candidates for cell reselection the priority described by the HCS will be used in the associated calculations.

high level data link control

The HDLC protocol is a general purpose protocol which operates at the data link layer of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by adding a trailer and a header.

History alarm

The confirmed alarms that have been saved in the memory and other external memories.

History Performance Data

The performance data that is stored in the history register or that is automatically reported and stored in the NMS.

Issue 01 (2011-10-20)


345


D Glossary

I IAE

incoming alignment error

IC

See integrated circuit

ICC

ITU carrier code

ICMP

See Internet Control Message Protocol

ID

See identity

identity

The collective aspect of the set of characteristics by which a thing is definitively recognizable or known.

Idle resource optical NE

When the U2000 is started successfully, an NE icon called "Idle ONE" will be displayed on the topological view. In this NE, the subracks and boards that are not divided to other optical NEs (such as OTM, OADM and other NEs) are retained. In this NE, idle DWDM subracks and boards are reserved, which can be distributed to other ONEs. Double-click the NE icon to view all the currently idle DWDM subracks or boards in the network.

IE

See Internet Explorer

IEC

See International Electrotechnical Commission

IEEE

See Institute of Electrical and Electronics Engineers

IETF

See Internet Engineering Task Force

IGMP

See Internet Group Management Protocol

Input jitter tolerance

The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when modulating the signal at an equipment input port, results in no more than two errored seconds cumulative, where these errored seconds are integrated over successive 30 second measurement intervals.

Institute of Electrical and Electronics Engineers

A society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEE focuses on electrical, electronics, computer engineering, and science-related matters.

integrated circuit

A combination of inseparable associated circuit elements that are formed in place and interconnected on or within a single base material to perform a microcircuit function.

integrated services digital network

A network defined in CCITT, providing comprehensive transmission service for the voice, video, and data. The ISDN enables the voice, video, and data transmission on a small number of data channels simultaneously, thus implementing a comprehensive transmission service.

intelligent power adjustment

A technology that the system reduces the optical power of all the amplifiers in an adjacent regeneration section in the upstream to a safety level if the system detects the loss of optical signals on the link. The loss of optical signals may due to the fiber is broken, the performance of equipments trend to be inferior or the connector is not plugged well. Thus, the maintenance engineers are not hurt by the laser being sent out from the slice of broken fiber.

Internal cable

The cables and optical fibers which are used for interconnecting electrical interfaces and optical interfaces within the cabinet.

internal spanning tree

A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.

Issue 01 (2011-10-20)


346


D Glossary

International Electrotechnical Commission

The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards.

International Organization for Standardization

An international association that works to establish global standards for communications and information exchange. Primary among its accomplishments is the widely accepted ISO/OSI reference model, which defines standards for the interaction of computers connected by communications networks.

International Telecommunication Union

A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R).

International Telecommunication UnionTelecommunication Standardization Sector

An international body that develops worldwide standards for telecommunications technologies. These standards are grouped together in series which are prefixed with a letter indicating the general subject and a number specifying the particular standard. For example, X.25 comes from the "X" series which deals with data networks and open system communications and number "25" deals with packet switched networks.

Internet Control Message Protocol

A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, it can let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSI reference model, packet (definition 1).

Internet Engineering Task Force

A worldwide organization of individuals interested in networking and the Internet. Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with studying technical problems facing the Internet and proposing solutions to the Internet Architecture Board (IAB). The work of the IETF is carried out by various working groups that concentrate on specific topics, such as routing and security. The IETF is the publisher of the specifications that led to the TCP/IP protocol standard.

Internet Explorer

Microsoft's Web browsing software. Introduced in October 1995, the latest versions of Internet Explorer include many features that allow you to customize your experience on the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.

Internet Group Management Protocol

The protocol for managing the membership of Internet Protocol multicast groups among the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships.

Internet Protocol

The TCP/IP standard protocol that defines the IP packet as the unit of information sent across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part. The entire protocol suite is often referred to as TCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791.

IP

See Internet Protocol

IP address

A 32-bit (4-byte) binary number that uniquely identifies a host (computer) connected to the Internet for communication with other hosts in the Internet by transferring packets. An IP address is expressed in dotted decimal notation, consisting of the decimal values of its 4 bytes, separated with periods; for example, 127.0.0.1. The first three bytes of the IP address identify the network to which the host is connected, and the last byte identify the host itself.

IP over DCC

The IP Over DCC follows TCP/IP telecommunications standards and controls the remote NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead DCC byte (the default is D1-D3) for communication.

IPA

See intelligent power adjustment

Issue 01 (2011-10-20)


347


D Glossary

IPG

inter-packet gap

ISDN

See integrated services digital network

ISO

See International Organization for Standardization

IST

See internal spanning tree

ITU

See International Telecommunication Union

ITU-T

See International Telecommunication Union-Telecommunication Standardization Sector

J Jitter

Short waveform variations caused by vibration, voltage fluctuations, and control system instability.

Jitter transfer

The physical relationship between jitter applied at the input port and the jitter appearing at the output port.

L label switched path

A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label switching mechanisms. A label-switched path can be chosen dynamically, based on normal routing mechanisms, or through configuration.

LACP

See Link Aggregation Control Protocol

LAG

See link aggregation group

LAN

See local area network

LAPD

link access procedure on the D channel

LAPS

link access protocol-SDH

Laser

A component that generates directional optical waves of narrow wavelengths. The laser light has better coherence than ordinary light. The fiber system takes the semi-conductor laser as the light source.

layer

A concept used to allow the transport network functionality to be described hierarchically as successive levels; each layer being solely concerned with the generation and transfer of its characteristic information.

LB

See loopback

LCAS

See link capacity adjustment scheme

LCD

See liquid crystal display

LCN

local communication network

LCT

local craft terminal

LED

See light emitting diode

LHP

long hop

Issue 01 (2011-10-20)


348


D Glossary

light emitting diode

A display and lighting technology used in almost every electrical and electronic product on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and perimeter lighting. LEDs are also used as the light source in multimode fibers, optical mice and laser-class printers.

Link Aggregation Control Protocol

A method of bundling a group of physical interfaces together as a logical interface to increase bandwidth and reliability. For related protocols and standards, refer to IEEE 802.3ad.

link aggregation group An aggregation that allows one or more links to be aggregated together to form a link aggregation group so that a MAC client can treat the link aggregation group as if it were a single link. link capacity adjustment scheme

LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitlessly increase or decrease the capacity of a link to meet the bandwidth needs of the application. It also provides a means of removing member links that have experienced failure. The LCAS assumes that in cases of capacity initiation, increases or decreases, the construction or destruction of the end-to-end path is the responsibility of the Network and Element Management Systems.

Link Control Protocol

In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes, configures, and tests data-link Internet connections.

link state advertisement

The link in LSA is any type of connection between OSPF routers, while the state is the condition of the link.

linktrace message

The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP is called Linktrace Message(LTM). LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.

linktrace reply

For 802.1ag MAC Trace, the destination MEP replies with a response message to the source MEP after the destination MEP receives the LTM, and the response message is called Linktrace Reply (LTR). LTR also includes the TTL that equals the result of the TTL of LTM minus 1.

liquid crystal display

A type of display that uses a liquid compound having a polar molecular structure, sandwiched between two transparent electrodes.

LLC

See logical link control

LMP

link management protocol

LOC

loss of clock

local area network

A network formed by the computers and workstations within the coverage of a few square kilometers or within a single building. It features high speed and low error rate. Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/ s (that is, 1 Gbit/s).

Locked switching

When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel.

logical link control

According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper sublayer of the OSI data link layer. The LLC is the same for the various physical media (such as Ethernet, token ring, WLAN).

logical port

A logical port is a logical number assigned to every application.

Issue 01 (2011-10-20)


349


D Glossary

loopback

A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors.

LOP

See loss of pointer

LOS

See Loss Of Signal

loss of pointer

Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost the pointer to the start of cell in the payload. This is used to monitor the performance of the PHY layer.

Loss Of Signal

Loss of signal (LOS) indicates that there are no transitions occurring in the received signal.

Lower subrack

The subrack close to the bottom of the cabinet when a cabinet contains several subracks.

LP

See logical port

LPT

link-state pass through

LSA

See link state advertisement

LSP

See label switched path

LT

linktrace

LTM

See linktrace message

LTR

See linktrace reply

M MA

Maintenance Associations

MAC

See media access control

MADM

multiple add/drop multiplexer

main distribution frame

A device at a central office, on which all local loops are terminated.

main path interface at the transmitter

A reference point on the optical fiber just after the OM/OA output optical connector.

main topology

A interface that displays the connection relation of NEs on the NMS (screen display). The default client interface of the NMS, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs, subnets in the network, the communication status as well as the basic network operation status. All topology management functions are accessed here.

maintenance domain

The network or the part of the network for which connectivity is managed by CFM. The devices in an MD are managed by a single ISP.

maintenance point

Maintenance Point (MP) is one of either a MEP or a MIP.

MAN

See metropolitan area network

managed object

The management view of a resource within the telecommunication environment that may be managed via the agent. Examples of SDH managed objects are: equipment, receive port, transmit port, power supply, plug-in card, virtual container, multiplex section, and regenerator section.

Issue 01 (2011-10-20)


350


D Glossary

Management information

The information that is used for network management in a transport network.

management information base

A type of database used for managing the devices in a communications network. It comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network.

manual switch

Switches normal traffic signal to the protection section, unless a failure condition exists on other sections (including the protection section) or an equal or higher priority switch command is in effect, by issuing a manual switch request for that normal traffic signal.

Mapping

A procedure by which tributaries are adapted into virtual containers at the boundary of an SDH network.

marking-off template

A quadrate cardboard with four holes. It is used to mark the positions of the installation holes for the cabinet.

MD

See maintenance domain

MDB

Memory Database

MDF

See main distribution frame

MDP

message dispatch process

MDS

message distribution service software

ME

maintenance entities

mean launched power

The average power of a pseudo-random data sequence coupled into the fiber by the transmitter.

Mean Time Between Failures

The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system.

media access control

A protocol at the media access control sublayer. The protocol is at the lower part of the data link layer in the OSI model and is mainly responsible for controlling and connecting the physical media at the physical layer. When transmitting data, the MAC protocol checks whether to be able to transmit data. If the data can be transmitted, certain control information is added to the data, and then the data and the control information are transmitted in a specified format to the physical layer. When receiving data, the MAC protocol checks whether the information is correct and whether the data is transmitted correctly. If the information is correct and the data is transmitted correctly, the control information is removed from the data and then the data is transmitted to the LLC layer.

MEP

maintenance end point

metropolitan area network

A metropolitan area network (MAN) is a network that interconnects users with computer resources in a geographic area or region larger than that covered by even a large local area network (LAN) but smaller than the area covered by a wide area network (WAN). The term is applied to the interconnection of networks in a city into a single larger network (which may then also offer efficient connection to a wide area network). It is also used to mean the interconnection of several local area networks by bridging them with backbone lines. The latter usage is also sometimes referred to as a campus network.

MFAS

See multiframe alignment signal

MIB

See management information base

MIP

maintenance intermediate point

MLD

See multicast listener discovery

Issue 01 (2011-10-20)


351


D Glossary

MLM laser

See multi-longitudinal mode laser

MO

See managed object

mother board

A printed board assembly that is used for interconnecting arrays of plug-in electronic modules.

mounting ear

A piece of angle plate with holes in it on a rack. It is used to fix network elements or components.

MP

See maintenance point

MPI

main path interface

MPI-R

main path interface at the receiver

MPI-S

See main path interface at the transmitter

MPLS

See Multiprotocol Label Switching

MS

Multiplex Section

MSA

Multiplex Section Adaptation

MSI

multi-frame structure identifier

MSOH

See multiplex section overhead

MSP

See multiplex section protection

MSPP

multi-service provisioning platform

MST

See multiplex section termination

MSTI

See multiple spanning tree instance

MSTP

See Multiple Spanning Tree Protocol

MTA

Mail Transfer Agent

MTBF

See Mean Time Between Failures

MTU

Maximum Transmission Unit

multi-longitudinal mode laser

An injection laser diode which has a number of longitudinal modes.

multicast listener discovery

The MLD is used by the IPv6 router to discover the multicast listeners on their directly connected network segments, and set up and maintain member relationships. On IPv6 networks, after MLD is configured on the receiver hosts and the multicast router to which the hosts are directly connected, the hosts can dynamically join related groups and the multicast router can manage members on the local network.

multiframe alignment signal

A distinctive signal inserted in every multiframe or once in every n multiframes, always occupying the same relative position within the multiframe, and used to establish and maintain multiframe alignment.

multiple spanning tree Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP instance within an MST Region, to provide a simply and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to multiple MSTIs.

Issue 01 (2011-10-20)


352


D Glossary

Multiple Spanning Tree Protocol

Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In this case, the proliferation and endless cycling of packets is avoided in the loop network. The protocol that introduces the mapping between VLANs and multiple spanning trees. This solves the problem that data cannot be normally forwarded in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.

multiplex section overhead

The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH definition.

multiplex section protection

A function, which is performed to provide capability for switching a signal between and including two multiplex section termination (MST) functions, from a "working" to a "protection" channel.

multiplex section termination

The function performed to generate the MSOH in the process of forming an SDH frame signal and terminates the MSOH in the reverse direction.

multiplexer

Equipment which combines a number of tributary channels onto a fewer number of aggregate bearer channels, the relationship between the tributary and aggregate channels being fixed.

Multiplexing

A procedure by which multiple lower order path layer signals are adapted into a higher order path or the multiple higher order path layer signals are adapted into a multiplex section.

Multiprotocol Label Switching

A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing.

MUX

See multiplexer

MVOA

mechanical variable optical attenuator

N NA

No Acknowledgment

NCP

See Network Control Protocol

NE

See network element

NE database

There are three types of database on NE SCC board as following: (1) DRDB: a dynamic database in a dynamic RAM, powered by battery; (2) SDB: a static database in a power-down RAM; (3) FDB0, FDB0: permanently saved databases in a Flash ROM. In efficient operation, the NE configuration data is saved in DRDB and SDB at the same time. Backing up an NE database means backing up the NE configuration data from SDB to FDB0 and FDB1. When an NE is restarted after power-down, the NE database is restored in the following procedures: As the SDB data is lost due to power-down, the main control restores the data first from DRDB. If the data in DRDB is also lost due to the exhaustion of the battery, the data is restored from FDB0 or FDB1.

Issue 01 (2011-10-20)


353


D Glossary

NE Explorer

The main operation interface, of the NMS, which is used to manage the telecommunication equipment. In the NE Explorer, the user can query, manage and maintain the NE, boards, and ports on a per-NE basis.

NE ID

An ID that indicates a managed device in the network. In the network, each NE has a unique NE ID.

NE Panel

A graphical user interface, of the network management system, which displays subracks, boards, and ports on an NE. In the NE Panel, the user can complete most of the configuration, management and maintenance functions for an NE.

NE-side data

The NE configuration data that is stored on the SCC board of the equipment. The NEside data can be uploaded to the network management system(NMS) and thus is stored on the NMS side.

NEBS

Network Equipment Building System

NEF

See network element function

Network Control Protocol

This is the program that switches the virtual circuit connections into place, implements path control, and operates the Synchronous Data Link Control (SDLC) link.

network element

A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control and communication(SCC) board which manages and monitors the entire network element. The NE software runs on the SCC board.

network element function

A function block which represents the telecommunication functions and communicates with the TMN OSF function block for the purpose of being monitored and/or controlled.

network management

The process of controlling a network so as to maximize its efficiency and productivity. ISO's model divides network management into five categories: fault management, accounting management, configuration management, security management and performance management.

Network Management A system in charge of the operation, administration, and maintenance of a network. System network node interface The interface at a network node which is used to interconnect with another network node. network segment

A part of an Ethernet or other network, on which all message traffic is common to all nodes, that is, it is broadcast from one node on the segment and received by all others.

network service access A network address defined by ISO, through which entities on the network layer can point access OSI network services. Network Time Protocol The Network Time Protocol (NTP) defines the time synchronization mechanism. It synchronizes the time between the distributed time server and the client. NM

See network management

NMS

See Network Management System

NNI

See network node interface

NOC

network operation center

Noise figure

An index that represents the degrade extent of optical signals after the signals passing a system.

NSAP

See network service access point

NTP

See Network Time Protocol

Issue 01 (2011-10-20)


354


D Glossary

O OA

See optical amplifier

OADM

See optical add/drop multiplexer

OADM frame

A frame which is used to hold the OADM boards.

OAM

See operation, administration and maintenance

OC

See optical coupler

OCI

open connection indication

OCP

See optical channel protection

OD

optical demultiplexing

ODB

optical duobinary

ODF

See optical distribution frame

ODUk

optical channel data unit-k

OEQ

optical equalizer

OFC

open fiber control

OLA

See optical line amplifier

OLP

See optical line protection

OM

optical multiplexing

OMS

optical multiplexing section

ONE

See optical network element

Online Help

The capability of many programs and operating systems to display advice or instructions for using their features when so requested by the user.

OOF

See out of frame

OPA

optical power adjust

open shortest path first A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A link state database is constructed of the network topology which is identical on all routers in the area. Open Systems Interconnection

A framework of ISO standards for communication between different systems made by different vendors, in which the communications process is organized into seven different categories that are placed in a layered sequence based on their relationship to the user. Each layer uses the layer immediately below it and provides a service to the layer above. Layers 7 through 4 deal with end-to-end communication between the message source and destination, and layers 3 through 1 deal with network functions.

operation, administration and maintenance

A group of network support functions that monitor and sustain segment operation, activities that are concerned with, but not limited to, failure detection, notification, location, and repairs that are intended to eliminate faults and keep a segment in an operational state and support activities required to provide the services of a subscriber access network to users/subscribers.

OpEx; OPEX

operation expenditure

OPS

optical physical section

Issue 01 (2011-10-20)


355


D Glossary

optic fiber connector

A device installed at the end of a fiber, optical source or receive unit. It is used to couple the optical wave to the fiber when connected to another device of the same type. A connector can either connect two fiber ends or connect a fiber end and a optical source (or a detector).+

optical add/drop multiplexer

A device that can be used to add the optical signals of various wavelengths to one channel and drop the optical signals of various wavelengths from one channel.

optical amplifier

Devices or subsystems in which optical signals can be amplified by means of the stimulated emission taking place in a suitable active medium.

optical attenuator

A passive device that increases the attenuation in a fiber link. It is used to ensure that the optical power of the signals received at the receive end is not extremely high. It is available in two types: fixed attenuator and variable attenuator.

optical channel

A signal transmitted at one wavelength in a fiber-optic system.

optical channel protection

In an optical transmission link that contains multiple wavelengths, when a certain wavelength goes faulty, the services at the wavelength can be protected if the optical channel protection is configured.

optical coupler

A coupler for coupling light in an optical system. Multiple discrete layers of alternating optical materials have respective first and second indexes of refraction. The thickness of each layer is a fraction of the light wavelength.

optical distribution frame

A frame which is used to transfer and spool fibers.

optical line amplifier

A piece of equipment that functions as an OLA to directly amplify the input optical signals and to compensate for the line loss. Currently, the key component of the OLA is the EDFA amplifier.

optical line protection

A protection mechanism that adopts dual fed and selective receiving principle and singleended switching mode. In this protection, two pairs of fibers are used. One pair of fibers forms the working route. The working route transmits line signals when the line is normal. The other pair of fibers forms the protection route. The protection route carries line signals when the line is broken or the signal attenuation is extremely large.

optical network element

A transport entity that implements the NE functions (terminal multiplexing, add/drop multiplexing, cross-connection and regeneration) in a DWDM layer network. The types of ONEs include OTM, OADM, OLA, REG and OXC. The locating of an ONE is equivalent to that of a common NE. In a view, an ONE is displayed with an icon, like a common NE and its alarm status can be displayed with colors. Logically, an ONE consists of different subracks. Like a common NE, an ONE cannot be expanded or entered like a sub-network. Similar to a common NE, an ONE provides a list of the subracks that form the NE to display the board layout.

optical signal-to-noise ratio

The most important index of measuring the performance of a DWDM system. The ratio of signal power and noise power in a transmission link. That is, OSNR = signal power/ noise power.

optical spectrum analyzer

A device that allows the details of a region of an optical spectrum to be resolved. Commonly used to diagnose DWDM systems.

optical supervisory channel

A technology that realizes communication among nodes in optical transmission network and transmits the monitoring data in a certain channel (the wavelength of the working channel for it is 1510 nm and that of the corresponding protection one is 1625 nm).

Optical switch

A passive component possessing two or more ports which selectively transmits, redirects, or blocks optical power in an optical fiber transmission line.

Issue 01 (2011-10-20)


356


D Glossary

optical time domain reflectometer

A device that sends a very short pulse of light down a fiber optic communication system and measures the time history of the pulse reflection to measure the fiber length, the light loss and locate the fiber fault.

optical transmission section

Optical transmission section allows the network operator to perform monitoring and maintenance tasks between NEs.

optical transponder unit

A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength.

optical transport network

A network that uses the optical signal to transmit data

optical wavelength shared protection

In the optical wavelength shared protection (OWSP), the service protection between different stations can be achieved by using the same wavelength, realizing wavelength sharing. This saves the wavelength resources and lowers the cost. The optical wavelength shared protection is mainly applied to the ring network which is configured with distributed services. It is achieved by using the OWSP board. In a ring network where services are distributed at adjacent stations, each station requires one OWSP board. Then, two wavelengths are enough for configuring the shared protection to protect one service among stations.

OPU

optical channel payload unit

OPUk

optical channel payload unit-k

orderwire

A channel that provides voice communication between operation engineers or maintenance engineers of different stations.

original equipment manufacturer

An original equipment manufacturer, or OEM is typically a company that uses a component made by a second company in its own product, or sells the product of the second company under its own brand.

OSA

See optical spectrum analyzer

OSC

See optical supervisory channel

OSI

See Open Systems Interconnection

OSN

optical switch node

OSNR

See optical signal-to-noise ratio

OSPF

See open shortest path first

OTDR

See optical time domain reflectometer

OTM

optical terminal multiplexer

OTN

See optical transport network

OTS

See optical transmission section

OTU

See optical transponder unit

OTUk

optical channel transport unit-k

out of frame

An NE transmits an OOF downstream when it receives framing errors in a specified number of consecutive frame bit positions.

Output optical power

The ranger of optical energy level of output signals.

overhead cabling

Cables or fibers connect the cabinet with other equipment from the top of the cabinet.

OWSP

See optical wavelength shared protection

Issue 01 (2011-10-20)


357


D Glossary

P PA

pre-amplifier

packet over SDH/ SONET

A MAN and WAN technology that provides point-to-point data connections. The POS interface uses SDH/SONET as the physical layer protocol, and supports the transport of packet data (such as IP packets) in MAN and WAN.

packet switched network

A telecommunication network which works in packet switching mode.

Packing case

A case which is used for packing the board or subrack.

Paired slots

Two slots of which the overheads can be passed through by using the bus on the backplane.

pass-through

The action of transmitting the same information that is being received for any given direction of transmission.

PBS

See peak burst size

PCB

See printed circuit board

PCC

protection communication channel

PCC

See policy and charging control

PCS

See physical coding sublayer

PDH

See plesiochronous digital hierarchy

PDL

See polarization dependent loss

PDU

Protocol Data Unit

PE

Provider Edge

peak burst size

A parameter used to define the capacity of token bucket P, that is, the maximum burst IP packet size when the information is transferred at the peak information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

peak information rate

Peak Information Rate. A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate.

Performance register

Performance register is the memory space for performance event counts, including 15min current performance register, 24-hour current performance register, 15-min history performance register, 24-hour history performance register, UAT register and CSES register. The object of performance event monitoring is the board functional module, so every board functional module has a performance register. A performance register is used to count the performance events taking place within a period of operation time, so as to evaluate the quality of operation from the angle of statistics.

PGND

protection ground

phase-locked loop

A circuit that consists essentially of a phase detector which compares the frequency of a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with the incoming or reference frequency.

PHY

See physical sublayer & physical layer

Issue 01 (2011-10-20)


358


D Glossary

physical coding sublayer

The PCS further helps to define physical layer specifications for 10 gigabit Ethernet after having been broken down into their Physical Media Dependent Sublayer or PMD. Each sublayer places the 10GBASE standards into either LAN or WAN specifications.

physical sublayer & physical layer

1. physical sublayer: One of two sublayers of the FDDI physical layer. 2. physical layer: In ATM, the physical layer provides the transmission of cells over a physical medium that connects two ATM devices. The PHY is comprised of two sublayers: PMD and TC

PID

photonics integrated device

PIM-DM

protocol independent multicast-dense mode

PIM-SM

See protocol independent multicast sparse mode

PIN

See Positive Intrinsic Negative

PIR

See peak information rate

plesiochronous digital hierarchy

A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.

PLL

See phase-locked loop

PMD

polarization mode dispersion

PMI

payload missing indication

POH

path overhead

point to multipoint

A communications network that provides a path from one location to multiple locations (from one to many).

Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating over Ethernet PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard PPP features such as authentication, encryption, and compression. Pointer

An indicator whose value defines the frame offset of a virtual container with respect to the frame reference of the transport entity on which it is supported.

polarization dependent The maximum, peak-to-peak insertion loss (or gain) variation caused by a component loss when stimulated by all possible polarization states. It is specified in dB units. policy and charging control

Short for Policy and Charging Control, the PCC is defined in 3GPP R7. The PCC provides the QoS control and service-based charging functions in the wireless bearer network.

POS

See packet over SDH/SONET

Positive Intrinsic Negative

Photodiode. A semiconductor detector with an intrinsic (i) region separating the p- and n-doped regions. It has fast linear response and is used in fiber-optic receivers.

Power box

A direct current power distribution box at the upper part of a cabinet, which supplies power for the subracks in the cabinet.

power distribution box A power box through which the power enters the cabinet and is re-distributed to various components, at the mean time, the Power Distribution Box protects the electric devices from current overload. PPP

See Point-to-Point Protocol

PPPoE

See Point-to-Point Protocol over Ethernet

Issue 01 (2011-10-20)


359


D Glossary

PRBS

See pseudo random binary sequence

PRC

primary reference clock

PRI

See primary rate interface

primary rate interface

An interface consisting of 23 channel Bs and a 64 kbit/s channel D that uses the T1 line, or consisting of 30 channel Bs and a channel D that uses the E1 line.

printed circuit board

A board used to mechanically support and electrically connect electronic components using conductive pathways, tracks, or traces, etched from copper sheets laminated onto a non-conductive substrate.

protection ground cable

A cable which connects the equipment and the protection grounding bar. Usually, one half of the cable is yellow; while the other half is green.

Protection path

A specific path that is part of a protection group and is labeled protection.

Protection policy

In case the service route provides multiple service protections, different protection policies can be selected as required. Protection policy refers to the protection mode given the priority in use for the trail: protection, no protection, and extra traffic. Of the above, the protection preference is divided into trail protection and subnet connection protection.

Protection service

A specific service that is part of a protection group and is labeled protection.

protocol independent multicast sparse mode

It is applicable to large-scale multicast networks with scattered members.

pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence values of any of the other elements, similar to real random sequences. PSI

payload structure identifier

PSN

See packet switched network

PSTN

See public switched telephone network

PT

payload type

PTMP

See point to multipoint

PTN

packet transport network

PTP

Point-To-Point

public switched telephone network

A telecommunications network established to perform telephone services for the public subscribers. Sometimes called POTS.

Q QA

Q adaptation

QoS

See quality of service

quality of service

A commonly-used performance indicator of a telecommunication system or channel. Depending on the specific system and service, it may relate to jitter, delay, packet loss ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the transmission system and the effectiveness of the services, as well as the capability of a service provider to meet the demands of users.

Issue 01 (2011-10-20)


360


D Glossary

R radio network controller

An equipment in the RNS which is in charge of controlling the use and the integrity of the radio resources.

RAI

remote alarm indication

RAM

See random access memory

random access memory Semiconductor-based memory that can be read and written by the central processing unit (CPU) or other hardware devices. The storage locations can be accessed in any order. Note that the various types of ROM memory are capable of random access but cannot be written to. The term RAM, however, is generally understood to refer to volatile memory that can be written to as well as read. Rapid Spanning Tree Protocol

An evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change. The RSTP protocol is backward compatible with the STP protocol.

Receiver Sensitivity

Receiver sensitivity is defined as the minimum acceptable value of average received power at point R to achieve a 10-12 (The FEC is open).

reconfiguration optical The WDM equipment supports the ROADM. It flexibly and dynamically adjusts add/ add/drop multiplexer drop wavelengths of sites on the network by adjusting the pass-through or block status of any wavelength without affecting the service transmission in the main optical channel. This implements wavelength allocation among sites on the network. After the ROADM is used, the existing services are not affected during upgrade. The wavelength can be modified quickly and efficiently during network maintenance, which reduces maintenance cost. In addition, the ROADM supports the equalization for optical power, which equalizes the optical power at the channel level. Reed Solomon Code

A type of forward error correcting codes invented in 1960 by Irving Reed and Gustave Solomon, which has become commonplace in modern digital communications.

reference clock

A kind of stable and high-precision autonous clock providing frequencies for other clocks for reference.

Reflectance

The ratio of the reflected optical power to the incident optical power.

REG

A piece of equipment or device that regenerates electrical signals.

Regeneration

The process of receiving and reconstructing a digital signal so that the amplitudes, waveforms and timing of its signal elements are constrained within specified limits.

REI

Remote Error Indication

Resource Reservation Protocol

The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. RSVP is a network control protocol like Internet Control Message Protocol (ICMP).

RF

Radio Frequency

RFC

Requirement for Comments

RFI

remote failure indication

ring network

A type of network topology in which each node connects to exactly two other nodes, forming a circular pathway for signals.

RIP

See Routing Information Protocol

Issue 01 (2011-10-20)


361


D Glossary

RMON

remote network monitoring

RNC

See radio network controller

ROADM

See reconfiguration optical add/drop multiplexer

route

A route is the path that network traffic takes from its source to its destination. In a TCP/ IP network, each IP packet is routed independently. Routes can change dynamically.

Routing Information Protocol

A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route based on the smallest hop count between source and destination. RIP is a distance vector protocol that routinely broadcasts routing information to its neighboring routers and is known to waste bandwidth.

RS Code

See Reed Solomon Code

RS232

In the asynchronous transfer mode and there is no hand-shaking signal. It can communicate with RS232 and RS422 of other stations in point-to-point mode and the transmission is transparent. Its highest speed is 19.2kbit/s.

RSTP

See Rapid Spanning Tree Protocol

RSVP

See Resource Reservation Protocol

RZ

return to zero code

S S1 byte

In an SDH network, each network element traces step by step to the same clock reference source through a specific clock synchronization path, thus realizing the synchronization of the whole network. If a clock reference source traced by the NE is missing, this NE will trace another clock reference source of a lower level. To implement protection switching of clocks in the whole network, the NE must learn about clock quality information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization status information. It uses the lower four bits of the multiplex section overhead S1 byte to indicate 16 types of synchronization quality grades. Auto protection switching of clocks in a synchronous network can be implemented using S1 byte and a proper switching protocol.

Safe control switch

The IPA safe switch is set in consideration of the long-span networking requirement, which cannot allow too low output optical power. If the safe control switch is turned off, IPA restarting optical power is the specified output power of the OAU. Otherwise, the IPA restarting optical power is restricted to less than 10 dBm.

SAN

See storage area network

SAP

service access point

SAPI

source access point identifiers

SBS

stimulated Brillouin scattering

SC

See square connector

SD

See signal degrade

SD trigger flag

SD stands for signal degrade. The SD trigger flag determines whether to perform a switching when SD occurs. The SD trigger flag can be set by using the network management system.

SDH

See synchronous digital hierarchy

Issue 01 (2011-10-20)


362


D Glossary

SDI

See Serial Digital Interface

SDP

serious disturbance period

Search domain

Search field refers to the range of IP addresses being searched. In the TCP/IP, the IP addresses include: Category A address (1.0.0.0---126.255.255.255). For example, 10.*.*.*, whose search field is 10.255.255.255, all 10.*.*.* to be searched. Category B address (128.0.0.0---191. 255. 255. 255). For example, 129.9.*.*, whose search field is 129.9.255.255, all 129.9.*.* to be searched. Category C address (192.0.0.0---223. 255. 255. 255). For example, 192.224.9.*, whose search field is 192.224.9.255, all 192.224.9.* to be searched. Category D address (224.0.0.0---230.255.255.255), which is reserved. Category E address (240.0.0.0---247.255.255.255), which is reserved. Netid 127.*.*.*, in which .*.*.* can be any number. This net-ID is a local address.

Secure File Transfer Protocol

A network protocol designed to provide secure file transfer over SSH.

Self-healing

Self-healing is the establishment of a replacement connection by network without the NMC function. When a connection failure occurs, the replacement connection is found by the network elements and rerouted depending on network resources available at that time.

Serial Digital Interface An interface for transmitting digital signals. Serial Line Interface Protocol

Serial Line Interface Protocol, defines the framing mode over the serial line to implement transmission of messages over the serial line and provide the remote host interconnection function with a known IP address.

service level agreement A service contract between a customer and a service provider that specifies the forwarding service a customer should receive. A customer may be a user organization (source domain) or another differentiated services domain (upstream domain). A SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. Service protection

A measure that ensures that the services can be received at the receive end.

SES

See severely errored second

SETS

See synchronous equipment timing source

settings

Parameters of a system or operation that can be selected by the user.

severely errored second A one-second period which has a bit error ratio >= 10-3 or at least one defect. Time interval of one second during which a given digital signal is received with an error ratio greater than 10-3 (Rec. ITU R F. 592 needs correction) . SF

See signal fail

SFP

See small form-factor pluggable

SFTP

See Secure File Transfer Protocol

shock-proof reinforce

A process by which the cabinet is fastened to the wiring frame or the top of the equipment room so that the cabinet stands stably.

shortcut menu

A menu that is displayed when right-clicking an object's name or icon. This is also referred to a context menu.

side door

The side door of a cabinet is used to protect the equipment inside the cabinet against unexpected touch and environment impact.

Issue 01 (2011-10-20)


363


D Glossary

side mode suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total ratio source spectrum to the second largest peak. side trough

The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet.

signal cable

Common signal cables cover the E1 cable, network cable, and other non-subscriber signal cable.

signal degrade

A signal indicating the associated data has degraded in the sense that a degraded defect (e.g., dDEG) condition is active.

signal fail

A signal that indicates the associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active.

signal to noise ratio

The ratio of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel).

Simple Network Management Protocol

A network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. This protocol ensures the transmission of management information between any two points. The polling mechanism is adopted to provide basic function sets. According to SNMP, agents, which can be hardware as well as software, can monitor the activities of various devices on the network and report these activities to the network console workstation. Control information about each device is maintained by a management information block.

single-ended switching A protection operation method which takes switching action only at the affected end of the protected entity (e.g. "trail", "subnetwork connection"), in the case of a unidirectional failure. single-mode fiber

A type of fiber optic cable through which only one type of light signal with a fixed wave length can travel at a time. The inner diameter of the single-mode fiber is less than 10 microns. This type of fiber is used to transmit data in long distance.

SLA

See service level agreement

SLIP

See Serial Line Interface Protocol

SLM

single longitudinal mode

SM

section monitoring

small form-factor pluggable

A specification for a new generation of optical modular transceivers.

SMF

See single-mode fiber

SMSR

See side mode suppression ratio

SNCP

See subnetwork connection protection

SNCTP

See subnetwork connection tunnel protection

SNMP

See Simple Network Management Protocol

SNR

See signal to noise ratio

soft permanent connections

An ASON connection which features flexible and dynamic adjustment of routes. SPC includes different classes of services (CoS).

SONET

See synchronous optical network

Issue 01 (2011-10-20)


364


span

D Glossary

The physical reach between two pieces of WDM equipment. The number of spans determines the signal transmission distance supported by a piece of equipment and varies according to transmission system type.

Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant network to block some undesirable redundant paths through certain algorithms and prune a loop network into a loop-free tree network. SPC

See soft permanent connections

SPM

self phase modulation

SQL

See structured query language

square connector

Cables may use two styles of connectors: "square" and "D-style".

SRLG

Shared Risk Link Group

SRS

stimulated Raman scattering

SSM

See Synchronization Status Message

SSMB

synchronization status message byte

SSU

synchronization supply unit

STM

Synchronous Transfer Mode

STM-1

See synchronous transport mode 1

STM-4

Synchronous Transport Module of order 4

storage area network

An architecture to attach remote computer storage devices such as disk array controllers, tape libraries and CD arrays to servers in such a way that to the operating system the devices appear as locally attached devices.

STP

See Spanning Tree Protocol

structured query language

A database query and programming language widely used for accessing, querying, updating, and managing data in relational database systems.

sub-network

Sub-network is the logical entity in the transmission network and comprises a group of network management objects. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a sub-network is used to contain the equipments which are located in adjacent regions and closely related with one another, and it is indicated with a sub-network icon on a topological view. The U2000 supports multilevels of sub-networks. A sub-network planning can better the organization of a network view. On the one hand, the view space can be saved, on the other hand, it helps the network management personnel focus on the equipments under their management.

sub-network number

A number used to differentiate network sections in a sub-network conference. A subnetwork ID consists of the first several digits (one or two) of a user phone number. An oderwire phone number consists of the sub-network ID and the user number.

subnet mask

The technique used by the IP protocol to determine which network segment packets are destined for. The subnet mask is a binary pattern that is stored in the client machine, server or router and is matched with the IP address.

subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. Issue 01 (2011-10-20)


365


D Glossary

subnetwork connection SNCTP provides a VC-4 level channel protection. When the working channel is faulty, tunnel protection the services of the entire VC-4 path can be switched over to the protection channel. support

A part used to support and fix a cabinet on the antistatic floor, it is made of welded steel plates and is used to block the cabinets up, thus facilitating floor paving and cabling. Before the whole set of equipment is grounded, insulation plates must be installed under the supports, and insulating coverings must be added to the expansion bolts to satisfy the insulation requirements.

Suppression state

An attribute set to determine whether an NE monitors the alarm. Under suppression status, NE will not monitor the corresponding alarm conditions and the alarm will not occur even when the alarm conditions are met.

Switching priority

There may be the case that several protected boards need to be switched; thus the tributary board switching priority should be set. If the switching priority of each board is set the same, the tributary board that fails later cannot be switched. The board with higher priority can preempt the switching of that with lower priority.

Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link. Message Nodes on an SDH network and a synchronization network acquire upstream clock information through this message. Then the nodes can perform proper operations on their clocks, such as tracing, switching, or converting to holdoff, and forward the synchronization information to downstream nodes. synchronize NE time

To send the system time of the server of the network management system to NEs so as to synchronize all NEs with the server.

synchronous digital hierarchy

A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is only used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure.

synchronous equipment timing source

The SETS function provides timing reference to the relevant component parts of multiplexing equipment and represents the SDH network clement clock.

synchronous optical network

A high-speed network that provides a standard interface for communications carriers to connect networks based on fiberoptic cable. SONET is designed to handle multiple data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbps, but multiples of this base rate go as high as 2.488 Gbps (gigabits per second).

synchronous transport Synchronous Transfer Mode at 155 Mbit/s. mode 1

T TCM

Tandem Connection Monitoring

TCP

See Transmission Control Protocol

TDM

See time division multiplexing

TE

See traffic engineering

Issue 01 (2011-10-20)


366


D Glossary

Telecommunication A protocol model defined by ITU-T for managing open systems in a communications Management Network network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services. terminal multiplexer

A device used at a network terminal to multiplex multiple channels of low rate signals into one channel of high rate signals, or to demultiplex one channel of high rate signals into multiple channels of low rate signals.

TFTP

See Trivial File Transfer Protocol

TIM

trace identifier mismatch

time division multiplexing

A multiplexing technology. TDM divides the sampling cycle of a channel into time slots (TSn, n=0, 1, 2, 3 and so on), and the sampling value codes of multiple signals engross time slots in a certain order, forming multiple multiplexing digital signals to be transmitted over one channel.

Time Slot

Continuously repeating interval of time or a time period in which two devices are able to interconnect.

Time Synchronization

Also called the moment synchronization, time synchronization means that the synchronization of the absolute time, which requires that the starting time of the signals keeps consistent with the UTC time.

time to live

A technique used in best-effort delivery systems to prevent packets that loop endlessly. The TTL is set by the sender to the maximum time the packet is allowed to be in the network. Each router in the network decrements the TTL field when the packet arrives, and discards any packet if the TTL counter reaches zero.

TL1

See Transaction Language 1

TLV

Type/Length/Value

TM

See terminal multiplexer

TMN

See Telecommunication Management Network

TP

traffic Policing

traffic engineering

A technology that is used to dynamically monitor the traffic of the network and the load of the network elements, to adjust in real time the parameters such as traffic management parameters, route parameters and resource restriction parameters, and to optimize the utilization of network resources. The purpose is to prevent the congestion caused by unbalanced loads.

Transaction Language Transaction Language One is a widely used telecommunications management protocol. 1 TL1 is a vendor-independent and technology-independent man-machine language. TL1 facilities can be provided as part of an OSS for interacting with either underlying management systems or NEs. One popular application is for a management system (or NE) to package its trap/notification data in TL1 format and forward it to an OSS component. ...(from authors.phptr.com/morris/glossary.html) Transaction Language 1 (TL1) is a widely used, "legacy", management protocol in telecommunications. It is a cross-vendor, cross-technology man-machine language, and is widely used to manage optical (SONET) and broadband access infrastructure in North America. It is defined in GR-831 by Bellcore (now Telcordia). (from en.wikipedia.org/wiki/TL1)

Issue 01 (2011-10-20)


367


D Glossary

Transmission Control Protocol

The protocol within TCP/IP that governs the breakup of data messages into packets to be sent via IP (Internet Protocol), and the reassembly and verification of the complete messages from packets received by IP. A connection-oriented, reliable protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in the ISO/OSI reference model.

tray

A component that can be installed in the cabinet for holding chassis or other devices.

tributary unit group

One or more Tributary Units, occupying fixed, defined positions in a higher order VCn payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that mixed capacity payloads made up of different size Tributary Units can be constructed to increase flexibility of the transport network

Trivial File Transfer Protocol

A small and simple alternative to FTP for transferring files. TFTP is intended for applications that do not need complex interactions between the client and server. TFTP restricts operations to simple file transfers and does not provide authentication. TFTP is small enough to be contained in ROM to be used for bootstrapping diskless machines.

trTCM

Two Rate Three Color Marker

TTI

trail trace identifier

TTL

See time to live

TU

tributary unit

TUG

See tributary unit group

U UAS

unavailable second

UAT

See unavailable time event

UDP

See User Datagram Protocol

unavailable time event A UAT event is reported when the monitored object generates 10 consecutive severely errored seconds (SES) and the SESs begin to be included in the unavailable time. The event will end when the bit error ratio per second is better than within 10 consecutive seconds. UNI

See user network interface

universal time coordinated

The world-wide scientific standard of timekeeping. It is based upon carefully maintained atomic clocks and is kept accurate to within microseconds worldwide.

Unprotected

Pertaining to the transmission of the services that are not protected, the services cannot be switched to the protection channel if the working channel is faulty or the service is interrupted, because protection mechanism is not configured.

upload

An operation to report some or all configuration data of an NE to the NMS(Network Management system). The configuration data then covers the configuration data stored at the NMS side.

Upper subrack

The subrack close to the top of the cabinet when a cabinet contains several subracks.

User

A client user of the NMS. The user name and password uniquely identifies the operation rights of a user in the NMS.

Issue 01 (2011-10-20)


368


User Datagram Protocol

D Glossary

A TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User Datagram Protocol (UDP) uses IP to deliver datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDP messages can be lost, duplicated, delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is, the destination device does not actively confirm whether the correct data packet is received.

user network interface The interface between user equipment and private or public network equipment (for example, ATM switches). UTC

See universal time coordinated

V VB

virtual bridge

VC

See virtual container

VCG

See virtual concatenation group

VCI

See virtual channel identifier

virtual channel identifier

A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination.

virtual concatenation group

A group of co-located member trail termination functions that are connected to the same virtual concatenation link

virtual container

The information structure used to support path layer connections in the SDH. It consists of information payload and path Overhead (POH) information fields organized in a block frame structure which repeats every 125 μs or 500 μs.

virtual local area network

A logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number. This is often associated with switched Ethernet.

virtual path identifier

The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs.

virtual private network A system configuration, where the subscriber is able to build a private network via connections to different network switches that may include private network capabilities. VLAN

See virtual local area network

VOA

Variable Optical Attenuator

voice over IP

An IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. VoIP involves sending voice information in a digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (PSTN).

VoIP

See voice over IP

VPI

See virtual path identifier

VPN

See virtual private network

VRRP

Virtual Router Redundancy Protocol

Issue 01 (2011-10-20)


369


D Glossary

W WAN

See wide area network

wavelength division multiplexing

A technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple channels to transmit simultaneously in a single fiber.

Wavelength protection The wavelength protection group is important to describe the wavelength protection group structure. Its function is similar to that of the protection subnet in the SDH NE. The wavelength path protection can only work with the correct configuration of the wavelength protection group. WDM

See wavelength division multiplexing

WEEE

waste electrical and electronic equipment

wide area network

A network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broad area, such as a province, a state or even a country.

Working path

The channels allocated to transport the normal traffic.

Working service

A specific service that is part of a protection group and is labeled working.

WRR

weighted round Robin

WSS

wavelength selective switching

WTR

Wait To Restore

WXCP

wavelength cross-connection protection

WXCP service

The WXCP service is also called the GE ADM protection service. The WXCP is a type of channel protection based on ring network. It adopts the dual fed and selective receiving principle and uses the cross-connection function to achieve service switching between working and protection channels.

X XFP

10Gbit/s Small Form-Factor Pluggable

XPM

cross-phase modulation

Issue 01 (2011-10-20)


370

Commissioning and Configuration Guide(V100R003C01_01)

Recommend Documents